eaglewen

Hi Wayne, Did you ever get a solution for this? I also are using rotary switches (not encoders) and when turning them on a regular speed often a position is lost. Turning slowly it works most of the time. Working with a mega2560. Thanks Werner

I think I'm missing something in Helios. I managed to get the VVI working via a kind of hack but now my altimeter is showing me the wrong value...in Helios I got 6100Ft while in DCS it is showing me 8100Ft. There must be somewhere a file to fix both issues, no? Werner

just found a solution by adding vvi=vvi*-1 to HeliosExport16.lua file My problem now is that the preflight-check in the control center is complaining that the configuration is not as expected...but it works. I hope someone has a better solution but for now it works for me function helios_private.processSimulatorData(selfData) local altBar = LoGetAltitudeAboveSeaLevel() local altRad = LoGetAltitudeAboveGroundLevel() local pitch, bank, yaw = LoGetADIPitchBankYaw() local vvi = LoGetVerticalVelocity() local ias = LoGetIndicatedAirSpeed() local aoa = LoGetAngleOfAttack() local glide = LoGetGlideDeviation() local side = LoGetSideDeviation() -- send this best effort (NOTE: helios.send will filter nil values) if (pitch ~= nil and bank ~= nil and yaw ~= nil) then -- these are text keys, which is very slightly slower but avoids collision with modules and drivers helios.send("T1", math.floor(0.5 + pitch * 57.3), "%d") helios.send("T2", math.floor(0.5 + bank * 57.3), "%d") helios.send("T3", math.floor(0.5 + yaw * 57.3), "%d") helios.send("T4", altBar, "%.1f") helios.send("T5", altRad, "%.1f") if math.abs(vvi) < 0.04 then -- don't send +/- 0.0 while bouncing on the ground vvi = 0.0 end vvi=vvi*-1 helios.send("T13", vvi, "%.1f") helios.send("T14", ias, "%.1f") helios.send("T16", aoa, "%.2f") helios.send("T17", glide, "%.3f") helios.send("T18", side, "%.3f") helios.send("T19", LoGetMachNumber(), "%.2f") local accel = LoGetAccelerationUnits() if accel ~= nil then helios.send("T20", accel.y or 0.0, "%.1f") end end end

Hi, I'm running the latest version of DCS and Helios with F-16C-50 I've setup the AOA, the ADI and the VVI on a monitor to use in the the central console. Everything is working fine except the VVI...this one is running reverse/opposite....meaning that when I'm going up the black part is showing while I'm going down the white part is moving. My AOA and ADi are running as they supposed to run. Any idea how this can be solved....should I edit the DCS.F-16C_50.hif.json file for instance? Not sure what the value and mappedvalue does. Or is there maybe an easier way in Helios? Any help is welcome { "heliosType": "DCS.Common.ScaledNetworkValue", "device": "Vertical Velocity Indicator", "name": "VVI", "description": "TODO: assign units, set calibration points, and write description", "exports": [ { "format": "%.4f", "id": "16" } ], "valueDescription": "TODO: describe range of output values after calibration", "unit": "Numeric", "calibration": { "points": [ { "value": -1, "mappedValue": -1 }, { "value": 1, "mappedValue": 1 } ], "precision": 4 } },

Hi, did you get my message from a couple days ago?

Hi, same question for me...did you manage to get it to work? Is it possible to extract the HUD (for me from the Viper)? Thanks

Hi Chroustall, In attachment the font I use on my DED. The ° and the up/down arrows are fixed in this font. I'm using the DEDFont16px.c in my ino file. Seeya Werner DEDfont16px.c DEDFont16px.fon DEDFont16px.bdf

Thanks to the both of you (for some reason I've missed your posts and today I stumbled on them )...I'm going to try with a potmeter....thanks for the tip

Hi, I copied the code above and changed to my own font and hurray it works again....I needed to change to the new addresses though to make it work (check your DCS-BIOS for these new addresses). Just to let you know Werner

Hi, I managed to get my DED working in a way as described above, tweaked a bit with the font and changed some minor things. It was working fine under DCS World 2.5 Beta. Then I updated my DCS to 2.7 and suddenly it isn't working anymore. The first thing I already noticed is the address change in DCS-BIOS, for instance first line was 0x44fc and now it seems to be 0x4500. However, if that was the only problem I would be out of the woods quickly. Even after changing this value nothing appears on my display...I reconnected the Arduino back to my old DCS system and it keeps working (with 0x44fc). I have the feeling DCS-BIOS isn't giving me the data back (the Webpage of DCS-Bios is reporting the values dough) or the data has another data-format which can't be used as written in the script. I don't have a clue to be honest. Any other persons having the same issue after updating? Thanks in advance Werner

anyone having the same behavior?

Hi, I'm using DCS-Bios to control my home-build-cockpit. Currently I'm interfacing the TrimWheels (pitch, roll, yaw) and I have an unexpected result. I'm using the command: DcsBios::RotaryEncode pitchTrim("PITCH_TRIM", "-3200","+3200", 48,49) When I turn the encoder one detent it goes directly to a fixed position (I gues +3200) and it stays there, even when I turn the enoder further. When I turn it one detant in the other direction it goes to the opposite position (I guess -3200). When I change the values to +-65535 it goes directly to the max position after turning it one detent. When I use the same encoder for changing the ehsiHdgSetBrn I see that the heading is turning fine, by turning the enoder the heading is following. So, the encoder is working fine but the behavior with the trim is not what I expect. Any idea what is wrong? Anyone else having the same problem? Thanks in advance Werner

Hi Matbog, can you tell us a bit more about how you interface the TACAN? Do you use the original parts or did you replace it with a stepper motor or something else? Thanks in advance Werner

Hi, I'm starting with DCS-BIOS. I managed to get the switches on the F16 to work via the Arduino as also outputs (leds). Next part is interfacing servos. Within the F16 I can't get them to work. With the P51 I get it to work with for instance the carbine temperature. The difference is that I see in the control reference (DCS-BIOS WEB interface) of the F16 'no data yet' for all the gauge values. For the swiches I see there is 0 or 1 ...for the AO for instance it stated 'No data yet'. When I do the same with the P51 I see some data appearing and of course because of this the servo is working fine in this case. The indicator of the virtual cockpit is green as soon as I start the F16 to fly, so I know there is connection between all things So my questions is ...what I'm doing wrong...the construction should be fine because of the working switches and the working servo with the P51. Do I need another F16 DCS-BIOS library maybe? It was recognized as a correct plugin within DCS-BIOS Seeya Werner

No one?