Re: ThumbDV & RaspiPi runs not stable

Annaliese McDermond
 

The start of every packet from the ThumbDV starts with a 0x61 byte. If AMBEServer cannot find that byte in any of the responses, it errors out. This is usually due to errors in AMBEserver by hand and it’s still running?

--
Annaliese McDermond
nh6z@...

On Mar 24, 2018, at 1:28 AM, anton.weigl@... wrote:

broken again when i wake up this morning (without usage)

pi@compass:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled)
Active: failed (Result: exit-code) since Sat 2018-03-24 09:23:38 CET; 1min 13s ago
Process: 1640 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/%i $AMBESERVER_FLAGS (code=exited, status=1/FAILURE)
Process: 1637 ExecStartPre=/bin/chmod 0660 /dev/%i (code=exited, status=0/SUCCESS)
Process: 1634 ExecStartPre=/bin/chgrp dialout /dev/%i (code=exited, status=0/SUCCESS)
Main PID: 1640 (code=exited, status=1/FAILURE)

Mar 24 02:50:50 compass systemd[1]: Started DV3000 Daemon.
Mar 24 02:50:50 compass AMBEserver[1640]: AMBEserver: Starting...
Mar 24 02:50:50 compass AMBEserver[1640]: AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 bps.
Mar 24 02:50:50 compass AMBEserver[1640]: AMBEserver: Initialized AMBE3000R version V120.E100.XXXX.C106.G514.R009.B0010411.C0020208.
Mar 24 02:50:50 compass AMBEserver[1640]: AMBEserver: Listening for connections on UDP port 2460.
Mar 24 09:23:38 compass AMBEserver[1640]: AMBEserver: Couldn't find start byte in serial data
Mar 24 09:23:38 compass AMBEserver[1640]: AMBEserver: processSerial failed to read packet
Mar 24 09:23:38 compass systemd[1]: ambeserver@...: main process exited, code=exited, status=1/FAILURE
Mar 24 09:23:38 compass systemd[1]: Unit ambeserver@... entered failed state.
Mar 24 09:23:38 compass systemd[1]: Triggering OnFailure= dependencies of ambeserver@....
pi@compass:~ $


any hints?

Join ambe@nw-digital-radio.groups.io to automatically receive all group messages.