Re: ambe
#ambeserver
Charles Wiant
Thanks to all ambe server is up and running
From: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io> On Behalf Of John D Hays - K7VE
Systemd Management of AMBEserver
A set of files for systemd management are located in the files section of the ambe subgroup on groups.io: ambesupport.tgz
mv ambesupport.tgz /tmp && cd / && sudo tar -xzvf /tmp/ambesupport.tgz From the Wiki -- https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum
Configuration File Location The systemd configuration files for AMBEserver are located in /etc/opendv cd /etc/opendv If your device is at a different location, e.g. /dev/ttyUSB1 simply copy the similar file and give it a new name with the new device sudo cp ambeserver-ttyUSB0.conf ambeserver-ttyUSB1.conf Modifying the Configuration FileUse an editor like vi or nano to edit your configuration file sudo vi /etc/opendv/ambeserver-ttyUSB0.conf There are two environment variables that may be modified namely UDP_PORT and AMBESERVER_FLAGS Here are the contents of the configuration file: # # Configuration file for the AMBEserver program started by systemd. # Adding flags to AMBESERVER_FLAGS will pass this to the daemon. # For example, to change the speed to 460800, use the following line: # AMBESERVER_FLAGS="-s 460800" # UDP_PORT=2460 AMBESERVER_FLAGS="" For example, on the newer ThumbDV™ (Rev. A) you would modify the AMBESERVER_FLAGS variable AMBESERVER_FLAGS="-s 460800" To have AMBEserver listen on another UDP port, which is useful if you have more than one AMBEserver running on a single Raspberry Pi -- each with its own AMBE device. UDP_PORT=18307 Managing the AMBEserverThe commands for checking, starting, stopping, enabling, and disabling the AMBEserver are as follows: sudo systemctl status ambeserver@... sudo systemctl start ambeserver@... sudo systemctl stop ambeserver@... sudo systemctl enable ambeserver@... sudo systemctl disable ambeserver@... Modify the tty service name as appropriate by replacing ttyUSB0 with:
Enabling the service will allow the AMBEserver to automatically restart when the Raspberry Pi is restarted.
----- If using the command line to start ambeserver in a terminal shell, and you don't want it to go away when you disconnect or logout, use nohup before the command and an & after. For an explanation of nohup, issue the command:
man nohup
John D. Hays K7VE
|
|
Re: ambe
#ambeserver
Note: You may need to create the opendv user, if it doesn't exist
sudo useradd opendv sudo usermod -G dialout opendv Systemd Management of AMBEserver A set of files for systemd management are located in the files section of the ambe subgroup on groups.io: ambesupport.tgz
Download this file to the target computer's filesystem and run mv ambesupport.tgz /tmp && cd / && sudo tar -xzvf /tmp/ambesupport.tgz
From the Wiki -- https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum
Configuration File Location
The systemd configuration files for AMBEserver are located in /etc/opendv cd /etc/opendv If your device is at a different location, e.g. /dev/ttyUSB1 simply copy the similar file and give it a new name with the new device sudo cp ambeserver-ttyUSB0.conf ambeserver-ttyUSB1.conf
Modifying the Configuration FileUse an editor like vi or nano to edit your configuration file sudo vi /etc/opendv/ambeserver-ttyUSB0.conf
There are two environment variables that may be modified namely UDP_PORT and AMBESERVER_FLAGS Here are the contents of the configuration file: # # Configuration file for the AMBEserver program started by systemd. # Adding flags to AMBESERVER_FLAGS will pass this to the daemon. # For example, to change the speed to 460800, use the following line: # AMBESERVER_FLAGS="-s 460800" # UDP_PORT=2460 AMBESERVER_FLAGS="" For example, on the newer ThumbDV™ (Rev. A) you would modify the AMBESERVER_FLAGS variable AMBESERVER_FLAGS="-s 460800"
To have AMBEserver listen on another UDP port, which is useful if you have more than one AMBEserver running on a single Raspberry Pi -- each with its own AMBE device. UDP_PORT=18307
Managing the AMBEserverThe commands for checking, starting, stopping, enabling, and disabling the AMBEserver are as follows: sudo systemctl status ambeserver@... sudo systemctl start ambeserver@... sudo systemctl stop ambeserver@... sudo systemctl enable ambeserver@... sudo systemctl disable ambeserver@... Modify the tty service name as appropriate by replacing ttyUSB0 with:
Enabling the service will allow the AMBEserver to automatically restart when the Raspberry Pi is restarted.
-----
If using the command line to start ambeserver in a terminal shell, and you don't want it to go away when you disconnect or logout, use nohup before the command and an & after. For an explanation of nohup, issue the command:
man nohup
John D. Hays
Kingston, WA K7VE
|
|
Re: ambe
#ambeserver
screen utility is good.. also there is byobu for linux command line. byobu is a great screen multiplexer that works on the console. I like it because you can have terminal windows side by side like with screen but you get more information at the bottom of the window with byobu. also byobu has mouse functionality with point and click to choose window and it is more user friendly in my opinion. screen is just as good at what it does also, but my choice is with byobu. sudo apt install screen byobu -y To get a list of the commands used with each program type: screen --help or byobu --help
VE3WVJ 73
|
|
Re: ambe
#ambeserver
Mike Norrbom
You can also install the screen utility.
https://linuxize.com/post/how-to-use-linux-screen/
I use it for many linux programs.
Thanks, Mike (N0VZC)
From: ambe@nw-digital-radio.groups.io <ambe@nw-digital-radio.groups.io>
On Behalf Of VE3WVJ
Sent: Wednesday, May 22, 2019 11:06 PM To: ambe@nw-digital-radio.groups.io Subject: Re: [ambe] ambe #ambeserver
[Edited Message Follows] make sure to type "&" after the command you want to run. This makes it run in the background. So you would need to type "AMBEServer &" in the terminal without the quotes to make it run after you close the terminal. Do not put the quotations. just type the command that is inside the quotations. Type this into the Terminal: AMBEServer & This should run the application in the background.. You can check that it is running using: ps aux | grep AMBEServer
Bill
|
|
Re: ambe
#ambeserver
make sure to type "&" after the command you want to run. This makes it run in the background. So you would need to type "AMBEServer &" in the terminal without the quotes to make it run after you close the terminal. Do not put the quotations. just type the command that is inside the quotations. Type this into the Terminal: AMBEServer & This should run the application in the background.. You can check that it is running using: ps aux | grep AMBEServer
Bill
|
|
ambe
#ambeserver
Charles Wiant
when i close terminal ambe server quits working any ideas
|
|
Re: Thumb DV with Android Phone
I wonder if anyone has tried a Y-cable so you can charge and plug in the Thumb DV at the same time.
Mike WM4B
From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of Gwen Patton
I tried using it plugged into my phone, but the battery drain was prohibitive. So I installed AMBEServer on a raspberry pi, punched a hole in my firewall, and set up a dynamic DNS for it. BlueDV AMBE connects to the ThumbDV, which is plugged into the pi through a powered USB hub.
Works perfectly.
73, Gwen, NG3P
On Fri, Apr 26, 2019, 10:35 PM Brent LeFevre <brent.lefevre@...> wrote:
|
|
Re: Thumb DV with Android Phone
Ludovic Ludo
Le 27/04/2019 à 03:03, Mike Besemer a
écrit :
Hello, audio depend on the quality of your phone. For me, fine like you can heard on : http://radioamateur.forumsactifs.com/t2159-dmr-et-dstar-sans-emetteur-recepteur-directement-sur-ordinateur-ou-telephone-portable-smartphone All info on http://radioamateur.forumsactifs.com/f35-dmr-dstar-c4fm (Use Google translate) Best regards, Ludovic - F5PBG
|
|
Re: Thumb DV with Android Phone
I tried using it plugged into my phone, but the battery drain was prohibitive. So I installed AMBEServer on a raspberry pi, punched a hole in my firewall, and set up a dynamic DNS for it. BlueDV AMBE connects to the ThumbDV, which is plugged into the pi through a powered USB hub. Works perfectly. 73, Gwen, NG3P
On Fri, Apr 26, 2019, 10:35 PM Brent LeFevre <brent.lefevre@...> wrote:
|
|
Re: Thumb DV with Android Phone
Brent LeFevre
I use it with an OTG adaptor to my LGV10, works like a dream.... As expected, it's a bit taxing On the battery of the phone. 73 de W4CHF Brent
On Fri, Apr 26, 2019, 9:03 PM Mike Besemer <mwbesemer@...> wrote:
|
|
Re: Thumb DV with Android Phone
Thanks Robert. Exactly what I needed to hear.
73,
Mike WM4B
From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of Robert Moldenhauer
Sent: Friday, April 26, 2019 9:40 PM To: ambe@nw-digital-radio.groups.io Subject: Re: [ambe] Thumb DV with Android Phone
I use a Galaxy Note 9 with a ThumbDV plugged into it directly with an OTG cable. I run BlueDV AMBE app. he combination works perfectly. I have access to DStar, DMR, and DM+ talkgroups, no C4FM at this point. I just checked into the Canadian DStar Net. Only issue is that the who screen is the push to talk and without a case it's easy to transmit by accident. Would like to hear from users who are using a Thumb DV with their Android phone. I’m very interested in this combination, but due to the fact that I’ve already got too many irons in the fire, I’d like to know what I’m getting in to first. Looks like Blue DV might be the way to go. Thoughts? 73, Mike WM4B
|
|
Re: Thumb DV with Android Phone
I use a Galaxy Note 9 with
a ThumbDV plugged into it directly with an OTG cable. I run BlueDV AMBE
app. he combination works perfectly. I have access to DStar, DMR, and
DM+ talkgroups, no C4FM at this point. I just checked into the Canadian
DStar Net. Only issue is that the who screen is the push to talk and
without a case it's easy to transmit by accident.
toggle quoted messageShow quoted text
Robert VK2DY Mike Besemer wrote on 27/4/19 11:03 am:
|
|
Thumb DV with Android Phone
Would like to hear from users who are using a Thumb DV with their Android phone. I’m very interested in this combination, but due to the fact that I’ve already got too many irons in the fire, I’d like to know what I’m getting in to first. Looks like Blue DV might be the way to go. Thoughts? 73, Mike WM4B
|
|
Re: DVSI USB-3000
Serdar ULUKONAKCI
Hi Scott,
toggle quoted messageShow quoted text
I tried 460800 for the baud rate but no luck :-(
On 24.03.2019 05:27, Scott Weis
(KB2EAR) via Groups.Io wrote:
|
|
Re: DVSI USB-3000
Scott Weis (KB2EAR)
Try 460800 for the baud rate.
From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of Serdar ULUKONAKCI
Sent: Saturday, March 23, 2019 5:44 PM To: ambe@nw-digital-radio.groups.io Subject: Re: [ambe] DVSI USB-3000
Hi John, On 23.03.2019 23:56, John D Hays - K7VE wrote:
|
|
Re: DVSI USB-3000
Serdar ULUKONAKCI
Hi John,
toggle quoted messageShow quoted text
You are great and thank you very much for your answers about my DVSI USB-3000. I can give you a SSH access to my RPI for your tests if you have time for further tests. Best Regards, Serdar On 23.03.2019 23:56, John D Hays - K7VE
wrote:
|
|
Re: DVSI USB-3000
Is that the right baud rate for the USB-3000? (I don't own one, and there has been no testing in of the USB-3000 with ThumbTest.exe)
On Sat, Mar 23, 2019 at 12:53 PM Serdar ULUKONAKCI <ta3as@...> wrote:
|
|
Re: DVSI USB-3000
Serdar ULUKONAKCI
Hi, I tested my DVSI USB-3000 with Thumbtest.exe program. Weird response. Any clue?
|
|
Re: Original ThumbDV and AMBED
Scott Weis (KB2EAR)
I have now confirmed that it does indeed work.
Two changes need to be made. First the Product Description needs to be reflashed to read any of the following “ThumbDV" or "DVstick-30" or "USB-3000". Any of which work fine. I used a program call FT_PROG. https://www.ftdichip.com/Support/Utilities.htm?#FT_PROG
Second, in the file cusb3000interface.cpp change line int baudrate = 460800; to int baudrate = 230400; Then recompile.
And as long as you have 2 devices, or at least 2 channels that it recognizes it works just fine. (I used an AMBE3003 device for the second one.) The software will not initialize with only one. You also can’t have a new 460800 baud and an old 240400 baud ThumbDV on the same system.
Hope that helps anyone else going down this road.
73, Scott KB2EAR
From: ambe@nw-digital-radio.groups.io [mailto:ambe@nw-digital-radio.groups.io] On Behalf Of John D Hays - K7VE
I am not sure if it will work, that is a question for the xlxd group.
But besides the baud rate the ThumbDV needs to be programmed with an identifier that the ambed server knows.
On Thu, Mar 14, 2019, 21:59 Scott Weis (KB2EAR) via Groups.Io <kb2ear=kb2ear.net@groups.io> wrote:
|
|
Dummyrepeater Issue
Hello all,
Still having issues with getting my PiDV up and running. Have moved to a Pi 3B+ and now have AMBEserver and ircddbgateway installed and running. I am using /dev/ttyS0 for the PiDV. (Both installed from Synaptic Package Manager). Dummyrepeater was also installed from Synaptic.
When I start AMBEserver, I get a message that it is listening on Port 2460. I also see traffic on ircddbgateway, so I feel confident that both are working. Dummyrepeater starts normally, but I think there is a configuration issue. I have a PiDV installed on the Pi 3B+ GPIO pins.
When I go to configure it, as I understand it, under ‘Dongle’, I should select ‘DV Serial’, but when I do that, dummyrepeater cannot find the dongle. If I select ‘Network’ and enter the local IP of the Pi, then the dongle is found and I can transmit. However, when I connect to a reflector, all I get bad is R2D2. Same for the Echo reflector. $ sudo python AMBEtest2.py produces:
D 8 N 1 False False False 0
Reset 6100010033 Any pointers? 73, Mike WM4B
|
|