CR1000

This depends on what is meant by “wireless.” Using telecommunication peripherals, the CR1000 can communicate with remote computers. Examples of “wireless” telecommunication options include cellular telephone, licensed and spread-spectrum radios, and satellite communications. Additionally, Ethernet interfaces allow the CR1000 to access, or be accessed by, the Internet or internal Local Area Networks (LANs).

These links allow the user to remotely access the datalogger's real-time data, stored data, and programming. Users can combine several telecommunication options. Popular telemetry options that can be combined include Ethernet-to-radio, multidrop-to-spread-spectrum radio, phone-to-multidrop, Ethernet-to-multidrop, and phone-to-radio.

Data storage and retrieval peripherals are described in this brochure. 

Not the same, but similar. The SDM-SIO4 provides RS-232 voltage levels; the CR1000 control ports provide 0 to 5 V only. Both usually work with all sensors, and both devices support RS-232 and TTL logic. The CR1000 is easier to set up and program for serial input. The SDM-SIO1 is another option.

The CR1000 can handle strings as a specific data type. It has integrated serial communications capabilities on the following:

• four control port pairs—COM1 (C1 Tx / C2 Rx) through COM4 (C7 Tx / C8 Rx)
• RS-232 port
• CSI/O port with the appropriate interface device

The serial I/O capabilities of the CR1000 are similar to, and faster than, the SDM-SIO4 capabilities on a CR10X or CR23X. SDM devices are addressable and are connected to a datalogger on C1 through C3. Therefore, one benefit of using multiple SDM devices on a CR1000 datalogger is that only three control ports are used.

Yes. We have created a software application, Transformer, to help migrate CR10X program files to CR1000 program files.

Transformer is available within LoggerNet 3.0: from the Windows Start Menu, navigate to LoggerNet3.0 | Utilities | Transformer.

In LoggerNet 4.x, from the main LoggerNet window, navigate to Program | Transformer.

A network camera can be connected directly to a CR1000 via an NL115 or NL120 and a crossover cable. The datalogger can retrieve and store images from the network camera. Then the images can be viewed or retrieved from the datalogger in a variety of ways. These include using LoggerNet, the CR1000 web server, the CR1000 FTP client/server, or the CR1000 email client.

LoggerNet (version 4) can be configured in the Setup Screen to save data in binary format. On the Data Files tab, set the Output Format to Binary Table Data (TOB1).

Alternately, the CardOut() and TableFile() instructions can be used to write binary files.

When using IP communications, data can be collected from a CR1000 using any of the following:

• LoggerNet
• FTP transfer of data from a datalogger to a computer
• SMTP transfer of data from a datalogger to a computer
• HTTP request of data from a datalogger by a computer
• serial stream over IP socket from a datalogger to a computer

No. The RS-232 does not provide 12 Vdc on any pin. The port does use an RS-232 driver chip that is capable of working with many “port-powered” interfaces.

Each of the COM RS-232, COM1, COM2, COM3, and COM4 ports has a maximum baud rate of 115200 bps. The actual maximum throughput for each serial port is about 11000 bps, depending on the bit format used.

Yes. For example, the NL115 allows the CR1000 to communicate over a local network or a dedicated Internet connection via TCP/IP. 

An interface is required. This can be done using an SDM-SIO1, or a third-party RS-422 to RS-232 converter.

The operating voltage is 9.6 Vdc to 16 Vdc. The datalogger will shut down at 9.6 V. When this happens, a counter is incremented in the datalogger's Status Table (low12Vcount). In general, 12 to 13 Vdc is good. Voltages above 16 Vdc can cause bad measurements, and the resulting data should be reviewed carefully. Sustained voltages in excess of ±16 Vdc can damage the datalogger and its wiring panel.

The minimum scan interval is 10 ms.

With operating system 25 or greater, the CR3000 supports CF cards in sizes up to 16 GB using the TableFile() instruction and TFOption 64. For earlier versions of the operating system, the largest CF card size supported is 2 GB.

For more information, see the application note “A Better Way to Write High-Frequency Data to 16 GB and Smaller CF Cards”.

The data structure that is used to store data in the datalogger's CPU memory cannot be downloaded directly. If a datalogger’s memory is expanded using a CompactFlash card, then the native TOB3 file can be downloaded using the Connect | File Control | Retrieve… menu.

Campbell Scientific dataloggers cannot communicate directly with LabVIEW. However, after data collected by any of the Campbell Scientific dataloggers has been retrieved and placed in the LoggerNet data cache, it can be shared with LabVIEW using a LoggerNet client called PC-OPC. A trial version of PC-OPC is available in the Downloads section of this page. 

Files can be transferred to an iPhone from a computer using File Sharing in iTunes.

Files can also be emailed to an iPhone or accessed through a cloud storage system such as Dropbox. LoggerLink is registered with iOS so that the program file types are handled correctly. Using the Open in feature allows these files to be copied to LoggerLink.

Telemetry peripherals are discussed and compared in the “Data Storage & Retrieval Peripherals” brochure. 

Yes. The CR1000 could be set up as a SDI-12 sensor using the SDI12SensorSetup() instruction. Alternatively, the CR1000 could be set up to perform serial communication with the CR3000 by connecting a COM1…COM4 port pair and ground from one datalogger to a COM1…COM4 port pair and ground on the other datalogger. The COM1…COM4 port lines need to cross Rx to Tx and vice versa.

Yes, the CR800-series, CR1000, and CR3000 dataloggers can be programmed with the CD100, CR1000KD, or integrated keypads. The keypad can be used to create new programs or edit programs that already exist in the datalogger's memory.

From the CD100 or CR1000KD home screen follow these steps:

1. Press Enter. 
2. Select File and press Enter. 
3. Select either New or Edit. 
• To modify an existing instruction, select the instruction, and press Enter. 
• To add a new instruction, press Ins, and select Instruction.

Eddy-covariance programs for the CR5000 and CR1000 are not published on our website. To purchase a datalogger program to measure the sensors used in these systems and perform the calculations, please contact one of the application engineers in our Flux Group.

Load the string to a buffer in the SDM-SIO4, and issue the command to send the string. See the SDM-SIO4 Instruction Manual for details.

Some possible causes include the following:

• the result of a hardware problem in the datalogger, the PC serial port, or the port driver
• power supply or grounding problems on the datalogger
• the port configuration of the datalogger (If the datalogger RS-232 port is configured at a fixed baud rate other than 115200, it might cause the error messages.)

The Device Configuration Utility, under its Unknown device type, has an Identify Logger Type button. This button will attempt to identify the device type, protocol, or both used for the datalogger and will attempt to do so at various baud rates. If the datalogger is synchronized with a different baud rate or is set up at a fixed baud rate, this feature may provide the means of determining what baud rate should be used for successful communication.

The CRBasic Editor Help contains example program code for all instructions in the datalogger. Look for the Example link at the top of each instruction topic. The CRBasic Help Tutorial demonstrates how to access this and other online CRBasic Editor Help files.

This might happen because the datalogger clock is being adjusted by a remote time source. If this occurs close to the same time that the datalogger is due to store data, it can result in either a skipped record or an additional record of data.

Short Cut for Windows (SCWin) is a free program generator for Campbell Scientific dataloggers, including the CR1000. The Campbell Scientific YouTube channel has a two-part series on using Short Cut. 

If the automatic clock synchronization option (LoggerNet [version 4] Setup, Datalogger, Clock tab) is used, do not set the Allowed Clock Deviation too tight (e.g., 1 s), as the PC will try to change the clock either due to drift in its own clock or because of delays in the communication from the PC to the datalogger. If the clock is updated too often, there is the risk of the datalogger “skipping records” if the time is pushed for just before it is supposed to store data.

While 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 datalogger does not automatically adjust for DST. Data continuity can be maintained by keeping datalogger clocks on standard time.

The advantage of the BrHalf4W circuit is that lead resistance does not affect the measurement. 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 the leads are of the same resistance.

An IfTimeIntoInterval()/EndIf construction with a PortSet() or WriteIO() instruction can be used to turn on and off external devices. See the article at www.campbellsci.com/tips-decisions for more information.

The datalogger assigns two attributes for program files:

• run now: specifies the file should be run as the current program
• run on power up: specifies that the file should be run as the program when the datalogger powers up

If the latter option is not set for the datalogger, the datalogger will not have a program running when it powers up, which will result in lost data. See the article at www.campbellsci.com/tips-how-do-you-run for more information.

The lithium battery voltage is measured by the datalogger once per day, and the value is held in the Status Table when it is running normally. The voltage is normally extremely stable if the datalogger is powered from another source and its temperature is stable. A new battery supplies approximately 3.6 Vdc; it should be replaced when its reading is at or below 2.7 Vdc.

Some Campbell Scientific sensors with an RS-232 output are supported in Short Cut. Due to 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. See the “Interfacing Serial Sensors with Campbell Scientific Dataloggers” application note for more information.

RTMC Pro software is capable of email alarms. An alarm could be set to trigger when there is a communication failure.

A skipped system scan can be seen in the datalogger’s Status Table. It indicates there was not enough time for the datalogger to do its background calibration procedures, which it does on a regular cycle. (Refer to the datalogger’s manual for more details.)

If these system scans are skipped, they are usually deferred until the next time they should run. This may not necessarily be a problem as long as the system scan does run some of the time. All it means is that the datalogger becomes slower to respond to changes, such as temperature, that can affect its calibration.

The Status Table, accessed from the CR1000KD or LoggerNet’s (version 4) Connect Screen, Station Status button, has some statistics that may be useful. In Appendix B of the CR1000 Operator’s Manual, refer to “ProcessTime,” “MaxProcTime,” “MeasureTime,” and “MeasureOps.”

The CR1000 can measure analog voltages in the ±5 Vdc range. A voltage divider such as the VDIV2:1 is required to reduce 10 Vdc to an acceptable range. See the VDIV10:1/VDIV2:1 manual for examples of wiring and programs. 

Sending a serial string out one of the datalogger COM ports requires at least two instructions. Generally, the SerialOpen() instruction is used to set up the communication port, such as 115.2k, N, 8, 1. The instructions SerialOut() or SerialOutBlock() can be used to transmit a specified string. See the CRBasic Editor Help for examples of programs using each of these instructions. 

From the CRBasic version 3.4 Help file: “TDF stands for Table Definitions File. When a program is compiled for a CR1000, CR3000, or CR800/850 datalogger a program_name.TDF file is created along with the original program file. This file contains the table definitions (table size, variable names, data types, etc.) for that program. In software that supports this functionality, the user can associate a TDF file with a datalogger. This can be useful if communication is taking place over a slow or unreliable communications link where the attempt to receive table definitions back from the datalogger fails.”

The datalogger’s Status Table has a LastSystemScan field that provides this information.

Yes. The simplest method is to use conditional program statements that execute most of the code based upon 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 this article: www.campbellsci.com/tips-decisions.

If the dataloggers are connected over some form of serial/PakBus link, they can be synchronized with each other using the ClockReport() and PakBusClock() instructions in the dataloggers. Use the ClockReport() instruction in the master (time) datalogger and the PakBusClock() instruction in the slave dataloggers. The option to broadcast to all can be used (providing no routing is needed), which means that just one packet of information is sent.

The ClockReport() instruction can be used as frequently as desired, although, for practical purposes, once or twice a day should be adequate for most applications. The clock should be set at a time that does not interfere with the timing of dataloggers storing their data.

If the dataloggers are connected over an IP network, use the NetworkTimeProtocol() instruction so that one datalogger acts as the time server.

If both dataloggers are using the same cell modem, then simultaneous connection and download is not possible. To resolve this, first create a local network, such as by direct connection, RF4xx radios, an MD485, or Ethernet. Then use the cell modem to access the network.

Yes. Control port pairs may be configured as full duplex asynchronous RS-232/TTL serial ports. See the datalogger manual for details. This application note provides additional details on interfacing RS-232 sensors.

The USR drive is a user-created drive in the CR1000, CR3000, and CR800 dataloggers. It can be set up by assigning a value to the datalogger's UsrDriveSize setting in the Status Table (by entering a value into the Status Table directly, by using DevConfig, or by setting it with the SetStatus() instruction). This drive must be set to at least 8192 bytes, in 512 byte increments. (If the value entered is not a multiple of 512 bytes, the size will be rounded up.) Maximum size is calculated based on the datalogger's total memory size less approximately 403 KB (reserved for the OS and file system). If the value entered for the UsrDriveSize is greater than the maximum, the drive will be set to the maximum.

Hardware such as the CC5MPX and datalogger instructions such as TableFile() can write files to the USR drive.

If the program is sent using the Program Send button in the Connect Screen, the data is always deleted.

If the program is sent using File Control | Send…, the Preserve data if no table changed option can be selected. If this option is selected, existing data and data table structures on the CR800, CR850, CR1000, and CR3000 (files stored to the CPU) are retained unless one of the following occurs:

• The data table name changes. 
• The data interval or offset changes. 
• The number of fields per record changes. 
• The number of bytes per field changes. 
• The number of records per table (table size) changes. 
• The field type, size, name, or position changes.

To summarize, with newer OSs, any change in the data table structure will delete all the tables on the datalogger's CPU, regardless of whether or not the program is sent with the File Control | Send… Preserve data if no table changed option selected. If the option was selected, but the datalogger was unable to retain the existing data, the Warning: Internal Data Storage Memory was re-initialized message appears in Compile Results.

Note: Campbell Scientific recommends collecting data before making any program changes.

The time to fill the datalogger’s memory depends on the following:

• the size of the data tables 
• the number of values being written to the data table 
• the data types of those values 
• the conditions that determine whether new data is added to a data table

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. (See www.campbellsci.com/tips-details for help with this.) 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.

Common causes include the following:

• loss of power to the datalogger and the program Run On Power-up attribute not being set  (See www.campbellsci.com/tips-how-do-you-run for help with this.) 
• a FillStop instruction in a CRBasic program used to set data tables to stop storing new data when full
• logical conditions for writing to data tables that do not evaluate as TRUE

The CR1000, CR3000, and CR800-series dataloggers can be used to collect binary data from processor-based sensors via a serial connection using a COM1…COM4 port (control port pair), CS I/O port, RS-232 port, or SDM-SIO1. In some cases, when using a COM1…COM4 port, an RS-232/RS-422/RS-485 to TTL converter may be required.

Note: The capabilities mentioned above are not available for the CR200X-series, CR5000, and CR9000X dataloggers.

Values may be viewed and modified from the Connect Screen in LoggerNet or from the main screen in PC400 and PC200W. Simply double-click the value to be changed, and key in the new variable. Alternatively, right-click on the value, select View Value, and make the change in the View/Modify the Current Value window.

Declare variables

Public_nmbr_float

Public nmbr_long As Long

Cast float variable as long variable

nmbr_long = nmbr_float

The CR3000 will move the integer portion of “nmbr_float” into “nmbr_long.”

It is possible that an older version of Short Cut is being used. Download the latest version of Short Cut.

If the latest version of Short Cut for Windows has already been downloaded, open the program.

1. Go to Tools | Options and make sure that the Enable Creation of Custom Sensor Files box is checked.
2. In the Generic Measurements folder, right-click the type of measurement to be made for the sensor, and select Create Custom Sensor.
3. Fill in the fields, and save the settings with the Save As button. 

Yes. The datalogger can control power to external devices under program control. For more information, see www.campbellsci.com/tips-decisions.

To turn a generator on and off, a solid state relay with a load capacity that matches or exceeds the power of the generator is needed. The relay is controlled by one of the control ports on the datalogger.

Yes, but only with a direct connection, such as an RS-232 cable or USB-to-serial adapter.

In the CR800-series, CR1000, and CR3000 dataloggers, there is a PreserveVariables instruction that stores the last known value of all Dim or Public variables. The values are restored if the datalogger recovers from a power failure, or if the program is stopped with the retain data option and then resumed.

Only the CR1000. Dataloggers such as the CR3000 and CR5000 have the necessary PRT bridge module built in.

A USB-to-serial cable is required.  This can be purchased from Campbell Scientific (p/n 17394) or from a local electronics store. USB-to-serial cables with the FTDI chipset are easier to use and seem to perform better than cables with the Prolific chipset.

Yes, the datalogger can act as an FTP Client to send a file or get a file from an FTP server, such as another datalogger or web camera. This is done using the CRBasic FTPClient () instruction. See the manual for the network link interface or CRBasic Editor Help for details and sample programs. 

Campbell Scientific recommends using the current datalogger OS for this feature. 

Current dataloggers supported by the BMP5 Direct SDK are the CR200X-series, CR1000, CR3000, CR800, and CR850. Retired supported dataloggers include the CR10X-PB, CR23X-PB, and CR510-PB. These dataloggers must have the optional PakBus operating system installed, which is available on the Downloads page of our website.

PC200W, which is available free of charge from the PC200W product page on our website.

Both of these are SDM devices. Each SDM device that is connected to a datalogger needs a different SDM address (i.e., 0 through 15). All SDM devices connect to the CR1000’s 12V, G, C1, C2, or C3 terminals. Therefore, up to 16 SDM devices can be connected to one datalogger.

See the Synchronous Devices for Measurement (SDMs) page for more information. 

These dataloggers do not have an RS-232 port; therefore, the computer must be connected to the datalogger’s CS I/O port. The SC32B provides a direct interface between the CS I/O port on a Campbell Scientific datalogger and the RS-232 port on a computer.

For dataloggers that have an RS-232 port, the SC32B is only necessary if connecting to the CS I/O port instead of the RS-232 port.

In addition to providing the interface with the datalogger, the SC32B also provides isolation between the grounds of the datalogger and the computer. This isolation may be important when measuring low-level, single-ended voltage measurements using a computer connected to a datalogger with an ac power source. For more information, see the SC32B Instruction Manual.

Using the FileControl() instruction, the .DAT files can be retrieved directly from the memory card. When data is collected by the standard method (not as downloaded files, but as streamed data) with a GetData() or similar instruction, the memory card is automatically used as a source of records to be returned when the internal CPU table no longer contains the oldest data. These records can be retrieved simply by using their record numbers.