Re: ThumbDV and AMBEserver : Couldn't find start byte in serial data -> SOLVED


Great that you solved it. If you are using Raspbian Jesse or Compass Linux using systemd is recommended over init.d

On Dec 28, 2016 07:25, "Santu OTTAVI" <t.ottavi@...> wrote:

Le 27/12/2016 à 23:00, John D Hays - K7VE a écrit :
Are you sure the ThumbDV is at /dev/ttyUSB0 ? (ls /dev/ttyUSB?)

Yes, it's on /dev/ttyUSB0. Here's what "dmesg" says :
  FTDI USB Serial Device converter now attached to ttyUSB0

Have you tried the python test scripts?

Yes. Using it on /dev/ttyUSB0, speed 460800, of course with ThumbDV connected :
Wrote: 5 bytes
Set DSTAR Mode
Wrote: 17 bytes
a -------------------------------------

If you have a Windows box handy, you can also test using ThumbTest.exe from

Done :
Enter COM port value (Default: COM1): COM20
Baud Rate(default:9600): 460800
a ☺ 9
a ♂ 0AMBE3000R
a 1 1V120.E100.XXXX.C106.G514.R009.B0010411.C0020208

If it is a newly purchased ThumbDV the baud rate is 460800
Brand new, ordered last month.

After re-checking all, reinstalling init.d script, and rebooting, it works !!!

I think the reason of the failure was I had an init.d startup script with the default speed (230400). This may have sent scrambled data to the serial port during boot, causing odd behavior later (even with the right speed settings).

For people who may encounter the same problem later, my init.d startup script contains the following line :
  /usr/bin/AMBEserver -d -i /dev/ttyUSB0 -s 460800

73 de TK1BI

Join to automatically receive all group messages.