Detlef_747

John, OK, that explains it, thank you. I found a solution I can work with (basically interpreting any strings in a Lua FSUIPC script directly, and using only "number" Lvars in Airmanager outside FSUIPC). Detlef

I do that, because I don't know PMDG variables I can directly use for some instruments of the B737. For almost all instruments I see the Lvar directly in the XML behaviour file provided with the aircraft. But for some not. And here I do use your offsets from the file Offset Mapping for PMDG 737-700.pdf. That has helped me a lot. The "SDK" which just seems to be a PMDG_NG3_SDK.h file is of no help for me right now. Detlef

John, thank you for your explanations. They are helpful for me. I think I have to stay with my solution. I don't want to write data to offsets, just read them and write the contents into Lvars. I use Siminnovations Airmanager to create instruments on a touchscreen. That software cannot access offsets in FSUIPC. Rather it waits for changes on MSFS simulator variables such as Lvars and then uses the information from the Lvar to control the instruments on the touchscreen. For example: Offset 64C9 13 char[13] ELEC_MeterDisplayBottom[13] has the information for the bottom line of this instrument: I generate the output you see here from the Lvars I read from FSUIPC via the interface provided from Sim Innovations. However, it only seems to work with numerical type Lvars. I was not able to see contents from String Lvars generated in FSUIPC, even though I tried to read them as strings. I can live with that now because FSUIPC allows me to generate multiple Lvars (type float) so that I spread the information from the offset on three separate Lvars. I am not sure I made myself more understandable. I just wanted to understand if and how string Lvars work. If I read the Lvar L:ipcpmdg_DC_Voltmeter generated with stringTest.lua inside the Siminnovations Airmanager, I get the numerical representation for example 9.0251229459308e-308 if I read it as number, and I get "" (an empty string) if I read it as string. That seems to be not an FSUIPC problem but someting in the Siminnovations interface. I currently experiment some more, just had a complete CTD of MSFS and it won't restart now. I need to restart my computer now... Detlef

Ok. Thank you for clarifying. Detlef

Hi again, I know what alignment on words, dword and so on is. But I do not understand, how I should add data to offsets. The PMDG offsets do work as you provide them in the file Offset Mapping for PMDG 737-700.pdf. Thank you again, Detlef

John, thank you for your fast reply. Ok, 8 characters max. That means the 13 character offsets for example 64BC 13 char[13] ELEC_MeterDisplayTop[13] from the PMDG offset won't work as one piece at leasts. As I said, I found a way arround it. Interpreting the string in the FSUIPC .lua script and write to separate Lvars. Thank you for providing the example script. I understand how the script should work but it does not assign a value other than 0 (approx 1.3e-307) to the Lvar. Or I am doing something wrong (which is often..). The counter value is not assigned to the Lvar. This is from the log file: 79860 LUA.3: Lvar updated: 1.1232813414918e-307, type=number 279875 LUA.3: Lvar value: myvar14 279938 LUA.3: Offset updated: myvar14 280907 LUA.3: Lvar updated: 1.1789081879545e-307, type=number

Hello, we have been in contact on Lvars some time ago. I have worked with the PMDG offsets more recently. I find, that I can generate Lvars that represent a float number just fine. But string Lvars don't work. So I did a work arround in the lua script attached. For example event.offset(0x64bc, "STR", 13, "ChangeMeterTopLine") calls the function ChangeMeterTopLine just fine. But I cannot write the string into an Lvar at once, so I interpret the string in the FSUIPC lua script and write to a couple of numerical (float) Lvars instead. Did I miss something with string Lvars? I only found ipc.createLvar(). Are there other functions I could use? Thank you Detlef PmdgOk.lua

John, I have had the registered version of FSUIPC(7 now) for so long, that I don't know what the non-pay version can do. I ask, because I want to provide a lua script to others. Do they have to buy FSUIPC7 in order to be able to start lua scripts automatically? Thank you Detlef

Installing the latest version sometimes does miricles.. I updated the aircraft to the latest PMDG 737 version, and the offsets mentioned above do work now! The lvars creation also works. I will leave the ipc.sleep calls inserted until the next FSUIPC7 version. I will try with a list of offsets, which will sum up the wating time, but that really is not a problem right now. Thanks again for your help. I very much appreciate it. The issue is solved. Detlef

John, thank you for the ongoing support. Sorry I deactivated the Lua logging at some point. I have it on again now. Both is on now. I also activated the option to see offset 65EA in the windows title. It always says 0. I have activated event logging also. Usually I would send event 32503 to operate the nose wheel steering switch. If I look at the log file, that event is present, but still offset 65EA is not changing in my environment here. Thank you for sending your log file. Yes, I see it is working in your setup. Something must be wrong or different in my setup. I have not yet tried with a modified lua script. But that seems not to be the main issue. Thank you Detlef FSUIPC7.log FSUIPC7.ini

Unfortunately I am also reading 0 all the time from those two offsets you mentioned. And I operated "arm spoiler" and the nose wheel steering switch. ipc.readUB(0x65ea) ipc.readUB(0x65fd) I did that. The log file says: 267687 PMDG 737 Client Data Received: ID=1313289013, Size=1049, FirstDataDW=536870944 (FSUIPC7 logfile attached) It says that just once, not repetatively. I may still be missing something. Thank you Detlef FSUIPC7.log pmdg737.lua

Hi John, I experimented some more this morning. With the Cirrus aircraft (FS2020 default) everything works as expected. I can read from offset 0x0bfc (flaps index) and write that value into an Lvar that I create myself (L:my_flaps_index). I can see and work with that Lvar in Air Manager (which is my goal). The Lvar also shows up in the Lvar list, if I generate one with the FSUIPC menu call. I have attached the resulting files here. However, if I try with PMDG offsets, I always see 0 as value. (Maybe some do work, that I did not try.) Can I somehow verify that the PMDG 737 is broadcasting its data? (I have the SDK section in the 737options.ini file but maybe something else is missing in my settings). Thank you Detlef pmdg737.lua FSUIPC7.ini FSUIPC7.log pmdg737.log

I just did. The Lua program stops running then I think. I am not sure I should restart everything. I will try more tomorrow. And I will try again with offsets for a default aircraft. Thank you Detlef pmdg737.log pmdg737.lua

Sorry, this is the script pmdg737.lua

John, thank you for your fast reply. I am sorry if I sound confusing. My intention is to read contents from offsets and write that contents into Lvars that I create myself using Lua script in FSUIPC. I did that here. See the attachment. I modified my lua script to be as simple as possible and inserted a 5 second pause before trying to write to the Lvar. My problem here: I always read 0 as value. I actually see the Lvars I created in my Airmanager instrument with their initial values 1234.0 and 4321.0 respectively. But after 5 s the display switches to 0. I have attached the files here. So I seem to never get any data from the offsets. I am sorry if I was confusing here. I did not try both at the same time. So when trying the .ini section I did not use a Lua script to generate Lvars. So in the files attached I had the PMDG 737-700 running, with engines off, APU on. I tried these specific offsets because I know how I can use PMDGs original Lvars for that. So I know they should work (0x64bb and 0x64E8). Thank you Detlef pmdg737.log FSUIPC7.ini FSUIPC7.log