CHIRP

This is usually an indication that one or more of the radio's settings is/are out-of-range. Attach a CHIRP Radio Images (*.img) file so it can be determined which setting(s) that might be.

Jim KC9HI

Image file as requested...

Conrad Aquino wrote:

Image file as requested...

Thanks. The Intro Line 1: with your callsign was padded with nul (0x00) characters. I changed them to spaces (0x20). I edited the field several times with CHIRP and the field was always padded to the full 15 characters with spaces. I don't know how they got changed to null characters to begin with, unless perhaps it was done with another programming software?

Jim KC9HI

Conrad Aquino wrote:

Jim... thanks so much for the fixed image file. There is a possibility that in a senior moment, I inadvertently used the QRZ-1 Programmer (RT Systems) software that came with the radio, instead of CHIRP for an update... I'll be sure to be more careful and not do that again.

That makes sense. RT Systems has apparently decided to pad the characters to the right of the Intro Lines as null characters. There is nothing wrong with that as long as the radio supports it (and it apparently does).

The cousins of the QRZ-1 (TYT TH-UV88 and Retevis RT85 come from the factory with the Intro Lines padded with spaces so that is what the CHIRP driver was developed to support.

Now that it is known that there is a potential for null characters to be in the intro lines, it makes sense to give CHIRP the capability of gracefully handling them when they are present.

I will see if I can make the changes necessary to bring this about.

Jim KC9HI

Patch submitted. Support will be in the next CHIRP daily build following acceptance.

Jim KC9HI

Applied in changeset commit:e66b9303f0c1.