[chirp_users] 2 UR-5V's refuse to download the factory set up
Afternoon,
I have 2 UR-5V's refuse to download the factory set up prior to me uploading my programing.
For the first radio the error code is;
Radio refused to send block 0x0000
For the second radio the error code is;
Radio refused to send block 0x1ec0
Using windows 7
Never had trouble with re=-programing BF UV-5R's before this
Any suggestions
Thanks,
Jay
The Savage Possum
Make sure you have the radio in memory recall mode, not VFO mode. I've had the same thing happen, and that cleared it up. On Mar 28, 2015 5:20 PM, "SavagePossum" savagepossum@gmail.com wrote:
Afternoon,
I have 2 UR-5V's refuse to download the factory set up prior to me uploading my programing.
For the first radio the error code is;
Radio refused to send block 0x0000
For the second radio the error code is;
Radio refused to send block 0x1ec0
Using windows 7
Never had trouble with re=-programing BF UV-5R's before this
Any suggestions
Thanks,
Jay
*The Savage Possum*
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
Crazy thing I am not only getting an error message stating that some of the features or functions may not work but the radio will not receive from one another no matter what.
Prior to this several radios were programmed and with no problems now the newer radios are not accepting programming, what can I do to over come this issue? I would really like to be able to program them the same as prior radios. Only the new radios are having a problem not the older UV5's
Rick_KRX1
On Sat, Mar 28, 2015 at 6:01 PM, Chucks chuckination@gmail.com wrote:
Make sure you have the radio in memory recall mode, not VFO mode. I've had the same thing happen, and that cleared it up. On Mar 28, 2015 5:20 PM, "SavagePossum" savagepossum@gmail.com wrote:
Afternoon,
I have 2 UR-5V's refuse to download the factory set up prior to me uploading my programing.
For the first radio the error code is;
Radio refused to send block 0x0000
For the second radio the error code is;
Radio refused to send block 0x1ec0
Using windows 7
Never had trouble with re=-programing BF UV-5R's before this
Any suggestions
Thanks,
Jay
*The Savage Possum*
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
On Sat, Mar 28, 2015 at 9:36 PM, kcrunchone hill kcrunchone@gmail.com wrote:
Crazy thing I am not only getting an error message stating that some of the features or functions may not work but the radio will not receive from one another no matter what.
Prior to this several radios were programmed and with no problems now the newer radios are not accepting programming, what can I do to over come this issue? I would really like to be able to program them the same as prior radios. Only the new radios are having a problem not the older UV5's
Rick_KRX1
Sounds like you've uploaded a CHIRP Radio Image file saved from a radio with BFB firmware into a radio with N5R firmware. That is a no-no. The reverse is also true. The memory layout was changed with the introduction of N5R firmware making one radios image file incompatible with the other.
You must not be using the latest daily build. The latest daily build verifies that the image being uploaded is compatible before uploading it. The upload is aborted if it isn't compatible the the target radio. Daily builds prior to September 2014 and the year old (next month) CHIRP v0.4.x stable build do not have this protection and because of this are not recommended for use with Baofeng radios.
Before upgrading you will have to upload the original back up image file that was saved before the incompatible image was loaded to the radio. If one wasn't made (for some reason they usually aren't) then you will be able to get one and instructions for recovery on the miklor.com website.
http://www.miklor.com/uv5r/UV5R-Recovery.php#N5R
Jim KC9HI
Sounds like it might be wise to save the factory image with the firmware version in the file name somewhere.
Sent from my iPossum Regards, The Savage Possum
On Mar 28, 2015, at 21:26, Jim Unroe rock.unroe@gmail.com wrote:
On Sat, Mar 28, 2015 at 9:36 PM, kcrunchone hill kcrunchone@gmail.com wrote: Crazy thing I am not only getting an error message stating that some of the features or functions may not work but the radio will not receive from one another no matter what.
Prior to this several radios were programmed and with no problems now the newer radios are not accepting programming, what can I do to over come this issue? I would really like to be able to program them the same as prior radios. Only the new radios are having a problem not the older UV5's
Rick_KRX1
Sounds like you've uploaded a CHIRP Radio Image file saved from a radio with BFB firmware into a radio with N5R firmware. That is a no-no. The reverse is also true. The memory layout was changed with the introduction of N5R firmware making one radios image file incompatible with the other.
You must not be using the latest daily build. The latest daily build verifies that the image being uploaded is compatible before uploading it. The upload is aborted if it isn't compatible the the target radio. Daily builds prior to September 2014 and the year old (next month) CHIRP v0.4.x stable build do not have this protection and because of this are not recommended for use with Baofeng radios.
Before upgrading you will have to upload the original back up image file that was saved before the incompatible image was loaded to the radio. If one wasn't made (for some reason they usually aren't) then you will be able to get one and instructions for recovery on the miklor.com website.
http://www.miklor.com/uv5r/UV5R-Recovery.php#N5R
Jim KC9HI _______________________________________________ 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
Is the above radio supported by proxy under some other branding or designation (ie like the H-777 supports BF-888)?
Sent from my iPossum Regards, The Savage Possum
On Mar 28, 2015, at 21:26, Jim Unroe rock.unroe@gmail.com wrote:
On Sat, Mar 28, 2015 at 9:36 PM, kcrunchone hill kcrunchone@gmail.com wrote: Crazy thing I am not only getting an error message stating that some of the features or functions may not work but the radio will not receive from one another no matter what.
Prior to this several radios were programmed and with no problems now the newer radios are not accepting programming, what can I do to over come this issue? I would really like to be able to program them the same as prior radios. Only the new radios are having a problem not the older UV5's
Rick_KRX1
Sounds like you've uploaded a CHIRP Radio Image file saved from a radio with BFB firmware into a radio with N5R firmware. That is a no-no. The reverse is also true. The memory layout was changed with the introduction of N5R firmware making one radios image file incompatible with the other.
You must not be using the latest daily build. The latest daily build verifies that the image being uploaded is compatible before uploading it. The upload is aborted if it isn't compatible the the target radio. Daily builds prior to September 2014 and the year old (next month) CHIRP v0.4.x stable build do not have this protection and because of this are not recommended for use with Baofeng radios.
Before upgrading you will have to upload the original back up image file that was saved before the incompatible image was loaded to the radio. If one wasn't made (for some reason they usually aren't) then you will be able to get one and instructions for recovery on the miklor.com website.
http://www.miklor.com/uv5r/UV5R-Recovery.php#N5R
Jim KC9HI _______________________________________________ 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
On 3/29/2015 08:45, Savage Possum wrote:
Is the above radio supported by proxy under some other branding or designation (ie like the H-777 supports BF-888)?
No. Not supported. There have been a couple people who said they would send one to a developer; but that fell on deaf ears.
Not truly surprised. I follow their yahoo group and they seem to be nothing trouble with software programming - depending on phase of the moon & how you hold your tongue.
From My iPossum Regards, The Savage Possum
On Mar 29, 2015, at 12:24, John Wilkerson jl_wilkerson@att.net wrote:
On 3/29/2015 08:45, Savage Possum wrote: Is the above radio supported by proxy under some other branding or designation (ie like the H-777 supports BF-888)?
No. Not supported. There have been a couple people who said they would send one to a developer; but that fell on deaf ears. _______________________________________________ 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
I've had ZERO difficulties programming mine.
On 3/29/2015 13:29, Savage Possum wrote:
Not truly surprised. I follow their yahoo group and they seem to be nothing trouble with software programming - depending on phase of the moon& how you hold your tongue.
From My iPossum
Regards, The Savage Possum
On Mar 29, 2015, at 12:24, John Wilkersonjl_wilkerson@att.net wrote:
On 3/29/2015 08:45, Savage Possum wrote: Is the above radio supported by proxy under some other branding or designation (ie like the H-777 supports BF-888)?
No. Not supported. There have been a couple people who said they would send one to a developer; but that fell on deaf ears.
Using 1.01 or 1.03? Green case or black case?
From My iPossum Regards, The Savage Possum
On Mar 29, 2015, at 14:53, John Wilkerson jl_wilkerson@att.net wrote:
I've had ZERO difficulties programming mine.
On 3/29/2015 13:29, Savage Possum wrote: Not truly surprised. I follow their yahoo group and they seem to be nothing trouble with software programming - depending on phase of the moon& how you hold your tongue.
From My iPossum
Regards, The Savage Possum
On Mar 29, 2015, at 12:24, John Wilkersonjl_wilkerson@att.net wrote:
On 3/29/2015 08:45, Savage Possum wrote: Is the above radio supported by proxy under some other branding or designation (ie like the H-777 supports BF-888)?
No. Not supported. There have been a couple people who said they would send one to a developer; but that fell on deaf ears.
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
1.03 Green Case
From: Savage Possum savagepossum@gmail.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Sunday, March 29, 2015 6:12 PM Subject: Re: [chirp_users] Puxing PX-888k supported?
Using 1.01 or 1.03? Green case or black case?
Thanks. Was going with earlier advice using 1.01 w/ the green case.
From My iPossum Regards, The Savage Possum
On Mar 29, 2015, at 18:03, John W. jl_wilkerson@att.net wrote:
1.03 Green Case
From: Savage Possum savagepossum@gmail.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Sunday, March 29, 2015 6:12 PM Subject: Re: [chirp_users] Puxing PX-888k supported?
Using 1.01 or 1.03? Green case or black case?
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
participants (7)
-
Chucks -
Jim Unroe -
John W. -
John Wilkerson
-
kcrunchone hill -
Savage Possum -
SavagePossum