|
Re: "... this report of my death was an exaggeration." -- Mark Twain 1897
Absolutely nothing. It's a manufacturability change, mostly support parts on the PCB. The functionality and primary chips are the same as the current ThumbDV.
On Mon, Sep 24, 2018 at 3:57 PM N9UMJ <n9umj2@...> wrote:
--
John D. Hays Edmonds, WA K7VE   
|
|
|
|
Re: "... this report of my death was an exaggeration." -- Mark Twain 1897
Judging by the number you still have on hand. Don't you mean The Report of my death has been"grossly" exaggerated? What are the differences between the sale Thumb and the new Thumb that would make.me want to wait and pay full price? Rick n9umj
On Mon, Sep 24, 2018, 6:13 PM John D Hays - K7VE <john@...> wrote:
|
|
|
|
"... this report of my death was an exaggeration." -- Mark Twain 1897
It was reported to me that someone on the International D-STAR net said that the ThumbDV was going out of production. THIS IS NOT TRUE. -- The ThumbDV is on sale for $99.95 on existing stock. NW Digital Radio is continuing the ThumbDV. See http://nwdigitalradio.com/thumbdv-clearance-sale/ for details. If you miss the sale, there is no functional difference, but the new batch will be back at full price. It is best to go the source for information. John D. Hays Edmonds, WA K7VE
|
|
|
|
Re: Linking to XLX reflectors
Ian
Purely as an exercise I have XLX running on a BeagleBoneBlack and today I updated my Macbook with the resulting one-way audio.
toggle quoted messageShow quoted text
A few minutes testing identified my problem and a workaround. Regards, Ian..
On 2018-09-20 20:17, Dick Herrick via Groups.Io wrote:
I suspect it’s an interim solution. Friends using Windows machines
|
|
|
|
Re: Linking to XLX reflectors
Annaliese McDermond
That’s what I figured. The dumb author of this software didn’t know who to ask about preferred protocols to the XLX reflectors and assumed that DExtra would work fine and was the easiest. I’m sure at some point in time soon that she’ll get around to shifting the protocol to connect to XLX reflectors to the DPlus or DCS link drivers instead. I heard she is getting married on Saturday, though, and has very limited time right now.
toggle quoted messageShow quoted text
-- Annaliese McDermond (NH6Z) Xenotropic Systems mcdermj@xenotropic.com
On Sep 20, 2018, at 12:22 PM, Steven Blackford <kb7sqi@gmail.com> wrote:
|
|
|
|
Re: Linking to XLX reflectors
Steven Blackford
There’s been an issue w/ use the XRF protocol w/ XLX reflectors known for a while. That’s why we recommend people use the DPLUS or DCS protocol on our XLX reflectors. I know for some, that can be an issue, but it solved all the problems we had w/ our users. 73 de K4SQI!
Steve, K4SQi
From: Dick Herrick via Groups.Io
Sent: Thursday, September 20, 2018 3:17 PM To: ambe@nw-digital-radio.groups.io Cc: Circuit Riders Subject: Re: [ambe] Linking to XLX reflectors
I suspect it’s an interim solution. Friends using Windows machines can access 2-way audio by calling up the XLX reflectors. What you have here is a work-around which is fine. However, I would not have known the association between the DCS and XLX nomenclature. How did you figure that one out?
I was able to open the plist data in 1.2.3 to compare the “strings” in XLX and DCS plists. Sure enough they point to the same … what appears to be … numeric DNS locations. For your DCS600XLX600 example they both point to 13.16.14.204. So is one a proxy for the other?
Thanks for writing back.
Dick Herrick, BEE, PE
|
|
|
|
Re: Linking to XLX reflectors
Dick Herrick
I suspect it’s an interim solution. Friends using Windows machines can access 2-way audio by calling up the XLX reflectors. What you have here is a work-around which is fine. However, I would not have known the association between the DCS and XLX nomenclature. How did you figure that one out?
toggle quoted messageShow quoted text
I was able to open the plist data in 1.2.3 to compare the “strings” in XLX and DCS plists. Sure enough they point to the same … what appears to be … numeric DNS locations. For your DCS600XLX600 example they both point to 13.16.14.204. So is one a proxy for the other? Thanks for writing back.
|
|
|
|
Re: Linking to XLX reflectors
Ian
I have Buster 1.2.3 and I experienced the same one-way effect. In my case the cure I found is to issue a connect, for example, to DCS600 A instead of XLX600 A.
A connection to XLX defaults to Dextra connection with one-way audio whereas a connect to DCS defaults to DCS and audio is heard in both directions. Is this what you are looking for ? Regards, Ian..
|
|
|
|
Re: Linking to XLX reflectors
Dick Herrick
Yes, same here. I referred to Anna, Buster’s creator. I’m sure she’ll take a look relatively soon.
toggle quoted messageShow quoted text
|
|
|
|
Linking to XLX reflectors
Ted Huston
I’m using Buster on MacBook Pro and ThumbDV. It works on REF reflectors, but not XLX reflectors. Recent update allowed linking to XLX reflector and transmission confirmed on Dashboard. Could not hear person I was trying to communicate with but, he could hear me (using BlueDV on a PC). Any clues?
Ted W8JTH
|
|
|
|
Re: How To install AMBESERVER on Raspbian or Debian.
See updated note on the wiki
On Tue, Sep 18, 2018, 01:39 Node750Tt <node750tt@...> wrote:
|
|
|
|
Re: I want to run BlueDV AMBE Server on Debian.
Go back and see updated wiki notes.
On Tue, Sep 18, 2018, 04:23 <js3cop@...> wrote: Hallo Eric,
|
|
|
|
Re: I want to run BlueDV AMBE Server on Debian.
js3cop@...
Hallo Eric,
I understand it by editing /etc/opendv/ambeserver-ttyUSB0.conf. However, the opendv directory does not exist. So I can not edit ambeserver-ttyUSB0.conf. Where is ConfigFile? I generally recognize that there is a configuration file in / etc. Thanks
|
|
|
|
Re: I want to run BlueDV AMBE Server on Debian.
js3cop@...
Thank you Eric,
I used it on raspberry pi. So I think I can use on debian machine. I will try editing the code of config file.(may be 460800 is right.) Thank you
|
|
|
|
How To install AMBESERVER on Raspbian or Debian.
This will put AMBESERVER on your Raspberry Pi running Raspbian or Debian box running Stretch or Jesse. THIS IS NOT FOR COMPASS LINUX. I am running this with ThumbDV in my Debian Box and also with my DVstick30 in my Raspberry Pi. I am able to use my Android Phone running BlueDV Ambe from the Play store, or my Laptop with BlueDV and connect to my machines from any part of the planet. My ThumbDV and DVstick30 are located over 10,000Km apart, and I can work D-Star or DMR stations. on my Android phone sitting at Starbucks, or an Airport, or on an Aircraft with WiFi. Enough said let's start. I love Kali Linux, so will do all as root. ssh into your machine, at the prompt run sudo bash hit the enter key, you will now be root user. nano /etc/ssh/sshd.config scroll to the line that says PORT 22 change 22 to any number you like. {I WARN YOU TO REMEMBER THIS NUMBER YOU ENTERED} Next scroll a little bit more to where you see. # Authentication # PermitRootLogin blah blah. On that line remove the hash tag # and blah blah, then put the word yes Ctrl + X and then Y on your keyboard. at the prompt run: passwd enter any password you want, you will see nothing as you typed in the password, hit enter, type the same password again enter now you have full root access into your machine. type reboot. After the machine is rebooted ssh back in with your new ssh port number and login as root with the root password you created. Now run: apt-get update apt-get install git curl wget after these are installed, run: git clone git://github.com/marrold/AMBEServer.git cd AMBEServer make make install At this point Ambeserver is installed on your machine. To be able to find your machine online, so before we start you will need to setup an account at one of these example: dyndns.org or noip.com, the list is endless, so your choice. After you make the account, create a hostname for your Raspberry Pi or Debian box on this website. Next back to your machine run: apt-get install ddclient During the installation you will be asked to enter your login name and password to your dns host account, you setup above, and choose what name you want to assign this machine from your account, once done, accept all the default prompts during the installation. after you returned at the prompt run: nano /etc/ddclient.conf after the last line of text type in this: Daemon=300 SSL=yes Next on your keyboard hit Ctrl + X key together then Y key, you will be back at the prompt. Home Router setup: That your Pi or Debian box is connected too. If your Machines are connected to the second or third router in your house, it will be a bit tricky to get to your machine, not impossible, but very involved, so best put these machines on your first Router after your ISP Fibe optic or cable box or directly on your ISP router. Basically you want your machines getting an IP from the first router into your home. Login into this router and set your Raspberry Pi or Debian box to get a fix IP, base on their Mac address. This is done in order for the router to always assigned the same IP whenever it reboots to your machine. Now find the port forwarding section in your router and open the ssh port number you assigned above using TCP to your machine IP address; also port 2460 use UDP. save and apply these changes into your router. Now to get the AMBEserver to start automatically anytime your machine reboot do the following: Save the script I attached somewhere on your desktop. The easiest way: Download and install WinSCP Now with WinSCP login your Machine with the assign IP your set in the router and ssh port as root & root password. you assigned above. on the right pane navigate to this directory. lib/systemd/system from the left pane navigate where you save my script and dragged it in that system directory. now close WinSCP. back at the machine run cd /etc/lib/systemd/system chmod 644 ambeserver@... systemctl daemon-reload systemctl enable ambeserver@... Now put your ThumbDV or DVstick30 into your Machine. run reboot. When your machine is back up, ssh back in and run systemctl status ambeserver@... You want to see ACTIVE in GREEN. Means your server is running and you are set to use your ThumbDV or DVstick30 with BlueDV Ambe on android or BlueDV on you PC. In the setup in BlueDV Ambe or BlueDV on PC or MAC if home use the Ip address of your machine baudrate 460800 and port 2460, when out of the home or on data on your phone use the hostname you assigned your machine at dyndns or noip.com. I hope this helps all to get going please post your comments, and let me know if you get it going. ps: The ambeserver @ ttyUSB0.service is not showing properly in the post it is all one no space as I type here on this line; but look at the name of my script that is how it should be written.
|
|
|
|
Re: I want to run BlueDV AMBE Server on Debian.
Eric Jarvi
I'm totally new to group and not familiar with this code or dvstick but maybe you have the wrong baud rate? I saw a similar grinding of the gears at first when using a ThumbDV with BlueDV for windows at the wrong internal baud rate. The default rate might be defined in the c code you compiled or in some parameter or settings file the a.out executable would accept? If so try editing the code or config file or parameter and using 460800 instead of 230400 for baud rate.
On Mon, Sep 17, 2018, 2:18 AM <js3cop@...> wrote: Hallo John,
|
|
|
|
Re: TOTALLY CONFUSED...
Gwen,
|
|
|
|
Re: XLX003 Reflector; Anna
Dick Herrick
Anna,
toggle quoted messageShow quoted text
I’m your tester for the XLX issue. Here’s what’s NOT happening. I can call someone using a Wintel (we were on the phone for testing purposes). He could hear me normally. When he responded from his Wintel, I heard nothing. Same thing with another Mac user who called me. So, it looks like you’re half-way there. I think you mentioned that you tested and didn’t get any responses. This may be the reason.
|
|
|
|
Re: sudo apt-get install ambeserver
I have updated instructions at https://nw-digital-radio.groups.io/g/ambe/wiki/AMBEserver-Addendum#Quick-Build-on-Linux The 'roll your own' (e.g. non-Compass Linux) approach, assumed familiarity with the target sufficient to fill in the 'blanks'. Like most Linux/Unix command line programs, placing the help flag will expose flags, e.g. AMBEserver -h The 3 parameters that may need adjusted are the device, e.g. /dev/ttyUSB0, the speed, e.g. 460800, and the UDP port it will listen on, e.g. 2640. The instructions are still sparse, but the components are now downloadable to fill in the blanks.
On Mon, Sep 17, 2018 at 2:01 PM Kenny Richards <kenny@...> wrote: I am pretty sure the ThumbDV I am using is of the second generation, so it doesn't need to be forced to the 460800 baud rate. I had forgot about that requirement for some people, but as you said, it can also be done from the command line. --
John D. Hays Edmonds, WA K7VE
|
|
|
|
Re: TOTALLY CONFUSED...
Kenny,
Thank you! I pulled a clone of that repository, did a make, then make install, and now I have it working both from my Win7 pc on BlueDV AND from my Android phone on BlueDV. It's still an experiment, but I have it actually functioning, so that's the important part. The instructions prior to this are piecemeal, confusing, and as you've shown, full of obfuscations and incorrect information. THIS worked. NOTHING on the Wiki worked at all. That wiki page needs to be edited to remove all the deprecated information.
|
|
|
