Bug #11850
openCannot connect to Yaesu FT-8900
0%
Description
I have latest Chirp Next 20250221 on Windows 10 and Yaesu FT-8900 and good old serial cable that I used numerous times with old Chirp.
But now, I only get error "index out of range"
Serial adapter is Prolific, i have right driver, version 3.2.0.0 and the same serial interface cable works fine with other radios (I have several adapters for different radios), meaning driver is working fine.
I tried Chirp Legacy. it does not work too but gives error: "ord() expected a character, but string of length 0 found"
Files
Updated by Predrag Supurovic 4 months ago
- File config.txt config.txt added
- File win_system_info.txt win_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250221]
Updated by David Strickland 21 days ago
I had the same issue with my FT-8900R but when I changed the baud rate to 1200, it started to work.
I did notice in the log, 9600 baud is being used.
73
David Strickland de KR8X
Updated by Dan Smith 21 days ago
David's suggestion about changing the baud rate is incorrect, please see FAQ_Adjusting_The_Serial_Port_Settings_In_Windows.
Predrag, it looks like CHIRP is getting invalid data from your radio. My guess would be a bad cable or bad connection resulting in just noise being received by CHIRP. Also could be a failure to follow the directions for initiating cloning mode (either too early or not at all). Yaesu radios unfortunately require a complex dance to initiate cloning at the exact right time, and it's easy to mess up.