开云体育

Another new release has been merged into the master branch. This contains the DPlus authorization that I've been talking about the last few posts, and a bug fix for DPRS.

Based on some information from the field (thanks Carty!), QnetGateway will attempt to connect to auth.dstargateway.org three times before it gives up. You can always update your gateway list by sending an "?????? F" to QnetGateway. This command will clear you current gateways list, and then reauthorize DPlus (if enabled) and reread your gwys.txt file.

Sometimes, I'm my own worst enemy. I have been working on many internal changes to make the code more understandable and supportable. During this process, I accidentally introduced a bug in APRS causing most updates to the aprs.net website to fail. This has been fixed and if you have aprs enabled in QnetGateway (it's on by default) and you've enable the GPS in your radio, you should see your position frequently updated in the aprs.fi website. (Thanks Colby!).

Of course this release contains the two new voice prompts. When you are first connected to rr.openquad.net, you system will tell you with a "connected to QuadNet" message. Also, if you try and route to a target for which QnetGateway doesn't yet have an IP address, then you will receive a "not in cache, please try again" message. By the time you receive this voice message, QnetGateway will have ask QuadNet how to route your traffic, and you should be good to go on the next key-up.

I just pushed up another version that contains some additional tweaks to QnetLink for DPlus authorization. Thanks to Carty, we found out that using systemd to wait on the network is not enough, so I've added some code that will wait as long as necessary to make the connection. In Carty's case, it looks like his wifi RasPi was taking about 15 seconds to get fully connected after systemd said the network was ready!

In a related development, I've added another voice message in this release: If you try to link to a reflector or repeater that is not in the QnetLink gateways list, you'll get a voice message. If you were trying to link to a DPlus reflector/repeater and got this messge, it probably means that your target wasn't downloaded during the authorization. If you were trying to link to a non-DPlus system, the callsign wasn't defined in your gwys.txt file.

Sorry about this if you've been trying to keep up with the releases, but I pushed up another release this morning! With this new release, when you link or if you try to link and your already linked, QnetLink will enunciate the link with a voice message, like "the module is linked to X R F seven five seven alpha", or "the module is already linked to X R F seven five seven charlie".

This release is for you "linkers", but I hope you will give routing a try. Most hams who try it, like it!

In case you are wondering, I use fromtexttospeech.com to generate original voice files in mp3 format. Then I use mpg123 to convert the mp3 file to a wav file. Then I use my own custom "OOT" module for gnuradio-companion and it uses a Northwest Digital ThumbDV to convert the wav file to AMBE data. It's a simple 3-step process that takes a few minutes to generate a new AMBE file.

I pushed up another new release today. This fixes several problems with APRS (position tracking), the most important was that your position was only occasionally being updated. If you don't disable APRS in QnetGateway (it's enabled by default), and you enable GPS on your radio, you position can be tracked at sites like aprs.fi. With an Icom radio, if you use D-PRS mode (found under the "GPS TX Mode" in the GPS menu), you can set the position icon that is displayed on the website using the menu system on your radio. If you use a Kenwood radio or if you use NMEA GPS on an Icom radio, you position will be tracked with a blue dot.

If you specify your hot-spot/repeater location, along with a description, in the "module" section of the config file, your module(s) will also be shown as a black "D" diamond. Obviously, since this hot-spot position is hard-coded in your config file, you don't want to specify it for a hot-spot whose location is variable, like a mobile rig. Even if you don't track the hot-spot, QnetGateway can still pass user positions to the aprs network.