[Question] Identify the units that have the problem with the transmit power calibration. about uvmod HOT 6 CLOSED

How do you tell which firmware is preinstalled? As far as i know the version string is nowhere on the radio.

I am currently working on a uvmod configurator tool (to do channels etc on the website without the need for software). Since this tool will have access to the eeprom, it can also easily identify radios that have the txpower bug, and ill display a little info banner.
Affected radios have one or more negative calibration values and the bug is that v26 does not properly treat negative values.

So far we dont have a mod to patch the bug in v26 but i am sure someone will do it soon enough.

from uvmod.

Will be added with the upcoming configurator feature

from uvmod.

How do you tell which firmware is preinstalled? As far as i know the version string is nowhere on the radio.

The radio send back the firmware version when you send the right command througt data cable so there are some ways to get the firmware version from the radio, like Python lib libuvk5 , or just by reading configuration with chirp software or with the official tool.

I am currently working on a uvmod configurator tool (to do channels etc on the website without the need for software).

Great news, I'm looking forward to it !

Since this tool will have access to the eeprom, it can also easily identify radios that have the txpower bug, and ill display a little info banner.

We should even be able to find this information in an img file made with chirp if we know where to look because it is an EEPROM dump.

Affected radios have one or more negative calibration values and the bug is that v26 does not properly treat negative values.

So far we dont have a mod to patch the bug in v26 but i am sure someone will do it soon enough.

If I understand correctly, v27 should work in all cases, wouldn't it be simpler to base the mods on this version? (Probably easier said than done if it is not the way that was chosen...)

from uvmod.

I found the version command and the way it works, the radio has the firmware version hardcoded in the function that replies to the 0x14 command when reading eeprom. I will be able to show the version in configurator. Oddly enough this has nothing to do with the version string found in the encoded firmware, because that never gets stored by the radio.

Right now I am implementing a .uvbk file format which is just the raw full eeprom with a crc16 appended to it. If the chirp format is close enough I can support that as well for import, which would automatically also work with the bug check. I am a little wary to support generic file formats such as .img though, since people could accidentally overwrite sensitive data with garbage by choosing a random file.

UVMOD is on v26 since the uvmod kitchen is, making it easy to transfer new mods. We do have most mods for v27 now so I could move everything to v27, although it seems like more effort than just making a mod that implements signed divide correctly. But after looking at the firmware I can see why nobody did it yet, it is a bit of a mess with multiple sections to be patched and amended.

from uvmod.

Thank you, this feature has a lot of value and will make a difference with existing configuration tools.

from uvmod.

Right now I am implementing a .uvbk file format which is just the raw full eeprom with a crc16 appended to it. If the chirp format is close enough I can support that as well for import, which would automatically also work with the bug check. I am a little wary to support generic file formats such as .img though, since people could accidentally overwrite sensitive data with garbage by choosing a random file.

I just opened a Chirp image with a hexadecimal editor and it got me thinking about this conversation again, here's what I saw if it's helpful...
The Chirp image is also a complete dump of the eeprom with additional data starting from address 0x2000
This data starts with "00 FF 63 68 69 72 70 EE 69 6D 67" i.e. "**chirp*img", which may be a good test to prevent messing around with random img files.

from uvmod.