Dominik

Thanks for the explanation, but I must be doing something wrong. Fsuipc returns Monitor IPC:7C90 (S32) = 0x1 - which is ok because the value is 1 However the next offset in the log is Input Event written to offset 0x7C50 not found: ':' trying to send 'I:FCC_ALT_HLD'

The first offset 0x7C50 corresponds to a value of e.g. "1" and the second 0x7C90 is a name e.g. "L:FCC_ALT_HLD" Dominik

Hi, I am using Fsuipc 7.5.0b for MFSM2024. After clicking on LOG>LIST INPUT EVENTS, a list of Input Events is displayed. Is there an option to set the ID numbers of these events? I want to use these ID numbers to manage with Offsets 3114 and 3110. Best regards Dominik

Thank you for your quick reply.

Is it possible to write data directly to the offset in pmdg or do I have to do it through events like this WriteFSUIPC($3110, 4, value); WriteFSUIPC($3114, 4, 70008); I am trying to directly send the state of e.g. a fuel pump switch and it doesn't work for me as if the offset was read-only.

It would be great if you would look into this in detail, maybe you will find a solution. Dominik

First of all, thank you for taking such a close look at my case. The script could definitely be written better. I wrote the LUA script for a ready-made program for handling MCP etc. which works on Xplane. In Xplane I have communication via writing and reading to a file. It's a pity that reading lvar took longer but I understand that you had to make such changes. For now I will work on version 7.4.11 until I modify the program for MCP to work with fsuipc offsets. I checked version 7.4.12 in which LUA works as slowly as in version 7.4.13 Dominik

Hello, I changed the parameter for LvarUpdateCeequency to VisualFrame in the wasm ini file but unfortunately no improvement. Attached are two log files with the Log -> Lua Plugins option enabled. When creating these logs the delay on the displays is still greater in version 7_4_13 Dominik FSUIPC7_4_13.log FSUIPC7_4_11.log

I am sending the files you requested in the attachment. The PMDG737Zapis.lua file saves data to a file that another program reads and sends this data to the MCP, Overhead and radio Panel. The PMDG737.lua file supports switches. B737 PMDG aircraft. I hope this will help solve the problem. Dominik. FSrecord7_4_13.csv FSrecord_7_4_11.csv PMDG737Zapis.lua PMDG737.lua

I start MFSM2020 then manually start fsuipc v7.4.11 everything works great. I close fsuipc and start v7.4.13 refreshing values on MCP becomes slow. I start v 7.4.11 again and everything works great. I don't change anything in lua code or other settings. If it's not fsuipc's fault then it's very strange. But if you say so then it has to be so.

Hello, I have a home-made MCP that communicates with fsuipc using a LUA script, data from MFSM 2020 is saved to a file. Another program reads this data and sends it to MCP displays, e.g. Altitude, etc. After installing the latest version of fsuipc 7.4.13, LUA slowed down terribly, data is sent to displays with a long delay (about 2 seconds). In the previous version of fsuipc 7.4.11, the problem did not occur and data on MCP displays refreshed immediately. Has the LUA refresh rate been reduced? - If something like that is. Dominik

OK. thank you for help,

In the LUA code, I added print (CDU_data) to display this data in the console. CDU_Data is displayed as a string that is constantly changing. Do you need to format this data somehow after reading? In the attachment I am sending the log file. FSUIPC7_prev.log

It uses LUA to read the offsets and write this data as text to a txt file. The second program reads this data from the txt file and sends it to the Arduino. My point is to use LUA to read the text lines on the CDU and save them as text in a txt file. Then the second program will read this data from the txt file and send it to the Arduino.

using LUA I can read PMDG offsets but I have a problem with CDU Screen Data offset 0x5400-0x57FF. Can anyone help me how to read these offsets correctly using LUA script. Thanks for any help. Dominik.

Thanks for your help, I set LvarScanDelay = 25 in FSUIPC_WASM.ini and actually fsuipc loaded more LVARs for me. Previously it was loading around 1700 now it's 1912. Everything works ok. I found the file FSUIPC_WAMS.ini in Community \ fsuipc-lvar-module only. There is no such file in the location mentioned in the Advanced User guide. Should I copy the teen ini file from the community folder?

After updating to SU10 it seems to me that fsuipc does not load all PMDG LVARs. Lua reports the bug that there is no such LVAR. It always helped to call from Add-ond >> WASM >> Reload and then everything was ok. I tested on versions 7.3.7 and 7.3.9dFSUIPC7.log Regards Dominik FSUIPC7.ini

Thank you for your help!

I have a homemade panel. I want lua to read if a given switch is on or off. I don't mean the switch settings in MSFS, but the switches on my panel that I can set in fsuipc.

With LUA I can write an event e.g. event.button (2,4,1, "EFIS320") and it works ok. But how do you check with LUA what position this button is in? Whether it is on or off, what is the position 0,1 or 2 Regards Dominik.

I think I found a solution to the problem, I have to use string.format("%04X", value)

Hello, I'm trying to read the offset 0x034E - COM1 frequency, using lua, Here is the code while 1 do file = io.open("test.txt", "w") ppp = ipc.readUW(0x034E) file:write(ppp, "\n") file:close() ipc.sleep(50) end The loop writes the value of this offset to the file. The value of this offset is 6194, com1 frequency is set to 118.050 It reads this value wrong and I don't know where I went wrong. Please help. Dominik.

Despite it all, you would add these offsets to the next version of fsuipc.

Autopilot offsets are working properly. You can write and read the values 1 and 2. Unfortunately the autopilot itself does not work properly, it seems to me that these offsets are responsible for the "dots" on the autopilot display and something else. If the plane climbs to the set altitude and we lower the autopilot altitude and write AUTOPILOT ALTITUDE SLOT INDEX value 2, the plane will not start descending. But if you press the cockpit switch that write the value 2 for AUTOPILOT ALTITUDE SLOT INDEX, the plane begins to descend. The button in the cockpit has to execute some other event. 0x029D 1 Byte APU SWITCH - works value 0,1 I have no idea, now I'm trying to start the autopilot via VB Dominik.

0290 - works well, result 1 or 2 0294 - works but you need / 65536 to get a result 1 or 2 0298 - works after pressing the button APU Start - result 1, APU off - result 0 It would be great if you could write these offsets, not only read. How would you find the SPEED_SLOT_INDEX_SET offset, it would be great x2 Dominik.