[chirp_users] Unable to read from QYT KT-8900
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
f.ketterman@mail.com mailto:fnk@softhome.net
www.survivalblog.net http://www.survivalblog.net
AC0XV
Molon Labe!
I get the same message with my 8900.
On Monday, May 9, 2016 2:50 PM, F.Ketterman f.ketterman@mail.com wrote:
<!--#yiv7793515554 _filtered #yiv7793515554 {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv7793515554 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv7793515554 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv7793515554 #yiv7793515554 p.yiv7793515554MsoNormal, #yiv7793515554 li.yiv7793515554MsoNormal, #yiv7793515554 div.yiv7793515554MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", sans-serif;}#yiv7793515554 a:link, #yiv7793515554 span.yiv7793515554MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv7793515554 a:visited, #yiv7793515554 span.yiv7793515554MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv7793515554 span.yiv7793515554EmailStyle17 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv7793515554 .yiv7793515554MsoChpDefault {font-family:"Calibri", sans-serif;} _filtered #yiv7793515554 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv7793515554 div.yiv7793515554WordSection1 {}-->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 Kettermanf.ketterman@mail.comwww.survivalblog.netAC0XVMolon 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
Make sure that the Device Manager shows that the port is working properly. It also shows which port to use. Download the latest CHIRP software. My KT8900 is now working properly with CHIRP. CHIRP daily-20160507 is what I am using.
On Mon, May 9, 2016 at 1:06 PM, Paul Mann via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
I am not familiar with that radio but learned that my F8HP needs to be in Frequency mode vs Channel mode. Might be worth a look? On May 9, 2016 8:35 PM, "Larry Lovell" larry.lovell76@gmail.com wrote:
I had the same issue with my QYT KT-8900. I used the Sainsonic 890 radio setting and everything uploaded with no problem.
Get Outlook for Android
On Mon, May 9, 2016 at 7:35 PM -0700, "Ted" tedfs3@gmail.com wrote:
I am not familiar with that radio but learned that my F8HP needs to be in Frequency mode vs Channel mode. Might be worth a look? On May 9, 2016 8:35 PM, "Larry Lovell" larry.lovell76@gmail.com wrote:
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to John Wolven at azrokitman@live.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
There is an experimental driver that was just provided in the KT8900 Yahoo Group. It works for my radio where it wasn't working before.
The testing of the dev driver is going very well, it will worth a try, I will include it on the daily Chirp in the following days.
http://chirp.danplanet.com/issues/3539#note-12
Also I'm testing internally a new ALIAS feature recently implemented by Dan for managing the clones in a more user friendly manner.
73 CO7WT Pavel.
El 09/05/16 a las 23:57, Trevor Holyoak escribió:
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 http://chirp.danplanet.com/attachments/2257/how%20to%20portmon.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ó:
participants (7)
-
azrokitman＠live.com -
F.Ketterman -
Larry Lovell -
Paul Mann -
Pavel Milanes (CO7WT) -
Ted -
Trevor Holyoak