These are the Support Forums for FSUIPC and related products.

These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.

Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.

Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE

Notifications

Clear all

PMDG event ID not working with SIOC script

Page 1 / 2 Next

Posts: 4

Fake Pilot

Registered

Topic starter

July 18, 2026 5:26 pm

(@fake-pilot)

Joined: 1 week ago

Hi All

I'm using FSUIPC 7 with MSFS2020. I trying to control the PMDG 737 with SIOC and a script. I'm having problems getting the Captain Main & Lower DU selectors to work.

I can get the parameter to work, which changes in the Offset Log when I display it on the FS title bar, but I can't get the Event ID's to work. The DU knobs on the PMDG don't turn when I turn the Opencockpits MIP hardware knob.

This is my script.... Have I written it correctly?

I've also tried Offset $65ED for the ID, taken from the PMDG 737 Offset mapping in the FSUIPC document and EnableBroadcast is active in the PMDG Options.ini

Regards.. Ian

// DU LEFT

Var 2080, name SEL_PAR, Link FSUIPC_OUT, Offset $3114, Length 4 // MAIN DU SELECTOR PARAMETER

Var 2082, name SEL_ID, Link FSUIPC_OUT, Offset $3110, Length 4 // MAIN DU SELECTOR ID

Var 54, name CPT_DU_OUTBD, Link IOCARD_SW, Device 17, Input 0

{

IF &CPT_DU_OUTBD = 1

{

&SEL_PAR = 0

&SEL_ID = 69967

}

Var 55, name CPT_DU_NORM, Link IOCARD_SW, Device 17, Input 1

{

IF &CPT_DU_NORM = 1

{

&SEL_PAR = 1

&SEL_ID = 69967

}

Var 56, name CPT_DU_ENG, Link IOCARD_SW, Device 17, Input 2

{

IF &CPT_DU_ENG = 1

{

&SEL_PAR = 2

&SEL_ID = 69967

}

Var 57, name CPT_DU_PFD, Link IOCARD_SW, Device 17, Input 3

{

IF &CPT_DU_PFD = 1

{

&SEL_PAR = 3

&SEL_ID = 69967

}

Var 58, name CPT_DU_MFD, Link IOCARD_SW, Device 17, Input 4

{

IF &CPT_DU_MFD = 1

{

&SEL_PAR = 4

&SEL_ID = 69967

}

This topic was modified 1 week ago by Fake Pilot

9 Replies

Posts: 331

FSUIPC Support

Moderator

July 18, 2026 7:08 pm

(@fsuipc-support)

Joined: 9 months ago

Posted by: @fake-pilot
↑
This is my script.... Have I written it correctly?

Sorry, but I have no idea. For SIOC scripts, ask for SIOC support.

The event ID you are sending looks correct - its this one:

#define EVT_DSP_CPT_MAIN_DU_SELECTOR (THIRD_PARTY_EVENT_ID_MIN + 335) // CAPT side MAIN PANEL DISPLAY UNITS (MAIN PANEL DUs) Selector

Bit from the script (extract) you have provided, I have no idea what is happening. Is the parameter written before the event? This is necessary.

Can you add logging (in FSUIPC7) for offsets 3114, 3110 and 65ED and show me /attach a log file. Also activate Event logging.

Posted by: @fake-pilot
↑
I can get the parameter to work, which changes in the Offset Log when I display it on the FS title bar, but I can't get the Event ID's to work. T

Does this mean that logging offset 3110 shows nothing? In that case, your SIOC script is not updating that offset, and you need SIOC support.

Posted by: @fake-pilot
↑
I've also tried Offset $65ED for the ID, taken from the PMDG 737 Offset mapping in the FSUIPC document and EnableBroadcast is active in the PMDG Options.ini

All PMDG specific offsets are read-only - you cannot and should not try to write/update them.

I am unavailable tomorrow - will check your files (if provided) on Monday.

John

Posts: 4

Fake Pilot

Registered

Topic starter

July 19, 2026 8:26 am

(@fake-pilot)

Joined: 1 week ago

Thanks John for your reply.

I have logged the Events and used Offsets 65ED & 3114. In the log file I can see that 3114 is changing the parameter when I turn the hardware DU selector, but 65ED has only one entry of number 1.

Log attached.

Ian

Attachment : FSUIPC7.log

Posts: 331

FSUIPC Support

Moderator

July 19, 2026 10:26 am

(@fsuipc-support)

Joined: 9 months ago

There is no logging for offset 3110 - can you add that please. I need to see that to make sure that the event is triggered, as it is the writing to that offset that triggers the sending of the event.

There was previously an issue that when writing the same value to offset 0x3110 would not trigger the event, but I thought that this was resolved. However, I will check this again here.

John

Posts: 4

Fake Pilot

Registered

Topic starter

July 19, 2026 11:38 am

(@fake-pilot)

Joined: 1 week ago

Updated log with 3110 Offset. Same as before. It registers the parameter but not the event. There's only 1 entry for 3110, numbered 79

Attachment : FSUIPC7.log

Page 1 / 2 Next