Hi Phil,
I just posted this in your thread on my Forum, but i'll repeat it here in case you aren't looking there at present:
I was investigating the solution I suggested that I might be able to implement when I stumbled across something already implemented in the current versions of both FSUIPC3 and FSUIPC4. This was a sepcial facility to allow my PFC and GA28R drivers to send axes direct to FSUIPC's calibration facilities. Being of, as I thought then, limited usefulness it was not documented in the FSUIPC SDK, but only in the PFC driver document. Here are the details:Quote:
Originally Posted by philb737
Application program axis handling
When using FSUIPC version 3.30 or later, application programs or modules can access the raw PFC axis values at offsets 3BA8 onwards. One 16-bit word is allowed for each (although currently all PFC axes have a maximum range of 0 to 127, this may change in future). The axes are:
3BA8 0 Aileron
3BAA 1 Elevator
3BAC 2 Rudder
3BAE 3 Quadrant axis 5
3BB0 4 Quadrant axis 3
3BB2 5 Quadrant axis 1
3BB4 6 Left toe brake
3BB6 7 Quadrant axis 6
3BB8 8 Quadrant axis 4
3BBA 9 Quadrant axis 2
3BBC 10 Right toe brake
3BBE 11 Elevator trim
3BC0 12 Aileron trim
3BC2 13 Rudder trim
3BC4 14 Steering tiller
3BC6 15 not used
There are control flags (to disconnect these axes) at offset 3BC8. Each bit, 2^0 to 2^15 can be set to disconnect the equivalent numbered axis above. The cowl flap axes are not part of this facility.
So ... please try this: get your Phidgets software to send the Rudder value to 3BAC, and the Tiller value to 3BC4. Best to do both this way for better chance that the automatic switchover takes place based on airspeed and so on.
Let me know how you get on, please. If this is useful I might add the details to the regular offsets list.
Regards
Pete