Data Loggers / CR9000XC
RETIRED ›
This product is no longer available and has been replaced by: GRANITE9,GRANITE10. Some accessories, replacement parts, or services may still be available.
CR9000XC Compact Datalogger Base System
Services Available

Overview

The CR9000XC, a compact version of the CR9000X, holds up to five user-selectable I/O modules. It is a modular, multiprocessor system that provides precision measurement capabilities in a rugged, battery-operated package. It consists of an environmental enclosure, a base system, and a chassis containing slots for the I/O modules.

The CR9000X series is our fastest datalogger series, with a measurement rate of 100,000 Hz and a clock speed of 180 MHz, making it ideal for rapid sampling applications.

See the entire list of available I/O modules for the CR9000XC and CR9000X.


Read More

Benefits and Features

  • Up to five I/O modules can be used to configure a system for your specific application.
  • Ideal for vehicle testing, structural or seismic monitoring, or other applications that require rapid sampling or a large number of high resolution channels
  • Throughput of 100,000 measurements per second is ideal for high demand research, such as flux and complex structural monitoring.
  • Contains an on-board 10baseT/100baseT port allowing direct Ethernet connection; an interface such as the NL100 is not required
  • CR9052IEPE and CR9052DC modules provide powerful anti-aliasing and real-time FFT capabilities that are unique to the CR9000X-series data loggers
  • Integrated PCMCIA slot accepts memory cards up to 2 GB for stand-alone data collecting.
  • Gas Discharge Tube (GDT) protected inputs
  • Collects and stores data and controls peripherals as the brain of your system

Images

Detailed Description

The CR9000XC's base system includes a CR9032 CPU module, CR9041 A/D module, CR9011 power supply module, and 128-Mbytes SDRAM memory for program and data storage. The CR9000XC's internal battery has a 7-Ahr capacity.

A mix of I/O modules is selected based on the measurements required for the application. Campbell Scientific offers a large variety of modules. Individual I/O modules can be swapped out, allowing the system to be reconfigured if requirements change.

I/O modules whose model numbers end in an E (e.g., CR9051E, CR9055E) and the CR9052DC include an easy connector module. Easy connector modules allow sensor wiring to remain connected while the input module’s measurement electronics and the rest of the datalogger system are used elsewhere.

The CR9000XC includes a non-corrosive, sealed, aluminum enclosure that provides protection from water, dust, and most environmental pollutants.

CR9000CX versus CR9000C

In August 2004, the CR9000XC replaced the CR9000C. The CR9000C and CR9000XC dataloggers differ in their CPU Module; the CR9000C datalogger uses the CR9031 and the CR9000XC datalogger uses the CR9032.

The CR9032 CPU module supports a measurement rate of up to 100,000 Hz, provides a 180 MHz clock speed, and adds a built-in RS-232 port, 10baseT/100baseT port, CS I/O port, and PC-card slot. The built-in ports enable communication without using the special interfaces (e.g., PLA100, TL925, NL105) that were required for the retired CR9000C datalogger. The PC-card slot allows the CR9000XC to store data on a Type I, Type II, or Type III PCMCIA card, or on a CompactFlash® card if an adapter is used.

An existing CR9000C datalogger may be upgraded to a CR9000XC by replacing the CR9031 CPU module with the CR9032 CPU module.

Specifications

-NOTE-
  • Additional specifications are listed in the CR9000X(C) Specifications Sheet.
  • For the CR9000XC, the current drain, weights, and specific number of input/output channels depend on the I/O modules chosen.
Operating Temperature Range
  • -25° to +50°C (standard)
  • -40° to +70°C (extended)
  • Non-condensing environment
Analog Inputs 28 single-ended or 14 differential per CR9050, CR9051E, or CR9055(E) module
Pulse Counters 12 per CR9071 module
Communications Ports
  • CS I/O
  • RS-232
  • 10baseT/100baseT
Switched 12 Volt 1
Digital I/O
  • Certain digital ports can be used to count switch closures.
  • 1 SDM and 8 outputs per CR9060 module or 16 I/Os per CR9071 module
Analog Voltage Accuracy ±(0.07% of reading + 4 A/D counts), -25° to +50°C
ADC 16-bit
Power Requirements 9.6 to 16 Vdc
Communication Protocols SDM
Warranty 3 years
Dimensions 25.4 x 27.9 x 22.9 cm (10 x 11 x 9 in.)
Weight 12.3 kg (27 lb) with modules

Compatibility

Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.

Miscellaneous

Product Compatible Note
LoggerNet Version 2.0 or higher
PC200 (retired)
PC400 Version 1.0 or higher
RTDAQ Version 1.0 or higher
Short Cut
VISUALWEATHER Version 2.0 or higher

Additional Compatibility Information

Compatibility with Retired Products

Customers can add CR9000XC dataloggers to networks containing the older CR9000 or CR9000C dataloggers. I/O modules other than the CR9080 can be used with either the CR9000 series or CR9000X series. CR9000 series communication interfaces (i.e., NL105, BLC100, TL925, PLA100) are not compatible with the CR9000XC, and therefore have been retired. RTDAQ software is not compatible with the older CR9000(C). Customers can upgrade a CR9000C datalogger to a CR9000XC datalogger by replacing the CR9000C's CR9031 CPU module with the contemporary CR9032C CPU module.

Sensors

With several channel types, the CR9000XC is compatible with many sensors, including thermocouples and 4 to 20 mA sensors.

Measurement and Control Peripherals

Measurement and control peripherals typically used with the CR9000XC 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 CR9000XC datalogger's maximum measurement rate and are therefore impractical for most CR9000XC applications.

Communications

The CR9000XC typically communicates with a PC via direct connect or Ethernet. Because the CR9000XC has an on-board 10baseT/100baseT port, an Ethernet interface such as the NL100 is not required.

Storage capacity can be increased by using a PC or CompactFlash card. The CR9000XC'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 CF cards that store up to 2 GB of data. 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 CR9000XC datalogger's maximum measurement rate and are therefore impractical for most CR9000XC applications.

Enclosures

The CR9000XC includes a non-corrosive, sealed, aluminum enclosure that provides protection from water, dust, and most environmental pollutants.

Software

CRBasic, the CR9000XC'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 CR9000XC is also compatible with other Campbell Scientific software.

Frequently Asked Questions

Number of FAQs related to CR9000XC: 36

Expand AllCollapse All

  1. What are the differences between the CR9000X and the CR9000XC?

    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.

  2. What needs to be done to get a CR3000 program to run on a CR9000 or CR9000X?
    The CR3000 program will have to be modified so that each measurement or control instruction includes the appropriate module number. Some parameters might differ as well.
  3. Is there a way to only record measurements during the daytime and put the data logger in sleep mode during the nighttime to conserve power?

    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. 

  4. How can data from a specific date range be collected from a data logger?

    There is a Custom button on the LoggerNet Connect screen that allows a variety of different data collection tasks, including collecting a range of data between dates.

    Note that, by default, data collected in this manner is stored to the C:\Campbellsci\LoggerNet\Data directory. This is a different directory and different file than where the data is stored from the LoggerNet scheduled data collection and from the Collect Now button on the Connect screen. (Scheduled collection and Collect Now data go into the same file and use the same data collection pointers.)

  5. How can it be calculated when a data logger data table will fill up?

    One of the simpler ways to approximate how long it will take for a data table to fill up is to open the LoggerNet Connect screen, click the Station Status button, and view the Table Fill Times tab.

    Note: Table Fill Time statistics cannot be calculated for a CR200-series data logger.

  6. Should an SC32B be installed between the RS-232 port on a data logger and the port on a desktop PC to prevent ground loop issues?

    No, because it would not work. The SC32B is used to do the following:

    • Convert data logger logic levels (on the CS I/O port) to RS-232 levels 
    • Optically isolate the data logger from the RS-232 peripheral 
  7. If a data logger OS has not been upgraded in a long time, can the most current OS be downloaded, or do the upgrades need to be done incrementally?

    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.

  8. Is there a free software package that allows the generation of programs that can sample data on the RS-232 or COM port of the data logger?

    Some Campbell Scientific sensors with an RS-232 output are supported in Short Cut. Because of the large variety of serial data formats, other sensors require creating a program in the CRBasic Editor. CRBasic Editor is included in several of the purchased software packages, such as LoggerNet. For more information, see the “Interfacing Serial Sensors with Campbell Scientific Data loggers” application note.

    Note: The CR200X-series data loggers have very limited serial capabilities.

  9. Instead of saving the data of a CRBasic data logger to one large file, how can it be saved in daily, hourly, or half-hourly files?

    Option 1

    Update the data logger OS to the most current version. Use the TableFile() instruction with Option 64 to create smaller files. For more information, see the “A Better Way to Write High-Frequency Data to 16 GB and Smaller CF Cards” application note.

    Option 2

    In the CRBasic program, set up multiple data tables using the DataTable() instruction. In each table, specify the desired output interval using the DataInterval() instruction.

    For example, the following three table definitions could be included in a program to store values once a day, once an hour, and every minute.

    DataTable (Daily,1,1000)
                    DataInterval (0,24,Hr,10)                 
                    Minimum (1,batt_volt,FP2,0,False)
                    Sample (1,PTemp,FP2)
    EndTable

     

    DataTable (Hourly,1,1000)
                    DataInterval (0,1,Hr,10)
                    Minimum (1,batt_volt,FP2,0,False)
                    Sample (1,PTemp,FP2)
    EndTable

     

    DataTable (OneMinute,1,1000)
                    DataInterval (0,1,Min,10)
                    Minimum (1,batt_volt,FP2,0,False)
                    Sample (1,PTemp,FP2)
    EndTable

  10. If an RF modem is used to communicate with a data logger and a PC running LoggerNet, but the modem baud rate is one third of the data logger baud rate, is that a problem?

    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.

Visit the FAQ Library

Privacy Policy Update

We've updated our privacy policy.  Learn More