Max number of digits supported - 8Segment Displays
-
- Posts: 7
- Joined: Fri Mar 19, 2021 6:00 pm
Max number of digits supported - 8Segment Displays
What are the maximum number of digits supported for 8 segment displays? I have 3 five digit units connected to the same segment lines. This works for my own code, written directly to the Arduino, however AirManager seems to top out at only 8 digits. Is this a hard limit?
Re: Max number of digits supported - 8Segment Displays
In theory you could add each module separately if the limit is indeed 8. I’m not sure the limit is published anywhere but it would need to be limited because you can’t multiplex indefinitely. It seems 15 is doable from what you say. I’ve never personally tried more than about 8.
The problem with splitting them of course is it consumes a lot of pins. If you have several displays to make it would be better to use a MAX7219 which is natively supported or alternatively the TM1637/38 via message port.
The problem with splitting them of course is it consumes a lot of pins. If you have several displays to make it would be better to use a MAX7219 which is natively supported or alternatively the TM1637/38 via message port.
Air Manager panels at https://www.experimentalsimavionics.com
Youtube Channel https://www.youtube.com/channel/UC8ZqXX ... kfZMq5BKig
Air Manager API Tutorial Video Series https://youtube.com/playlist?list=PLNr0 ... baT4gJKg5D
Youtube Channel https://www.youtube.com/channel/UC8ZqXX ... kfZMq5BKig
Air Manager API Tutorial Video Series https://youtube.com/playlist?list=PLNr0 ... baT4gJKg5D
-
- Posts: 7
- Joined: Fri Mar 19, 2021 6:00 pm
Re: Max number of digits supported - 8Segment Displays
Looks like I may need to split them - pins aren't too much of an issue as they're plugged into a Mega. I have a couple of MAX7219s spare, however these are OpenCockpits modules, which are a better fit size wise. The other option, as you say, is to message port it. Thanks for your help.
Re: Max number of digits supported - 8Segment Displays
There are some troubles with the MAX7219 at the moment, both in 3.x and 4.0. It's something we're gonna fix, but it'll be in 4.1 or 4.2. Corjan went all in with a oscilloscope to analyze the signals, and see what's going wrong. No progress yet I believe.