New Model #2475
closedUV-5R error Incorrect model selected
Added by Gary M about 9 years ago. Updated about 4 years ago.
0%
Description
Unable to download the factory image from a new UV5R. I get the error "Incorrect model selected." CHIRP works fine on two other UV5R radios with the same FTDI USB cable, Windows XP, and daily build 20150325. Also tried builds 20150321 and 20150318 and got same error. Attached the Debug.log in case it is helpful.
Files
| debug.log (13.5 KB) debug.log | Gary M, 03/30/2015 04:17 PM | ||
| debug - Fail.log (13 KB) debug - Fail.log | Failed Debug Log | A. Kitzman, 04/06/2015 01:42 PM | |
| uv5r.py (56.3 KB) uv5r.py | Jim Unroe, 04/08/2015 07:35 PM | ||
| debug.log (13.9 KB) debug.log | debug log | Michael McClelland, 04/13/2015 12:30 PM | |
| CHIRP-invalidmodel.zip (1.51 MB) CHIRP-invalidmodel.zip | Microsoft Problem Step Recorder screenshots | Michael McClelland, 04/13/2015 12:30 PM | |
| debug.log (13.3 KB) debug.log | UV-5Rv3+ Debug on daily build 20150415 | Asa Randall, 04/15/2015 08:21 AM | |
| debug.log (17.9 KB) debug.log | ferencak gregor, 04/17/2015 02:45 PM | ||
| debug.log (818 KB) debug.log | debulg | ferencak gregor, 04/25/2015 01:20 AM | |
| uv5r (4).py (54.1 KB) uv5r (4).py | ferencak gregor, 04/25/2015 01:20 AM |
Updated by A. Kitzman about 9 years ago
- File debug - Fail.log debug - Fail.log added
Build 20150405 shows the same error. Attached the Debug.log from 20150405 Build.
This condition occurs on 3 new UV5R, purchased from Amazon in the past week.
BFB297
150126N
The same setup works fine with BFB293.
Updated by Daniele Bellettati about 9 years ago
Thank you for your interest.
Have a UV-5R buyed from Amazon
Power +3 gives bfb297
Power +6 gives 150304N
I'm using the daily build 20150405.
Cable is original BAOFENG Prolific on COM 18 with driver version 3.2.0.0
Cable and communication was perfectly functional with a november 2014 baofeng firmware version
I also get "Incorrect "model selected"" and then the radio reboots.
Updated by Elliott Reyna about 9 years ago
Hello, first time posting here...
Same issue as above. Just ordered a UV-5R from Amazon on 4/6/15
Have been using CHIRP with 5 other Baofengs for over a year.
BFB297
150304N
Daily Build 20150405
3.2.0.0 driver
I also tried to upload an earlier IMG file (just for ships and giggles)
Got error message - Unsupported Firmware Version 'HN5RV011FB297'
Updated by Jim Unroe about 9 years ago
- Assignee set to Jim Unroe
- Target version set to 0.5.0
I'm working on a patch to add this "new" firmware version.
Jim KC9HI
Updated by Joel Sowers about 9 years ago
Thanks Jim! I see you are working this but for what it's worth
Newbie here - Just bought my radio from Amazon last week.
Same issues as reported above - Incorrect Model Selected
My Radio Info :
Power + 3 = BFB297
Power + 6 = 150304N
Chirp DB = 02150405
Mac OSX Yosemite Ver 10.10.2
Baofeng Cable & Latest Prolific Driver
Updated by Jim Unroe about 9 years ago
This test module has the "new" firmware fix and so other updates that I have been working on. If you want to try it and give me some feedback as to if it works for you or not here is how you use it.
1 download the uv5r.py file and save it to where you normally keep you CHIRP .img files
2 click Help and enable "Enable Developer Functions"
3 click File
4 click Load Module and load the file that was saved in step 1
Try it.
Note: This does not permanently change your CHIRP. You will have to load it each time you load CHIRP. Once this patches has been submitted and integrated into CHIRP, you won't have to load it any more and you can disable "Enable Developer Functions"
Jim KC9HI
Updated by Joel Sowers about 9 years ago
Awesome Jim!
It worked great - tested download and upload - worked like a champ!
Let me know if you need any other data.
Thanks again for such a quick response!
Updated by Daniele Bellettati about 9 years ago
Many thanks Jim!
Now work great with .py module.
Your passion and your dedication are priceless.
Updated by Matthew Ross about 9 years ago
Confirmed this works on my new UV-5R's (with same specs posted above). Also works on two different old models I have, (one a 5r, one a 5r+) with this module loaded. I'd say it's working, all around! Thanks!
Updated by Michael McClelland about 9 years ago
- File debug.log debug.log added
- File CHIRP-invalidmodel.zip CHIRP-invalidmodel.zip added
Hi, I am using a UV-5R purchased from Amazon in late March, I am using the latest CHIRP daily-20150411. I continue to get the "Invalid model" error as described by others.
When attempting to load the patch included above, I get an error stating "Unable to load module; invalid syntax (uv5r.py, line 1)" Though this module may be unnecessary with this build as it is later than the ones others have used.
I am using version 3.4.67.325 of the Prolific driver, which accompanied my Cable on a CD... But I have also downgraded to 3.2.0.
Updated by Michael McClelland about 9 years ago
Looks like I have resolved my issue, when downloading the uv5r.py, it was downloading the formatted HTML, not the native python. My issue has been corrected, and I have successfully cloned my radio.
Steps I took to resolve: Click on the uv5r.py link in the top of the ticket text to open the sites listing, clicked on the "download" button at the top of the screen, saved the file to disk, and copied to the CHIRP directory. (Saving directly to the ../program files(x86)/CHIRP directory causes a permissions issue with browsers).
Updated by Asa Randall about 9 years ago
I continue having issues with the UV-5RV3+ I purchased in late March.
Getting "Incorrect Model" error, Using daily build 20150411 and uv5r.py patch (also, without patch, have the same error).
+3: BFB297
+6: 150110N
Thanks so much for all the hard work on this.
Updated by Jim Unroe about 9 years ago
- Status changed from New to Feedback
Try after tomorrows daily build. If you still have issues, then attach a debug.log file.
Jim KC9HI
Updated by Asa Randall about 9 years ago
Just tried new daily build 20150415, with same result (Incorrect Model). Debug Attached.
I do note that the Radio Version is reported as '\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'; not sure if this is typical or may relate to bad firmware flash?
Again, very grateful for the help.
Updated by Gary M about 9 years ago
Great work CHIRP team! Build 20150415 works on the following UV5R's
HN5RV01, 3+: 1FB297, 6+: 150126N
NSR2401, 3+: BFB297 6+: 14006N
NSR-20, 3+: BFB297 6+: 14006N
Updated by Jim Unroe about 9 years ago
Asa,
For whatever reason, your radio reports its firmware version as '\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'. This doesn't give CHIRP anything useful to determine if the radio connected is same type of radio that the user selected. I have seen this with at least one other radio so I don't know if this was the result of a bad flash or just a simple mistake at the factory. Unless one of the other developers has a suggestion, I'm not sure anything can be done to support this radio.
Jim
Updated by ferencak gregor about 9 years ago
Asa Randall wrote:
I continue having issues with the UV-5RV3+ I purchased in late March.
Getting "Incorrect Model" error, Using daily build 20150411 and uv5r.py patch (also, without patch, have the same error).
+3: BFB297
+6: 150110N
Thanks so much for all the hard work on this.
I have done the same steps as described same firmware number and also +6 number except my was declared as standard UV-5R. VIP software from baofeng (
BF5R_VIP_v120725_BFB291_ENG(VB6).zip) reads information from it normally if I don't count random freezes.
Thanks
Updated by ferencak gregor about 9 years ago
attaching my log just to keep in line. Jim took a look on it already.
Updated by ferencak gregor about 9 years ago
problem solved. I think Jim can give more info about solving issue when radio does not give his name to Chirp.
Updated by ferencak gregor about 9 years ago
- File debug.log debug.log added
- File uv5r (4).py uv5r (4).py added
I came across with uploading of image to radio:
[2015-04-25 11:04:17,733] chirp.ui.mainapp - DEBUG: Opening port after pre_upload prompt. [2015-04-25 11:04:32,105] chirp.ui.clone - DEBUG: Clone thread started [2015-04-25 11:04:32,167] chirp.ui.mainapp - INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%. [2015-04-25 11:04:32,276] chirp.ui.mainapp - INFO: Ident: 000: aa 30 76 04 00 05 20 dd .0v..... [2015-04-25 11:04:32,292] chirp.ui.mainapp - DEBUG: _firmware_version_from_image: 000: 20 20 20 20 20 20 20 20 ........ 008: 20 20 20 20 20 20 00 00 ........ [2015-04-25 11:04:32,651] chirp.ui.mainapp - INFO: Image Version is ' ' [2015-04-25 11:04:32,651] chirp.ui.mainapp - INFO: Radio Version is '\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' [2015-04-25 11:04:32,651] chirp.ui.reporting - DEBUG: Reporting exception [2015-04-25 11:04:32,651] chirp.ui.common - ERROR: -- Exception: -- [2015-04-25 11:04:32,651] chirp.ui.common - ERROR: Traceback (most recent call last): File "chirp\ui\clone.pyo", line 236, in run File "D:\Downloads\uv5r (4).py", line 704, in sync_out File "D:\Downloads\uv5r (4).py", line 549, in _do_upload RadioError: The upload was stopped because the firmware version of the image ( ) does not match that of the radio (ÿÿÿÿÿÿÿÿÿÿÿÿÿÿ). [2015-04-25 11:04:32,651] chirp.ui.common - ERROR: ---------------- [2015-04-25 11:04:32,651] chirp.ui.clone - ERROR: Clone failed: The upload was stopped because the firmware version of the image ( ) does not match that of the radio (ÿÿÿÿÿÿÿÿÿÿÿÿÿÿ). [2015-04-25 11:04:32,683] chirp.ui.clone - DEBUG: Clone thread ended [2015-04-25 11:04:32,683] chirp.ui.reporting - DEBUG: Reporting model usage: Baofeng_UV-5R,upload,True [2015-04-25 11:04:32,683] chirp.ui.reporting - DEBUG: Reporting exception [2015-04-25 11:04:32,683] chirp.ui.inputdialog - ERROR: --- Exception Dialog: The upload was stopped because the firmware version of the image ( ) does not match that of the radio (ÿÿÿÿÿÿÿÿÿÿÿÿÿÿ). --- [2015-04-25 11:04:32,683] chirp.ui.inputdialog - ERROR: Traceback (most recent call last): File "chirpw", line 66, inAttributeError: 'NoneType' object has no attribute 'split' [2015-04-25 11:04:32,683] chirp.ui.inputdialog - ERROR: ---------------------------- D:\Downloads\chirp-daily-20150416-win32\chirpw.exe\chirp\ui\mainapp.py:483: PangoWarning: Invalid UTF-8 string passed to pango_layout_set_text() [2015-04-25 11:04:33,073] chirp.ui.reporting - DEBUG: Failed to report:
Steps i took:
- connect radio to PC and start chirp
- load additional py script by Jim (attached)
- download image
- save original image
- import CSV with additional frequencies
- save additional config
- tried to upload and failed
Updated by gary frazier almost 9 years ago
mine is the same debug log as above.
has this issue been resolved?
Or should I return the radio. Just got it 4 days ago.
thanks
Updated by Jim Unroe almost 9 years ago
Gary,
This can't be resolved. The information that CHIRP requires to determine where the radio "image" came from is missing. You either need to get the radio replaced with one that has the necessary information or use the OEM software that does not require this information. Sorry, but this is a problem with the radio and not CHIRP.
Jim KC9HI
Updated by Bernhard Hailer about 4 years ago
- Status changed from Feedback to Closed
No more traffic on this ticket.