[chirp_devel] Bug 937: FT-857D crashes due to problematic channel

Robert Terzi
Wed Jun 26 07:26:12 PDT 2013


On 6/26/2013 2:37 AM, IZ3GME Marco wrote:

> Can you please confirm that creating a short memory label on the radio
> itself fires up the bug?

I haven't found a way to create a label on the radio that isn't space padded
out to 8 characters.

It looks like it's the 0xff appearing in the 5th byte that triggers the bug
on my radio.

Note: the radio creates a default label of CH-NNN (6 chars) that you have to
change to spaces if you have less than 6 chars.  (In my tests, the 7th and 8th
bytes were spaces even though they weren't touched.)
  
I'm told FTBasicMMO (G4HFQ's software for the ft-8x7) has always space padded to 8 chars.

> FYI on my early FT857 I have many memories labels of 2,3 and 4
> characters and I never had a problem, this issue must be limited to only
> some production batches.

But are they space padded, or filled out with 0xff?

In your patch, the implied field names in the format strings won't work on Python
versions < 2.7.  Specifying field 0 will allow it work on Python 2.6

     Change '{<:5}' to '{0:<5}'


Thanks for your help,
--Rob






More information about the chirp_devel mailing list