Jump to content
The simFlight Network Forums

Issue with Pro-Flight Multi elevator trim


Recommended Posts

Hey guys,

I am running FSX, FSUIPC and own the Saitek Pro Flight Multi panel

All of the controls on the panel seem to work perfectly except the elevator trim

When ever i turn the elevator trim wheel it seems to move a bit then reset back to zero.

Here is a copy of the log file while in the aircraft, on the tarmac. (This problem is not aircraft specific either)

89186 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN

89233 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN

89233 *** AXIS: Cntrl= 65706 (0x000100aa), Param= 87 (0x00000057) ELEVATOR_TRIM_SET

89280 *** AXIS: Cntrl= 65706 (0x000100aa), Param= 55 (0x00000037) ELEVATOR_TRIM_SET

89280 *** AXIS: Cntrl= 65706 (0x000100aa), Param= 119 (0x00000077) ELEVATOR_TRIM_SET

89280 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN

89280 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN

89342 *** AXIS: Cntrl= 65706 (0x000100aa), Param= 151 (0x00000097) ELEVATOR_TRIM_SET

I believe that one of these entries is invalid but i am unsure which one and completely unsure how to remedy this problem

I have disabled FSUIPC and the trim worked perfectly as well.

FYI i alsy own the Instrument panel, flight yoke, throttle quadrant and at one stage had the X52pro connect at the same time (but that has been disconnected now)

Thank you very much for the product and the any help you can provide

Nasica

Link to comment
Share on other sites

I am running FSX, FSUIPC and own the Saitek Pro Flight Multi panel

All of the controls on the panel seem to work perfectly except the elevator trim

When ever i turn the elevator trim wheel it seems to move a bit then reset back to zero.

Here is a copy of the log file while in the aircraft, on the tarmac. (This problem is not aircraft specific either)

89186 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN

89233 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN

89233 *** AXIS: Cntrl= 65706 (0x000100aa), Param= 87 (0x00000057) ELEVATOR_TRIM_SET

89280 *** AXIS: Cntrl= 65706 (0x000100aa), Param= 55 (0x00000037) ELEVATOR_TRIM_SET

89280 *** AXIS: Cntrl= 65706 (0x000100aa), Param= 119 (0x00000077) ELEVATOR_TRIM_SET

89280 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN

89280 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN

89342 *** AXIS: Cntrl= 65706 (0x000100aa), Param= 151 (0x00000097) ELEVATOR_TRIM_SET

I believe that one of these entries is invalid but i am unsure which one and completely unsure how to remedy this problem

I have disabled FSUIPC and the trim worked perfectly as well.

FYI i alsy own the Instrument panel, flight yoke, throttle quadrant and at one stage had the X52pro connect at the same time (but that has been disconnected now)

You obviously have an FSUIPC axis assignment for the trim as well, and that is sending its own trim settings as you can see (the highlighted lines). Just find it and delete/clear it.

Pete

Link to comment
Share on other sites

You obviously have an FSUIPC axis assignment for the trim as well, and that is sending its own trim settings as you can see (the highlighted lines). Just find it and delete/clear it.

Pete

Thank you for your help,

After many weeks of frustration i have finally tracked down the problem, turns out i was looking in the wrong place, and i thought i would share it with anyone here who may come across the same problem.

After installing the Saitek software it set the FS9 panel module to autorun with the FSX module, this was obviously causing some confliction.

After going to the task manager and closing that particular process everything worked perfectly.

Thanks again for your help and for you great software.

Nasica

Edited by nasica
Link to comment
Share on other sites

After installing the Saitek software it set the FS9 panel module to autorun with the FSX module, this was obviously causing some confliction.

After going to the task manager and closing that particular process everything worked perfectly.

Glad you solved it!

Good flying!

Regards

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.