@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

41 minutes ago, zetato said:

everything works except for the airspeed,

As I wrote above, the autopilot airspeed lock variable is not used by iFly, it is always 0. I don't know a solution for that. All I could find is the package on flightsim.to that I also mentioned above. This will apparently write the value into an LVar that you can then insert into the display script instead of the AVar. I have no idea if and how that package works though.

Edit: I will look into the iFly SDK and see if I can include an Aircraft Module for the plane in AAO. But that will be in the next version at the earliest.

Edited March 3Mar 3 by Lorby_SI

Thank you very much!

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

38 minutes ago, zetato said:

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

%(L:add_iFly_spd_value, Number) 1.94384 *%!03d!

Edited March 7Mar 7 by Lorby_SI

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

23 minutes ago, zetato said:

100 on MCP Vs 194 on Combo

That is because you are multiplying the value by 1.94.

Why not just use the variable as it is, without a unit and without conversion? LVars usually don't have a unit anyway (=no "Knots", etc. - just "Number")

%(L:add_iFly_spd_value, Number)%!03d!

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

@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

Edited March 11Mar 11 by zetato

9 hours ago, zetato said:

Any ideas?

The events/scripts/variables/whatever that you are using to control those switches are incorrect?

9 hours ago, zetato said:

already removed and reinstalled

Don't ever do that. You could lose all your AAO assignments

Edited March 12Mar 12 by Lorby_SI

16 hours ago, Lorby_SI said:

The events/scripts/variables/whatever that you are using to control those switches are incorrect?

Don't ever do that. You could lose all your AAO assignments

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

 

I imagine that there is interference between the scripts, because they have to use the same LVars. In general, LVars are a bad choice for operating switches. You have to give the internal logic of the aircraft time to see and process the LVars' value, and only after that you can use it again.

Edited March 12Mar 12 by Lorby_SI

26 minutes ago, Lorby_SI said:

I imagine that there is interference between the scripts, because they have to use the same LVars. In general, LVars are a bad choice for operating switches. You have to give the internal logic of the aircraft time to see and process the LVars' value, and only after that you can use it again.

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

Mauro

18 hours ago, zetato said:

The others 3 windows heaters are the same with different numbers.

What does that mean? What exactly is the code of the other scripts? To me this looks like maybe the variables got mixed up. What kind of hardware did you assign them to?

Other than the missing bracket at the end of your code, it is working fine for me. 

Edited March 13Mar 13 by Lorby_SI

 

@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

Edited March 13Mar 13 by zetato