Sorcerer GPSS and GPSV problems

[SabaJoe]

Need help with a Lancair ES-P flying with a dual Sport Chelton EFIS with pinpoint GDAHRS integrated with the Sorcerer autopilot and Garmin SL30 Nav/Com. Seems like the Sorcerer will work fine in capturing and holding Altitude Select and Track when programmed on the autopilot. If the Chelton is programed with a flight plan and targeted altitudes or an approach, the GPSS will S curve rather violently when transitioning from one waypoint track to another. Similarly, GPSV will cause severe porpoising when the unit transitions altitudes or tries to follow the HITS glide slope. I checked the settings on the LAT ACTIVITY (4), LAT TORQUE (12), VRT ACTIVITY (4), and VRT TORQUE (12).

Would appreciate some troubleshooting tips.


Thanks

[TrutrakTech]

Can you tell me what options you have enabled in the Chelton setup? Thanks!

[SabaJoe]

I have not personally explored the Chelton setup. It was configured by the avionics installer. Is there somethig I should be looking for in particular? I would be happy to call from the cockpit and see what adjustments I could make by phone conference.

[SabaJoe]

Actually as we speak, my avionics installer tells me there is a new Sorcerer software update V2.36 which he thinks may address the problem (my Chelton's were updated November 2009). Is there something I should try before sending the Sorcerer back for the software update?

[SabaJoe]

Hello Lucas:
I am still struggling with the Sorcerer/ Chelton integration particularly if there is vertical guidance with a target altitude or waypoint defined vertical altitude programmed into the Chelton. A GPS approach for example which has the Jeppeson defined vertical guidance is a roller coaster ride of + and - G forces when coupled to the Sorcerer. Now that the Sorcerer was updated with the new combined GPSS/GPSV button, is it possible to engage GPSS while on a Chelton driven approach and use the Sorcerer altitude select to program vertical guidance and altitude capture even if the Chelton has different values? On the old version I would just use GPSS but I just want to be sure I can expect the Sorcerer altitude select function to overide the GPSV component of the combined GPSS/GPSV Sorcerer function in the new version.

[TrutrakTech]

Joe,

Just select any other vertical mode. Alt hold, altitude select, VNAV, or a straight vertical speed select. Any of these modes will put vertical control in the hands of the Sorcerer while leaving it in GPSS. I hope this helps!

[SabaJoe]

great. I will manage the VNav that way. Perhaps one day someone will figure out why the Chelton can send the VNAV commands to the Sorcerer in a usable way.

[TrutrakTech]

great. I will manage the VNav that way. Perhaps one day someone will figure out why the Chelton can send the VNAV commands to the Sorcerer in a usable way.

I would LOVE for that to happen. But we've been waiting a long time....

[SabaJoe]

Lucas, when a Chelton is tuned for an ILS approach and the NAV source selected by the Chelton is the ILS/localizer frequency, the HITS box GPS LATERAL and VERTICAL guidance is still generated by the system. If the Sorcerer mode selected is the GPSS, what nav data source is the sorcerer autopilot using in the coupled approach? Is it the glideslope from the ILS/localizer or the GPS generated HITS?
Thanks

[TrutrakTech]

It would be the GPS generated HITS.