MarkStallen

I've found two new A320NX events that work : 33=MobiFlight.A320_Neo_MFD_BTN_TERRONND_1 34=MobiFlight.A320_Neo_PFD_BTN_LS_1 (this one instead of 34=MobiFlight.A320_Neo_MFD_BTN_LS_1) Add them in your xxxx.evt in the FSUIPC dir. and your events.txt in your mobiflight WASM module

After a thousand tries I've the APPR and LOC -mode on the A320NX FBW working. My fsuipc.ini : For the LOC-Mode : 63=B0800=1 P258,1,C32785,0 -{:MobiFlight.A320NX_AUTOPILOT_LOC_MODE}- 64=B0800=0 P258,1,C32785,1 -{:MobiFlight.A320NX_AUTOPILOT_LOC_MODE}- 65=B0800=1 U258,1,C32785,0 -{:MobiFlight.A320NX_AUTOPILOT_LOC_MODE}- 66=B0800=0 U258,1,C32785,1 -{:MobiFlight.A320NX_AUTOPILOT_LOC_MODE}- 67=P258,1,C65723,0 -{AP_LOC_HOLD}- 68=U258,1,C65723,0 -{AP_LOC_HOLD}- 69=B07FC=1 P258,1,Cx010007FC,x00 -{offset byte set, offset 07FC}- 70=B07FC=1 U258,1,Cx010007FC,x00 -{offset byte set, offset 07FC}- For the APPR-mode: 245=B07FC=0 P257,5,C65806,0 -{AP_APR_HOLD_ON}- 246=B07FC=0 P257,5,C32786,1 -{:MobiFlight.A320NX_AUTOPILOT_APPR_MODE}- 247=B07FC=1 P257,5,C65813,0 -{AP_LOC_HOLD_OFF}- 249=B07FC=1 P257,5,C32786,0 -{:MobiFlight.A320NX_AUTOPILOT_APPR_MODE}- 250=B07FC=0 U257,5,C65806,0 -{AP_APR_HOLD_ON}- 251=B07FC=0 U257,5,C32786,1 -{:MobiFlight.A320NX_AUTOPILOT_APPR_MODE}- 253=B07FC=1 U257,5,C65813,0 -{AP_LOC_HOLD_OFF}- 254=B07FC=1 U257,5,C32786,0 -{:MobiFlight.A320NX_AUTOPILOT_APPR_MODE}- 255=B07FC=1 P257,5,Cx010007FC,x00 -{offset byte set, offset 07FC}- The messages on the PFD and the intercepts are working as advertized. Only on the screen the lights of the buttons won't come on or off. (other separate offsets?)

Is it possible to see the mobiflight event triggered in the console-log when I trigger them via the simulator screen? If I press a control on the screen and it has a common FSUIPC event then it shows up in the console, but if I press a control on the screen with a working mobiflight-event nothing shows up in the console, only if I trigger them via FSUIPC (vrinsight-panel) itself.

Would be very nice. But if you mean by "pushing in the sim" that you select these on the microsoft simulator screen, that works for me too. I was selecting autobrake lo and med via FSUIPC on my vrinsight-panel and I can't get that to work. It works in the vanilla A320 but not with the FBW mod.

I think you're wrong the decel-led is on 0C46 and is boolean. 0260 is a byte with values(0-3). You say that your panel is active after pushing lo or med (lights come on?), but does it also show on your PFD? in my FBW Dev Mod this is not working.

Still not working for me In the Vanilla A320 it works as advertized but in the FBW not. Writing the 2F80 works but only 4 (Max) changes the setting of the A/C. Setting the autobrake off (writing x01 in 2F80) doesn't work either. If I write 1,2,3,4 to 28F0 then FSUIPC writes 0,1,2,3 in offset 0260 (correct?) , so that's usefull for the lights in my homebuild cockpit. I hope in the near future they make this also workable for the FBW A320

How do you set-up Linda to use these Mobiflight events. I can make a lua with functions like : function XXXXXX () ipc.control( xxxxx, p ) end end Is it possible to call the mobiflight events like this?

Yves, we have to wait untill Mobiflight releases these events. After that you can use my entries for the fsuipc.ini file.

Yep Change them in the events.txt and in the .evt files of FSUIPC to : A320_Neo_CDU_1_BTN_UP A320_Neo_CDU_1_BTN_DOWN A320_Neo_CDU_1_BTN_PREVPAGE A320_Neo_CDU_1_BTN_NEXTPAGE

Rename _SLASH with _DIV in the events.txt off the mobiflight WASM module. BTN_0 should also be there. I found this and more on the Discord-Channel of Mobiflight. Updates Will be discussed on this channel

For the NAV_MODE 200=P256,9,Cx510066FF,x00050001 -{offset byte cyclic inc, offset 66FF (Incr=1, Limit=5)}- 201=B66FF=0 P256,9,C32775,0 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 202=B66FF=1 P256,9,C32775,1 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 203=B66FF=2 P256,9,C32775,2 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 204=B66FF=3 P256,9,C32775,3 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 205=B66FF=4 P256,9,C32775,4 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 208=B66FF=5 P256,9,Cx010066FF,x04 -{offset byte set, offset 66FF}- 210=P256,10,Cx610066FF,x00050001 -{offset byte cyclic dec, offset 66FF (Decr=1, Limit=5)}- 211=B66FF=0 P256,10,C32775,0 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 212=B66FF=1 P256,10,C32775,1 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 213=B66FF=2 P256,10,C32775,2 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 214=B66FF=3 P256,10,C32775,3 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 215=B66FF=4 P256,10,C32775,4 -{:MobiFlight.A320_Neo_MFD_NAV_MODE_1}- 218=B66FF=5 P256,10,Cx010066FF,x00 -{offset byte set, offset 66FF}-

This works perfectly 100=P256,11,Cx510066C0,x00070001 -{offset byte cyclic inc, offset 66C0 (Incr=1, Limit=7)}- 101=B66C0=0 P256,11,C32776,0 -{:MobiFlight.A320_neo_MFD_Range_1}- 102=B66C0=1 P256,11,C32776,1 -{:MobiFlight.A320_neo_MFD_Range_1}- 103=B66C0=2 P256,11,C32776,2 -{:MobiFlight.A320_neo_MFD_Range_1}- 104=B66C0=3 P256,11,C32776,3 -{:MobiFlight.A320_neo_MFD_Range_1}- 105=B66C0=4 P256,11,C32776,4 -{:MobiFlight.A320_neo_MFD_Range_1}- 106=B66C0=5 P256,11,C32776,5 -{:MobiFlight.A320_neo_MFD_Range_1}- 107=B66C0=6 P256,11,C32776,6 -{:MobiFlight.A320_neo_MFD_Range_1}- 108=B66C0=7 P256,11,Cx010066C0,x06 -{offset byte set, offset 66C0}- 110=P256,12,Cx610066C0,x00070001 -{offset byte cyclic dec, offset 66C0 (Decr=1, Limit=7)}- 111=B66C0=0 P256,12,C32776,0 -{:MobiFlight.A320_neo_MFD_Range_1}- 112=B66C0=1 P256,12,C32776,1 -{:MobiFlight.A320_neo_MFD_Range_1}- 113=B66C0=2 P256,12,C32776,2 -{:MobiFlight.A320_neo_MFD_Range_1}- 114=B66C0=3 P256,12,C32776,3 -{:MobiFlight.A320_neo_MFD_Range_1}- 115=B66C0=4 P256,12,C32776,4 -{:MobiFlight.A320_neo_MFD_Range_1}- 116=B66C0=5 P256,12,C32776,5 -{:MobiFlight.A320_neo_MFD_Range_1}- 117=B66C0=6 P256,12,C32776,6 -{:MobiFlight.A320_neo_MFD_Range_1}- 118=B66C0=7 P256,12,Cx010066C0,x00 -{offset byte set, offset 66C0}- I made it go up to 7 and if it does go back to 6 or 0 so it doesn't cycle back. I can use the same trick for the NAV_MODE. Now we only have to wait until Mobiflight releases these events

Could this work in the ini? 100=P256,11,Cx510066C0,x00060001 101=B66C0=0 P256,11,C32776,0 102=B66C0=1 P256,11,C32776,1 103=B66C0=2 P256,11,C32776,2 104=B66C0=3 P256,11,C32776,3 105=B66C0=4 P256,11,C32776,4 106=B66C0=5 P256,11,C32776,5 107=B66C0=6 P256,11,C32776,6 110=P256,12,Cx610066C0,x00060001 111=B66C0=0 P256,12,C32776,0 112=B66C0=1 P256,12,C32776,1 113=B66C0=2 P256,12,C32776,2 114=B66C0=3 P256,12,C32776,3 115=B66C0=4 P256,12,C32776,4 116=B66C0=5 P256,12,C32776,5 117=B66C0=6 P256,12,C32776,6

I would like to work ahead and trying to figure out how I can implement some events when they are released. Maybe you can help me to get started, because I tried to understand your advanced quide and tutorials. But I don't know how to start. Must it be done in the ini-file, via a macro or a lua script. For instance : 8=MobiFlight.A320_neo_MFD_Range_1 will be an event with parameters from 0 to 6 I use a vrinsight MCP combo with a rotary-switch for this range turning to the right/and left is in the ini 32=P256,11,C32776,0 -{:MobiFlight.A320_neo_MFD_Range_1}- 33=P256,12,C32776,0 -{:MobiFlight.A320_neo_MFD_Range_1}- Is it true that if i knew the offset (example WXXXX) of the current range setting (0-6) that i could program in the ini something like : 32=WXXXX=0 P256,11,C32776,1 33=WXXXX=1 P256,11,C32776,2 34=WXXXX=2 P256,11,C32776,3 etc XX=WXXXX=5 P256,11,C32776,6 and 36=WXXXX=6 P256,12,C32776,5 37=WXXXX=5 P256,12,C32776,4 38=WXXXX=4 P256,12,C32776,3 etc XX=WXXXX=1 P256,12,C32776,0 Or is there an sollution without knowing the offset. I hope somebody can help me out.

2=MobiFlight.A320_Neo_MFD_BTN_CSTR_13=MobiFlight.A320_Neo_MFD_BTN_WPT_14=MobiFlight.A320_Neo_MFD_BTN_VORD_15=MobiFlight.A320_Neo_MFD_BTN_NDB_16=MobiFlight.A320_Neo_MFD_BTN_ARPT_1 are working Also the CDU-buttons are working. All other no luck yet. Like the mentioned spreadsheet

And offcourse: [Events] 0=MobiFlight.A320_Neo_CDU_2_BTN_DIR 1=MobiFlight.A320_Neo_CDU_2_BTN_PROG 2=MobiFlight.A320_Neo_CDU_2_BTN_PERF 3=MobiFlight.A320_Neo_CDU_2_BTN_INIT 4=MobiFlight.A320_Neo_CDU_2_BTN_DATA 5=MobiFlight.A320_Neo_CDU_2_BTN_FPLN 6=MobiFlight.A320_Neo_CDU_2_BTN_RAD 7=MobiFlight.A320_Neo_CDU_2_BTN_FUEL 8=MobiFlight.A320_Neo_CDU_2_BTN_SEC 9=MobiFlight.A320_Neo_CDU_2_BTN_ATC 10=MobiFlight.A320_Neo_CDU_2_BTN_MENU 11=MobiFlight.A320_Neo_CDU_2_BTN_AIRPORT 12=MobiFlight.A320_Neo_CDU_2_BTN_UARROW 13=MobiFlight.A320_Neo_CDU_2_BTN_DARROW 14=MobiFlight.A320_Neo_CDU_2_BTN_LARROW 15=MobiFlight.A320_Neo_CDU_2_BTN_RARROW 16=MobiFlight.A320_Neo_CDU_2_BTN_L1 17=MobiFlight.A320_Neo_CDU_2_BTN_L2 18=MobiFlight.A320_Neo_CDU_2_BTN_L3 19=MobiFlight.A320_Neo_CDU_2_BTN_L4 20=MobiFlight.A320_Neo_CDU_2_BTN_L5 21=MobiFlight.A320_Neo_CDU_2_BTN_L6 22=MobiFlight.A320_Neo_CDU_2_BTN_R1 23=MobiFlight.A320_Neo_CDU_2_BTN_R2 24=MobiFlight.A320_Neo_CDU_2_BTN_R3 25=MobiFlight.A320_Neo_CDU_2_BTN_R4 26=MobiFlight.A320_Neo_CDU_2_BTN_R5 27=MobiFlight.A320_Neo_CDU_2_BTN_R6 28=MobiFlight.A320_Neo_CDU_2_BTN_A 29=MobiFlight.A320_Neo_CDU_2_BTN_B 30=MobiFlight.A320_Neo_CDU_2_BTN_C 31=MobiFlight.A320_Neo_CDU_2_BTN_D 32=MobiFlight.A320_Neo_CDU_2_BTN_E 33=MobiFlight.A320_Neo_CDU_2_BTN_F 34=MobiFlight.A320_Neo_CDU_2_BTN_G 35=MobiFlight.A320_Neo_CDU_2_BTN_H 36=MobiFlight.A320_Neo_CDU_2_BTN_I 37=MobiFlight.A320_Neo_CDU_2_BTN_J 38=MobiFlight.A320_Neo_CDU_2_BTN_K 39=MobiFlight.A320_Neo_CDU_2_BTN_L 40=MobiFlight.A320_Neo_CDU_2_BTN_M 41=MobiFlight.A320_Neo_CDU_2_BTN_N 42=MobiFlight.A320_Neo_CDU_2_BTN_O 43=MobiFlight.A320_Neo_CDU_2_BTN_P 44=MobiFlight.A320_Neo_CDU_2_BTN_Q 45=MobiFlight.A320_Neo_CDU_2_BTN_R 46=MobiFlight.A320_Neo_CDU_2_BTN_S 47=MobiFlight.A320_Neo_CDU_2_BTN_T 48=MobiFlight.A320_Neo_CDU_2_BTN_U 49=MobiFlight.A320_Neo_CDU_2_BTN_V 50=MobiFlight.A320_Neo_CDU_2_BTN_W 51=MobiFlight.A320_Neo_CDU_2_BTN_X 52=MobiFlight.A320_Neo_CDU_2_BTN_Y 53=MobiFlight.A320_Neo_CDU_2_BTN_Z 54=MobiFlight.A320_Neo_CDU_2_BTN_1 55=MobiFlight.A320_Neo_CDU_2_BTN_2 56=MobiFlight.A320_Neo_CDU_2_BTN_3 57=MobiFlight.A320_Neo_CDU_2_BTN_4 58=MobiFlight.A320_Neo_CDU_2_BTN_5 59=MobiFlight.A320_Neo_CDU_2_BTN_6 60=MobiFlight.A320_Neo_CDU_2_BTN_7 61=MobiFlight.A320_Neo_CDU_2_BTN_8 62=MobiFlight.A320_Neo_CDU_2_BTN_9 63=MobiFlight.A320_Neo_CDU_2_BTN_DOT 64=MobiFlight.A320_Neo_CDU_2_BTN_PLUSMINUS 65=MobiFlight.A320_Neo_CDU_2_BTN_SP 66=MobiFlight.A320_Neo_CDU_2_BTN_SLASH 67=MobiFlight.A320_Neo_CDU_2_BTN_OVFY 68=MobiFlight.A320_Neo_CDU_2_BTN_CLR

And these: [Events] 0=MobiFlight.A320_Neo_CDU_1_BTN_DIR 1=MobiFlight.A320_Neo_CDU_1_BTN_PROG 2=MobiFlight.A320_Neo_CDU_1_BTN_PERF 3=MobiFlight.A320_Neo_CDU_1_BTN_INIT 4=MobiFlight.A320_Neo_CDU_1_BTN_DATA 5=MobiFlight.A320_Neo_CDU_1_BTN_FPLN 6=MobiFlight.A320_Neo_CDU_1_BTN_RAD 7=MobiFlight.A320_Neo_CDU_1_BTN_FUEL 8=MobiFlight.A320_Neo_CDU_1_BTN_SEC 9=MobiFlight.A320_Neo_CDU_1_BTN_ATC 10=MobiFlight.A320_Neo_CDU_1_BTN_MENU 11=MobiFlight.A320_Neo_CDU_1_BTN_AIRPORT 12=MobiFlight.A320_Neo_CDU_1_BTN_UARROW 13=MobiFlight.A320_Neo_CDU_1_BTN_DARROW 14=MobiFlight.A320_Neo_CDU_1_BTN_LARROW 15=MobiFlight.A320_Neo_CDU_1_BTN_RARROW 16=MobiFlight.A320_Neo_CDU_1_BTN_L1 17=MobiFlight.A320_Neo_CDU_1_BTN_L2 18=MobiFlight.A320_Neo_CDU_1_BTN_L3 19=MobiFlight.A320_Neo_CDU_1_BTN_L4 20=MobiFlight.A320_Neo_CDU_1_BTN_L5 21=MobiFlight.A320_Neo_CDU_1_BTN_L6 22=MobiFlight.A320_Neo_CDU_1_BTN_R1 23=MobiFlight.A320_Neo_CDU_1_BTN_R2 24=MobiFlight.A320_Neo_CDU_1_BTN_R3 25=MobiFlight.A320_Neo_CDU_1_BTN_R4 26=MobiFlight.A320_Neo_CDU_1_BTN_R5 27=MobiFlight.A320_Neo_CDU_1_BTN_R6 28=MobiFlight.A320_Neo_CDU_1_BTN_A 29=MobiFlight.A320_Neo_CDU_1_BTN_B 30=MobiFlight.A320_Neo_CDU_1_BTN_C 31=MobiFlight.A320_Neo_CDU_1_BTN_D 32=MobiFlight.A320_Neo_CDU_1_BTN_E 33=MobiFlight.A320_Neo_CDU_1_BTN_F 34=MobiFlight.A320_Neo_CDU_1_BTN_G 35=MobiFlight.A320_Neo_CDU_1_BTN_H 36=MobiFlight.A320_Neo_CDU_1_BTN_I 37=MobiFlight.A320_Neo_CDU_1_BTN_J 38=MobiFlight.A320_Neo_CDU_1_BTN_K 39=MobiFlight.A320_Neo_CDU_1_BTN_L 40=MobiFlight.A320_Neo_CDU_1_BTN_M 41=MobiFlight.A320_Neo_CDU_1_BTN_N 42=MobiFlight.A320_Neo_CDU_1_BTN_O 43=MobiFlight.A320_Neo_CDU_1_BTN_P 44=MobiFlight.A320_Neo_CDU_1_BTN_Q 45=MobiFlight.A320_Neo_CDU_1_BTN_R 46=MobiFlight.A320_Neo_CDU_1_BTN_S 47=MobiFlight.A320_Neo_CDU_1_BTN_T 48=MobiFlight.A320_Neo_CDU_1_BTN_U 49=MobiFlight.A320_Neo_CDU_1_BTN_V 50=MobiFlight.A320_Neo_CDU_1_BTN_W 51=MobiFlight.A320_Neo_CDU_1_BTN_X 52=MobiFlight.A320_Neo_CDU_1_BTN_Y 53=MobiFlight.A320_Neo_CDU_1_BTN_Z 54=MobiFlight.A320_Neo_CDU_1_BTN_1 55=MobiFlight.A320_Neo_CDU_1_BTN_2 56=MobiFlight.A320_Neo_CDU_1_BTN_3 57=MobiFlight.A320_Neo_CDU_1_BTN_4 58=MobiFlight.A320_Neo_CDU_1_BTN_5 59=MobiFlight.A320_Neo_CDU_1_BTN_6 60=MobiFlight.A320_Neo_CDU_1_BTN_7 61=MobiFlight.A320_Neo_CDU_1_BTN_8 62=MobiFlight.A320_Neo_CDU_1_BTN_9 63=MobiFlight.A320_Neo_CDU_1_BTN_DOT 64=MobiFlight.A320_Neo_CDU_1_BTN_PLUSMINUS 65=MobiFlight.A320_Neo_CDU_1_BTN_SP 66=MobiFlight.A320_Neo_CDU_1_BTN_SLASH 67=MobiFlight.A320_Neo_CDU_1_BTN_OVFY 68=MobiFlight.A320_Neo_CDU_1_BTN_CLR

Just found these : (not tested yet) [Events] 0=MobiFlight.XMLVAR_Baro_Selector_HPA_1 1=MobiFlight.A320_Neo_MFD_BTN_LS_1 2=MobiFlight.A320_Neo_MFD_BTN_CSTR_1 3=MobiFlight.A320_Neo_MFD_BTN_WPT_1 4=MobiFlight.A320_Neo_MFD_BTN_VORD_1 5=MobiFlight.A320_Neo_MFD_BTN_NDB_1 6=MobiFlight.A320_Neo_MFD_BTN_ARPT_1 7=MobiFlight.A320_Neo_MFD_NAV_MODE_1 8=MobiFlight.A320_neo_MFD_Range_1 9=MobiFlight.XMLVAR_NAV_AID_SWITCH_L1_State 10=MobiFlight.XMLVAR_NAV_AID_SWITCH_L2_State 11=MobiFlight.AP_MANAGED_SPEED_IN_MACH_TOGGLE 12=MobiFlight.A320_Neo_CDU_MODE_MANAGED_SPEED 13=MobiFlight.A320_Neo_CDU_MODE_SELECTED_SPEED 14=MobiFlight.A320_Neo_CDU_MODE_MANAGED_SPEED 15=MobiFlight.A320_Neo_FCU_MODE_MANAGED_SPEED 16=MobiFlight.A320_Neo_CDU_MODE_SELECTED_SPEED 17=MobiFlight.A32NX_TRK_FPA_MODE_ACTIVE 18=MobiFlight.A320NX_AUTOPILOT_LOC_MODE 19=MobiFlight.A320NX_AUTOPILOT_APPR_MODE 20=MobiFlight.A320_Neo_EXPEDITE_MODE 21=MobiFlight.A320NX_METRIC_ALT_TOGGLE 22=MobiFlight.XMLVAR_Autopilot_Altitude_Increment 23=MobiFlight.XMLVAR_Baro_Selector_HPA_2 24=MobiFlight.A320_Neo_MFD_BTN_LS_2 25=MobiFlight.A320_Neo_MFD_BTN_CSTR_2 26=MobiFlight.A320_Neo_MFD_BTN_WPT_2 27=MobiFlight.A320_Neo_MFD_BTN_VORD_2 28=MobiFlight.A320_Neo_MFD_BTN_NDB_2 29=MobiFlight.A320_Neo_MFD_BTN_ARPT_2 30=MobiFlight.A320_Neo_MFD_NAV_MODE_2 31=MobiFlight.A320_neo_MFD_Range_2 32=MobiFlight.XMLVAR_NAV_AID_SWITCH_R1_State 33=MobiFlight.XMLVAR_NAV_AID_SWITCH_R2_State

I saw we were also discussing this on the flightsimulator forum 😀 small world. Would be so nice if you're able to get this to work.

Can you do the same with the spad.next wasm (make een event-file with the spad.next ID's? You can call the Mobiflight with [Events] 0=MobiFlight.AS1000_PFD_VOL_1_INC 1=MobiFlight.AS1000_PFD_VOL_1_DEC 2=MobiFlight.AS1000_PFD_VOL_2_INC 3=MobiFlight.AS1000_PFD_VOL_2_DEC etc.... That works, but the spad.next has also the ID's for the A320 Neo and the A320 FBW How to call the Spad.next ID's ? 0=??????.A320_NEO_MFD_RANGE_1 etc

That works Thanks

With FSUIPC 3.0.4c I see in the console that EVENT LIGHT_POTENTIOMETER_24_SET is triggered all the time with Param=100. Happens with A320 vanilla and FBW

Yep you're right, it all works in the vanilla A320. So I placed my post bij FBW. (same with your new #defined key's in 7.0.4c) Thanks

DEC = decimal offset It was working before the latest MSFS update. I used the buttons with my vrinsight combo, using LINDA. I'm using your FSUIPC version 7.0.0.4c and the FBW A32NX. I will check to see if it's still working with the vanilla A320. In the console you see the correct offsets when pushing on the buttons in the game. The same offsets I also see when I press the VrInsight buttons, but they make no change..

The offsets for the APP en LOC function on the A320 don't work anymore ? DEC 65806 parameter 0 DEC 65723 parameter 0