I turned off the routing.? I will also install your new version.??

"hree different devices logged into openquad.net"? -? I try to always unlink from a reflector / talkgroup when I end a QSO to avoid two instances.? ?I just looked through the various tabs on openquad.net and do not see any links to N9KO at this time.? Hopefully you were seeing some historical info about my three devices.??

Thanks for your help.?

开云体育

This is curious. That error message means it made 326 attempts to read the "magic start byte" of a DV3000 packet. 326 is the maximum size of any packet that the DV3000 might send (all the other packet that might be sent are significantly smaller). The start byte (0x61) is suppose to be at the beginning of EVERY packet received from the DV3000 chip and it's how an out-of-sync chip might be brought back into sync.

I have pushed up a new version that now make 328 attempts and then reports a little more details about trying to find the start byte. It might be helpful to me in understanding what the problem is.

Cal, on another matter:

When you're using qdv, if you are linking, you should probably shut off routing, unless you are expecting an incoming Callsign Route. You're wasting a lot of bandwidth you aren't using. When the qdv routing gateway opens, you receive A LOT of data when it first logs into rr.openquad.net and then you get additional data each time anyone on the network keys up. With ~5500 users on the network at most any time, that's a lot of data and when you're linking, you're not using any of it!

Also I noticed that you can have up to three different devices logged into openquad.net, all with the same call, N9KO, and all with the same IP. This is not a good idea. Routing won't work well. You should only have one station logged into QuadNet from an IP address, and even if you have multiple stations logged into QuadNet from different IPs, each station should still have a unique callsign. I see that at least one of your stations is a PiStar device. You can turn off ircDDBGateway (I think you just have to leave the "rr.openquad.net" blank). Your other station is showing as a regular ircDDBGateway, so you can do the same for it.

QDV hung up, but there were no Beeps ythis time.

~/bin/qdv

Initialized AMBE3000R version V120.E100.XXXX.C106.G514.R009.B0

#Gateways: /home/calvin/etc/gwys.txt=2135

read 62 indicies from /home/calvin/etc/announce/index.dat

xrf=20, dcs=21, ref=22, AudioUnit=23, MAX+1=24

starting CIRCDDB

Successfully connected to rr.openquad.net at [104.131.81.32]:9007

IRCDDBApp::setBestServer s-grp1s2

IRCDDBApp::setCurrentNick n9ko-4

IRCDDBApp: state=2 choose new 's-'-user

IRCDDBApp: state=3 tableID=1

IRCDDBApp: state=3 tableID=0

sending File:/home/calvin/etc/announce/connected2network.dat mod:A RADIO_ID=WELCOME_TO_QUADNET

?

IRCDDBApp: state=6 initialization completed

Pushed the Link button for XRF757 A.

Link request to XRF757? ?to module A

Connected from: [XRF757? ] A

sending File:/home/calvin/etc/announce/linked.dat mod:A RADIO_ID=LINKED_XRF757_A

?

CDV3000U: Couldn't find start byte in serial data

Terminated

-- 
___________________________
73
n7tae (at) tearly (dot) net

Will do right now

开云体育

Sorry, not enough to go on. Were there any interesting messages in the terminal you start qdv from? Next time, please open a new window and type "killall qdv" and then send me what's in the terminal window where qdv was launched.

I was listening to the start of the Qnet Array pre-net just now.? I had a short QSO with someone and then was just listening for the net to start when I started hearing short beeps coming for the laptop.? I tried to mouse-click on the unlink tab and nothing happened.? I had to close it down by closing down the terminal box.? Is there a timer that needs to be adjusted to prevent this from happening again.?

Cal
N9KO?

-- 
___________________________
73
n7tae (at) tearly (dot) net

There beeping started at about 10 minutes of no TX from me.? There was activity that I was listening to on XRF757 A.

I was listening to the start of the Qnet Array pre-net just now.? I had a short QSO with someone and then was just listening for the net to start when I started hearing short beeps coming for the laptop.? I tried to mouse-click on the unlink tab and nothing happened.? I had to close it down by closing down the terminal box.? Is there a timer that needs to be adjusted to prevent this from happening again.?

Cal
N9KO?

Thanks Cal, I pushed up a new version (200510) with a shorter window. Users can make it bigger by dragging a corner. Hopefully this will fit on your smaller screen.

Looks like it worked.? I ran it on an Acer notebook (9 inch screen) running Ubuntu MATE 18.04.? The QDV screen is a little too tall for the 9 inch screen as I can only as I cannot see below the Echo Test and QuickKey boxes.? I tried to decrease the height of the QDV screen, but could only move it up and down.? Is there a way I can decrease the height of the QDV screen?

Tnx
Cal
N9KO

Do in this order (from your build directory):
make uninstall
make clean
git pull
sudo apt install libsqlite3-dev
make
make install

and then a "sudo make installdash" if you want to use the web-based dashboard.

What files related to the prior installation are no longer needed and should be deleted?

I've uploaded a new release (200508) today with many changes:

• Since the very beginning IRC clients have maintained both an "inner" and "outer" Follow-Me cache for routing. The inner cache was maintained the IRCDDB thread and the outer cache was maintained by the gateway. This is redundant and very inefficient. DigitalVoice, qdv, now uses a single cache to manage Follow-Me data.
• The location of the configuration directory has been moved from $(HOME)/.config/qdv to $(HOME)/etc. After doing a "make install" the binary will be installed in $(HOME)/bin. If this directory is not in your search path, you can start it from your home directory by typing "bin/qdv" or from any directory by typing "~/bin/qdv". You can add $(HOME)/bin to your search path by modifying you $(HOME)/.bashrc file. Look for the "export PATH" line.
• Incoming audio quality has been significantly improved by applying the same "healing" technology I developed for QnetGateway. This will repair many situations with incoming voice streams where packets are lost or arrive out of order.
• It is now possible to maintain a link while you are routing. I don't recommend this, but it is possible. If you just enable linking, URCall will be fixed on "CQCQCQ". If you enable both linking and routing, be sure URCall is properly set before keying up! Use "CQCQCQ" to send your voice-stream to the linked reflector. Anything else will be sent on a route.
• A web-based dashboard is now included. This is very similar to the dashboard I've already developed for QnetGateway. It uses the php mini-server. This web server is not suitable for the world-wide-web an should only be used on a local network. To install it, type "sudo make installdash", then surf to "http://localhost", or "http://<hostname>.local (where <hostname> is the name of the system qdv is running on), or "http://127.0.0.1" using a browser on the system that qdv and the mini-server is running on.
• Finally, there is an About dialog box. You may need to click the "X" twice to make it go away.

Tom N7TAE

I too have been waiting for this Codec2 thing to put something in my hands for VHF UHF. It seems their focus has been mostly for HF. I was hoping by now to at least see some code I could run on a Raspberry PI and interface to the packet radio port of my analog radio.

The M17 project is also interesting, but I feel it will be pretty much the same problem, getting commercial vendors to adopt it.

So in my opinion, the best option is APCO25. Its been out of patent for 8 or so years, and there are multiple manufactures of the radios, as well as used radios floating around.

As for anonymous authors, its easy to see that DSD (the oldest project) is maintained by Jared Szechy, K8JSS

The more recent rewrite is via a French ham:


With the other two projects that I mentioned before their contact info is easily obtainable for anyone who wants to reach out and help with the projects.

And the non ham project, the GEO mobile radio project, also has the coders names in the git rep:


No one is hiding, there has always been exceptions for non-commercial/research usage of patented technology. By our very definition, ham radio has always existed based on that very premise.
There has been a lot of mis-information over the years, ironically by some of the folks that sell AMBE thumb dongles.

This is very different than taking something that isn't your and selling it for profit like the Team6160 AMBE guys, or the more recent Hytera news.

Steve,

I appreciate what you are trying to do, but you could have provided a link to . There is a lot of good stuff there.

For me, I'm not that interested in fooling around with software solutions to Icom and Motorola/Yaesu vocoders. If this was truly on the up-and-up, how come many of the github repositories dealing with D-Star vocoder are published by anonymous-type users? Bruce Perens is rich, he can afford a lawyer. I'm not.

I'm waiting for an affordable, high quality Codec2-based HT and mobile radio, then I think I'll probably sell all my big vendor hardware at the next hamfest and be very happy to move to a 100% open-source world, even if it never becomes as popular as what we have now.

That's why I'm keeping my eye on the . Do you know of other projects that are as far along as they are?

Tom N7TAE

It would likely just be better to create a multi-channel software vocoder for D-Star, this chip business is silly.

A lot of folks use the MD380 emulator (which is the handy work of Travis, KK4VCZ's md380 reverse engineering project) to get around the hardware requirements of most systems that with otherwise require with dongles or boards.

Its also the preference for a virtual environment where you don't have physical access to the servers. Russell, KV4S did a good job documenting this with his blog entry titled "Hosting an AllStar Node and an AllStarDMR bridge in the cloud"

Sadly that emulator doesn't support D-Star even though that is the mode completely out of patent.



If someone is up to coding a solution for D-Star, these projects might be good to look at as some of the basics are in these projects:

Sorry for taking so long to approve your message! I was out for most of the end of Dec.

Your message look normal. When you click the settings button, it automatically re-initializes the ThumbDV, so you'll see the second "Initialized" line. Settings starts a Dialog which normally freezes the main window until an okay or cancel is clicked in the Settings Dialog.

Are you sure the settings dialog isn't hidden by the main window?

First off, thank you very much for all your hard work.?

I recently install qdv on a clean Buster image on a Raspberry Pi 4.? I followed your instructions as listed in git to the letter (hence the clean image as I didn't want pulseaudio messing with my settings in various things running on other images).? Everything installed and built correctly according to the terminal output.

When I run 'bin/qdv,' the gui starts and I get this terminal output:

-----------------------------
pi@raspberrypi:~ $ bin/qdv
read 62 indicies from /home/pi/.config/qdv/announce/index.dat
Host map contains:
??? 622 XLX_Hosts.txt
??? 506 DExtraHosts.txt
??? 456 DCS_Hosts.txt
??? 474 DPlus_Hosts.txt
??? 0 MyHosts.txt
Initialized AMBE3000R version V120.E100.XXXX.C106.G514
---------------------------------

If I click on 'Settings' the button in the gui goes grey, and nothing else happens at all.? The gui is completely frozen.? To stop the program, I have to go back to terminal and issue ctrl+c. The full output in the terminal changes to this:
---------------------------------
pi@raspberrypi:~ $ bin/qdv
read 62 indicies from /home/pi/.config/qdv/announce/index.dat
Host map contains:
??? 622 XLX_Hosts.txt
??? 506 DExtraHosts.txt
??? 456 DCS_Hosts.txt
??? 474 DPlus_Hosts.txt
??? 0 MyHosts.txt
Initialized AMBE3000R version V120.E100.XXXX.C106.G514
Initialized AMBE3000R version V120.E100.XXXX.C106.G514
----------------------------------

Any ideas on what could be happening?

SOLVED? It seems the humming was due to my Logitech H390 USB headset.? I tried my BT/wireless H800 headset.? Could not get the H800 to be recognized by the Audio Device Settings when I was using BT.? Everything worked when I inserted the wireless dongle into the RPi and selected the wireless dongle optin on the headset.? No hum!!!

I followed your instructions for the RPi install.

There are no differences between the default setting and the Logitech setting.

The "sound card selection is working" is related to a different thread for my installation on a laptop running Ubuntu 18..04

Hi Cal,

If you installed pulseaudio on your Pi and selected the default ALSA device as instructed in the README.md file, you should see both a "default" device as well as your specific headset in the new device selection for the audio input and audio output on the Settings Dialog. I'm asking if there is any difference between using "default" setting or the setting for your Logitech headset.

Earlier, you left a message on the "sound card selection is working" thread saying you re-installed and qdv was working great. Did the humming start later?

Tom N7TAE