CHIRP

I have a Jetstream JT270M. I am using the 2015-06-22 daily build on NetRunner Linux 14.0. The behaviour I am about to describe also happens with the 2015-06-07 daily build.

On initial use, I was able to read the out-of-the-box config from my radio into CHIRP and save it as an image file. I can read that image file back without issues.

Lately, however, now that I have actual content in my images, I can't read them back. Once read back, the config displayed shows frequencies well out of range of what my radio can do (frequencies in the neighbourhood of 1666 MHz, 890 MHz, etc).

Additionally, the console output complains mightily about CTCSS tones. I noticed that this radio implements 58 CTCSS tones, but that CHIRP only supports the more-standard 50. It also seems that this radio defaults to one of the lower-than-normal tones and I think this is causing exceptions that may, in turn, cause misreads of the image file.

I can read the config from the radio without issue. I can also write it back. I don't have any idea if the image file itself is valid or not, i.e. whether it is corrupted on write or corrupted on read.

The program appears not to have produced a debug log, however, I've attached the console output. I have also attached the image file.