AlMassimo

And here is the translation... pretty lapidary... "Question 2: According to the log, this is a BVar (>B:AIRLINER_LS_Toggle) As far as I know, BVars are currently not usable."

This is the page were I found "(>B:AIRLINER_LS_Toggle)" https://www.mobiflight.com/forum/message/25041.html

Hi John you were right, of course! variable L:BTN_TERRONND_ACTIVE was displayed in the list but I missed it. This is solved and works. Coming to the variable AIRLINER_LS_Toggle I tested with 1 (>K:AIRLINER_LS_On) but it didn't work I enclose a screenshot of the Behavior panel in developer mode with the variables highlighted and pinned. Searching on the net I found this reference to "(>B:AIRLINER_LS_Toggle)" but I can't speak deutsch so I cannot understand what they say It's a pity because all the efis controls are listed under the tab "airliner" in MSFS/Behavior/Events page.

If it is an event it was not tracked by the events in console, i pressed repeatedly the button in the VC but nothing was displayed under the console. Are the B and F type currently traceable somehow ?

I meant also with Mobiflight of course.

Hi John, the variable L:BTN_TERRONND_ACTIVE was not displayed in LVAR list, does the list include ALL the LVARS used by the plane or only those already known ? I can't remember having seen it, and I added succesfully in the .ini file, after that it worked perfectly but maybe I missed it in the list. Seems to be a general use LVAR so could be interesting to add if a basic list is created. Also AIRLINER_LS_On seems to be a generic airliner event (if it is an event) - I couldn't test it yesterday (was too late in Italy) but I'll do that this evening. Things are looking promising! With this procedure I hope to find more specific controls for the FCU, even if HDG, SPD ALT and VS SLOT functions are working (but only with the default A320 unfortunately). Next step will be to activate more EFIS buttons (Constraint, waypoints, airports), I've also found an interesting tutorial for a complete CDU keyboard with a simpe Arduino Micro and Fsuipc!

WoW!!! I'll install and try! In the meanwhile, I made some progresses... I searched under (MSFS folder)\LocalCache\Packages\Official\OneStore\asobo-vcockpits-instruments-a320-neo\html_ui\Pages\VCockpit\Instruments\Airliners\A320_Neo\MFD\A320_Neo_MFD.js and found this LVAR L:BTN_TERRONND_ACTIVE that I tested successfully adding it in FSUIPC7.ini I couldn't find a var for the PFD LS display mode, and so went on DEVELOPER MODE/BEHAVIOR --> A320_Neo --> interior events page was empty but hitting "Quick Reload" after some seconds it was populated by a lot of tags, selecting AIRLINER I found AIRLINER_LS_On and using the parameter 1 and 0 and hitting "Execute" the LS was activated and deactivated. GOOD! So I tested it as an LVAR setting it in FSUIPC 0 or 1 but didn't work. Probably it's not an LVAR, cannot even be an HVAR since it has a parameter... so this procedure seems to be very useful to find out internal variables (or events, like AIRLINER_LS_Toggle) but I must understand how to use these vars! Maybe they are A: vars. Now I will test the new version and will report the results, thanks John!

That would be wonderful!

Hi John, I will do more testing with 3110, I hope to get it working. Regarding A320_Neo IMHO is very confusing that some (many) of the FBW HVARS have the name A320_Neo_somewhat, instead of A32NX, I mean something different from A320_Neo. as you suggested I'll probably end up to convert my cockpit for the FBW, but at the moment I have all working (almost 90%) fine with A320_Neo, the FCU works very well with SLOT values 1 and 2 and all controls are fully operative, but almost none of them works with the FBW, even the throttles needs totally different calibration, parking brake, speedbrake, EFIS, all require reprogramming the code with new HVARS and LVARS, but now I know how to do that. Before giving up I'll try to catch the HVARS or LVARS used by A320_Neo with the MSFS developer mode "behavior display", there is an interesting video about this here https://www.youtube.com/watch?v=PKBjEl9E5A4 it's referred to MobiFlight but I need to transfer the variables to offsets and use or activate them via SIOC-FSUIPC and maybe LUA. I'm writing all this to share my experience with other simmers, sorry to take up your time but these new functions available through WASM and LVAR/HVAR handling are so powerful that I think is useful to share any possible achievement or working example. Thanks for your extraordinary work.

New update The HVARS I was trying to activate with Asobo A320 don't work (as John suggested) but they work with FBW A320, current stable version. Once selected the FBW 320 (and after having studied the updated manual - that I was unaware was installed under "users\massimo\mydocuments") I managed to activate properly some HVARS in different ways : macro file (.mcro) [Macros] 1=H:A320_Neo_PFD_BTN_LS_1=Set 2=H:A320_Neo_MFD_BTN_TERRONND_1=Set 3=H:A320_Neo_MFD_BTN_CSTR_1=Set 4=H:A320_Neo_MFD_BTN_WPT_1=Set 5=H:A320_Neo_MFD_BTN_VORD_1=Set 6=H:A320_Neo_MFD_BTN_NDB_1=Set 7=H:A320_Neo_MFD_BTN_ARPT_1=Set Via calculator code (>H:A320_Neo_PFD_BTN_LS_1) and finally via SIOC using a button on my MCP, changing the state of a custom offset (0xA010) read by a LUA basic code function update_switches() test_BTN = ipc.readUB(0xA010) if (test_BTN == 1) then ipc.activateHvar("H:A320_Neo_PFD_BTN_LS_1") end end -- update_switches event.timer(200,"update_switches") This worked, but I have multiple change of state of the HVAR, I must set a flag to avoid this, not difficult. The only thing I couldn't make to work was the Var 0001 name FS_CONTROL Link FSUIPC_OUT Offset $3110 Length 4 using the value 262144 that should have activated the HVAR in myevents.txt A320_Neo_MFD_BTN_LS_1#(>H:A320_Neo_MFD_BTN_LS_1) I will do more testing on this part because it would be much more direct and does not require lua code. So, now almost all seems to make sense, I only wonder how to find the LVARs or HVARS that control the EFIS and FCU in Asobo A320_Neo...

Oh Thanks!!! Maybe I simply installed fsuipc without selecting docs, I can't remember having seen that option. I'll study the new manual before bothering you again, I promise. Thanks for your support, I love LVARS they work like a charm, but at the moment I HATE HVARS... but it's my fault. YES I forgot to activate logging of buttons. Now I see the HVAR being called by the button, but doesn't trigger the LS, I must study the aircraft logic. Thanks again

Hi John, thanks for your patience and sorry for my confusing (and confused) post. I try to clarify my doubts "Did you restart FSUIPC7? Presets are only loaded on start-up. " Of course I did, my preset is visible listing HVARS, and there is also the same HVAR I created a preset for, but as you said I can use my own preset, this does not harm, but if the HVAR is already present is useless to create a custom one. When I wrote "I tested both", I mean my own preset, and the existing one (H:A320_Neo_PFD_BTN_LS_1). Assigning this HVAR to a button does not trigger any effect. If I simply "activate" the HVAR nothing happens. I expect the LS button to light up and the LS reticle to appear in the PFD, but this doesn't happen. Given that I created the custom preset PFD_LS# (>H:A320_Neo_PFD_BTN_LS_1), this should be assigned the value 40001, so in SIOC code I tested these lines : Var 0001 name FS_CONTROL Link FSUIPC_OUT Offset $3110 Length 4 Var 0002 name FS_PAR Link FSUIPC_OUT Offset $3114 Length 4 Var 0154, name I_PFD_LS, Link IOCARD_SW, Input 34 { IF &I_PFD_LS = 1 { &FS_PAR = 1 // Is this required ? Probably not &FS_CONTROL = 40001 &FS_CONTROL = DELAY 0 10 } } This should trigger LS display ON/OFF but doesn't work. I will test also 262145 (&FS_CONTROL = 262145) since I'm not sure it is a HEX or DEC required. Coming to the calculator, you say I have to input simply "(>H:A320_Neo_PFD_BTN_LS_1)" right ? This should trigger the LS function on/off ? Or just activate the HVAR ? I'm sorry to ask all these questions, but I just installed the new release of FSUIPC and under the documents I find FSUIPC7 for Advanced Users.pdf 8/1/2021 but at page 45 there is nothing about this, it just talks about joysticks, no WASM section at all, where can I find the updated guide ??? Thanks, I owe you a dozen beers, I know...!

BIG update! I removed completely the MobiFlight Wasm module from community folder and removed all the FSUIPC assignments to yoke axis and throttle levers (all analog axis I have) and assigned them directly to MSFS. The result is... 3 hours of intensive flight activities, FSUIPC, SIOC and Mobiflight real-time configurations and reload, CDU managed flights, all sort of test and NOT A SINGLE CTD... never happened before! I also used Spacedesk to display the popup gauges on a secondary PC with only a little framerate drop. All flights were performed with FSUIPC standard and custom offsets activated by Mobiflight (Arduino) or SIOC (Opencockpits devices) including the 2 LVARS that I inserted in FSUIPC.ini that worked perfectly. Seems that something caused conflicts or trouble between FSUIPC, MF and MSFS, but now all seems to work consistently. I need some further help with HVARS (see my previous post) I can't manage to assign them or to see them operating) especially for EFIS and FCU managed modes (I had some success with SLOT offsets, even not completely solved by now). Handling LVARS and HVARS would allow to control almost every function of the specific plane, but what will happen when I fly with another plane ?

I started testing but I have some questions... I created a file myevents.txt containing only one row PFD_LS# (>H:A320_Neo_PFD_BTN_LS_1) and I can find PFD_LS in the presets list, but I also see the same H_var already included in HVARS, do I need to put it also under myevents.txt ? H:A320_Neo_PFD_BTN_LS_1 is there already a control value for this one and how do I find it ? I tried to assign both to some key or button, but on the console I don't see this HVAR being called when I press that button/key. What am I doing wrong ? What string should I put in the calculator to see it executed ? And what should I obtain ? In the case of events.txt, the presets would get the offset (I think is an offset, or a control value) 0x400001 (or 26215) I suppose it's 0x40001 (HEX ?) but does not corrispond to 26215... I'm really confused. I know how to assign a control under SIOC by using 0x3110, but I need to understand the exact value to use with it, and wich parameter (I suppose 0 and 1). A lot of things to try and understand...! I searched in the supplied manuals but no match was found for LVAR or HVAR, and I could find no other useful indication, maybe I'm missing some doc.

Ok thanks! Probably the CTDs increased after I installed the FBW, I suspect also Mobiflight increases the instability, I have more confidence in FSUIPC because I always have it running and normally very few CTD happen, but when I switch from normal PC/Joystick flight to my cockpit, I activate SIOC and Mobiflight and the OC modules plus 3 arduinos, and the simulator seems not to like this... but having no crash diagnostics is very difficult to understand what is causing the CTD. I've never seen a program so unstable and without any serious error handling, even if it is a super-wonderful flight simulator that I love nonetheless! Of course maybe the external hardware and software to cause the instability but I had a lot more complex cockpit HW/SW with Xplane and almost no CTD at all... In the weekend I hope to develop the new controls for EFIS and then the FCU (AP/CDU managed modes, the rest is all working)

Hi John, thanks a lot! Good stuff to study and experiment. I have a question, what is the meaning of the value I read after the lvar name in lvars list ? I can't figure out, but maybe it's useful to know. So, after defining the hvars presets in myevents.txt, using the proper control number I could assign to an hvar in SIOC the value needed to perform a function (es. switch LS on and off) by triggering the offset 0x3110 (I'll study how this works on advanced manual). BTW... even when things work perfectly I have a huge lot of CTD of MSFS... what a pity, I spend more time restarting the simulator and reprogramming the flight, etc, than flying and testing the new things I'm studying. Then, without an apparent reason, the sim works smoothly for hours!

First step worked fine. First of all, I enabled WASM addon from fsuipc menu (ALT-F if one wants to know) and then restarted flight. WASM was enabled and I could see a list of LVARS. Great, but only some lvars were displayed. To see the effect of any change it is necessary to hit again list lvars. The correct vars were [LvarOffsets] 1=A320_Neo_MFD_NAV_MODE=UB66C0 2=A320_Neo_MFD_Range=UB66C1 I corrected the second row in fsuipc.ini, then hit reload under wasm menu in fsuip and then both controls worked perfectly. The code in SIOC was Var 0282, name FS_MODO, Link FSUIPC_OUT, Offset $66C0, Length 1 // EFIS_MODE Var 0283, name PM_RANG, Link FSUIPC_OUT, Offset $66C1, Length 1 // PM_EFIS_RANG Then other lines assigned to FS_MODO and PM_RANG the values 0,1,2,3... according to knobs position. All wonderful! (FSUIPC IS a MASTERPIECE, no doubt about this). Now I would like to assign to EFIS buttons the PFD_LS and MFD TERRAIN function, and ARPT and WAYPOINTS. This seems to be more complicated for me because these controls are under HVARS, not LVARS. How I set them ? For the moment, I just don't know.

Hello, after a wide and pretty frustrating search on the net, forums, google searches and reading all supplied manuals and docs, I surrended and now I would like to start a topic (if already exists please someone tell me where to find it) about existing documentation, examples, tutorials or simple posts illustrating step by step procedure to add lvars for a specific plane and assign them to offsets so to control them via hardware (I am trying to convert my B737 MCP and EFIS into A320 functional FCU and EFIS. For the moment I would like to deal with Asobo A320 Neo, and only after that, trying to switch to the more complex FBW 320. At the moment I only understood that I have to insert something like this : [LvarOffsets] 1=A320_Neo_MFD_NAV_MODE=UB66C0 2=A320_Neo_MFD_NAV_Range=UB66C1 in fsuipc.ini, and then from SIOC I should be able to set the values of 66C0 and 66C1 with the usual code. Is that correct ? I think there is a whole world of things to know more than this... where can I find a basic guide ? Thanks a lot for any help!

Thanks, I saw that post, but I don't know how to create the pokeysdevice object without luacom. I could try to compile it in 64 bit environment, but I think I'd rather work on Arduino if it is less complicated that this solution. It was a really powerful and easy to use combination, it's a pity it was abandoned (at least seems abandoned).

No, I installed the most recent luacom.dll I could find, compiled in 2020 and compatible with lua 5.1, in the lua dir under FSUIPC7 dir. Then i set my lua code for the pokeys inside the ipcready lua. These are the first rows of my mip.lua code (that worked fine with fsx when I last used it) require "luacom" poKeys = luacom.CreateObject("poKeysDevice_DLL.poKeysDevice") if poKeys == nil then ipc.log("Error: poKeysDevice_DLL object creation failed.") ipc.display("NO POKEYS - QUIT PROGRAM") ipc.exit() end When I launch MSFS nothing happens, but when I look in the log file I find this : 149422 LUA.1: beginning "C:\FSTools\FSUIPC7\ipcReady.lua" 149422 LUA.1: C:\FSTools\FSUIPC7\ipcReady.lua:1 149438 LUA.1: Global: ipcPARAM = 0 149578 LUA.2: beginning "C:\FSTools\FSUIPC7\mip.lua" 149578 LUA.2: C:\FSTools\FSUIPC7\mip.lua:1 149594 LUA.2: Global: ipcPARAM = 0 149656 *** LUA Error: error loading module 'luacom' from file 'C:\FSTools\FSUIPC7\lua\luacom.dll': %1 non è un'applicazione di Win32 valida. I tested both the luacom supplied with the lua for windows precompiled package (and luacom.dll is dated may 2008...) and the most recent luacom.dll that I found on the net, but none of the two worked (if the error is caused by the specific version of luacom). Currently I am exploring many other territories, form MobiFlight to Python libraries that seem to work directly with simconnect and could be interfaced with arduino, but of course if I could make my Pokeys to work with LUA and FSUIPC I would feel much more "comfortably at home" let me say...!

Looking on the console, the parameter 1 is not received apparently; when I press the button, on the console the row with control 68065 shows a parameter = 0, nevertheless the autopilot knob works, but the Var 0442 should issue a value 1 to the control parameter... This function in SIOC/FSUIPC could be used for improving the old fsx drivers for MCP and even EFIS. My next test will be on the EFIS side, to see if sending controls work on the NAV display or the GPS. I'm also working on interaction between FSUIPC, MobiFlight and Arduino, but I miss my LUA interface with my Pokeys (currently still connected to all my overhead...) Is there any hope that LUACOM will be working again ?

Hello, I found a good solution with this option available in SIOC through a powerful function in FSUIPC : Var 0441 name FS_CONTROL Link FSUIPC_OUT Offset $3110 Length 4 Var 0442 name FS_PAR Link FSUIPC_OUT Offset $3114 Length 4 Var 0426, name I_HDGSEL, Link IOCARD_SW, Input 28 { IF &I_HDGSEL = 1 { &FS_PAR = 1 &FS_CONTROL = 68065 &FS_CONTROL = DELAY 0 10 So pressing the heading lock button I also send the command to commute HDG SLOT to 1, and that work. The first idea (sending an fsuipc virtual joystick button) is very interesting, but worked randomly, sometimes the button press was detected, many other times no. Probably something has to be fixed... Anyway FSUIPC is really a great tool, and the more you know it the more you discover how poweful it is!

Hi John and Pete, I found in sioc manual that sioc can simulate a button action on one of FSUIPC virtual joystick. This way I could use the button of the MCP AP MASTER to do also a simulated button press for the VJ : Var 1 Link IOCARD_SW Input 116 Type I { &FO_JoyStick64 = CHANGEBIT 0 v1 // toggle bit 0 of joystick 64 } Var 2 name FO_JoyStick64 Link FSUIPC_OUT Offset $3340 Length 4 SO I could assign this button the action of setting the hdg slot to 1. That should work in theory... and this opens a lot of possibilities also! I'll try and report the result.

Thanks a lot John!!!! THAT WORKS! The control was set to FMC, capturing the current heading value. Setting the slot to 1 the control is passed to MCP heading value as set with the HDG knob. This is very good, and the same thing can be applied to altitude and speed. Now the ideal thing would be to send this control automatically when I push the AP button, is there some way I could send this command from sioc, when I press the AP button ? or maybe I could write some LUA code ? What do you suggest John ? I understand that this could be a problem when using the FMC. I wonder why they do this passage to the FMC if no flight plan whatsoever was set... To answer to Spokes2112 (thank you first of all) I agree with you that somewhere in cfg somewhat should be this setting, but the aircraft.cfg seems to be locked (".fsarchive) if you can find some other path to reach the autopilot configuration, I can't find it... As I said I checked many files under instruments, I also found the 787 FCU.js and other, but all attempts to modify those files didn't work.

I have found this possibly interesting post on MSFS forums : "There are no commands that are visible in control settings GUI. But you can control the FCU authority with these Sim Connect sim events; HEADING_SLOT_INDEX_SET SPEED_SLOT_INDEX_SET ALTITUDE_SLOT_INDEX_SET VS_SLOT_INDEX_SET Sending these with parameter 2 gives the authority to FCU, and sending with parameter 1 activates selected mode for each knob. You’ll need to use a 3rd party controller interface software that use sim connect; ....." Maybe that these "SLOT_INDEX" variables or controls set to 1 allow normal operations for the knobs of MCP ? I cannot send them directly to simconnect... never even tried to do this directly, only used FSUIPC.