DaveSCUSA

Wow, thanks

Sorry to bother you again but I'm a bit confused how to set an Offset, especially one I define. In the Advanced Users, to use offsets with keypresses, it states: "This is normally an FS control number (as in my lists), or a special FSUIPC number for additional controls. It can be in decimal, or, preceded by ‘x’ in hexadecimal. The additional FSUIPC controls range from 1000 to 3000, and also values xcc00zzzz in hexadecimal which encode the FSUIPC “Offset” controls. See list below for full details." A bit confused by "also values xcc00zzzz in hexadecimal which encode the FSUIPC “Offset” controls". In the Adding Offset Conditions, the example used is "31=P174,10,Cx510066C0,x00030001". Not sure what "Cx5100" is. In using the Key Assignments UI (see attached graphic), I selected Offset Byte Set using offset x66C0 and a parameter of 4, expecting: 1=49,24,x010066C0,4 Instead, FSUIPC7.ini contains (Choosing Tab+2 to set a control): [Keys] 1=49,24,x01000000,x00 -{tab+1: Press=offset byte set, offset 0000 }- 2=50,24,67187,0 -{tab+2: Press=BATTERY1_SET }- As you suggested, I wanted to use this offset as a condition: 1=49,24,x010066C0,4 - [tab+0: Keypress Press=offset byte set, offset 66C0}- sets use ATC response 2=B66C0>0 50,24,K1 -{tab+1: Enter 1}- as a response to ATC 3=B66C0=0 50,24,C67090,0 -{tab+1, Press=TOGGLE_EXTERNAL_POWER}- 4=50,24,x010066C0,0 - [tab+0: Keypress Press=offset byte set, offset 66C0}- reset to no ATC . . . . . . . . . . On to 10 other buttons. I have confused myself reading in different sections of the documentation. Appendix 1 doesn't mention keypresses. Thanks

Thanks. Seems complicated to add key press but if they are all "called" routines, it may not be terrible. I'll try offsets.

I have read the User and Advanced Guides including Appendix 1. Can one treat key presses with compound programming as with buttons? E.g. in a 12 button keypad sending key press combination (settable) to Windows: 1=48,256,C1003,13 Keys RAlt+0 set Flag 13 (Button 1) 2=(F+0,13)49,256,K49 Keys RAlt+1 and Flag 13 is set, send 1 (Button 2 send 1 to ATC) 3=(F+0,13)49,256,C1004,13 Keys RAlt+1 and Flag 13 is set, reset Flag 13 (Button 2) 4=(F-0,13)49,256,Cxxxx,1 RAlt+1 If Flag 13 not set, set control to turn Ext Power On (Button 2) 5=(F-0,13)49,256,LELECT_EXT_INPUT1,4 RAlt+1 If Flag 13 not set, send 4 to aircraft input event turn on Ext Power If I knew how to turn this 12 Button keypad into a joystick, I would. Thanks

Thank you

Thanks to the new FSUIPC7 input event logging, I've discovered that the Citation Mustang C510 inputs a control event as well as an input event with most cockpit button/switch input. I have studied the compound button assignments. Am I right that a button or two can be dependent on a previous button press? Is there a way (haven't been able to find) to have a control and an input event exercised by a single button push without Lua? It seems that both aircraft I use (C510 & DA62) have a control and input event on the same switch. At your suggestion I used the UI to assign controls to the Alpha and Bravo.

Is the ability to add a parameter to an input event available in the UI Assignment for Buttons & Switches any time soon?

Thanks

I am continuing to receivethese in the Log: Found 57438 InputEvent found: 'LANDING_GEAR_Gear' with hash=16178909335228778991 [type=0] Continuously showing: 61750 InputEvent received: 'LANDING_GEAR_Gear', Value=1.000000 (param='') 61781 InputEvent received: 'LANDING_GEAR_Gear', Value=1.000000 (param='') 61813 InputEvent received: 'LANDING_GEAR_Gear', Value=1.000000 (param='') 61828 InputEvent received: 'LANDING_GEAR_Gear', Value=1.000000 (param='') 61860 InputEvent received: 'LANDING_GEAR_Gear', Value=1.000000 (param='') Entered in the [General] section of FSUIPC7.ini: DontLogThese=65700,66080,66172-66181,65962,66523,65568 DontLogTheseIE=LANDING_GEAR_Gear Should there be quotes around the input event?

The other reason I use Lua! Although I retired as an IT executive and business consultant, I find preogramming very relaxing and rewarding. Since retiring, I have completed projects in HTML/CSS, Python, VBA, FSX XML and now FSUIPC7 Lua. Next step, native Lua.

Thanks for your time. I look forward to the release this week.

Thanks for the extraordinary time you've spent on this. Please forget any reply on starting an Lua module with a button press. Just want to execute code to manipulate a Sim event. Again, all I need is: 1. Event.button or event.key executing a function in a module. 2. Run that module via the [Auto] section. 3. Have a LuaPath in the [LuaFiles] section if the Lua is located in that folder. That's it? No other actions needed? As an ex-pilot and retired programmer, I have options I want to use to make the use in the home built cockpit more realistic. I have the pilot manuals for several aircraft. I can more easily tie functions together that aren't correct in the MSFS aircraft. E.g. Upon start. Ensure the ignition is on. Fuel valve is open. Starter stops after reaching its minimum rpm.

Thanks

Really helpful. Thanks. What would the input event entry look like using DontLogTheseIE parameter? Its number or name as appears in the log list of input events found?

I'm sorry John, what is obvious to you is not always understood by your customers. You keep saying "assignment on your Alpha is starting the Alpha_Buttons.lua script" and "lua on a button press, as i have said many times now". where is the Lua started by a button/key press? Between the lines interpretation, does every button/key assignment in the [Button] and [Key] sections start the Lua module? What I am understanding is that the steps should be: 1. List the Luas in the [Auto] section or use the ipcready.lua module. 2. The event.button and event.key statements in the module will be executed whenever a button/key press is completed. 3. Don't need the entries in the [LuaFiles] section in FSUIPC7.ini except the LuaPath entry. 4. No [Buttons] or [Key] sections in the FSUIPC7.ini are needed except if one wants to start a module with a press. If the above is not correct or I still don't understand, please point me to documentation that provides the steps needed and what entries are needed where to execute a function on a button or key press.

Thank you for your time. I am still getting used to FSUIPC and its nuances. I'm still a bit confused about starting and the sequence of events in the Lua. In reading the documentation, it appears the series of actions needed to set up an execution of a plug-in (Lua module) with events are: 1. Assign a switch/button to an Lua module either by using a text editor on the FSUIPC7.ini file or using the Key/Buttons assignments facility. For Buttons - "5=PA,13,CL1:R,0 -{ALTERNATOR_ON}-" and for Keys - "0=54,136,L1:R,0 -{rctl+6: Press=Lua Alpha_Buttons }-". 2. In the Lua module, use event.Buttons or event.Key ("event.button(A,13, "TOGGLE_AVIONICS_MASTER") -- On" or "event.key(54,136,"ATC_RAlt_6")") to execute the function in the Lua module. 3. The .ini entries tie the button press/key press to the Lua module. 4. Add the Lua module name to the [Auto] section to load the Lua module ("1=Lua Alpha_Buttons" and "4=Lua Sayo-12Keys"). 5. Add the Lua module to the [LuaFiles] section ("1=Alpha_Buttons" and "4=Sayo-12Keys") also include "LuaPath=C:\FSUIPC7\LuaFiles" to use a folder to contain the .lua files. These entries provide the buttons/keys definitions with the Lua module where the function resides. 6. Start MSFS 2020 and start an aircraft to run and the the Lua modules will be available when an aircraft is in its flying state. Can I understand from your statement quoted above that an Lua entry in the [Auto] section and an event in an Lua module are mutually excleusive? You state "assigned EVERY button to start the lua script". Not sure what that means. Does every entry in the [Buttons] and [Keys] sections in the .ini start a Lua script? What are my steps to correct the situation if it is other than removing the Lua entries from the [Auto] section? What am I not understanding from the sequence of actions above that is causing errors. And I did miss the single "-" on the ipc.readSTR entry, old eyes. Thanks again.

I have two issues. 1. Kept getting Lua compile errors with the ipc.readSTR statement with the Alpha_Buttons.lua module - attached: -- Find A/C Title local acloaded = "None" acloaded = ipc.readSTR(0x0618,4) - Read ICAO Designator from acraft.cfg ipc.log("A/C - "..acloaded) So I commented the statements out (See the Lua module). 2. Now I have a clean compile but receive the errors: 140078 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed 144062 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed 145125 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed 189672 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed 191984 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed 195187 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed 197031 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed Each line item above appeared every time I exercized a switch on my Honeycomb Alpha. The killed message doen't appear on my test PC - same user and MSFS synced with my Sim PC. The test PC does not have eith the Honeycomb Alpha or Bravo attached. I hope you can help fighue this out. I tried to find the Lua error "killed" online, but no details. Thanks FSUIPC7.ini FSUIPC7.log Alpha_Buttons.log Alpha_Buttons.lua

Thank you. What I was asking was the syntax of using. ipc.execCalcCode. You answered that. Thanks for the input on Mobiflight. Since I don't use it, it is not on my radar. I'll give it an attempt. The reason many of us come to you is that you have more experience than anyone (except Asosbo developers) in SimConnect, Lua and Polish notation. For many of us, the documentation is inadequate and confusing. Looking to you for clarity.

The events below are logged when turning the Avionics Master Switch On/Off in the cockpit. I would like to attached this activity to the Avionics switch on the Honeycomb Alpha. The AVIONICS_MASTER_SET is not used in this aircraft. Apparently the aircraft logic connects and disconnects the RH_Main_BUS (#3) to the Avionics Bus (#4) as listed in the Systems.cfg. Avionics On 389375 *** EVENT: Cntrl= 67073 (0x00010601), Param1= 3 (0x00000003), Param2= 4 (0x00000004) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE Avionics Off 424703 *** EVENT: Cntrl= 67073 (0x00010601), Param1= 3 (0x00000003), Param2= 4 (0x00000004) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE According to the SDK, the event is coded (Polish Reverse) - (K:3:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE:4, Bool) The only way I can see to toggle this event is to execute: ipc.execCalcCode(“K:3:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE:4, Bool”) Is this correct or is there a better way? Is there an improvement to ipc.control(67073, param) to enter 2 indices?

I keep getting this error after a var has been filled: 106890 LUA: Global: DVar = Fuel_L_Bravo OFF 106906 LUA: C:\FSUIPC7\Test_Keys.lua:46 fn: UpdateWnd 106937 LUA: C:\FSUIPC7\Test_Keys.lua:47 fn: UpdateWnd 106953 LUA: C:\FSUIPC7\Test_Keys.lua:48 fn: UpdateWnd 106968 *** LUA Error: C:\FSUIPC7\Test_Keys.lua:48: attempt to concatenate global 'Dvar' (a nil value) Have been over examples, plug-ins. Can't seem to find where it is wrong (my eyes may be getting too old). function UpdateWnd() ipc.writeUD(0x66C2, 5) -- Set Bravo for Message if val == nil then mess = (" T - "..Dvar) ipc.writeSTR(0x3380,mess) else message = (" T - "..Dvar.." Value = "..val) ipc.writeSTR(0x3380,mess) val = nil end end PS - This is a test lua to double check using the events in the aircraft Test_Keys.log Test_Keys.lua

It appears the thread that one can place a potential Beta problem has been closed. 270968 InputEvent received: 'PRESET_FADEC', Value=0.000000 (param='') Once an aircraft (DA62 Improvement Mod) has been put in the flystate, the above inputevent appears as if in a loop. Had to shut input event logging off. Is there a way to indicate that we don't want to log "InputEvent found:" at this time? Sure would save a lot of log. Thanks FSUIPC7.ini FSUIPC7.log

Sorry, the .ZIP file is still too large to upload. Even the image file of the zip results are too large. I have pared down the files and did attach them above.

Thanks for your development and attention. I tried FSUIPC7 "********* FSUIPC7, Version 7.3.26f (23rd November 2023) by John Dowson *********" I had a slight problem as there were several unrecognized input events as if in a loop. I have attached the log. I also extracted the "InputEvent received but not known:" input events, sorted by name, marked the duplicates and resorted by FSUIPC7 time. They are listed in the file FSUIPC7.sorted.txt. I'm not sure what to make of this? This the DA62 Improvement Mod. Just got a message "too large". I'll have to cut them back. The log ended at line # 47,930. 2FSUIPC7.log 2-FSUIPC7.sorted.txt

Thank you again. It is difficult using ipc.execCalcCode(“code”) when you don't know the indices used. I look forward to using the Beta version today. Is there a significance of the parameter in the event log with a toggle? apparently it shows correctly with the SET controls. The ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE seems to show multiple numbers in the param.

I have been exploring the events with the DA62 aircraft. Several of the events are toggle type events (controls). I was to understand that that toggle events have no parameters. However there are parameters displayed. One or two questions. 1. In the Event Log Entry - one of the kex values is the parameter. What is the other hex value? 2. If a toggle event has no parameter, do you know why one is shown in the entries? 3. If there are 2 indices in an event, is the param one of the indices and can Lua show both indices? Engine Master Left On 1862188 *** EVENT: Cntrl= 67063 (0x000105f7), Param= 0 (0x00000000) ENGINE_MASTER_1_TOGGLE 1862204 *** EVENT: Cntrl= 67073 (0x00010601), Param= 9 (0x00000009) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE 1862204 *** EVENT: Cntrl= 67073 (0x00010601), Param= 5 (0x00000005) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE 1862204 *** EVENT: Cntrl= 67073 (0x00010601), Param= 7 (0x00000007) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE 1862204 *** EVENT: Cntrl= 66241 (0x000102c1), Param= 2 (0x00000002) TOGGLE_MASTER_BATTERY 1862204 *** EVENT: Cntrl= 67073 (0x00010601), Param= 6 (0x00000006) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE [0]: Source bus index [1]: bus index Toggle bus connection state with a bus. Takes two indices, the initial bus and the second bus (see SimVars And Keys for more information). The bus index is the N index of the bus.N definition in both cases.