Re: ThumbDV used as an AMBE Server
TG9AOR
Also to be noted is that now the DVMega is not working either. I did not run apt-get upgrade when I unpacked the image before trying out the AMBE Server project.Will stop here for now, time to go to bed. 73 de TG9AOR
|
|
Re: ThumbDV used as an AMBE Server
These are two separate issues. If you are not using bluetooth, uninstall/purge those two packages. It appears that the daemon is not getting a response to a reset command on the ThumbDV. Make sure you have it on /dev/ttyUSB0 (or adjust accordingly) -- and make sure to have the baud rate set to 460800 in the configuration file (see the Wiki for instructions). Perhaps your DVMega and ThumbDV are on different USB port numbers than what you have configured.
On Tue, Feb 7, 2017 at 7:05 PM, TG9AOR via Groups.Io <agroaviation@...> wrote:
|
|
Re: ThumbDV used as an AMBE Server
TG9AOR
I went ahead and reinstalled the image, and started from 0. The issue with the DVMega was, that when I did apt-get upgrade, the /boot/cmdline.txt got replaced, and so it called for a fsk repair item that is not to be there in order for the DVMega to work. It did. Once I got the DVMega working again, I installed ambeserver, configured per wiki (ttyUSB0) and enabled and started via systemctl, all worked well(The ambeserver operation, never got to linking over the net with dummyrepeater). However, once ambeserver got up and running the DVMega went bad again, in the sense that when I verified operation I exited the program (it is GUI, I have no seed file or know how to configure both G4KLX suites via daemon with compass) and after verification of proper ambeserver operation I restarted dstarrepeater and it behaved the same way as yesterday. I went ahead and reinstalled the image, installed both ircDDBGateway and DStarRepeater and all is well, now I will install the node dashboard in a while. Anyway I enjoyed the project, I like it that it does make me read and research and learn more than in High School or my short stroll through College! 73 and many thanks. TG9AOR
|
|
Re: ThumbDV used as an AMBE Server
TG9AOR
I went ahead and installed compass lite on a separate Rpi3, insterted the ThumbDV and installed ambeserver, and: pi@TG9AOR:~ $ sudo systemctl status ambeserver@... -l Feb 09 12:16:47 TG9AOR systemd[1]: Started DV3000 Daemon. So the setup now is Rpi2 with DVMega(Repeater2) and ircDDBGateway -192.168.0.10-connected to Repeater 1 via 192.168.0.12 & Port 20011 RPi3 with ThumbDV and ambeserver-192.168.0.11-Listening on port 2460 Windows 10 Laptop with DummyRepeater(Repeater 1)-192.168.0.12-Connected to ambeserver via the Dongle Tab on DummyRepeater(DV3000 Network-192.168.0.11 & Port 2460) and connected to ircDDBGateway via the Network Tab(Gateway 192.168.0.10 & Port 20010) and this is where I am not sure, I left Local IP Address 127.0.0.1 & Port 20011, but I have no devices attached here to this laptop. The DummyRepeater does not connect to the Gateway, it does not bring up the not linked status. When I press the Transmit button on the laptop, the ThumbDV does light up, but I do not pass any audio to the Gateway as I am connected to REF012E for testing and the audio does not come back to the laptop. I do see on the Gateway's log passing AMBE to port 20011 but I do not hear a thing on my laptop. What did I miss?? Thanks.
|
|
Re: ThumbDV used as an AMBE Server
Your ircddbgateway needs HB listening on 0.0.0.0 and make sure your repeater 2 (DummyRepeater) on ircddbgateway has the laptop's IP address.
On Feb 9, 2017 04:30, "TG9AOR via Groups.Io" <agroaviation=yahoo.com@groups.io> wrote:
|
|
Re: ThumbDV used as an AMBE Server
Is your HB Local adress is 0.0.0.0 ?
toggle quoted messageShow quoted text
If you have 127.0.0.1, change it! You must use 0.0.0.0 to listen all interfaces. Look my "print screen". Nicolas - F8FKD --------------------------------------------
En date de : Jeu 9.2.17, John D Hays - K7VE <john@hays.org> a écrit :
Objet: Re: [ambe] ThumbDV used as an AMBE Server À: ambe@nw-digital-radio.groups.io Date: Jeudi 9 février 2017, 16h37 Your ircddbgateway needs HB listening on 0.0.0.0 and make sure your repeater 2 (DummyRepeater) on ircddbgateway has the laptop's IP address. On Feb 9, 2017 04:30, "TG9AOR via Groups.Io" <agroaviation=yahoo.com@groups.io> wrote: I went ahead and installed compass lite on a separate Rpi3, insterted the ThumbDV and installed ambeserver, and:pi@TG9AOR:~ $ sudo systemctl status ambeserver@ttyUSB0.service -l ● ambeserver@ttyUSB0.service - DV3000 Daemon Loaded: loaded (/lib/systemd/system/ ambeserver@.service; enabled) Active: active (running) since Thu 2017-02-09 12:16:47 UTC; 2min 28s ago Process: 702 ExecStartPre=/bin/chmod 0660 /dev/%i (code=exited, status=0/SUCCESS) Process: 687 ExecStartPre=/bin/chgrp dialout /dev/%i (code=exited, status=0/SUCCESS) Main PID: 717 (AMBEserver) CGroup: /system.slice/system- ambeserver.slice/ambeserver@ ttyUSB0.service └─717 /usr/sbin/AMBEserver -p 2460 -i /dev/ttyUSB0 -s 460800Feb 09 12:16:47 TG9AOR systemd[1]: Started DV3000 Daemon. Feb 09 12:16:47 TG9AOR AMBEserver[717]: AMBEserver: Starting... Feb 09 12:16:47 TG9AOR AMBEserver[717]: AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 bps. Feb 09 12:16:47 TG9AOR AMBEserver[717]: AMBEserver: Initialized AMBE3000R version V120.E100.XXXX.C106.G514.R009. B0010411.C0020208. Feb 09 12:16:47 TG9AOR AMBEserver[717]: AMBEserver: Listening for connections on UDP port 2460. So the setup now isRpi2 with DVMega(Repeater2) and ircDDBGateway -192.168.0.10-connected to Repeater 1 via 192.168.0.12 & Port 20011RPi3 with ThumbDV and ambeserver-192.168.0.11- Listening on port 2460Windows 10 Laptop with DummyRepeater(Repeater 1)-192.168.0.12-Connected to ambeserver via the Dongle Tab on DummyRepeater(DV3000 Network-192.168.0.11 & Port 2460) and connected to ircDDBGateway via the Network Tab(Gateway 192.168.0.10 & Port 20010) and this is where I am not sure, I left Local IP Address 127.0.0.1 & Port 20011, but I have no devices attached here to this laptop. The DummyRepeater does not connect to the Gateway, it does not bring up the not linked status. When I press the Transmit button on the laptop, the ThumbDV does light up, but I do not pass any audio to the Gateway as I am connected to REF012E for testing and the audio does not come back to the laptop. I do see on the Gateway's log passing AMBE to port 20011 but I do not hear a thing on my laptop. What did I miss?? Thanks.
|
|
Re: ThumbDV used as an AMBE Server
TG9AOR
John! It worked! Thank you so much! I did have to set the Local IP address on my DummyRepeater to 0.0.0.0 in order for it to work, just setting the HB IP to 0.0.0.0 and leaving the laptop´s IP to 127.0.0.1 did not cut it. I did see the following output from the gateway when I transmitted: M: 2017-02-09 19:46:42: Linking TG9AOR A to DCS502 B But, if transmitted with my radio the output was different, as in not unknown: M: 2017-02-09 19:50:48: From RF I am ver very happy to have completed this project, I really appreciate your support. Have a great day! TG9AOR
|
|
Re: ThumbDV used as an AMBE Server
TG9AOR
Dear Nicolas F8FKD: Thanks for your information. TG9AOR
|
|
Re: ThumbDV used as an AMBE Server
TG9AOR
As an update, I deleted and reentered my callsign data from all fields in Dummy Repeater and now it checks out OK on the Gateway: M: 2017-02-10 00:11:13: GATEWAY: OE9PKV G 194.208.145.43 73
|
|
Xfrelextors
Abbot Carder
Hello, I having issues with hearing and speaking with people in xreflectors. I spoke with a ham who was using a mega board today just fine. We could hear each other and talk just fine. Others using other devices including a dv4mini I was unable to hear. In some cases they could not hear me either. Wondering if anyone else is having this issue or if there is a fix. Thanks I am using the ambe3000 board with a raspberry pi3 and Buster on a mac because I am unable to get xreflectors to work on my pi. I love to board just have some issues with a few things. Thanks --
|
|
ThumbDV & Buster / Mac
J.R. Jesson, N7JRJ
I’ve just received the ThumbDV from NW Digital Radio. I’m trying to use Buster, but when I select the serial device representing the ThumbDV and try to set the port speed to 460800, buster locks up. I’m running MacOS Sierra. I've googled and checked this forum. My next step will be to setup the ThumbDB on a Pi3/Compass, but I’d like to get this working on my laptop if possible. Jeremy McDermond's site is down (NH6Z), so I thought I would ask here. Advice appreciated! 73, J.R., N7JRJ
|
|
Re: ThumbDV & Buster / Mac
Lyn
HI J.R.
toggle quoted messageShow quoted text
I am using a ThumbDV and Buster with Sierra 10.12.4 and it works OK with baud set to 46800 - see attached screen shot. I don’t remember doing anything special when I installed Buster, but that was some time ago. As far a I can tell, there is no support for Buster to keep host files (or however they use to add new reflectors) so what you get is all there is. Also, the voice prompt when you link/unlink has gone away recently. 73, Lyn - KC8I
|
|
Re: ThumbDV & Buster / Mac
Craig McVeay <cmcveay@...>
J.R., I had a similar issue and I found that it was caused by the FTDI drivers that I had installed for another device. I did the uninstall process for the drivers, restarted the laptop and then plugged in the dongle and fired up Buster to find everything working as it should.
On Sat, Mar 4, 2017 at 12:07 PM, <N7JRJ@...> wrote:
|
|
Re: ThumbDV & Buster / Mac
J.R. Jesson, N7JRJ
Lyn- Thanks for the quick reply. I'm running Sierra release 10.12.3 (notice you're running beta -- very brave). Buster finds my serial port, but when I switch from the default 230400, I get beachball, full cpu usage, and the vocoder isn't found. I've rebooted to ensure system is clean. I've checked logs, but see nothing from Buster. 73, J.R., N7JRJ
|
|
Re: ThumbDV & Buster / Mac
Brendan O'Neill
I’m using ThumbDV with Buster on OSX 10.11.6 El Capitan and it’s working just fine and continues to have voice so long as in Preferences > Audio > Announce Reflector Status Change is checked. Working here as advertised for some time now…
73, Brendan KM4HRR
|
|
Re: ThumbDV & Buster / Mac
J.R. Jesson, N7JRJ
Craig- Thanks! I double checked and do not have the FTDI drivers installed. I did boot into my Bootcamp partition and all is well with the ThumbDV in Windows. I'd prefer to run MacosX, however. Continuing to Troubleshoot. 73, J.R., N7JRJ
|
|
Re: ThumbDV & Buster / Mac
Lyn
J.R. Regarding 10.12.4 beta, this is a first for me. I recently inherited this 2011 iMac and added it to my fleet. It was giving me fits by losing WIFI when asleep and then wouldn't reconnect. I tried some recommended fixes, but they only lasted a day or so. I decided I didn’t have much to lose and possibly they could see what was happening as they monitored my Mac. Strange as it may seem, the problem is gone with 10.12.4 beta. It’s usually better to be lucky than good! No issues at all so far with the beta. 73 and Have Fun! Lyn
|
|
Re: ThumbDV & Buster / Mac - RESOLVED
J.R. Jesson, N7JRJ
It turns out that another application on my Mac, Suunto Moveslink, grabbed the serial port /dev/tty.usbserial-DN00WN4G as soon as the device was inserted. I turned off the Moveslink app and all is well. 73, J.R., N7JRJ
|
|
Re: ThumbDV & Buster / Mac - RESOLVED
Lyn
Thanks J.R.
toggle quoted messageShow quoted text
I thought about looking at the source code out of curiosity but decided that was way above my pay grade. If adding a couple of XREFs isn’t too difficult, I might follow your lead and give it a try later. Lyn
|
|
AMBEServer : Invalid start byte 0x05 (seems to expect 0x61)
Santu OTTAVI (TK1BI)
Hi,
I'm trying to set up a D-Star to Asterisk. I've got a DV3000U/ThumbDV connected on a Raspberry Pi, with the AMBEServer listening. I'm trying to connect to it from another Linux or Windows machine, using "dplus_cli" or "dextra_cli" command line tools from Scott, KI4LKF. With both software (dplus_cli under Linux, and dextra_cli under Windows), I see incoming UDP packets to AMBEServer, but it does not answer. Having a look at AMBEServer source code, I noticed that : - AMBEServer generates an error because it receives an invalid start byte when reading from the socket : 0x05 - AMBEServer seems to wait for DV3K_START_BYTE = 0x61 Any idea about why (old) KI4LKF client software are sending 0x05 as a start byte, while AMBEServer seems to expect 0x61 ? Thank you in advance. Kind regards. 73 de TK1BI
|
|