Carliolian

Andrew Got the ground connections working. Use Lvar "7X7X_Ground_Power_Light_NotInUse" not "7X7X_Ground_Power_Light_Connected" -- $$ Grund Power Unit function PMDG_CDU2_GroundPower_on () PMDG_CDU2_GroundConn () ipc.sleep(10) NGXchocks = ipc.readLvar("NGXWheelChocks") NGXGPU = ipc.readLvar("7X7X_Ground_Power_Light_NotInUse") ipc.sleep(100) if NGXchocks == 0 and NGXGPU == 0 then DspShow ("not", "able") ipc.sleep(1000) DspShow ("set", "chks") elseif NGXchocks == 1 and NGXGPU == 0 then PMDG_PED_CDU2_LSK_2L () else DspShow ("GPU", "on") end end function PMDG_CDU2_GroundPower_off () PMDG_CDU2_GroundConn () ipc.sleep(10) NGXchocks = ipc.readLvar("NGXWheelChocks") NGXGPU = ipc.readLvar("7X7X_Ground_Power_Light_NotInUse") ipc.sleep(100) if NGXchocks == 0 and NGXGPU == 0 then DspShow ("not", "able") ipc.sleep(1000) DspShow ("set", "chks") elseif NGXchocks == 1 and NGXGPU == 1 then PMDG_PED_CDU2_LSK_2L () else DspShow ("GPU", "off") end end function PMDG_CDU2_GroundPower_toggle () if _tl("7X7X_Ground_Power_Light_NotInUse", 0) then PMDG_CDU2_GroundPower_on () else PMDG_CDU2_GroundPower_off () end end Frank

Andrew this: function PMDG_CDU1_GroundPower_toggle () if _tl("7X7X_Ground_Power_Light_Connected", 0) then PMDG_GroundPower_on () <<<<---------------- should be PMDG_CDU1_GroundPower_on else PMDG_GroundPower_off () <<<<---------------- should be PMDG_CDU1_GroundPower_off end end But it still does not woek for me Frank

will do soon

Hi Andrew I think that I have the same problem I don’t see the installed aircraft any more. All my current aircraft work ok. I have MSFS installed on my F: drive. When MSFS installed it asks you twice where to install. There is a thin file/directory select at the bottom. The first part is the flight sim location +/- 10 GB. The second is the location for all the scenery and content. Most people don’t see it. Once I missed it myself, had to download 60+ GB twice. During Beta testing I saw this link “how to move MSFS” https://forums.flightsimulator.com/t/how-to-change-the-installation-path-of-installed-packages-inc-community-folder/471682 Having you sim on a custom location has many advantages. Frank

Good news, the P3D actions for the DC 6 also work in MSFS. I haven't tested everything, just the ones I need so far.

If after SU 5 "Linda ready" etc messages are not showing. There is a new option in "Assistance settings" - "Software tips" needs to be on.

A32NX_OVHD_ELEC_BAT_2_PB_IS_AUTO is for the FBW A320 neo It can be watched in Developermode -> Windows -> model behavour debug -> LoCAL VARIABLES. If you are not using FBW A320 then it will not be there. SO the "if" statements will return a nil. Frank

Hi ???? I think you probably don't have the WASM installed. Download and install the latest FSUIPC Version 7.2 from https://forum.simflight.com/topic/92507-fsuipc7-v720-beta-release-new-facility-to-add-lvars-to-offsets-for-both-read-and-writeupdate/ Frank

Hi Joe I have been working on some functions. I had some problems and I think I found the answer. ipc.readLvar was not working sometimes when "L:" was included the with variable. I have changed the Battery functions A32NX_OVHD_ELEC_BAT_1_PB_IS_AUTO not A32NX_OVHD_ELEC_BAT_10_PB_IS_AUTO and they now work. Also I have added APU start/stop using Lvars. I am working on increase /decrease display brightness but not having much luck. Uses control 67227 with parameters 84 .. 94 can be seen the the console, each parameter is a different display but there is no way to apply a direction? Frank. function A32nx_Bat1_SET(bat1Status) ipc.writeLvar("A32NX_OVHD_ELEC_BAT_1_PB_IS_AUTO", bat1Status) end function A32nx_Bat1_ON() DspShow ("Bat1", "On") bat1Status = 1 A32nx_Bat1_SET(bat1Status) end function A32nx_Bat1_OFF() DspShow ("Bat1", "Off") bat1Status = 0 A32nx_Bat1_SET(bat1Status) end function A32nx_Bat1_TOGGLE() bat1Status = ipc.readLvar("A32NX_OVHD_ELEC_BAT_1_PB_IS_AUTO") if bat1Status >= 1 then bat1Status = 0 else bat1Status = 1 end A32nx_Bat1_SET(bat1Status) end function A32nx_Bat2_SET(bat2Status) ipc.writeLvar("L:A32NX_OVHD_ELEC_BAT_2_PB_IS_AUTO", bat2Status) end function A32nx_Bat2_ON() bat2Status = 1 A32nx_Bat2_SET(bat2Status) end function A32nx_Bat2_OFF() bat2Status = 0 A32nx_Bat2_SET(bat2Status) end function A32nx_Bat2_TOGGLE() bat2Status = ipc.readLvar("A32NX_OVHD_ELEC_BAT_2_PB_IS_AUTO") if bat2Status >= 1 then bat2Status = 0 else bat2Status = 1 end A32nx_Bat2_SET(bat2Status) end function A32nx_OHD_BTN_APU_ON() ipc.writeLvar("A32NX_OVHD_APU_MASTER_SW_PB_IS_ON", 1) end function A32nx_OHD_BTN_APU_OFF() ipc.writeLvar("A32NX_OVHD_APU_MASTER_SW_PB_IS_ON", 0) end function A32nx_OHD_BTN_APU_START() ipc.writeLvar("A32NX_OVHD_APU_START_PB_IS_ON", 1) end function A32nx_OHD_BTN_ENG1_ANTI_ICE_ON() ipc.writeLvar("XMLVAR_Momentary_PUSH_OVHD_ANTIICE_ENG1_Pressed", 1) end function A32nx_OHD_BTN_ENG1_ANTI_ICE_OFF() ipc.writeLvar("XMLVAR_Momentary_PUSH_OVHD_ANTIICE_ENG1_Pressed", 0) end function A32nx_OHD_BTN_ENG2_ANTI_ICE_ON() ipc.writeLvar("XMLVAR_Momentary_PUSH_OVHD_ANTIICE_ENG2_Pressed", 1) end function A32nx_OHD_BTN_ENG2_ANTI_ICE_OFF() ipc.writeLvar("XMLVAR_Momentary_PUSH_OVHD_ANTIICE_ENG2_Pressed", 0) end function A32nx_OHD_BTN_WING_ANTI_ICE_ON() ipc.writeLvar("XMLVAR_Momentary_PUSH_OVHD_ANTIICE_WING_Pressed", 1) end function A32nx_OHD_BTN_WING_ANTI_ICE_OFF() ipc.writeLvar("XMLVAR_Momentary_PUSH_OVHD_ANTIICE_WING_Pressed", 0) end function A32nx_OHD_ALL_ANTI_ICE_OFF() A32nx_OHD_BTN_ENG1_ANTI_ICE_OFF() ipc.sleep(10) A32nx_OHD_BTN_ENG2_ANTI_ICE_OFF() ipc.sleep(100) A32nx_OHD_BTN_WING_ANTI_ICE_OFF() end function A32nx_OHD_ALL_ANTI_ICE_ON() A32nx_OHD_BTN_ENG1_ANTI_ICE_ON() ipc.sleep(100) A32nx_OHD_BTN_ENG2_ANTI_ICE_ON() ipc.sleep(100) A32nx_OHD_BTN_WING_ANTI_ICE_ON() end function DCDU_L_Brightness10 () ipc.writeLvar("A32NX_PANEL_DCDU_L_BRIGHTNESS", 10) end function DCDU_L_Brightness5 () ipc.writeLvar("A32NX_PANEL_DCDU_L_BRIGHTNESS", 0.5) end function MCDU_L_Brightness1 () -- default= 0.4 to 1 ipc.writeLvar("A32NX_MCDU_L_BRIGHTNESS", 1) end function MCDU_L_Brightness5 () ipc.writeLvar("A32NX_MCDU_L_BRIGHTNESS", 0.4) end

Yes I have got the latest versions. I have been following this for some time, waiting for a breakthrough. At the moment I think it might be something to do with access rights . I will do more testing today. I see all the hvars in "list lvars".

Dear Joe I have been trying to get Lvar/Hvar working this last week. Thanks for your work so far, if I get any more working I will let you know. BUT I still do not have the H:vars working. I just read this in the FSUIPC forum. https://forum.simflight.com/topic/92032-fsuipc-wasm-module-client-side-api-lvarhvar-discussion-topic/?do=findComment&comment=560594 you need to have the Hvars listed in the community \FSUIPC WASM folder. Can I have a copy of yours please. I am working on it this afternoon. Frank

Good Morning Scott Thanks for all your good work over the last few years and especially now with MSFS. Today I got the new FSUIPC7 and was hoping that we will soon be able to create profiles in Linda for MSFS. The default settings are good, so far, but I think that profiles for different aircraft should be the highest priority at the moment. look forward to your reply Frank

Thanks Andrew I will investigate further. FS Labs A320 update released 50 minutes ago😊 Frank Darbyshire

Hi everyone Nothing about P3D V4.4 so far so I will start. So far I have not had any problems everything seems to go quicker, loading, response etc and that's my problem now. I have just been flying the MJC Dash 8-400 when I adjust the heading or altitude on the VRinsight MCP the values jump by 1000' i.e. in fast mode unless you turn the knob slowly. I will b flying again this afternoon and will try other planes. Any ideas how to slow things down. Frank Darbyshire

Try UK Virtual https://flyuk.aero/en/index.php?page=home

I had the same problem yesterday. Took me 2 hours to fix it . Everything was ok on Friday But yesterday none of the presets worked. Could see Chase plane reacting but nothing worked. After un/reinstalling other apps and CP I noticed that the beta 04 was being installed reinstalled but only the stable version then it worked. Still have to check today though.

Hi all Linda fans I have recently received another Saitek FIP , my 4th ( birthday present). But now my question is : is there any way to select which instruments should be shown by using LUA/Linda. I fly different aircraft from light GA to heavy metal Jets, but whenever I change aircraft I have to re-select which FIPs I want. One cumbersome method is to have several different SaiFlightFip.xml files. This file defines which instruments should be shown in each FIP when FSX/P3D starts. SaiFlightFip.xml is only updated when FSX/P3D exits so that the same instruments will be shown next startup. SaiFlightFip.xml contains <FipList> <Fip Serial="MZ82D39BCB" Name="My Alt Sp VS"/><Fip Serial="MZB1E67FBA" Name="PFD version 3"/><Fip Serial="MZEF0EAEF0" Name="Altimeter"/><Fip Serial="SZ00031217" Name="Airspeed Indicator"/></FipList> If I remember beforehand I put the correct file in the Saitek folder before I start P3D. If not then I put the file in the Saitek folder after P3D has started Then I run this batch file ( as administrator) "Restart Satek.bat" taskkill /F /IM SaiFlightSimX.exe Net stop "SaiDOutput" Net start "SaiDOutput" start "fred" /B "C:\Program Files (x86)\Saitek\ProFlight FSX Plugin\SaiFlightSimX.exe" ( this batch file is also great when testing/designing new custom instruments) Which then shows the instruments I want. But the instruments are not active and so I have to reset the aircraft (control ;) What would be really useful would to be able select the instrument configuration in LUA/ Linda when Linda has detected which aircraft is being used. Has anyone any ideas? Linda is Great Frank

Hi Scot Don't bother trying to find out about SIOC All SIOC does here is set a bit in the virtual joystick buttons of FSUIPC between address 3340 and 3363. Which appear in FSUIPC exactly as any other 'real' button, and can be programmed from there in FSUIPC. Which I did for a while. I added events to be able to catch these buttons event.button(64,0,3,"handleButtons") This will eventually be handled by a function in user.lua which calls functions from actions.lua e.g. Function VButton_5 (downUp) if downUp ==1 777_ENGINE_L_START_start () end end --which works fine. If you mean "what would I like to see in Linda for virtual buttons". Then : 1. To be able to enable/disable virtual joysticks 1..9 probably in the settings screen. 2. In the joysticks screen to see and assign "On Press" & "On Release". This would mean detecting the events and assigning functions which could be stored in config-hid.lua. Hope this was what you wanted. Thanks Carliolian

Hello All For some time now I have been using LINDA with my Saitek switch panel, Yoke & VRInsite MCP . Great tool, thank you Guenseli. But eventually I thought that it was time to add more buttons and switches. I decided to buy an Open Cockpits i/p, o/p board and build it myself, having had some experience with electronics and software, no problems except that I soldered all the diodes the wrong way round. Everything working ok, programmed most of the switches and lights with SIOC to operate via FSUIPC. But,as I a fly several different types of aircraft and it's not easy to detect in SIOC the aircraft currently in use. So, I used LINDA to write a bit to a user byte in FSUIC which I could then detect in SIOC. Each user.lua sets a different bit (Boeing, Airbus, default, ..etc). That was a bit better. But programming in SIOC is so... time consuming I though there has to be a better way. So more study and research. I thought to write LUA code to be run by FSUIPC. I looked at writing my own app and running it in LUA/FSUIPC but then I thought much of the code is already available in LINDA actions.lua but I don't want to touch that. After much trial and error and searching I found the lib-user.lua Just what I need. I don't need to write my own routines everything is available from here. So what now happens. All that SIOC does is operate one of the virtual joystick buttons in FSUIPC , e.g. # SIOC code Var 0994, name JoyStick1, Link FSUIPC_OUT, Offset $3340, Length 4 // Joystick address Var 0169, name SetJoyBtn, Link SUBRUTINE { IF &BtnSet = 1 { &JoyStick1 = SETBIT &BtnNumber } ELSE { &JoyStick1 = CLEARBIT &BtnNumber } } -- one variable for each button Var 0170, name PBtn1, Link IOCARD_SW, Device 3, Input 8, Type I { &BtnSet = &PBtn1 &BtnNumber = 1 CALL &SetJoyBtn } Var 0171, name PBtn2, Link IOCARD_SW, Device 3, Input 6, Type I { &BtnSet = &PBtn2 &BtnNumber = 2 CALL &SetJoyBtn } Var 0172, name PBtn3, Link IOCARD_SW, Device 3, Input 7, Type I { &BtnSet = &PBtn3 &BtnNumber = 3 CALL &SetJoyBtn } These button events are caught by LINDA in lib-user.lua # LINDA lib-user.lua code function handleButtons(joynum, button, downup) -- call handler VButton_handler (joynum, button, downup) -- this fuction is in the user.lua of each airplane -- or you can handle each event separtely (globaly) here. if button == 0 then end if button == 1 then end if button == 2 then end if button == 3 then end if button == 4 then end -- etc end -- function -- events for virtual joystick buttons event.button(64,0,3,"handleButtons") event.button(64,1,3,"handleButtons") event.button(64,2,3,"handleButtons") event.button(64,3,3,"handleButtons") event.button(64,4,3,"handleButtons") event.button(64,5,3,"handleButtons") -- etc and sent to the button handler which is in LINDA user.lua # LINDA user.lua function VButton_handler (joyNo,btnNo,downUp) -- switch case would be nice here -- only joy stick 64 -- FSUIPC is from 0 .. 31, Linda 1.. 32 if btnNo == 0 then VButton_1 (downUp) elseif btnNo == 1 then VButton_2 (downUp) elseif btnNo == 2 then VButton_3 (downUp) elseif btnNo == 3 then VButton_4 (downUp) elseif btnNo == 4 then VButton_5 (downUp) elseif btnNo == 5 then VButton_6 (downUp) end -- etc end -- end VButton_handler This means that each aircraft in LINDA has its own set of actions for the aircraft currently in use and has full access to all the LINDA code. BINGO!!! Also all the user.lua code can be edited in LINDA editor. lib-user.lua should not need to be changed except for generic actions. I put the default settings in the templates/users/user.lua for any new aircraft. At the moment all my encoders are working ok, but I think I might try write something to be able to control them better in lua. What would be 'icing on the cake', if it was possible to assign functions to the virtual joystick buttons from the LINDA interface, but I realize that that is not quite as simple as I first thought. :wub: My thanks to Guenseli and Peter Dowson for there dedication and great support. Hope that this will be of use to others A very happy Carliolian