Campbell Scientific LoggerNet Datalogger Support Software - Manual (Page 148)

Section 5. Real-Time Tools
5.1.5.2 CR200 Series Programs
Programs for the CR200 Series dataloggers must be precompiled before being
sent to the datalogger. The compiled file is a binary image file with a *.bin
extension. Unlike the other dataloggers, CR200 Series dataloggers do not have
an on-board compiler. Consequently, the *.bin file must be generated with a
version of the precompiler that matches the operating system in the datalogger,
either during program creation in the CRBasic Editor, or when the file is
downloaded to the datalogger by LoggerNet. If a *.bin file is downloaded to a
CR200, and the version of that binary file does not match the datalogger’s OS,
the download will fail and an error will be returned.
The LoggerNet installation includes all of the compilers for the CR200 that
were available at the date of release. When sending a program, if you choose
to send the *.CR2 file, LoggerNet will first check the OS version of the
datalogger and then attempt to compile the *.CR2 file with the matching
compiler. If you choose to send the *.bin file, LoggerNet will not check the
CR200’s OS or precompile the file, it will just send the *.bin file. In this
instance, it is up to you to ensure that the *.bin file was created with the correct
precompiler.
5.1.5.3 Retrieving Datalogger Programs
The program running in the datalogger can be retrieved and saved to a file by
pressing the Retrieve button. You will be prompted for a name and directory
in which to store the retrieved file. Files for the CRBasic dataloggers (e.g.,
CR1) can be opened directly in the CRBasic Editor. A retrieved *.dld file can
be imported into Edlog for editing by using Edlog’s Document DLD feature
(Section 7, Creating and Editing Datalogger Programs). The binary image files
(*.bin) for the CR200 Series dataloggers cannot be retrieved.
This feature is useful if the original file has been corrupted, lost, or erased.
Note that programs may not be reliably retrieved over noisy or slow
communications links.
5.1.6 Program Association
A table-based datalogger maintains final storage table information internally —
this is referred to as the datalogger’s table definitions. The LoggerNet server
uses this information for the Add dialog box when you select values to view on
a Numeric or Graphical display and for the LoggerNetData applications.
Mixed-array dataloggers do not store final storage information internally.
However, this information is contained in the *.dld file as commented text.
When you download a program to a datalogger, LoggerNet uses the input
location and final storage information from this file. If you communicate with
a datalogger that already has a program in it, you can use the Datalogger |
Associate Program option to select a *.dld file from which LoggerNet should
get this information. A program file can also be associated with a datalogger
from the Setup Screen’s Program tab.
Programs created with Edlog version 2.0 and greater include both the input
location information and the final storage information in the *.dld file.
Previous versions of Edlog stored only the input location information in the
*.dld. If final storage information is not available for viewing in LoggerNet
5-12