System information
Section 4. The CR1000 Type Datalogger
4-6
files, and start the new program on the datalogger. Check the File Control
Response. If the RespCode returns a zero, determine the amount of time to
wait as declared in the HoldOff parameter and wait at lest that amount of time
before continuing the process. Otherwise, report and act on the error message.
Send the Get Programming Statistics transaction and obtain compile results to
verify the new datalogger program information. Since the datalogger is
compiling the program and allocating table space, the application may need to
wait for this response. The datalogger will send a Please Wait message if a
delay is going to occur.
Once the application verifies that the datalogger has properly compiled and is
running the new program, table definitions can be retrieved and used by the
application.
4.7.1 Interpreting the Response
After the datalogger program has been sent to the CR1000 type datalogger, the
application should anticipate a File Download Response message. The
response code within this message indicates the next action the application
should attempt. Possible response codes include: complete (0x00), permission
denied (0x01), insufficient resources or memory full (0x02), invalid fragment
number (0x09), invalid file name (0x0d), and file is not currently accessible
(0x0e).
4.7.2 Handling Rejection
When everything goes as planned, the datalogger indicates the program was
sent successfully with a response code of “complete”. However, if a problem
occurs when sending a program, the datalogger will indicate the nature of the
problem with a different response code.
For example, a “permission denied” message indicates that security is enabled
on the CR1000 type datalogger and an improper security code has been sent to
the datalogger. The application should prompt for and send the correct security
code. Additionally, the CR1000 type datalogger can store multiple programs
and files so an “insufficient resources or memory full” response code requires
the application to use the File Control transaction to remove existing programs
or files and make room for the new program.
Finally, the application must determine how long to wait before discarding a
transaction and retrying the packet with a new transaction number when a
command has been sent but a response hasn’t been received. The expected
latency varies across different communication mediums but the application
should be aware of this variability and set the maximum retry interval
accordingly.
4.7.3 Erasing Files on the CFM100
The CompactFlash™ Module of the CR1000 and CR3000 provides additional
storage for data, programs, and files. The File Control transaction can
administer and delete files from the CFM100 in the same manner as deleting
files from datalogger memory but by specifying a file and location on the
memory card instead of a file and location in the datalogger memory.