[chirp_users] Retevis RT22
I have tried to download onto chirp so I can update new radios and I continuously get an error saying radio identification failed I’m using the oct 16 download
Any suggestions?? We have done this before with other RT22s
Rebecca
Sent from my iPhone
On Sun, Oct 24, 2021 at 7:18 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
I have tried to download onto chirp so I can update new radios and I continuously get an error saying radio identification failed I’m using the oct 16 download
Any suggestions?? We have done this before with other RT22s
Rebecca
Attach a debug.log file.
Jim KC9HI
How do I get a debug.log file??
Sent from my iPhone
On Oct 24, 2021, at 7:31 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Sun, Oct 24, 2021 at 7:18 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
I have tried to download onto chirp so I can update new radios and I continuously get an error saying radio identification failed I’m using the oct 16 download
Any suggestions?? We have done this before with other RT22s
Rebecca
Attach a debug.log file.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rebecca at rcopeland@mandeljcc.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com [ "CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe" ]
On Sun, Oct 24, 2021 at 7:37 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
How do I get a debug.log file??
How to find debug.log file is explained in the CHIRP website's documentation area. More specifically it is on the "How to report issues" page. Here is the direct link to it.
https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
Jim KC9HI
Sent from my iPhone
On Oct 24, 2021, at 7:52 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Sun, Oct 24, 2021 at 7:37 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
How do I get a debug.log file??
How to find debug.log file is explained in the CHIRP website's documentation area. More specifically it is on the "How to report issues" page. Here is the direct link to it.
https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rebecca at rcopeland@mandeljcc.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com [ "CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe" ]
On Sun, Oct 24, 2021 at 8:15 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
Sent from my iPhone
I get "corrupt and can't be opened".
Jim KC9HI
I looked at it and I think the part you'll be looking for is: [2021-10-24 19:19:06,763] chirp.ui.inputdialog - ERROR: ---------------------------- [2021-10-24 19:19:15,259] chirp.ui.mainapp - DEBUG: User selected Retevis RT22 on port COM6 [2021-10-24 19:19:15,260] chirp.ui.clone - DEBUG: Clone thread started [2021-10-24 19:19:15,260] chirp.drivers.retevis_rt22 - DEBUG: download [2021-10-24 19:19:17,124] chirp.ui.reporting - DEBUG: Reporting exception [2021-10-24 19:19:17,124] chirp.ui.common - ERROR: -- Exception: -- [2021-10-24 19:19:17,124] chirp.ui.common - ERROR: Traceback (most recent call last): File "chirp\ui\clone.pyo", line 255, in run File "chirp\drivers\retevis_rt22.pyo", line 387, in sync_in File "chirp\drivers\retevis_rt22.pyo", line 273, in do_download File "chirp\drivers\retevis_rt22.pyo", line 147, in _rt22_enter_programming_mode RadioError: The radio did not accept program mode after five tries. Check you interface cable and power cycle your radio.
[2021-10-24 19:19:17,124] chirp.ui.common - ERROR: ---------------- [2021-10-24 19:19:17,124] chirp.ui.clone - ERROR: Clone failed: The radio did not accept program mode after five tries. Check you interface cable and power cycle your radio.
------ Original Message ------ From: "Jim Unroe" rock.unroe@gmail.com To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Sent: Sun 10 24 21 19:29:07 Subject: Re: [chirp_users] Retevis RT22
On Sun, Oct 24, 2021 at 8:15 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
Sent from my iPhone
I get "corrupt and can't be opened".
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Al Jones at al@aljones.us To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Ok, so what do I do now?
Sent from my iPhone
On Oct 24, 2021, at 8:39 PM, Al Jones al@aljones.us wrote:
I looked at it and I think the part you'll be looking for is: [2021-10-24 19:19:06,763] chirp.ui.inputdialog - ERROR:
[2021-10-24 19:19:15,259] chirp.ui.mainapp - DEBUG: User selected Retevis RT22 on port COM6 [2021-10-24 19:19:15,260] chirp.ui.clone - DEBUG: Clone thread started [2021-10-24 19:19:15,260] chirp.drivers.retevis_rt22 - DEBUG: download [2021-10-24 19:19:17,124] chirp.ui.reporting - DEBUG: Reporting exception [2021-10-24 19:19:17,124] chirp.ui.common - ERROR: -- Exception: -- [2021-10-24 19:19:17,124] chirp.ui.common - ERROR: Traceback (most recent call last): File "chirp\ui\clone.pyo", line 255, in run File "chirp\drivers\retevis_rt22.pyo", line 387, in sync_in File "chirp\drivers\retevis_rt22.pyo", line 273, in do_download File "chirp\drivers\retevis_rt22.pyo", line 147, in _rt22_enter_programming_mode RadioError: The radio did not accept program mode after five tries. Check you interface cable and power cycle your radio.
[2021-10-24 19:19:17,124] chirp.ui.common - ERROR: ---------------- [2021-10-24 19:19:17,124] chirp.ui.clone - ERROR: Clone failed: The radio did not accept program mode after five tries. Check you interface cable and power cycle your radio.
------ Original Message ------ From: "Jim Unroe" rock.unroe@gmail.com To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Sent: Sun 10 24 21 19:29:07 Subject: Re: [chirp_users] Retevis RT22
On Sun, Oct 24, 2021 at 8:15 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
Sent from my iPhone
I get "corrupt and can't be opened".
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Al Jones at al@aljones.us 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 Rebecca at rcopeland@mandeljcc.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com [ "CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe" ]
On Sun, Oct 24, 2021 at 8:49 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
Ok, so what do I do now?
Unless you can get the OEM software to work, it is a cable/connection problem. No programming software can work unless there is a complete and working connection between the radio and computer. Make sure that nothing is getting in the way of the plug getting fully inserted into the socket. Sometimes the socket cover can get in the way. Sometimes the shape of the radio's case can get in the way. Sometimes the socket of these cheap radios is positioned too far inside the case so the pins of the programming cable can't fully reach inside the socket to make proper connections. Sometimes it is possible to work around these issues by pressing on the plug as the cloning progresses.
Jim KC9HI
Okay, I will try another radio, using the same cable I used in July to program 10 radios
Sent from my iPhone
On Oct 24, 2021, at 9:12 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Sun, Oct 24, 2021 at 8:49 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
Ok, so what do I do now?
Unless you can get the OEM software to work, it is a cable/connection problem. No programming software can work unless there is a complete and working connection between the radio and computer. Make sure that nothing is getting in the way of the plug getting fully inserted into the socket. Sometimes the socket cover can get in the way. Sometimes the shape of the radio's case can get in the way. Sometimes the socket of these cheap radios is positioned too far inside the case so the pins of the programming cable can't fully reach inside the socket to make proper connections. Sometimes it is possible to work around these issues by pressing on the plug as the cloning progresses.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rebecca at rcopeland@mandeljcc.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com [ "CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe" ]
or cut a lttle plastic off....
בתאריך יום ב׳, 25 באוק׳ 2021 ב-4:14 מאת Jim Unroe <rock.unroe@gmail.com >:
On Sun, Oct 24, 2021 at 8:49 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
Ok, so what do I do now?
Unless you can get the OEM software to work, it is a cable/connection problem. No programming software can work unless there is a complete and working connection between the radio and computer. Make sure that nothing is getting in the way of the plug getting fully inserted into the socket. Sometimes the socket cover can get in the way. Sometimes the shape of the radio's case can get in the way. Sometimes the socket of these cheap radios is positioned too far inside the case so the pins of the programming cable can't fully reach inside the socket to make proper connections. Sometimes it is possible to work around these issues by pressing on the plug as the cloning progresses.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to amnon at amnon.zohar@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Sun, Oct 24, 2021 at 8:41 PM Al Jones al@aljones.us wrote:
I looked at it and I think the part you'll be looking for is: [2021-10-24 19:19:06,763] chirp.ui.inputdialog - ERROR:
[2021-10-24 19:19:15,259] chirp.ui.mainapp - DEBUG: User selected Retevis RT22 on port COM6 [2021-10-24 19:19:15,260] chirp.ui.clone - DEBUG: Clone thread started [2021-10-24 19:19:15,260] chirp.drivers.retevis_rt22 - DEBUG: download [2021-10-24 19:19:17,124] chirp.ui.reporting - DEBUG: Reporting exception [2021-10-24 19:19:17,124] chirp.ui.common - ERROR: -- Exception: -- [2021-10-24 19:19:17,124] chirp.ui.common - ERROR: Traceback (most recent call last): File "chirp\ui\clone.pyo", line 255, in run File "chirp\drivers\retevis_rt22.pyo", line 387, in sync_in File "chirp\drivers\retevis_rt22.pyo", line 273, in do_download File "chirp\drivers\retevis_rt22.pyo", line 147, in _rt22_enter_programming_mode RadioError: The radio did not accept program mode after five tries. Check you interface cable and power cycle your radio.
[2021-10-24 19:19:17,124] chirp.ui.common - ERROR: ---------------- [2021-10-24 19:19:17,124] chirp.ui.clone - ERROR: Clone failed: The radio did not accept program mode after five tries. Check you interface cable and power cycle your radio.
It is a programming cable issue. CHIRP is not getting a reply back from the radio after it sends the request to begin the cloning process after trying 5 times. You would get the exact same error if you attempted to download with the plug not inserted into the radio. My guess is that the issue has something to do with the connection between the plug and the radio's socket. Check to see that nothing is keeping the plug from being fully inserted into the socket.
Jim KC9HI
Thank you, I have checked and the plug is 100% plugged in to the radio and the computer
Sent from my iPhone
On Oct 24, 2021, at 8:57 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Sun, Oct 24, 2021 at 8:41 PM Al Jones al@aljones.us wrote:
I looked at it and I think the part you'll be looking for is: [2021-10-24 19:19:06,763] chirp.ui.inputdialog - ERROR:
[2021-10-24 19:19:15,259] chirp.ui.mainapp - DEBUG: User selected Retevis RT22 on port COM6 [2021-10-24 19:19:15,260] chirp.ui.clone - DEBUG: Clone thread started [2021-10-24 19:19:15,260] chirp.drivers.retevis_rt22 - DEBUG: download [2021-10-24 19:19:17,124] chirp.ui.reporting - DEBUG: Reporting exception [2021-10-24 19:19:17,124] chirp.ui.common - ERROR: -- Exception: -- [2021-10-24 19:19:17,124] chirp.ui.common - ERROR: Traceback (most recent call last): File "chirp\ui\clone.pyo", line 255, in run File "chirp\drivers\retevis_rt22.pyo", line 387, in sync_in File "chirp\drivers\retevis_rt22.pyo", line 273, in do_download File "chirp\drivers\retevis_rt22.pyo", line 147, in _rt22_enter_programming_mode RadioError: The radio did not accept program mode after five tries. Check you interface cable and power cycle your radio.
[2021-10-24 19:19:17,124] chirp.ui.common - ERROR: ---------------- [2021-10-24 19:19:17,124] chirp.ui.clone - ERROR: Clone failed: The radio did not accept program mode after five tries. Check you interface cable and power cycle your radio.
It is a programming cable issue. CHIRP is not getting a reply back from the radio after it sends the request to begin the cloning process after trying 5 times. You would get the exact same error if you attempted to download with the plug not inserted into the radio. My guess is that the issue has something to do with the connection between the plug and the radio's socket. Check to see that nothing is keeping the plug from being fully inserted into the socket.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rebecca at rcopeland@mandeljcc.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com [ "CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe" ]
There is info on this link:
https://chirp.danplanet.com/projects/chirp/wiki/How_To_Report_Issues
Look about halfway down the page.
You will need to create a login/account to report an issue
Ken, N2VIP
On Oct 24, 2021, at 18:35, Rebecca Copeland rcopeland@mandeljcc.org wrote:
How do I get a debug.log file??
Sent from my iPhone
On Oct 24, 2021, at 7:31 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Sun, Oct 24, 2021 at 7:18 PM Rebecca Copeland rcopeland@mandeljcc.org wrote:
I have tried to download onto chirp so I can update new radios and I continuously get an error saying radio identification failed I’m using the oct 16 download
Any suggestions?? We have done this before with other RT22s
Rebecca
Attach a debug.log file.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rebecca at rcopeland@mandeljcc.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com [ "CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe" ]
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ken Hansen at ken@n2vip.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (5)
-
Al Jones
-
Amnon Zohar
-
Jim Unroe
-
Ken Hansen
-
Rebecca Copeland