Bug #7773



Added by Barry Smith over 3 years ago. Updated over 3 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Chirp Version:
Model affected:
Yaesu FT-1900
Debug Log:
I read the instructions above:



I find your reply belittling:-

You assume I did not do this and that you recommending that I go to another suppier is astounding!

Your response:-
"I had this issue a few times, best thing I can say is the cable driver needs refreshed. try unplugging cable then uninstall / reinstall the driver for the cable.
Also watch your timming while accessing the commands for the radio>computer. You have to hit the V/M after selecting to continue however you have to hit LOW first than to write.
If these two dont work than I would suggest reinstalling Chirp or getting the software from the G4HFQ Site. 73."

My response:-

Your not interested in an old radio problem.

The issue is NOT my cable or drivers or My PC ot my OS. The issue is with your software!

My program will read the ack(hex 06) and TX the memory dump!

I can supply the memory offset(Flags, channels)) if required.

I raised this originally probably 2 years ago and the next release did fix it but susequent releses failed!

Don't trest your users as idiots!

Related issues

Related to Bug #7025: Yaesu FT-1900E - Failed to communicate with radio. Failed to read headerNew08/29/2019

Actions #1

Updated by Bernhard Hailer over 3 years ago

  • Status changed from New to Closed
  • Model affected changed from (All models) to Yaesu FT-1900

It is unclear where you're responding to? This ticket will not reach the intended parties.
Please use open tickets to leave comments, do not open new tickets about issues which are already discussed elsewhere.

You can find open tickets by clicking the tab "Issues" and browsing through them. You can presort them or add filters to find what you're looking for. When you found the ticket, you can always comment right there - click "Update". Thanks!

For your specific issue, it might be helpful if you can dig out when you sent your input, and when it started to fail again. Perhaps we can find out what changed at these times.

One more thing: the response you got was from somebody who wanted to help. That's good, Chirp is a community after all. Even if you think that it won't help in your case, it's certainly not anything to be angry about.


Also available in: Atom PDF