Hi Jan,
- the memory names are not populated in CHIRP's display.
Just to be sure, you are using 0.1.11b7, right? I think this was fixed already for the F6A in a previous beta.
Did you do a from-source install previously and maybe now are running directly from the source tarball? That could be part of the problem. I'd either do an install of this one to overwrite the old one, or clean out the files installed in the rest of the system so you know that you're running the current version.
- when trying to set a new (previously empty) memory, entering a new value for the frequency results in this message:
This might be related to the above as well. Are you able to make changes to existing memory channels?
Note that the driver seems to think it's talking to a D7, but I've really got an F6.
That's just the debug code being silly, it wouldn't be getting this far if it didn't know it was an F6A :)
When you try the above, if it still doesn't work, it would be helpful to see the whole debug log. If you're running from the command line, something like:
./chirpw >file_for_dan.txt 2>&1
would work.
I went back to 0.1.10 to see if it could read my radio, but it came back with no memories populated (trying to read as a D7 as it didn't have a generic Kenwood or F6 option).
Yeah, 0.1.10 didn't support it at all.
Thanks!