Now you should be able to make a backup, and when you reflash the SD card, install the nextion driver (without setting the modem up) and then restoring your good settings and it'll work perfectly everytime
Lets see if MMDVMHost and the Nextion driver are spewing things to the serial port.
Go to the Expert configuration and under the [NextionDriver] section
set the LogLevel=6
reboot just to clean up the logs and reset everything.
Then make a call or two to a talkgroup or parrot or something, or just wait for some traffic to whatever talkgroup you park on and then SSH in and type this.
Code: Select all
grep -i NextionDriver /var/log/syslog
Code: Select all
May 10 21:33:58 pi-star2 NextionDriver: TXbuffer is t2.txt="2 Listening" May 10 21:33:58 pi-star2 NextionDriver: 287 strstr(TXbuffer, "t2.txt" is [t2.txt="2 Listening"] May 10 21:33:58 pi-star2 NextionDriver: TX: t2.txt="2 Listening" May 10 21:33:58 pi-star2 NextionDriver: NET: t2.txt="2 Listening" May 10 21:33:58 pi-star2 NextionDriver: LH: check [t2.txt="2 Listening"] on page 2 May 10 21:33:58 pi-star2 NextionDriver: LH: page 2 field 2 is [txt="2 Listening"] May 10 21:33:58 pi-star2 NextionDriver: LH: statusval 72
set the LogLevel=2
Don't forget that step, or you'll fill up the space allocated for the logs.
First check to make sure the serial port is wired correctly. RX on the modem needs to go to TX on the screen, and TX on the modem needs to go to RX on the screen.
You've already said you ran the screen to reset the default baud rate back to 9600, so that is correct.
If it still doesn't work, then I'll have to point the blame on the .tft screen you loaded.
Question, what .HMI are you loading and where did you get it from? Did you create the .tft in the editor yourself? What version of the editor did you use? Theres another user that is mentioning that when he used the latest editor (.58) his screens stopped functioning also. I'll have to admit I was (and still am) highly skeptical of that claim, but if two people are experiencing the same issue, then its something that needs to be taken very seriously as others are going to experience this same issue.
Lets try what he said worked for him.
Download https://nextion.itead.cc/download/nexti ... p-vLTS.zip
Unzip it to a folder and make sure that when you run that exe that the new Nextion editorer isn't currently running or you'll get some DLL errors.
Download a known working .HMI from PD0DIB just for testing
https://github.com/PD0DIB/Nextion_HAM-r ... %208/GLOBE
Load one of those .HMI's for your screen model number and create the .TFT file and side load that and see if things are working correctly.
At this point you can either load the .HMI you had originally wanted into the .53 editor and create a .TFT and try and load that to see if that works or try to load it into the new editor .58 and see if it breaks things again. Either way we are gaining valuable information.