EDDC - Enhanced Display Driver Code

The Enhanced Display Driver Code

 
By Using This Website, You agree to the following Website Linked Disclaimer 
 

Attention: READ And Follow All Procedures

 
YES, YOU have to read and follow all of the procedures below. This Website and all of it's Webpages are very dynamic, meaning, changes can happen to them almost daily. DON'T ASSUME that a procedure that was done one way yesterday is the same today. Always review the information provided on all of this Website's Webpages.
 
As there are many users of this information below and as they come across a problem, may it be Our mistakes or theirs, We try to implement changes to the content below to help avoid the rest from having the same or similar problems. This also means that a lot of defining of each procedure may be offered. This may become boring, mundane to the rest of the more expert users.
 
We all learn at different paces and over simplification helps everyone get things right in the end. PLEASE be understanding of this as We wish to be all-inclusive by having this information help the many Beginners to the very few Experts. We hope that this Website helps make the many that come here the greatest Digital Amateur Radio Operators of tomorrow.
 
When You Learn, What You Learn, Always Help Another In Need, PAY IT FOWARD, TEAM AG4OJ, ENJOY!
 

FIRST: Is Everything Setup And Updated Properly?

 
Make SURE that your NEXTION DISPLAY is ALREADY wired properly BEFORE powering it up. Obviously the GND should be connected to the GND and the +5V should be connected to the +5V. Next, the TX should be connected to the RX and the RX should be connected to the TX. ENSURE that the DATA WIRES are crisscrossed.
 
 Connecting The Nextion Display
 
See How The Wires Are Connected In The Image Above.
 
On a MMDVM Modem connected Nextion Display, it is very important to use a "LEVEL SHIFTER" in-between the MMDVM Modem and the Nextion Display. Connecting 5.0V logic data lines of the Nextion Display with the 3.3V logic data lines of the MMDVM Modem microcontroller is NOT advisable.
 
On a 06/15/21, We gained access to special equipment to measure what We call Substrate Noise and Coupling (SN&C), a very sophisticated interference test. In the tests We measured MMDVM Modem Microcontroller SN&C. We found that an attached Nextion Display to the MMDVM Modem Microcontroller increased the SN&C considerably when not using a Logic Level Shifter.
 
With the Logic Level Shifter, the SN&C was the same, similar to as if NO Nextion Display is connected. Be warned that increasing SN&C can have a profound effect on the MMDVM Modem Microcontroller ability to function properly and/or accurately. SN&C can even stall, cause problems with upgrading of the firmware when flashing the MMDVM Modem Microcontroller.
 
Let's finally mention that not all Nextion commands make it through to a MMDVM Modem connected Nextion Display. This seems to be a busy serial port problem between the MMDVMHost and the MMDVM Modem under high MODE data transfers. This bottle-neck at times has actually shutdown the Display Driver, where a reboot is the only way to make the display work again.
 
OK, one more point to mention. Most of the MMDVM Modem connected Nextion Displays DO NOT have the ability to communicate back to the Raspberry Pi, Pi-Star, MMDVMHost operating system. This means NO Bi-directional data flow, meaning that command buttons on the Nextion Displays will not work. Very few out there are programmed just right to make it work.
 
Remember here, anything that can effect the MMDVM Modem's operation, it's overall health, will intern effect your resulting Digital Mode Communications. This is just Our growing list of the many reasons why We continue to strongly recommend the use of a USB to TTL device connection for the Nextion Display instead, as shown in the image provided above.
 
 3.3v to 5.0v Level Shifter
 
This Is A Typical Logic Level Shifter In The Image Above.
 
The Nextion Display needs to be flashed with Firmware that can display at least the MMDVMHost messages. Usually, it needs to be able to display added Display Driver Messages also. The default manufacturer's display Firmware on a new display will only show their display's introduction code.
 
We provide Nextion Display Firmware files on this website for all sizes and types of Nextion Displays. They will display all of the MMDVMHost sent messages as well as those extra ones from the installed display driver, if used.
 
 MMDVM Modem's Firmware Version
Check the MMDVM Modem Firmware from the Pi-Star Admin screen (See The Green Arrows In The Picture), make sure it is up to date. As of 05/22/21, the latest Firmware version for a typical MMDVM Modem Hat is v1.5.2. IF this firmware is not up to date, it can cause all kinds of problems, frustrations, headaches, etc. PLEASE ask for help if flashing the MMDVM Modem Firmware doesn't work.
 
For The Raspberry Pi OS, Pi-Star, and the MMDVMHost, always do a "sudo pistar-update" in the Pi-Star's ssh window. A "sudo pistar-upgrade" maybe in order also. Doing these will save a lot of headaches from a non-current Raspberry Pi's OS and Pi-Star. We have a Guide here on this website that will help you ensure that everything is up to date.
 
Always reach out for help if you don't understand how to do any of this stuff.
 
...OK, You Have Ensured That Everything Is Setup And Updated Properly...
 
 Amateur Radio Callsign AG4OJ  Nextion Display Code Files - Version B  NDC - Version B Release Notes  AG4OJ's E-Mail Account
 

SECOND: Is Your Nextion Display Showing MMDVMHost Messages?

 
DO NOT install ANY Display Driver Just YET!
 
LOOK! READ THIS SECTION COMPLETELY!
 
Make SURE that your NEXTION DISPLAY is ALREADY displaying values being sent by the MMDVMHost within Pi-Star!
 
Is It Already Displaying Your Callsign, The Date, And Time On The IDLE Screen?
 
Does It Switch To A Mode Screen When YOU or Someone else Is Transmitting?
 
If it is NOT, DO NOT Install ANY Display Driver just YET, this will only add to your installation headaches. Remember here, if it isn't working already, then there's a GOOD possibility that it'll never work right! Go now and make sure it is working before you proceed. GET HELP to fix this situation BEFORE continuing with ANY Display Driver installation.
 
...OK, You have ensured that the Nextion Display is DISPLAYING MMDVMHost Messages...
 
...As Described Above WITHOUT ANY Display Driver being installed...
 
 Amateur Radio Callsign AG4OJ  Nextion Display Code Files - Version B  NDC - Version B Release Notes  AG4OJ's E-Mail Account
 

THIRD: Did You Then Install The ON7LDS NDDC?

This is to say that YOU have already made sure that the Nextion Display is displaying the Pi-Star / MMDVMHost sent messages. Then, install the ON7LDS Nextion Display Driver Code and make sure that it continues to WORK properly, as expected. This as the procedures below do not install all the other ON7LDS Nextion Display Driver support files at this time.
 
...The Link Below, After Installing The Display Driver, Will Have a DDC Link To Return Here...
 

 CLICK HERE To Install ON7LDS NDD NEXT!

 
...OK, You have ensured that the ON7LDS NDDC is installed...
 
 Amateur Radio Callsign AG4OJ  Nextion Display Code Files - Version B  NDC - Version B Release Notes  AG4OJ's E-Mail Account
 

FOURTH: The EDDC Executable Requirements

The EDDC below needs an unhindered Bi-Directional Serial DATA Flow. The EDDC needs the Nextion Display to be connected to the Raspberry Pi through a USB to TTL device. This type of connection is something that is NOT always possible with a MMDVM Modem Hat connected Nextion Display. Some will work, most will not.
 
USE of the EDDC below on a MMDVM Modem Connected Nextion Displays are NO LONGER recommended OR Supported by Us. Please use the Version A of the NDC and the ON7LDS NDDC for all MMDVM Modem connections.
 
...OK, You have a properly USB to TTL connected Nextion Display...
 
 Amateur Radio Callsign AG4OJ  Nextion Display Code Files - Version B  NDC - Version B Release Notes  AG4OJ's E-Mail Account
 

FIFTH: Did You Change The Nextion Display Code To Version B?

NDC Version B will only show Pi-Star/MMDVMHost and any extra EDDC messages by using the EDDC executable on this webpage. This Display Driver is an advanced version and is more likely to be updated frequently by Us. This version of the Nextion Display Code WILL NOT respond to ANY of the ON7LDS NDDC sent messages, it will ignore them.
 

Nextion Display Code Version B

 
...The Link Below, After Installing The Nextion Display Code, Will Have a DDC Link To Return Here...
 
 The Nextion Display Code Version B
 The Nextion Display Code Version B Link. HELLO! Clicking this link will take you to 36 different code files for Nextion Displays. Types Nextion Basic, Enhanced, and Intelligent, Sizes 2.4", 2.8", 3.2", 3.5", 4.3", 5.0", 7.0", and 10.1", Two Landscape Orientations.
 

Nextion Display Code Release Notes - Version B

 
...The Link Below, After Reading The Release Notes, Will Have a DDC Link To Return Here...
 
 Nextion Display Code Release Notes Version B
 Nextion Display Code Release Notes Version B Link. ATTENTION! Please read all of the RELEASE NOTES. They contain all the information needed to operate Our Nextion Display Code. There are now special initial setups and button behaviors everywhere. These release notes are Our “Users Manual” of sorts.
 
...OK, You have updated the Nextion Display with Version B Code...
 
 Amateur Radio Callsign AG4OJ  Nextion Display Code Files - Version B  NDC - Version B Release Notes  AG4OJ's E-Mail Account
 

The EDDC Executable Introduction

As We Dig Into The ON7LDS NDDC

This will take time. We wish to first not break anything that it already does. This means that as We dig into the ON7LDS NDDC, it will be slow going. Releases may have to wait so that We can thoroughly inspect our changes and make sure that it ONLY enhances what it used to do. We hope that you understand Our way of thinking, and, that We don't want you using anything partially coded, half baked.
 
...Presently The EDDC Should Be Considered Developing Software, With Stepped Releases...
 

Installing The Enhanced Display Driver Code Below

This code is meant to compile and respond similarly to the ON7LDS NDDC. It's what has been done under the hood is what usually matters. This means that the compiled NDC flashed to your Nextion Display should know of any changes documented in the EDDC Release Notes Link. 
 

This Is Your Final WARNING Before YOU Proceed

WE assume from this point on that YOU are advanced enough to understand what is going on when you take the following actions below. This is your final WARNING that you are about to make your Pi-Star -> MMDVMHost -> Nextion Display Driver Code, NDDC -> Nextion Display(Nextion Display Code) installation switch to using this Enhanced Display Driver Code, EDDC.
 
...Presently The EDDC Should Be Considered Developing Software, With Stepped Releases...
 
 Amateur Radio Callsign AG4OJ  Nextion Display Code Files - Version B  NDC - Version B Release Notes  AG4OJ's E-Mail Account
 

The Enhanced Display Driver Code Executable

July 20th, 2021, Release v210720

Hello! Welcome to the Editing and Expanding project for this Enhanced Display Driver Code. This so We can make it do more than it has ever done before. You will have to have the latest version of ON7LDS Nextion Display Driver already installed and working.
 
...EDDC Version 210720 Requires NDC VerB 210714. Underlying Coding Changes Have Been Made...
 

EDDC Executable Release Notes

 The EDDC Release Notes
 The EDDC Release Notes Link. These Release Notes are for those who are writing their own Nextion Display Code and are looking to use the extra functionality of this EDDC. This version supplied here will compile and has been tested to work as documented within these Release Notes. ENJOY!
 

Installation Procedures For The EDDC Executable

 
...We Have Changed The Part As To Part Bs To Coincide With The VerB NDCs...
 
...This Keeps The NDC VerB With Part B EDDC Procedures, Eliminates Some Confusion...
 

Part B1: Installing And Updating The Database Files

 
...This section will help you create the code directory and install the supporting database files...
 
MAKE SURE: That after every command executed below that the command prompt remains in "(rw)" mode. IF it should change back to "(ro)" after executing a command, do another "rpi-rw" to get it back to "(rw)" mode first.
 
ALSO MAKE SURE: That the last command executes properly. IF it switched back to "(ro)" during the last command, something may be incompletely done. Watch for this, as this happens when it is least expected, causing problems that are hard to find. Do the "rpi-rw" again, get back to "(rw)", then re-execute the last command when it doubt.
 
COMMAND COPY AND PASTE: You can copy and paste these commands into the Pi-Star SSH window. With your mouse, highlight the "BOLD BLACK COLORED" command below. Press CRTL-C. Go to your Pi-Star SSH Window. Click on the flashing cursor to make sure you are "IN" the SSH window.
 
With the mouse, right click in the flashing SSH cursor. When the menu pops-up, click on "Paste from browser". Click inside of the "ENTRY BOX" and press CRTL-V to paste your copied command from this webpage into the dialog box. Press the OK button. The command should be pasted onto the SSH window command line. Press enter. DONE! Command executed!
 
... Pi-Star -> Configuration -> Expert -> SSH Access ...
 
... From The Freshly Started Pi-Star SSH Access Window ...
 
pi-star login: pi-star <ENTER KEY>
 
Password: raspberry <ENTER KEY>
 
pi-star@pi-star(ro):~$ rpi-rw <ENTER KEY>
 
pi-star@pi-star(rw):~$ sudo su <ENTER KEY>
 
root@pi-star(rw):pi-star$ df -hT /home <ENTER KEY>
 
 Disk Free Command
 
Executing the command above should give the image above. Look at the value under the Size. If this closely matches the size of Your SD Card, all is well, continue below. IF NOT, then execute "pistar-expand" command, wait for it to finish. Then execute a "reboot" command, and start all over again.
 
SEE, this image above says "30G" for Our 32 GB SD Card. Like We have said, it'll be close in value. IF the SD card is NOT completely in use by the Raspberry Pi OS, then the "pistar-update" command below could FAIL to perform a complete update in some way.
 
root@pi-star(rw):pi-star$ pistar-update <ENTER KEY>
 
Executing the command above will make sure that your Raspberry Pi OS / MMDVMHost / Pi-Star installation is COMPLETELY up to date. This is very important, as everything depends on being current.
 
root@pi-star(rw):pi-star$ pistar-upgrade <ENTER KEY>
 
Executing the command above will see if your on the current version. RE-DO the last two commands until your completely updated and upgraded.
 
root@pi-star(rw):pi-star$ mkdir code <ENTER KEY>
 
IF executing the command above complains "cannot create directory 'code': File exists", this is OK. It means that the directory already exists. Just continue to the next command. This isn't your first time doing this rodeo, lasso the next command, HA!
 
root@pi-star(rw):pi-star$ cd code <ENTER KEY>
 
Executing these last two commands above will initialize and place you in the DDC coding directory.
 
root@pi-star(rw):code$ pwd <ENTER KEY>
 
/home/pi-star/code
 
"pwd" Shows that We are in the right directory.
 
root@pi-star(rw):code$ ls -al <ENTER KEY>
 
1. Executing the "ls -al" command above will give a directory listing.
 
2. If you have done this section before, and there's a bunch of files listed, THEN
 
root@pi-star(rw):code$ rm -r /home/pi-star/code/* <ENTER KEY>
 
1. The command above will remove all of the files in the directory, including the Sub-Directories.
 
2. This way the directory "/home/pi-star/code/" is now ready for a fresh Re-Start.
 
root@pi-star(rw):code$ wget https://drses.com/AG4OJ/EDDC/Code/Scripts/getScripts.sh <ENTER KEY>
 
root@pi-star(rw):code$ chmod u+x getScripts.sh <ENTER KEY>
 
root@pi-star(rw):code$ mkdir Scripts <ENTER KEY>
 
root@pi-star(rw):code$ mv getScripts.sh Scripts/getScripts.sh <ENTER KEY>
 
root@pi-star(rw):code$ ./Scripts/getScripts.sh <ENTER KEY>
 
The "./Scripts/getScripts.sh" when executed will download/update all the required scripts for this webpage, making them executable, including refreshing the "getScripts.sh" file just executed.
 
root@pi-star(rw):code$ ./Scripts/databases.sh <ENTER KEY>
 
Executing the "./Scripts/databases.sh" will download the new database files, remove the old ones, and update them on the Pi-Star image. These are "stripped.csv", "userDMRID.csv", "BM_groups.txt", "TGIF_groups.txt", and "DMR+_groups.txt" files. The "databases.sh" script file will be left behind in the "code/Scripts/" directory for future database updates at your leisure.
 
The "BM_groups.txt", "TGIF_groups.txt", and "DMR+_groups.txt" files are for different DMR Networks. They allow for displaying the proper Talk Group Names for the intended Network. Setting this is done on the Pi-Star Configure -> Expert -> MMDVMHost -> NextionDriver section setting of the GroupsFile. Click "Apply Changes" and then REBOOT Pi-Star for the replacement database file to take effect.
 
...OK, If all You Wanted Was Installing/Updating The Databases, STOP HERE...
 
ATTENTION: IF Your Nextion Display Is Connected To The MMDVM Modem, YOU WILL Have to STOP HERE.
 
WE Do Not Support MMDVM Modem Connections, Some May Still Work, Many WILL NOT Work With The EDDC.
 

Part B2: Downloading The Enhanced Display Driver Code Files

 
...This section will help you download the Enhanced Display Driver Code files...
 
... Pi-Star -> Configuration -> Expert -> SSH Access ...
 
... From The Freshly Started Pi-Star SSH Access Window ...
 
pi-star login: pi-star <ENTER KEY>
 
Password: raspberry <ENTER KEY>
 
pi-star@pi-star(ro):~$ rpi-rw <ENTER KEY>
 
pi-star@pi-star(rw):~$ cd code <ENTER KEY>
 
pi-star@pi-star(rw):code$ sudo su <ENTER KEY>
 
root@pi-star(rw):code$ pwd <ENTER KEY>
 
/home/pi-star/code
 
root@pi-star(rw):code$ ./Scripts/getIt.sh <ENTER KEY>
 
Executing these commands above will download the Enhanced Display Driver code files to the "/home/pi-star/code" directory. The "./Scripts/getIt.sh" Script file and the EDDC files will remain in the "code" directory afterwards. The executing the "./Scripts/getIt.sh" script in the future makes sure that you have downloaded the latest version of the code.
 

Part B3: Compiling The Enhanced Display Driver Code Files

 
...This section will help you Compile the Enhanced Display Driver Code...
 
root@pi-star(rw):code$ make <ENTER KEY>
 
After running the "make" command, you should NOT see any errors. If you do, something went wrong, STOP right HERE! Retrace your steps. when all else fails, contact Us, DO NOTHING FURTHER!
 

Part B4: Installing The Enhanced Display Driver Code Files

 
...This section will help you install the Enhanced Display Driver Code...
 
root@pi-star(rw):code$ ls -al NextionDriver <ENTER KEY>
 
-rwxw-xr-x 1 root root 53684 Feb 7 17:25 NextionDriver
 
OK, make just compiled the file, NO ERRORS WERE REPORTED. Doing this next command above makes sure that We have a compiled executable. IF this command above gives you a file listing for the NextionDriver, as shown, continue to the next commands below.
 
root@pi-star(rw):code$ rm /usr/local/bin/NextionDriver <ENTER KEY>
 
This next command above removes the active NextionDriver executable from the Pi-Star image.
 
root@pi-star(rw):code$ cp NextionDriver /usr/local/bin/NextionDriver <ENTER KEY>
 
This next command above moves a copy of the newly compiled NextionDriver into place.
 
root@pi-star(rw):code$ ls -al /usr/local/bin/NextionDriver <ENTER KEY>
 
-rwxw-xr-x 1 root bin 53684 Feb 7 17:25 /usr/local/bin/NextionDriver
 
This last command above gives a directory listing of the properly placed newly compiled NextionDriver version.
 
The first output of file listing above and this last one should match file sizes and dates of compile. Remember here, the file sizes should match, yet, depending on the build version, they both could be a different size then shown. The date will obviously be the date when you compiled the EDDC. This is just an example of what you'll see.
 
The "./Scripts/moveIt.sh" script was also downloaded by the "./Scripts/getScripts.sh" and does all 4 of the above commands. If you feel comfortable with the procedures above, the "./Scripts/moveIt.sh" will save some time. The "./Scripts/moveIt.sh" script still shows the file sizes and dates, this so there can still be a visual comparison of the files on the screen.
 

Part B5: MMDVMHost - Editing The "mmdvmhost" Settings File

 
...This Section Shows How To Edit The MMDVMhost Settings File...
 
root@pi-star(rw):code$ nano /etc/mmdvmhost <ENTER KEY>
 
This is a text edit of the "mmdvmhost" settings file. It's EXTREMELY IMPORTANT that you be VERY CAREFUL editing this "mmdvmhost" settings file. Arrow down until you find the area in the file with the areas shown below. YOUR "Port=" values maybe different if your Nextion Display is connected to the MMDVM MODEM.
 
At the bottom of the [NextionDriver] section, add spaces for the variables list with the GREEN ARROWS below. The variables with the RED ARROWS belong to the NDDC ONLY. We've included both sections as a reference to everything that has to do with the Nextion Display. Watch to keep the space between the "NextMsgFlags" and "[OLED]" section as you make the edits.
 
 MMDVMHost - mmdvmhost Settings Edit
 
...See Part B7 VIOLET ARROWS section to explain which set of numbers to use...
 
After making the proper edits to the "mmdvmhost" file with the nano editor;
 
1. "CTRL-O" will bring up a line with the file name to save, "/etc/mmdvmhost".
 
2. PRESS the ENTER KEY. The line will disappear. Then saying so many lines written.
 
3. "CTRL-X" will close the "nano" text editor and return you to the command prompt.
 

Part B6: Changing The Nextion Display Code

 
...This Section Makes Sure That The Nextion Display Firmware Is Updated...
 
root@pi-star(rw):code$ reboot <ENTER KEY>
 
Rebooting will allow the new database files, the "mmdvmhost" settings file edits, and the EDDC to take effect. You should now see what the EDDC sends to Our Nextion Display Code Version B. If you haven't updated the Nextion Display Code on your Nextion Display to the latest Version B;
 
PROPERLY Shut down Pi-Star and Click Here To Update It Now. 
 

Part B7: MMDVMHost - Explaining The Settings Page

 
The Nextion and Nextion Driver Sections
 
...This Section Explains The Nextion and Nextion Driver Sections...
 
Pi-Star MENU -> Configuration -> Expert -> MMDVMHost. Scroll down to see the two Nextion Display sections below. This will show that you have done the proper edits to the "mmdvmhost" file.
 
 MMDVMHost Expert Settings Page
 
The GREEN ARROWS shows where to adjust the IDLE and MODE screen brightness.
 
These values are usually set to between 5 to 100.
 
The EDDC and NDC VerB gives you complete control over the screen brightness.
 
The NDDC and NDC VerA still has some internal influence on the screen brightness.
 
The BLUE ARROW is where you change the Talk Groups names file for each DMR Network.
 
The BM_groups.txt is for The Brandmeister Network. (UNIX ANSI)
 
The TGIF_groups.txt is for the TGIF Network. (UNIX ANSI)
 
The DMR+_groups.txt is for the DMR+ Network. (UNIX ANSI)
 
The BROWN ARROW is where you change the user database file name.
 
The userDMRID.csv is for the newer lookup database version.
 
The stripped.csv is for the older lookup database version. (NDDC DEPRECATED In v1.20)
 
!!! ATTENTION: The EDDC still uses the stripped.csv file.
 
The VIOLET ARROWS shows the numbers used to handle each type of user database.
 
The LEFT MOST NUMBERS are for the userDMRID database.
 
The RIGHT MOST NUMBERS are for the stripped database. (NDDC DEPRECATED In v1.20)
 
!!! ATTENTION: The EDDC still ignores these number assignments.
 
The RED ARROWS are the added MMDVMHost settings for the EDDC.
 
The ScreenSaver is the Screen Saver TimeOut in seconds. A ZERO turns it OFF.
 
The GenerateCPU set the frequency in seconds which the CPU parms are updated. A ZERO turns it OFF.
 
The HostMsgFlags & NextMsgFlags - SEE EDDC Release Notes Webpage.
 
The DMR ID Lookup Section
 
...This Section Explains The DMR ID Lookup Section...
 
Pi-Star MENU -> Configuration -> Expert -> MMDVMHost. Scroll down to see the DMR Id Lookup section below. This is where it has to be changed to show the DMR ID number on the Nextion Display Code.
 
 MMDVMHost DMR Id Lookup 1
 
In the image above, it shows the default settings used to point to the Database file that the MMDVMHost uses to translate the user DMR ID number into a Callsign and short name. The time value is for how often to check for updates.
 
 MMDVMHost DMR Id Lookup 2
 
In the image above, it shows the changed name Database file. This is a created empty file by the ./Scripts/databases.sh script. It is used to give the MMDVMHost a default file to look at, that is empty of DMR IDs. The time is changed to ZERO, as there is no need to do an update. This will allow all of the user DMR IDs to pass through the MMDVMHost to the EDDC and then onto the NDC VerB code on the Nextion Display.
 
There is one problem to all of this. This translation table is used to show the callsigns on the Pi-Star ADMIN screen. By changing this, Pi-Star will no longer show callsigns. It will only show the DMR ID numbers. They can still be clicked on the ADMIN screen and will show user information from RadioID.net. This is how the EDDC can get the DMR number to show it on the Nextion Display.
 

Re-Installing / Changing The NDDC Version

 
Installing the EDDC Executable above can be easily over-written, undone by doing the steps below. We now provide several different versions of the NDDC below that can be re-installed.
 
The extra older versions provided below are mostly for Our developers/programmers to use. They are included here for backward compatibility, testing, and trouble shooting. We just make them available to everyone else who wishes to do their own developing/programming of the Display Drivers provided on this website.
 
 Installing The ON7LDS NDDC
 Installing The ON7LDS NDDC Link. ATTENTTION: IF YOU have never installed the ON7LDS Nextion Display Code, THEN YOU must do that now. The procedures below will not work until you do. Click on the links associated with this paragraph to go and do this before proceding below.
 
 EDDC - Part B1
 EDDC - Part B1 Link. ATTENTTION: IF YOU have never done Part B1 procedures above, THEN YOU will need to do Part B1 (ONLY) above before starting with Part A1 below. Click on the links associated with this paragraph to go and do this now, otherwise the procedures below will not work right.
 
!!! ATTENTION: These Versions Below Are Modified By Us, They Now Include The Ability To Handle 210,000 Contacts.
 
The User Databases Provided By Us On This Website Exceed 200,000 User DMR Contacts.
 
root@pi-star(rw):code$ ./Scripts/nddc119.sh <ENTER KEY>
 
210122 - The v1.19 version above is the original ON7LDS version. With the Pi-Star update on 06/07/21, it included the updated MMDVMHost which stopped transmitting the t31 LOCATION message. (Changed in the August 27th, 2020 release of the MMDVMHost) This version, when installed, will NO LONGER show the t31 LOCATION message.
 
root@pi-star(rw):code$ ./Scripts/nddc119A.sh <ENTER KEY>
 
210610 - The v1.19A version above is the version where We added in the t31 LOCATION message, added in the extra code. With the Pi-Star update on 06/07/21, it included the updated MMDVMHost which stopped transmitting the t31 LOCATION message. (Changed in the August 27th, 2020 release of the MMDVMHost)
 
root@pi-star(rw):code$ ./Scripts/nddc120.sh <ENTER KEY>
 
210615 - The v1.20 version above is the latest ON7LDS version. This version includes some new extra features that are not fully tested by Us. After several GitHub changes over the course of two days after it's first release, it appears that the changes to this version have stopped, stabilized for now.
 

Re-Installing / Changing The NDDC

 
...We Have Changed The Part Bs To Part As To Coincide With The VerA NDCs...
 
...This Keeps The NDC VerA With Part A NDDC Procedures, Eliminates Some Confusion...
 

Part A1: Downloading The ON7LDS Nextion Display Driver Code Files

 
...This Section Downloads The ON7LDS NDDC...
 
... Pi-Star -> Configuration -> Expert -> SSH Access ...
 
... From The Freshly Started Pi-Star SSH Access Window ...
 
pi-star login: pi-star <ENTER KEY>
 
Password: raspberry <ENTER KEY>
 
pi-star@pi-star(ro):~$ rpi-rw <ENTER KEY>
 
pi-star@pi-star(rw):~$ sudo su <ENTER KEY>
 
root@pi-star(rw):pi-star$ cd code <ENTER KEY>
 
root@pi-star(rw):code$ pwd <ENTER KEY>
 
/home/pi-star/code
 
root@pi-star(rw):code$ ./Scripts/getScripts.sh <ENTER KEY>
 
root@pi-star(rw):code$ ./Scripts/nddc120.sh <ENTER KEY>
 
Executing these commands above will download the ON7LDS Nextion Display Driver code files to the "/home/pi-star/code" directory. The "./Scripts/nddc120.sh" Script file is one available from the list above. These NDDC files will remain in the "code" directory afterwards. This over-writes the previous code files.
 

Part A2: Compiling The ON7LDS Nextion Display Driver Code Files

 
...This Section Compiles The ON7LDS NDDC...
 
root@pi-star(rw):code$ make <ENTER KEY>
 
After running the "make" command, you should NOT see any errors. If you do, something went wrong, STOP right HERE! Retrace your steps. when all else fails, contact me, DO NOTHING FURTHER!
 

Part A3: Installing The ON7LDS Nextion Display Driver Code Files

 
...This Section Installs The ON7LDS NDDC...
 
root@pi-star(rw):code$ ls -al NextionDriver <ENTER KEY>
 
-rwxw-xr-x 1 root root 53684 Feb 7 17:25 NextionDriver
 
OK, make just compiled the file, NO ERRORS WERE REPORTED. Doing this next command above makes sure that We have a compiled executable. IF this command above gives you a file listing for the NextionDriver, as shown, continue to the next commands below.
 
root@pi-star(rw):code$ rm /usr/local/bin/NextionDriver <ENTER KEY>
 
root@pi-star(rw):code$ cp NextionDriver /usr/local/bin/NextionDriver <ENTER KEY>
 
root@pi-star(rw):code$ ls -al /usr/local/bin/NextionDriver <ENTER KEY>
 
-rwxw-xr-x 1 root bin 53684 Feb 7 17:25 /usr/local/bin/NextionDriver
 
The next command above removes the active NextionDriver executable from the Pi-Star image. The next command after that moves a copy of the newly compiled NextionDriver into place. Then the last command above give a directory listing of the properly placed newly compiled NextionDriver version.
 
The output of file listing above and this last one should match file sizes and dates of compile. Remember here, the file sizes should match, yet, depending on the build version, they both could be a different size then shown. The date will obviously be the date when you compiled the Nextion Driver Code. This is just an example of what you'll see.
 
The "moveIt.sh" script was also downloaded by the "./Scripts/getScripts.sh" and does all 4 of the above commands. If you feel comfortable with the procedures above, the "./Scripts/moveIt.sh" will save some time. The "./Scripts/moveIt.sh" script still shows the file sizes and dates so there can still be a visual comparison of the files on the screen.
 
The above procedures restores the ON7LDS Nextion Display Driver Code, erasing the installed EDDC.
 

Part A4: Changing The Nextion Display Code

 
...This Section Makes Sure That The Nextion Display Firmware Is Updated...
 
root@pi-star(rw):code$ reboot <ENTER KEY>
 
Rebooting will allow the ON7LDS Nextion Display Driver Code, the NDDC to take effect. If you haven't updated the Nextion Display Code on your Nextion Display to the latest Version A;
 
PROPERLY Shut down Pi-Star and Click Here To Update It Now. 
 

Feedback Here Is Important, Getting HELP

 AG4OJ's E-Mail Account
 Our Email Link Is To The Left. So, if you see, or even think you see a mistake, PLEASE send us a short Email with all of the details so We can correct it. Help is always available by this Email address. Further contact can be done by agreed upon phone call. OR send some praises! It's all GOOD to US! TEAM AG4OJ! ENJOY!