5.3.1 CSDATA
This directory contains all the instrument data created by the shell command SAVECS. Where
there are the following 4 files.
5.3.1.1 CONFIG.BIN
This file contains a binary copy of the instrument FRAM. It is only compatible with software of
the same version.
5.3.1.2 CONFIG.CAL
This file keeps a copy of the instrument calibration data as a text file which can be loaded back
into the instrument by either using LOADCS or by pasting to a terminal at the shell.
5.3.1.3 CONFIG.CSV
This file keeps a copy of the Modbus address to register mapping as a CSV file which can be
loaded back into the instrument by using LOADMODBUSCSV.
5.3.1.4 CONFIG.TXT
This file keeps a copy of the instrument registers as a text file which can be loaded back into
the instrument by either using LOADCS or by pasting to a terminal at the shell.
5.3.2 IMAGES
This directory has a binary image of the application (APPLICATION.IMG) and bootloader
software (BOOTLOADER.IMG). This can be reprogrammed using the normal software programming
methods if required.
5.3.3 SYSTEM
This is a full copy of the entire system directory.
5.4 Batch Directory
The data for each given batch is stored under the path /YEAR/MONTH/DAY/BATCHNAME/ folder. So,
assume the date is June 30
th
, 2010 and we have both the batch title and batch id prompts turned on as prompts
during the start sequence of a batch/blend. When prompted for the title, we enter ‘BATCHNOW’ and when
prompted for the ID we enter ‘876’. If you navigate to the year and month in the batch path directory and type the
DIR command you will see that a batch folder has been created called ‘BATCHNOW_876.1’:
The .1 extension is taken directly from the register ‘I_TOTAL_BATCH_COUNT’. This is the total
number of batches that have been run since the registers were last defaulted.
Within the batch folder itself you should see the following files listed:
To Next Page
Loading...
Need help?
General
