On 04/08/2011 10:40 PM, Catherine James wrote:
Recently, I've been spending a good bit of time attempting to program all of
my most-used aircraft so that I can engage and disengage the autopilot
through the joystick. I've been able to get this to work on the Seneca II
with a short nasal
The nasal code
replicates the behavior described in the Century III Autopilot Flight
System Pilot's Operating Handbook. You used to be able to download a
PDF of this from Century. This is no longer the case.
Try this link http://www.centuryflight.com/manuals/CENTIIB.pdf.
Catherine,
Not quite the answer you seek, but following to Sids comments. My advice is
keep any thing you want generic to your setup away from aircraft model nasal
if possible.
If it helps,
I used xml for controlling some auto pilot functions via Joy stick control
to avoid fooling around in
Sid wrote: Maybe you already looked into this , but to me it would make more
sense to bind the joystick buttons to activate the enable properties in the
actual autopilot.xml files rather than modifying the author's specialized
scripts.Or write a generic nasal file to handle the variety of
Just another thought , but I'm on a laptop with mouse ... no joystick
to test is property aliasing ?
the multipayer options give me the idea but i'm no expert on this myself...
multiplay
generic
int n=0 alias=/systems/electrical/outputs/strobe/
/generic
Maybe you already looked into this , but to me it would make more
sense to bind the joystick buttons to activate the enable properties
in the actual autopilot.xml files rather than modifying the author's
specialized scripts.Or write a generic nasal file to handle the
variety of different enabling
6 matches
Mail list logo
