CHIRP

Hi Dave,

daily-01062012 is a couple months old at this point. Can you test the latest daily build and see if the behavior remains? There is another 8800 user (the driver is nearly identical) that seems to think that everything is working fine these days.

Make sure that you do the full import again with the new driver, as only touching the memories will cause any new code to run.

If you still experience issues, I'll need to know which memories specifically and which attributes don't get set properly, as well as have a copy of the CSV file you're using.

Thanks!

I have just replicated the problem using daily-02292012.

I have attached the csv file I am tying to upload, also the image that has "gone wrong" (in case it is useful).

As far as I can see the problems are with locations 19, 20 and 24. 19 and 20 should be 145.737500 (now 145.730000) while 24 should be 145.7875 (now 145.780000). I believe all other entries to be perfect. This is consistent with the previous versions I have tried.

Thank you.

I think my thinking was coming from the other end - that the radio is breaxking rather than fixing something. Either way, I got somewhat muddled up with my files and sent you something incomprehensible - sorry about that!

Attached are the two files you asked for. An initially uploaded one, and downloaded one following the editing of a single memory, which in this case is location 24. I copied the memory to VFO, changed the incorrect frequency of 145.780000 to 145.787500, saved it back to location 24 and manually entered the name GB3KD (the same as it was written by CHIRP).

I hope that is correct and hope it helps - thank you for your efforts.

Cool, thanks, got it fixed!

If you're on Linux, you can grab a snapshot of the repository and test this before the daily comes out. If you could do this, that would be great so I can get going on making a formal release.

http://d-rats.com/hg/hgwebdir.cgi/chirp.hg/archive/tip.tar.gz

Thanks!