Current Release Notes
This section is maintained just to show the ongoing history of each revision of the coded files. This could mean that what is written here is the way the screens works. Each revision may make changes to the overall operation of the display code slightly. Keep this in mind when looking for how things work. Email me if you need to resolve some display screen error.
As a quick reminder here, I'm not looking for any pity. I'm just reminding you that I'm legally blind. Anything that could go wrong will. Add in my disabilities, and, programming errors can happen. If you see something, anything, just tell me about it. I can usually fix what ever is wrong quickly and repost a fixed file. THANKS FOR YOUR UNDERSTANDING!
Email Me At: ag4oj [at] arrl [dot] net
ATTENTION: ALL images are created by me. ALL code is written by me. My HMI and tft files have embedded copyright notices. Though this is meaningless to most, it is said here to inform those who think something contained in my files belongs to them in some way. ALL screens display the same things, only difference in them is the size.
NOTE 1: My Nextion Display coded files will mostly work without the Nextion Display Driver being installed. It's important that the display is displaying Hotspot data before adding the Nextion Display Driver. ONLY the IDLE and DMR screens benefit from the Nextion Display Driver being installed, presently. OH, and the "POWER" and "REBOOT" buttons.
NOTE 2: More displayable information, as in sent data commands, are sent over a USB to TTL Display connection as compared to the MMDVM modem Nextion display connection. These coded Nextion Display tft files are designed to take advantage of all the extra commands that are sent via a USB type of display connection.
NOTE 3: Using the Raspberry Pi 3B+ and 4B Requires you to use 4.1.0 or greater version of Pi-Star. This also tends to run a bit warmer, usually requiring a fan and or heatsink combination to cool them down. WARNING, the heat build up can burn you. Raspberry Pi 3B requires less power to operate, much better at this time for mobile, remote, or battery operations.
NOTE 4: The added heat build up on the Raspberry Pi 3B+ and 4B almost always has nothing to do with adding a Nextion Display and the Nextion Display Driver to your Hotspot. The Nextion Display has it's own processor. The Nextion Display Driver mostly uses some memory and only jumps into action when it captures MMDVMHost Nextion Display messages.
NOTE 5: Other than adding the Nextion Display Driver to Pi-Star to enhance the IDLE and DMR screens, my screen code DOESN'T require ANY extra loaded programs to run successfully and completely. I want you up and running quickly with your newly connected Nextion Display.
NOTE 6: Every effort is made to use every possible feature of the Raspberry Pi SBC, the Raspberry Pi OS, the MMDVM modem, the MMDVMHost, Pi-Star, and the Nextion Display Driver before a coded Display BEHAVIOR is added, changed, or enhanced. This is the "Keep It Simple Stupid" OR "KISS" motto of these Nextion Display Coded files.