Vinc_Vega

Thanks for explaining the difference, Regards, Vinc

Edited: No, it's just a "send command" in text form like this DcsBios::tryToSendDcsBiosMessage("FSCP_BOOST_MAIN_L", "1"); The pins have to be declared and read within normal Arduino code. Than and under defined conditions (pin high or low) the command will be send. Now that I'm back at my laptop, I may give further hints. If you follow the sketchbook entry for the 16bit expander, you'll see a few more examples on how to use such code. Beware of that the text messages to DcsBios only have to be send if a signal has changed (e.g. switch to a new position), else it may block the bus traffic. Regards, Vinc

Thank you! Maybe here is a part of the solution to see updates in the HUD only view: Regards, Vinc

Thank you for the reply. Best regards, Vinc

No answer so far, just try to pull from here: https://github.com/DCSBIOSKit/dcs-bios-arduino-library/tree/rs485 But keep a backup of your files! Regards, Vinc

I knew that I've read it somewhere: https://dcs-bios.a10c.de/docs/v0.5.1/userguide.html#_aircraft_specific_notes Regards, Vinc

It's a matter of the cockpit view only rendered displays not the devices. So input should be possible, even if there is no visible output. Regards, Vinc

@maciekish Do you have any experience with your fix, running more than one RS485 bus per Mega? Regards, Vinc

I somewhere red that the HUD only view may cause trouble with rendering some instruments. The clock maybe one of these. It also can be the case in external views. Therefore, an additional viewport, rendering the cockpit should be created. That view may be outside of the visual area and in the size of only 1 by 1 pixels. But I haven't done that, so far no experience. Regards, Vinc

Hi Purzel, according to the control reference in your case I would suggest to use the code from the "Internal Lights" section -> Instrument Lightning (light green) of the F-18. That represents the gauge position and not the position of the potentiometer. void onInstrIntLtChange(unsigned int newValue) { /* your code here */ } DcsBios::IntegerBuffer instrIntLtBuffer(0x7560, 0xffff, 0, onInstrIntLtChange); Within the "your code here" section you have to define the output signal. See below code snippet from the A-10C console light script for example, that is included in almost all my panels. The pot is connected to A2 (analogue input pin, only applicable to the lighting control panel), digital pin 3 is used as signal output for backlit panels. You therefore, first have to declare the output pin (must be a pin with PWM functionality). As an Arduino Nano is only capable to PWM signals from 0 to 255 (0 to 5Volt), in my case the mapping function is simply a division of the returned "new Value" by 256. The calculated value finally is written as an analogue value to the output pin (PWM signal). I then use the 0 to 5Volt steering signal to control the brightness of a 12Volt backlighting LED-Strip via MOSFET. Best regards, Vinc

Hi Purzel, I have to look into the control reference later when I'm back home, but at the first glance your output seems to be the position of the Potentiometer. I mean the rotating animation of the knob itself in the cockpit. That may be a workaround if really no output of the backlighting is available. Regards, Vinc

Thanks, so than recieving a CDU page or the Caution Panel Lights via RS485 shouldn't be so slow anymore? Regards, Vinc

Thanks for the feedback. Regards, Vinc

Dear developers, Building the hardware and software for my A-10C cockpit since years, now one of the radios has to be reworked to reproduce the simulation. Most data are exporteable via interfaces like DcsBios but that seems not fully the case for the newly introduced ARC-210 radio. Is there a possibility to export the display other than using yet another viewport? Would you please document the ARC-210 simulation interface for cockpit builders? Thanks in advance. Best regards, Vinc

The script should be in the C:\Users\...\Saved Games\DCS.openbeta\Scripts\Programs folder, where you also can find the connect-serial-port.cmd file. After editing the cmd-file just make a shortcut to your desktop to open (not edit) it for the start. Regards, Vinc

Yes, in theory you only have to adjust one line within the multiple-com-ports.cmd script with a text editor. Just add your com ports, separated by a space, like below for ports 8 and 16: @echo off REM The COMPORTS variable should be set to a space-separated list of COM port numbers: set COMPORTS=8 16 for %%i in (%COMPORTS%) do start /b cmd /c connect-serial-port.cmd /Q %%i But practically, it doesn't work reliable for me either. Regards, Vinc

Hi Les, we had a long discussion on the altimeter sketch of the Bf-109. Maybe there are some useful points for your investigation. Else we may again discuss details via PM. Best regards, Vinc

Congrats, you finally made it working! It's your design and therefore, has to work only at your rig. If, sometimes in the future, you'll improve details or your own PCBs, you may get rid of the second Mega. But do I understand it right, that the termination, pullup and pulldown resistors brought no more stability? And the additional line of the second Mega fixed the glitches? Regards, Vinc Additionally, did you split the inputs and outputs to different lines?

In theory both ends of the line should have termination resistors. Not shure if it is getting better if you'd used an additional resistor at the Mega's end. Regards, Vinc

I'm interested too. Regards, Vinc

Yes, R5 and R6 are for signal stability, pulldown (line B low) and pullup (line A high) respectively, and should reduce the noise on the lines. You sometimes see such resistors in I2C connection too. Those resistors, if necessary, are only applicable to one end of the lines. Regards, Vinc

Hi Les, Have a look at the ready made RS485 modules. All the resistors seem to be of the SMD type. In my opinion R7 is one of the resistors you are looking for, 120 Ohm between the A and B lines. https://arduinoinfo.mywikis.net/wiki/RS485-Modules So the answer to your question is: No Regards, Vinc

Hi BeBe, No, it displays the Fuel Flow Couter values of the F-16. Have a second look at the clip posted here: According to the control reference the addresses for the flow counter are 0x44e8, 0x44e4 and 0x44e6. That of the fuel totalizer display are 0x44f2, 0x44ee and 0x44f0. We already had an issue with the A-10 and Bf-109 in the past, that some addresses had changed. So maybe you have to update your DcsBios files? Regards, Vinc

Update of the adjustable sketch for the SH1106 I2C OLED, including shrinked numbers (by 2 pixels in width and height each). Graphics file see below for download, let me know if the numbers should be smaller. Regards, Vinc digits_22x30.h

Hi Enabler, I did some modifications to the sketch, so you may adjust it to your needs. The digits may be shifted vertically by a new constant "BL" (for bottom line). Horizontal shifting may be done by adjusting the variable "h_adj", where 0 alligns all left and 4 centers the output to the display. Furthermore, the black rectangular areas are swapped with white filled rects to illuminate your engravings. That backlights even may be adjusted to your instrument bezel. I think you'll make it, just read the comments from line 17 on. Unfortunately I haven't found an easy way to reduce the fontsize, so the above "characters_n.h" file is still in use. EDIT: update see below posting Regards, Vinc