MobiFlight Community Support

I found that L:TransmitterSelectorKnobPos does not work in Mobiflight. (A2A Piper Cherokee)
L:AudioSensSwitch=SET Works great in Leo Bodnar board and in Mobiflight.
L:AudioLampTestSwitch=SET Works great in Leo Bodnar board and in Mobiflight.
L:AudioCom1SpkSwitch=SET Works great in Leo Bodnar board and in Mobiflight.
L:AudioCom2SpkSwitch=SET Works great in Leo Bodnar board and in Mobiflight.
L:AudioNav1SpkSwitch=SET Works great in Leo Bodnar board and in Mobiflight.
L:AudioNav2SpkSwitch=SET Works great in Leo Bodnar board and in Mobiflight.
L:AudioMkrSpkSwitch=SET Works great in Leo Bodnar board and in Mobiflight.
L:AudioAdf1SpkSwitch=SET Works great in Leo Bodnar board and in Mobiflight.
L:AudioDMESpkSwitch=SET Works great in Leo Bodnar board and in Mobiflight.
L:AudioAutoSpkSwitch=SET Works great in Leo Bodnar board and in Mobiflight.
L:TransmitterSelectorKnobPos Works great in Leo Bodnar board BUT NOT in Mobiflight.
Thanks in advance,
vangyver

Sorry.
Not understand the basic problem!

Technical a Bodnar do nothing else like MF ..... it send a Command or better a Joystick Aktion that finally is set to a command.

You need to explane more detailed where the problem is....

A2A ? Do you use a LUA Script ? If yes.... Check how the script work.... And how you emulate the MF Action to it.
Pretty sure the Bodnar is seen as a Joystick Button. If MF is seen as a Offset Status then this can be the problem.
So check your Code !

I use a macro file placed in the module folder which is accessed by FSUIPC. I also use a Leo Bodnar BU0836X. I use on – off switches.
Runnig Prepar3d
My macro file: 1Piper Cherokee.mcro
[MACROS]
1=L:Eng1_StarterSwitch=SET
2=L:Battery1Switch=Set
3=L:BeaconLightSwitch=SET
4=L:BeaconLightSwitch=SET
5=L:NavinstrLightSwitch=SET
6=L:FSelCherokeeState=Set
7=L:Com2InnerKnobPull=TOGGLE
8=L:Com1OnOff=SET
9=L:Com1InnerKnobPull=TOGGLE
10=L:Nav1PullIdent=SET
11=L:Com2InnerKnobPull=TOGGLE
12=L:Com2OnOff=SET
13=L:Nav2PullIdent=SET
14=L:AdfAdfButton=TOGGLE
15=L:AdfBfoButton=TOGGLE
16= L:AdfFrqButton=TOGGLE
17=L:AdfFrqEtButton=TOGGLE
18=L:AdfFrqRstButton=TOGGLE
19=L:AdfOnOffKnob=SET
20=L:ADFFreqOuterKnob=INC
21=L:ADFFreqOuterKnob=DEC
22=L:AdFFreqInnerKnob=INC
23=L:AdFFreqInnerKnob=DEC
24=L:AdFFreqInnerKnobPull=TOGGLE
25=L:kn62OnOff=SET
26=L:kn62Function=SET
27=L:XpdrIdentSwitch=TOGGLE
28=L:XpdrModeKnobPos=Set
29=L:ApMaster=SET
30=L:GpsNavSelector=SET
31=L:ApModeYokeSwitch=TOGGLE
32=L:ApAltSwitch=TOGGLE
33=L:ApDisconnectSwitch=TOGGLE
34=L:AttitudePlane=INC
35=L:AttitudePlane=DEC
36=L:AudioSensSwitch=SET
37=L:AudioLampTestSwitch=SET
38=L:AudioCom1SpkSwitch=SET
39=L:AudioCom2SpkSwitch=SET
40=L:AudioNav1SpkSwitch=SET
41=L:AudioNav2SpkSwitch=SET
42=L:AudioMkrSpkSwitch=SET
43=L:AudioAdf1SpkSwitch=SET
44=L:AudioDMESpkSwitch=SET
45=L:AudioAutoSpkSwitch=SET
46=L:TransmitterSelectorKnobPos=SET

All the above works great with FSUIPC.
However I am running out of connections so therefore using an Arduino with Mobiflight to handle lines 36 to 46. With Mobiflight lines 36 to 45 works great. I Just cannot get line 46 to work. All the above macros are used for the A2A Piper Cherokee aircraft. I have no idea on how to use or get the offset for L:TransmitterSelectorKnobPos=SET.
Thanks for any help you can suggest,
vangyver

The issue is ony one Lvar (L:TransmitterSelectorKnobPos), all other Lvars
working fine. My guess is there may be a limit on L:Var name lengths in
Mobiflight.

I know FSUIPC had a limit of 32 prior to version 5.153 and thereafter was
increased to 64.

Do you use the Mobiflight "LUA Macro" Plug In , to fire these stuff ?

Found the problem when using LVARs. Too many characters.

https://a2asimulations.com/forum/viewtopic.php?f=116&t=73194#p556631

Strange.....

I not know the Code/logic of this tool.
A user build this and send it to Sebastian.
He include it.... But we basically not know how it work.

Techical...... We use THIS interface......

0D70 128 Macros and Lua requests
]For a Macro, the string should begin with up to 16 characters
giving the .MCRO file name (just the name part, not the type),
and then, separated by a ‘:’ character, the macro name within
that file—again, up to 16 characters. Spaces either side of the ‘:’
are optional.

So for my understanding..... the name of the Macro can not be longer then 16 Chars over all.

**************

Summary..... cool if it work. But i not know/understand, WHY it work. For my point of view it should not !

1Piper Cherokee: L:TransmitterSelectorKnobPos Contains 45 characters (space counts as one).
I believe the module name box must be 32 characters or less.

I agree....

The only part i wondering is the discription, that said..

the macro name within
that file—again, up to 16 characters

So from this announcment i would think that " L:TransmitterSelectorKnobPos" contains 28 Chars .... Means the "second Part" from the string is longer then 16 !

May the Discription is wrong.... So it must be called "MacroName AND Function Name must have "together" max of 32 Chars." So e.g. a 5 Char Macro name would allow a 31Char Function Name . ??

*****
Whatever.... It work for You. Problem Solved !