on7lds / NextionDriver

Driver program to connect MMDVMhost with Nextion Displays, adding extra functionality
33 stars 33 forks source link

Driver Fails to detect display #29

Closed ceilingduster closed 1 year ago

ceilingduster commented 1 year ago

I have a MMDVM_HS_HAT_DUPLEX board (shows 2018 v1.0) that has the 5V, GND and TX connected to a Nextion Display TJC3224T022_011 (5V, GND, RX). Included some pretty pictures of the board. The Nextion Layout files I can't seem to find anywhere... they give the callsign HS9AWO.

attachments: https://imgur.com/a/ktlXjhD

The firmware I was given, worked perfectly, display, YSF, everything until I upgraded the firmware... meaning I don't know what Nextion Driver version was on the OS.

The first thing I did to try and fix was goto pi-star.uk/downloads and grab the latest 4.15 bundle, and flashed it. It boots up, I can configure the YSF again, connect, and everything works fine. However, I get no information on the display.

The next thing I did was install the driver using this repository. I have tried both manually and using the Driver Installer script.

With debugging enabled, the logs would indicate everything is working:

Aug 25 15:40:28 pi-star NextionDriver: Data files directory: /usr/local/etc/ Aug 25 15:40:28 pi-star NextionDriver: Reading groups from /usr/local/etc/groups.txt Aug 25 15:40:28 pi-star NextionDriver: Read 1443 groups. Aug 25 15:40:28 pi-star NextionDriver: Reading users from /usr/local/etc/stripped.csv Aug 25 15:40:28 pi-star NextionDriver: delimiter ',' Aug 25 15:40:28 pi-star NextionDriver: DMRid in field 1 Aug 25 15:40:28 pi-star NextionDriver: Call in field 2 Aug 25 15:40:28 pi-star NextionDriver: Name in field 3 Aug 25 15:40:28 pi-star NextionDriver: Extra data in fields 4,5 and 7 Aug 25 15:40:36 pi-star NextionDriver: Read 145874 users in 3342 ms. Aug 25 15:40:39 pi-star NextionDriver: Sorted CALL table in 1477 ms. Aug 25 15:40:39 pi-star NextionDriver: Disk size : 59856 MB (55636 free) Aug 25 15:40:44 pi-star NextionDriver: IPv4: lo:127.0.0.1 Aug 25 15:40:44 pi-star NextionDriver: IPv4: eth0:172.16.1.137 Aug 25 15:40:44 pi-star NextionDriver: Default interface is : eth0

and debug messagess like:

Aug 25 15:40:44 pi-star NextionDriver: Default interface is : eth0 Aug 25 15:40:44 pi-star NextionDriver: TX: t3.txt="0 eth0:172.16.1.137" Aug 25 15:40:44 pi-star NextionDriver: LH: check [t3.txt="0 eth0:172.16.1.137"] on page 0 Aug 25 15:40:44 pi-star NextionDriver: LH: page 0 field 3 is [txt="0 eth0:172.16.1.137"] Aug 25 15:40:44 pi-star NextionDriver: LH: statusval 0 Aug 25 15:40:44 pi-star NextionDriver: TX: t3.txt="eth0:172.16.1.137" Aug 25 15:40:44 pi-star NextionDriver: LH: check [t3.txt="eth0:172.16.1.137"] on page 0 Aug 25 15:40:44 pi-star NextionDriver: LH: page 0 field 3 is [txt="eth0:172.16.1.137"] Aug 25 15:40:44 pi-star NextionDriver: LH: statusval 0

Aug 25 15:40:39 pi-star NextionDriver: Checking display ... Aug 25 15:40:41 pi-star NextionDriver: Checking display ... Aug 25 15:40:42 pi-star NextionDriver: Checking display ... Aug 25 15:40:43 pi-star NextionDriver: No Nextion display found.

my /etc/mmdvmhost is setup as:

[Nextion] Port=/dev/ttyNextionDriver Brightness=50 DisplayClock=1 UTC=0 ScreenLayout=3 IdleBrightness=20

[NextionDriver] Port=/dev/ttyAMA0 # <---- important DataFilesPath=/usr/local/etc/ LogLevel=4 GroupsFile=groups.txt DMRidFile=stripped.csv

DMRidDelimiter=,

DMRidId=1

DMRidCall=2

DMRidName=3

DMRidX1=4

DMRidX2=5

DMRidX3=7

ShowModeStatus=0 RemoveDim=0 WaitForLan=1 SleepWhenInactive=0

The line port=/dev/ttyAMA0 is the modem. I can confirm that via pistar-findmodem: Detected MMDVM_HS (GPIO): /dev/ttyAMA0 (MMDVM_HS_Dual_Hat-v1.5.2 20201108 14.7456MHz dual ADF7021 FW by CA6JAU GitID #89daa2000650038390000074E52364B)

HOWEVER, If I try to run the NextionDriver, something happens and the system, including pistar-findmodem fails to detect the modem. I don't know what value to put there as /dev/ttyAMA0 is the modem, and the Nextion Display is connected through the modem. If I put a random value in there (of a device that exists such as /dev/modem), MMDVM starts to work again.

ceilingduster commented 1 year ago

Was found to be more of an issue with pi-star and the NextionDriver