Bug #5469

TH-9000 220 - Radio did not accept block at 0100

Added by Tony Scandurra over 2 years ago. Updated 15 days ago.

Status:Feedback Start date:12/30/2017
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:TYT TH-9000 (220 MHz)

Description

When using CHIRP to upload frequency data to my TH-9000 220 radio, I receive the error "Radio did not accept block at 0100".

I am able to upload data using the TYT TH-9000 software.

My TH-9000 144 and 440 rigs work fine with CHIRP.

Debug log is attached.

I have done searches both on the CHIRP website and with Google to see if anyone else has reported this issue, but I could find none.

debug.log (30.9 kB) Tony Scandurra, 12/30/2017 08:47 am

History

Updated by Gary Hughes over 2 years ago

Tony Scandurra wrote:

When using CHIRP to upload frequency data to my TH-9000 220 radio, I receive the error "Radio did not accept block at 0100".

I am able to upload data using the TYT TH-9000 software.

My TH-9000 144 and 440 rigs work fine with CHIRP.

Debug log is attached.

I have done searches both on the CHIRP website and with Google to see if anyone else has reported this issue, but I could find none.

I have the same problem. I can read from radio, but not write to it.

Updated by Bernhard Hailer 5 months ago

  • Status changed from New to Feedback
  • Model affected changed from TH-9000 220 to TYT TH-9000 (220 MHz)

This looks like a cable issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
RTSystemsCablesAndMavericks (if you're running MacOS)
If there's no solution to be found in any of them, please read: How To Report Issues and provide a fresh debug log. Thank you!
If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php

Updated by Bernhard Hailer 15 days ago

  • Target version set to chirp-daily

Based on the original description, there might be an issue with the reported ID from that radio. Leaving this bug report open.

Also available in: Atom PDF

prevent spam