ariz Posted November 4, 2017 Report Share Posted November 4, 2017 Hi everyone I'm sorry if this questions has been asked before. I have looked around for similar problems, but I can't seems to find any fix for mine My problem is simple, I'm trying to read the CMD A annunciator of PMDG 737 NGX on P3D v4. From my understanding, I would need to read offset 0x6545 to do this, so here's my simple lua script that i made to do so arduino = com.open("COM3", 9600, 0) while 1 do cmd_a = ipc.readUB(0x6545) ipc.display(cmd_a) end The problem is, I can't seem to get any value (the value in ipc display is always 0, regardless if the button (CMD A) is lit up or not). Would be great if someone could point out the mistakes/ misunderstandings I've made here What I've done: I have added the line to enable data broadcast for PMDG in '737NGX_Options.ini' file I know that the LUA file is running as the ipc display is displaying number on top of the screen Background Information: I'm running on P3D v4, using latest version of FSUIPC (5.121b). I'm trying to build the MCP eventually. In doing so, I'm using and arduino card, and uses serial communication. Any help would be greatly appreciated. If further clarification is needed, please ask me. Cheers! Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 6, 2017 Report Share Posted November 6, 2017 Is FSUIPC getting the 737NGX data? Check something more obvious, such as the Flight Number string at offset 6614. Read that via ipc.readSTR. If that and other data is ok, then the Annunciator indications problem becomes a question for PMDG. There are parameters in the FSUIPC5.INI file to enable/disable the various PMDG offset reading. Check that this is not set to disable them. They should be enabled by default -- either PMDG737offsets=Auto or PMDG737offsets=Yes Pete Link to comment Share on other sites More sharing options...
ariz Posted November 13, 2017 Author Report Share Posted November 13, 2017 Hi Pete, thanks for the reply. It seems that my P3D install is somehow messed up. I have reinstalled it and I can read any offset now just fine. Thanks for the help! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now