#Profile for Minicockpit OVHD panel.
1 messages · Page 1 of 1 (latest)
Switches that get out of sync is likely caused by momentary button code being used in latching switches.
Please show the code used for those switches.
Hi Jamie it's the eng anti ice switch, it's not a latching switch. What I meant by out of sync is if you operate only one button in the VC then use the ovhd button and there is only 1, it would toggle 1 off and the other ON, that's all it is, it's a toggle function as they are not latching.
I didn't understand what you mean by "and there is only 1". If the button is momentary (non-latching) and the current system (both in VC and physical panel) state is ON, then pressing the button will turn the system OFF. Are you saying that is not what happens?
If the button is non-latching, it can't get out of sync becausse there is no state attached to its current position (like a latching switch would have)
On the mini overhead, there is only one switch where in the VC there are 2 independent switches, so if in the VC you press only 1 of them, when you then use the button on the mini ovhd, it toggles 1 OFF and the other ON which is why I mentioned the retrigger which follows the condition of eng 2 anti ice.
ahhh that is a different issue, you are trying to control two systems with one switch using only toggle events.
ok, so if one system is on and the other off, what do you want the physical button to do?
I guess there are three options, one, toggle each system separately (which is what is happening now). Two, if sys A is ON and B is Off, turn both ON (toggle based on B state). And three, if Sys A is ON and B is Off, turn both OFF (toggle based on A state).
All I'd like is for them to be in synch which is what the retrigger is doing for me, I don't have the knowledge to do it in other ways to sync via the button. Let me force my system back inline with everybody else on the 10.5.3.15 then I'll come back to this. Meanwhile it's been excepted on flightsim.to. 10.5.3.16 now installed. Problem: this 10.5.3.16 refuses to run, no messages or anything, doesn't display and not hidden behind any other windows nor is it on the taskbar as a running app but it's showing in task manager.
are you on FBW A320 DEV?
the mfproj file seems to contain both new and older code for Eng1 Anti Ice toggle
why is it bound to the on release action instead of on press? do you know?
Yes, dev version
Press condition is when the button is not pressed.
The codes should be for dev version so whatever they were, there are lots of duplications for various functions even on dev and some don't work, the format for both engines is the same just with the required reference to which engine, I have MF back running again, the mobiflight process was still shown as running in the task manager so killed that off.
as you can see here, they show press, this is without them being pressed.
wait, you mean the minioverhead buttons are wired as normally closed buttons? So when you press them, they actually open the contact?
that is a crazy way to complicate things IMHO
that would explain why the profile buttons are configured as on release instead of on press
here is the current code in the A32nx for anti ice engine 1
It confused me at first whehn I saw the Press was when in their normal state and is why I set up as when released. Yes thats the code I'm using that you show above.
(L:A32NX_BUTTON_OVHD_ANTI_ICE_ENG_1_POSITION, Bool) ! (>L:A32NX_BUTTON_OVHD_ANTI_ICE_ENG_1_POSITION, Bool)
(L:XMLVAR_Momentary_PUSH_OVHD_ANTIICE_ENG1_Pressed) ! (>L:XMLVAR_Momentary_PUSH_OVHD_ANTIICE_ENG1_Pressed)
(L:A32NX_BUTTON_OVHD_ANTI_ICE_ENG_2_POSITION, Bool) ! (>L:A32NX_BUTTON_OVHD_ANTI_ICE_ENG_2_POSITION, Bool)
(L:XMLVAR_Momentary_PUSH_OVHD_ANTIICE_ENG2_Pressed) ! (>L:XMLVAR_Momentary_PUSH_OVHD_ANTIICE_ENG2_Pressed)
This is eng1 & 2 combined
ok, but this code will just toggle the state whatever it is for both, regardless of what the current state is.
if one is on and the other is off, then it toggles it that way too
yep, that's where the sync issue is if you use either of the VC buttons on their own
ok, you need to introduce a check for the state, so that pressing the button will sync if not in sync
you can take Eng1 to be the master and Eng 2 to be the slave system
I thought there might be a precondition but I don't know whow to use them.
Eng 2 seems to be the master if you use retrigger
it is whatever we want it to be
try this
(L:A32NX_BUTTON_OVHD_ANTI_ICE_ENG_1_POSITION, Bool) ! s0 (>L:A32NX_BUTTON_OVHD_ANTI_ICE_ENG_1_POSITION, Bool)
l0 (>L:XMLVAR_Momentary_PUSH_OVHD_ANTIICE_ENG1_Pressed)
l0 (>L:A32NX_BUTTON_OVHD_ANTI_ICE_ENG_2_POSITION, Bool)
l0 (>L:XMLVAR_Momentary_PUSH_OVHD_ANTIICE_ENG2_Pressed)
I'll duplicate then turn the original OFF.
ok testing 🙂
Ok, that's with eng 2 as master
Thanks you so much Jamie, I'd better update flightsim.to
could you explain how it works, I did a little rpn 50 yrs ago and I do follow some things ok. I've not noticed the l displayed like that before where it's l0
It simpler than I originally thought
We use the first Lvar for ENG1 as the master toggle and sync all other three Lvars to this value.
So no matter if the state is different, after executing, all four variables will be in sync.
s0 stores the fist Lvar toggled state
l0 reloads this value back to store in all the other Lvars
it's syncing to eng 2
its one way of looking at it. It is actually toggling Eng1 antiice and then syncing to that toggled state.
It's working anyway, I was trying to find it in the MF docs about it
finding what about it?
Just to read about how it's used
for RPN read the guide in the msfs sdk website
I know the basic maths part, I built a calculater when I was at college and that used rpn
Sorry no. Should I?
it was his calculators that I built.
I was in engineering school in the mid 70s
He was a designer, made computers, calculators, the C5
ohh ok, the Sinclair computer