The CR216X is a small, low-cost datalogger that includes an internal 2.4 GHz spread-spectrum radio for transmitting data to another CR216(X), an RF416 radio, or RF432 radios. The 2.4 GHz frequency can be used worldwide.
The CR216X provides stand-alone operation in harsh, remote environments. It reads input from one or two sensors, then transmits its data wirelessly via its internal radio. Multiple CR216Xs can be configured as a network, or units can be deployed individually.
The CR216X can be used in a wireless sensor network. Wireless sensor networks are appealing because they are often more economical than trenching, laying conduit, and pulling wire. When used as a wireless sensor, the CR216X measures the sensors attached to it, then transmits its data wirelessly via its spread-spectrum radio to a master datalogger. The master datalogger must use the PakBus communication protocol (e.g., CR800,CR850, CR1000, CR3000). For more information on how to configure a PakBus system, please read our PakBus Networking Guide.
The CR216X has several input channels for measuring a variety of sensors. Gas discharge tubes provide rugged electrostatic discharge protection for the inputs.
The CR216X does not make differential measurements and is not compatible with SDM devices, multiplexers, or thermocouples. (Refer to the Compatibility information on the web page for compatible sensors, peripherals, and software.) Recalibration services are not offered for the CR216X dataloggers.
|-NOTE-||Note: Additional specifications are listed in the CR200X-Series Specifications Sheet.|
|Internal Spread-Spectrum Radio Operating Frequency Range||2.450 to 2.482 GHz|
|Transmitter Power Output||50 mW|
|Maximum Scan Rate||1 Hz|
|Pulse Count Channels||2|
|Switched Excitation Channels||2 voltage|
|Communication Ports||1 RS-232|
|Switched Battery Port||1|
|Input Voltage Range||0 to 2500 mV|
|Analog Voltage Accuracy||±(0.25% of reading + (1.2 mV)x(offset)) at -40° to +50°C|
|Analog Voltage Resolution||0.6 mV|
|Operating Temperature||-40° to +50°C|
|Power Requirements||7 to 16 Vdc|
|Typical Current Drain||
|Protocols Supported||PakBus (leaf node only), SDI-12|
|CE Compliance Standards to which Conformity Is Declared||IEC61326:2002|
|Dimensions||14.0 x 7.6 x 4.8 cm (5.5 x 3.0 x 1.9 in.)|
|Weight||271 g (9.5 oz)|
|Final Storage||512 kB of flash memory for approximately 125,000 data points|
|Operating System||106 kB of flash memory|
|Intermediate Storage||8 kB of SRAM for communication buffers, calculations, variables, etc.|
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
|LOGGERNET||Version 2.1 or higher|
|PC400||Version 1.0 or higher|
|PCONNECT (retired)||Version 3.0 or higher|
|PCONNECTCE (retired)||Version 2.0 or higher|
|VISUALWEATHER||Version 2 or higher|
The CR216X can communicate with a PC via direct connect, NL201 Network Link Interface, NL240 Wi-Fi Network Link, MD485 multidrop modem, and digital cellular modems. Data can be viewed on an iOS device, an Android device, CD295 DataView II Display, or a user-supplied PDA. To use an iOS or Android device, go to the Apple Store or Google Play and download our LoggerLink Mobile Apps free of charge. User-supplied PDAs require either PConnect or PConnectCE software.
The CR216X's internal spread spectrum radio can transmit data to other CR216(X) loggers, RF416 radios, or RF430 radios. Certain CR216X settings must match the radio's settings for communications between the data logger and radio to be successful. The factory default settings of these devices might not match; therefore, they may need to be reconfigured before communications can take place.
If the CR216X is in the transparent mode, it can communicate with the retired CR215 loggers or RF415 radios.
Campbell Scientific’s SDM devices and multiplexers are not supported.
The CR216X can measure a variety of sensors including SDI-12 sensors and 4 to 20 mA sensors. It cannot make differential measurements and is not compatible with the freezing-rain/ice, fuel moisture/temperature, geographic position, present weather, soil heat flux, soil matric water potential, and strain sensors listed on our price lists.
Applications with minimal power requirements can use the ENC200 enclosure to house the data logger and the #16869 sealed rechargeable battery. The ENC200 cannot house a barometer or a battery that is larger than the #16869. However, an ENC10/12 or ENC12/14 enclosure is adequate for most CR216X-based systems.
The CR216X uses an external power supply and has a built-in regulator. When connected to the on-board charging circuit, the sealed rechargeable battery should be 7 A h or smaller. Using larger batteries with the data logger's built-in charger may result in excessive PC board heating. This is especially a concern when the battery is deeply discharged or failing with a shorted cell. Campbell Scientific also recommends that solar panels be 10 W or less and wall chargers be 1 A or smaller.
Execution of this download installs the Operating System and Compiler on your computer for the following dataloggers:CR200X, CR206X, CR211X, CR216X and CR295X. It also updates the support files for the CRBasic Editor.
Note: Newer CR206X dataloggers (serial # ≥ 19122) and newer CR211X dataloggers (serial # ≥ 19143) have 250 mW radios that must use OS 3 or higher for their datalogger operating system.
Number of FAQs related to CR216X: 38
Expand AllCollapse All
The maximum cable length depends on the interface being used.
Yes. The simplest method is to use conditional program statements that execute most of the code based on time. For example, the data could be scheduled to log at 6 a.m. and finish at 8 p.m. using CRBasic instructions such as IfTime(). Another option is to use an IfThen/EndIf construction that does a logical test of light-level measurements based on a light sensor. An additional option is to use calculated sunrise and sunset times along with a combination of RealTime() and Case instructions.
For more information, see the “Decisions, Decisions, Decisions…” article.
The voltage excitation channels are high impedance when not connected, meaning that internally they are isolated from the data logger ground. The connected sensor, however, may tie the voltage excitation channel to ground, such as through a completion resistor.
Data will only be lost if the data logger’s internal 3 V battery is also bad. The “table definitions out of date” message simply implies that the data logger is running a program that the PC software does not recognize. After successfully connecting, the message “updating table definitions” should appear. This means that the PC software has knowledge of the program running on the data logger and should not affect data stored on the data logger.
The data logger assigns two attributes for program files:
If the latter option is not set for the data logger, the data logger will not have a program running when it powers up, which will result in lost data. For more information, see the “How Do You Run?” article.
Technically, the SRM-5A is compatible with the CR200X-series dataloggers, but it is more complicated to use it with these data loggers. To use a SRM-5A with a CR200X-series datalogger, the SRM-5A must be in the DTE position on the station modem. In addition, user-supplied adapters and gender changers are needed to complete the connections between the SRM-5A and the RS-232 port of the data logger. Contact Campbell Scientific for more information.
Not directly. If the CS15-L is connected to a CR200(X) datalogger, the data logger can take the ac measurement and control a solid-state relay based on some threshold within the data logger program. The solid-state relay can then control other relays, solenoids, or motor starters. (Use of a solid-state relay is preferred because the data logger can trigger it with a small 5 Vdc mA signal.) For more information, see the “Measurement and Control Peripherals” section of the operator’s manual.
Yes. Both the RavenXTV (Verizon) and the RavenXTG (AT&T) are available.
It is possible to upgrade the OS without downloading each OS version between the existing one on the data logger and the most current one available. For example, a CR1000 can be upgraded directly from OS 14 to OS 25. However, when a large jump in OS versions is made, the upgrade will likely restructure the Status table and the Setting table, and they will need to be manually reloaded.
Note that in many instances, an OS update may not be necessary. Before updating, check the OS Revision History to see if a newer version would provide desired benefits.
If the automatic clock synchronization option (LoggerNet [version 4] Setup, Datalogger, Clock tab) is used, do not set the Allowed Clock Deviation too tight (for example, 1 s), as the PC will try to change the clock either because of drift in its own clock or because of delays in the communication from the PC to the data logger. If the clock is updated too often, there is the risk of the data logger skipping records if the time is pushed forward just before it is supposed to store data.
Although most PCs are usually synchronized with Internet time, the default update time is several days, and a PC can typically drift tens of seconds in that period.
Clock issues also appear when changing to or from daylight saving time, as the data logger does not automatically adjust for DST. Data continuity can be maintained by keeping data logger clocks on standard time.
In addition, if the data logger’s internal 3 V battery is bad and the data logger’s main 12 V power supply is cycled, the data logger’s clock will reset to a default time.
This might happen because the data logger clock is being adjusted by a remote time source. If this occurs close to the same time that the data logger is due to store data, it can result in either a skipped record or an additional record of data.
If LoggerNet 4 is used to collect data on a schedule, check the setup for that data logger. Look at the settings on the Clock tab in the LoggerNet Setup Screen. If that is enabled, the clock is checked and set at midnight every day and may interfere with data collection at that same time.
Skipped scans and power outages could also result in records missing from a data table. Check the data logger’s station status or Status table and look for skipped scans, watchdogs, and low 12 V counts.