Date   

Re: PiDV, AMBEserver and Buster

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:~ $


Re: PiDV, AMBEserver and Buster

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

 


Re: PiDV, AMBEserver and Buster

 

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

 


Re: PiDV, AMBEserver and Buster

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

 


Re: PiDV, AMBEserver and Buster

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:~ $


Re: PiDV, AMBEserver and Buster

 

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

 


Re: PiDV, AMBEserver and Buster

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



Re: PiDV, AMBEserver and Buster

 

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

Bryan K7UDR


Re: PiDV, AMBEserver and Buster

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


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:~ $


Use ThumbDV to Feed Radio Data Port or Modulate Audio? #thumbdv #ambe

Joe_Hutcheson
 

Hi - Has anyone tried to use a ThumbDV with its AMBE firmware to feed digital data to a radio's TNC input or to modulate a radio's audio?  I have an IC-7000, which has a 9600 data input and, like many, I have the ability to interface computer audio with the transceiver.  Would be nice/fun to get it to work D-Star and DMR, if that's possible.

Thanks, Joe, KE1U


Re: Changing Talkgroups in BlueDV

Mike Kilsby
 

Many thanks Gwen, I need to get a better understandIng about the BM Static/Dynamic setup.
73’s Mike


Re: Thumb DV / DVstick 30

 

Should work just fine. 


On Sat, Mar 28, 2020, 23:06 Mike Kilsby <bundyave8rr@...> wrote:
Thanks John, I am just waiting for a USB Type C to USB A adapter and hopefully all will work.


Re: Changing Talkgroups in BlueDV

Gwen Patton
 

That drop off over time is a function of a specific repeater. The talk group is there regardless of how long between keyups, but repeater owners try to balance what's got the attention of their machine with the usage it warrants.

There are talk groups on my local DMR repeater that will disconnect after n minutes without a transmission. But that might be different on another repeater where that TG gets used a lot, and is set to full time.

The ThumbDV doesn't access through any repeaters, so it's not subject to how the repeater owners set each talk group on their machine.

73,
Gwen, NG3P

On Sun, Mar 29, 2020, 2:12 AM Mike Kilsby <bundyave8rr@...> wrote:
And Gwen, do you know if the new TG will stay on permanently (if there is no traffic) until another 4000 is sent?
I thought it would be dynamic and drop off after a period of time and require another key up to reactivate?
cheers Mike VK4MY.


Re: Changing Talkgroups in BlueDV

Mike Kilsby
 

And Gwen, do you know if the new TG will stay on permanently (if there is no traffic) until another 4000 is sent?
I thought it would be dynamic and drop off after a period of time and require another key up to reactivate?
cheers Mike VK4MY.


Re: Thumb DV / DVstick 30

Mike Kilsby
 

Thanks John, I am just waiting for a USB Type C to USB A adapter and hopefully all will work.


Re: Thumb DV / DVstick 30

 

Not the Go, but have used the ThumbDV™ with the Surface 3 and other Windows based tablets. Used BlueDV software. 

The ThumbDV™ is on sale right now. 

On Sat, Mar 28, 2020, 22:14 Mike Kilsby <bundyave8rr@...> wrote:
Hi Guys, just wondering IF any members have used the ThumbDV or DVstick 30 with a Microsoft Surface Go Tablet using Blue DV software?
Rgds Mike VK4MY


Thumb DV / DVstick 30

Mike Kilsby
 

Hi Guys, just wondering IF any members have used the ThumbDV or DVstick 30 with a Microsoft Surface Go Tablet using Blue DV software?
Rgds Mike VK4MY


I want to be able to send messages to users.

Alex
 

I want to be able to send messages to users.

 

73, Alex, UW0WU


Ambeserver IP address changed

Nomis Bayan Jr.
 

The IP address for our ambeserver was changed, now we can not connect to our dstar reflector. I can connect to other dstar reflector except our dstar reflector. The DMR TG is working fine. Please advice.

601 - 620 of 1637