CR9000X的基础系统包括：CR9032 CPU模块、CR9041 A/D模块、CR9011供电模块、以及存储数据和程序的128-MB SDRAM内存。CR9000X的内部电池为 14-Ahr容量。
CR9000X vs CR9000
CR9032 CPU模块支持测量速率高达100,000 Hz，提供了180 MHz的时钟速度，添加了内置的RS-232端口、10baseT/100baseT以太网端口、CS I/O端口和PC卡插槽。内置的这些端口使得CR9000X不需要原先CR9000所需的特殊接口（例如：PLA100、TL925、NL105）就可进行通讯。PC卡卡槽可以让CR9000X存储数据到I型、II型或III型PCMCIA卡，如果使用适配器也可支持CompactFlash®卡。
CR9000可以升级到CR9000X，通过替换CR9031 CPU模块为CR9032 CPU模块。
|Operating Temperature Range||
|Analog Inputs||28 single-ended or 14 differential per CR9050, CR9051E, or CR9055(E) module|
|Pulse Counters||12 per CR9071 module|
|Switched 12 Volt||1 terminal|
|Analog Voltage Accuracy||±(0.07% of reading + 4 A/D counts), -25° to +50°C|
|Power Requirements||9.6 to 16 Vdc|
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
|LOGGERNET||Version 2.0 or higher|
|PC400||Version 1.0 or higher|
|RTDAQ||Version 1.0 or higher|
|VISUALWEATHER||Version 2.0 or higher|
Customers can add CR9000X dataloggers to networks containing the older CR9000 or CR9000C dataloggers. I/O modules other than the CR9080 can be used with either the CR9000 or CR9000X. CR9000 communication interfaces (i.e., NL105, BLC100, TL925, PLA100) are not compatible with the CR9000X, and therefore have been retired.
With several channel types, the CR9000X is compatible with many sensors, including thermocouples and 4 to 20 mA sensors.
Measurement and control peripherals typically used with the CR9000X are our AM25T 25-Channel Solid State Multiplexer, SDM-CAN Interface, SDM-INT8 Eight Channel Interval Timer, and SDM-SIO4 Serial Input/Output Module. Other measurement and control peripherals are compatible but they do not support the CR9000X datalogger's maximum measurement rate and are therefore impractical for most CR9000X applications.
The CR9000X typically communicates with a PC via direct connect or Ethernet. Because the CR9000X has an on-board 10baseT/100baseT port, an Ethernet interface such as the NL201 is not required.
Storage capacity can be increased by using a PC or CompactFlash card. The CR9000X's PCMCIA card slot supports one Type I, Type II, or Type III PC Card or the CF1 adapter and one CompactFlash (CF) card.
The storage capacity of Type II cards exceeds 1 GB. Type III cards provide data storage capacities exceeding 1 GB but may not be suitable for all environments. Campbell Scientific offers several CF cards that have passed our ESD testing and operate properly with our data loggers (see Ordering tab). Please note that the PCMCIA and CompactFlash cards need to be industrial-grade and have a storage capacity of 2 GB or less.
Other communication peripherals are compatible but they do not support the CR9000X datalogger's maximum measurement rate and are therefore impractical for most CR9000X applications.
Two enclosures are offered for the CR9000X. The 8253 fiberglass environmental enclosure is designed for field applications where the enclosure will be exposed to the elements. The 8255 lab enclosure is for applications where the CR9000X will reside inside a building.
CRBasic, the CR9000X's full programming language, supports simple or complex programming and many on-board data reduction processes. CRBasic is included in RTDAQ, LoggerNet, and PC400.
RTDAQ Real-Time Data Acquisition Software must be ordered separately; the CR9000X is also compatible with other Campbell Scientific software.
Current Operating System, Compiler and CR9000X support files for the CRBasic Editor. Requires the Device Configuration Utility, LoggerNet or RTDAQ to upload.
Use of this file will update the datalogger support files for the CRBasic Editor included in LoggerNet and RTDAQ.
Upgrade PC9000 version 5.0, 5.1, 5.2 or 5.3 to 5.3.1; no intermediate steps are required.
PC9000 5.0, 5.1, 5.2 or 5.3 must be installed on your machine.
The CR9000X and CR9000XC differ only in the number of I/O cards they can hold. The CR9000X can hold 9 I/O cards, and the CR9000XC can hold 5 I/O cards. We provide both sizes to accommodate our customers; the same I/O cards can be used in either chassis.
There are two ways to upgrade an operating system:
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 TimeIntoInterval(). 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 advantage of the BrHalf4W circuit is that the effect of lead resistance is measured and compensated for. The disadvantage is that it requires two differential (four single-ended) voltage input channels and four wires to the sensor.
Some sensors have four wires and are sensitive enough that the lead resistance would cause too great an error.
The BrHalf, a two-wire measurement, does not compensate for lead resistance.
The BrHalf3W lead compensation assumes that both leads are of the same resistance.
The data logger will not reset the SW12 unless it is done under program control using the SW12() or PortSet() instructions, or unless the data logger compiles or recompiles a program. This could be done when a new program is sent to the data logger, or if the power is cycled.
If small amounts of data are transferred per transmission, it will not be a problem. Larger amounts of data can overrun buffers in the modem, causing lost data. In that situation, lower the baud rate on the data logger to avoid the issue.
All the input terminals, peripheral and communications terminals, operating system, and Flash EEPROM are checked. The data logger is checked to ensure that all hardware operates within published specifications.
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.