TERR ON ND

[elledejonge]

Is there a suport key/switch for the TERR ON ND switch. Cannot find it in the list connected to Mobiflight / FSUIPC. I saw some other post here about it, but they where all before MSFS2020 

[John Dowson]

56 minutes ago, elledejonge said:

Is there a suport key/switch for the TERR ON ND switch.

Do you mean to ask if there is a control/event to control the TERR ON ND switch? For which aircraft? A320 I presume, but it really helps if you can give more information when requesting support.... And do you mean an MSFS control or a MobiFlight one?

All MSFS controls are listed in the controls document that you will find in your FSUIPC documents folder.
For MobiFlight events, you need to ask MobiFlight, or download the latest release and take a look at their events file.

For the A320, there is the lvar BTN_TERRONND_ACTIVE

Of course, you can't use that directly using FSUIPC7 at the moment. Lvar support is still a few weeks away, although I hope to be releasing the FSUIPC WASM module for beta testing in the next few days.

[elledejonge]

all your questions are right. Its a A320 and i am using Mobiflight to controle the button, but with FSUIPC as input.

I will check the documentation, but i understand the LVAR command must still be implemented so i have to wait a moment.

Thxs for the quick response

next time i will try to be more accurate within the question 🙂 

[MarkStallen]

Put in mobiflight events.txt : A320_Neo_MFD_BTN_TERRONND_1#(>H:A320_Neo_MFD_BTN_TERRONND_1)

and add A320_Neo_MFD_BTN_TERRONND_1 to your xxxx.evt

[John Dowson]

1 hour ago, MarkStallen said:

Put in mobiflight events.txt : A320_Neo_MFD_BTN_TERRONND_1#(>H:A320_Neo_MFD_BTN_TERRONND_1)

and add A320_Neo_MFD_BTN_TERRONND to your xxxx.evt

Thats interesting! Is this a general way to set lvars using MobiFlight events? Or does the hvar (in this case H:A320_Neo_MFD_BTN_TERRONND_1) also have to exist?
I'm not sure on the relationship between lvars and hvars...

Also,  do you have a list of available hvars, for the A320 or any other aircraft?

[MarkStallen]

Here they are :

MSFS2020 - MobiFlight WASM Events - Google Spreadsheets

for instance in events.txt in the community/mobiflight-event-module/modules:

XMLVAR_Autobrakes_Level_MED#2 (>L:XMLVAR_Autobrakes_Level)

A320_Neo_PFD_BTN_LS_1#(>H:A320_Neo_PFD_BTN_LS_1)

in the evt-file call them with :

XMLVAR_Autobrakes_Level_MED

A320_Neo_PFD_BTN_LS_1

It's not possible to give a parameter by yourself. I'm using custom offsets to keep up.

If you open op the aircraft behaviours in the developermode. Then you can find all LVars and Hvars used and put them in the events.txt and xxxx.evt als described above. Everything is now working on my DIY cockpit. All buttons, switches and roterary's. Lights like LDG gear and Auto brk etc. I programmed via Visual Basic and FSUIPC. 

 

[asessa]

On 3/3/2021 at 3:45 PM, MarkStallen said:

Here they are :

MSFS2020 - MobiFlight WASM Events - Google Spreadsheets

for instance in events.txt in the community/mobiflight-event-module/modules:

XMLVAR_Autobrakes_Level_MED#2 (>L:XMLVAR_Autobrakes_Level)

A320_Neo_PFD_BTN_LS_1#(>H:A320_Neo_PFD_BTN_LS_1)

in the evt-file call them with :

XMLVAR_Autobrakes_Level_MED

A320_Neo_PFD_BTN_LS_1

It's not possible to give a parameter by yourself. I'm using custom offsets to keep up.

If you open op the aircraft behaviours in the developermode. Then you can find all LVars and Hvars used and put them in the events.txt and xxxx.evt als described above. Everything is now working on my DIY cockpit. All buttons, switches and roterary's. Lights like LDG gear and Auto brk etc. I programmed via Visual Basic and FSUIPC. 

 

Hi Marks, i'm using the XMLVAR_Autobrakes_Level_xxx with MF and my Autobrake Panel and A320Nx Custom AP+FBW but :

XMLVAR_Autobrakes_Level_MED activates the LOW button

XMLVAR_Autobrakes_Level_MAX activates the MED button

For MAX i have to use the fsuipc event Autobrake with value of 4.

Can you confirm ?

ps.

Great home cockpit's set! Ho do you popup that chronometer texture?

And Do you know a method to save all popuped windows so i haven't to popup they at every flights?

 

[MarkStallen]

The chronometer and the landinggear and brake lights coming from a Visual Basic Program working with FSUIPC.

Be sure that in your events.txt contains :

XMLVAR_Autobrakes_Level_OFF#0 (>L:XMLVAR_Autobrakes_Level)
XMLVAR_Autobrakes_Level_LOW#1 (>L:XMLVAR_Autobrakes_Level)
XMLVAR_Autobrakes_Level_MED#2 (>L:XMLVAR_Autobrakes_Level)
XMLVAR_Autobrakes_Level_MAX#3 (>L:XMLVAR_Autobrakes_Level)

Then it works. (You can't give a parameter, but you have to use all the commands seperate)

[MarkStallen]

For the pop-outs I use Window Title changer and Win Layout manager. When I start-up I have to pop-out the panels all together after that pop-out apart and give them a name (1,2, 3--6) with Title changer. Then in lay-outmager I saved those names with their position and size so I can run that preset. Costs about one minut.

[asessa]

17 minutes ago, MarkStallen said:

For the pop-outs I use Window Title changer and Win Layout manager. When I start-up I have to pop-out the panels all together after that pop-out apart and give them a name (1,2, 3--6) with Title changer. Then in lay-outmager I saved those names with their position and size so I can run that preset. Costs about one minut.

Thanks , i will try 

[asessa]

30 minutes ago, MarkStallen said:

The chronometer and the landinggear and brake lights coming from a Visual Basic Program working with FSUIPC.

Be sure that in your events.txt contains :

XMLVAR_Autobrakes_Level_OFF#0 (>L:XMLVAR_Autobrakes_Level)
XMLVAR_Autobrakes_Level_LOW#1 (>L:XMLVAR_Autobrakes_Level)
XMLVAR_Autobrakes_Level_MED#2 (>L:XMLVAR_Autobrakes_Level)
XMLVAR_Autobrakes_Level_MAX#3 (>L:XMLVAR_Autobrakes_Level)

Then it works. (You can't give a parameter, but you have to use all the commands seperate)

Ok, i will try 

Thanks

[asessa]

11 hours ago, asessa said:

Ok, i will try 

Thanks

Ok works.

But now i lost fsuipc offset...to light on leds on the my pushbuttons

[MarkStallen]

I made an custom offset to trigger the lights (66D0). In my ini file like this :

If this offset was the same as before then I set it to 4 and in the and back to zero (so you can push your autobrake settings on and off by pushing it twice.

P258,23 and U258,23 is my MAX-button (with press and release I do the same) and P(U)258,22 is my MED and P(U)258,23 my LO

217=B66D0=3 P258,23,Cx010066D0,x04     -{offset byte set, offset 66D0}-
218=B66D0=2 P258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
219=B66D0=1 P258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
220=B66D0=0 P258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
221=B66D0=3 U258,23,Cx010066D0,x04     -{offset byte set, offset 66D0}-
222=B66D0=2 U258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
223=B66D0=1 U258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
224=B66D0=0 U258,23,Cx010066D0,x03     -{offset byte set, offset 66D0}-
225=B66D0=3 P258,23,C32805,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_MAX}-
226=B66D0=3 U258,23,C32805,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_MAX}-
227=B66D0=4 P258,23,C32802,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}-
228=B66D0=4 U258,23,C32802,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}-
229=B66D0=4 P258,23,Cx010066D0,x00     -{offset byte set, offset 66D0}-
230=B66D0=4 U258,23,Cx010066D0,x00     -{offset byte set, offset 66D0}-
231=B66D0=2 P258,22,Cx010066D0,x04     -{offset byte set, offset 66D0}-
232=B66D0=3 P258,22,Cx010066D0,x02     -{offset byte set, offset 66D0}-
233=B66D0=1 P258,22,Cx010066D0,x02     -{offset byte set, offset 66D0}-
234=B66D0=0 P258,22,Cx010066D0,x02     -{offset byte set, offset 66D0}-
235=B66D0=2 U258,22,Cx010066D0,x04     -{offset byte set, offset 66D0}-
236=B66D0=3 U258,22,Cx010066D0,x02     -{offset byte set, offset 66D0}-
237=B66D0=1 U258,22,Cx010066D0,x02     -{offset byte set, offset 66D0}-
238=B66D0=0 U258,22,Cx010066D0,x02     -{offset byte set, offset 66D0}-
239=B66D0=2 P258,22,C32804,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_MED}-
240=B66D0=2 U258,22,C32804,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_MED}-
241=B66D0=4 P258,22,C32802,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}-
242=B66D0=4 U258,22,C32802,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}-
243=B66D0=4 P258,22,Cx010066D0,x00     -{offset byte set, offset 66D0}-
244=B66D0=4 U258,22,Cx010066D0,x00     -{offset byte set, offset 66D0}-
245=B66D0=1 P258,21,Cx010066D0,x04     -{offset byte set, offset 66D0}-
246=B66D0=3 P258,21,Cx010066D0,x01     -{offset byte set, offset 66D0}-
247=B66D0=2 P258,21,Cx010066D0,x01     -{offset byte set, offset 66D0}-
248=B66D0=0 P258,21,Cx010066D0,x01     -{offset byte set, offset 66D0}-
249=B66D0=1 U258,21,Cx010066D0,x04     -{offset byte set, offset 66D0}-
250=B66D0=3 U258,21,Cx010066D0,x01     -{offset byte set, offset 66D0}-
251=B66D0=2 U258,21,Cx010066D0,x01     -{offset byte set, offset 66D0}-
252=B66D0=0 U258,21,Cx010066D0,x01     -{offset byte set, offset 66D0}-
253=B66D0=1 P258,21,C32803,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_LOW}-
254=B66D0=1 U258,21,C32803,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_LOW}-
255=B66D0=4 P258,21,C32802,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}-
256=B66D0=4 U258,21,C32802,0     -{:MobiFlight.XMLVAR_Autobrakes_Level_OFF}-
257=B66D0=4 P258,21,Cx010066D0,x00     -{offset byte set, offset 66D0}-
258=B66D0=4 U258,21,Cx010066D0,x00     -{offset byte set, offset 66D0}-

[MarkStallen]

What I also found is that setting the autobrake you push offset 02F8 from 1 to 0. Only then it works. After T/O and gear up this one is going back to 1. In that case you have to switch your custom offset  back to 0 so that your lights go off. So I added also this offset (see 300-311).

Now there's a problem. As soon as you hit your brakes 02F8 goes also to 1. As a solution I programmed in the ini that as I release my brakes 02F8 goes back to 0 (see 313 and 315)

300=B66D0>0 P258,21,Cx01002F80,x00     -{offset byte set, offset 2F80}-
301=B66D0=0 P258,21,Cx01002F80,x01     -{offset byte set, offset 2F80}-
302=B66D0>0 U258,21,Cx01002F80,x00     -{offset byte set, offset 2F80}-
303=B66D0=0 U258,21,Cx01002F80,x01     -{offset byte set, offset 2F80}-
304=B66D0>0 P258,22,Cx01002F80,x00     -{offset byte set, offset 2F80}-
305=B66D0=0 P258,22,Cx01002F80,x01     -{offset byte set, offset 2F80}-
306=B66D0>0 U258,22,Cx01002F80,x00     -{offset byte set, offset 2F80}-
307=B66D0=0 U258,22,Cx01002F80,x01     -{offset byte set, offset 2F80}-
308=B66D0>0 P258,23,Cx01002F80,x00     -{offset byte set, offset 2F80}-
309=B66D0=0 P258,23,Cx01002F80,x01     -{offset byte set, offset 2F80}-
310=B66D0>0 U258,23,Cx01002F80,x00     -{offset byte set, offset 2F80}-
311=B66D0=0 U258,23,Cx01002F80,x01     -{offset byte set, offset 2F80}-
313=PA,1,Cx01002F80,x00     -{offset byte set, offset 2F80}-
315=UA,1,Cx01002F80,x00     -{offset byte set, offset 2F80}-

[asessa]

You mean in the fsuipc ini file?

[MarkStallen]

Yes, probably you can also create a lua for it, but I'm not fully proficient on that yet

[asessa]

Ok. We wait for new fsuipc with support for lvars 🙂

[MarkStallen]

My first try with a LUA :

in the ini file :

225=P258,23,CL4:R,3
226=U258,23,CL4:R,3
227=P258,22,CL4:R,2
228=U258,22,CL4:R,2
229=P258,21,CL4:R,1
230=U258,21,CL4:R,1

[LuaFiles]
1=ipcReady
2=LINDA
3=Geluid
4=Autobrake

Lua autobrake : 

LastAutoBrakePos = ipc.readUB("66D0")
if ipcPARAM = LastAutoBrakePos then
    ipc.writeUB("02F8",1)
    ipc.writeUB("66D0",0)
    ipc.control(32802)
elseif ipcPARAM = 1 then
    ipc.writeUB("02F8",0)
    ipc.writeUB("66D0",1)
    ipc.control(32803)
elseif ipcPARAM = 2 then
    ipc.writeUB("02F8",0)
    ipc.writeUB("66D0",2)
    ipc.control(32804)
elseif ipcPARAM = 3 then
    ipc.writeUB("02F8",0)
    ipc.writeUB("66D0",3)
    ipc.control(32805)
end

 

[MarkStallen]

Eureka, this really works. One small change in the LUA :

LastAutoBrakePos = ipc.readUB("66D0")
if ipcPARAM == LastAutoBrakePos then
    ipc.writeUB("2F80",1)
    ipc.writeUB("66D0",0)
    ipc.control(32802)
elseif ipcPARAM == 1 then
    ipc.writeUB("2F80",0)
    ipc.writeUB("66D0",1)
    ipc.control(32803)
elseif ipcPARAM == 2 teen
    ipc.writeUB("2F80",0)
    ipc.writeUB("66D0",2)
    ipc.control(32804)
elseif ipcPARAM == 3 then
    ipc.writeUB("2F80",0)
    ipc.writeUB("66D0",3)
    ipc.control(32805)
end

[John Dowson]

One small thing...you don't need to, and shouldn't, edit or change the [LuaFiles] section in the FSUIPC ini file. This is auto-generated and managed by FSUIPC. You can get into issues if you manually change this section, so best not to. If you drop in a new lua, better to restart FSUIPC to get this added, or maybe one of the reload functions (from button/axes assignments dialog) will do this, not sure without checking.