Topics

PiDV, AMBEserver and Buster

Mechanical_Mac
 

Ladies and gents,
 
HELP!!
 
Before I pull out the remaining few strands of hair I have left, for the love of God, can someone please tell me what I'm doing wrong? I initially attempted to install my DV3000 on my Raspberry Pi 3 B+ according to the instruction found at:

https://nw-digital-radio.groups.io/g/ambe/wiki/Installing-AMBEserver-on-a-Raspberry-Pi-3-and-PiDV%E2%84%A2
 
Having failed miserably, I followed John's advice at:

https://nw-digital-radio.groups.io/g/ambe/wiki/Installing-AMBEserver-on-a-Raspberry-Pi-3-and-PiDV%E2%84%A2

and attempted to install it using the latest version of Buster and the Quick Build on Linux method outlined at:
https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum
 
Still no success. Any advice much appreciated. Here are the results:
---
login as: pi 
pi@....3's password:
Linux raspberrypi 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l
 
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
 
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Apr 20 14:25:56 2020
pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-04-20 14:25:48 EDT; 4min 33s ago
  Process: 405 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)
 
Apr 20 14:25:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed to determine user credent
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed at step USER spawning /bi
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exite
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 20 14:25:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies
 
pi@raspberrypi:~ $ sudo journalctl -xe
-- Kernel start-up required 1794003 microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 97195633 microseconds.
Apr 20 14:28:44 raspberrypi sshd[857]: Accepted password for pi from 192.168.1.2 port 51407 ssh2
Apr 20 14:28:44 raspberrypi sshd[857]: pam_unix(sshd:session): session opened for user pi by (uid=0)
Apr 20 14:28:44 raspberrypi systemd-logind[297]: New session c3 of user pi.
-- Subject: A new session c3 has been created for user pi
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID c3 has been created for the user pi.
--
-- The leading process of the session is 857.
Apr 20 14:28:44 raspberrypi systemd[1]: Started Session c3 of user pi.
-- Subject: A start job for unit session-c3.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-c3.scope has finished successfully.
--
-- The job identifier is 791.
Apr 20 14:29:53 raspberrypi sudo[848]: pam_unix(sudo:session): session closed for user root
Apr 20 14:30:21 raspberrypi sudo[884]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:30:21 raspberrypi sudo[884]: pam_unix(sudo:session): session opened for user root by pi(ui
Apr 20 14:30:44 raspberrypi sudo[884]: pam_unix(sudo:session): session closed for user root
Apr 20 14:33:51 raspberrypi sudo[896]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:33:52 raspberrypi sudo[896]: pam_unix(sudo:session): session opened for user root by pi(ui
 
pi@raspberrypi:~ $

Clint Heffner
 

That always works for me.  I just use/do it on raspbian. But follows those directions.

I have not been able to do it from the directions you listed.

Clint -- KF8MZ

 

Be advised there are some issues with Buster on Catalina that Anna is looking into.

Bryan K7UDR

Mechanical_Mac
 

Not an issue for me but thanks.

Colin
Colin G. MacArthur B.A., LL.B.


On Mon, Apr 20, 2020 at 4:47 PM Bryan Hoyer <bhhoyer@...> wrote:
Be advised there are some issues with Buster on Catalina that Anna is looking into.

Bryan K7UDR


 

Are you using a PiDV™ or ThumbDV™ the errors look like you are trying a PiDV™

On Mon, Apr 20, 2020 at 1:36 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Ladies and gents,
 
HELP!!
 
Before I pull out the remaining few strands of hair I have left, for the love of God, can someone please tell me what I'm doing wrong? I initially attempted to install my DV3000 on my Raspberry Pi 3 B+ according to the instruction found at:

 
Having failed miserably, I followed John's advice at:


and attempted to install it using the latest version of Buster and the Quick Build on Linux method outlined at:
 
Still no success. Any advice much appreciated. Here are the results:
---
login as: pi 
pi@....3's password:
Linux raspberrypi 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l
 
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
 
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Apr 20 14:25:56 2020
pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-04-20 14:25:48 EDT; 4min 33s ago
  Process: 405 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)
 
Apr 20 14:25:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed to determine user credent
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed at step USER spawning /bi
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exite
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 20 14:25:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies
 
pi@raspberrypi:~ $ sudo journalctl -xe
-- Kernel start-up required 1794003 microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 97195633 microseconds.
Apr 20 14:28:44 raspberrypi sshd[857]: Accepted password for pi from 192.168.1.2 port 51407 ssh2
Apr 20 14:28:44 raspberrypi sshd[857]: pam_unix(sshd:session): session opened for user pi by (uid=0)
Apr 20 14:28:44 raspberrypi systemd-logind[297]: New session c3 of user pi.
-- Subject: A new session c3 has been created for user pi
-- Defined-By: systemd
--
-- A new session with the ID c3 has been created for the user pi.
--
-- The leading process of the session is 857.
Apr 20 14:28:44 raspberrypi systemd[1]: Started Session c3 of user pi.
-- Subject: A start job for unit session-c3.scope has finished successfully
-- Defined-By: systemd
--
-- A start job for unit session-c3.scope has finished successfully.
--
-- The job identifier is 791.
Apr 20 14:29:53 raspberrypi sudo[848]: pam_unix(sudo:session): session closed for user root
Apr 20 14:30:21 raspberrypi sudo[884]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:30:21 raspberrypi sudo[884]: pam_unix(sudo:session): session opened for user root by pi(ui
Apr 20 14:30:44 raspberrypi sudo[884]: pam_unix(sudo:session): session closed for user root
Apr 20 14:33:51 raspberrypi sudo[896]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:33:52 raspberrypi sudo[896]: pam_unix(sudo:session): session opened for user root by pi(ui
 
pi@raspberrypi:~ $



--
John D. Hays
Kingston, WA
K7VE

 

Mike Moore
 

I read the original and the 2 replies.  I just got mine working locally but have not enabled outside connections yet.  I struggled with getting mine working for a week of tries.  I saw the reference to the instructions  https://nw-digital-radio.groups.io/g/ambe/wiki/Installing-AMBEserver-on-a-Raspberry-Pi-3-and-PiDV%E2%84%A2  I have attached a PDF that I downloaded with what eventually worked for me but I originally was using an older Raspberry pi with a single core and believe that was the problem.  When I put  2018-12-31-compass-lite on a 4 core Raspberry Pi and followed the same instructions, Everything worked fine.  I use mostly blue dv on windows.  I have not tried buster with the network arrangement.
73, KC2NM
Mike Moore
mikemoore@...
Cell, Text (585) 721-0011
Google Voice (585) 310-1812




On Mon, Apr 20, 2020 at 4:36 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Ladies and gents,
 
HELP!!
 
Before I pull out the remaining few strands of hair I have left, for the love of God, can someone please tell me what I'm doing wrong? I initially attempted to install my DV3000 on my Raspberry Pi 3 B+ according to the instruction found at:

 
Having failed miserably, I followed John's advice at:


and attempted to install it using the latest version of Buster and the Quick Build on Linux method outlined at:
 
Still no success. Any advice much appreciated. Here are the results:
---
login as: pi 
pi@....3's password:
Linux raspberrypi 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l
 
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
 
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Apr 20 14:25:56 2020
pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-04-20 14:25:48 EDT; 4min 33s ago
  Process: 405 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)
 
Apr 20 14:25:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed to determine user credent
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed at step USER spawning /bi
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exite
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 20 14:25:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies
 
pi@raspberrypi:~ $ sudo journalctl -xe
-- Kernel start-up required 1794003 microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 97195633 microseconds.
Apr 20 14:28:44 raspberrypi sshd[857]: Accepted password for pi from 192.168.1.2 port 51407 ssh2
Apr 20 14:28:44 raspberrypi sshd[857]: pam_unix(sshd:session): session opened for user pi by (uid=0)
Apr 20 14:28:44 raspberrypi systemd-logind[297]: New session c3 of user pi.
-- Subject: A new session c3 has been created for user pi
-- Defined-By: systemd
--
-- A new session with the ID c3 has been created for the user pi.
--
-- The leading process of the session is 857.
Apr 20 14:28:44 raspberrypi systemd[1]: Started Session c3 of user pi.
-- Subject: A start job for unit session-c3.scope has finished successfully
-- Defined-By: systemd
--
-- A start job for unit session-c3.scope has finished successfully.
--
-- The job identifier is 791.
Apr 20 14:29:53 raspberrypi sudo[848]: pam_unix(sudo:session): session closed for user root
Apr 20 14:30:21 raspberrypi sudo[884]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:30:21 raspberrypi sudo[884]: pam_unix(sudo:session): session opened for user root by pi(ui
Apr 20 14:30:44 raspberrypi sudo[884]: pam_unix(sudo:session): session closed for user root
Apr 20 14:33:51 raspberrypi sudo[896]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:33:52 raspberrypi sudo[896]: pam_unix(sudo:session): session opened for user root by pi(ui
 
pi@raspberrypi:~ $

Mechanical_Mac
 

The dv3000 which is now the PiDV as I understand.

Colin
Colin G. MacArthur B.A., LL.B.


On Mon, Apr 20, 2020 at 5:11 PM John D Hays - K7VE <john@...> wrote:
Are you using a PiDV™ or ThumbDV™ the errors look like you are trying a PiDV™

On Mon, Apr 20, 2020 at 1:36 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Ladies and gents,
 
HELP!!
 
Before I pull out the remaining few strands of hair I have left, for the love of God, can someone please tell me what I'm doing wrong? I initially attempted to install my DV3000 on my Raspberry Pi 3 B+ according to the instruction found at:

 
Having failed miserably, I followed John's advice at:


and attempted to install it using the latest version of Buster and the Quick Build on Linux method outlined at:
 
Still no success. Any advice much appreciated. Here are the results:
---
login as: pi 
pi@....3's password:
Linux raspberrypi 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l
 
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
 
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Apr 20 14:25:56 2020
pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-04-20 14:25:48 EDT; 4min 33s ago
  Process: 405 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)
 
Apr 20 14:25:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed to determine user credent
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed at step USER spawning /bi
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exite
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 20 14:25:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies
 
pi@raspberrypi:~ $ sudo journalctl -xe
-- Kernel start-up required 1794003 microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 97195633 microseconds.
Apr 20 14:28:44 raspberrypi sshd[857]: Accepted password for pi from 192.168.1.2 port 51407 ssh2
Apr 20 14:28:44 raspberrypi sshd[857]: pam_unix(sshd:session): session opened for user pi by (uid=0)
Apr 20 14:28:44 raspberrypi systemd-logind[297]: New session c3 of user pi.
-- Subject: A new session c3 has been created for user pi
-- Defined-By: systemd
--
-- A new session with the ID c3 has been created for the user pi.
--
-- The leading process of the session is 857.
Apr 20 14:28:44 raspberrypi systemd[1]: Started Session c3 of user pi.
-- Subject: A start job for unit session-c3.scope has finished successfully
-- Defined-By: systemd
--
-- A start job for unit session-c3.scope has finished successfully.
--
-- The job identifier is 791.
Apr 20 14:29:53 raspberrypi sudo[848]: pam_unix(sudo:session): session closed for user root
Apr 20 14:30:21 raspberrypi sudo[884]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:30:21 raspberrypi sudo[884]: pam_unix(sudo:session): session opened for user root by pi(ui
Apr 20 14:30:44 raspberrypi sudo[884]: pam_unix(sudo:session): session closed for user root
Apr 20 14:33:51 raspberrypi sudo[896]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:33:52 raspberrypi sudo[896]: pam_unix(sudo:session): session opened for user root by pi(ui
 
pi@raspberrypi:~ $



--
John D. Hays
Kingston, WA
K7VE

 

 

OK. So first thing is to make sure the PiDV is properly seated on the pins.
Here is information on using the serial port from the GPIO (turn off console to it) https://www.abelectronics.co.uk/kb/article/1035/raspberry-pi-3--4-and-zero-w-serial-port-usage
Use the ambetest.py program(s) to verify the serial port is communicating with the PiDV HAT.  (Baud Rate is 230K unless the board has been modified).

If it passes all of that, then try the AMBEserver.

Make sure nothing else is installed that might be grabbing the port.  I suggest the current version of Buster and AMBEserver alone to get going.


On Mon, Apr 20, 2020 at 3:33 PM Mechanical_Mac <c.g.macarthur@...> wrote:
The dv3000 which is now the PiDV as I understand.

Colin
Colin G. MacArthur B.A., LL.B.


On Mon, Apr 20, 2020 at 5:11 PM John D Hays - K7VE <john@...> wrote:
Are you using a PiDV™ or ThumbDV™ the errors look like you are trying a PiDV™

On Mon, Apr 20, 2020 at 1:36 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Ladies and gents,
 
HELP!!
 
Before I pull out the remaining few strands of hair I have left, for the love of God, can someone please tell me what I'm doing wrong? I initially attempted to install my DV3000 on my Raspberry Pi 3 B+ according to the instruction found at:

 
Having failed miserably, I followed John's advice at:


and attempted to install it using the latest version of Buster and the Quick Build on Linux method outlined at:
 
Still no success. Any advice much appreciated. Here are the results:
---
login as: pi 
pi@....3's password:
Linux raspberrypi 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l
 
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
 
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Apr 20 14:25:56 2020
pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-04-20 14:25:48 EDT; 4min 33s ago
  Process: 405 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)
 
Apr 20 14:25:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed to determine user credent
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed at step USER spawning /bi
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exite
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 20 14:25:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies
 
pi@raspberrypi:~ $ sudo journalctl -xe
-- Kernel start-up required 1794003 microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 97195633 microseconds.
Apr 20 14:28:44 raspberrypi sshd[857]: Accepted password for pi from 192.168.1.2 port 51407 ssh2
Apr 20 14:28:44 raspberrypi sshd[857]: pam_unix(sshd:session): session opened for user pi by (uid=0)
Apr 20 14:28:44 raspberrypi systemd-logind[297]: New session c3 of user pi.
-- Subject: A new session c3 has been created for user pi
-- Defined-By: systemd
--
-- A new session with the ID c3 has been created for the user pi.
--
-- The leading process of the session is 857.
Apr 20 14:28:44 raspberrypi systemd[1]: Started Session c3 of user pi.
-- Subject: A start job for unit session-c3.scope has finished successfully
-- Defined-By: systemd
--
-- A start job for unit session-c3.scope has finished successfully.
--
-- The job identifier is 791.
Apr 20 14:29:53 raspberrypi sudo[848]: pam_unix(sudo:session): session closed for user root
Apr 20 14:30:21 raspberrypi sudo[884]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:30:21 raspberrypi sudo[884]: pam_unix(sudo:session): session opened for user root by pi(ui
Apr 20 14:30:44 raspberrypi sudo[884]: pam_unix(sudo:session): session closed for user root
Apr 20 14:33:51 raspberrypi sudo[896]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:33:52 raspberrypi sudo[896]: pam_unix(sudo:session): session opened for user root by pi(ui
 
pi@raspberrypi:~ $



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 

Mechanical_Mac
 

John,

I followed the instructions for enabling the mini UART serial port and I disabled the serial console. I modified the AMBESERVER_FLAGS in /etc/opendv/ambeserver-ttyS0.conf to AMBESERVER_FLAGS="-s 230400" to set the baud rate of the DV3000. I left UDP_PORT=2460 unchanged. This is the result.

pi@raspberrypi:~/Downloads $ python ambesocketest.py
^CTraceback (most recent call last):
  File "ambesocketest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt
--
pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; v
   Active: failed (Result: exit-code) since Tue 2020-04-21 14:20:21 ED
  Process: 838 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited

Apr 21 14:20:21 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 21 14:20:21 raspberrypi systemd[838]: ambeserver@...: Fa
Apr 21 14:20:21 raspberrypi systemd[838]: ambeserver@...: Fa
Apr 21 14:20:21 raspberrypi systemd[1]: ambeserver@...: Cont
Apr 21 14:20:21 raspberrypi systemd[1]: ambeserver@...: Fail
Apr 21 14:20:21 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 21 14:20:21 raspberrypi systemd[1]: ambeserver@...: Trig

pi@raspberrypi:~ $ sudo journalctl -xe
Apr 21 14:20:21 raspberrypi sudo[831]: pam_unix(sudo:session): session
Apr 21 14:20:21 raspberrypi systemd[1]: Started Serial Getty on ttyS0.
-- Subject: A start job for unit serial-getty@... has finish
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit serial-getty@... has finished succes
--
-- The job identifier is 665.
Apr 21 14:21:12 raspberrypi sudo[844]:       pi : TTY=pts/0 ; PWD=/hom
Apr 21 14:21:12 raspberrypi sudo[844]: pam_unix(sudo:session): session
Apr 21 14:21:21 raspberrypi sudo[844]: pam_unix(sudo:session): session
Apr 21 14:24:15 raspberrypi sudo[857]:       pi : TTY=pts/0 ; PWD=/hom
Apr 21 14:24:15 raspberrypi sudo[857]: pam_unix(sudo:session): session
Apr 21 14:24:20 raspberrypi sudo[857]: pam_unix(sudo:session): session
Apr 21 14:24:46 raspberrypi sudo[867]:       pi : TTY=pts/0 ; PWD=/hom
Apr 21 14:24:46 raspberrypi sudo[867]: pam_unix(sudo:session): session

pi@raspberrypi:~ $

Colin
Colin G. MacArthur B.A., LL.B.


On Mon, Apr 20, 2020 at 6:58 PM John D Hays - K7VE <john@...> wrote:
OK. So first thing is to make sure the PiDV is properly seated on the pins.
Here is information on using the serial port from the GPIO (turn off console to it) https://www.abelectronics.co.uk/kb/article/1035/raspberry-pi-3--4-and-zero-w-serial-port-usage
Use the ambetest.py program(s) to verify the serial port is communicating with the PiDV HAT.  (Baud Rate is 230K unless the board has been modified).

If it passes all of that, then try the AMBEserver.

Make sure nothing else is installed that might be grabbing the port.  I suggest the current version of Buster and AMBEserver alone to get going.


On Mon, Apr 20, 2020 at 3:33 PM Mechanical_Mac <c.g.macarthur@...> wrote:
The dv3000 which is now the PiDV as I understand.

Colin
Colin G. MacArthur B.A., LL.B.


On Mon, Apr 20, 2020 at 5:11 PM John D Hays - K7VE <john@...> wrote:
Are you using a PiDV™ or ThumbDV™ the errors look like you are trying a PiDV™

On Mon, Apr 20, 2020 at 1:36 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Ladies and gents,
 
HELP!!
 
Before I pull out the remaining few strands of hair I have left, for the love of God, can someone please tell me what I'm doing wrong? I initially attempted to install my DV3000 on my Raspberry Pi 3 B+ according to the instruction found at:

 
Having failed miserably, I followed John's advice at:


and attempted to install it using the latest version of Buster and the Quick Build on Linux method outlined at:
 
Still no success. Any advice much appreciated. Here are the results:
---
login as: pi 
pi@....3's password:
Linux raspberrypi 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l
 
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
 
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Apr 20 14:25:56 2020
pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-04-20 14:25:48 EDT; 4min 33s ago
  Process: 405 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)
 
Apr 20 14:25:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed to determine user credent
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed at step USER spawning /bi
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exite
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 20 14:25:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies
 
pi@raspberrypi:~ $ sudo journalctl -xe
-- Kernel start-up required 1794003 microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 97195633 microseconds.
Apr 20 14:28:44 raspberrypi sshd[857]: Accepted password for pi from 192.168.1.2 port 51407 ssh2
Apr 20 14:28:44 raspberrypi sshd[857]: pam_unix(sshd:session): session opened for user pi by (uid=0)
Apr 20 14:28:44 raspberrypi systemd-logind[297]: New session c3 of user pi.
-- Subject: A new session c3 has been created for user pi
-- Defined-By: systemd
--
-- A new session with the ID c3 has been created for the user pi.
--
-- The leading process of the session is 857.
Apr 20 14:28:44 raspberrypi systemd[1]: Started Session c3 of user pi.
-- Subject: A start job for unit session-c3.scope has finished successfully
-- Defined-By: systemd
--
-- A start job for unit session-c3.scope has finished successfully.
--
-- The job identifier is 791.
Apr 20 14:29:53 raspberrypi sudo[848]: pam_unix(sudo:session): session closed for user root
Apr 20 14:30:21 raspberrypi sudo[884]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:30:21 raspberrypi sudo[884]: pam_unix(sudo:session): session opened for user root by pi(ui
Apr 20 14:30:44 raspberrypi sudo[884]: pam_unix(sudo:session): session closed for user root
Apr 20 14:33:51 raspberrypi sudo[896]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:33:52 raspberrypi sudo[896]: pam_unix(sudo:session): session opened for user root by pi(ui
 
pi@raspberrypi:~ $



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 

Mechanical_Mac
 

Mike, 

I tried with the Compass distro and got nowhere but I might try it again now that I'm aware of the serial port issues.

Colin
Colin G. MacArthur B.A., LL.B.


On Mon, Apr 20, 2020 at 5:19 PM Mike Moore <mikemoore@...> wrote:
I read the original and the 2 replies.  I just got mine working locally but have not enabled outside connections yet.  I struggled with getting mine working for a week of tries.  I saw the reference to the instructions  https://nw-digital-radio.groups.io/g/ambe/wiki/Installing-AMBEserver-on-a-Raspberry-Pi-3-and-PiDV%E2%84%A2  I have attached a PDF that I downloaded with what eventually worked for me but I originally was using an older Raspberry pi with a single core and believe that was the problem.  When I put  2018-12-31-compass-lite on a 4 core Raspberry Pi and followed the same instructions, Everything worked fine.  I use mostly blue dv on windows.  I have not tried buster with the network arrangement.
73, KC2NM
Mike Moore
mikemoore@...
Cell, Text (585) 721-0011
Google Voice (585) 310-1812




On Mon, Apr 20, 2020 at 4:36 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Ladies and gents,
 
HELP!!
 
Before I pull out the remaining few strands of hair I have left, for the love of God, can someone please tell me what I'm doing wrong? I initially attempted to install my DV3000 on my Raspberry Pi 3 B+ according to the instruction found at:

 
Having failed miserably, I followed John's advice at:


and attempted to install it using the latest version of Buster and the Quick Build on Linux method outlined at:
 
Still no success. Any advice much appreciated. Here are the results:
---
login as: pi 
pi@....3's password:
Linux raspberrypi 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l
 
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
 
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Apr 20 14:25:56 2020
pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-04-20 14:25:48 EDT; 4min 33s ago
  Process: 405 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)
 
Apr 20 14:25:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed to determine user credent
Apr 20 14:25:48 raspberrypi systemd[405]: ambeserver@...: Failed at step USER spawning /bi
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exite
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 20 14:25:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 20 14:25:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies
 
pi@raspberrypi:~ $ sudo journalctl -xe
-- Kernel start-up required 1794003 microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 97195633 microseconds.
Apr 20 14:28:44 raspberrypi sshd[857]: Accepted password for pi from 192.168.1.2 port 51407 ssh2
Apr 20 14:28:44 raspberrypi sshd[857]: pam_unix(sshd:session): session opened for user pi by (uid=0)
Apr 20 14:28:44 raspberrypi systemd-logind[297]: New session c3 of user pi.
-- Subject: A new session c3 has been created for user pi
-- Defined-By: systemd
--
-- A new session with the ID c3 has been created for the user pi.
--
-- The leading process of the session is 857.
Apr 20 14:28:44 raspberrypi systemd[1]: Started Session c3 of user pi.
-- Subject: A start job for unit session-c3.scope has finished successfully
-- Defined-By: systemd
--
-- A start job for unit session-c3.scope has finished successfully.
--
-- The job identifier is 791.
Apr 20 14:29:53 raspberrypi sudo[848]: pam_unix(sudo:session): session closed for user root
Apr 20 14:30:21 raspberrypi sudo[884]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:30:21 raspberrypi sudo[884]: pam_unix(sudo:session): session opened for user root by pi(ui
Apr 20 14:30:44 raspberrypi sudo[884]: pam_unix(sudo:session): session closed for user root
Apr 20 14:33:51 raspberrypi sudo[896]:       pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bi
Apr 20 14:33:52 raspberrypi sudo[896]: pam_unix(sudo:session): session opened for user root by pi(ui
 
pi@raspberrypi:~ $

 

You need to take a step wise approach to debug:

1. Make sure the HAT is properly seated.  

Orient it so that it is sitting on pins 1-26, here is an illustration on a 40 pin GPIO Raspberry Pi
image.png

Use a current version of Raspbian (Compass Linux is deprecated)
Build/Install ambeserver
Do Not Start amberserver until you confirm that the PiDV is communicating with the Raspberry Pi

Use the test program from 
sudo python AMBEtest3.py -i /dev/ttyS0

If this fails, then you may have a hardware problem.  On success, then test in foreground (not as daemon, don't use systemctl yet)

sudo AMBEserver -i /dev/ttyS0

Watch for errors, and then open a second terminal window and use:

python ambesocktest.py

If the ambesocktest works, then you can kill the AMBEserver and restart it with systemctl.
My lab is down at the moment so I am unable to do hands on build and document.  

--
John D. Hays
Kingston, WA
K7VE

 

Mechanical_Mac
 

Thanks John, I really appreciate your assistance.

The PIDV is definitely installed correctly on the Raspberry Pi, starting at PIN 1.
I always start with a fresh install of the latest version of Raspbian, now Buster.
I didn't get very far. The following steps were done sequentially.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ambeserver
e:  unable to locate package ambeserver

I searched the raspbian package list for ambeserver without success. 

Any suggestions?
 
Colin
Colin G. MacArthur B.A., LL.B.


On Wed, Apr 22, 2020 at 1:01 AM John D Hays - K7VE <john@...> wrote:
You need to take a step wise approach to debug:

1. Make sure the HAT is properly seated.  

Orient it so that it is sitting on pins 1-26, here is an illustration on a 40 pin GPIO Raspberry Pi
image.png

Use a current version of Raspbian (Compass Linux is deprecated)
Build/Install ambeserver
Do Not Start amberserver until you confirm that the PiDV is communicating with the Raspberry Pi

Use the test program from 
sudo python AMBEtest3.py -i /dev/ttyS0

If this fails, then you may have a hardware problem.  On success, then test in foreground (not as daemon, don't use systemctl yet)

sudo AMBEserver -i /dev/ttyS0

Watch for errors, and then open a second terminal window and use:

python ambesocktest.py

If the ambesocktest works, then you can kill the AMBEserver and restart it with systemctl.
My lab is down at the moment so I am unable to do hands on build and document.  

--
John D. Hays
Kingston, WA
K7VE

 

 

You probably need to build AMBEserver it is not on the standard repositories. 



On Wed, Apr 22, 2020, 19:25 Mechanical_Mac <c.g.macarthur@...> wrote:
Thanks John, I really appreciate your assistance.

The PIDV is definitely installed correctly on the Raspberry Pi, starting at PIN 1.
I always start with a fresh install of the latest version of Raspbian, now Buster.
I didn't get very far. The following steps were done sequentially.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ambeserver
e:  unable to locate package ambeserver

I searched the raspbian package list for ambeserver without success. 

Any suggestions?
 
Colin
Colin G. MacArthur B.A., LL.B.


On Wed, Apr 22, 2020 at 1:01 AM John D Hays - K7VE <john@...> wrote:
You need to take a step wise approach to debug:

1. Make sure the HAT is properly seated.  

Orient it so that it is sitting on pins 1-26, here is an illustration on a 40 pin GPIO Raspberry Pi
image.png

Use a current version of Raspbian (Compass Linux is deprecated)
Build/Install ambeserver
Do Not Start amberserver until you confirm that the PiDV is communicating with the Raspberry Pi

Use the test program from 
sudo python AMBEtest3.py -i /dev/ttyS0

If this fails, then you may have a hardware problem.  On success, then test in foreground (not as daemon, don't use systemctl yet)

sudo AMBEserver -i /dev/ttyS0

Watch for errors, and then open a second terminal window and use:

python ambesocktest.py

If the ambesocktest works, then you can kill the AMBEserver and restart it with systemctl.
My lab is down at the moment so I am unable to do hands on build and document.  

--
John D. Hays
Kingston, WA
K7VE

 

 

Here are short instructions.
From  https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum#Quick-Build-on-Linux  

Quick Build on Linux

If you cannot find an AMBEserver package for your architecture and distribution. Try this:

wget https://raw.githubusercontent.com/dl5di/OpenDV/master/DummyRepeater/DV3000/AMBEserver.c
Open https://github.com/dl5di/OpenDV/blob/master/DummyRepeater/DV3000/AMBEserver.c
select "RAW"
Copy and past the source code into AMBEserver.  Or just use the attached copy.

gcc -o AMBEserver AMBEserver.c
Place the executable in an appropriate place, and create configuration and autostart files.  On Raspbian/Debian this would be
sudo cp AMBEserver /usr/sbin
sudo chmod +x /usr/sbin/AMBEserver
 
A set of files for systemd management are located in the files section: ambesupport.tgz (https://nw-digital-radio.groups.io/g/ambe/files)

Download this file to the target computer's filesystem and run 
mv ambesupport.tgz /tmp &&  cd / && sudo tar -xzvf /tmp/ambesupport.tgz

Use the above instructions to manage the server.  (From the WIKI article)
 
The test programs (python) can be obtained here  https://github.com/dl5di/OpenDV/tree/master/DummyRepeater/DV3000 
Open AMBEtest3.py go to raw and copy and paste to similarly named file (Attached)
  Open ambesocktest.py go to raw and copy and paste to similarly named file  or download this one from  https://nw-digital-radio.groups.io/g/ambe/files  

Run the tests I mentioned earlier


On Wed, Apr 22, 2020 at 7:57 PM John D Hays - K7VE via groups.io <john=hays.org@groups.io> wrote:
You probably need to build AMBEserver it is not on the standard repositories. 



On Wed, Apr 22, 2020, 19:25 Mechanical_Mac <c.g.macarthur@...> wrote:
Thanks John, I really appreciate your assistance.

The PIDV is definitely installed correctly on the Raspberry Pi, starting at PIN 1.
I always start with a fresh install of the latest version of Raspbian, now Buster.
I didn't get very far. The following steps were done sequentially.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ambeserver
e:  unable to locate package ambeserver

I searched the raspbian package list for ambeserver without success. 

Any suggestions?
 
Colin
Colin G. MacArthur B.A., LL.B.


On Wed, Apr 22, 2020 at 1:01 AM John D Hays - K7VE <john@...> wrote:
You need to take a step wise approach to debug:

1. Make sure the HAT is properly seated.  

Orient it so that it is sitting on pins 1-26, here is an illustration on a 40 pin GPIO Raspberry Pi
image.png

Use a current version of Raspbian (Compass Linux is deprecated)
Build/Install ambeserver
Do Not Start amberserver until you confirm that the PiDV is communicating with the Raspberry Pi

Use the test program from 
sudo python AMBEtest3.py -i /dev/ttyS0

If this fails, then you may have a hardware problem.  On success, then test in foreground (not as daemon, don't use systemctl yet)

sudo AMBEserver -i /dev/ttyS0

Watch for errors, and then open a second terminal window and use:

python ambesocktest.py

If the ambesocktest works, then you can kill the AMBEserver and restart it with systemctl.
My lab is down at the moment so I am unable to do hands on build and document.  

--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 

 

I verified that AMBEserver will build on Buster Raspbian, I don't have a PiDV to test with at the moment.
--
John D. Hays
Kingston, WA
K7VE

 

Mechanical_Mac
 

Hi John,

I followed your instructions word for word. Results below.

sudo python AMBEtest3.py -i /dev/ttyS0
pi@raspberrypi:~ $ sudo python AMBEtest3.py -i /dev/ttyS0
AMBEtest3.py -s <serial port>
AMBEtest3.py -n -s <serial port> (for ThumbDV Model A
pi@raspberrypi:~ $ python ambesocktest.py
^CTraceback (most recent call last):
  File "ambesocktest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt

Same command but substituted -s flag and promising results.
pi@raspberrypi:~ $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes
a9
Product ID
6100010030
Wrote: 5 bytes
a
 0AMBE3000R
Version
6100010031
Wrote: 5 bytes
a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

Then ran this command, things look like they're working as expected.
pi@raspberrypi:~ $ sudo AMBEserver -i /dev/ttyS0
AMBEserver: Starting...
AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
AMBEserver: Initialized AMBE3000R version V120.E100.XXXX.C106.G514.R009.B0010411.C0020208.
AMBEserver: Listening for connections on UDP port 2460.
Finally I tried the socket tests
python ambesocketest.py
                0AMBE3000R
Server reply : a
                0AMBE3000R
Server reply : a
                0AMBE3000R
^CTraceback (most recent call last):
  File "ambesocketest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt

Hallelujah! The first positive news of the quarantine.

So then I tried:
pi@raspberrypi:~ $ sudo systemctl enable ambeserver@...
Created symlink /etc/systemd/system/multi-user.target.wants/ambeserver@... → /lib/systemd/system/ambeserver@.service.
pi@raspberrypi:~ $

No visible errors so I assumed it was enabled. I rebooted and tried:
sudo systemctl status ambeserver@...

pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-04-24 15:05:48 EDT; 8min ago
  Process: 403 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)

Apr 24 15:05:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 24 15:05:48 raspberrypi systemd[403]: ambeserver@...: Failed to determine user credentials: No such process
Apr 24 15:05:48 raspberrypi systemd[403]: ambeserver@...: Failed at step USER spawning /bin/chgrp: No such process
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exited, status=217/USER
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 24 15:05:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
pi@raspberrypi:~ $

Damn! So close. So I don't know what to make of that.

Colin
Colin G. MacArthur B.A., LL.B.


On Thu, Apr 23, 2020 at 1:19 AM John D Hays - K7VE <john@...> wrote:
Here are short instructions.
From  https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum#Quick-Build-on-Linux  

Quick Build on Linux

If you cannot find an AMBEserver package for your architecture and distribution. Try this:

wget https://raw.githubusercontent.com/dl5di/OpenDV/master/DummyRepeater/DV3000/AMBEserver.c
Open https://github.com/dl5di/OpenDV/blob/master/DummyRepeater/DV3000/AMBEserver.c
select "RAW"
Copy and past the source code into AMBEserver.  Or just use the attached copy.

gcc -o AMBEserver AMBEserver.c
Place the executable in an appropriate place, and create configuration and autostart files.  On Raspbian/Debian this would be
sudo cp AMBEserver /usr/sbin
sudo chmod +x /usr/sbin/AMBEserver
 
A set of files for systemd management are located in the files section: ambesupport.tgz (https://nw-digital-radio.groups.io/g/ambe/files)

Download this file to the target computer's filesystem and run 
mv ambesupport.tgz /tmp &&  cd / && sudo tar -xzvf /tmp/ambesupport.tgz

Use the above instructions to manage the server.  (From the WIKI article)
 
The test programs (python) can be obtained here  https://github.com/dl5di/OpenDV/tree/master/DummyRepeater/DV3000 
Open AMBEtest3.py go to raw and copy and paste to similarly named file (Attached)
  Open ambesocktest.py go to raw and copy and paste to similarly named file  or download this one from  https://nw-digital-radio.groups.io/g/ambe/files  

Run the tests I mentioned earlier


On Wed, Apr 22, 2020 at 7:57 PM John D Hays - K7VE via groups.io <john=hays.org@groups.io> wrote:
You probably need to build AMBEserver it is not on the standard repositories. 



On Wed, Apr 22, 2020, 19:25 Mechanical_Mac <c.g.macarthur@...> wrote:
Thanks John, I really appreciate your assistance.

The PIDV is definitely installed correctly on the Raspberry Pi, starting at PIN 1.
I always start with a fresh install of the latest version of Raspbian, now Buster.
I didn't get very far. The following steps were done sequentially.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ambeserver
e:  unable to locate package ambeserver

I searched the raspbian package list for ambeserver without success. 

Any suggestions?
 
Colin
Colin G. MacArthur B.A., LL.B.


On Wed, Apr 22, 2020 at 1:01 AM John D Hays - K7VE <john@...> wrote:
You need to take a step wise approach to debug:

1. Make sure the HAT is properly seated.  

Orient it so that it is sitting on pins 1-26, here is an illustration on a 40 pin GPIO Raspberry Pi
image.png

Use a current version of Raspbian (Compass Linux is deprecated)
Build/Install ambeserver
Do Not Start amberserver until you confirm that the PiDV is communicating with the Raspberry Pi

Use the test program from 
sudo python AMBEtest3.py -i /dev/ttyS0

If this fails, then you may have a hardware problem.  On success, then test in foreground (not as daemon, don't use systemctl yet)

sudo AMBEserver -i /dev/ttyS0

Watch for errors, and then open a second terminal window and use:

python ambesocktest.py

If the ambesocktest works, then you can kill the AMBEserver and restart it with systemctl.
My lab is down at the moment so I am unable to do hands on build and document.  

--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 

 

Those are very good results.  It looks like a permission problem, as I stated in another thread.

As I stated, I don't have access to a PiDV™ at the moment (packed away during an extended house move), but I will try on a ThumbDV™ when I get a minute.  It may be something faulty in the service file.



On Fri, Apr 24, 2020 at 1:16 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Hi John,

I followed your instructions word for word. Results below.

sudo python AMBEtest3.py -i /dev/ttyS0
pi@raspberrypi:~ $ sudo python AMBEtest3.py -i /dev/ttyS0
AMBEtest3.py -s <serial port>
AMBEtest3.py -n -s <serial port> (for ThumbDV Model A
pi@raspberrypi:~ $ python ambesocktest.py
^CTraceback (most recent call last):
  File "ambesocktest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt

Same command but substituted -s flag and promising results.
pi@raspberrypi:~ $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes
a9
Product ID
6100010030
Wrote: 5 bytes
a
 0AMBE3000R
Version
6100010031
Wrote: 5 bytes
a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

Then ran this command, things look like they're working as expected.
pi@raspberrypi:~ $ sudo AMBEserver -i /dev/ttyS0
AMBEserver: Starting...
AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
AMBEserver: Initialized AMBE3000R version V120.E100.XXXX.C106.G514.R009.B0010411.C0020208.
AMBEserver: Listening for connections on UDP port 2460.
Finally I tried the socket tests
python ambesocketest.py
                0AMBE3000R
Server reply : a
                0AMBE3000R
Server reply : a
                0AMBE3000R
^CTraceback (most recent call last):
  File "ambesocketest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt

Hallelujah! The first positive news of the quarantine.

So then I tried:
pi@raspberrypi:~ $ sudo systemctl enable ambeserver@...
Created symlink /etc/systemd/system/multi-user.target.wants/ambeserver@... → /lib/systemd/system/ambeserver@.service.
pi@raspberrypi:~ $

No visible errors so I assumed it was enabled. I rebooted and tried:
sudo systemctl status ambeserver@...

pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-04-24 15:05:48 EDT; 8min ago
  Process: 403 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)

Apr 24 15:05:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 24 15:05:48 raspberrypi systemd[403]: ambeserver@...: Failed to determine user credentials: No such process
Apr 24 15:05:48 raspberrypi systemd[403]: ambeserver@...: Failed at step USER spawning /bin/chgrp: No such process
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exited, status=217/USER
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 24 15:05:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
pi@raspberrypi:~ $

Damn! So close. So I don't know what to make of that.

Colin
Colin G. MacArthur B.A., LL.B.


On Thu, Apr 23, 2020 at 1:19 AM John D Hays - K7VE <john@...> wrote:
Here are short instructions.
From  https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum#Quick-Build-on-Linux  

Quick Build on Linux

If you cannot find an AMBEserver package for your architecture and distribution. Try this:

wget https://raw.githubusercontent.com/dl5di/OpenDV/master/DummyRepeater/DV3000/AMBEserver.c
Open https://github.com/dl5di/OpenDV/blob/master/DummyRepeater/DV3000/AMBEserver.c
select "RAW"
Copy and past the source code into AMBEserver.  Or just use the attached copy.

gcc -o AMBEserver AMBEserver.c
Place the executable in an appropriate place, and create configuration and autostart files.  On Raspbian/Debian this would be
sudo cp AMBEserver /usr/sbin
sudo chmod +x /usr/sbin/AMBEserver
 
A set of files for systemd management are located in the files section: ambesupport.tgz (https://nw-digital-radio.groups.io/g/ambe/files)

Download this file to the target computer's filesystem and run 
mv ambesupport.tgz /tmp &&  cd / && sudo tar -xzvf /tmp/ambesupport.tgz

Use the above instructions to manage the server.  (From the WIKI article)
 
The test programs (python) can be obtained here  https://github.com/dl5di/OpenDV/tree/master/DummyRepeater/DV3000 
Open AMBEtest3.py go to raw and copy and paste to similarly named file (Attached)
  Open ambesocktest.py go to raw and copy and paste to similarly named file  or download this one from  https://nw-digital-radio.groups.io/g/ambe/files  

Run the tests I mentioned earlier


On Wed, Apr 22, 2020 at 7:57 PM John D Hays - K7VE via groups.io <john=hays.org@groups.io> wrote:
You probably need to build AMBEserver it is not on the standard repositories. 



On Wed, Apr 22, 2020, 19:25 Mechanical_Mac <c.g.macarthur@...> wrote:
Thanks John, I really appreciate your assistance.

The PIDV is definitely installed correctly on the Raspberry Pi, starting at PIN 1.
I always start with a fresh install of the latest version of Raspbian, now Buster.
I didn't get very far. The following steps were done sequentially.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ambeserver
e:  unable to locate package ambeserver

I searched the raspbian package list for ambeserver without success. 

Any suggestions?
 
Colin
Colin G. MacArthur B.A., LL.B.


On Wed, Apr 22, 2020 at 1:01 AM John D Hays - K7VE <john@...> wrote:
You need to take a step wise approach to debug:

1. Make sure the HAT is properly seated.  

Orient it so that it is sitting on pins 1-26, here is an illustration on a 40 pin GPIO Raspberry Pi
image.png

Use a current version of Raspbian (Compass Linux is deprecated)
Build/Install ambeserver
Do Not Start amberserver until you confirm that the PiDV is communicating with the Raspberry Pi

Use the test program from 
sudo python AMBEtest3.py -i /dev/ttyS0

If this fails, then you may have a hardware problem.  On success, then test in foreground (not as daemon, don't use systemctl yet)

sudo AMBEserver -i /dev/ttyS0

Watch for errors, and then open a second terminal window and use:

python ambesocktest.py

If the ambesocktest works, then you can kill the AMBEserver and restart it with systemctl.
My lab is down at the moment so I am unable to do hands on build and document.  

--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 

Mechanical_Mac
 

Thank you very much John, I really appreciate your help. No need to rush, I'm not going anywhere.

Colin
Colin G. MacArthur B.A., LL.B.


On Fri, Apr 24, 2020 at 4:50 PM John D Hays - K7VE <john@...> wrote:
Those are very good results.  It looks like a permission problem, as I stated in another thread.

As I stated, I don't have access to a PiDV™ at the moment (packed away during an extended house move), but I will try on a ThumbDV™ when I get a minute.  It may be something faulty in the service file.



On Fri, Apr 24, 2020 at 1:16 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Hi John,

I followed your instructions word for word. Results below.

sudo python AMBEtest3.py -i /dev/ttyS0
pi@raspberrypi:~ $ sudo python AMBEtest3.py -i /dev/ttyS0
AMBEtest3.py -s <serial port>
AMBEtest3.py -n -s <serial port> (for ThumbDV Model A
pi@raspberrypi:~ $ python ambesocktest.py
^CTraceback (most recent call last):
  File "ambesocktest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt

Same command but substituted -s flag and promising results.
pi@raspberrypi:~ $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes
a9
Product ID
6100010030
Wrote: 5 bytes
a
 0AMBE3000R
Version
6100010031
Wrote: 5 bytes
a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

Then ran this command, things look like they're working as expected.
pi@raspberrypi:~ $ sudo AMBEserver -i /dev/ttyS0
AMBEserver: Starting...
AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
AMBEserver: Initialized AMBE3000R version V120.E100.XXXX.C106.G514.R009.B0010411.C0020208.
AMBEserver: Listening for connections on UDP port 2460.
Finally I tried the socket tests
python ambesocketest.py
                0AMBE3000R
Server reply : a
                0AMBE3000R
Server reply : a
                0AMBE3000R
^CTraceback (most recent call last):
  File "ambesocketest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt

Hallelujah! The first positive news of the quarantine.

So then I tried:
pi@raspberrypi:~ $ sudo systemctl enable ambeserver@...
Created symlink /etc/systemd/system/multi-user.target.wants/ambeserver@... → /lib/systemd/system/ambeserver@.service.
pi@raspberrypi:~ $

No visible errors so I assumed it was enabled. I rebooted and tried:
sudo systemctl status ambeserver@...

pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-04-24 15:05:48 EDT; 8min ago
  Process: 403 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)

Apr 24 15:05:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 24 15:05:48 raspberrypi systemd[403]: ambeserver@...: Failed to determine user credentials: No such process
Apr 24 15:05:48 raspberrypi systemd[403]: ambeserver@...: Failed at step USER spawning /bin/chgrp: No such process
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exited, status=217/USER
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 24 15:05:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
pi@raspberrypi:~ $

Damn! So close. So I don't know what to make of that.

Colin
Colin G. MacArthur B.A., LL.B.


On Thu, Apr 23, 2020 at 1:19 AM John D Hays - K7VE <john@...> wrote:
Here are short instructions.
From  https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum#Quick-Build-on-Linux  

Quick Build on Linux

If you cannot find an AMBEserver package for your architecture and distribution. Try this:

wget https://raw.githubusercontent.com/dl5di/OpenDV/master/DummyRepeater/DV3000/AMBEserver.c
Open https://github.com/dl5di/OpenDV/blob/master/DummyRepeater/DV3000/AMBEserver.c
select "RAW"
Copy and past the source code into AMBEserver.  Or just use the attached copy.

gcc -o AMBEserver AMBEserver.c
Place the executable in an appropriate place, and create configuration and autostart files.  On Raspbian/Debian this would be
sudo cp AMBEserver /usr/sbin
sudo chmod +x /usr/sbin/AMBEserver
 
A set of files for systemd management are located in the files section: ambesupport.tgz (https://nw-digital-radio.groups.io/g/ambe/files)

Download this file to the target computer's filesystem and run 
mv ambesupport.tgz /tmp &&  cd / && sudo tar -xzvf /tmp/ambesupport.tgz

Use the above instructions to manage the server.  (From the WIKI article)
 
The test programs (python) can be obtained here  https://github.com/dl5di/OpenDV/tree/master/DummyRepeater/DV3000 
Open AMBEtest3.py go to raw and copy and paste to similarly named file (Attached)
  Open ambesocktest.py go to raw and copy and paste to similarly named file  or download this one from  https://nw-digital-radio.groups.io/g/ambe/files  

Run the tests I mentioned earlier


On Wed, Apr 22, 2020 at 7:57 PM John D Hays - K7VE via groups.io <john=hays.org@groups.io> wrote:
You probably need to build AMBEserver it is not on the standard repositories. 



On Wed, Apr 22, 2020, 19:25 Mechanical_Mac <c.g.macarthur@...> wrote:
Thanks John, I really appreciate your assistance.

The PIDV is definitely installed correctly on the Raspberry Pi, starting at PIN 1.
I always start with a fresh install of the latest version of Raspbian, now Buster.
I didn't get very far. The following steps were done sequentially.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ambeserver
e:  unable to locate package ambeserver

I searched the raspbian package list for ambeserver without success. 

Any suggestions?
 
Colin
Colin G. MacArthur B.A., LL.B.


On Wed, Apr 22, 2020 at 1:01 AM John D Hays - K7VE <john@...> wrote:
You need to take a step wise approach to debug:

1. Make sure the HAT is properly seated.  

Orient it so that it is sitting on pins 1-26, here is an illustration on a 40 pin GPIO Raspberry Pi
image.png

Use a current version of Raspbian (Compass Linux is deprecated)
Build/Install ambeserver
Do Not Start amberserver until you confirm that the PiDV is communicating with the Raspberry Pi

Use the test program from 
sudo python AMBEtest3.py -i /dev/ttyS0

If this fails, then you may have a hardware problem.  On success, then test in foreground (not as daemon, don't use systemctl yet)

sudo AMBEserver -i /dev/ttyS0

Watch for errors, and then open a second terminal window and use:

python ambesocktest.py

If the ambesocktest works, then you can kill the AMBEserver and restart it with systemctl.
My lab is down at the moment so I am unable to do hands on build and document.  

--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 

 

You man need this on Buster

sudo usermod -G dialout opendv
Then try starting AMBEserver again.


On Fri, Apr 24, 2020 at 3:32 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Thank you very much John, I really appreciate your help. No need to rush, I'm not going anywhere.

Colin
Colin G. MacArthur B.A., LL.B.


On Fri, Apr 24, 2020 at 4:50 PM John D Hays - K7VE <john@...> wrote:
Those are very good results.  It looks like a permission problem, as I stated in another thread.

As I stated, I don't have access to a PiDV™ at the moment (packed away during an extended house move), but I will try on a ThumbDV™ when I get a minute.  It may be something faulty in the service file.



On Fri, Apr 24, 2020 at 1:16 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Hi John,

I followed your instructions word for word. Results below.

sudo python AMBEtest3.py -i /dev/ttyS0
pi@raspberrypi:~ $ sudo python AMBEtest3.py -i /dev/ttyS0
AMBEtest3.py -s <serial port>
AMBEtest3.py -n -s <serial port> (for ThumbDV Model A
pi@raspberrypi:~ $ python ambesocktest.py
^CTraceback (most recent call last):
  File "ambesocktest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt

Same command but substituted -s flag and promising results.
pi@raspberrypi:~ $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes
a9
Product ID
6100010030
Wrote: 5 bytes
a
 0AMBE3000R
Version
6100010031
Wrote: 5 bytes
a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

Then ran this command, things look like they're working as expected.
pi@raspberrypi:~ $ sudo AMBEserver -i /dev/ttyS0
AMBEserver: Starting...
AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
AMBEserver: Initialized AMBE3000R version V120.E100.XXXX.C106.G514.R009.B0010411.C0020208.
AMBEserver: Listening for connections on UDP port 2460.
Finally I tried the socket tests
python ambesocketest.py
                0AMBE3000R
Server reply : a
                0AMBE3000R
Server reply : a
                0AMBE3000R
^CTraceback (most recent call last):
  File "ambesocketest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt

Hallelujah! The first positive news of the quarantine.

So then I tried:
pi@raspberrypi:~ $ sudo systemctl enable ambeserver@...
Created symlink /etc/systemd/system/multi-user.target.wants/ambeserver@... → /lib/systemd/system/ambeserver@.service.
pi@raspberrypi:~ $

No visible errors so I assumed it was enabled. I rebooted and tried:
sudo systemctl status ambeserver@...

pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-04-24 15:05:48 EDT; 8min ago
  Process: 403 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)

Apr 24 15:05:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 24 15:05:48 raspberrypi systemd[403]: ambeserver@...: Failed to determine user credentials: No such process
Apr 24 15:05:48 raspberrypi systemd[403]: ambeserver@...: Failed at step USER spawning /bin/chgrp: No such process
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exited, status=217/USER
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 24 15:05:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
pi@raspberrypi:~ $

Damn! So close. So I don't know what to make of that.

Colin
Colin G. MacArthur B.A., LL.B.


On Thu, Apr 23, 2020 at 1:19 AM John D Hays - K7VE <john@...> wrote:
Here are short instructions.
From  https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum#Quick-Build-on-Linux  

Quick Build on Linux

If you cannot find an AMBEserver package for your architecture and distribution. Try this:

wget https://raw.githubusercontent.com/dl5di/OpenDV/master/DummyRepeater/DV3000/AMBEserver.c
Open https://github.com/dl5di/OpenDV/blob/master/DummyRepeater/DV3000/AMBEserver.c
select "RAW"
Copy and past the source code into AMBEserver.  Or just use the attached copy.

gcc -o AMBEserver AMBEserver.c
Place the executable in an appropriate place, and create configuration and autostart files.  On Raspbian/Debian this would be
sudo cp AMBEserver /usr/sbin
sudo chmod +x /usr/sbin/AMBEserver
 
A set of files for systemd management are located in the files section: ambesupport.tgz (https://nw-digital-radio.groups.io/g/ambe/files)

Download this file to the target computer's filesystem and run 
mv ambesupport.tgz /tmp &&  cd / && sudo tar -xzvf /tmp/ambesupport.tgz

Use the above instructions to manage the server.  (From the WIKI article)
 
The test programs (python) can be obtained here  https://github.com/dl5di/OpenDV/tree/master/DummyRepeater/DV3000 
Open AMBEtest3.py go to raw and copy and paste to similarly named file (Attached)
  Open ambesocktest.py go to raw and copy and paste to similarly named file  or download this one from  https://nw-digital-radio.groups.io/g/ambe/files  

Run the tests I mentioned earlier


On Wed, Apr 22, 2020 at 7:57 PM John D Hays - K7VE via groups.io <john=hays.org@groups.io> wrote:
You probably need to build AMBEserver it is not on the standard repositories. 



On Wed, Apr 22, 2020, 19:25 Mechanical_Mac <c.g.macarthur@...> wrote:
Thanks John, I really appreciate your assistance.

The PIDV is definitely installed correctly on the Raspberry Pi, starting at PIN 1.
I always start with a fresh install of the latest version of Raspbian, now Buster.
I didn't get very far. The following steps were done sequentially.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ambeserver
e:  unable to locate package ambeserver

I searched the raspbian package list for ambeserver without success. 

Any suggestions?
 
Colin
Colin G. MacArthur B.A., LL.B.


On Wed, Apr 22, 2020 at 1:01 AM John D Hays - K7VE <john@...> wrote:
You need to take a step wise approach to debug:

1. Make sure the HAT is properly seated.  

Orient it so that it is sitting on pins 1-26, here is an illustration on a 40 pin GPIO Raspberry Pi
image.png

Use a current version of Raspbian (Compass Linux is deprecated)
Build/Install ambeserver
Do Not Start amberserver until you confirm that the PiDV is communicating with the Raspberry Pi

Use the test program from 
sudo python AMBEtest3.py -i /dev/ttyS0

If this fails, then you may have a hardware problem.  On success, then test in foreground (not as daemon, don't use systemctl yet)

sudo AMBEserver -i /dev/ttyS0

Watch for errors, and then open a second terminal window and use:

python ambesocktest.py

If the ambesocktest works, then you can kill the AMBEserver and restart it with systemctl.
My lab is down at the moment so I am unable to do hands on build and document.  

--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 

Mechanical_Mac
 

Hi John,

I tried:
pi@raspberrypi:~ $ sudo usermod -G dialout opendv
usermod: user 'opendv' does not exist

And now when I attempt:
pi@raspberrypi:~ $ sudo AMBEserver -i /dev/ttyS0
AMBEserver: Starting...
AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
AMBEserver: Couldn't find start byte in serial data
AMBEserver: error receiving response to reset
AMBEserver: Could not initialize the DV3K!

Colin
VE3CWQ


On Fri, Apr 24, 2020 at 7:42 PM John D Hays - K7VE <john@...> wrote:
You man need this on Buster

sudo usermod -G dialout opendv
Then try starting AMBEserver again.

On Fri, Apr 24, 2020 at 3:32 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Thank you very much John, I really appreciate your help. No need to rush, I'm not going anywhere.

Colin
Colin G. MacArthur B.A., LL.B.


On Fri, Apr 24, 2020 at 4:50 PM John D Hays - K7VE <john@...> wrote:
Those are very good results.  It looks like a permission problem, as I stated in another thread.

As I stated, I don't have access to a PiDV™ at the moment (packed away during an extended house move), but I will try on a ThumbDV™ when I get a minute.  It may be something faulty in the service file.



On Fri, Apr 24, 2020 at 1:16 PM Mechanical_Mac <c.g.macarthur@...> wrote:
Hi John,

I followed your instructions word for word. Results below.

sudo python AMBEtest3.py -i /dev/ttyS0
pi@raspberrypi:~ $ sudo python AMBEtest3.py -i /dev/ttyS0
AMBEtest3.py -s <serial port>
AMBEtest3.py -n -s <serial port> (for ThumbDV Model A
pi@raspberrypi:~ $ python ambesocktest.py
^CTraceback (most recent call last):
  File "ambesocktest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt

Same command but substituted -s flag and promising results.
pi@raspberrypi:~ $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes
a9
Product ID
6100010030
Wrote: 5 bytes
a
 0AMBE3000R
Version
6100010031
Wrote: 5 bytes
a11V120.E100.XXXX.C106.G514.R009.B0010411.C0020208
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

Then ran this command, things look like they're working as expected.
pi@raspberrypi:~ $ sudo AMBEserver -i /dev/ttyS0
AMBEserver: Starting...
AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
AMBEserver: Initialized AMBE3000R version V120.E100.XXXX.C106.G514.R009.B0010411.C0020208.
AMBEserver: Listening for connections on UDP port 2460.
Finally I tried the socket tests
python ambesocketest.py
                0AMBE3000R
Server reply : a
                0AMBE3000R
Server reply : a
                0AMBE3000R
^CTraceback (most recent call last):
  File "ambesocketest.py", line 23, in <module>
    d = s.recvfrom(1024)
KeyboardInterrupt

Hallelujah! The first positive news of the quarantine.

So then I tried:
pi@raspberrypi:~ $ sudo systemctl enable ambeserver@...
Created symlink /etc/systemd/system/multi-user.target.wants/ambeserver@... → /lib/systemd/system/ambeserver@.service.
pi@raspberrypi:~ $

No visible errors so I assumed it was enabled. I rebooted and tried:
sudo systemctl status ambeserver@...

pi@raspberrypi:~ $ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
   Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-04-24 15:05:48 EDT; 8min ago
  Process: 403 ExecStartPre=/bin/chgrp dialout /dev/ttyS0 (code=exited, status=217/USER)

Apr 24 15:05:48 raspberrypi systemd[1]: Starting DV3000 Daemon...
Apr 24 15:05:48 raspberrypi systemd[403]: ambeserver@...: Failed to determine user credentials: No such process
Apr 24 15:05:48 raspberrypi systemd[403]: ambeserver@...: Failed at step USER spawning /bin/chgrp: No such process
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Control process exited, code=exited, status=217/USER
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 24 15:05:48 raspberrypi systemd[1]: Failed to start DV3000 Daemon.
Apr 24 15:05:48 raspberrypi systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
pi@raspberrypi:~ $

Damn! So close. So I don't know what to make of that.

Colin
Colin G. MacArthur B.A., LL.B.


On Thu, Apr 23, 2020 at 1:19 AM John D Hays - K7VE <john@...> wrote:
Here are short instructions.
From  https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum#Quick-Build-on-Linux  

Quick Build on Linux

If you cannot find an AMBEserver package for your architecture and distribution. Try this:

wget https://raw.githubusercontent.com/dl5di/OpenDV/master/DummyRepeater/DV3000/AMBEserver.c
Open https://github.com/dl5di/OpenDV/blob/master/DummyRepeater/DV3000/AMBEserver.c
select "RAW"
Copy and past the source code into AMBEserver.  Or just use the attached copy.

gcc -o AMBEserver AMBEserver.c
Place the executable in an appropriate place, and create configuration and autostart files.  On Raspbian/Debian this would be
sudo cp AMBEserver /usr/sbin
sudo chmod +x /usr/sbin/AMBEserver
 
A set of files for systemd management are located in the files section: ambesupport.tgz (https://nw-digital-radio.groups.io/g/ambe/files)

Download this file to the target computer's filesystem and run 
mv ambesupport.tgz /tmp &&  cd / && sudo tar -xzvf /tmp/ambesupport.tgz

Use the above instructions to manage the server.  (From the WIKI article)
 
The test programs (python) can be obtained here  https://github.com/dl5di/OpenDV/tree/master/DummyRepeater/DV3000 
Open AMBEtest3.py go to raw and copy and paste to similarly named file (Attached)
  Open ambesocktest.py go to raw and copy and paste to similarly named file  or download this one from  https://nw-digital-radio.groups.io/g/ambe/files  

Run the tests I mentioned earlier


On Wed, Apr 22, 2020 at 7:57 PM John D Hays - K7VE via groups.io <john=hays.org@groups.io> wrote:
You probably need to build AMBEserver it is not on the standard repositories. 



On Wed, Apr 22, 2020, 19:25 Mechanical_Mac <c.g.macarthur@...> wrote:
Thanks John, I really appreciate your assistance.

The PIDV is definitely installed correctly on the Raspberry Pi, starting at PIN 1.
I always start with a fresh install of the latest version of Raspbian, now Buster.
I didn't get very far. The following steps were done sequentially.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ambeserver
e:  unable to locate package ambeserver

I searched the raspbian package list for ambeserver without success. 

Any suggestions?
 
Colin
Colin G. MacArthur B.A., LL.B.


On Wed, Apr 22, 2020 at 1:01 AM John D Hays - K7VE <john@...> wrote:
You need to take a step wise approach to debug:

1. Make sure the HAT is properly seated.  

Orient it so that it is sitting on pins 1-26, here is an illustration on a 40 pin GPIO Raspberry Pi
image.png

Use a current version of Raspbian (Compass Linux is deprecated)
Build/Install ambeserver
Do Not Start amberserver until you confirm that the PiDV is communicating with the Raspberry Pi

Use the test program from 
sudo python AMBEtest3.py -i /dev/ttyS0

If this fails, then you may have a hardware problem.  On success, then test in foreground (not as daemon, don't use systemctl yet)

sudo AMBEserver -i /dev/ttyS0

Watch for errors, and then open a second terminal window and use:

python ambesocktest.py

If the ambesocktest works, then you can kill the AMBEserver and restart it with systemctl.
My lab is down at the moment so I am unable to do hands on build and document.  

--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE