Date   

Re: Thumb DV Baud rate change #ambe #ambeserver #thumbdv

VE3MIC
 

I see that John has replied.  I forgot to add that the procedure is not for the faint of heart, which is why John has asked why you wish to do it.
de Mike


Re: Thumb DV Baud rate change #ambe #ambeserver #thumbdv

VE3MIC
 

Hi Don. I recall reading a how-to from John Hays of NW Digital Radio, where he explains how to do "surgery" to an Original ThumbDV to change the baud rate from 230,400 to 460,800, I believe that it involved in cutting a couple of traces on the PCB and re-jumpering.
I'll see if I can locate the document.
73 de Mike

On Friday, October 9, 2020, 08:19:34 p.m. EDT, Donald Jacob <wb5eku@...> wrote:


Sorry if this has been answered before, I searched but could not find it.
I have an original ThumbDV, its baud rate is 230,400. My new ThumbDV has a baud rate of 460800, Is there a
hardware (relative easy!) mod to bring the original up to 460800 ?
Thanks
Don
WB5EKU


Re: Thumb DV Baud rate change #ambe #ambeserver #thumbdv

 

Don,


Changing the baud rate is not trivial.  Is there a particular reason you wish to change it?

On Fri, Oct 9, 2020, 17:18 Donald Jacob <wb5eku@...> wrote:
Sorry if this has been answered before, I searched but could not find it.
I have an original ThumbDV, its baud rate is 230,400. My new ThumbDV has a baud rate of 460800, Is there a
hardware (relative easy!) mod to bring the original up to 460800 ?
Thanks
Don
WB5EKU


Thumb DV Baud rate change #ambe #ambeserver #thumbdv

 

Sorry if this has been answered before, I searched but could not find it.
I have an original ThumbDV, its baud rate is 230,400. My new ThumbDV has a baud rate of 460800, Is there a
hardware (relative easy!) mod to bring the original up to 460800 ?
Thanks
Don
WB5EKU


ThumbDV ambeserver intermittent transmission #ambeserver #thumbdv

roylosbanes@...
 

Hello everyone, I recently setup ambeserver linke to peanut and to our YSF Reflector which is alos link to our club's repeater (Yaesu DR1X). We recently encountered intermittent transmissions when TX from Peanut App to C4FM. All other modes don't have any issues. So from Peanut to any other modes, TX is ok, RX to peanut from other modes also have no issues. So the main issue is why are we having intermittent transmissions from Peanut going to YSFReflector? Anyone here encountered the same issue?
-Setup:
ThumbDV connected to RPI3B+ with 30mbps internet connection
MMDVM Repeater setup for YSF connected to Motorola GM300>Linked to Yeasu DR1x

Thanks,
73 de 4I1AYZ


Re: order

Doug Waugh (KC0EQA)
 

 
Thank you, Bryan. Receive them monday and all working as expected. Glad I got them from you guys.

73's 
Doug KC0EQA
 


Re: order

 

Out of the Office Friday, took care of this already.

73
Bryan K7UDR


On Oct 3, 2020, at 6:53 AM, Doug Waugh (KC0EQA) <waughdj@...> wrote:

I just ordered a couple days ago, everything cleared, But haven't heard a word about it yet. Or even if I got the $20 discount. I emailed through support and haven't heard anything back either. I don't think anyone is even checking system for orders..


Re: order

Doug Waugh (KC0EQA)
 

I just ordered a couple days ago, everything cleared, But haven't heard a word about it yet. Or even if I got the $20 discount. I emailed through support and haven't heard anything back either. I don't think anyone is even checking system for orders..


Re: PiDV, AMBEserver and Buster

KB5ZUR
 

Thanks John,
That does work. I've tested and it does start automatically on reboot. I'm not really sure of the security ramifications of running this way especially since pi this will be port forwarded through to the internet so I can use it remotely.
I wonder if there is anything I could add to the systemctl cmd (-user or something) when starting Ambeserver rather than changing the user to root.
Again thanks for all your help in getting this going. I learned a few things LOL.

-David
KB5ZUR


On Fri, Oct 2, 2020 at 12:09 PM John D Hays - K7VE <john@...> wrote:
I don't recommend running daemons as root, but you could edit
/etc/systemd/system/ambeserver@.service

[Unit]
Description=AMBEserver Daemon
After=network.target serial-getty@%i.service dev-%i.device
Conflicts=serial-getty@%i.service
OnFailure=serial-getty@%i.service

[Service]
User=opendv
EnvironmentFile=/etc/opendv/%p-%i.conf
PermissionsStartOnly=true
ExecStartPre=/bin/chgrp dialout /dev/%i
ExecStartPre=/bin/chmod 0660 /dev/%i
ExecStart=/usr/local/sbin/AMBEserver -p ${UDP_PORT} -i /dev/%i $AMBESERVER_FLAGS
Restart=on-abort

[Install]
WantedBy=multi-user.target


And change User to root.   As you can see this script supposedly changes group permissions to dialout and read/write for the device.  So it should work.

Verify that user opendv is a member of the dialout group

grep dialout /etc/group

On Fri, Oct 2, 2020 at 9:05 AM KB5ZUR <kb5zur@...> wrote:
I tried this the other night and again just now.

I copied my ambeserver-ttyS0.conf to ambeserver-serial0.conf and to serial 1.conf.

I tried enabling and running both and got the error  "ambeserver@... failed no such file or or directory. same for serial1

however I do see this in /dev
lrwxrwxrwx  1 root root           5 Oct  1 17:48 serial0 -> ttyS0
lrwxrwxrwx  1 root root           7 Oct  1 17:48 serial1 -> ttyAMA0

-DS


On Fri, Oct 2, 2020 at 10:19 AM John D Hays - K7VE <john@...> wrote:
There are some automatic aliases.

Try serial0 and serial1 and see if that helps.  


--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

 

I don't recommend running daemons as root, but you could edit
/etc/systemd/system/ambeserver@.service

[Unit]
Description=AMBEserver Daemon
After=network.target serial-getty@%i.service dev-%i.device
Conflicts=serial-getty@%i.service
OnFailure=serial-getty@%i.service

[Service]
User=opendv
EnvironmentFile=/etc/opendv/%p-%i.conf
PermissionsStartOnly=true
ExecStartPre=/bin/chgrp dialout /dev/%i
ExecStartPre=/bin/chmod 0660 /dev/%i
ExecStart=/usr/local/sbin/AMBEserver -p ${UDP_PORT} -i /dev/%i $AMBESERVER_FLAGS
Restart=on-abort

[Install]
WantedBy=multi-user.target


And change User to root.   As you can see this script supposedly changes group permissions to dialout and read/write for the device.  So it should work.

Verify that user opendv is a member of the dialout group

grep dialout /etc/group

On Fri, Oct 2, 2020 at 9:05 AM KB5ZUR <kb5zur@...> wrote:
I tried this the other night and again just now.

I copied my ambeserver-ttyS0.conf to ambeserver-serial0.conf and to serial 1.conf.

I tried enabling and running both and got the error  "ambeserver@... failed no such file or or directory. same for serial1

however I do see this in /dev
lrwxrwxrwx  1 root root           5 Oct  1 17:48 serial0 -> ttyS0
lrwxrwxrwx  1 root root           7 Oct  1 17:48 serial1 -> ttyAMA0

-DS


On Fri, Oct 2, 2020 at 10:19 AM John D Hays - K7VE <john@...> wrote:
There are some automatic aliases.

Try serial0 and serial1 and see if that helps.  


--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

KB5ZUR
 

I tried this the other night and again just now.

I copied my ambeserver-ttyS0.conf to ambeserver-serial0.conf and to serial 1.conf.

I tried enabling and running both and got the error  "ambeserver@... failed no such file or or directory. same for serial1

however I do see this in /dev
lrwxrwxrwx  1 root root           5 Oct  1 17:48 serial0 -> ttyS0
lrwxrwxrwx  1 root root           7 Oct  1 17:48 serial1 -> ttyAMA0

-DS


On Fri, Oct 2, 2020 at 10:19 AM John D Hays - K7VE <john@...> wrote:
There are some automatic aliases.

Try serial0 and serial1 and see if that helps.  


--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

 

There are some automatic aliases.

Try serial0 and serial1 and see if that helps.  


--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

KB5ZUR
 

John,
Thanks for the help. 
I'm definitely a noob when it comes to a lot of Linux  commands and I appreciate you sending me the references. I will study the documentation to get more familiar with the system administration commands. I had tried a few things on my own researching the problem and decided to start fresh last night and here is where it stands.

Re-installed the OS and configured the pi using latest version from raspberry pi web site
Using sudo-raspi config, I set up the serial port turning off the boot console and enabling the com port
Ran the AMBEserver3.py test to verify the PiDV serial communications. (FYI, I had to modify the AMBEserver3.py file to delete the tm symbol after ThumbDV on line 22 as my python program couldn't understand the symbol)
Test runs fine so I proceed with the ambesocktesy.py running AMBEserver -i /dev/ttyS0 and that runs fine too.
 In fact I operated BlueDV on my PC as additional verification of the AMBEserver.

The wheels come off when I try to run the server as a service using sudo systemctl enable ambeserver@ttyS0 and  sudo systemctl start ambeserver@ttyS0 and  sudo systemctl status ambeserver@ttyS0
 I get the ever troubling error " AMBEserver: Unable to open GPIO export interface: Permission denied"

I then change the ownership of /dev/ttyS0 with:
sudo chown root:dialout /dev/ttyS0
sudo chmod 660 /dev/ttyS0
after testing I get 
ls -l /dev/tty[AS]*
crw-rw---- 1 root dialout 204, 64 Oct  1 17:48 /dev/ttyAMA0
crw-rw---- 1 root dialout   4, 64 Oct  2 09:14 /dev/ttyS0

but when I start the server again the same problems. Server fails with the GPIO permission failure and
the ownership of ttyS0 reverts back to this state.
ls -l /dev/tty[AS]*
crw-rw---- 1 root dialout 204, 64 Oct  1 17:48 /dev/ttyAMA0
crw--w---- 1 root tty       4, 64 Oct  2 09:21 /dev/ttyS0

somehow the  sudo systemctl start ambeserver@ttyS0 resets the ownership of of ttyS0

Again being a noob, I'm not sure where to go from here. I'm hoping this info will give you some insight as to how I can proceed from here.

Thanks again for your help.
-David
KB5ZUR



On Thu, Oct 1, 2020 at 2:14 PM John D Hays - K7VE <john@...> wrote:
David,

There are two commands you should become familiar with chown (to change ownership of a file or directory) and chmod (to change permissions for the owner, group, and world of a file or directory).  Also, learn chgrp.

Issue the commands:

man chmod
man chown
man chgrp

to read the manual pages for each command.

chown root:dialout /dev/ttyS0
chmod 660 /dev/ttyS0

After doing so, do the ls -l /dev/tty[AS]*  to see the new ownership and permissions of both AMA0 and S0.

I advise getting some system administration knowledge, you can start with articles like https://opensource.com/article/17/7/20-sysadmin-commands


On Wed, Sep 30, 2020 at 6:25 PM KB5ZUR <kb5zur@...> wrote:
Hi John,
Pardon my ignorance but I'm not sure how to make that change of ownership of /dev/ttyS0 can you kindly advise how to do that. I don't want to screw things up now that I am this close.

I appreciate all the help.

Thanks,
-David

On Wed, Sep 30, 2020 at 7:03 PM John D Hays - K7VE <john@...> wrote:
Try changing the ownership of /dev/ttyS0 -- your listing did not show it belonging to the dialout group.

On Wed, Sep 30, 2020 at 4:59 PM KB5ZUR <kb5zur@...> wrote:
Hi John,

Still no Joy!  tried your suggestion and the server failed. I stopped the server and ran the AMBEtest3.py and it hangs about half way through the test.
i@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyAMA0
Setting ...
/dev/ttyAMA0
d
8
N
1
False
False
False

Reset
6100010033

grep dialout shows the following:
pi@DV3000SVR:~/ambeserver-install $ grep dialout /etc/group
dialout:x:20:pi,opendv
 AMBEtest3,py with ttyS0 seems to complete

pi@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes

Product ID
6100010030
Wrote: 5 bytes

Version
6100010031
Wrote: 5 bytes

Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

What now coach?

-David
KB5ZUR


On Wed, Sep 30, 2020 at 11:25 AM John D Hays - K7VE <john@...> wrote:
OK, normally the PiDV™ would be on /dev/ttyAMA0 and not /dev/ttyS0 (Pi4 may re-map).

Give a try with:
sudo systemctl stop ambeserver@...  
sudo systemctl disable ambeserver@...  
sudo systemctl start ambeserver@...  
sudo systemctl status ambeserver@... 

If all is good, then

sudo systemctl enable ambeserver@...    

You can verify that opendv is in the dialout group with
 grep dialout /etc/group

Which should return something like:
dialout:x:20:opendv     

On Wed, Sep 30, 2020 at 6:58 AM KB5ZUR <kb5zur@...> wrote:
John,
Her you go.
-DS

pi@DV3000SVR:~/ambeserver-install $ ls -l /dev/tty*

crw-rw---- 1 root dialout 204, 64 Sep 29 15:13 /dev/ttyAMA0
crw--w---- 1 root tty       4, 64 Sep 29 17:56 /dev/ttyS0


Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.




--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

 

David,

There are two commands you should become familiar with chown (to change ownership of a file or directory) and chmod (to change permissions for the owner, group, and world of a file or directory).  Also, learn chgrp.

Issue the commands:

man chmod
man chown
man chgrp

to read the manual pages for each command.

chown root:dialout /dev/ttyS0
chmod 660 /dev/ttyS0

After doing so, do the ls -l /dev/tty[AS]*  to see the new ownership and permissions of both AMA0 and S0.

I advise getting some system administration knowledge, you can start with articles like https://opensource.com/article/17/7/20-sysadmin-commands


On Wed, Sep 30, 2020 at 6:25 PM KB5ZUR <kb5zur@...> wrote:
Hi John,
Pardon my ignorance but I'm not sure how to make that change of ownership of /dev/ttyS0 can you kindly advise how to do that. I don't want to screw things up now that I am this close.

I appreciate all the help.

Thanks,
-David

On Wed, Sep 30, 2020 at 7:03 PM John D Hays - K7VE <john@...> wrote:
Try changing the ownership of /dev/ttyS0 -- your listing did not show it belonging to the dialout group.

On Wed, Sep 30, 2020 at 4:59 PM KB5ZUR <kb5zur@...> wrote:
Hi John,

Still no Joy!  tried your suggestion and the server failed. I stopped the server and ran the AMBEtest3.py and it hangs about half way through the test.
i@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyAMA0
Setting ...
/dev/ttyAMA0
d
8
N
1
False
False
False

Reset
6100010033

grep dialout shows the following:
pi@DV3000SVR:~/ambeserver-install $ grep dialout /etc/group
dialout:x:20:pi,opendv
 AMBEtest3,py with ttyS0 seems to complete

pi@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes

Product ID
6100010030
Wrote: 5 bytes

Version
6100010031
Wrote: 5 bytes

Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

What now coach?

-David
KB5ZUR


On Wed, Sep 30, 2020 at 11:25 AM John D Hays - K7VE <john@...> wrote:
OK, normally the PiDV™ would be on /dev/ttyAMA0 and not /dev/ttyS0 (Pi4 may re-map).

Give a try with:
sudo systemctl stop ambeserver@...  
sudo systemctl disable ambeserver@...  
sudo systemctl start ambeserver@...  
sudo systemctl status ambeserver@... 

If all is good, then

sudo systemctl enable ambeserver@...    

You can verify that opendv is in the dialout group with
 grep dialout /etc/group

Which should return something like:
dialout:x:20:opendv     

On Wed, Sep 30, 2020 at 6:58 AM KB5ZUR <kb5zur@...> wrote:
John,
Her you go.
-DS

pi@DV3000SVR:~/ambeserver-install $ ls -l /dev/tty*

crw-rw---- 1 root dialout 204, 64 Sep 29 15:13 /dev/ttyAMA0
crw--w---- 1 root tty       4, 64 Sep 29 17:56 /dev/ttyS0


Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.




--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

KB5ZUR
 

Hi John,
Pardon my ignorance but I'm not sure how to make that change of ownership of /dev/ttyS0 can you kindly advise how to do that. I don't want to screw things up now that I am this close.

I appreciate all the help.

Thanks,
-David

On Wed, Sep 30, 2020 at 7:03 PM John D Hays - K7VE <john@...> wrote:
Try changing the ownership of /dev/ttyS0 -- your listing did not show it belonging to the dialout group.

On Wed, Sep 30, 2020 at 4:59 PM KB5ZUR <kb5zur@...> wrote:
Hi John,

Still no Joy!  tried your suggestion and the server failed. I stopped the server and ran the AMBEtest3.py and it hangs about half way through the test.
i@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyAMA0
Setting ...
/dev/ttyAMA0
d
8
N
1
False
False
False

Reset
6100010033

grep dialout shows the following:
pi@DV3000SVR:~/ambeserver-install $ grep dialout /etc/group
dialout:x:20:pi,opendv
 AMBEtest3,py with ttyS0 seems to complete

pi@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes

Product ID
6100010030
Wrote: 5 bytes

Version
6100010031
Wrote: 5 bytes

Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

What now coach?

-David
KB5ZUR


On Wed, Sep 30, 2020 at 11:25 AM John D Hays - K7VE <john@...> wrote:
OK, normally the PiDV™ would be on /dev/ttyAMA0 and not /dev/ttyS0 (Pi4 may re-map).

Give a try with:
sudo systemctl stop ambeserver@...  
sudo systemctl disable ambeserver@...  
sudo systemctl start ambeserver@...  
sudo systemctl status ambeserver@... 

If all is good, then

sudo systemctl enable ambeserver@...    

You can verify that opendv is in the dialout group with
 grep dialout /etc/group

Which should return something like:
dialout:x:20:opendv     

On Wed, Sep 30, 2020 at 6:58 AM KB5ZUR <kb5zur@...> wrote:
John,
Her you go.
-DS

pi@DV3000SVR:~/ambeserver-install $ ls -l /dev/tty*

crw-rw---- 1 root dialout 204, 64 Sep 29 15:13 /dev/ttyAMA0
crw--w---- 1 root tty       4, 64 Sep 29 17:56 /dev/ttyS0


Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.




--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

 

Try changing the ownership of /dev/ttyS0 -- your listing did not show it belonging to the dialout group.

On Wed, Sep 30, 2020 at 4:59 PM KB5ZUR <kb5zur@...> wrote:
Hi John,

Still no Joy!  tried your suggestion and the server failed. I stopped the server and ran the AMBEtest3.py and it hangs about half way through the test.
i@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyAMA0
Setting ...
/dev/ttyAMA0
d
8
N
1
False
False
False

Reset
6100010033

grep dialout shows the following:
pi@DV3000SVR:~/ambeserver-install $ grep dialout /etc/group
dialout:x:20:pi,opendv
 AMBEtest3,py with ttyS0 seems to complete

pi@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes

Product ID
6100010030
Wrote: 5 bytes

Version
6100010031
Wrote: 5 bytes

Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

What now coach?

-David
KB5ZUR


On Wed, Sep 30, 2020 at 11:25 AM John D Hays - K7VE <john@...> wrote:
OK, normally the PiDV™ would be on /dev/ttyAMA0 and not /dev/ttyS0 (Pi4 may re-map).

Give a try with:
sudo systemctl stop ambeserver@...  
sudo systemctl disable ambeserver@...  
sudo systemctl start ambeserver@...  
sudo systemctl status ambeserver@... 

If all is good, then

sudo systemctl enable ambeserver@...    

You can verify that opendv is in the dialout group with
 grep dialout /etc/group

Which should return something like:
dialout:x:20:opendv     

On Wed, Sep 30, 2020 at 6:58 AM KB5ZUR <kb5zur@...> wrote:
John,
Her you go.
-DS

pi@DV3000SVR:~/ambeserver-install $ ls -l /dev/tty*

crw-rw---- 1 root dialout 204, 64 Sep 29 15:13 /dev/ttyAMA0
crw--w---- 1 root tty       4, 64 Sep 29 17:56 /dev/ttyS0


Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.




--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

KB5ZUR
 

Hi John,

Still no Joy!  tried your suggestion and the server failed. I stopped the server and ran the AMBEtest3.py and it hangs about half way through the test.
i@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyAMA0
Setting ...
/dev/ttyAMA0
d
8
N
1
False
False
False

Reset
6100010033

grep dialout shows the following:
pi@DV3000SVR:~/ambeserver-install $ grep dialout /etc/group
dialout:x:20:pi,opendv
 AMBEtest3,py with ttyS0 seems to complete

pi@DV3000SVR:~/ambeserver-install $ sudo python AMBEtest3.py -s /dev/ttyS0
Setting ...
/dev/ttyS0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes

Product ID
6100010030
Wrote: 5 bytes

Version
6100010031
Wrote: 5 bytes

Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

What now coach?

-David
KB5ZUR


On Wed, Sep 30, 2020 at 11:25 AM John D Hays - K7VE <john@...> wrote:
OK, normally the PiDV™ would be on /dev/ttyAMA0 and not /dev/ttyS0 (Pi4 may re-map).

Give a try with:
sudo systemctl stop ambeserver@...  
sudo systemctl disable ambeserver@...  
sudo systemctl start ambeserver@...  
sudo systemctl status ambeserver@... 

If all is good, then

sudo systemctl enable ambeserver@...    

You can verify that opendv is in the dialout group with
 grep dialout /etc/group

Which should return something like:
dialout:x:20:opendv     

On Wed, Sep 30, 2020 at 6:58 AM KB5ZUR <kb5zur@...> wrote:
John,
Her you go.
-DS

pi@DV3000SVR:~/ambeserver-install $ ls -l /dev/tty*

crw-rw---- 1 root dialout 204, 64 Sep 29 15:13 /dev/ttyAMA0
crw--w---- 1 root tty       4, 64 Sep 29 17:56 /dev/ttyS0


Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.




--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

 



--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

 

OK, normally the PiDV™ would be on /dev/ttyAMA0 and not /dev/ttyS0 (Pi4 may re-map).

Give a try with:
sudo systemctl stop ambeserver@...  
sudo systemctl disable ambeserver@...  
sudo systemctl start ambeserver@...  
sudo systemctl status ambeserver@... 

If all is good, then

sudo systemctl enable ambeserver@...    

You can verify that opendv is in the dialout group with
 grep dialout /etc/group

Which should return something like:
dialout:x:20:opendv     


On Wed, Sep 30, 2020 at 6:58 AM KB5ZUR <kb5zur@...> wrote:
John,
Her you go.
-DS

pi@DV3000SVR:~/ambeserver-install $ ls -l /dev/tty*

crw-rw---- 1 root dialout 204, 64 Sep 29 15:13 /dev/ttyAMA0
crw--w---- 1 root tty       4, 64 Sep 29 17:56 /dev/ttyS0


Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.




--
John D. Hays
Kingston, WA
K7VE

 


Re: PiDV, AMBEserver and Buster

KB5ZUR
 

John,
Her you go.
-DS

pi@DV3000SVR:~/ambeserver-install $ ls -l /dev/tty*
crw-rw-rw- 1 root tty       5,  0 Sep 29 15:13 /dev/tty
crw--w---- 1 root tty       4,  0 Sep 29 15:13 /dev/tty0
crw------- 1 pi   tty       4,  1 Sep 29 15:13 /dev/tty1
crw--w---- 1 root tty       4, 10 Sep 29 15:13 /dev/tty10
crw--w---- 1 root tty       4, 11 Sep 29 15:13 /dev/tty11
crw--w---- 1 root tty       4, 12 Sep 29 15:13 /dev/tty12
crw--w---- 1 root tty       4, 13 Sep 29 15:13 /dev/tty13
crw--w---- 1 root tty       4, 14 Sep 29 15:13 /dev/tty14
crw--w---- 1 root tty       4, 15 Sep 29 15:13 /dev/tty15
crw--w---- 1 root tty       4, 16 Sep 29 15:13 /dev/tty16
crw--w---- 1 root tty       4, 17 Sep 29 15:13 /dev/tty17
crw--w---- 1 root tty       4, 18 Sep 29 15:13 /dev/tty18
crw--w---- 1 root tty       4, 19 Sep 29 15:13 /dev/tty19
crw--w---- 1 root tty       4,  2 Sep 29 15:13 /dev/tty2
crw--w---- 1 root tty       4, 20 Sep 29 15:13 /dev/tty20
crw--w---- 1 root tty       4, 21 Sep 29 15:13 /dev/tty21
crw--w---- 1 root tty       4, 22 Sep 29 15:13 /dev/tty22
crw--w---- 1 root tty       4, 23 Sep 29 15:13 /dev/tty23
crw--w---- 1 root tty       4, 24 Sep 29 15:13 /dev/tty24
crw--w---- 1 root tty       4, 25 Sep 29 15:13 /dev/tty25
crw--w---- 1 root tty       4, 26 Sep 29 15:13 /dev/tty26
crw--w---- 1 root tty       4, 27 Sep 29 15:13 /dev/tty27
crw--w---- 1 root tty       4, 28 Sep 29 15:13 /dev/tty28
crw--w---- 1 root tty       4, 29 Sep 29 15:13 /dev/tty29
crw--w---- 1 root tty       4,  3 Sep 29 15:13 /dev/tty3
crw--w---- 1 root tty       4, 30 Sep 29 15:13 /dev/tty30
crw--w---- 1 root tty       4, 31 Sep 29 15:13 /dev/tty31
crw--w---- 1 root tty       4, 32 Sep 29 15:13 /dev/tty32
crw--w---- 1 root tty       4, 33 Sep 29 15:13 /dev/tty33
crw--w---- 1 root tty       4, 34 Sep 29 15:13 /dev/tty34
crw--w---- 1 root tty       4, 35 Sep 29 15:13 /dev/tty35
crw--w---- 1 root tty       4, 36 Sep 29 15:13 /dev/tty36
crw--w---- 1 root tty       4, 37 Sep 29 15:13 /dev/tty37
crw--w---- 1 root tty       4, 38 Sep 29 15:13 /dev/tty38
crw--w---- 1 root tty       4, 39 Sep 29 15:13 /dev/tty39
crw--w---- 1 root tty       4,  4 Sep 29 15:13 /dev/tty4
crw--w---- 1 root tty       4, 40 Sep 29 15:13 /dev/tty40
crw--w---- 1 root tty       4, 41 Sep 29 15:13 /dev/tty41
crw--w---- 1 root tty       4, 42 Sep 29 15:13 /dev/tty42
crw--w---- 1 root tty       4, 43 Sep 29 15:13 /dev/tty43
crw--w---- 1 root tty       4, 44 Sep 29 15:13 /dev/tty44
crw--w---- 1 root tty       4, 45 Sep 29 15:13 /dev/tty45
crw--w---- 1 root tty       4, 46 Sep 29 15:13 /dev/tty46
crw--w---- 1 root tty       4, 47 Sep 29 15:13 /dev/tty47
crw--w---- 1 root tty       4, 48 Sep 29 15:13 /dev/tty48
crw--w---- 1 root tty       4, 49 Sep 29 15:13 /dev/tty49
crw--w---- 1 root tty       4,  5 Sep 29 15:13 /dev/tty5
crw--w---- 1 root tty       4, 50 Sep 29 15:13 /dev/tty50
crw--w---- 1 root tty       4, 51 Sep 29 15:13 /dev/tty51
crw--w---- 1 root tty       4, 52 Sep 29 15:13 /dev/tty52
crw--w---- 1 root tty       4, 53 Sep 29 15:13 /dev/tty53
crw--w---- 1 root tty       4, 54 Sep 29 15:13 /dev/tty54
crw--w---- 1 root tty       4, 55 Sep 29 15:13 /dev/tty55
crw--w---- 1 root tty       4, 56 Sep 29 15:13 /dev/tty56
crw--w---- 1 root tty       4, 57 Sep 29 15:13 /dev/tty57
crw--w---- 1 root tty       4, 58 Sep 29 15:13 /dev/tty58
crw--w---- 1 root tty       4, 59 Sep 29 15:13 /dev/tty59
crw--w---- 1 root tty       4,  6 Sep 29 15:13 /dev/tty6
crw--w---- 1 root tty       4, 60 Sep 29 15:13 /dev/tty60
crw--w---- 1 root tty       4, 61 Sep 29 15:13 /dev/tty61
crw--w---- 1 root tty       4, 62 Sep 29 15:13 /dev/tty62
crw--w---- 1 root tty       4, 63 Sep 29 15:13 /dev/tty63
crw--w---- 1 root tty       4,  7 Sep 29 15:13 /dev/tty7
crw--w---- 1 root tty       4,  8 Sep 29 15:13 /dev/tty8
crw--w---- 1 root tty       4,  9 Sep 29 15:13 /dev/tty9
crw-rw---- 1 root dialout 204, 64 Sep 29 15:13 /dev/ttyAMA0
crw------- 1 root root      5,  3 Sep 29 15:13 /dev/ttyprintk
crw--w---- 1 root tty       4, 64 Sep 29 17:56 /dev/ttyS0

On Tue, Sep 29, 2020 at 6:38 PM John D Hays - K7VE <john@...> wrote:
Provide a listing of the command

ls -l /dev/tty*

On Tue, Sep 29, 2020 at 2:12 PM KB5ZUR <kb5zur@...> wrote:
On Fri, Apr 24, 2020 at 06:42 PM, John D Hays - K7VE wrote:
sudo usermod -G dialout opendv
Hi John,
I'm at exactly this same point with my PiDV on a new Raspberry pi 3B+ install.
PiDV works with ttl to usb adaptor in wibdows and passed AMBEtest3.py fine.

Tried the "sudo usermod -G dialout opendv with no success. I still get the following errors when trying to run ambeserver@ttyS0
pi@DV3000SVR:~/ambeserver-install $ sudo systemctl status ambeserver@...
● ambeserver@... - AMBEserver Daemon
   Loaded: loaded (/etc/systemd/system/ambeserver@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-09-29 15:38:36 CDT; 34s ago
 Main PID: 1546 (code=exited, status=1/FAILURE)
 
Sep 29 15:38:36 DV3000SVR systemd[1]: Starting AMBEserver Daemon...
Sep 29 15:38:36 DV3000SVR systemd[1]: Started AMBEserver Daemon.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Starting...
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Opened serial port /dev/ttyS0 at 230400 bps.
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Unable to open GPIO export interface: Permission denied
Sep 29 15:38:36 DV3000SVR AMBEserver[1546]: AMBEserver: Could not initialize the DV3K!
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Main process exited, code=exited, status=1/FAIL
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Failed with result 'exit-code'.
Sep 29 15:38:36 DV3000SVR systemd[1]: ambeserver@...: Triggering OnFailure= dependencies.
lines 1-14/14 (END)


seems to be some sort of GPIO Permission denied error.

Driving me a bit crazy trying to figure this out. Any help is appreciated.



--
John D. Hays
Kingston, WA
K7VE

 

221 - 240 of 1660