zetato

@Lorby_SI Good news! Using your suggestions I found the two wipers knob were setting the relevant switch in close position and they were the only two closed at the loading of the plane in the sim. I removed the binding and now the heaters are working perfectly! Thank you very much once more! Mauro

Understood, thank you, I check if I can solve in some way waiting for a future release of Lorby! Mauro

Do you mean all the switches binded on the Bodnar Card? Or all the erratic Heaters switches? In the first case I'm not sure i can, I have three Bodnar Cards with more than 60 switches of different types.. The heaters switches are always off at the beginning of the flight, some other probably not... Mauro

I tried both the suggestions of you previous post, but nothing changes... I tried also with the virtual keyboard, but I'm struggling... My swithes are conneted to a Leo Bodnar BU0836X card, Lorby recognise it and when I add the button it is correctly shown in the "press button/key" box, but then I click in the "virtual event" box, choose for exemple NumPad3, click close and in the "Press button/key" box the switch number is disappeared replaced by NumPad3, so if I click ADD, only NumPad3 appears in the Assigned Button list and the switch does not work.. At the present only the NumPad4 has worked correctly, binded on my BU0836 Interface Button 12, no luck with NumPad1,2 and 3... So strange... Mauro

@Lorby_SI Tis is an exemple of what is coded inside the XML file of the model for the switch of heater number 1: <Component id="VC_Window_Heat_Switch_1_SW_Obj_01" NODE="VC_Window_Heat_Switch_1_SW_Obj_01"> <UseTemplate Name="ASOBO_GT_Anim_Code"> <ANIM_NAME>VC_Window_Heat_Switch_1_SW</ANIM_NAME> <ANIM_LENGTH>10</ANIM_LENGTH> <ANIM_CODE> (L:VC_Window_Heat_1_SW_VAL,number) </ANIM_CODE> <ANIM_LAG>81</ANIM_LAG> </UseTemplate> <UseTemplate Name="ASOBO_GT_MouseRect"> <CURSOR>Hand</CURSOR> <TOOLTIPID>WINDOW HEAT Switches</TOOLTIPID> <MOUSEFLAGS>LeftSingle+RightSingle+WheelUp+WheelDown</MOUSEFLAGS> <CallbackCode> (M:Event) 'LeftSingle' scmp 0 == if{ 81 (>L:VC_Anti_Ice_trigger_VAL,number) } (M:Event) 'RightSingle' scmp 0 == if{ 0 (>L:VC_Anti_Ice_trigger_VAL,number) } (M:Event) 'WheelUp' scmp 0 == if{ 7 (>L:VC_Anti_Ice_trigger_VAL,number) } (M:Event) 'WheelDown' scmp 0 == if{ 8 (>L:VC_Anti_Ice_trigger_VAL,number) } </CallbackCode> </UseTemplate> </Component> Mauro

@Lorby_SIThanks for interesting, those are the sequence provided in the script I found, but I tried extracting others variable from the file xml of the model with the same result. (L:VC_Window_Heat_1_SW_VAL,·Number)·0·==·if{·8·(>L:VC_Anti_Ice_trigger_VAL,·Number)·}·els{·7·(>L:VC_Anti_Ice_trigger_VAL,·Number)·} (L:VC_Window_Heat_2_SW_VAL,·Number)·0·==·if{·10·(>L:VC_Anti_Ice_trigger_VAL,·Number)·}·els{·9·(>L:VC_Anti_Ice_trigger_VAL,·Number)·} (L:VC_Window_Heat_3_SW_VAL,·Number)·0·==·if{·12·(>L:VC_Anti_Ice_trigger_VAL,·Number)·}·els{·11·(>L:VC_Anti_Ice_trigger_VAL,·Number)·} (L:VC_Window_Heat_4_SW_VAL,·Number)·0·==·if{·14·(>L:VC_Anti_Ice_trigger_VAL,·Number)·}·els{·13·(>L:VC_Anti_Ice_trigger_VAL,·Number)·} I tried also this: (L:VC_Window_Heat_1_SW_VAL,·Number)·0·==·if{·8·(>L:VC_Anti_Ice_trigger_VAL,·Number)·(WAIT:200|300)·10·(>L:VC_Anti_Ice_trigger_VAL,·Number)·(WAIT:200|300)·12·(>L:VC_Anti_Ice_trigger_VAL,·Number)·(WAIT:200|300)·14·(>L:VC_Anti_Ice_trigger_VAL,·Number)·}·els{·7·(>L:VC_Anti_Ice_trigger_VAL,·Number)·(WAIT:200|300)·9·(>L:VC_Anti_Ice_trigger_VAL,·Number)·(WAIT:200|300)·11·(>L:VC_Anti_Ice_trigger_VAL,·Number)·(WAIT:200|300)·13·(>L:VC_Anti_Ice_trigger_VAL,·Number)·} on a single switch, but also in this way the heaters are working almosta casually, sometime all together, other times only one or two etc. P.S. binding the command on keybord buttons using Ifly plugin function seems to work well, but I have dedicated switch on my panel and I would like to use it... Mauro

Ty anyway, really I don't know what's happening and why only in the A/ICE section. Mauro

Hi, yes, they are and they were working well for many days. Now I Have for exemple "script:iFly737MAX-AICE Window Heat 1 TOGGLE" the relative variable is (L:VC_Window_Heat_1_SW_VAL, Number) 0 == if{ 8 (>L:VC_Anti_Ice_trigger_VAL, Number) } els{ 7 (>L:VC_Anti_Ice_trigger_VAL, Number) The others 3 windows heaters are the same with different numbers. Closing the switch should activate the heater, opening the switch should deactivate it, In the last days some times it works sometimes no, I mean, turing on all the four switches, maybe the one stays off and the others goes on or viceversa, totally casually, and the same turning them off. Mauro

@Lorby_SI Hello again, I'm really happy with my setup, but over the last two days, something strange has happened: The entire heater section, and only that one, on the iFly B737 Max 8 model has started responding erratically to controls. I've mapped the toggle controls to my switches for the window heaters, probe heaters, and engine/wing de-icing. Over the last two days, I've noticed that often moving my switches has no effect in the cockpit. Perhaps a second movement of the same switch does, but not always and completely randomly... Everything else in the cockpit works perfectly. I've already removed and reinstalled the model, updated lorby, and reimported my scripts and models, but to no avail... It seems something between lorby and the model, on lorbly green leds are responding correctly, but often on the model some actions are missed, only in the Anti/Deice section.. Any ideas? Thanks. Mauro

I don't know how to thank you. I tried a thousand different ways, and the solution was right there, but without your help, I never would have found it. Everything works now, thank you so much!! Mauro

Thank you, I tried but remain exatly the same, 100 on MCP Vs 194 on Combo and so on... Soory, I don't want to bore you, Mauro

Update: using "add lvar for ifly" I found this variable (L:add_iFly_spd_value) I changed in my VRI Bridge Display Editor (Speed section) the coding from %(A:AUTOPILOT AIRSPEED LOCK VAR, knots)%!03d! in %(L:add_iFly_spd_value, knots)%!03d! and now the COMBO is retrieving a value, but this value seems to be shown in m/s and not in knots... In fact when the aircraft MCP shows 100 (minimum value) on my COMBO display I read 194, for 250 I read 486 and so on. With the help of AI I tried to compile a conversion eg. %((L:add_iFly_spd_value) 1.943844 *, int)%!03d! , but no luck. Keep triyng, but I'm short of ideas. Mauro

Thank you very much! Mauro

@Lorby_SI You were very kind in helping me with the CRS solution, so I'd like to take this opportunity to ask you if you can figure out why, in the instructions below (these are the instructions used via the appropriate editor to specify which values to display on the MCP COMBO II display), everything works except for the airspeed, which is received by the simulator when I rotate the encoder, but the value doesn't appear on the COMBO display. Thanks again. %(A:AUTOPILOT FLIGHT DIRECTOR ACTIVE, Bool) 1 ==%{if}FD{else} {end} %(A:AUTOPILOT AIRSPEED LOCK VAR, knots)%!03d! QNH %(A:Kohlsman setting mb, Millibars)%!04d! %(A:AUTOPILOT HEADING LOCK DIR, degrees)%!03d! %(A:AUTOPILOT ALTITUDE LOCK VAR, feet)%!05d! %(A:AUTOPILOT VERTICAL HOLD VAR, feet/minute)%!+04d! Mauro

Thank man, it works!! I tried something similar before but I was wrong in the syntax!! Thank you very much!! Mauro