Bug #7863
openFailed to communicate with radio: Radio did not ack block 0 [FT-818 w/ Bluetooth]
0%
Description
A known (yet unsolved) issue is ruining my day. My brand new (tx opened) Yaesu FT-818ND got a perfectly functioning Bluetooth CAT adapter, which can seamlessly run HRD, unfortunately CHIRP can read from radio but cannot write into it. The software reports "Radio did not ack block 0" just a few seconds after pressing C (Rx) button on the radio panel.
Files
Related issues
Updated by Bernhard Hailer almost 4 years ago
- Status changed from New to Feedback
- Assignee deleted (
Dan Smith) - Priority changed from High to Normal
- Model affected changed from (All models) to Yaesu FT-818ND
Indeed, your radio doesn't hear Chirp for some reason.
Does HRD write to the radio, can you switch bands etc.?
I've heard of issues with Bluetooth adapters before - any chance you could try a cable connection with the radio?
Updated by Daniele IW9HOJ almost 4 years ago
Bernhard Hailer wrote:
Indeed, your radio doesn't hear Chirp for some reason.
Does HRD write to the radio, can you switch bands etc.?
I've heard of issues with Bluetooth adapters before - any chance you could try a cable connection with the radio?
From HRD I can do everything, no issues at all. I've tried the adaptor on both my PC's with the very same result. The driver seems nicely working. I also tried to vary the Rx button pressure timing, as stated in #2933, but got no success. Eventually I just ordered an FTDI chip cable, then I'll be able to try it.
Updated by Bernhard Hailer almost 4 years ago
Thanks Daniele. #2933 offers important clues, hopefully that helps to bash the Bluetooth bug. Looking forward to your report with the cable.
Updated by Daniele IW9HOJ almost 4 years ago
The FTDI cable has arrived, I installed its genuine driver from https://www.ftdichip.com/Drivers/VCP.htm and it worked as expected, no issues at all with Chirp. Please find the debug file alleged to this message.
Updated by Bernhard Hailer almost 4 years ago
Ok, then we will leave this report (and also #2933) open until one of the developers has a chance to look into the Buetooth timing issue. Thanks for your feedback!