MobiFlight Community Support

Hi, in MF app i have various error message : "Problem with trasform. An error occurred on parsing your value formula. Please review and correct any errors".

But i don't see any reference at which formula it refer... how can know it?

Hi

Normaly this should be shown with a Red "!" in the specific Config Line.
If not mostly MF fully Stop ( Crash)
Then you know the problematic Config cause all Output Lines that work have already a Value in the Right Collumns ( FSUIPC Value, Output Value)
On a point this Values are not longer shown ( The moment of Crash)
Normaly the last Config that include Values or the next below is the critical one.

Another attempt.... Disable all Configs....
Then RUN MF and enable once by once until the issue Warning comes. Then you know it also!

If needed..... Like always! Join Discord. I can have a look on it via shared screen.

Hi

Normaly this should be shown with a Red "!" in the specific Config Line.
If not mostly MF fully Stop ( Crash)
Then you know the problematic Config cause all Output Lines that work have already a Value in the Right Collumns ( FSUIPC Value, Output Value)
On a point this Values are not longer shown ( The moment of Crash)
Normaly the last Config that include Values or the next below is the critical one.

Another attempt.... Disable all Configs....
Then RUN MF and enable once by once until the issue Warning comes. Then you know it also!

If needed..... Like always! Join Discord. I can have a look on it via shared screen.

Hi Pizman, thank you for response..
MF doesn't crash, fortunately.
I'll check if i have the ! symbol in the specific config line (do you meen in MF Output section, right?)

I'll check if i have the ! symbol in the specific config line (do you meen in MF Output section, right?)

Yes!

As i said... Try to check this.
If it not work, contact me on discord. With a sheared screen i can check the config within some minutes and can solve the problem !

I'll check if i have the ! symbol in the specific config line (do you meen in MF Output section, right?)

Yes!

As i said... Try to check this.
If it not work, contact me on discord. With a sheared screen i can check the config within some minutes and can solve the problem !

Ok i will check and report

Hi pizman, i have only "precondition is not satisfied" warning, nothing about error logged

As i said....
From Screenshot i can not figure this out. Only with a shared screen on Discord or when you do the checks i would do there.

The Symbol is "missed Precondition" ( Mouse Over). But the exact SAME Symbol is also used for parsing error . ( We know thats bad.... Its already in the feature request list).
So if you mousover all "Red !" i expect one or more are not "Precondition" they show e.g. "parsing Error."
And here we are !

As i said....
From Screenshot i can not figure this out. Only with a shared screen on Discord or when you do the checks i would do there.

The Symbol is "missed Precondition" ( Mouse Over). But the exact SAME Symbol is also used for parsing error . ( We know thats bad.... Its already in the feature request list).
So if you mousover all "Red !" i expect one or more are not "Precondition" they show e.g. "parsing Error."
And here we are !

I'll check all the symbol on every lines where it is and all are "precondition not satisfied".
It's difficult to schedule a discord session for me.
Does MF have a log where the error is entered more precisely?

In any case my FCU seems to works well for all functions even if with this errors

Not sure if this is available in the Logging.

With some experience its possible to check simply the Transform and Compare Tabs.... Then i would see the issue pretty sure.

Another idea is to use the "Disbale" Logic.

Simply disable maybe the half of the Output Configs ..... Press STOP and RUN . If Issue still exist it is pretty sure in the other half. If Problem no longer happen it was in the first half you disable at the moment.
Then next step is to again disable the half of the Config Block ( you know from first test where problem is) ..... Same idea....
By this technic you not need to check every single config.... You simply reduce number of Configs from 100% to 50% to 25% with just 2 Testruns and some clicks on the disable Button.

At the end if you know the problematic config you check the syntax there.

Not sure if this is available in the Logging.

With some experience its possible to check simply the Transform and Compare Tabs.... Then i would see the issue pretty sure.

Another idea is to use the "Disbale" Logic.

Simply disable maybe the half of the Output Configs ..... Press STOP and RUN . If Issue still exist it is pretty sure in the other half. If Problem no longer happen it was in the first half you disable at the moment.
Then next step is to again disable the half of the Config Block ( you know from first test where problem is) ..... Same idea....
By this technic you not need to check every single config.... You simply reduce number of Configs from 100% to 50% to 25% with just 2 Testruns and some clicks on the disable Button.

At the end if you know the problematic config you check the syntax there.

Ok, your debug logic idea is clear.
I will try.

Thanks

Finally with the last version i can see what formulas are in error!

Error 08/05/2022 12:33:59 Transform error (Speed Dot): An error occurred on parsing your value formula. Please review and correct any errors.
Error 08/05/2022 12:33:59 Transform error (Display is On): An error occurred on parsing your value formula. Please review and correct any errors.
Error 08/05/2022 12:33:59 Transform error (FCU Display Brightness (LEDs)): An error occurred on parsing your value formula. Please review and correct any errors.
Error 08/05/2022 12:33:59 Transform error (Heading Dot): An error occurred on parsing your value formula. Please review and correct any errors.
Error 08/05/2022 12:33:59 Transform error (LEDs HDG Mode): An error occurred on parsing your value formula. Please review and correct any errors.
Error 08/05/2022 12:33:59 Transform error (LEDs TRK Mode): An error occurred on parsing your value formula. Please review and correct any errors.
Error 08/05/2022 12:33:59 Transform error (LED LAT): An error occurred on parsing your value formula. Please review and correct any errors.
Error 08/05/2022 12:33:59 Transform error (Altitude is Managed): An error occurred on parsing your value formula. Please review and correct any errors.
Error 08/05/2022 12:33:59 Transform error (Speed Dot): An error occurred on parsing your value formula. Please review and correct any errors.
Error 08/05/2022 12:33:59 Transform error (Altitude is Managed): An error occurred on parsing your value formula. Please review and correct any errors.

Hi pizman82 , here the expressions i get error.
Can you help me?

Error 09/05/2022 15:53:41 Transform error (Speed Dot): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="if(#=1, if(A=0, 1, $), 0)" substrStart="0" substrEnd="7" />

Error 09/05/2022 15:53:41 Transform error (Display is On): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="if(#!=0 && @!=0, 1, 0)" substrStart="0" substrEnd="7" />

Error 09/05/2022 15:53:41 Transform error (FCU Display Brightness (LEDs)): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="if(#=1, $, 0)" substrStart="0" substrEnd="7" />

Error 09/05/2022 15:53:41 Transform error (Heading Dot): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="if(#=1, if(A=0, 1, $), 0)" substrStart="0" substrEnd="7" />

Error 09/05/2022 15:53:41 Transform error (LEDs HDG Mode): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="if(#=1 && ($=0 || A=0), 1, 0)" substrStart="0" substrEnd="7" />

Error 09/05/2022 15:53:41 Transform error (LEDs TRK Mode): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="if(#=1 && ($=1 || A=0), 1, 0)" substrStart="0" substrEnd="7" />

Error 09/05/2022 15:53:41 Transform error (LED LAT): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="#" substrStart="0" substrEnd="7" />

Error 09/05/2022 15:53:41 Transform error (Altitude is Managed): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="if(#=0 && A=1, 1, $)" substrStart="0" substrEnd="7" />

Error 09/05/2022 15:53:41 Transform error (Speed Dot): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="if(#=1, if(A=0, 1, $), 0)" substrStart="0" substrEnd="7" />

Hi

Looks like you get more then one issue :-)

At first.... please confirm you not use spaces !!
(Not sure if those come from Copy Text to Forum or if you really got them in the transform code! )

e.g.

Error 09/05/2022 15:53:41 Transform error (Speed Dot): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="if(#=1, if(A=0, 1, $), 0)" substrStart="0" substrEnd="7" />

NOT ... if(#=1, if(A=0, 1, $), 0) ..... You need : if(#=1,if(A=0,1,$),0)

I can not see the whole thematic... So if there are also other issues..... But definitly using spaces is wrong!

Hi

Looks like you get more then one issue :-)

At first.... please confirm you not use spaces !!
(Not sure if those come from Copy Text to Forum or if you really got them in the transform code! )

e.g.

Error 09/05/2022 15:53:41 Transform error (Speed Dot): An error occurred on parsing your value formula. Please review and correct any errors.
<transformation active="True" expression="if(#=1, if(A=0, 1, $), 0)" substrStart="0" substrEnd="7" />

NOT ... if(#=1, if(A=0, 1, $), 0) ..... You need : if(#=1,if(A=0,1,$),0)

I can not see the whole thematic... So if there are also other issues..... But definitly using spaces is wrong!

Ok i will check all.
Are Also this without spaces "if(#=1&&($=0||A=0),1,0)" ?

mmmhhh.

The rule "no spaces" is basic. a Space in a formula syntax is always a bad idea....

About your syntax: "if(#=1&&($=0||A=0),1,0)
Here i´m not sure and need to test myself....
If i remember right there is a Case by case Logic. So "maybe" your syntax is not correct.

You expect: If # is not 1 then it must be always "0" .... If #=1 AND One of $ or A = 0 then "1".
Maybe yoúr syntax work.... In Precondtion it will not work in case we have no brackets there.

i would use.... if(#=0,0,if($=0||A=0,1,0))
Means.... If #=0 then result is always "0" and statement is over.... If Not (#=1) then we check if $ or A = 0 .... If one of both is 0 then 1 else 0 .
(Remember the second Check is only done if #=1 )

So you avoid the the internal logic in case you make a more cleare statement.
AGAIN: Maybe your code do the same..... I never test it myself !