PM MCP Throughpass

[Cpt Krabs]

Hello,

I have a problem with the 04F4 offset of PM. I use an IOCards system on my cockpit with SIOC. No problem for use the ELAN codes to contral all the MCP Buttons, everything works fine.

My problem is about this (found in the PM Offsets documentation after the list of ELAN K codes) :

Suggestion:

V10 MINS

V11 BARO

V12 Copilot MINS

V13 Copilot BARO

V101002 (increments MINS by 2 units)

V110004 (decrements BARO by 4 units) V11 [baro] 0 [dec] 004 [4 units]

Send offset and value to write in UIPC...

E0 [offset] [numbytes] [value] (value can be anything after the 7th byte, with or without leading zeroes

E00BC081234.5 writes 1234.5 in 0XBC0 8 bytes (=double)

E004F42005 writes 5 into 0x4F4 (i.e. E0 04F4 2 005)

E004F422 writes 5 into 0x4F4

This seems to be very powerfull but I do not understant were to send these values. If I send direct as "Assign" to O4F4, SIOC do not want because I send letters (V, E, ...). If I only send the numbers, nothing happens. Here is an example of my ssi file where I tried to program the CPT Baro encoder with these codes :

Var 4036, name CPT_BARO_ENC, Link IOCARD_ENCODER, Device 1, Input 40, Aceleration 3, Type 2 // CPT BARO Encoder

{

L0 = &CPT_BARO_ENC

IF L0 > 0

{

&MCP_THROUGH = 111004

&MCP_THROUGH = DELAY 0 ,25

}

IF L0 < 0

{

&MCP_THROUGH = 110004

&MCP_THROUGH = DELAY 0 ,25

}

}

Could you please telle me where and what to send these values ? The document from PM says "Send offset and value to write in UIPC" but I do not understand what offset to use and what to send ?

Thank you very much

[Pete Dowson]

Could you please telle me where and what to send these values ? The document from PM says "Send offset and value to write in UIPC" but I do not understand what offset to use and what to send ?

Sorry, I don't know anything much about "Elan K Codes". I think that's all to do with keyboards. Have you tried PM support?

The values I use when writing to 04F4 are those listed in the main table, aganst the offset for 04F4 -- i.e. "Airbus 1 MAP ...." ertc. I think all the codes you can use are listed there. I think the MCP Throughpass is offset 04F2. If you look in the main table for 04F2 it gives an example.

I think, for ogffset use, you are reading the wrong list of codes. The ones you quote above are only for keyboard or character based communications "Elan". If you look in the list before that section you will see.

Regards

Pete

[Cpt Krabs]

Thanks for the quick answer Pete. I speak about O4F2 offset (throughpass) sorry for the 04F4 type error.

The problem is that I have MCP freeze when DisableRemoteMCP=Off in the MCP.ini file, that's why I set it to ON. The problem now is that I cannot use the 04F4 offset to set my DH / BARO because this offset needs you set DisableRemoteMCP=Off for this to work. I'm looking for another solution but I do not find...

[Pete Dowson]

The problem is that I have MCP freeze when DisableRemoteMCP=Off in the MCP.ini file, that's why I set it to ON.

Hmm. Have you raised this with PM? Or is it a problem with a specific hardware MCP? I really don't understand how that parameter helps. Very odd.

Regards

Pete

[Cpt Krabs]

I never have any answer from PM support... I do not use any MCP hardware, only switches and encoders mounted myself and connected to IOCards.

[Pete Dowson]

I never have any answer from PM support... I do not use any MCP hardware, only switches and encoders mounted myself and connected to IOCards.

So what is "freezing"? You mean the PM MCP software hangs? If so that is certainly a matter for PM support. Are you up to date? The PM modules are updated relatively frequently -- there was one less than a month ago.

Pete

[Cpt Krabs]

No the software doesn't hang but when I manipulate encoders, switches, after about 1 minute the PM MCP doesn't accept any command from my hardware and if I look in the software window the small windows sandglass appears on the mouse pointer for about 2 minutes. After that the MCP is ready for new commands. When I turn the option "DisableRemoteMCP" to ON in the .ini file the problem disappears but I do not have any access to the 04F4 offsets.

[Pete Dowson]

No the software doesn't hang but when I manipulate encoders, switches, after about 1 minute the PM MCP doesn't accept any command from my hardware and if I look in the software window the small windows sandglass appears on the mouse pointer for about 2 minutes. After that the MCP is ready for new commands. When I turn the option "DisableRemoteMCP" to ON in the .ini file the problem disappears but I do not have any access to the 04F4 offsets.

Hmm. Sorry, then. All I can suggest is making sure you are using the latest version, enabling the Logging (in the MCP.INI file), and submitting details to PM support. Do IOCards interface directly to pmMCP, or do you have a software driver? If so, could it be a problem with the latter? The fact that you are asking about 04F2 access suggests you have your own software? Are you sure it isn't that keeping the MCP in some loop?

I have my own driver for the PFC MCP hardware interfacing to the pmMCP and don't have any problems. The 04F2 access is fine, but then I definitely don't have "DisableRemoteMCP" set to on. However, my 04F2 and 04F4 access is via a queuing system which waits a short time (250 mSecs max) for the pmMCP to clear the previous value to zero before writing the next. Also, for dials, I keep the hardware display up to date locally, but only transmit the updated values to the pmMCP offset when the dial stops turning for a while (500 mSecs, for example). This avoids overloading the pm code and the interface for no good reason.

Regards

Pete

[Cpt Krabs]

My IOCards interface with pM MCP via SIOC programing software. I'll try your queuing system and add some wait instructions with my commands. I'll keep you informed.

Thank you very much and best regards