[chirp_users] Issue with latest build and Baofeng GT-3TP
I updated today and made a minor mod to my HT, lowering default tx power on one of my stored freqs. That failed to store the mod on HT, no error msg. Tried twice. Failed.
Then back in the truck I found that I could no longer hear other HTs in our convoy. So I reset the HT, uninstalled the latest CHIRP build on my w10 box, went back to daily-20201014, re-uploaded file to HT, and all is working fine again.
On Wed, Nov 25, 2020 at 10:36 PM Ceferino Lamb ceferino.lamb@gmail.com wrote:
I updated today and made a minor mod to my HT, lowering default tx power on one of my stored freqs. That failed to store the mod on HT, no error msg. Tried twice. Failed.
Then back in the truck I found that I could no longer hear other HTs in our convoy. So I reset the HT, uninstalled the latest CHIRP build on my w10 box, went back to daily-20201014, re-uploaded file to HT, and all is working fine again.
-- K7CRL Quis custodiet ipsos custodes?
The way CHIRP uploads a full "memory blob" to the radio, there should be no difference between uploading the same "image" using the current daily buld and the 20201014 daily build.
Jim KC9HI
What you say makes sense to me. But the events unfolded as described, and backing up to previous release 20201014 apparently resolved the issue. FYI
On Thu, Nov 26, 2020 at 7:10 AM Jim Unroe rock.unroe@gmail.com wrote:
On Wed, Nov 25, 2020 at 10:36 PM Ceferino Lamb ceferino.lamb@gmail.com wrote:
I updated today and made a minor mod to my HT, lowering default tx power
on one of my stored freqs. That failed to store the mod on HT, no error msg. Tried twice. Failed.
Then back in the truck I found that I could no longer hear other HTs in
our convoy. So I reset the HT, uninstalled the latest CHIRP build on my w10 box, went back to daily-20201014, re-uploaded file to HT, and all is working fine again.
-- K7CRL Quis custodiet ipsos custodes?
The way CHIRP uploads a full "memory blob" to the radio, there should be no difference between uploading the same "image" using the current daily buld and the 20201014 daily build.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Reno Lamb at ceferino.lamb@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Thu, Nov 26, 2020 at 2:30 PM Ceferino Lamb ceferino.lamb@gmail.com wrote:
What you say makes sense to me. But the events unfolded as described, and backing up to previous release 20201014 apparently resolved the issue. FYI
Nothing has been changed in the CHIRP uv5r.py driver module since 20201014 that would cause this. I think that if you tried the latest version again, you would see that it would work just fine. You don't even have to mess with your current installation. Just download the ZIP version and extract it to a convenient place. Then just double click the "chirpw.exe" file to run this version separate from your installed version. Handy if you want/need to have multiple versions available for testing (or to test the new version before affecting your installed version).
Jim KC9HI
participants (2)
-
Ceferino Lamb -
Jim Unroe