I will try to amplify David's response by explaining just what is
going on with the memory files and why it needs to done the way
it is.
FTBasic enables you to modify the memories in the FT-817 by using
a feature of the rig that was designed for another purpose - to
copy or 'clone' the setup of one rig to another.
To do this, FTBasic pretends to be another FT-817, and receives a
complete copy of the status of the source rig, memories and all,
when the Read FT817 button is clicked. These files can be saved to
disk with a .817 file suffix for subsequent reloading.
Likewise, when you write back the memories to the FT817, it is not
just the 200 memories you have just been amending that gets sent
to the target FT817 - it is the complete status of the rig that
you used to retrieve the memories in the first place.
Because FTBasic has to deal in 'complete' images from/to the rigs
it needs the 'other' information about the rig to import the CSV
memories into. Because of this, it refuses to Import a CSV file
until it has a set of the 'other' data to merge the memories to.
This is why the Import/Export buttons are greyed out until you
have a valid complete rig image (which may be acquired direct from
the rig, or from a previously saved image).
I hope this helps.
Bob G4HFQ
