AlMassimo

Yes they are for FBW A320 (or "A32NX") that has different controls for left and right seat switches. Most of FBW variables are "A32NX_something" but probably the first added were still "A320_something" and this causes some confusion, since they are difficult to distinguish from default A320 variables. It could be a good thing to have different hvar files for A320 and FBW A32NX.

Ok very interesting. I fixed the Hvar issue following your indications 1) updated with lates beta 3.9 2) added to A320.hvar under "modules" folder these 2 lines : H:A320_Neo_MFD_BTN_ARPT H:A320_Neo_PFD_BTN_LS And now also ipc.activateHvar works perfectly.

Thanks John, I agree, using calculator code in lua is an extremely powerful and useful option, so probably I won't use activateHvars, that initially seemed more straightforward and easy, but in the end calculator code is probably the most effective tool and can do almost everything! Best regards Massimo

Hi John, I use LUA for managing LVARS and all works very well. Since I use OpenCockpits MCP and EFIS, I have to use some offsets ("A001, A002, A003...") to allow LUA to detect OC buttons or knobs, and then it sets the LVARS properly. So this code works perfectly (with default Asobo A320 neo) : function MFD_RANGE_SET() MFD_range = ipc.readUB(0xA001) ipc.writeLvar("L:A320_Neo_MFD_Range", MFD_range) end event.offset("A001","UB", "MFD_RANGE_SET") When offset A001 changes (controlled by my O.C. EFIS range knob, the Lvar is set correctly. I tried to handle also HVARS : function PFD_ILS_MODE() ILS_BTN = ipc.readUB(0xA004) if ILS_BTN == 1 then ipc.activateHvar("H:A320_Neo_PFD_BTN_LS") end end event.offset("A004","UB", "PFD_ILS_MODE") This DOESN'T WORK, but if I replace the activateHvar with calculator code, it works perfectly function PFD_ILS_MODE() ILS_BTN = ipc.readUB(0xA004) if ILS_BTN == 1 then ipc.execCalcCode("(>H:A320_Neo_PFD_BTN_LS)") end end event.offset("A004","UB", "PFD_ILS_MODE") What I am doing wrong with ipc.activateHvar ? No problems for me to use calculator code, but I would like to understand why ipc.activateHvar doesn't work. The same happens with other Hvars, all work in calculator code but not in ipc.activateHvar. Maybe that this happens because I can't find those Hvars under wasm --> list Hvars, but the calculator code finds them. How can I add them to FSUIPC ?

Hello Jose, time ago I considered buying that panel (but then I didn't); it doesn't seem to be compatible with MSFS (you don't specify if you use MSFS but since you are posting on FSUIPC7 forum I suppose so). Anyway have you seen this video ? https://www.youtube.com/watch?v=5M2YrVHU2ew It seems to be quite comprehensive and step by step guide on how to configure your device. (but probably you want to use it as a "joystick" device I think)

WOW this is something I have to try!!! THANKS this IS the best way IMO! I'm sorry I didn't figure it out before...

ANYWAY (and I wont bother you any longer on this subject) since a simple list Lvars solve everything, it appears to me that Fsuip CAN do something to update Lvars created much too later to solve the problem by increasing lvar scan delay... to what, 120 secs ? No way, at least for me, I'll do a list Lvars and all works. Bye John

Ok sorry I thought it was an interesting issue, but of course it's not for all, for me all this was very instructive though. best regards ant thanks for your time

I found this on log : 153141 3692 *** EVENT: Cntrl= 66984 (0x000105a8), Param= 0 (0x00000000) COM3_VOLUME_SET 153454 3692 *** EVENT: Cntrl= 67230 (0x0001069e), Param= 1 (0x00000001) AP_MANAGED_SPEED_IN_MACH_OFF 154047 3692 *** EVENT: Cntrl= 67230 (0x0001069e), Param= 1 (0x00000001) AP_MANAGED_SPEED_IN_MACH_OFF 154141 3984 **** Lvar 'FLIGHTPLAN_APPROACH_COURSE' not found: cannot add to offset 0xA022 154157 3692 *** EVENT: Cntrl= 66964 (0x00010594), Param= 1 (0x00000001) COM1_RECEIVE_SELECT 154157 3692 *** EVENT: Cntrl= 66965 (0x00010595), Param= 0 (0x00000000) COM2_RECEIVE_SELECT 154157 3692 *** EVENT: Cntrl= 66966 (0x00010596), Param= 0 (0x00000000) COM3_RECEIVE_SELECT 154157 3692 *** EVENT: Cntrl= 66978 (0x000105a2), Param= 100 (0x00000064) COM1_VOLUME_SET 154157 3692 *** EVENT: Cntrl= 66981 (0x000105a5), Param= 0 (0x00000000) COM2_VOLUME_SET 154157 3692 *** EVENT: Cntrl= 66984 (0x000105a8), Param= 0 (0x00000000) COM3_VOLUME_SET 154204 3984 Lvars/Hvars received - checking aircraft autos.... 154204 11212 LUA.1: beginning "D:\FSTools\FSUIPC7\ipcReady.lua" 154344 3692 *** EVENT: Cntrl= 67251 (0x000106b3), Param= 10 (0x0000000a) NAV1_RADIO_SET_HZ 154454 3692 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 2048 (0x00000800) NAV1_RADIO_SET 154547 3692 *** EVENT: Cntrl= 67230 (0x0001069e), Param= 1 (0x00000001) AP_MANAGED_SPEED_IN_MACH_OFF The messge appears ONLY for COURSE not for ILS, so it was not loaded at all in fsuipc.ini I tried with wasm reload when Lvar was correctly listed but still it was not loaded on offset A024

Uselessly stubborn I must say... Did not work of course... weird that the frequency is updated, but the course not, only after list Lvars... well, I'll do a list Lvars just after setting the flight plan, not a big deal, but still weird for me.

Done, wasm scan delay increased to 50, this takes a LOT of time before being able to control MDF display (before it was just after 25 secs and always worked, both MDF MODE and MFD RANGE. But this is not a big problem. The problem is that this time ILS frequency was correctly read and set by LUA and displayed on radio panel BUT COURSE DID NOT. I checked in console and lua did not detect any event connected to ILS COURSE. Even this time, hitting list LVARS, immediately it was read and displayed... I think it would be great to do some LVARS rescan, let say once every 10 seconds, or even more, just to be sure to intercept also LVARS created during flight, as ILS frequency and course (they are not even listed before creating a plan with an ILS approach). Just because I'm a little stubborn (or very stubborn) I'll try again to define these 2 lvars in Fsuipc7.ini and see if they worked again as they did yesterday, regardless of was scan delay or list Lvars command...

Ok I've seen your reply, I have currently 25, I can increase to 50 but after 25 many Lvars are read (and work) but when I do the first list Lvars they still apear 0 and change only on second list Lvars

Hi John, apparently there is some issue in updating Lvars, that is solved only with a list Lvars. Until I click on list Lvars (some) Lvars are not updated or not read at all. I mean some because these [LvarOffsets] 1=A320_Neo_MFD_NAV_MODE=UBA000 2=A320_Neo_MFD_Range=UBA001 4=BTN_TERRONND_ACTIVE=UBA005 are read correctly and they control the MFD display just after some seconds of delay from flight start (as set in wasm.ini) other do not

Here is the lua code if you want to have a look at it function ILS_freq_set() ILS_freq = ipc.readLvar("FLIGHTPLAN_APPROACH_ILS") * 100 + 0.001 ipc.control(67251, ILS_freq * 10000) end function ILS_course_set() ILS_course = ipc.readLvar("FLIGHTPLAN_APPROACH_COURSE") + 0.001 ipc.control(65716, ILS_course) end event.Lvar("FLIGHTPLAN_APPROACH_ILS", 500, "ILS_freq_set") event.Lvar("FLIGHTPLAN_APPROACH_COURSE", 500, "ILS_course_set")

Hi John, I tested the lua code and obtained some apparently incoherent results. At first, having removed the Lvar assignment in Fsuipc7.ini, loaded the flight, configured the airplane for takeoff, then set the CDU for ILS approach and the event was triggered, and the ILS frequency was detected and transferred to NAV1 active frequency 0x0350, and this caused SIOC to immediately update the display on the NAV1 panel. I was encouraged to add other code to my lua program in order to get also the ILS course value. Also this worked fine. I was confused. Then I made another fly, same settings, but this time the frequency was not updated. I went to Fsuipc wasm menu and selected list lvars. ILS frequency was 0 and all other Lvars were still 0. But in the same instant when I selected list Lvars suddendly the NAV1 display showed the ILS frequency! I hit list Lvars again and this time all Lvars showed their values. Very strange they were still 0 the first time, because the plane was loaded many minutes before, so all Lvars should have been loaded by then. I enclose the Fsuipc.log file, so you can analyze and check what was wrong. FSUIPC7.log