Hello to all,I am able to get my X and Y axis to work very well in WinXP (an Epic-modified F-22 plugged into the FLCS port). As I incorporate other analogs into my project like my Epic-modified TQS (plugged into Plug :(, I start getting mixed up axis outputs in WInXP. It will usually keep X as X, but switch the Z and X (and Rx) axis. device(COCKPIT) { connector(FirstExpansionModule); analog(0, ROLL, X); analog(1, PITCH, Y); analog(6, THROTTLE, Z); // analog(13, RUDDER, Rz); button(5, 2, TG1); };EpicInfo shows the axis working in the proper channels, both Input and Output, however, I go to windows and it is hosed. I have gone over wiring diagrams and checked my hardware. I am thinking it is in my files somewhere.I unplugged the TQS and the same thing happens when I only add the rudders - it trades the Y and Rx axis.Thanks in advance for any help or ideas. Just trying to learn...

This worked for me.device(Device0) {connector(moduleone); analog(0,roll,X); analog(1,pitch,Y); analog(2,rudder,Z); analog(3,throttle,Rx); analog(4,propeller,Ry); analog(5,mixture,Rz);}Steve K.

OOPS!forgot the ; after the last };Sorry!Steve K.

whoops. I thought I replied earlier.. I updated my EPRom and it fixed the problems I had with the axis numbering.