TABLES OF FREQUENCIES & TONES
Frequently the required channel
information (frequencies and CTCSS tones) is already available in a
tabular form. To alleviate the tedium and risk of errors
associated with re-entering this information into the programming
software, we have incorporated a direct import facility.
Due to the multiplicity of file
formats and their ever-morphing nature, the decision has been made to
limit the importing to one type - comma separated variable (CSV).
The main menu selection "Load Buffer
from Binary File" is employed. If the file is not
recognised as a
proper binary file, a dialogue box asks if it is a CSV format
file. If it isn't, file processing is aborted. If the file
is a CSV format and structured as required, the data will be
imported. Note that before processing the file data, the user is
required to identify the target radio so that a proper interpretation
can be made. The data can then be viewed/edited via the main menu
Contents” selection as if it had been directly
entered on the edit form.
If the available tabular data is in a
formatted file such as a Microsoft Word table, it is suggested that
this should be imported into Excel (or a similar spreadsheet) and the
columns "massaged" to fit the structure detailed below before saving as
a .CSV file.
If the data does not match the
specified radio type/band and these requirements, the import process is
To be recognised as a valid file, the
CSV file MUST be structured as follows:
1. Column order:
#, Tx frequency, Rx frequency, Tx tone, Rx tone
- OR -
#, Rx frequency, Tx
frequency, Rx tone, Tx tone
(Frequencies MUST be in MHz)
2. A header row
column (channel #): must start with "c" or "C"
Second column: must start with "T" or
"R" to indicate which of the above column orders are to be used for
3. Each row which
has a channel number MUST have data in all columns, whether zero or
not, as this drives the comma presence on each line of data.
4. Each channel's data is represented
by one line in the CSV file, being the five fields above separated by a
comma and terminating in a <CR><LF>.
5. If a channel is not programmed, it
does not need to appear in the file. See the following sample file:
which imports as
Mismatch between CSV file frequencies and selected frequency band.
the data does not fit the band, importing will fail and a blank table
Amateur band frequencies.
are supported as normal. For example, with a CSV file containing
frequencies in the 6 metre band and:
Be aware that (as always - see
Appendix 7) once Ham mode has been triggered, it remains active until
the program is closed.
- a selection of “66-88 MHz” is
made, the resulting import will presume a modified VHF mid-band radio
and show the radio type as “50-54 MHz”.
- a selection of “30-50 MHz”, the
import will presume a VHF low-band radio and show the radio type as “25-55 MHz”.
Column headers in the CSV file.
technically the MINIMUM required for import is the first two columns,
it is good practice to provide proper headers for all five
columns. This also ensures that the header line/row delivers the
correct comma count to the import routine.
File length issues.
importing has been implemented without any attempt to make the process
over-smart. The initial check of an input file is the length
(byte count). A binary (EPROM image) file will be 2048
bytes. If the byte count is NOT 2048, the user is asked if the
selected file is a CSV type. If the response is Yes it is tested
accordingly. If the response is No, the file is
not valid and the
entire file read process is aborted.
In the unlikely event that a CSV file
is exactly 2048 bytes, the user will not be asked a question but the
file read will fail with an “Invalid
File!” error message. In this event, you will need to
add/remove data from the CSV file to alter the byte count. This
can be as simple as adding an extra space or trailing zero.
This feature was introduced in Release
1.12 of the Z-273 programming routine, and is incorporated in the beta
release (0.99) for Z-350 . To check the latest
releases of our 70-1000X software, look here.
If you are a SkyLine 70-1000X owner and do not have the latest
releases, this probably means we have not been able to contact you via
email, so please contact us.