The ThumbDV™ uses FTDI chips. On Linux and MacOS typically no driver install is required. On Windows, the driver should be installed by the OS, but if it can't be located, then use this information -

I just tested on a USB 3.0 port here and works just fine. Have not heard of any general issues with USB 3.0 Sometimes a particular computer has an issue, a powered USB hub sometimes helps.

Does it appear as a COM port when you plug it in? If it is very old, you may need to switch to 230400 baud. (Turn serial off, goto Menu -> Setup then under AMBE block). There is a test exe in the file

We have noted some folks having crash issues with BlueDV for Windows. This is generally not a ThumbDV™ issue. Be sure you have the latest install and follow the note at https://www.pa7lim.nl/bluedv-wi

#bluedv

Hi Greg, This is basic networking. If the server and client are on the same host use 127.0.0.x, if on the same LAN (even if across a VPN) use the LAN interface address, eg. 192.168.1.x. If running ove

#thumbdv

Make sure the FTDI driver is on the HP laptop.

Ryan, It's pretty rare to have either a ThumbDV™ or PiDV™ fail. Have you run the test program (in files, the .exe for Windows or the Python program on Linux) and what were the results? What program ar

I cannot answer for that specific product, since it is not a NW Digital Radio product like the ThumbDV™ However a couple of data points: The AMBEserver (generic) software is port and IP address agnost

Have you run the ThumbTest.exe from https://nw-digital-radio.groups.io/g/ambe/files ??? The ThumbDV™ appears to the operating system and applications as a simple serial device. There is no user firmwa

You could also run a VPN between your XLXD host and AMBED host. (Isolating the AMBED from the public Internet and then it could also be at a dynamic public IP).

#thumbdv

N7TAE has done some great work.

#thumbdv

DMR and Fusion HR use the same AMBE vocoder mode, so the reflector only needs to handle the digital wrappers and network transit.

#thumbdv

If you are using the Windows version of AMBEserver, contact info@...

Hi Sven, The dv33 is not a product of NW Digital Radio, so please contact the manufacturer for support. The invocation of ambeserver@ThumbDV is exclusive to the ThumbDV™ you must discover what port yo

That would be an excellent solution, should you decide to do so.

#ambe #ambeserver #thumbdv

Don, Please review http://nwdigitalradio.com/thumbdv-model-a/ Changing the baud rate is not trivial. Is there a particular reason you wish to change it?

#ambe #ambeserver #thumbdv

I don't recommend running daemons as root, but you could edit /etc/systemd/system/ambeserver@.service [Unit] Description=AMBEserver Daemon After=network.target serial-getty@%i.service dev-%i.device Co

There are some automatic aliases. Try serial0 and serial1 and see if that helps. See: https://spellfoundry.com/2016/05/29/configuring-gpio-serial-port-raspbian-jessie-including-pi-3-4/#Raspberry_Pi_3_

David, There are two commands you should become familiar with chown (to change ownership of a file or directory) and chmod (to change permissions for the owner, group, and world of a file or directory

Try changing the ownership of /dev/ttyS0 -- your listing did not show it belonging to the dialout group.