Update Notes - History
October 18st, 2019
Return To Download page, link to the left. It's October 18th, 2019. The current revision number is 191018A, all earlier version are now considered archived and obsolete. Use of earlier versions are not recommended due to the ongoing maturity, code changes of the Nextion Display Driver and the MMDVMHost. (Updated for use with Pi-Star/MMDVM Host Versions 3.4.17 (Updated) and 4.1.0RC6 (Updated) under current tests with no problems. Version 1.17 of the ON7LDS GitHub Nextion Driver still being monitored under close scrutiny level testing.)
A. The DMR Page Handler has been updated to handle the rearranged user information fields on both time slots. These changes started in Version 1.16 of the Nextion Display Driver on the ON7LDS GitHub account. I'm watching this closely to make sure I got it all reformatted correctly.
B. If you don't understand the installation instructions to use the newest version of the Nextion Display Driver, I will be posting an instructional guide group of webpages shortly. Sorry, I can only do so much with my limited eyesight problems. I want pictures and such which takes a lot of editing.
C. In this new version of the Nextion Display Driver, v1.17, there is a bug in the new way the driver handles the DMR user information. For example, a CSV entry ... 1234567,XXNXXX,FirstName,,,,COUNTRY, ... The COUNTRY name will be moved up, ripples into the Last Name position, in this example because it's blank, of the defined text strings because of the completely blank fields not being properly handled in the Nextion Display Driver code. This is only a bug, it doesn't break anything, it will just look odd on the display / screen when it happens. This means that it has nothing to do with my display / screen code.
October 6st, 2019
Return To Download page, link to the left. It's October 6th, 2019. The current revision number is 191006A, all earlier version are now considered archived and obsolete. Use of earlier versions are not recommended due to the ongoing maturity, code changes of the Nextion Display Driver and the MMDVMHost (Updated for use with Pi-Star/MMDVM Host Versions 3.4.17 (Updated) and 4.1.0RC6 (Updated) under current tests with no problems).
A. The FLAG CODE has went through another revision, this again for speed, redundant code reduction. This will most probably be the last time this will have to be done.
B. DMR Time Slot Manager has been revised to make sure a switch takes place if the MMDVM Host / NDD fails to send one or the other Time Slot information messages. Or, more so fails to send one of the messages right away. Yeah, this can happen, on very rare occasions. This fixes a failed / slow changing of the display.
C. DMR Page Handler only decodes 1x1, 2x1, 1x2, 1x3, 2x2, and 2x3 callsigns. 7, 8, and 9 digits, DMR IDs and TG#s will now just pass through with no flag decode. Callsign Decode Error will now trigger at the tenth digit.
D. YSF Page Handler now filters the callsign field. As long as the callsign is suffixed by a " ", "/", or a "-" AND it's a 1x1, 2x1, 1x2, 1x3, 2x2, or 2x3 callsign, it will be decoded, Country Name and flag being displayed. (i.e. "AG4OJ BILL", "AG4OJ/BILL", "AG4OJ-BILL") This means that things like "AMERICALNK" will not decode to Spain and Spain's flag anymore. This also means that callsigns all crammed together with no " ", "/", or "-" will not be decoded. SO, "AG4OJBILLY" will not decode AG4OJ as being the Untied States of America with the USA Flag. This is not FOOL PROOF by no means, it just reduces the incorrect decode of other messages being sent in the callsign field of the YSF message stream.
October 1st, 2019
Return To Download page, link to the left. It's October 1st, 2019. The current revision number is 191001A, all earlier version are now considered archived and obsolete. Use of earlier versions are not recommended due to the ongoing maturity, code changes of the Nextion Display Driver and the MMDVMHost (Updated for use with the latest GitHub ON7LDS Nextion Display Driver v1.15. Pi-Star/MMDVM Host Versions 3.4.17 (Updated) and 4.1.0RC6 (Updated) under current tests with no problems).
A. Since this display is driven by a busy serial port at times, timers used to drive this display code have been relaxed to afford more time to process all of the serially sent commands properly. Remember, power supply requirements of bigger displays, your Pi-Zero W/Modem board may handle a 2.4" and 3.5", yet, 4.3" and above could cause all kinds of problems.
Using High Speed Serial settings in Pi-Star can make elusive intermittent problems. High Speed Serial is not necessary for my display code and High Speed Serial has it's own set of additional problems. Like RF interference from the Hotspot MMDVM board, Raspberry Pi board, WIFI/Bluetooth Transmissions, and, even more so, close proximity higher powered transmitters.
Protect (RF Choke), twist the wires together, and RF insulate the back of the display when using the hotspot in High Speed Serial and/or Higher Power RF environments. Also, note here that the displays themselves can emit RF noise that can interfere with other receivers. These displays are meant to be installed into a protective case. Cases that protect the display and protect the environment they operate in.
1. This is a tinkerers platform, iTead Nextion Displays, Raspberry Pis, Raspbian, Pi-Star, MMDVM Host, NDD, etc. ANYTHING at ANYTIME can and will go wrong, just take a deep breath. ANYONE who expects complete perfection, and/or near like, commercial product performance needs to think extra long and hard before buying/building one of these things. Realize the time needed when assemblying, using, and/or trouble shooting one of these things. All of this can be a steep learning curve for any layman.
2. ANYONE making all of these pieces into a commercial product is asking for heavy customer support costs and complaints. Just Saying, In My Humble Opinion, over what I have seen in almost 40 years as a Professional Engineer. If you paid a good price for a commercial product based around these pieces, make sure you get your monies worth of support calls in when you need them, because you will. Something around, about these things are always in flux.
3. I know many of you have PAID a PRICE to own one of these hotspots. Many have bought your own Raspberry Pi Board, MMDVM Modem board, and Display. Some have made their own special holder for it all. You have spent many hours learning how to take care of that little hotspot. So, in turn, since you have done all that hard work, I make the next statement.
4. With all of this being said, I'm still willing to program my screen coded files for everyone cost free. I answer all Emails as soon as I can, Email link at the bottom of this page. Any phone calls must first leave a message, I don't answer/call back unknown phone numbers, EVER.
B. Display of Dual Time Slots for DMR has been added. This was done in a way that no screen space was wasted when one of the Time Slots don't have anything to show. There's no need for two different versions of this code. The code defaults to the first active Time Slot. The Screen Status Images that are shown under the "DMR" logo is also a button, that, when pressed, will switch the active Time Slot being displayed on the screen. (The button turns gray when pressed) The two numbers to the right of the DMR logo/Screen Status Button are Time Slot Status Indicators only.
1. Transmit Priority Over-ride Selection. When a local transmission, like your radio being keyed, received by the hotspot/repeater, the screen code will switch to that Time Slot and display your transmit info on that Time Slot Screen. This will also "LOCK" the Time Slot to your Transmitted Time Slot during the transmission and for 20 seconds afterwards (No matter what the state of either Time Slots are afterwards). IF both Time Slots are being transmitted on into the Hotspot/repeater, then the first Transmitter takes screen priority.
2. Receive Priority Over-ride Selection. When pressing the Screen Status Button under the "DMR" logo, you will select the other Time Slot. The button background will turn gray while pressed showing that you pressed the button. This Time Slot change will then be "LOCKED" to the new Time Slot selection for 10 seconds no matter what the state of either Time Slots are at the time. After 10 seconds it will return to Standard Operating Mode. The Screen Status Button resets the timer and over-rides selected Time Slot every time it is pressed.
3. Standard Operating Mode. Which ever Time Slot is in active "NETWORK" transmission first is the one that will be displayed on the screen. When that Time Slot drops into NETWORK Receive, and the other Time Slot is still in NETWORK Transmission, it will become the displayed Time Slot. When both are in NETWORK Receive, the last one that dropped out of NETWORK Transmission will be the shown Time Slot on the Display. When both Time Slots are in NETWORK Transmission, the first one into that state will be displayed.
4. Time Slot Status Indicators, Screen Status Button colors. Green background with black letters is NETWORK Receive (Waiting for some one to talk). Red background with black letters is NETWORK Transmit (Someone is talking and/or NETWORK "HANG" Time). Red background with white letters is local RF Transmit into the Hotspot/Repeater. (You are, someone is transmitting into the hotspot/repeater locally)
5. So, you say you have a single Time Slot, single Hat MMDVM board. What does all of this mean for you? Well, the 1st Time Slot Indicator will always show a blank gray spot, or, a number 1 with a green background. MMDVM Host still sends out a Time Slot 1 message, even if it's only doing Time Slot 2. This code makes it possible for future hardware upgrades, like a dual hat, without unnecessary display code changes. This means swapping out displays programmed with the same screen code version is made easier.