forum.pistar.uk

Hi all

I have a zum radio which has a nextion screen, it connects via modem in pistar all works fine, I then install the driver for the extra data to be passed through, this goes fine and I get the extra data on the screen , the config screen now shows /dev/tty/NextionDriver

My issue is that the D-star network drops after a random amount of time, so no d-star traffic passes, the only way to get it back on line is to reboot.
tried so far
latest pistar image inc both betas
different SD cards
different PSU
different pi's (2 and 3b)
not sure where to look to see where the error would be logged.

thanks
Cliff

Hi
I would have thought the same, as in network connection, but unfortunatly it is 100% the driver, I have a facebook post running and a couple of other have said the same.
so with the driver loaded the modem works 100% and works without issue if I connect it to say REF001C, as there is regular traffic on there. if it is left to go idle for an un known quantity of time maybe an hour or over night without being connected to a reflector, the d-star network in Pi-star will go red and it no longer works on D-star, a reboot fixes the issue.
I am 100% certain that it is when the driver is installed as I left it for over a week just idling, tx-ing the time every hour and nothing else and it no issues, install the driver and within 1/2 a day it has gone red and no more d-star connection..

So my only conclusion is the driver messes with something somewhere and kills d-star, I have no Idea what or where, I wouldnt even know what logs to look at.... currently it is running with out the Nextion driver and has been for 2 days solid since re-imaging and no issues..

More than happy to install driver and capture logs or whatever if somone is capable of diagnosing them, currently running with spots with no data on the nextion screen which will do until this issue can be resolved.
At least I am not the only one now I am getting others saing same thing on the facebook..

thanks

Cliff

and yes that was a typo the /dev/tty/NextionDriver it does say /dev/ttyNextionDriver
And I guess I should say that I also have DMR and YSF enabled along with Dstar

Hi
Nope as I said this is on a ZUM-Radio modem, it has a 32gb card in it and pi-star has been expanded to use it. I do have an error in syslog just as it fails, but surely it cant be running out of space, ?
I'd be very happy if it an easy fix, just had the system running for 24+ hours on a 2gb sd card without the drivers, put in the 16gb on with drivers and failed after about 2 hours... if this is a space issue where is the rest going? just checked and it says 24g free? (df -h)

Feb 2 11:45:29 pi-star NextionDriver: NET: MMDVM.status.val=24
Feb 2 11:45:29 pi-star NextionDriver: LH: check [MMDVM.status.val=24] on page 0
Feb 2 11:45:29 pi-star NextionDriver: NET: click S0,1
Feb 2 11:45:29 pi-star NextionDriver: LH: check [click S0,1] on page 0
Feb 2 11:45:29 pi-star NextionDriver: NET: t2.txt="02/02/20 11:45:29"
Feb 2 11:45:29 pi-star NextionDriver: LH: check [t2.txt="02/02/20 11:45:29"] on page 0
Feb 2 11:45:29 pi-star NextionDriver: LH: page 0 field 2 is [txt="02/02/20 11:45:29"]
Feb 2 11:45:29 pi-star NextionDriver: LH: statusval 24
Feb 2 11:45:29 pi-star NextionDriver: LH Inhibit#012
Feb 2 11:45:29 pi-star rsyslogd: file '10' write error: No space left on device [v8.1901.0 try https://www.rsyslog.com/e/2027 ]
Feb 2 11:45:29 pi-star rsyslogd: action 'action-13-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.1901.0 try https://www.rsyslog.com/e/2027 ]
Feb 2 11:45:29 pi-star rsyslogd: file '10' write error: No space left on device [v8.1901.0 try https://www.rsyslog.com/e/2027 ]
Feb 2 11:45:29 pi-star rsyslogd: action 'action-13-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.1901.0 try https://www.rsyslog.com/e/2027 ]
Feb 2 11:45:29 pi-star rsyslogd: file '10' write error: No space left on device [v8.1901.0 try https://www.rsyslog.com/e/2027 ]
Feb 2 11:45:29 pi-star rsyslogd: action 'action-13-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.1901.0 try https://www.rsyslog.com/e/2027 ]
Feb 2 11:45:29 pi-star rsyslogd: file '10' write error: No space left on device [v8.1901.0 try https://www.rsyslog.com/e/2027 ]
Feb 2 11:45:29 pi-star rsyslogd: action 'action-13-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.1


output from df -h

pi-star@pi-star(ro):~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 29G 3.2G 24G 12% /
devtmpfs 360M 0 360M 0% /dev
tmpfs 488M 0 488M 0% /dev/shm
tmpfs 32M 32M 0 100% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 32M 0 32M 0% /sys/fs/cgroup
tmpfs 1.0M 0 1.0M 0% /var/lib/nginx/body
tmpfs 64M 8.0K 64M 1% /tmp
tmpfs 1.0M 72K 952K 8% /var/cache/samba
tmpfs 64K 0 64K 0% /var/lib/php/sessions
tmpfs 4.0M 2.2M 1.9M 54% /var/lib/samba/private
tmpfs 64M 11M 54M 18% /var/log
tmpfs 16K 0 16K 0% /var/lib/sudo
tmpfs 32K 16K 16K 50% /var/lib/dhcpcd5
tmpfs 16K 4.0K 12K 25% /var/lib/logrotate
/dev/mmcblk0p1 63M 54M 9.9M 85% /boot
tmpfs 98M 0 98M 0% /run/user/1000

I have noticed the /var/log directory is 64m the syslog was 21mb when it failed and the others added another 12mb so less than the 64mb..

So pointers or suggestions, it does look like the nextion driver fills the syslog file with everything... still not sure why it would kill d-star network

thanks

Cliff

Ok
As I have said it is a ZUM Radio, lots of people use them they are used in repeaters and high powered hotspots. It sits on top of the pi and connects out to the radio.. so it's not a regular hotspot
So it stopping working is related to the driver having the wrong log level as standard causing the pi to run out of space.. ask didn't know this was the cause and through the investigation I carried out, it failed when the driver is installed, hence the logical assumption that it is the driver.
And hence posting this issue..the instructions i found on the internet didn't mention log levels.

So I have lowered the log level, glad it was simple
If you would like more info on a zum-radio please let me know

Sorry if this has been asked, but what screen layout are you using? And if it isn't populating the extra fields that the nextion driver provides then perhaps you can re-image and start with a clean install and just use the internal driver provided with pi-star.

Then if this still plays up there's something else causing your problem. I realise that it's a pain to make a fresh start, especially if you have lots of custom settings.

Maybe post a picture of the screen layout because if you are using the same type as me then you might have a similar problem that one of my hotspots does causing the nextion screen to become unresponsive, but that's a different problem to what you're talking about in this thread.

Sent from my Pixel 4 XL using Tapatalk