Topics

ambeserver failing?

Mike Besemer
 

Still struggling.  Currently getting an Unable to Transmit error from dummyrepeater. 

I went back and looked at ambeserver.  As you can see below, I start ambeserver and immediately check the status.  It appears to start properly.  Then I check the status again less than a minute later and see a failed message.  I dont know if this is what’s causing dummyrepeater to throw the error code, but I dont think this is right.

Mike

WM4B

pi@compass:~ $ sudo systemctl start ambeserver@...

pi@compass:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)

   Active: active (running) since Sat 2019-03-16 16:55:45 EDT; 12s ago

  Process: 2201 ExecStartPre=/bin/chmod 0660 /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

  Process: 2198 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

 Main PID: 2204 (AMBEserver)

   CGroup: /system.slice/system-ambeserver.slice/ambeserver@...

           └─2204 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyAMA0 -r

Mar 16 16:55:45 compass systemd[1]: Starting DV3000 Daemon...

Mar 16 16:55:45 compass systemd[1]: Started DV3000 Daemon.

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Starting...

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

pi@compass:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)

   Active: failed (Result: exit-code) since Sat 2019-03-16 16:56:22 EDT; 22s ago

  Process: 2204 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/ttyAMA0 $AMBESERVER_FLAGS (code=exited, status=1/FAILURE)

  Process: 2201 ExecStartPre=/bin/chmod 0660 /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

  Process: 2198 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

 Main PID: 2204 (code=exited, status=1/FAILURE)

Mar 16 16:55:45 compass systemd[1]: Starting DV3000 Daemon...

Mar 16 16:55:45 compass systemd[1]: Started DV3000 Daemon.

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Starting...

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAILURE

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Unit entered failed state.

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Failed with result 'exit-code'.

pi@compass:~ $


 

Try starting it on the command line, not using the systemctl / service scripts and see if it stays up.

On Sat, Mar 16, 2019 at 2:01 PM Mike Besemer <mwbesemer@...> wrote:

Still struggling.  Currently getting an Unable to Transmit error from dummyrepeater. 

I went back and looked at ambeserver.  As you can see below, I start ambeserver and immediately check the status.  It appears to start properly.  Then I check the status again less than a minute later and see a failed message.  I dont know if this is what’s causing dummyrepeater to throw the error code, but I dont think this is right.

Mike

WM4B

pi@compass:~ $ sudo systemctl start ambeserver@...

pi@compass:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)

   Active: active (running) since Sat 2019-03-16 16:55:45 EDT; 12s ago

  Process: 2201 ExecStartPre=/bin/chmod 0660 /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

  Process: 2198 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

 Main PID: 2204 (AMBEserver)

   CGroup: /system.slice/system-ambeserver.slice/ambeserver@...

           └─2204 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyAMA0 -r

Mar 16 16:55:45 compass systemd[1]: Starting DV3000 Daemon...

Mar 16 16:55:45 compass systemd[1]: Started DV3000 Daemon.

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Starting...

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

pi@compass:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)

   Active: failed (Result: exit-code) since Sat 2019-03-16 16:56:22 EDT; 22s ago

  Process: 2204 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/ttyAMA0 $AMBESERVER_FLAGS (code=exited, status=1/FAILURE)

  Process: 2201 ExecStartPre=/bin/chmod 0660 /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

  Process: 2198 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

 Main PID: 2204 (code=exited, status=1/FAILURE)

Mar 16 16:55:45 compass systemd[1]: Starting DV3000 Daemon...

Mar 16 16:55:45 compass systemd[1]: Started DV3000 Daemon.

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Starting...

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAILURE

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Unit entered failed state.

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Failed with result 'exit-code'.

pi@compass:~ $




--


John D. Hays
Edmonds, WA
K7VE

   

Mike Besemer
 

How do I do that?

 

 

 

From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of John D Hays - K7VE
Sent: Saturday, March 16, 2019 5:33 PM
To: ambe@nw-digital-radio.groups.io
Subject: Re: [ambe] ambeserver failing?

 

Try starting it on the command line, not using the systemctl / service scripts and see if it stays up.

 

On Sat, Mar 16, 2019 at 2:01 PM Mike Besemer <mwbesemer@...> wrote:

Still struggling.  Currently getting an ‘Unable to Transmit’ error from dummyrepeater. 

I went back and looked at ambeserver.  As you can see below, I start ambeserver and immediately check the status.  It appears to start properly.  Then I check the status again less than a minute later and see a ‘failed’ message.  I don’t know if this is what’s causing dummyrepeater to throw the error code, but I don’t think this is right.

Mike

WM4B

pi@compass:~ $ sudo systemctl start ambeserver@...

pi@compass:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)

   Active: active (running) since Sat 2019-03-16 16:55:45 EDT; 12s ago

  Process: 2201 ExecStartPre=/bin/chmod 0660 /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

  Process: 2198 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

 Main PID: 2204 (AMBEserver)

   CGroup: /system.slice/system-ambeserver.slice/ambeserver@...

           └─2204 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyAMA0 -r

Mar 16 16:55:45 compass systemd[1]: Starting DV3000 Daemon...

Mar 16 16:55:45 compass systemd[1]: Started DV3000 Daemon.

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Starting...

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

pi@compass:~ $ sudo systemctl status ambeserver@...

● ambeserver@... - DV3000 Daemon

   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)

   Active: failed (Result: exit-code) since Sat 2019-03-16 16:56:22 EDT; 22s ago

  Process: 2204 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/ttyAMA0 $AMBESERVER_FLAGS (code=exited, status=1/FAILURE)

  Process: 2201 ExecStartPre=/bin/chmod 0660 /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

  Process: 2198 ExecStartPre=/bin/chgrp dialout /dev/ttyAMA0 (code=exited, status=0/SUCCESS)

 Main PID: 2204 (code=exited, status=1/FAILURE)

Mar 16 16:55:45 compass systemd[1]: Starting DV3000 Daemon...

Mar 16 16:55:45 compass systemd[1]: Started DV3000 Daemon.

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Starting...

Mar 16 16:55:45 compass AMBEserver[2204]: AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAILURE

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Unit entered failed state.

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.

Mar 16 16:56:22 compass systemd[1]: ambeserver@...: Failed with result 'exit-code'.

pi@compass:~ $

 


 

--

 


John D. Hays
Edmonds, WA

K7VE

 

   

 

 

Same way as your email of the 12th

Mike Besemer mwbesemer@... via groups.io 

Mar 12, 2019, 5:11 PM (4 days ago)
to ambe

pi@raspberrypi:/usr/sbin $ sudo AMBEserver -i /dev/ttyAMA0

AMBEserver: Starting...

AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.


Leave running in one window and then try your other programs.

--


John D. Hays
Edmonds, WA
K7VE

   

Mike Besemer
 

Well, that’s what I thought, but considering that exactly zero things have worked correctly since I started this project, I thought I’d confirm.

 

So: 

pi@compass:/usr/sbin $ sudo ./AMBEserver  -d -i /dev/ttyAMA0

AMBEserver: Starting...

AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

pi@compass:/usr/sbin $ AMBEserver: Couldn't find start byte in serial data

AMBEserver: error receiving response to reset

AMBEserver: Could not initialize the DV3K!

 

Mike

WM4B

 

From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of John D Hays - K7VE
Sent: Saturday, March 16, 2019 6:31 PM
To: ambe@nw-digital-radio.groups.io
Subject: Re: [ambe] ambeserver failing?

 

Same way as your email of the 12th

 

Mike Besemer mwbesemer@... via groups.io 

Mar 12, 2019, 5:11 PM (4 days ago)

to ambe

pi@raspberrypi:/usr/sbin $ sudo AMBEserver -i /dev/ttyAMA0

AMBEserver: Starting...

AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

 

Leave running in one window and then try your other programs.

 

--

 


John D. Hays
Edmonds, WA

K7VE

 

   

 

 

On Sun, Mar 17, 2019 at 03:52 AM, Mike Besemer wrote:

Well, that’s what I thought, but considering that exactly zero things have worked correctly since I started this project, I thought I’d confirm.

 

So: 

pi@compass:/usr/sbin $ sudo ./AMBEserver  -d -i /dev/ttyAMA0

AMBEserver: Starting...

AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

pi@compass:/usr/sbin $ AMBEserver: Couldn't find start byte in serial data

AMBEserver: error receiving response to reset

AMBEserver: Could not initialize the DV3K!

 

Mike

WM4B

Your DV3K is not  being seen by the operating system, I had to edit a startup file on the pi for it to work. Had the same problem.

 

Mike Besemer
 

I did: 

 

 

$ sudo nano /boot/config.txt

init_uart_clock=3686400

 

 

$ sudo nano /etc/inittab

T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100

with:(or delete the line entirely)

#T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100

(Actually, /etc/inittab does not even exist)

 

 

$ sudo nano /boot/cmdline.txt

dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait

 

What did I miss?

 

Mike

WM4B

 

From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of Ernest Pratt
Sent: Sunday, March 17, 2019 3:43 AM
To: ambe@nw-digital-radio.groups.io
Subject: Re: [ambe] ambeserver failing?

 

On Sun, Mar 17, 2019 at 03:52 AM, Mike Besemer wrote:

Well, that’s what I thought, but considering that exactly zero things have worked correctly since I started this project, I thought I’d confirm.

 

So: 

pi@compass:/usr/sbin $ sudo ./AMBEserver  -d -i /dev/ttyAMA0

AMBEserver: Starting...

AMBEserver: Opened serial port /dev/ttyAMA0 at 230400 bps.

pi@compass:/usr/sbin $ AMBEserver: Couldn't find start byte in serial data

AMBEserver: error receiving response to reset

AMBEserver: Could not initialize the DV3K!

 

Mike

WM4B

Your DV3K is not  being seen by the operating system, I had to edit a startup file on the pi for it to work. Had the same problem.