Jocman Posted May 4, 2024 Posted May 4, 2024 Hi all. I'd like to report a couple of errors I found in BoRT snippets while trying to display the R-800 VHF frequencies (Ka-50 BS3). I was keeping having the same error message on arduino IDE whe trying to read FrequencY1: "Ka_50_R800_FREQ1_A was not declared in this scope" After lot of try, I checked the library Addresses.h and found that the right string is not "Ka_50_R800_FREQ1_A" but "Ka_50_R800_FREQ1_ADDR" Same issue (and solution) for Frequency4: is not "Ka_50_R800_FREQ4_A" but "Ka_50_R800_FREQ4_ADDR" Jocman "For once you have tasted flight you will walk the earth with your eyes turned skywards, for there you have been and there you will long to return" (L. Da Vinci) Prev. Projects: https://forums.eagle.ru/showthread.php?t=50071
No1sonuk Posted May 4, 2024 Posted May 4, 2024 I've flagged this thread in the Skunkworks Discord. If you have a Github account, you can also create an "issue" there.
charliefox2 Posted May 4, 2024 Posted May 4, 2024 Hey Jocman, I took a look at this and it seems like the issue is that you're using a version of bios from between August-September 2023. This old version used to generate ids like this, before we had to change it due to a bug and some control types missing. I'd recommend you update to the latest version of bios, which you can get here https://github.com/DCS-Skunkworks/dcs-bios/releases/latest
Jocman Posted May 5, 2024 Author Posted May 5, 2024 (edited) 11 hours ago, charliefox2 said: Hey Jocman, I took a look at this and it seems like the issue is that you're using a version of bios from between August-September 2023. This old version used to generate ids like this, before we had to change it due to a bug and some control types missing. I'd recommend you update to the latest version of bios, which you can get here https://github.com/DCS-Skunkworks/dcs-bios/releases/latest Uhmmmm, honestly when i got the issue, i downloaded all the new fork related releases from skunkworks (arduino library, dcsbios and bort). Right now i'm not home, but if i'm not wrong dcsbios is release 8 (or anyway the all-in-one or smtg like) and the library i'm sure is the last update. Same about bort. To be someway sure, i first deleted everything the reinstalled the updated versions. Then i got the issues i'm reporting Edited May 5, 2024 by Jocman Jocman "For once you have tasted flight you will walk the earth with your eyes turned skywards, for there you have been and there you will long to return" (L. Da Vinci) Prev. Projects: https://forums.eagle.ru/showthread.php?t=50071
charliefox2 Posted May 6, 2024 Posted May 6, 2024 It looks like the Addresses.h file in the arduino library repo is hopelessly out of date. Try using the Addresses.h file in the dcs-bios repo https://github.com/DCS-Skunkworks/dcs-bios/blob/master/Scripts/DCS-BIOS/doc/Addresses.h
Jocman Posted May 12, 2024 Author Posted May 12, 2024 Here again with another issue. This time is Targeting Mode Control Panel. The problem is the Head-on airborne target button My snippet code is: //AUTOTURN BTN DcsBios::Switch2Pos weaponsAutoTurnBtn("WEAPONS_AUTO_TURN_BTN", AutoturnBtn); //A/A H O BTN DcsBios::Switch2Pos weaponsForwardHemiTargetBtn("WEAPONS_FORWARD_HEMI_TARGET_BTN", AAHBtn); But in the sim autoturn works properly, the second one gives no sign of life. In Socat I can see the commands as in picture, where you can see the first command given is related to Autoturn and the second to Head-on airborne target button In both cases the command is sent, but only the first get a response, not the second. Honestly the second message sent seems very weird to me, but this is what I'm getting (only 1 and 0, with no message.....).... On 5/6/2024 at 5:03 AM, charliefox2 said: It looks like the Addresses.h file in the arduino library repo is hopelessly out of date. Try using the Addresses.h file in the dcs-bios repo https://github.com/DCS-Skunkworks/dcs-bios/blob/master/Scripts/DCS-BIOS/doc/Addresses.h Well I tried but when I compile I get a bounch of error related to the new Addresse.h, so I back the the last one.... Jocman "For once you have tasted flight you will walk the earth with your eyes turned skywards, for there you have been and there you will long to return" (L. Da Vinci) Prev. Projects: https://forums.eagle.ru/showthread.php?t=50071
Jocman Posted May 18, 2024 Author Posted May 18, 2024 (edited) Here again one more time. I'm reporting an "extended issue" (or I suppose it could be really extended). The last release of BORT owns a very interesting feature, the Address Constants; as I think them very useful, I decided to change all the arduino sketches where I use LEDs (there are a lot of lamps in the Ka-50......). So for an entire week (the freetime isn't so much) I updated alle the LED sketches by using the new address constants snippets. While compiling every updated sketch, I got always the same error msg "X was not declared in this scope" for every LED snippet. Checking the Address.h library, the issue is related to a "_AM" suffix in the BORT snippet with no correspondence in Address.h library. My first solution was to arbitrary delete alle the _AM suffixes in every snippet. When compiling I didn't get any error msg more, so I updated all the sketches this way. This morning I started to upload the new sketches to the boards. The first "lucky one" was the APU Control Panel lamps. The same arduino drives the Fuel Vlv Levers and the Brake lever. I realized that the panel stopped working: the levelers where dead, so as the LEDs. After several try and retry (and a burned arduino ....damn....) I checked the snippets and the Address.h again Something like: APU fuel shutoff valve is open Lamp (green) DcsBios::LED apuFuelVlvOpen(Ka_50_APU_FUEL_VLV_OPEN_AM, PIN); But in Address.h it should be: Ka_50_APU_FUEL_VLV_OPEN 0x191A, 0x1, 0 But beside the missing _AM suffix, even the values aren't matching. In fact, unticking the Use Address Constants box in BORT, the same LED has this snippet: DcsBios::LED apuFuelVlvOpen(0x191a, 0x0001, PIN); But these values don't match the Address.h library. I'm not a programmer (not at all....), but I think 0x1 is not seen in the same way as 0x0001 by a computer So, unticked the box, I used the other snippets, and everything started working fine now. I don't know if I wrote a lot of bulls**ts and there's no issue at all (it's just me an idiot) , but is the only solution I found for the problem. Nevertheless, the possibility to use a constants is very useful for the reasons they where implemented in DCSBIOS, so I'd like to use it someday. By now I think I'll reprogram all the sketches back to the old version.... @No1sonuk As I have a github account now, can you tell me where to report an issue there? and if you can be so kind to report this new one to for me now. Sorry if I ask again, but is there any solution the the previous message issue (the Head-on airborne target button)? Thanks all Edited May 18, 2024 by Jocman Jocman "For once you have tasted flight you will walk the earth with your eyes turned skywards, for there you have been and there you will long to return" (L. Da Vinci) Prev. Projects: https://forums.eagle.ru/showthread.php?t=50071
No1sonuk Posted May 18, 2024 Posted May 18, 2024 4 hours ago, Jocman said: @No1sonuk As I have a github account now, can you tell me where to report an issue there? and if you can be so kind to report this new one to for me now. Each of the DCS-BIOS related sections has an "issues" tab. This one is specific to BORT: https://github.com/DCS-Skunkworks/Bort/issues
Recommended Posts