“Tools->Save database now”. If things seem unstable, use that a lot.
Next version of AAO has an Offline mode, where you don’t need the sim all the time.
On the dialog where you can create new script groups you can delete them too.
You probably could edit the gauge itself, maybe the variables don’t work for your particular plane?
C:\Users.…\AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS\FipGauges_MSFS\Gauges
Thanks for the quick answer.
Got it, thank you. Will do.
Sorry, I didn’t noticed that. Thank you, that will help a lot.
Thanks for pointing that out. Sadly I am not familiar with dealing with these xml files. Is there an API somewhere? When I look at this line: (A:Kohlsman setting hg,inHg) % …it looks like integer to me, which would explain my problem. Would you mind telling me, how to declare two decimal digits?
Awesome support, thank you so much!
I need to look at that gauge again first. It has been quite some time. Maybe some update of AAO broke it - it is not like a lot of people are using them…
I am having a hard time posting that line completely. One more try:
“Value Minimum=“0” Maximum=“99” >(A:Kohlsman setting hg,inHg) %”
That is not how this gauge works. It is shifting long image strips with numbers on it, not displaying text-
Find line 414 in the XML and change it from this
<Value Minimum="0" Maximum="99">(A:Kohlsman setting hg,inHg) (A:Kohlsman setting hg,inHg) % - 100 *</Value>
to this: (replace the % in the middle with flr)
<Value Minimum="0" Maximum="99">(A:Kohlsman setting hg,inHg) (A:Kohlsman setting hg,inHg) flr - 100 *</Value>
Same for the mach number, that is line 740 (replace the % in the middle with flr)
<Value Minimum="0" Maximum="99">(A:Airspeed Mach,number) (A:Airspeed Mach,number) flr - 100 * %</Value>
Edit: the code in these Saitek FIP gauges is probably pre-FSX. The “%” (or modulo) has a different spec in later FSX versions and in MSFS, that is why the code fails here. At some point the RPN logic in AAO had been updated to current specs, but unfortunately nobody thought of checking the legacy Saitek gauges.
That worked! Absolutely awesome support! Thank you so much!
This will be super!
After several years with FSUIPC I decided to give this one a try. So far I’m quite impressed, the GUI feels a lot more intuitive than FSUIPC and it seems you can do a lot without having to dive into the upside world of RPN scripting 
One thing that I haven’t been able to figure out though is how map an event to an axis so that it triggers when I move the axis up into a certain range but not when I move it down and out of the range.
In my case I like to map the Gyrop Pilot Lever in the DC-6 to one of my Honeycomb Bravo levers. I would like to trigger the event when I move the lever all the way up and again when I engage the button at the bottom. However I can’t figure out how to prevent the event from triggering when I move the lever down.
In the GUI there’s an option for triggering virtual keys depending on the direction of movement (up, down etc) but I can’t find a similar option for triggering scripts/sim events.
I’ve tried a script with an if/else if statement like the following (pseudo code):
If lever > 16300 and LVar == 0 then {
Send xxx01 to ROTOR_BRAKE
WAIT 1000
} else {
if lever < -16300 and LVar == 1 then {
Send xxx01 to ROTOR_BRAKE
WAIT 1000
}
That didn’t work
P.S @LorbySI it would be super if you could add page numbers in the manual, that would make it easier to navigate from the table of contents
P.S 2: I figured it out! Two scripts, one assigned to the axis and one to the button made it work. The script assigned to axis triggers if the lever is > 16000 and LVar == 0. The script assigned to button triggers only if Lvar == 1
Hello,
I try to use AAO with Saitek FIPs but with no luck. AAO sees all of them, but when I try to set a gauge, nothing happens after klicking on the “set gauge button”. I only installed the last driver for FIPs and no plugin.
Can anybody help or give advice?
The latest driver won’t cut it, Logitech removed the 3rd party API. You need a specific version, “Flight_Instrument_Panel_x64_Drivers_8.0.150.0.exe” which you will also get on the Logitech support site. When everything is installed correctly. the FIP should show the advertising screen (see AAO manual what that looks like). Only then can you connect AxisAndOhs.
For everyone struggling with RNP I found this absolute GEM right here at the forum. I can’t understand why that post haven’t got more than 2 likes and a handful of responses, as far as I’m concerned @devsnek deserves a Nobel Prize for this 
On my end, it is the same with trigger events:
Edit: unfortunately there is indeed a bug. When you open an axis assignment to change it, the dialog doesn’t “get it” if there is a trigger event assigned to the axis. This will be fixed in the next version.
But I would also use RPN scripts for more complex requirements. I would query the associated PMDG LVar to make a switch or not:
lever 16300 > if{ (L:dc6_443_obj_switch, Bool) 0 == if{ lever up} } els{ (L:dc6_443_obj_switch, Bool) 1 == if{ lever down}}
@LorbySI I’m afraid I’ve found another bug:
Go to Templates->Edit Template, select one and press Edit selected. Select an assignment and press the - button.
Expected behavior: The selected assignment should be deleted
Actual behavior: The first assignment in the group is deleted
OK. I will put it on the list for 2.20.
The file you mentioned (Flight_Instrument_Panel_x64_Drivers_8.0.150.0.exe) IS the driver itself as far as I know and this one is installed. The name is “Direct Output”:
If the splash screen is visible, that should be good enough. So what happens when you start AAO, connect it to the sim and activate “Hardware->Saitek FIPs enabled”?
but when I try to set a gauge, nothing happens after klicking on the “set gauge button”.
That one I didn’t understand. Where is that button exactly?
The button I mentioned, is the one in the lower right corner of the “config FIP” window.
If I klick it, nothing happens. It just change color.
And yes, this is also true when Sim is connected.
I’m sorry, but I don’t understand what you are trying to do. This dialog changes what the buttons do on that gauge. That’s it.
This activates the connection to the FIPs:
When you want to switch to other gauges, you use the two lower buttons on the FIP itself.
Edit: using four FIPs with AAO is not recommended. The update rate will be very low, the DirectOutput API will probably run this at 4 FPS or worse. As the product description states, “up to three Saitek FIPs” are supported. More will still work, but they will be slow.
I’m sorry if I could not describe my problem clear enough. But, good news, it’s running now. I was struggled due to fact, that obviously nothing should happen, when I change gauges in the FIPs configuration window (and of cause sim has to run). But in background it do. I now have 4 FIPs in use and everyone shows the chosen instrument. One last question:
I would like to disable the labels right beside the buttons 1-6. I deleted the text of every button and klicked on “change gauge” and activated “Saitek FIPs enabled” in the pull down menu, but labels are still there. What I made wrong was not to restart AAO, after Changes.
Please see pictures below:
I have it done now. Thanks for your help!
