If you speak with the CERT team member, appreciate if you can ask what version of Chirp he validated works with the T70A, type of cable used, cable chipset if known and where the cable was purchased? That would be very helpful. I ordered a FTDI cable from a different vendor and will see if that helps.
Thanks again Nick KB1GZN
On May 26, 2015, at 7:24 PM, JD Morrow ngauge75@verizon.net wrote:
Nick, Our one CERT Team has about 10 of the T70A's, I have programmed them several times over the last few years, with multiple cables, and do not seem to have a problem with Chirp. The vast majority of problems I have run into have either been cable related or just a boneheaded step on my part (ie: fat fingered the data). I do not own a T70 or have one readily available so can not help with the protocol.
73's John KC2TXV
-----Original Message----- From: Nicholas Papadonis Sent: Tuesday, May 26, 2015 6:09 PM To: Discussion of CHIRP Subject: [chirp_users] IC-T70A not communicating with Chirp
Folks,
I’m having a similar issue as below and filed the following bug:
http://chirp.danplanet.com/issues/2605
I have tested both Genuine FTDI and Prolific USB->Serial cables with no success. The USB->Serial chips are detected by both Windows 7 and Mac OS, however when Chirp sends out the 0xE0 detection frame, there is always a 0 byte response back when I would have suspected at least a byte for the Model ID according to the code. I have tested Chirp all the way back to v1.1 when the code log says T70A support was first added. My assumption is that it must have worked back then, however this is not confirmed yet. It’s odd that both cables resulted in 0 byte reads and now I’m suspecting either the T70A has a different protocol or newer manufactured firmware that changed the control codes.
Has anyone validated the IC-T70A *ever* worked with Chirp? If so, can you share your experience and possibly the serial number and purchase date of the radio?
Thanks, Nick KB1GZN
Thank you very much David, After trying many other things... I ran the cable loop back tester software, and set to COM3. Ran the test and nothing happens. I have tried this with the radio just turned on. I have tried this with hreadio in the CLONE mode. I have tried this with the radio in the CLONE OUT mode. I never get any response. I think perhaps I have a bad cable - sigh! One other clue is that the cable makes the radio SCAN whenevr I plug it in normally I have to fiddle with it and reinsert it numerous times before it will stop scanning and sit at a fixed frequency. The supplier assures me these are not the fake chips but genuine FTDI chips he is using, and charged a premium price for it. The cable came from Mark Dunkle, KJ6ZWL. I will relay all of this information and see if he can send me another cable that works. Manufacturer: FTDI on USB Serial Converter Driver Provided: FTDI 8/26/2014 Driver Version: 2.12.0.0 Brian Carling
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users 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 To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com