Bug #2851
closedNew Baofeng uv-82 "Radio did not respond"
0%
Description
I have 2 older (~6 months) uv-82 that work fine with chirp.
I just purchased 2 more. Both of them fail with "Radio did not respond"
I have verified that the cable and software install continue to work with my older units and I'm convinced my newer ones have the cables fully inserted.
There does seem to be some interactions with my new radio because attempts to download it do cause changes on the display.
power on with 5 key reports:
version
B82S27
power on with 6 key reports:
150313N
B820001
Files
Updated by Jim Unroe over 8 years ago
- Status changed from New to Feedback
Ed,
According to the debug.log file, CHIRP doesn't work because the radio is not responding. This has to be a radio or cable issue.
Radios with that firmware version have been around for about 10 months. Double check that the plug is fully into the radio. You might even try pressing on the plug during the attempted transfer.
Jim KC9HI
Updated by Ed Beers over 8 years ago
I am sure my cable is fully connected.
I guess I will have to try and locate another cable for testing or de-case my radio so I can see the connections.
Ed
Updated by Scott Nance over 8 years ago
I am having the same issue, I can download from the radio, but I cannot upload. Just got this radio yesterday.
Updated by Jim Unroe over 8 years ago
Have you download from the radio to CHIRP and then immediately uploaded back to the radio or are you trying to upload a CHIRP Radio Image from another radio?
If you try to upload an image from a UV-5R, for example, into a UV-82 you will get a "radio did not respond" error and that would be expected.
Jim KC9HI
Updated by Ed Beers over 8 years ago
Scott has a different problem and should start his own bug if he thinks it necessary.
Mine are brand new with no changes (not even manual ones). My "radio did not respond" occurs when I attempt to do a initial download.
I have a new cable on order.
Updated by Jim Unroe over 8 years ago
Ed,
Do they work with the OEM software?
Jim KC9HI
Updated by Ed Beers over 8 years ago
I haven't been able to install the OEM SW. Some problem with an ancient visual basic serial port library.
Updated by Ed Beers over 8 years ago
My new cable works on all four units. Why the other one only works on two of them remains a mystery.
My original intent was to clone the configuration from the first two to the new two.
After reading over the issues others are having, it sound like this is not possible or not wise.
Can I update the code in the units so they all accept the same configuration?
Updated by Mark Banks over 8 years ago
See my issue report on the UV-5X. Not sure if it is related but two new UV-5X would not hook and I have an older UV-5R that I confirmed my hardware with. After using the OEM Baofeng VIP s/w to read and write, CHIRP (0.4.1, ignore the issue report of 0.4.0) was able to read / write to the radio. A full reset of the radio did not effect CHIRP's ability to read / write. Is it possible factory new radios have an issue with CHIRP that can be solved by a read / write with OEM s/w ? Not sure....
Updated by Ed Beers over 8 years ago
Mark, This is probably unrelated as I never even attempted to use an SW other than CHIRP to access my units.
Updated by Jim Unroe over 8 years ago
Ed,
No, the firmware of Baofeng radios cannot be changed.
Save the channels from one radio as the "master image" (*.img). Then use the CHIRP Import feature to import the "master image" into the other 3 radios.
Jim KC9HI
Updated by Bernhard Hailer almost 4 years ago
- Status changed from Feedback to Closed
- Model affected changed from Baofeng uv-82 to Baofeng UV-82
No more traffic on this ticket.