Throttle interfering with spoiler

[dazzan]

Hi Pete

I think this is a complicated issue, but I do not find an explanation

for what is happening, I tried already so muchon my own.

Under FS2004 I had a driver to connect my throttle (hardware).

Everything worked fine. I used offset 0X88C,2 (ENG1) and offset 0X924,2 (ENG2) to write to.

For the spoilers I used offset 0xBD0, 4.

Now in FSX, if I move the throttle levers (they still use the same offsets), the spoilers are deployed too. That means the throttle works correctly but it also moves the spoilers.

I tried with an old PFC console (with PFC driver), there everything was working correctly.

Which offset does the PFC throttle use for the throttle?

Perhaps you have another idea what to check.

Many thanks

Gilles

[Pete Dowson]

Under FS2004 I had a driver to connect my throttle (hardware).

Everything worked fine. I used offset 0X88C,2 (ENG1) and offset 0X924,2 (ENG2) to write to.

For the spoilers I used offset 0xBD0, 4.

Now in FSX, if I move the throttle levers (they still use the same offsets), the spoilers are deployed too. That means the throttle works correctly but it also moves the spoilers.

Hmmm. Can't detect any connection at all here. Can you reproduce that with FSInterrogate?

Please enable FSUIPC4's IPC read and write logging, and also Monitor those offsets (to the Log) and run such a test. Show me the results -- or if the log is large, Zip it and send it to petedowson@btconnect.com.

Make sure, please, that you use the latest version (4.023 here at present, or 4.026 later tonight), and a default aircraft.

Regards

Pete

[Pete Dowson]

I think this is a complicated issue, but I do not find an explanation

for what is happening, I tried already so muchon my own.

Thanks for the Log, It shows the reason clearly and it isn't complicated. I'm sure you would have seen it for yourself if you'd used the Logging before:

Everytime you write to the throttle offsets you write the same value to the high word of the spoiler offset. Here:

2659000 WRITEex 088C, 2 bytes: C2 02 ..

2659000 WRITEex 0924, 2 bytes: C2 02 ..

2659000 WRITEex 0BCC, 4 bytes: 00 00 00 00 ....

2659000 WRITEex 0BD0, 4 bytes: 00 00 C2 02 ....

2659046 WRITEex 088C, 2 bytes: C2 02 ..

2659046 WRITEex 0924, 2 bytes: C2 02 ..

2659046 WRITEex 0BCC, 4 bytes: 00 00 00 00 ....

2659046 WRITEex 0BD0, 4 bytes: 00 00 C2 02 ....

2659109 WRITEex 088C, 2 bytes: 86 06 ..

2659109 WRITEex 0924, 2 bytes: 86 06 ..

2659109 WRITEex 0BCC, 4 bytes: 00 00 00 00 ....

2659109 WRITEex 0BD0, 4 bytes: 00 00 86 06 ....

etc etc throughtout the log.

Those are HUGE values of course (0x06860000). Maybe, in FS9 and before, FS ignored values over the maximum (16383, or 03FFF), or only used the low bits -- but evidently FSX treats this as maximum deployment instead.

Really it is an error in your program. Obviously you don't really want to set the two high bytes of the spoiler as you do. However, since FS9 and before ignored it, for compatibility I will change FSUIPC4 to filter those bytes off, in the next release.

Regards

Pete

[dazzan]

Pete you are the best!!

Many thanks

Gilles