If there is a free and easy to use tool that I could use to capture that info while using the OEM software, I’d be glad to do so.
> On Mar 18, 2021, at 11:51 AM, Jim Unroe <[email protected]> wrote: > > On Thu, Mar 18, 2021 at 10:08 AM Mike Allred <[email protected]> wrote: >> >> OK... >> >> Last night I got the OEM Kenwood programming software running using DOSBOX >> and it worked great with both radios (I have 2). Of course, I would still >> like to get Chirp working. But, this proves that the programming cable and >> radios are working correctly. >> >> I have attached 2 additional debug logs. One using the TK-760G profile in >> Chirp and one using the TK-762 profile. >> >> The 760G profile seemed to do even less than the 760 profile as it didn't >> even put the radio in programming mode. >> >> The 762 profile appears to have behaved exactly as the 760 profile did - >> radio goes into programming mode but Chirp errors out. >> >> >> Mike > > Unfortunately, neither debug.log file has captured any response from > the radio. It is probably going to take capturing the serial port > communications during the cloning process. > > Jim > _______________________________________________ > chirp_users mailing list > [email protected] > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to Mike at [email protected] > To unsubscribe, send an email to > [email protected] _______________________________________________ chirp_users mailing list [email protected] http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to [email protected] at [email protected] To unsubscribe, send an email to [email protected]
