Re: [chirp_users] Errors when trying to read from Icom IC-92AD
Today I received a cable for my Kenwood TH-F6A and find it has the same problem as the Icom. These two are the only "live mode" radios I've tried, perhaps my issue is more generally with live mode?
The TH-F6A cable is a USB version, branded Maxton Data. When connecting to the radio most memory channels are red, a few actually show up correctly. This time I tried adding some data to an empty memory that was successfully read. Surprisingly, this does *usually* work. A couple of times the frequency would show up in the radio, but when I added an offset or tone the software seemed to indicate it was sent (green highlight then back to white) but the radio never showed the change. On one entry I made another change (change step size or something) and BOTH changes finally showed up on the radio.
While Chirp was trying to read the memories the console showed many repeats of "Unexpected result returned from radio" and "Not sure what to do with this:" followed by either a '0' or a line of gibberish.
Anyone have thoughts or suggestions to try?
Thanks, Joe
I have recently gotten back to playing with my radios after a few years (too many hobbies!) and was pleased to find Chirp can work with all of them. At this point I've successfully read and reprogrammed several radios but my IC-92AD is not cooperating.
I have the Icom programming cable and have tried reading its memory on Mac, Win and Linux with roughly the same result. Chirp reads data, but with lots of errors. Mac/Linux seem most successful, with just a few memory channels marked in red, Windows fails on almost all. But even the channels that do get read aren't quite right. There may be duplicated channel numbers, one blank the other with a frequency in it. The channel numbers may be out of order. Or some have incorrect data.
A screenshot of one read attempt (this morning): http://www.n5usr.net/images/230615_chirp/92ADLive_230615.png
Note for memories 21-27, that block is actually all FRS frequencies. The ham repeater entries are valid entries but they are NOT in memory locations 21 / 23 / 25 / 27.
I also made a log file for one run (not this morning's, but similar results): http://www.n5usr.net/images/230615_chirp/IC92AD.log
Am I doing something wrong? Perhaps a setting in the radio that needs to be changed? I've looked through the options and nothing strikes me as likely but you never know...
Chirp version is: CHIRP next-20230608 on all three platforms.
Anyone have thoughts or suggestions to try?
Yes: please fill out a bug report with a debug log, per these instructions:
https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
Describing the issues sounds nice, but the meat needed to actually see what is wrong and do something about it is in the debug log. I don't have an F6 so I may or may not be able to help with that. I do have a 92AD, which works for me, but I have to see that debug log as well to have any idea what's going on.
Also, the F6 and the 92AD are not the same cable, at least on the face of it. Are you using an adapter to go from the 92AD multi-pin connector to speaker/mic jacks and then putting those onto the F6 cable? If so, I'm surprised that works at all. I've only ever used the 92AD for programming with the data cable, so that's really all I can reproduce here.
--Dan
On Jun 16, 2023, at 7:10 PM, Dan Smith via chirp_users chirp_users@intrepid.danplanet.com wrote:
Anyone have thoughts or suggestions to try?
Yes: please fill out a bug report with a debug log, per these instructions:
https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
Okay, I thought I read somewhere it was recommended to post here first. Will do that.
Describing the issues sounds nice, but the meat needed to actually see what is wrong and do something about it is in the debug log. I don't have an F6 so I may or may not be able to help with that. I do have a 92AD, which works for me, but I have to see that debug log as well to have any idea what's going on.
I did post a link to my debug log for the 92AD in my first post - at least, the file created when I ran 'chirp --log'. I don't have a 'debug.log' being generated in ~/.chirp/.
Also, the F6 and the 92AD are not the same cable, at least on the face of it. Are you using an adapter to go from the 92AD multi-pin connector to speaker/mic jacks and then putting those onto the F6 cable? If so, I'm surprised that works at all. I've only ever used the 92AD for programming with the data cable, so that's really all I can reproduce here.
No, I have different cables for the two radios. The actual Icom serial cable for the 92AD and a third-party USB cable for the F6A. Both radios exhibit similar behavior when trying to read them in Chirp, so it seems to rule out a cable or configuration problem with the 92AD. I just noticed that these two radios use "live mode" while the others I've successfully read/programmed all used "clone mode" so thought maybe it was related to that.
FWIW, this evening I located my old RS92 CD and loaded the software to my Win 10 laptop. It works perfectly with the 92AD, so at least I do know for sure that the problem isn't with the radio or cable.
Thanks, Joe
Okay, I thought I read somewhere it was recommended to post here first. Will do that.
Fair enough. Usage questions here, bugs there :)
I did post a link to my debug log for the 92AD in my first post - at least, the file created when I ran 'chirp --log'. I don't have a 'debug.log' being generated in ~/.chirp/.
Please use the debug-log-getter in the help menu. It captures a snapshot and makes sure it's fresh.
No, I have different cables for the two radios. The actual Icom serial cable for the 92AD and a third-party USB cable for the F6A. Both radios exhibit similar behavior when trying to read them in Chirp, so it seems to rule out a cable or configuration problem with the 92AD. I just noticed that these two radios use "live mode" while the others I've successfully read/programmed all used "clone mode" so thought maybe it was related to that.
Okay, I misunderstood and thought you were saying you were using the same one for both.
FWIW, this evening I located my old RS92 CD and loaded the software to my Win 10 laptop. It works perfectly with the 92AD, so at least I do know for sure that the problem isn't with the radio or cable.
Yep, from the log it looks clearly like not a cable problem. I see you opened a bug, thanks, we'll continue there. Please open a *separate* one for the F6 because they're not related.
--Dan
You might try a different computer and/or operating system. I seem to remember having trouble with the Icom live on linux, but not on windows. Been a long time ago, so can't remember details for sure, could have been the other way around.
On 6/16/23 18:45, Joe Martine wrote:
Today I received a cable for my Kenwood TH-F6A and find it has the same problem as the Icom. These two are the only "live mode" radios I've tried, perhaps my issue is more generally with live mode?
The TH-F6A cable is a USB version, branded Maxton Data. When connecting to the radio most memory channels are red, a few actually show up correctly. This time I tried adding some data to an empty memory that was successfully read. Surprisingly, this does *usually* work. A couple of times the frequency would show up in the radio, but when I added an offset or tone the software seemed to indicate it was sent (green highlight then back to white) but the radio never showed the change. On one entry I made another change (change step size or something) and BOTH changes finally showed up on the radio.
While Chirp was trying to read the memories the console showed many repeats of "Unexpected result returned from radio" and "Not sure what to do with this:" followed by either a '0' or a line of gibberish.
Anyone have thoughts or suggestions to try?
Thanks, Joe
I have recently gotten back to playing with my radios after a few years (too many hobbies!) and was pleased to find Chirp can work with all of them. At this point I've successfully read and reprogrammed several radios but my IC-92AD is not cooperating.
I have the Icom programming cable and have tried reading its memory on Mac, Win and Linux with roughly the same result. Chirp reads data, but with lots of errors. Mac/Linux seem most successful, with just a few memory channels marked in red, Windows fails on almost all. But even the channels that do get read aren't quite right. There may be duplicated channel numbers, one blank the other with a frequency in it. The channel numbers may be out of order. Or some have incorrect data.
A screenshot of one read attempt (this morning): http://www.n5usr.net/images/230615_chirp/92ADLive_230615.png
Note for memories 21-27, that block is actually all FRS frequencies. The ham repeater entries are valid entries but they are NOT in memory locations 21 / 23 / 25 / 27.
I also made a log file for one run (not this morning's, but similar results): http://www.n5usr.net/images/230615_chirp/IC92AD.log
Am I doing something wrong? Perhaps a setting in the radio that needs to be changed? I've looked through the options and nothing strikes me as likely but you never know...
Chirp version is: CHIRP next-20230608 on all three platforms.
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Paul AC0HY at ac0hy@wpmills.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
participants (3)
-
Dan Smith -
Joe Martine -
W Paul Mills