MobiFlight Community Support

Newbie question guys, be merciful..

I've got an I2C backpacked 16X2 LCD working on my Mega 2560, and have working Com1 display. If I add a second mapping for Com1-Standby at the opposite end of the same line, the display cycles between the 2 many times per second, but can't seem to display them both simultaneously.

Ideally I'd have liked to have Com1 + Standby on the upper line, and Nav1 + Standby on the lower line if it were possible.

Am I going to have to learn millions of programming to make it happen?

Thanks,

Ryan.

It sounds like the 16x2 display is resetting (and clearing) between each update. Try setting 4 values and see if MB cycles between 4 values.

That behaviour could be:
1 A feature of the software.
2 A feature of the display.

Do you know if there are display hardware settings that cause it to auto-reset when values change?

I would expect the software to cache the 32 bytes of the display, update just the bytes for the frequency change, then send the entire 32 bytes.
OR use a method that changes a few characters leaving the rest unchanged.

Cheers
Paul

Thanks for the response Paul, much appreciated!

I found this:
https://plclip.com/video/ja0tvTbaEnI/mobiflight-como-usar-un-lcd-display-using-an-lcd-display.html - which explained what I needed to do.

I was attempting to configure display space for each variable within its function, rather than establishing each variable and having a separate function for the display.

For a moment it worked well, then I added an encoder and 2 buttons. Now it's 'uploading with error' and crashing P3D, but thats a problem for tomorrow.

Thanks again!

Ryan.

Ryan,

Reboot everything including your PC. The USB link tends to go out of sync between MB and the Arduino.

Paul

Hi Ryan,

Welcome to MobiFlight.

What you are describing is a "typical" beginner mistake. I assume you have two different configs that access the display.

Do you have this in advance

https://www.mobiflight.com/forum/topic/838.html

worked through tutorial? It is in German, but should be comprehensible with the Google translator.

What happens: With your first config you write, for example, something in line 1 of your display, with the 2nd Config you write something in line 2 of the display, while the entry of the first line is deleted beforehand. When writing back to the first line, the second line is deleted. This creates a flickering display.

Note the configuration in pictures 6 and 7 of the tutorial. Then it should work.
You may only assign the display output once, otherwise it will flicker.

Please report the result.

I do apologies for the newbie mistakes! I did get Com1 and Com1-Standby working well last night. But it seems every time I try to add the Nav freqs to the equation it causes a crash.



https://www.dropbox.com/s/ogu6u9yu5jvdr76/Error.JPG?dl=0

This was a fresh attempt this morning.

I'm sure i'm doing something silly somewhere but I can't find it..

Appreciate the responses and apologies again for wasting you guys time.

Okay so I got it to work, but the only thing I changed was not using the weird 'S' symbol usually in position 3 on the display config list...

I changed that one to $ and used # for position 4 as default.

Peculiar problem, but got past it at least.

Onwards to the next step!

Ryan,

please delete the NAV-entries. Copy the COM-Configs and change the Offsets

Ryan,

$ is always the intern variable of MF! It represents an actual value - look at the transform-line.

If you do not want to use the §-character you can use "!" or "=" i.e. but you should avoid the "$"!

Thanks as always Stephan, it seems to work okay if I substitute the § for something else. Have used '!' as you suggested. All good now.