Date   

Re: PiDV, AMBEserver and Buster

Mechanical_Mac
 

SUCCESS!!

I tried "sudo usermod -G dialout opendv". Turned out there was no user opendv. So I added the user with "sudo adduser opendv". Tried "sudo usermod -G dialout opendv" again and it returned no errors.

I then tried "sudo systemctl enable ambeserver@...", rebooted and ran the"sudo systemctl status ambeserver@..." command. It failed to connect, but then I remembered that I hadn't modified ambeserver-ttyS0.conf to set DV3000 baud rate at 230400. Used "sudo nano /etc/opendv/ambeserver-ttyS0.conf" to set it appropriately. Rebooted and tried: "sudo systemctl status ambeserver@..." again and SUCCESS!!.

Thanks John for your invaluable assistance.

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


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

 


Re: PiDV, AMBEserver and Buster

 

Create the user and try again



On Sat, Apr 25, 2020, 12:56 Mechanical_Mac <c.g.macarthur@...> wrote:
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

 


Re: PiDV, AMBEserver and Buster

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

 


Re: Thumbdv and IC9700

Art Olson
 

Charlie, John
Thanks for your feedback

art N2AJO


New file uploaded to ambe@nw-digital-radio.groups.io

ambe@nw-digital-radio.groups.io Notification <ambe+notification@...>
 

Hello,

This email message is a notification to let you know that the following files have been uploaded to the Files area of the ambe@nw-digital-radio.groups.io group.

Uploaded By: John D Hays - K7VE <john@...>

Description:
Source file for AMBEserver -- compile on Linux/Unix with gcc -o AMBEserver AMBEserver.c | copy to /usr/sbin | newer versions of Linux will require you have an opendv user, which is also a member of the dialout group.

Cheers,
The Groups.io Team


Re: Thumbdv and IC9700

Charles Wiant
 

The thunb dv lets you you use your microphone off your computer to talk , it will not recieve from radio .


On Apr 25, 2020, at 10:11 AM, John D Hays - K7VE <john@...> wrote:


Hi Art,

Not sure what you are trying to do.  ThumbDV™ and BlueDV are for network connectivity, so I am not sure how the IC-9700 comes into play. 

On Sat, Apr 25, 2020, 08:07 Art Olson <olson339@...> wrote:
New to this site so this may be a dumb question but here it goes. I have a NWDR AMBE thumbdv. Connected to my PC (Win10) and Blue DV installed. I ran the thumbdv test and it is communicating on a com port. I configured BlueDV and started DSTAR. I can receive but can not transmit from my IC9700 which is set for DV operation.

I also have a dvmega on a rpi and that works correctly. You might ask why both - well I bought the Thumbdv last year and am just now seeing what I can use it for.

Any ideas - am I missing something


Re: Thumbdv and IC9700

 

Hi Art,

Not sure what you are trying to do.  ThumbDV™ and BlueDV are for network connectivity, so I am not sure how the IC-9700 comes into play. 

On Sat, Apr 25, 2020, 08:07 Art Olson <olson339@...> wrote:
New to this site so this may be a dumb question but here it goes. I have a NWDR AMBE thumbdv. Connected to my PC (Win10) and Blue DV installed. I ran the thumbdv test and it is communicating on a com port. I configured BlueDV and started DSTAR. I can receive but can not transmit from my IC9700 which is set for DV operation.

I also have a dvmega on a rpi and that works correctly. You might ask why both - well I bought the Thumbdv last year and am just now seeing what I can use it for.

Any ideas - am I missing something


Thumbdv and IC9700

Art Olson
 

New to this site so this may be a dumb question but here it goes. I have a NWDR AMBE thumbdv. Connected to my PC (Win10) and Blue DV installed. I ran the thumbdv test and it is communicating on a com port. I configured BlueDV and started DSTAR. I can receive but can not transmit from my IC9700 which is set for DV operation.

I also have a dvmega on a rpi and that works correctly. You might ask why both - well I bought the Thumbdv last year and am just now seeing what I can use it for.

Any ideas - am I missing something


Re: ThumbDV on Ubuntu 20.04 Focal Fossa

John Spoonhower
 

OK. The service is running now. Thanks for the help, John. I'll let it run tonight before taking the next steps in the process tomorrow.
73, John, NX2I


Re: ThumbDV on Ubuntu 20.04 Focal Fossa

 

Try rebooting. 


On Fri, Apr 24, 2020, 18:11 John Spoonhower <jpspoonhower@...> wrote:
John,
maybe there's some progress here. I added opendv to the dialout group with:
sudo adduser -G dialout opendv

then the service starts OK for awhile:
john@ubuntu1:~$ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
     Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2020-04-24 21:05:21 EDT; 33s ago
    Process: 87701 ExecStartPre=/bin/chgrp dialout /dev/ttyUSB0 (code=exited, status=0/SUCCESS)
    Process: 87710 ExecStartPre=/bin/chmod 0660 /dev/ttyUSB0 (code=exited, status=0/SUCCESS)
   Main PID: 87711 (AMBEserver)
      Tasks: 1 (limit: 2170)
     Memory: 416.0K
     CGroup: /system.slice/system-ambeserver.slice/ambeserver@...
             └─87711 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyUSB0 -s 460800

Apr 24 21:05:21 ubuntu1 systemd[1]: Starting DV3000 Daemon...
Apr 24 21:05:21 ubuntu1 systemd[1]: Started DV3000 Daemon.
Apr 24 21:05:21 ubuntu1 AMBEserver[87711]: AMBEserver: Starting...
Apr 24 21:05:21 ubuntu1 AMBEserver[87711]: AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 >
john@ubuntu1:~$

but then fails:
john@ubuntu1:~$ 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 21:05:55 EDT; 21s ago
    Process: 87701 ExecStartPre=/bin/chgrp dialout /dev/ttyUSB0 (code=exited, status=0/SUCCESS)
    Process: 87710 ExecStartPre=/bin/chmod 0660 /dev/ttyUSB0 (code=exited, status=0/SUCCESS)
    Process: 87711 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/ttyUSB0 $AMBESERVER_FLAG>
   Main PID: 87711 (code=exited, status=1/FAILURE)

Apr 24 21:05:21 ubuntu1 systemd[1]: Starting DV3000 Daemon...
Apr 24 21:05:21 ubuntu1 systemd[1]: Started DV3000 Daemon.
Apr 24 21:05:21 ubuntu1 AMBEserver[87711]: AMBEserver: Starting...
Apr 24 21:05:21 ubuntu1 AMBEserver[87711]: AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 >
Apr 24 21:05:55 ubuntu1 AMBEserver[87711]: AMBEserver: Couldn't find start byte in serial data
Apr 24 21:05:55 ubuntu1 AMBEserver[87711]: AMBEserver: error receiving response to reset
Apr 24 21:05:55 ubuntu1 AMBEserver[87711]: AMBEserver: Could not initialize the DV3K!
Apr 24 21:05:55 ubuntu1 systemd[1]: ambeserver@...: Main process exited, code=exited,>
Apr 24 21:05:55 ubuntu1 systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 24 21:05:56 ubuntu1 systemd[1]: ambeserver@...: Triggering OnFailure= dependencie>
lines 1-18/18 (END)


Re: ThumbDV on Ubuntu 20.04 Focal Fossa

John Spoonhower
 

John,
maybe there's some progress here. I added opendv to the dialout group with:
sudo adduser -G dialout opendv

then the service starts OK for awhile:
john@ubuntu1:~$ sudo systemctl status ambeserver@...
● ambeserver@... - DV3000 Daemon
     Loaded: loaded (/lib/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2020-04-24 21:05:21 EDT; 33s ago
    Process: 87701 ExecStartPre=/bin/chgrp dialout /dev/ttyUSB0 (code=exited, status=0/SUCCESS)
    Process: 87710 ExecStartPre=/bin/chmod 0660 /dev/ttyUSB0 (code=exited, status=0/SUCCESS)
   Main PID: 87711 (AMBEserver)
      Tasks: 1 (limit: 2170)
     Memory: 416.0K
     CGroup: /system.slice/system-ambeserver.slice/ambeserver@...
             └─87711 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyUSB0 -s 460800

Apr 24 21:05:21 ubuntu1 systemd[1]: Starting DV3000 Daemon...
Apr 24 21:05:21 ubuntu1 systemd[1]: Started DV3000 Daemon.
Apr 24 21:05:21 ubuntu1 AMBEserver[87711]: AMBEserver: Starting...
Apr 24 21:05:21 ubuntu1 AMBEserver[87711]: AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 >
john@ubuntu1:~$

but then fails:
john@ubuntu1:~$ 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 21:05:55 EDT; 21s ago
    Process: 87701 ExecStartPre=/bin/chgrp dialout /dev/ttyUSB0 (code=exited, status=0/SUCCESS)
    Process: 87710 ExecStartPre=/bin/chmod 0660 /dev/ttyUSB0 (code=exited, status=0/SUCCESS)
    Process: 87711 ExecStart=/usr/sbin/AMBEserver -p ${UDP_PORT} -i /dev/ttyUSB0 $AMBESERVER_FLAG>
   Main PID: 87711 (code=exited, status=1/FAILURE)

Apr 24 21:05:21 ubuntu1 systemd[1]: Starting DV3000 Daemon...
Apr 24 21:05:21 ubuntu1 systemd[1]: Started DV3000 Daemon.
Apr 24 21:05:21 ubuntu1 AMBEserver[87711]: AMBEserver: Starting...
Apr 24 21:05:21 ubuntu1 AMBEserver[87711]: AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 >
Apr 24 21:05:55 ubuntu1 AMBEserver[87711]: AMBEserver: Couldn't find start byte in serial data
Apr 24 21:05:55 ubuntu1 AMBEserver[87711]: AMBEserver: error receiving response to reset
Apr 24 21:05:55 ubuntu1 AMBEserver[87711]: AMBEserver: Could not initialize the DV3K!
Apr 24 21:05:55 ubuntu1 systemd[1]: ambeserver@...: Main process exited, code=exited,>
Apr 24 21:05:55 ubuntu1 systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Apr 24 21:05:56 ubuntu1 systemd[1]: ambeserver@...: Triggering OnFailure= dependencie>
lines 1-18/18 (END)


Re: ThumbDV on Ubuntu 20.04 Focal Fossa

John Spoonhower
 

Here's what happens:
sudo usermod -G dialout opendv
[sudo] password for john:
usermod: user 'opendv' does not exist


Re: PiDV, AMBEserver and Buster

 

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

 


Re: ThumbDV on Ubuntu 20.04 Focal Fossa

 

Try this

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


On Fri, Apr 24, 2020 at 4:06 PM John Spoonhower <jpspoonhower@...> wrote:
OK....I had some free time. I ran the ThumbTest.exe program on Windows 7 and the device passed.
It's back to Ubuntu....
John, NX2I



--
John D. Hays
Kingston, WA
K7VE

 


Re: ThumbDV on Ubuntu 20.04 Focal Fossa

John Spoonhower
 

OK....I had some free time. I ran the ThumbTest.exe program on Windows 7 and the device passed.
It's back to Ubuntu....
John, NX2I


Re: PiDV, AMBEserver and Buster

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

 


Re: ThumbDV on Ubuntu 20.04 Focal Fossa

John Spoonhower
 

OK,
I will run the windows test tomorrow. I just ran the same tests (with the same results) on a different Linux machine running  Linux Mint 19.3 (Ubuntu bionic).
John S


Re: ThumbDV on Ubuntu 20.04 Focal Fossa

 

Yes, if this is a brand new ThumbDV™ from the website, then it should be the 460800 version.  Each unit is tested before shipping.

On Fri, Apr 24, 2020 at 1:30 PM John Spoonhower <jpspoonhower@...> wrote:
Yes, the LED blinks when AMBEtest3 runs.
when I run AMBEserver -s 460800 -p 2460 -i /dev/ttyUSB0 I see the LED blink 1 time.

dropping the speed to 230400 doesn't change anything. The thumbDV just arrived here a week ago; I assume it was (is) a new version.

I could try to run the device on a windows machine if that makes sense. Please let me know.
73, John NX2I



--
John D. Hays
Kingston, WA
K7VE

 


Re: ThumbDV on Ubuntu 20.04 Focal Fossa

 

If you have a Windows machine, there is a test program in the files section of this group.  It shouldn't hurt :)



On Fri, Apr 24, 2020 at 1:30 PM John Spoonhower <jpspoonhower@...> wrote:
Yes, the LED blinks when AMBEtest3 runs.
when I run AMBEserver -s 460800 -p 2460 -i /dev/ttyUSB0 I see the LED blink 1 time.

dropping the speed to 230400 doesn't change anything. The thumbDV just arrived here a week ago; I assume it was (is) a new version.

I could try to run the device on a windows machine if that makes sense. Please let me know.
73, John NX2I



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

 

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

 

561 - 580 of 1635