The error about "Radio identification failed" rises when Chirp has managed to talk with the radio (hence the cable is ok) but Chirp is unable to effectively identify the radio model.

I'm very interested on the debug.log file from chirp after one of this errors (Search the chirp wiki to know where you can find this file.)

90% of the time this error means that we have a unknown radio variant on the wild, the solution is to make a serial capture of the download/upload  process for me to analyze and include it on the current Chirp version.

Here you can find how to doit: how to portmon.doc past emails on the wiki has useful intel about tricks to run in if you have 64 bit only systems..

73.


El 09/05/16 a las 15:06, Paul Mann via chirp_users escribió:
I get the same message with my 8900.


On Monday, May 9, 2016 2:50 PM, F.Ketterman <f.ketterman@mail.com> wrote:


I have not been able to successfully read from my QYT KT-8900 radio I consistently receive the following message ‘An error has occurred’ ‘Radio identification failed.’  Note that this is with two different cables (one supplied with radio requiring older Prolific driver, and the other a brand new BTECH cable that I used without error to program my BTECH UV-2501+220).  I am using the latest version of CHIRP (daily-20160507) build on a Windows 10 x64 system.
 
Frank Ketterman
AC0XV
Molon Labe!
 

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Paul Mann at pauledmann@yahoo.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com



_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to M.Sc. Pavel Milanes Costa at pavelmc@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com