#MAX7219 showing slightly different number from output value shown in mobiflight connector 10.5.3
1 messages · Page 1 of 1 (latest)
I tested three of them and they're all the same.
so if I change number like A, A+1, A+2, A+1 the shown result is the number before A, A, A+1, A+2
like one step behind
You need to show exactly what you are doing.
Post screenshots of the output config: simvar, Modify and display tabs
Your video is very confusing panning back and forth.
The config line says HDG copy, but you appear to be trying to display Altitude. Very confusing.
that's just me not having changed the name
(it says alt but it's the same one)
Can you explain what are you trying to do with those modifiers? Seem unnecessary. If you want to display Flight Level instead of Altitude just divide by 100 and probably floor the value instead of rounding.
If you want to display numbers right justified use the left padding option in the display tab.
yes that's what I want to do and I'll change to it but does it have anything to do with my problem?
the problem is, that max7219 seemingly shows the previous value(shown in mobiflight connecter) rather than current
What does the flight Sim Value column receive from the Sim. Mobiflight simply displays what it received.
the hardware should display what's in the Output Value column, no?
Yes
Show me
Post screenshot of the Mobiflight window with the values clearly
Then what is displayed
I don't use substring or padding very often. Mobiflight is not very strong at handling characters.
But what comes out of your modifiers should be what is displayed. I also noted your substring picks four characters but your display is set for only 3.
it cut the last character when I set the substring to 0~2 so I increased it
I changed to what you suggested and still the same tho
one more tested, every four same. showing the previous value, not changed value
Does sustring maybe need to be character 1-3?
the index starts with 1?
I thought it started with 0 like many other programming things
but anyway fine
I believe it's not hardware fault since when I tested it with Arduino IDE with my own code it worked.