IRS Button assignment for PMDG

maybe try a direct assignment in FSUIPC (e.g. a key assignment) to this first to check if it is working correctly in the 373-800 in MSFS2024

I tested the above and it’s fine. 

I have found the problem but I don’t know why.  With my additions to the sioc script for IRS I found that my speedbrake and flaps (also configured in sioc to send to the x3110 and x3114 offsets and which you got working for me 100%) stopped working.  These both were using Event Control and a Parameter for left mouse click.

So I took out everything to do with IRS and speedbrake/flaps work again.

So then I just added NOTHING ELSE but one switch, the TEST position of IRS knob, and lo and behold, after moving the knob to TEST, this stops my speedbrake/flaps from working again.  I can get them working again by reloading the sioc script, but if I turn the IRS knob to TEST again, they are no longer working.

The other thing I noticed is that when I turned the knob to Test, in PMDG it didn’t go to the TEST position but just one to the left, as if the offset gets corrupted

So this button in my script is doing something to those 2 offsets whereby they seem to get blocked/corrupted.  I know you are not a sioc supporter, but the script is so simple. I thought it may be because these Direct Parameters (different from Mouse click parameters, which are all I have used so far in the sioc script) may be repeating and blocking out the offsets.

Input 48 is my TEST button, Parameter 0 is the TEST btn position in the PMDG sdk

Var 0150, name TestCtrl, Link FSUIPC_OUT, Offset $3110, Length 4 

Var 0151, name TestParam, Link FSUIPC_OUT, Offset $3114, Length 4 

Var 0152, name IRS_TEST_I, Link IOCARD_SW, Device 7, Input 48
{
  IF &IRS_TEST_I = 1
  {
    &TestParam = 0  
    &TestCtrl = 69861
  }
}

As a side note, when I had the full IRS part of the script in (not just the above bit) I got the following windows error when reloading the script.  I had to close the program and open again

EDIT 1 – maybe I should not have multiple variables in the sioc script pointing to these 2 offsets.  For example I have 2 for spedbrake and flaps as follows, these work fine together:

Var 0105, name SpdBrkCtrl, Link FSUIPC_OUT, Offset $3110, Length 4 // For the control ID

Var 0106, name SpdBrkParam, Link FSUIPC_OUT, Offset $3114, Length 4 // For the parameter

Var 0110, name FlapLeverCtrl, Link FSUIPC_OUT, Offset $3110, Length 4 // For the control ID

Var 0111, name FlapParam, Link FSUIPC_OUT, Offset $3114, Length 4 // For the parameter

But then I have also another for the TEST button:

Var 0150, name TestCtrl, Link FSUIPC_OUT, Offset $3110, Length 4 

Var 0151, name TestParam, Link FSUIPC_OUT, Offset $3114, Length 4 

I have now changed the script so there are just 2 lines referring to x3310 and x3114, this seems to have stopped the issue with my speedbrake/flaps stopping working.

If I set the knob on the IRS to the far right (HDG/STS) using an fsuipc button (parameter 4), then if I move the knob to the left it seems to work, but I can’t move right!  It seems just like a left mouse click but always going in a left turn and not a right turn.

I ran the log below, you can see the above in action, the knob being Control 69861 and you can see the parameters 3,2, 1, 0.  The control 76xxx is just my jittery flap or speedbrake lever

I noticed that these Direct Parameters are being written as S8, whereas I have them in my script as 4 bytes, unsure if this is relevant

602203 Monitor IPC:3110 (U32) = 76423
   602718 Monitor IPC:3110 (U32) = 76773
   603172 Monitor IPC:3110 (U32) = 76423
   604281 Monitor IPC:3110 (U32) = 69861
   604281 Monitor IPC:3114 (S8) = 3
   604375 Monitor IPC:3110 (U32) = 76423
   604375 Monitor IPC:3114 (S8) = 0
   604937 Monitor IPC:3110 (U32) = 76773
   605031 Monitor IPC:3110 (U32) = 76423
   606203 Monitor IPC:3110 (U32) = 69861
   606203 Monitor IPC:3114 (S8) = 1
   606234 Monitor IPC:3110 (U32) = 76423
   606234 Monitor IPC:3114 (S8) = 0
   606562 Monitor IPC:3110 (U32) = 69861
   606812 Monitor IPC:3110 (U32) = 76423
   607703 Monitor IPC:3110 (U32) = 76773
   608422 Monitor IPC:3110 (U32) = 76423
   608578 Monitor IPC:3110 (U32) = 69861
   608578 Monitor IPC:3114 (S8) = 2
   608640 Monitor IPC:3110 (U32) = 76423
   608640 Monitor IPC:3114 (S8) = 0
   608875 Monitor IPC:3110 (U32) = 69861
   608875 Monitor IPC:3114 (S8) = 3
   609172 Monitor IPC:3110 (U32) = 76423
   609172 Monitor IPC:3114 (S8) = 0
   609390 Monitor IPC:3110 (U32) = 76773
   609656 Monitor IPC:3110 (U32) = 76423
   611422 Monitor IPC:3110 (U32) = 76773

Hi John, still on this IRS, now on the output display! The PMDG 737 offsets has these 2:

  I have the following in my script but it is not producing anything meaningful.  The script is simply placing the PMDG offset string into the left and right side of the display, when the battery is on (-999999 blanks the display when battery is off).  The offsets are 7 and 8 bytes respectively (left, right), but sioc only accepts 1,2,4 or 8 so I put in 8

Var 0160, name IRS_L, Link IOCARD_DISPLAY, Device 7, Digit 9, Numbers 6     // IRS's LEFT DISPLAY DIGITS

Var 0161, name IRS_R, Link IOCARD_DISPLAY, Device 7, Digit 1, Numbers 7     // IRS's RIGHT DISPLAY DIGITS

Var 0168, name IRS_Rconv, Link FSUIPC_IN, Offset $6435, Length 8 

Var 0169, name IRS_Lconv, Link FSUIPC_IN, Offset $642E, Length 8 

Var 0170, name Batt, Link FSUIPC_IN, Offset $64A5, Length 1 
{
  IF &Batt = 0
  {
    &IRS_R = -999999
    &IRS_L = -999999    
  }
  ELSE
  {
    &IRS_R = &IRS_Rconv
    &IRS_L = &IRS_Lconv  	    
  }	
}

Posted by: @skythelimit

↑

I noticed that these Direct Parameters are being written as S8, whereas I have them in my script as 4 bytes, unsure if this is relevant

You should log offset 0x3114 as S32 to get the correct value, not S8 as you are then logging just one of the 4 bytes.

The logging should tell you what parameter and control are being sent, with the last-logged parameter being used when the control number is logged.

If you are writing to these offsets using multiple threads, then you can get into issues, e.g. thread1 may write the parameter and then thread 2 could change this before thread 1 writes the control. I don’t know SIOC, so it is up to you how such issues are resolved in SIOC.

Not sure what is happening, or if this is really an issue, but the logging should tell you what is happening.

John

Posted by: @skythelimit

↑

still on this IRS, now on the output display! The PMDG 737 offsets has these 2:

Not sure why you created a new topic if its the same issue….I have merged this in with your other topic.

But I can’t help with SIOC. You can also try logging those offsets to make sure they are holding the correct values, but I cannot help with using these in SIOC.