The CR800 is a smaller, research-grade datalogger designed for stand-alone operation in harsh, remote environments. It is intended for smaller configurations in which fewer sensors will be measured. Each CR800 reads input from sensors, then transmits the data via a communication peripheral; most sensors and telecommunication devices are compatible. Multiple CR800s can be configured as a network or units can be deployed individually.
Another datalogger, the CR850, is similar to the CR800, but it has an integrated keyboard and display screen for on-site control.Read More
The CR800 consists of measurement electronics encased in a plastic shell and an integrated wiring panel. This datalogger uses an external keyboard/display and power supply. Low power consumption allows the CR800 to operate for extended periods on a battery recharged with a solar panel—eliminating the need for AC power. The CR800 suspends execution when primary power drops below 9.6 V, reducing the possibility of inaccurate measurements.
The on-board operating system includes measurement, processing, and output instructions for programming the datalogger. The programming language, CRBasic, uses a BASIC-like syntax. Measurement instructions specific to bridge configurations, voltage outputs, thermocouples, and pulse/frequency signals are included. Processing instructions support algebraic, statistical, and transcendental functions for on-site processing. Output instructions process data over time and control external devices.
|-NOTE-||Note: Additional specifications are listed in the CR800-Series Specifications Sheet.|
|Operating Temperature Range||
|Analog Inputs||6 single-ended or 3 differential (individually configured)|
|Voltage Excitation Terminals||2 (VX1, VX2)|
|Switched 12 Volt||1 terminal|
|Input Limits||±5 V|
|Analog Voltage Accuracy||±(0.06% of reading + offset) at 0° to 40°C|
|Power Requirements||9.6 to 16 Vdc|
|Real-Time Clock Accuracy||±3 min. per year (Correction via GPS optional.)|
|Internet Protocols||FTP, HTTP, XML POP3, SMTP, Telnet, NTCIP, NTP|
|Communication Protocols||PakBus, Modbus, DNP3, SDI-12, SDM|
|Idle Current Drain, Average||0.7 mA (@ 12 Vdc)|
|Active Current Drain, Average||
|Dimensions||24.1 x 10.4 x 5.1 cm (9.5 x 4.1 x 2 in.)|
|Weight||0.7 kg (1.5 lb)|
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
|LOGGERNET||(Version 3.3 or higher)|
|PC400||(Version 1.4 or higher)|
|PCONNECT (retired)||(Version 3.3 or higher)|
|PCONNECTCE (retired)||(Version 2.2 or higher)|
|VISUALWEATHER||(Version 2 or higher)|
With several channel types, the CR800 is compatible with nearly every available sensor, including thermocouples, SDI-12 sensors, and 4 to 20 mA sensors. A custom ASIC chip expands its pulse count, control port, and serial communications capabilities. The CR800's I/O ports can be paired as transmit and receive, allowing serial communications with serial sensors and devices.
The CR800 is compatible with all of our CDMs (requires an SC-CPI), SDMs, multiplexers, vibrating-wire interfaces, terminal input modules, and relays.
The CR800 communicates with a PC via direct connect, NL201 Ethernet Interface, multidrop modems, phone modems (land line, digital cellular, and voice-synthesized), RF telemetry, and satellite transmitters (Argos, Iridium, and Inmarsat.
Data can be viewed on the CR1000KD Keyboard Display, CD100 Mountable Display with Keypad, user-supplied iOS or Android device (requires LoggerLink), CD295 DataView II Display, or a user-supplied PDA (PConnect or PConnectCE software required).
The SC115 is the only compatible external data storage device. The CR800 does not have a peripheral port and is therefore not compatible with the CFM100, NL115, or NL120.
The CR800 and its power supply can be housed in any of our standard enclosures.
Any 12 Vdc source can power the CR800 datalogger. Power supplies commonly used with the CR800 are the BPALK, PS150, and PS200. The BPALK provides eight non-rechargeable D-cell alkaline batteries with a 7.5 A h rating at 20°C.
Both the PS150 and PS200 consist of a sealed rechargeable 7 A h battery and a charging regulator. Their battery should be connected to a charging source (either a wall charger or solar panel). These two power supplies differ in their charging regulator. The PS150 has a standard regulator and the PS200 has a micro-controller-based smart regulator. The PS200's regulator provides two-step constant voltage charging and temperature compensation that optimize battery charging and increases the battery’s life.
Also available are the BP12 and BP24 battery packs, which provide nominal ratings of 12 and 24 A h, respectively. These batteries should be connected to a regulated charging source (e.g., a CH100 or CH200 connected to a unregulated solar panel or wall charger).
CRBasic, the CR800's full programming language, supports simple or complex programming and many onboard data reduction processes.
Execution of this download installs the CR800 Operating System and Compiler on your computer. It also updates the CR800 support files for the CRBasic Editor.
Note: This OS has crossed the 2 Meg CR800 size limit for remote download. The OS must be downloaded to the 2 Meg CR800 via direct connect with the Device Configuration Utility. All OS download methods are supported by the 4 Meg CR800.
Upgrading from versions prior to version 28 of the Operating System will reset the datalogger’s CPU drive. This is due to a change in the format of the file system from FAT16 to FAT32. In order for the datalogger to operate correctly, as part of the upgrade, the CPU drive is formatted to FAT32. Any programs stored and running from the CPU drive will be lost. It is not recommended to update the datalogger’s Operating System over a remote connection where program control regulates the communication equipment (turning it on or off, etc.). In these cases, an on-site visit and a backup using DevConfig’s backup utility is necessary to update the datalogger’s Operating System.
In all cases where the datalogger is being updated from an Operating System prior to 28, the use of DevConfig’s backup utility is recommended due to the CPU drive being formatted using the new FAT32 format.
A software utility used to download operating systems and set up Campbell Scientific hardware. Also will update PakBus Graph and the Network Planner if they have been installed previously by another Campbell Scientific software package.
Supported Operating Systems:
Windows 10, 8.1, 8, and 7 (Both 32 and 64 bit)
Number of FAQs related to CR800: 147
Expand AllCollapse All
The internal file storage on the datalogger has limits on the size, quantity, and name length of files. The file name of the new file may need to be shortened, or some older files may need to be deleted using File Control.
The time to fill the datalogger memory depends on the following:
For the older array-based dataloggers, the time to fill the memory is determined by multiplying the number of values by the number of bytes needed to store them. Most values were stored as either two bytes or four bytes. This result is multiplied by the number of scans per minute to get the number of bytes per minute. To get the time to fill, divide the amount of memory in the storage area by the number of bytes per minute.
For newer dataloggers, such as the CR10000, the easiest way to determine the time limit is to load the program and let the datalogger make the calculation. This information can be found in the program details. (For help with this, see the "Details, Details, Details!" article.) As another option, in LoggerNet, this information may be viewed in the Status table where each data table in the program is assigned a field called DataFillDays, or in the Table Fill Times tab of Station Status in the Connect screen. The time limit may also be viewed in the main screen of PC400 and PC200W. These options work well for data that is written to the data table based only on time.
For data tables that store data based on some condition other than time, the datalogger is not able to estimate how often the condition will occur. The datalogger assumes the worst case scenario, which is that data will be written to conditional tables every scan. The result is that the DataFillDays field may show a conditional table filling in minutes or hours, when in reality the condition that triggers data storage is rare and the table will never be filled. This is why it is important to define the table size for conditional data tables to a specific number of records rather than allowing the datalogger to auto-allocate table size. Auto-allocation should only be used for data tables that store data based only on time.
For more information, see the Data Table Memory Allocation Tutorial.
If the mistake is caught quickly and the 24 Vdc power source is removed before the surge protection fails, apply the 12 Vdc power source and continue. If a 24 Vdc power source was applied for an extended period, the surge protection will fail and the datalogger will have to be returned for repair.