[chirp_users] Wrong Kenwood radio, ID or unknown variant, see LOG output.
I have a Kenwood 372G (1). The radio shows - PC- and CHIRP seems to indicate everything is going smooth (cloning) until the very end. The radios are for work and I only want to leave commercial frequencies in it.
I guess I haven't figured out how to report an issue, so bear with me for posting here.
The debug file is attached. The errors above the one in the subject got corrected and can be ignored, I think.
Thanks.
Hi Gene,
Kenwood TK-372G Driver author here.
There are some kind of USB-TTL adapters that are picky about cloning this Kenwood Family, please try this:
* Use a real Serial port if possible (the ones in the back of the PC) * If you use a USB adapter try *NOT to use it on a USB 3.0* port or a USB hub. * If none of this above works, try a different USB-Serial Adapter. (if your interface allow it) * If all this don't work, please test the USB-serial + program interface with the OEM software to check it's working ok.
You described that the radio is getting the PC signal (it shows -PC- in the display) and the log shows that the radio didn't accept the PROGRAM command after trying 10 times...
In my experience some USB-TTL adapters just don't work with this radios (but yes with others, like the Feidaxin FD268A or the Baofengs) I suspect about the USB-serial chip sets or USB driver not keeping up with the requirements of the radio.
In this case the radio is passing to program mode and answering back but the PC seems to have a lag or not in sync with the answer...
Culprit?: who knows... chipset... driver... python-serial+driver...
In any case I'm willing to resolve that issue, please test the proposed curse of action and report back.
Cheers, Pavel, CO7WT.
El 11/05/18 a las 02:12, Gene Vincent escribió:
I have a Kenwood 372G (1). The radio shows - PC- and CHIRP seems to indicate everything is going smooth (cloning) until the very end. The radios are for work and I only want to leave commercial frequencies in it.
I guess I haven't figured out how to report an issue, so bear with me for posting here.
The debug file is attached. The errors above the one in the subject got corrected and can be ignored, I think.
Thanks.
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
Thanks for the reply.
I don't have a copy of the original software. I understand that it is DOS anyway.
I don't have a omputer with a real serial port either.
Both are the reason I turned to CHIRP.
I did try a couple of adapter cables before sending the log.
On Fri, May 11, 2018, 11:21 Pavel Milanes Costa pavelmc@gmail.com wrote:
Hi Gene,
Kenwood TK-372G Driver author here.
There are some kind of USB-TTL adapters that are picky about cloning this Kenwood Family, please try this:
- Use a real Serial port if possible (the ones in the back of the PC)
- If you use a USB adapter try *NOT to use it on a USB 3.0* port or a
USB hub.
- If none of this above works, try a different USB-Serial Adapter. (if
your interface allow it)
- If all this don't work, please test the USB-serial + program
interface with the OEM software to check it's working ok.
You described that the radio is getting the PC signal (it shows -PC- in the display) and the log shows that the radio didn't accept the PROGRAM command after trying 10 times...
In my experience some USB-TTL adapters just don't work with this radios (but yes with others, like the Feidaxin FD268A or the Baofengs) I suspect about the USB-serial chip sets or USB driver not keeping up with the requirements of the radio.
In this case the radio is passing to program mode and answering back but the PC seems to have a lag or not in sync with the answer...
Culprit?: who knows... chipset... driver... python-serial+driver...
In any case I'm willing to resolve that issue, please test the proposed curse of action and report back.
Cheers, Pavel, CO7WT.
El 11/05/18 a las 02:12, Gene Vincent escribió:
I have a Kenwood 372G (1). The radio shows - PC- and CHIRP seems to indicate everything is going smooth (cloning) until the very end. The radios are for work and I only want to leave commercial frequencies in it.
I guess I haven't figured out how to report an issue, so bear with me for posting here.
The debug file is attached. The errors above the one in the subject got corrected and can be ignored, I think.
Thanks.
chirp_users mailing listchirp_users@intrepid.danplanet.comhttp://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
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to gene8348@gmail.com at gene8348@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Also, there's something in the log about a 370 radio that I don't have.
On Fri, May 11, 2018, 11:32 Gene Vincent gene8348@gmail.com wrote:
Thanks for the reply.
I don't have a copy of the original software. I understand that it is DOS anyway.
I don't have a omputer with a real serial port either.
Both are the reason I turned to CHIRP.
I did try a couple of adapter cables before sending the log.
On Fri, May 11, 2018, 11:21 Pavel Milanes Costa pavelmc@gmail.com wrote:
Hi Gene,
Kenwood TK-372G Driver author here.
There are some kind of USB-TTL adapters that are picky about cloning this Kenwood Family, please try this:
- Use a real Serial port if possible (the ones in the back of the PC)
- If you use a USB adapter try *NOT to use it on a USB 3.0* port or a
USB hub.
- If none of this above works, try a different USB-Serial Adapter.
(if your interface allow it)
- If all this don't work, please test the USB-serial + program
interface with the OEM software to check it's working ok.
You described that the radio is getting the PC signal (it shows -PC- in the display) and the log shows that the radio didn't accept the PROGRAM command after trying 10 times...
In my experience some USB-TTL adapters just don't work with this radios (but yes with others, like the Feidaxin FD268A or the Baofengs) I suspect about the USB-serial chip sets or USB driver not keeping up with the requirements of the radio.
In this case the radio is passing to program mode and answering back but the PC seems to have a lag or not in sync with the answer...
Culprit?: who knows... chipset... driver... python-serial+driver...
In any case I'm willing to resolve that issue, please test the proposed curse of action and report back.
Cheers, Pavel, CO7WT.
El 11/05/18 a las 02:12, Gene Vincent escribió:
I have a Kenwood 372G (1). The radio shows - PC- and CHIRP seems to indicate everything is going smooth (cloning) until the very end. The radios are for work and I only want to leave commercial frequencies in it.
I guess I haven't figured out how to report an issue, so bear with me for posting here.
The debug file is attached. The errors above the one in the subject got corrected and can be ignored, I think.
Thanks.
chirp_users mailing listchirp_users@intrepid.danplanet.comhttp://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
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to gene8348@gmail.com at gene8348@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
El 11/05/18 a las 11:32, Gene Vincent escribió:
I don't have a copy of the original software. I understand that it is DOS anyway.
Wrong, the ending in "G" series is known as the "Series 60G" and did has a windows version software, it's named KPG-56D in version 4.0... it needs a serial o work...
Cheers.
On Fri, May 11, 2018 at 10:16 AM, Pavel Milanes Costa pavelmc@gmail.com wrote:
Hi Gene,
Kenwood TK-372G Driver author here.
Pavel,
I took a look at the debug log this morning but didn't have time to reply (and was hoping that you would also notice this discussion).
It appeared to me that the radio was being read OK. The problem, as I saw it, was that CHIRP was receiving "P3720\x06\xfb" from the radio but CHIP is expecting "P3720\x06\xff" (the last byte being FB instead of FF).
It seems to me that a test driver could be posted that just changes the FF to FB to see if the radio could be fully read by CHIRP. If it can, then maybe all that is needed would be to add and additional "fingerprint" to the driver.
Jim KC9HI
That would be wonderful if it is possible. Thanks.
On Fri, May 11, 2018 at 3:24 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Fri, May 11, 2018 at 10:16 AM, Pavel Milanes Costa pavelmc@gmail.com wrote:
Hi Gene,
Kenwood TK-372G Driver author here.
Pavel,
I took a look at the debug log this morning but didn't have time to reply (and was hoping that you would also notice this discussion).
It appeared to me that the radio was being read OK. The problem, as I saw it, was that CHIRP was receiving "P3720\x06\xfb" from the radio but CHIP is expecting "P3720\x06\xff" (the last byte being FB instead of FF).
It seems to me that a test driver could be posted that just changes the FF to FB to see if the radio could be fully read by CHIRP. If it can, then maybe all that is needed would be to add and additional "fingerprint" to the driver.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to gene8348@gmail.com at gene8348@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
Playing with the OEM software I can't find a variant that identifies as this:
"P3720\x06\xfb\f1"
Gene, please can you describe the radio, in frequency range, number of channels, add on boards etc?
I'm thinking like Jim, maybe this is a custom or special model?
Or the two last bytes means something I haven't deciphered yet?
Maybe options included? Scramber? trunking?
If so then we must about to match that two last bytes...
I'm waiting for a borrowed TK-272G handy radio to make some tests.....
Cheers to all...
El 11/05/18 a las 15:24, Jim Unroe escribió:
On Fri, May 11, 2018 at 10:16 AM, Pavel Milanes Costa pavelmc@gmail.com wrote:
Hi Gene,
Kenwood TK-372G Driver author here.
Pavel,
I took a look at the debug log this morning but didn't have time to reply (and was hoping that you would also notice this discussion).
It appeared to me that the radio was being read OK. The problem, as I saw it, was that CHIRP was receiving "P3720\x06\xfb" from the radio but CHIP is expecting "P3720\x06\xff" (the last byte being FB instead of FF).
It seems to me that a test driver could be posted that just changes the FF to FB to see if the radio could be fully read by CHIRP. If it can, then maybe all that is needed would be to add and additional "fingerprint" to the driver.
Jim KC9HI _______________________________________________ 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
participants (3)
-
Gene Vincent -
Jim Unroe -
Pavel Milanes Costa