[chirp_users] ctcss tones written wrong? (ft-817nd)

[ag6eb at limpoc.com]

Hi,

I've just gotten a FT-817nd and started playing around with it using Chirp. 
Everything is looking great except one problem.  It looks like if I create a 
memory entry with a CTCSS tone setting and it is written to a previously empty 
channel, when looking at that channel on the radio I will see a random 16 bit 
number (ie, 26654) instead of a formatted tone value (like "77.0"). (they 
don't appear to match; three channels all set to a 100.0hz tone will show 
three different random-looking numbers on the radio.) It does not transmit a
correct CTCSS tone. There don't appear to be any other data errors.  

If I overwrite the value using the radio, it then works fine. If I clone the
radio to Chirp and then write it back immediately, the values are all still
good, but I don't know if this is because it already contains valid contents
or because i'm now writing valid contents. 

Fwiw I am using debian linux and the daily build package from the apt repo, 
but the same thing appears to happen with the 0.2.2 tarball from the site. 
Further info: it is a recent-ish US model that's been MARS modded (no special
channels) and thus I am using the "FT-817ND (Intl versions)"  instead of the
US version hardware type. 

Anyway, I'm happy to try any suggested experiments or provide any further info
if it would help. I also have a paid copy of FTBasicMMO which does write tones
correctly, for comparison, but i'd much prefer to keep using chirp. 

thanks for a fine piece of software!
eric