AP VS integration

[bradrcfii]

I am setting up a GoFLight MCPPro for some of the Autopilot functions for the ORBX Lancair. I was able to use sucessfully FSUIPC for Heading, Altitude Hold, Approach and Nav. However, I have not been able to integrate the VS function. It is an on/off type switch on the AP panel. You first engage VS, then dial in the rate. I am not sure if I should use CS Hold, VS On Off,. VS set etc. functions found in the FS drop down list. I believe I tried them all and non worked.

Any idea's or is this an Orbx problem.

Thanks,

PS I am running 4.70b.

[Pete Dowson]

... I have not been able to integrate the VS function. It is an on/off type switch on the AP panel. You first engage VS, then dial in the rate.

That's normal. The VS dial isn't usually operative until VS is engaged. Note that you usually need to set an altitude to climb or descend to first.

I am not sure if I should use CS Hold, VS On Off,. VS set etc. functions found in the FS drop down list. I believe I tried them all and non worked.

If the aircraft uses standard FS controls you should be able to find out by enabling event logging in the FSUIPC Logging tab, then operating the aircraft using the mouse and checking the FSUIPC log to see what controls were sent.

You could also check what you are doing in a default aircraft such as the default 737.

If the aircraft doesn't use standard FS controls then you'd need to seek alternative means. Check the "User Contributions" subforum to see if there are any clues there.

Regards

Pete

[bradrcfii]

Thanks for the suggestions. I will enable logging.

The Lancair autopilot is a little less functional in that there is no altitude selection, can't set an altitude. You push the ALT button when you are at the altitude you want to be. Kind of old style. A Cessna T210 I flew in the early 80's operated the same way.

[bradrcfii]

I logged the event(s) when I hit the VS button on the AP. The log shows many events for the button push so not sure what to do.

Thanks,

534531 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

534593 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

534640 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

534671 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 0 (0x00000000) AP_VS_VAR_SET_ENGLISH

534671 *** EVENT: Cntrl= 66124 (0x0001024c), Param= -100 (0xffffff9c) AP_ALT_VAR_SET_ENGLISH

534671 *** EVENT: Cntrl= 66103 (0x00010237), Param= 1 (0x00000001) AP_PANEL_ALTITUDE_ON

534671 *** EVENT: Cntrl= 66102 (0x00010236), Param= 1 (0x00000001) AP_VS_SET

534703 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

534765 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

534812 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

534875 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

534937 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

534984 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535046 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535109 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535156 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535218 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535250 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535312 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535359 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535421 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535484 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535531 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535593 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

535656 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

[Pete Dowson]

I logged the event(s) when I hit the VS button on the AP. The log shows many events for the button push so not sure what to do.

Well, apart from continuously toggling the flight director on and off (about 20 times per second):

534531 *** EVENT: Cntrl= 66288 (0x000102f0), Param= 1 (0x00000001) TOGGLE_FLIGHT_DIRECTOR

the only AP commands were:

534671 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 0 (0x00000000) AP_VS_VAR_SET_ENGLISH

534671 *** EVENT: Cntrl= 66124 (0x0001024c), Param= -100 (0xffffff9c) AP_ALT_VAR_SET_ENGLISH

534671 *** EVENT: Cntrl= 66103 (0x00010237), Param= 1 (0x00000001) AP_PANEL_ALTITUDE_ON

534671 *** EVENT: Cntrl= 66102 (0x00010236), Param= 1 (0x00000001) AP_VS_SET

I assume the aircraft code is doing that FD toggling, though why I have no idea. It seems to be unrelated to your button usage, though, doesn't it?

So, now you know what you need to send FS to enably the VS. You can make the one button send those 4 controls one after the other. you wil have to edit the FSUIPC INI file to do that. The log above shows you the control number ("Cntrl= ..." and the Parameter (Param =) for each of the 4, so it is easy enough. Something like this in the [buttons] section:

xxx=Pjoy,button,C66036,0

xxx=Pjoy,button,C66124,-100

xxx=Pjoy,button,C66103,1

xxx=Pjoy,button,C66102,1

where xxx are incrementing numbers after those already used, and of course joy,button identify the joystick and button number.

Regards

Pete

[bradrcfii]

Thank you. The constant steam of FD events starts when I hit the Heading Button. Does not look right to me either. On this AP, you must engage a lateral mode before a pitch mode can be enabled. I first hit the heading button that started the event stream and then VS.

[bradrcfii]

ORBX response asking about the event stream when hitting the Heading button.

"Unfortunately the fsx autopilot system does not mimic well the functions of the stec55x. A fair bit of coding trickery was employed to get it to function close to correctly. A byproduct of this is the event streaming you noticed. Regardless there is no performance hit or other problems associated with it.

As for setting up hardware to work with it your best bet is to dissable it and use a simpler AP because it will usualy cause conflicts"

I am not sure what he means in his statement about disabling and using simpler hardware. Integrating some of the MCPPro functions has been easy via FSUIPC.

[Ian P]

I believe he means disable the gauge and use a more basic gauge, rather than the hardware, Brad.

Ian P.

[bradrcfii]

I see. Thanks.