/-------------------------------\
| Saved Memory Bank File Format |
\-------------------------------/

When a memory bank is downloaded from the scanner via the dump command, it is
saved in a plain text file that can be read and uploaded back to the scanner
via the load command.  These data files can be used by any scanner supported by
the sctl program.  Furthermore, the file is not bank-specific -- a download
from one bank can be uploaded to any other bank on the scanner.  Any existing
data in a bank is erased when data is uploaded over it [1].

The first line of the file will be "version" followed by a number.  This is the
version number of the memory bank file format.  The current version is "1"

The next part of the file consists of six columns of data, with each row
holding the data for a single frequency.  No file may have more than 30 rows of
frequency data, since a single bank on the scanner can only hold 30
frequencies.  Each column is separated by a single space as follows:

frequency trunk delay lockout autorec ctcss

Frequency - stores the frequency (divide by 10000 to get the frequency in MHz)
Trunk - F for false, N for true (saved, but not restored)
Delay - F for false, N for true
Lockout - F for false, N for true
Autorec - F for false, N for true (saved, but not restored)
CTCSS - ctcss tone frequency, or 0 if none (saved, but not restored)

In the future, a seventh column may be added to support alpha tags, but this
feature is not currently implemented.  The BC780XLT has alpha tag support built
into the scanner itself, but other models do not.  We would like to provide
"virtual alpha tags" for scanners that don't have them.

The final section of the file (starting at line 32) will contain data on
talkgroups, for trunked banks.  This feature hasn't been implemented yet.

Another problem is that trunked bands are currently recorded as being trunked,
but when they are uploaded they are not set on the scanner as being trunked.
Obviously, this part of the program still needs to be written.  The same goes
for Autorec and CTCSS.  "We're working on it."

Until this file format grows beyond the experimental stages, it is not
recommended that you dump/load trunked banks using it.

Footnotes:
1. Currently Trunk, Autorec, and CTCSS flags are -not- erased when new data is
uploaded over their frequency.

FF Changelog:
version 1 - original file format
