MobiFlight Community Support

Hi.
Hopefully tonight i can do your testings.
Lets talk via Email.... Pretty sure we find a solution... If not we have a good argument for Sebastian to rework that tool.

Hi, thanks a lot. I'll be waiting for your email.

Good News.... I have test it.
Bad News..... All you said is correct and confirmed.

So all my solutions wont work..

The Problem is simple..... Until now nobody need this cause normaly a Radio (Whatever a Multi) not share Xpdr and ADF on same Display....
If you check your PMDG you see the instrument you like to rebuild use VHF1 VHF2 VHF 3 and so on..... But XPDR is a own panel and also ADF.

Basicly your right.... If you like to build this panel then it "should" be possible. BUT. It isnt with current Mobiflight Logic.

I will report this to Sebastian.... Maby its possible to change this. If not i personaly see NO WAY to fix this in a improvisional way at the moment.

Lets wait for his comment.

@ SEBASTIAN : For detailed informations about that cantact me via whatsapp if needed.

Well, the situation is clear. It's a pity but not the end of the world . Still it would be nice if it can be addressed in the future versions of MobiFlight which is a great tool; thanks for your effort!

Still it would be nice if it can be addressed in the future versions of MobiFlight

I Think so.... We talked last week about a basic rework of the Max7219 GUI ( Maby a Placeholder System like in LCD) .
But please plan for a longer waiting time. There exist some other more prior ideas Sebastian like to implement.

Finaly i can´t garantee if this come. If it need a deeper rework of the code he maby decide to cancel this idea. Just note that this is verry specific and not needed in 98% of Situations. So Priority is still low.

Thank You !

OK, fine. Thanks!

Hi. OK, after XPDR failure I've tried your solution with ADF- it works! Two configs for COM (NAV will follow), one with three inner digits and the second with the outer two, transform "$%10+10" for the outer digits and bingo! Now I have COM, NAV and ADF on one display . It's just important not to forget to remove transform "$+10000" for the COM three inner digits.
So there is just an XPDR that doesn't work but I can live with it. Thanks again for your great support!

Believe it or not, but I've made it for XPDR as well- MobiFlight flexibilty is unbeleivable! So- two configs for XPDR. The first is for the inner three digits: the problem was that with XPDR code less than 1000 the digits had to be shifted right by one digit. So I've made a compare: if the value is >=1000 set it to $, else set it to ($-$%10)/10- first making the last digit always zero by distracting the current last digit's value, then shifting right by dividing by 10 with left padding set to zero. The config for the outer two digits is with transform $%10, so that only the rightmost digit of the code is used and left padding is set to "space" so the leftmost (fifth) digit is blanked. That's it. Thanks again for your great ideas and for MobiFlight!

Hi again.

Thanks for the good news.
As you said.... Mobiflight (and specialy the transform field) is verry deep. Whatever this is basicly a issue that we can not run a Display with different configs and digit numbers..... But normaly we can find a way to fix this with a good logic.
But summary splitting a Com1 into 2 Configs just to prevent the issue is NOT a good solution.... Its just Improvisional to take care about the other problem.

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

By the way. Today Sebastian send me the first Beta Version of a new tool. Will test it the next days. Whatever this Beta also not fix the Diggit Logic Problem, it will be verry helpfulll in your case.
If it work fine then we can pretty sure handle your Problem finaly with ONE Config for each Element... So splitting is no longer needed.

Please stay patient......
Thanks !

Hi again. Great; of course if this issue can be handled so that config splitting is not needed- that would be nice. However already now my radio module is working as I planned, so I can patiently wait for the ultimate solution. Thanks again!