I got a few new GT3-TP spares, and programmed them with CHIRP as usual. Something's changed in the startup display at boot. I use two parameters under "Setting/Other Settings" to display my CHIRP version level and my call sign on boot:
Power-On Message 1 used to display on the 1st line Power-On Message 2 used to display on the 2nd line (both briefly on boot)
Now, neither works. "GT-3" displays on the 1st line "MARK III" displays on the 2nd line
And the 6+Power-On Message settings seem to also be ignored. They are also greyed out in CHIRP, cannot be changed.
Anybody BTDT? Got a remedy? I already jailbroke the new units with a hard factory reset.
On Mon, Oct 14, 2024 at 12:24 PM Ceferino Lamb via Users users@lists.chirpmyradio.com wrote:
I got a few new GT3-TP spares, and programmed them with CHIRP as usual. Something's changed in the startup display at boot. I use two parameters under "Setting/Other Settings" to display my CHIRP version level and my call sign on boot:
Power-On Message 1 used to display on the 1st line Power-On Message 2 used to display on the 2nd line (both briefly on boot)
Now, neither works. "GT-3" displays on the 1st line "MARK III" displays on the 2nd line
CHIRP will skip these fields during the upload if it is detected that the "aux" memory area in the uploaded image was from a different radio. In other words, the power message will not be updated if the uploaded image is not from the radio being programmed. What you must do is download from the radio that you want to edit the power-on message, edit the power-on message in this newly create tab and finally upload this tab back to the same radio that it came from.
If you have followed the process above and the power-on message does not update, then the radio itself no longer supports the editing of these fields. If this is the case, there is nothing that CHIRP can do (CHIRP can't make a radio do something that it doesn't support).
And the 6+Power-On Message settings seem to also be ignored. They are also greyed out in CHIRP, cannot be changed.
The ability to edit these fields have been remove from CHIRP for a long time in order to preserve the date that is contains (since it is very useful for troubleshooting)
Anybody BTDT? Got a remedy? I already jailbroke the new units with a hard factory reset.
Jim KC9HI
This is very interesting. I didn't know Boafengs had any unique ID associated with a unit.
Is it perhaps a firmware rev that is used, or is it really an unique ID?
I am programming some ICOM HTs for a friend and leaned that they transmit their unique ID with every trx. This "feature" may have been fatal to certain Lebanese recently.
On Mon, Oct 14, 2024 at 12:25 PM Jim Unroe via Users users@lists.chirpmyradio.com wrote:
On Mon, Oct 14, 2024 at 12:24 PM Ceferino Lamb via Users users@lists.chirpmyradio.com wrote:
I got a few new GT3-TP spares, and programmed them with CHIRP as usual. Something's changed in the startup display at boot. I use two parameters under "Setting/Other Settings" to display my CHIRP version level and my call sign on boot:
Power-On Message 1 used to display on the 1st line Power-On Message 2 used to display on the 2nd line (both briefly on boot)
Now, neither works. "GT-3" displays on the 1st line "MARK III" displays on the 2nd line
CHIRP will skip these fields during the upload if it is detected that the "aux" memory area in the uploaded image was from a different radio. In other words, the power message will not be updated if the uploaded image is not from the radio being programmed. What you must do is download from the radio that you want to edit the power-on message, edit the power-on message in this newly create tab and finally upload this tab back to the same radio that it came from.
If you have followed the process above and the power-on message does not update, then the radio itself no longer supports the editing of these fields. If this is the case, there is nothing that CHIRP can do (CHIRP can't make a radio do something that it doesn't support).
And the 6+Power-On Message settings seem to also be ignored. They are also greyed out in CHIRP, cannot be changed.
The ability to edit these fields have been remove from CHIRP for a long time in order to preserve the date that is contains (since it is very useful for troubleshooting)
Anybody BTDT? Got a remedy? I already jailbroke the new units with a hard factory reset.
Jim KC9HI _______________________________________________ Users mailing list users@lists.chirpmyradio.com https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com To unsubscribe, send an email to users-leave@lists.chirpmyradio.com To report this email as off-topic, please email users-owner@lists.chirpmyradio.com List archives: https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/
The exploding Icoms were a long-discontinued FM (analog) HT that had several unique features, like, you could add a d-Star board to or a DTMF decoder to it:
https://www.passion-radio.fr/fiches/icom/u82/u82-angl.pdf
https://m.jpost.com/middle-east/article-820735
Analog radios don't identify themselves with each transmission, the more likely cause of the explosion was a signal sent to all radios that activated the DTMF decoder in each radio.
I've not dug too deep into this story, but an in-band signal, broadcast across the region thru linked repeaters, seems the most likely method.
Ken
On Oct 14, 2024, at 14:59, Ceferino Lamb via Users users@lists.chirpmyradio.com wrote:
I am programming some ICOM HTs for a friend and leaned that they transmit their unique ID with every trx. This "feature" may have been fatal to certain Lebanese recently.
Meant to add this, the IC-V82 also has a pager function (pocket beep), see page 36 for more info:
https://lodiarc.org/members/wa6osx/IC-V82_U82_manual.pdf
That would seem the perfect remote detonation method...
Ken
On Oct 14, 2024, at 15:20, Ken Hansen ken@n2vip.org wrote:
The exploding Icoms were a long-discontinued FM (analog) HT that had several unique features, like, you could add a d-Star board to or a DTMF decoder to it:
https://www.passion-radio.fr/fiches/icom/u82/u82-angl.pdf
https://m.jpost.com/middle-east/article-820735
Analog radios don't identify themselves with each transmission, the more likely cause of the explosion was a signal sent to all radios that activated the DTMF decoder in each radio.
I've not dug too deep into this story, but an in-band signal, broadcast across the region thru linked repeaters, seems the most likely method.
Ken
On Oct 14, 2024, at 14:59, Ceferino Lamb via Users users@lists.chirpmyradio.com wrote:
I am programming some ICOM HTs for a friend and leaned that they transmit their unique ID with every trx. This "feature" may have been fatal to certain Lebanese recently.
Thanks Jim for the successful workaround. I also had go back in and set MR A, B channels manually, then upload to HT again. Oddly, VFO A, B were retained, but not MR.
But again, this only affects the latest batch of GT3-TP units I just bought. The previous 30 or so I've programmed with CHIRP are unaffected by this anomaly.
Thanks also for the PTT-IS tip. I didn't know that.
I didn't mean to start a thread here on the exploding ICOM HTs. I reckon that's been discussed plenty in RadioReference etc.
Reno K7CRL
On Mon, Oct 14, 2024 at 3:28 PM Ken Hansen via Users users@lists.chirpmyradio.com wrote:
Meant to add this, the IC-V82 also has a pager function (pocket beep), see page 36 for more info:
https://lodiarc.org/members/wa6osx/IC-V82_U82_manual.pdf
That would seem the perfect remote detonation method...
Ken
On Oct 14, 2024, at 15:20, Ken Hansen ken@n2vip.org wrote:
The exploding Icoms were a long-discontinued FM (analog) HT that had several unique features, like, you could add a d-Star board to or a DTMF decoder to it:
https://www.passion-radio.fr/fiches/icom/u82/u82-angl.pdf
https://m.jpost.com/middle-east/article-820735
Analog radios don't identify themselves with each transmission, the more likely cause of the explosion was a signal sent to all radios that activated the DTMF decoder in each radio.
I've not dug too deep into this story, but an in-band signal, broadcast across the region thru linked repeaters, seems the most likely method.
Ken
On Oct 14, 2024, at 14:59, Ceferino Lamb via Users users@lists.chirpmyradio.com wrote:
I am programming some ICOM HTs for a friend and leaned that they transmit their unique ID with every trx. This "feature" may have been fatal to certain Lebanese recently.
Users mailing list users@lists.chirpmyradio.com https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com To unsubscribe, send an email to users-leave@lists.chirpmyradio.com To report this email as off-topic, please email users-owner@lists.chirpmyradio.com List archives: https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/
On Mon, Oct 14, 2024 at 3:58 PM Ceferino Lamb via Users users@lists.chirpmyradio.com wrote:
This is very interesting. I didn't know Boafengs had any unique ID associated with a unit.
I didn't say anything about an ID. I am talking about firmware versions.
Is it perhaps a firmware rev that is used, or is it really an unique ID?
The firmware version used to get bumped every time a new firmware was released. Not everything just gets a BFB298. In other words, you may have two radios that identify has having BFB298 firmware but in reality the firmware may not be the same.
These radios can transmit a PTT-ID. However, they are programmed by the user and are not necessarily unique. There can be up to 5 characters of comprised of a character set of 12 DTMF signals plus {blank} (13^5 = 371,293 combinations).
participants (3)
-
Ceferino Lamb -
Jim Unroe -
Ken Hansen