Bug #11493
openI can not connect to Chirp after I upgraded to the new Chirp.
0%
Description
(Describe what you were doing) conecting my radio to chrip
(Describe what you expected to happen) chirp to see my radio
(Describe what actually happened instead) it didnt
Files
Updated by Jon Gillingham 3 months ago
- File config.txt config.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20240821]
Updated by Andrew B 3 months ago
Jon Gillingham wrote:
(Describe what you were doing) conecting my radio to chrip
Experiencing a similar issue - "Radio did not respond" - on BaoFeng BF-F8HP (UV-5R 3rd Gen) - on upload as well using next-20240821. Rolling back to next-20240814 restored the functionality.
Updated by Dan Smith 3 months ago
@Andrew B Your BF-F8HP is different from the UV-5G Plus described in this bug. I can't explain why you would experience a difference between 0814 and 0821 with that radio since nothing has changed, but it sounds like you should open a new bug (with a log containing a reproduction on the current version) so we can have a look.
Updated by Dan Smith 3 months ago
Also, @Jon Gillingham -- you said your radio is a "Baofeng UV-5G Plus" but your debug log shows you chose "Radioddity UV-5G Plus". These are not the same radio. Which do you really have? For the baofeng, you should be choosing this per the list on the front page:
Baofeng ... UV-5G Plus (use Baofeng GM-5RH)
So do you have the Radioddity or the Baofeng?
Updated by Jon Gillingham 3 months ago
I have the Baofeng uv 5g plus. I will try GM- 5RH. Recovering from shoulder
surgery so it might take a few days. Thanks
On Fri, Aug 30, 2024, 2:14 PM Andrew B redmine@chirpmyradio.com wrote: