MobiFlight Community Support

I have used the instruction from Stephan to program this window(7 segment).
As long as I only use the IAS basic entry it works without fault.
If I try to set in for Mach and also the blank Connector reporting
11/11/2020 1:23:40 PM(75): Problem with transform. An error occured on parsing your value formula. Please review and correct any errors.
The program is running but this fault is repeating 4-6 times every second with different PM (Numbers)
I have not tried with also the Pseudo Blank and therefore not used precondition in the blank entry.
I tried to use that precondition but the I got the red warning sign in he connector on that line.
Anyone that can help me with this problem
HenningR

The Red Warning Sign is not meaning a Error.... This Symbol show you that THAT Config is currently not working in case of a Precondition that is FALSE at the moment !.

If you Build 2 Configs for the Speed Display..... One for MACH the other for IAS. Then its logical and correct that ONE is working and the OTHER is showing that Red Explentation Mark "!"

Your Problem with the Error in Logging is a Issue in your Configs. Without see it on Discord ( shared screen) or see your MCC File i can not tell you where the issue is. But 100% sure its a wrong entry in one of the Configs.
If you like you can disable all involved Configs then the issue is gone. Then enable 1 by 1 until the Error warning occure. Then you know WHAT of the Configs include the problem !

I am looking at the instruction. It sees to me that in the mach formula there is a space between $ and slash and spase between slash and 10,0.
Is this correct or is it of no significance.
HenningR

Spaces in formulars are prohibited.
Sometimes spaces sneak into the formulas while copying.

I am taking up again this subject.
I have tried all possible solutions in my head, but no luck.
The IAS display works ok in IAS on takeoff and climb, but as soon as I engage VNAV it just freeze in last set figures(numbers). That is because I can't get the blank function to work.
I have put them in as described in the setup. If I hook the "Space" the indicator starts to flicker, if I set 0 then I get four 0's in the display even when on ground (have not tested in air)
I am using four digits and the comparison is set as described with 4 blanks. I have not put in any pseudo Blank
Anyone to tell me where I am wrong in the configs
HenningR

Hi Henning.

Without see the configs i can not help.

The Flickering pretty sure was the correct way.....
Important is.... This config need 2 ( or 3) configs whatever way you go.
It need One Ocnfig instance that is used for MACH ( with a decimal Point in use) and a second Config that is used for IAS ( Without Decimal Point).
Finaly you can use the IAS Cponfig also for the blanking logic.... OR .... You use a 3rd Config that is used if Display must be blanked.

If 2 Configs work SAME TIME then this occure in Flickering. For example the IAS is still try to show the current speed.... And the Blank Config same time try to show spaces.
So it flickering.

As i said i can not directly guide you without see the situation.... But i will say in the moment your Display was flickering you was on the right way JUST you got a wrong or missing Precondition. Get sure at this moment only the BLANK Config is active... The other must be disabled ( Red ! Symbol) .

@ savery999

Technical NO.
The Prconditions are a part of MF since the beginning. So it not change the situation within the years.
It also not act if it´s not used. No Preconditions in use means no negative impact from it.
If it´s used the code element is verry small.... So it´s technical normaly not possible that you "feel" a problem here. We talk about milliseconds in a loop.

The Only point you "feel" the Precondition is the moment when it swap. In exactly THAT Loop you feel a little delay. ....
For example when you blank a Display by precondtion . Lets say if you press a Button then the Display must swap from COM1 to COM2 .
This will not happen instant.... It will hapen in the "next" loop. A small Config this is in milliseconds..... A Large Full Cockpit file with 1000+ Configs this will take maybe a little more.

**************
Solution:
Confirm your "Logging Mode" is disabled. Thats use to find issues. But it slow down the system massive! Specialy Encoders get extrem delays if Logging is active !
Thats not a Bug. Logging mode is not planed to use all time. this is just for debugging !