Script “Batt Master all off” just the 3 respective Off-events, no bus lookup
SD Button “BUS TIE”:
AaO Toggle
Write event: K: C700-Bus Tie Toggle
Send value: 0
Read variable: A: BUS CONNECTION ON:6, Bool
On value: 1
Script “Bus Tie Toggle”:
5 6 (>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE)
I deleted the bus lookup from the “Batt Master all on” script and deleted the BUS TIE button.
After that the SD updated String variables. Numeric variables were never affected.
I don’t have that. The selected altitude will reset to 0 when I connect AAO, but that is the only time this happens. It stays dialled in just fine after that, no matter if I do it on the MultiPanel or in the VC.
Be mindful that the MultiPanel will not work in default mode with the CJ4. The MP must be switched to MIDI mode and customized manually.
This, when used on its own, may be causing an invalid state? Shouldn’t there be some other A: variable following it?
“How to use that in the SD plugin”? By using the S: option and putting an RPN script into the textbox that handles both A: vars and that returns a value at the end
Edit: btw. what “String variables” are we talking about exactly?
Please consider sending me an email to the support address on the last page of the manual. Might be easier than dealing with an issue like this in a forum - especially for the other readers…
Yes, as far as I have tested. I have started to go through every aircraft, and that’s not the only problem I’ve found. The A320Neo behaves very oddly (flashing buttons, and all rotary controls setting to zero or some other preset value when I stop rotating), and in addition to the “ALT” not illuminating, the “AP” master doesn’t either.
Rather than swamp this thread with what I’ve found, I’ll pm you with a full list of what I find.
The Saitek Panel logic in AAO is only compatible with the most default of the default aircraft.
Any of the more advanced addons must be configured by hand, that cannot be covered with default code. All the autopilot buttons and variables are different for almost every aircraft in MSFS. You will have to switch the Saitek panel over to MIDI mode and configure everything manually more often than not. Afraid that is just how it is with MSFS, there are no rules anymore. Every aircraft developer is just doing whatever they want.
I will check the defaults, to see if the variables still apply to MSFS after the latest SUs, but that is as far as the built-in logic can go.
I have just tried it with the steam gauge default C172 and it worked fine. The ALT button illuminated as expected, and everything on the MultiPanel seemd to work out of the box.
@LorbySI How do I transition from the demo version to the full version? If I just run the installer that came with the full version download will that overwrite any profiles that I have created in the demo version? Great program, thanks for all your work and support for the community.
No, it won’t. The installer just replaces the executables.
If you want to make sure, you can either save and export your configs as Templates in AAO, or make a backup copy of the database folder:
C:\Users.…\AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS
Okay strange, seems to be something in my setup, I just have the Saitek Radio Panel nothing else from Logitech/Saitek, so what could it be ? Because if I disable it, the altitude doesn’t keep resetting, so I definitely has something to do with it
Okay strange, seems to be something in my setup, I just have the Saitek Radio Panel nothing else from Logitech/Saitek, so what could it be ? Because if I disable it, the altitude doesn’t keep resetting, so I definitely has something to do with it
Oh, wait, I think I know what that is! There is a bit of logic in the Panel handler, that will reset the selected altitude to 0 if the simulator reports it to be below 0 (as a safeguard against invalid values). Unfortunately, with some aircraft the default selected altitude variable has strange values all the time - and since you don’t have a MultiPanel, you can’t override the incorrect variable manually. But I have one, and the override is in place, so I don’t see it like you do.
Can you please send me an email with your proof of purchase? Then you can have a copy of the current development build where I will fix this. Address is on the last page of the manual.
DA62
Cessna 172
King Air 350
Grand Caravan
Baron G58 and
Beechcraft Bonanza
Behaviour is the same on all of those…all lights except “ALT” illuminate when toggled to “ON”. The “ALT” light never illuminates, but the autopilot appears to fly to the altitude set, providing I dial in a VS that sends it in the right direction (!). If I prompt the aircraft to climb or descend to the AP_Hold altitude that’s been set, the aircraft goes to the correct altitude, and holds as required. But - at no time can I illuminate the “ALT” button.
Happy New Year to you, your team and all your clients!
I’m sorry, but I don’t know what to tell you. I went through your list just now, and the ALT button illuminates every time, for each of these aircraft, both with the button on the MP and the one in the cockpit. I loaded the plane at an airport, and pressed the button twice on the MP and in the VC, to see if the LED turns on and off, and if the mode registers in the cockpit too.
OK. Thanks for your efforts. These things happen. and I know there are often random weird things that can’t be tracked down in isolation. The support you give your clients is amazing, but sometimes you can’t win them all !
Can anybody tell me how to display the Volts value of the Batteries in the FBW A320 on the Streamdeck. I tried the text gauges, but i can not find a script that works.
thanks
Hi everyone. I’m in need of some help controlling the LEDs on the X-Touch. I copied this script from the AAO manual (changing the MIDI ID to match my hardware setup) as a test, but the top left button on Layer A does not change state with the AP. Monitoring the variable I confirmed the variable is changing state.
Since today my Streamdecks dont work anymore. The commands are not executed in the cockpit of the FBW A320. It seems, the connection is lost. Any idea what i could try to fix it?
