|
Re: Thumb DV Baud rate change
#ambe
#ambeserver
#thumbdv
Mike, thanks! John sent it to me and it does look quite formatible for thesej old eyes! 73 WB5EKU
|
|
|
|
Re: Thumb DV Baud rate change
#ambe
#ambeserver
#thumbdv
Hi John, Yes, I would like to have my original one and my newer one run at the same baud rate for a transcoder project.
On Fri, Oct 9, 2020 at 5:51 PM John D Hays - K7VE <john@...> wrote:
|
|
|
|
Re: Thumb DV Baud rate change
#ambe
#ambeserver
#thumbdv
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
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, Please review http://nwdigitalradio.com/thumbdv-model-a/ 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.
|
|
|
|
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)
73's Doug KC0EQA
|
|
|
|
Re: order
Out of the Office Friday, took care of this already.
toggle quoted messageShow quoted text
73 Bryan K7UDR
|
|
|
|
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
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:
|
|
|
|
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:
--
John D. Hays Kingston, WA K7VE
|
|
|
|
Re: PiDV, AMBEserver and Buster
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:
|
|
|
|
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
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 Installed the AMBEserver per https://github.com/nwdigitalradio/ambeserver-install 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:
|
|
|
|
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:
--
John D. Hays Kingston, WA K7VE
|
|
|
|
Re: PiDV, AMBEserver and Buster
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:
|
|
|
|
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:
--
John D. Hays Kingston, WA K7VE
|
|
|
|
Re: PiDV, AMBEserver and Buster
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:
|
|
|
|
Re: PiDV, AMBEserver and Buster
Be sure to review https://github.com/nwdigitalradio/ambeserver-install John D. Hays Kingston, WA K7VE
|
|
|