0% found this document useful (0 votes)

2K views236 pages

CR310 Manual

Datalogger CR310

Uploaded by

elisio_fonseca

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

2K views236 pages

CR310 Manual

Datalogger CR310

Uploaded by

elisio_fonseca

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 236

Revision: 12/19/2018

Copyright © 2000 – 2018

Campbell Scientific, Inc.
Precautions
DANGER — MANY HAZARDS ARE ASSOCIATED WITH INSTALLING, USING, MAINTAINING,
AND WORKING ON OR AROUND TRIPODS, TOWERS, AND ANY ATTACHMENTS TO TRIPODS
AND TOWERS SUCH AS SENSORS, CROSSARMS, ENCLOSURES, ANTENNAS, ETC. FAILURE TO
PROPERLY AND COMPLETELY ASSEMBLE, INSTALL, OPERATE, USE, AND MAINTAIN TRIPODS,
TOWERS, AND ATTACHMENTS, AND FAILURE TO HEED WARNINGS, INCREASES THE RISK OF
DEATH, ACCIDENT, SERIOUS INJURY, PROPERTY DAMAGE, AND PRODUCT FAILURE. TAKE ALL
REASONABLE PRECAUTIONS TO AVOID THESE HAZARDS. CHECK WITH YOUR
ORGANIZATION'S SAFETY COORDINATOR (OR POLICY) FOR PROCEDURES AND REQUIRED
PROTECTIVE EQUIPMENT PRIOR TO PERFORMING ANY WORK.
Use tripods, towers, and attachments to tripods and towers only for purposes for which they are
designed. Do not exceed design limits. Be familiar and comply with all instructions provided in
product manuals. Manuals are available at www.campbellsci.com or by telephoning 435-227-
9000 (USA). You are responsible for conformance with governing codes and regulations, includ-
ing safety regulations, and the integrity and location of structures or land to which towers, tri-
pods, and any attachments are attached. Installation sites should be evaluated and approved by
a qualified engineer. If questions or concerns arise regarding installation, use, or maintenance of
tripods, towers, attachments, or electrical connections, consult with a licensed and qualified
engineer or electrician.
General

l Prior to performing site or installation work, obtain required approvals and permits. Com-
ply with all governing structure-height regulations, such as those of the FAA in the USA.
l Use only qualified personnel for installation, use, and maintenance of tripods and towers,
and any attachments to tripods and towers. The use of licensed and qualified contractors is
highly recommended.
l Read all applicable instructions carefully and understand procedures thoroughly before
beginning work.
l Wear a hardhat and eye protection, and take other appropriate safety precautions while
working on or around tripods and towers.
l Do not climb tripods or towers at any time, and prohibit climbing by other persons. Take
reasonable precautions to secure tripod and tower sites from trespassers.
l Use only manufacturer recommended parts, materials, and tools.

Utility and Electrical

l You can be killed or sustain serious bodily injury if the tripod, tower, or attachments you
are installing, constructing, using, or maintaining, or a tool, stake, or anchor, come in con-
tact with overhead or underground utility lines.
l Maintain a distance of at least one-and-one-half times structure height, or 20 feet, or the
distance required by applicable law, whichever is greater, between overhead utility lines
and the structure (tripod, tower, attachments, or tools).
l Prior to performing site or installation work, inform all utility companies and have all under-
ground utilities marked.
l Comply with all electrical codes. Electrical equipment and related grounding devices
should be installed by a licensed and qualified electrician.

Elevated Work and Weather

l Exercise extreme caution when performing elevated work.

l Use appropriate equipment and safety practices.
l During installation and maintenance, keep tower and tripod sites clear of un-trained or
non-essential personnel. Take precautions to prevent elevated tools and objects from drop-
ping.
l Do not perform any work in inclement weather, including wind, rain, snow, lightning, etc.

Maintenance

l Periodically (at least yearly) check for wear and damage, including corrosion, stress cracks,
frayed cables, loose cable clamps, cable tightness, etc. and take necessary corrective
actions.
l Periodically (at least yearly) check electrical ground connections.

DANGER: Fire, explosion, and severe-burn hazard. Misuse or improper installation of the internal
lithium battery can cause severe injury. Do not recharge, disassemble, heat above 100 °C (212 °F),
solder directly to the cell, incinerate, or expose contents to water. Dispose of spent lithium bat-
teries properly.
WARNING:

l Protect from over-voltage.

l Protect from water (see Datalogger enclosures (p. 86)).
l Protect from ESD (see Electrostatic discharge and lightning protection (p. 88)).

IMPORTANT: Note the following about the internal battery:

l When primary power is continuously connected to the datalogger, the battery will last up
to 10 years or more.
l When primary power is NOT connected to the datalogger, the battery will last about three
years.
l See Internal battery (p. 86) for more information.
IMPORTANT: Maintain a level of calibration appropriate to the application. Campbell Scientific
recommends factory recalibration of the datalogger every three years.
WHILE EVERY ATTEMPT IS MADE TO EMBODY THE HIGHEST DEGREE OF SAFETY IN ALL
CAMPBELL SCIENTIFIC PRODUCTS, THE CUSTOMER ASSUMES ALL RISK FROM ANY INJURY
RESULTING FROM IMPROPER INSTALLATION, USE, OR MAINTENANCE OF TRIPODS, TOWERS,
OR ATTACHMENTS TO TRIPODS AND TOWERS SUCH AS SENSORS, CROSSARMS,
ENCLOSURES, ANTENNAS, ETC.
Warranty and
Acknowledgements
The datalogger is warranted for three (3) years subject to this limited warranty: https://www.camp-
bellsci.com/terms#warranty.

Acknowledgements
lwIP
Copyright (c) 2001-2004 Swedish Institute of Computer Science.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of con-
ditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of con-
ditions and the following disclaimer in the documentation and/or other materials provided
with the distribution.
3. The name of the author may not be used to endorse or promote products derived from this
software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR “AS IS” AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
Table of Contents
1. Data acquisition system components 1
1.1 Sensors 2
1.2 The CR300 Series Datalogger 3
1.2.1 CR300 Series Product Line 3
1.2.2 Overview 3
1.2.3 Operations 4
1.2.4 Programs 4

2. Wiring panel and terminal 4

2.1 Power input 7
2.1.1 Power LED indicator 8
2.2 Power output 8
2.3 Grounds 9
2.4 Communications ports 10
2.4.1 USB port 10
2.4.2 Ethernet port 11
2.4.3 C terminals for communications 11
2.4.3.1 SDI-12 ports 11
2.4.4 RS-232 Port 11
2.4.4.1 RS-232 Power States 12
2.5 Programmable logic control 12

3. Setting up the datalogger 14

3.1 Setting up communications with the datalogger 14
3.1.1 USB or RS-232 communications 15
3.1.2 Virtual Ethernet over USB (RNDIS) 16
3.1.2.1 Connecting to your datalogger via RNDIS 16
3.1.3 Ethernet communications 17
3.1.3.1 Configuring datalogger Ethernet settings 17
3.1.3.2 Ethernet LEDs 18
3.1.3.3 Setting up Ethernet communications between the datalogger and com-
puter 19
3.1.4 Wi-Fi communications 20

Table of Contents - i
3.1.4.1 Configuring the datalogger to host a Wi-Fi network 20
3.1.4.2 Connecting your computer to the datalogger over Wi-Fi 20
3.1.4.3 Setting up Wi-Fi communications between the datalogger and the data-
logger support software 21
3.1.4.4 Configuring dataloggers to join a Wi-Fi network 22
3.1.4.5 Wi-Fi LED indicator 23
3.1.5 Cellular Communications 23
3.1.5.1 Cellular (TX/RX) LED Indicator 25
3.1.6 Radio communications 26
3.1.6.1 Configuration options 26
3.1.6.2 RF407-Series radio communications with one or more dataloggers 27
Configuring the RF407-Series radio 28
Setting up communications between the RF407-Series datalogger and the
computer 28
3.1.6.3 RF407-Series radio communications with multiple dataloggers using one
datalogger as a router 29
Configuring the RF407-Series radio 30
Configuring the datalogger acting as a router 30
Adding routing datalogger to LoggerNet network 31
Adding leaf dataloggers to the network 31
Using additional communications methods 32
3.2 Testing communications and completing EZ Setup 32
3.3 Connecting the datalogger to a computer 33
3.4 Creating a program in Short Cut 33
3.5 Sending a program to the datalogger 35
3.5.1 Program run options 36

4. Working with data 37

4.1 Collecting data 38
4.1.1 Collecting data using LoggerNet 38
4.1.2 Collecting data using PC200W or PC400 38
4.2 Viewing historic data 39
4.3 About data tables 40
4.3.1 Table definitions 40
4.3.1.1 Header rows 40
4.3.1.2 Data records 42
4.4 Creating data tables in a program 43

Table of Contents - ii
5. Data memory 45
5.1 Flash memory 45
5.2 Serial flash memory 45
5.2.1 Data memory 45
5.2.2 CPU drive 46

6. Measurements 47
6.1 Voltage measurements 47
6.1.1 Single-ended measurements 48
6.1.2 Differential measurements 48
6.2 Current-loop measurements 49
6.2.1 Voltage Ranges for Current Measurements 49
6.2.2 Example Current-Loop Measurement Connections 49
6.3 Resistance measurements 51
6.3.1 Resistance measurements with voltage excitation 51
6.3.2 Strain measurements 54
6.3.3 Accuracy for resistance measurements 56
6.4 Period-averaging measurements 57
6.5 Pulse measurements 58
6.5.1 Low-level ac measurements 59
6.5.2 High-frequency measurements 59
6.5.3 Switch-closure and open-collector measurements 59
6.5.3.1 P_SW Terminal 60
6.5.3.2 C terminals 60
6.5.4 Quadrature measurements 60
6.5.5 Pulse measurement tips 62
6.5.5.1 Input filters and signal attenuation 62
6.5.5.2 Pulse count resolution 62
6.6 Vibrating wire measurements 63
6.6.1 VSPECT® 63

7. Communications 64
7.1 General serial communications 65
7.2 Modbus communications 65
7.2.1 About Modbus 66
7.2.2 Modbus protocols 67
7.2.3 Understanding Modbus Terminology 68

Table of Contents - iii

7.2.4 Connecting Modbus devices 68
7.2.5 About Modbus communications 69
7.2.6 About Modbus programming 69
7.2.6.1 Endianness 70
7.2.6.2 Function codes 70
7.2.7 Modbus information storage 71
7.2.7.1 Registers 71
7.2.7.2 Coils 71
7.2.7.3 Data Types 72
Unsigned 16-bit integer 72
Signed 16-bit integer 72
Signed 32-bit integer 72
Unsigned 32-bit integer 73
32-Bit floating point 73
7.2.8 Modbus tips and troubleshooting 73
7.2.8.1 Error codes 73
Result code -01: illegal function 73
Result code -02: illegal data address 74
Result code -11: COM port error 74
7.3 Internet Communications 74
7.4 DNP3 communications 75
7.5 PakBus communications 75
7.6 SDI-12 communications 76
7.6.1 SDI-12 transparent mode 76
7.6.1.1 SDI-12 transparent mode commands 77
7.6.2 SDI-12 programmed mode/recorder mode 78
7.6.3 Programming the datalogger to act as an SDI-12 sensor 78
7.6.4 SDI-12 power considerations 79

8. Maintaining your datalogger 81

8.1 Datalogger calibration 81
8.2 Datalogger security 82
8.2.1 Security codes 83
8.2.2 Creating a .csipasswd file 84
8.2.2.1 Command syntax 85
8.3 Datalogger enclosures 86
8.4 Internal battery 86

Table of Contents - iv
8.4.1 Replacing the internal battery 87
8.5 Electrostatic discharge and lightning protection 88
8.6 Power budgeting 89
8.7 Updating the operating system 89
8.7.1 Sending an operating system to a local datalogger 90
8.7.2 Sending an operating system to a remote datalogger 91

9. Tips and troubleshooting 93

9.1 Checking station status 94
9.1.1 Viewing station status 94
9.1.2 Watchdog errors 94
9.1.3 Results for last program compiled 95
9.1.4 Skipped scans 95
9.1.5 Skipped records 96
9.1.6 Variable out of bounds 96
9.1.7 Battery voltage 96
9.2 Understanding NAN and INF occurrences 96
9.3 Timekeeping 97
9.3.1 Clock best practices 97
9.3.2 Time stamps 98
9.3.3 Avoiding time skew 98
9.4 CRBasic program errors 99
9.4.1 Program does not compile 99
9.4.2 Program compiles but does not run correctly 99
9.5 Troubleshooting Radio Communications 100
9.6 Reducing Out of Memory Errors 100
9.7 Resetting the datalogger 100
9.7.1 Processor reset 101
9.7.2 Program send reset 101
9.7.3 Manual data table reset 101
9.7.4 Formatting drives 102
9.7.5 Full memory reset 102
9.8 Troubleshooting power supplies 102
9.9 Minimizing ground loop errors 103
9.10 Improving voltage measurement quality 104
9.10.1 Deciding between single-ended or differential measurements 104
9.10.2 Minimizing ground potential differences 105

Table of Contents - v
9.10.2.1 Ground potential differences 106
9.10.3 Minimizing power-related artifacts 107
9.10.3.1 Minimizing electronic noise 107
9.10.4 Filtering to Reduce Measurement Noise 108
9.10.5 Minimizing settling errors 110
9.10.5.1 Measuring settling time 110
9.10.6 Factors affecting accuracy 113
9.10.6.1 Measurement accuracy example 113
9.10.7 Minimizing offset voltages 114
9.11 Field calibration 115
9.12 File name and resource errors 115
9.13 Information tables and settings (advanced) 115
9.13.1 Information tables directories 116
9.13.1.1 Frequently used 117
9.13.1.2 Communications 117
General communications 117
PakBus communications 118
TCP_IP communications 118
Cellular communications 118
RF407-Series radio communications 118
Wi-Fi communications 119
9.13.1.3 Background calibration 119
9.13.1.4 Data 119
9.13.1.5 OS and hardware versions 119
9.13.1.6 Power monitoring 119
9.13.1.7 Security 119
9.13.1.8 Signatures 119
9.13.2 Information tables and settings descriptions 120
9.13.2.1 DataTableInfo table system information and settings 120
9.13.2.2 Status Table system information and settings 121
9.13.2.3 Device Configuration Utility settings 127
Cellular settings 145
RF407-series radio settings 152
Wi-Fi settings 157

10. Specifications 163

10.1 System specifications 163

Table of Contents - vi
10.2 Physical specifications 164
10.3 Power requirements 164
10.4 Power output specifications 166
10.5 Analog measurements specifications 167
10.5.1 Voltage measurements 167
10.5.2 Resistance measurements specifications 169
10.5.3 Period-averaging measurement specifications 169
10.5.4 Current-loop measurement specifications 170
10.6 Pulse measurement specifications 170
10.6.1 Switch-closure input 170
10.6.2 High-frequency input 171
10.6.3 Low-level ac input 171
10.6.4 Quadrature input 171
10.7 Digital input/output specifications 171
10.7.1 Pulse-width modulation specifications 172
10.8 Communications specifications 172
10.8.1 Wi-Fi option specifications 173
10.8.2 RF radio option specifications 173
10.8.3 Cellular option specifications 175
10.8.3.1 -CELL200 (International) 175
10.8.3.2 -CELL205 (North America) 176
10.8.3.3 -CELL210 (United States) 176
10.8.3.4 -CELL215 (EMEA) 176
10.8.3.5 -CELL220 (Australia and New Zealand) 177
10.9 Standards compliance specifications 177

11. Glossary 179

12. Index 218

Table of Contents - vii

1. Data acquisition system
components
A basic data acquisition system consists of sensors, measurement hardware, and a computer with
programmable software. The objective of a data acquisition system should be high accuracy,
high precision, and resolution as high as appropriate for a given application.
The components of a basic data acquisition system are shown in the following figure.

Following is a list of typical data acquisition system components:

l Sensors - Electronic sensors convert the state of a phenomenon to an electrical signal (see
Sensors (p. 2) for more information).
l Datalogger - The datalogger measures electrical signals or reads serial characters. It con-
verts the measurement or reading to engineering units, performs calculations, and reduces
data to statistical values. Data is stored in memory to await transfer to a computer by way of
an external storage device or a communications link.
l Data Retrieval and Communications - Data is copied (not moved) from the datalogger, usu-
ally to a computer, by one or more methods using datalogger support software. Most com-
munications options are bi-directional, which allows programs and settings to be sent to
the datalogger. For more information, see Sending a program to the datalogger (p. 35).

1. Data acquisition system components 1

l Datalogger Support Software - Software retrieves data, sends programs, and sets settings.
The software manages the communications link and has options for data display.
l Programmable Logic Control - Some data acquisition systems require the control of
external devices to facilitate a measurement or to control a device based on measurements.
This datalogger is adept at programmable logic control. See Programmable logic control
(p. 12) for more information.

1.1 Sensors
Sensors transduce phenomena into measurable electrical forms by modulating voltage, current,
resistance, status, or pulse output signals. Suitable sensors do this with accuracy and precision.
Smart sensors have internal measurement and processing components and simply output a
digital value in binary, hexadecimal, or ASCII character form.
Most electronic sensors, regardless of manufacturer, will interface with the datalogger. Some
sensors require external signal conditioning. The performance of some sensors is enhanced with
specialized input modules. The datalogger, sometimes with the assistance of various peripheral
devices, can measure or read nearly all electronic sensor output types.
The following list may not be comprehensive. A library of sensor manuals and application notes
is available at www.campbellsci.com/support to assist in measuring many sensor types.

l Analog
o Voltage
o Current
o Strain
o Thermocouple
o Resistive bridge

l Pulse
o High frequency
o Switch-closure
o Low-level ac
o Quadrature

l Period average
l Vibrating wire (through interface modules)
l Smart sensors
o SDI-12
o RS-232
o Modbus
o DNP3
o TCP/IP (CR310 only)

1. Data acquisition system components 2

1.2 The CR300 Series Datalogger
CR300 series dataloggers are multi-purpose, compact, measurement and control dataloggers.
These small, low-cost, high-value dataloggers offer fast communications, low power require-
ments, built-in USB, and excellent analog input accuracy and resolution. They can measure most
hydrological, meteorological, environmental, and industrial sensors. They concentrate data,
make it available over varied networks, and deliver it using your preferred protocol. They also per-
form automated on-site or remote decision making for control and M2M communications.
CR300 series dataloggers are ideal for small applications requiring long-term remote monitoring
and control.

1.2.1 CR300 Series Product Line

The CR300 series product line consists of the CR300 and the CR310. The primary differences
between the CR300 and CR310 are that the CR310 offers removable terminals and a 10/100 Eth-
ernet connection.

The CR300 series can include Wi-Fi, cellular, or the following radio options for different regions:

l RF407: US and Canada

l RF412: Australia and New Zealand
l RF422: Europe

1.2.2 Overview
The CR300 series datalogger is the main part of a data acquisition system (see Data acquisition
system components (p. 1) for more information). It has a central-processing unit (CPU), analog
and digital measurement inputs, analog and digital outputs, and memory. An operating system
(firmware) coordinates the functions of these parts in conjunction with the onboard clock and
the CRBasic application program.
The CR300 series can simultaneously provide measurement and communications functions. Low
power consumption allows the datalogger to operate for extended time on a battery recharged
with a solar panel, eliminating the need for ac power. The CR300 series temporarily suspends

1. Data acquisition system components 3

operations when primary power drops below 9.6 V, reducing the possibility of inaccurate meas-
urements.

1.2.3 Operations
The CR300 series measures almost any sensor with an electrical response, drives direct com-
munications and telecommunications, reduces data to statistical values, performs calculations,
and controls external devices. After measurements are made, data is stored in onboard, non-
volatile memory. Because most applications do not require that every measurement be recorded,
the program usually combines several measurements into computational or statistical summaries,
such as averages and standard deviations.

1.2.4 Programs
A program directs the datalogger on how and when sensors are measured, calculations are
made, data is stored, and devices are controlled. The application program for the CR300 series is
written in CRBasic, a programming language that includes measurement, data processing, and
analysis routines, as well as the standard BASIC instruction set. For simple applications, Short Cut,
a user-friendly program generator, can be used to generate the program. For more demanding
programs, use the full featured CRBasic Editor.
If you are programming with CRBasic, you can utilize the extensive help available within the
CRBasic Editor (also see https://help.campbellsci.com/CRBasic/CR300/ for searchable, CRBasic
online help).

2. Wiring panel and terminal

The CR300 series wiring panel provides ports and removable terminals for connecting sensors,
power, and communications devices. It is protected against surge, over-voltage, over-current,
and reverse power. The wiring panel is the interface to most datalogger functions so studying it is
a good way to get acquainted with the datalogger. Functions of the terminals are broken down
into the following categories:

l Analog input
l Pulse counting
l Analog output
l Communications
l Digital I/O
l Power input

2. Wiring panel and terminal 4

l Power output
l Power ground
l Signal ground

Table 2-1: Analog input terminal functions

1 2 3 4 5 6
SE
┌ 1┐ ┌ 2┐ ┌ 3┐
DIFF
H L H L H L
Single-Ended Voltage ü ü ü ü ü ü
Differential Voltage H L H L H L
Ratiometric/Bridge ü ü ü ü ü ü
Thermocouple ü ü ü ü ü ü
Current Loop ü ü
Period Average ü ü ü ü

Table 2-2: Pulse counting terminal functions

Pulse Counting C1 C2 P_SW P_LL SE1 SE2 SE3 SE4 SE5 SE6
Switch-Closure ü ü ü
High Frequency ü ü ü ü ü ü ü ü
Low-level Ac ü
Quadrature ü ü ü ü

2. Wiring panel and terminal 5

Table 2-3: Analog output terminal functions
VX1 VX2
Switched Voltage Excitation ü ü

Table 2-4: Voltage1 output terminal functions

C1 C2 SE1-4 VX1 VX2 P_SW SW12V
3.3 Vdc ü ü ü ü
5 Vdc ü ü ü ü
12 Vdc ü
1 SE 1-4, P_SW, and C1-C2 have limited drive capacity

Table 2-5: Communications terminal functions

C1 C2 SE1-3 RS-232
SDI-12 ü ü
RS-232 ü
RS-232 0-5V ü ü
GPS Time Sync ü ü ü
GPS NMEA Sentences Rx Rx Rx
Communication functions also include Ethernet (CR310 only) and USB

Table 2-6: Digital I/O terminal functions

C1 C2 P_SW SE1 SE2 SE3 SE4 SE5 SE6
General I/O ü ü ü ü ü ü ü
Pulse-Width Modulation Output ü ü ü ü
Interrupt ü ü ü ü ü

2. Wiring panel and terminal 6

2.1 Power input
The datalogger requires a power supply. It can receive power from a variety of sources, operate
for several months on non-rechargeable batteries, and supply power to many sensors and
devices. The datalogger operates with external power connected to the green BAT and/or CHG
terminals on the face of the wiring panel. The positive power wire connects to +. The negative
wire connects to -. The power terminals are internally protected against polarity reversal and high
voltage transients.
In the field, the datalogger can be powered in any of the following ways:

l 10 to 18 Vdc applied to the BAT + and – terminals

l 16 to 32 Vdc applied to the CHG + and – terminals

To establish an uninterruptible power supply (UPS), connect the primary power source (often a
transformer, power converter, or solar panel) to the CHG terminals and connect a nominal 12 Vdc
sealed rechargeable battery to the BAT terminals. See Power budgeting (p. 89) for more inform-
ation.

WARNING:
Sustained input voltages in excess of 32 Vdc on CHG or BAT terminals can damage the tran-
sient voltage suppression.

Ensure that power supply components match the specifications of the device to which they are
connected. When connecting power, switch off the power supply, insert the connector, then turn
the power supply on. See Troubleshooting power supplies (p. 102) for more information.
Following is a list of CR300 series power input terminals and the respective power types sup-
ported.

l BAT terminals: Voltage input is 10 to 18 Vdc. This connection uses the least current since
the internal datalogger charging circuit is bypassed. If the voltage on the BAT terminals
exceeds 19 Vdc, power is shut off to certain parts of the datalogger to prevent damaging
connected sensors or peripherals.
l CHG terminals: Voltage input range is 16 to 32 Vdc. Connect a primary power source, such
as a solar panel or Vac-to-Vdc transformer, to CHG. The voltage applied to CHG terminals
must be at least 0.3 V higher than that needed to charge a connected battery. When within
the 16 to 32 Vdc range, it will be regulated to the optimal charge voltage for a lead acid bat-
tery at the current datalogger temperature, with a maximum voltage of approximately 15
Vdc. A battery need not be connected to the BAT terminals to supply power to the data-

2. Wiring panel and terminal 7

logger through the CHG terminals. The onboard charging regulator is designed for effi-
ciently charging lead-acid batteries. It will not charge lithium or alkaline batteries.
l USB port: 5 Vdc via USB connection. If power is also provided with BAT or CHG, power will
be supplied by whichever has the highest voltage. If USB is the only power source, then the
SW12 terminal will not be operational. When powered by USB (no other power supplies
connected) Status field Battery = 0. Functions that will be active with a 5 Vdc source
include sending programs, adjusting datalogger settings, and making some measurements.
The maximum excitation on VX1 and VX2 is reduced to 2500 mV.

NOTE:
The Status field Battery value and the destination variable from the Battery() instruction
(often called batt_volt or BattV) in the Public table reference the external battery
voltage. For information about the internal battery, see Internal battery (p. 86).

2.1.1 Power LED indicator

When the datalogger is powered, the Power LED will turn on according to power and program
states:

l Off: No power, no program running.

l 1 flash every 10 seconds: Powered from BAT, program running.
l 2 flashes every 10 seconds: Powered from CHG, program running.
l 3 flashes every 10 seconds: Powered via USB, program running.
l Always on: Powered, no program running.

2.2 Power output

The datalogger can be used as a power source for sensors and peripherals. Take precautions to
prevent damage to sensors or peripherals from over- or under-voltage conditions, and to min-
imize errors. Additionally, exceeding current limits causes voltage output to become unstable.
Voltage should stabilize once current is again reduced to within stated limits. The following are
available:

l Continuous 12 V: BAT + and – provide a connection to the unregulated, nominal 12 Vdc

battery. It may rise above or drop below the power requirement of the sensor or peripheral.
l SW12: program-controlled, switched 12 Vdc terminal. It is often used to power devices such
as sensors that require 12 Vdc during measurement. Voltage on a SW12 terminal will
change with datalogger supply voltage. CRBasic instruction SW12() controls the SW12 ter-
minal (see the CRBasic instruction for SW12() for more information).

2. Wiring panel and terminal 8

l VX terminals: supply precise output voltage used by analog sensors to generate high res-
olution and accurate signals. In this case, these terminals are regularly used with resistive-
bridge measurements (see Resistance measurements (p. 51) for more information). Using
the SWVX() instruction, VX terminals can also supply a selectable, switched, regulated 3.3
or 5 Vdc power source to power digital sensors and toggle control lines (see the CRBasic
instruction for SWVX() for more information).
l C , SE 1-4, and P_SWterminals: can be set low or high as output terminals(SE 1-4 and P_SW
to 3.3 V, and C to 5 V). With limited drive capacity, digital output terminals are normally
used to operate external relay-driver circuits. Drive current and high-state voltage levels
vary between terminals. See also Digital input/output specifications (p. 171).

2. Wiring panel and terminal 9

In the field, at a minimum, a proper earth ground will consist of a 5-foot copper-sheathed
grounding rod driven into the earth and connected to the large brass ground lug on the wiring
panel with a 14 AWG wire. In low-conductive substrates, such as sand, very dry soil, ice, or rock, a
single ground rod will probably not provide an adequate earth ground. For these situations,
search for published literature on lightning protection or contact a qualified lightning-protection
consultant.
In laboratory applications, locating a stable earth ground is challenging, but still necessary. In
older buildings, new Vac receptacles on older Vac wiring may indicate that a safety ground exists
when, in fact, the socket is not grounded. If a safety ground does exist, good practice dictates to
verify that it carries no current. If the integrity of the Vac power ground is in doubt, also ground
the system through the building plumbing, or use another verified connection to earth ground.
See also:

l Minimizing ground loop errors (p. 103)

l Minimizing ground potential differences (p. 105)

2.4 Communications ports

The datalogger is equipped with ports that allow communications with other devices and net-
works, such as:

l Computers
l Smart sensors
l Modbus and DNP3 networks
l Ethernet (CR310)
l Modems
l Campbell Scientific PakBus® networks
l Other Campbell Scientific dataloggers

Campbell Scientific datalogger communications ports include:

l RS-232
l USB
l Ethernet
l C terminals

2.4.1 USB port

One USB port supports communicating with a computer through datalogger support software or
through virtual Ethernet (RNDIS), and provides 5 Vdc power to the datalogger (powering
through the USB port has limitations - details are available in the specifications). The datalogger

2. Wiring panel and terminal 10

USB port does not support USB flash or thumb drives. Although the USB connection supplies 5 V
power, a 12 Vdc battery will be needed for field deployment.

2.4.2 Ethernet port

CR310 models include one The RJ45 10/100 Ethernet port is used for IP communications.

2.4.3 C terminals for communications

C terminals are configurable for the following communications types:

l SDI-12
l RS-232 (0 to 5 V)

Some communications types require more than one terminal, and some are only available on spe-
cific terminals. This is shown in the datalogger specifications.

2.4.3.1 SDI-12 ports

SDI-12 is a 1200 baud protocol that supports many smart sensors. C1 and C2 can each be con-
figured as an SDI-12 communications port. Maximum cable lengths depend on the number of
sensors connected, the type of cable used, and the environment of the application. Refer to the
sensor manual for guidance.
For more information, see SDI-12 communications (p. 76).
See also Communications specifications (p. 172).

2.4.4 RS-232 Port

RS-232 represents a loose standard defining how two computing devices can communicate with
each other. For instruction on setting up RS-232 communications with a computer, see USB or
RS-232 communications (p. 15).
One nine-pin DCE port, labeled RS-232, normally is used to communicate with a computer run-
ning datalogger support software, to connect a modem, or to read a smart sensor. The RS-232
port functions as either a DCE or DTE device. The most common use of the RS-232 port is as a
connection to a computer DTE device (using a standard DB9-to-DB9 cable). Pins 1, 4, 6, and 9
function differently than a standard DCE device to accommodate a connection to a modem or
other DCE device via a null modem cable. For the RS-232 port to function as a DTE device, a null
modem adapter is required.
RS-232 communications normally operate well up to a transmission cable capacitance of 2500
picofarads, or approximately 50 feet of commonly available serial cable.

2. Wiring panel and terminal 11

2.4.4.1 RS-232 Power States
Under normal operation, the RS-232 port is powered down waiting for input. Upon receiving
input, there is a 40-second software timeout before shutting down. The 40-second timeout is
generally circumvented when communicating with datalogger support software because it sends
information as part of the protocol that lets the datalogger know it can shut down the port.
When in sleep mode, hardware is configured to detect activity and wake up. Sleep mode may
lose the first character of the incoming data stream. PakBus takes this into consideration in the
"ring packets" that are preceded with extra sync bytes at the start of the packet. SerialOpen()
leaves the interface powered-up, so no incoming bytes are lost.
When the datalogger has data to send via RS-232, if the data is not a response to a received
packet, such as sending a beacon, it will power up the interface, send the data, and return to
sleep mode without a 40 second timeout.
Wiring panel and terminal (p. 4)

2.5 Programmable logic control

The datalogger can control instruments and devices such as:

l Controlling cellular modem or GPS receiver to conserve power.

l Triggering a water sampler to collect a sample.
l Triggering a camera to take a picture.
l Activating an audio or visual alarm.
l Moving a head gate to regulate water flows in a canal system.
l Controlling pH dosing and aeration for water quality purposes.
l Controlling a gas analyzer to stop operation when temperature is too low.
l Controlling irrigation scheduling.

Control decisions can be based on time, an event, or a measured condition. Controlled devices
can be physically connected to C, VX, SE1 -SE4, P_SW, or SW12 terminals. Short Cut has pro-
visions for simple on/off control. Control modules and relay drivers are available to expand and
augment datalogger control capacity.

l C terminals are selectable as binary inputs, control outputs, or communication ports. These
terminals can be set low (0 Vdc) or high (5 Vdc) using the PortSet() or WriteIO()
instructions (see PortSet() and WriteIO() in the CRBasic help for more information).
Other functions include device-driven interrupts, asynchronous communications and SDI-
12 communications. A C terminal configured for digital I/O is normally used to operate an
external relay-driver circuit because the terminal itself has limited drive capacity.

2. Wiring panel and terminal 12

l VX terminals can be set low or high using the PortSet() or SWVX() instruction (see
PortSet() and SWVX() in the CRBasic help for more information).
l SW12 terminals can be set low (0 V) or high (12 V) using the SW12() instruction (see SW12
()in the CRBasic help for more information).

The following image illustrates a simple application wherein a C terminal configured for digital
input, and another configured for control output are used to control a device (turn it on or off)
and monitor the state of the device (whether the device is on or off).

In the case of a cell modem, control is based on time. The modem requires 12 Vdc power, so con-
nect its power wire to a datalogger SW12 terminal. The following code snip turns the modem on
for the first ten minutes of every hour using the TimeIsBetween() instruction embedded in
an If/Then logic statement:
If TimeIsBetween (0,10,60,Min)Then
SW12(1) 'Turn phone on.
Else
SW12(0) 'Turn phone off.
EndIf

2. Wiring panel and terminal 13

3. Setting up the datalogger
The basic steps for setting up your datalogger to take measurements and store data include:

1. Configuring your communications connection.

2. Testing communications (optional).
3. Connecting the datalogger to the computer.
4. Creating a program.
5. Sending that program to the datalogger.

3.1 Setting up communications with the

datalogger
The first step in setting up and communicating with your datalogger is to configure your con-
nection. Communications peripherals, dataloggers, and software must all be configured for com-
munications. Additional information is found in your specific peripheral manual, and the
datalogger support software manual and help.
The default settings for the datalogger allow it to communicate with a computer via USB, RS-232,
or Ethernet (on CR310 models). For other communications methods or more complex applic-
ations, some settings may need adjustment. Settings can be changed through Device Con-
figuration Utility or through datalogger support software.
You can configure your connection using any of the following options. The simplest is via USB.
For detailed instruction, see:

l USB or RS-232 communications (p. 15)

l Virtual Ethernet over USB (RNDIS) (p. 16)
l Ethernet communications (p. 17) (CR310 models only)
l Wi-Fi communications (p. 20) (WIFI models only)
l Cellular Communications (p. 23) (CELL models only)
l Radio communications (p. 26) (RF models only)

For other configurations, see the LoggerNet EZSetup Wizard help. Context-specific help is given
in each step of the wizard by clicking the Help button in the bottom right corner of the window.
For complex datalogger networks, use Network Planner.

3. Setting up the datalogger 14

3.1.1 USB or RS-232 communications
Setting up a USB or RS-232 connection is a good way to begin communicating with your data-
logger. Because these connections do not require configuration (like an IP address), you need
only set up the communications between your computer and the datalogger. Use the following
instructions or watch a video.

Initial setup instruction follows. These settings can be revisited using the datalogger support soft-
ware Edit Datalogger Setup option .

1. Using datalogger support software, launch the EZSetup Wizard.

l PC200W and PC400 users, click Add Datalogger .
l LoggerNet users, click Setup , click the View menu to ensure you are in the EZ (Sim-
plified) view, then click Add Datalogger.
2. Click Next.
3. Select your datalogger from the list, type a name for your datalogger (for example, a site or
project name), and click Next.
4. If prompted, select the Direct Connect connection type and click Next.
5. If this is the first time connecting this computer to a CR300 series via USB, click Install
USB Driver, select your datalogger, click Install, and follow the prompts to install the
USB drivers.
6. Plug the datalogger into your computer using a USB or RS-232 cable. The USB connection
supplies 5 V power as well as a communications link, which is adequate for setup, but a 12V
battery will be needed for field deployment. If using RS-232, external power must be
provided to the datalogger.

NOTE:
The Power LED on the datalogger indicates the program and power state. Because the
datalogger ships with a program set to run on power-up, the Power LED flashes 3 times
every 10 seconds when powered over USB. When powered with a 12 V battery, it flashes
1 time every 10 seconds.

7. From the COM Port list, select the COM port used for your datalogger.
8. USB and RS-232 connections do not typically require a COM Port Communication Delay -
this allows time for the hardware devices to "wake up" and negotiate a communications
link. Accept the default value of 00 seconds and click Next.
9. The baud rate and PakBus address must match the hardware settings for your datalogger.

3. Setting up the datalogger 15

The default PakBus address is 1. A USB connection does not require a baud rate selection.
RS-232 connections default to 115200 baud.

NOTE:
Unlike the RS-232 port on some other Campbell Scientific dataloggers that autobaud,
the CR300 RS-232 port does not. If the hardware and software settings for baud rate
and PakBus address do not match, you will not be able to connect.

10. Set an Extra Response Time if you have a difficult or marginal connection and you want
the datalogger support software to wait a certain amount of time before returning a com-
munication failure error.
11. LoggerNet and PC400 users can set a Max Time On-Line to limit the amount of time the
datalogger remains connected. When the datalogger is contacted, communication with it
is terminated when this time limit is exceeded. A value of 0 in this field indicates that there
is no time limit for maintaining a connection to the datalogger.
12. Click Next.
13. By default, the datalogger does not use a security code or a PakBus encryption key. There-
fore, the Security Code can be set to 0 and the PakBus Encryption Key can be left blank. If
either setting has been changed, enter the new code or key. See Datalogger security (p. 82)
for more information.
14. Click Next.
15. Review the Communication Setup Summary. If you need to make changes, click Previous to
return to a previous window and change the settings.

Setup is now complete, and the EZSetup Wizard allows to you click Finish or click Next to test
communications, set the datalogger clock, and send a program to the datalogger. See Testing
communications and completing EZ Setup (p. 32) for more information.

3.1.2 Virtual Ethernet over USB (RNDIS)

CR300 series dataloggers with OS version 6 or greater support RNDIS (virtual Ethernet over USB).
This allows the datalogger to communicate via TCP/IP over USB. Watch a video or use the fol-
lowing instructions.

3.1.2.1 Connecting to your datalogger via RNDIS

3. Setting up the datalogger 16

NOTE:
Ensure the datalogger is connected directly to the computer USB port (not to a
USB hub). We recommended always using the same USB port on your computer.

2. Physically connect your datalogger to your computer using a USB cable, then open Device
Configuration Utility and select your datalogger.
3. Select the communication port used to communicate with the datalogger from the COM
Port list.
4. Press Connect, click the Settings Editor tab >Advanced sub-tab > USB Configuration list >
Virtual Ethernet (RNDIS).
5. Click Apply.
6. Retrieve your IP Address. On the bottom, left side of the screen, select Use IP Connection,
then click the browse button next to the Communication Port box. Note the IP Address
(default is 192.168.66.1). If you have multiple dataloggers in your network, more than one
datalogger may be returned. Ensure you select the correct datalogger by verifying the data-
logger serial number or station name (if assigned).
7. A virtual IP address can be used to connect to the datalogger using Device Configuration
Utility or other computer software, or to view the datalogger internal web page in a
browser. To view the web page, open a browser and enter www.linktodevice.com or the IP
address you retrieved in the previous step (for example, 192.168.66.1) into the address bar.

To secure your datalogger from others who have access to your network, we recommend that you
set security and establish access permissions using .csipasswd. For more information, see
Creating a .csipasswd file (p. 84).

3.1.3 Ethernet communications

The CR310 offers a 10/100 Ethernet connection. Use Device Configuration Utility to enter the data-
logger IP Address, Subnet Mask, and IP Gateway address. After this, use the EZSetup Wizard to
set up communications with the datalogger. If you already have the datalogger IP information,
you can skip these steps and go directly to Setting up Ethernet communications between the
datalogger and computer (p. 19).

3.1.3.1 Configuring datalogger Ethernet settings

3. Setting up the datalogger 17

2. Connect an Ethernet cable to the 10/100 Ethernet port on the datalogger. The yellow and
green Ethernet port LEDs display activity approximately one minute after connecting. If you
do not see activity, contact your network administrator. For more information, see Ethernet
LEDs (p. 18).
3. Using datalogger support software (LoggerNet, PC400, or PC200W), open Device Con-
figuration Utility ( ).
4. Select the CR300 Series datalogger from the list
5. Select the port assigned to the datalogger from the Communication Port list. If connecting
via Ethernet, select Use IP Connection.
6. By default, this datalogger does not use a PakBus encryption key; so, the PakBus Encryp-
tion Key box can be left blank. If this setting has been changed, enter the new code or key.
See Datalogger security (p. 82) for more information.

7. Click Connect.
8. On the Deployment tab, click the Ethernet subtab.
9. The Ethernet Power setting allows you to reduce the power consumption of the datalogger.
If there is no Ethernet connection, the datalogger will turn off its Ethernet interface for the
time specified before turning it back on to check for a connection. Select Always On, 1
Minute, or Disable.
10. Enter the IP Address, Subnet Mask, and IP Gateway. These values should be provided by
your network administrator. A static IP address is recommended. If you are using DHCP,
note the IP address assigned to the datalogger on the right side of the window. When the
IP Address is set to the default, 0.0.0.0, the information displayed on the right side of the
window updates with the information obtained from the DHCP server. Note, however, that
this address is not static and may change. An IP address here of 169.254.###.### means
the datalogger was not able to obtain an address from the DHCP server. Contact your net-
work administrator for help.
11. Apply to save your changes.

3.1.3.2 Ethernet LEDs

When the datalogger is powered, and Ethernet Power setting is not disabled, the 10/100 Ethernet
LEDs will show the Ethernet activity:

l Solid Yellow: Valid Ethernet link.

l No Yellow: Invalid Ethernet link.
l Flashing Yellow: Ethernet activity.
l Solid Green: 100 Mbps link.
l No Green: 10 Mbps link.

3. Setting up the datalogger 18

3.1.3.3 Setting up Ethernet communications between the datalogger
and computer
Once you have configured the Ethernet settings or obtained the IP information for your data-
logger, you can set up communications between your computer and the datalogger over Eth-
ernet.
This procedure only needs to followed once per datalogger. However, these settings can be
revised using the datalogger support software Edit Datalogger Setup option ( ).

1. Using datalogger support software, open EZSetup.

l PC400 users, click the Add Datalogger button ( ).
l LoggerNet users, select Setup ( ) from the Main category on the toolbar, click the
View menu to ensure you are in the EZ (Simplified) view, then click the Add Data-
logger button.

NOTE:
PC200W does not support IP connections.

2. Click Next.
3. Select the CR300 Series from the list, enter a name for your datalogger (for example, a site
or project name), Next.
4. Select the IP Port connection type and click Next.
5. Type the datalogger IP address followed by a colon, then the port number of the data-
logger in the Internet IP Address box (these were set up through the Ethernet com-
munications (p. 17)) step. They can be accessed in Device Configuration Utility on the
Ethernet subtab. Leading 0s must be omitted. For example:
l IPv4 addresses are entered as 192.168.1.2:6785

l IPv6 addresses must be enclosed in square brackets. They are entered as [2001:d-

b8::1234:5678]:6785
6. The PakBus address must match the hardware settings for your datalogger. The default
PakBus address is 1.
l Set an Extra Response Time if you want the datalogger support software to wait a cer-

tain amount of time before returning a communications failure error.

l LoggerNet and PC400 users can set a Max Time On-Line to limit the amount of time

the datalogger remains connected. When the datalogger is contacted, com-

munications with it is terminated when this time limit is exceeded. A value of 0 in this
field indicates that there is no time limit for maintaining a connection to the data-
logger. Next.
7. By default, the datalogger does not use a security code or a PakBus encryption key. There-
fore the Security Code can be set to 0 and the PakBus Encryption Key can be left blank. If

3. Setting up the datalogger 19

either setting has been changed, enter the new code or key. See Datalogger security (p.
82). Next.
8. Review the Communication Setup Summary. If you need to make changes, click Previous to
return to a previous window and change the settings.

Setup is now complete, and the EZSetup Wizard allows you Finish or select Next. The Next steps
take you through testing communications, setting the datalogger clock, and sending a program
to the datalogger. See Testing communications and completing EZ Setup (p. 32) for more inform-
ation.

3.1.4 Wi-Fi communications

By default, CR300 series-WIFI dataloggers are configured to host a Wi-Fi network. The Log-
gerLink mobile app for iOS and Android can be used to connect with a CR300 series-WIFI. Up to
eight devices can connect to a network created by a CR300 series. The setup follows the same
steps shown in this video: CR6-WIFI Datalogger - Setting Up a Network.

NOTE:
The user is responsible for emissions if changing the antenna type or increasing the gain.

3.1.4.1 Configuring the datalogger to host a Wi-Fi network

By default, CR300-WIFI dataloggers are configured to host a Wi-Fi network. If the settings have
changed, you can follow these instructions to reconfigure the datalogger:

1. Ensure your CR300-WIFI is connected to an antenna and power.

2. Using Device Configuration Utility, connect to the datalogger.
3. On the Deployment tab, click the Wi-Fi sub-tab.
4. In the Configuration list, select the Create a Network option.
5. Optionally, set security on the network to prevent unauthorized access by typing a pass-
word in the Password box (recommended).
6. Apply your changes.

3.1.4.2 Connecting your computer to the datalogger over Wi-Fi

1. Open the Wi-Fi network settings on your computer.

3. Setting up the datalogger 20

2. Select the Wi-Fi-network hosted by the datalogger. The default name is CR300 followed by
the serial number of the datalogger. In the previous image, the Wi-Fi network is CRxxx.
3. If you set a password, select the Connect Using a Security Key option (instead of a PIN) and
type the password you chose.
4. Connect to this network.

3.1.4.3 Setting up Wi-Fi communications between the datalogger and

the datalogger support software
1. Using LoggerNet or PC400, click Add Datalogger to launch the EZSetup Wizard. For
LoggerNet users, you must first click Setup , then View menu to ensure you are in the EZ
(Simplified) view, then click Add Datalogger .

NOTE:
PC200W does not support IP connections.

2. Select the IP Port connection type and click Next.

3. In the Internet IP Address field, type 192.168.67.1. This is the default datalogger
IP address created when the CR300-WIFI creates a network.
4. Click Next.

3. Setting up the datalogger 21

5. The PakBus address must match the hardware settings for your datalogger. The default
PakBus address is 1.
l Set an Extra Response Time if you want the datalogger support software to wait a cer-

tain amount of time before returning a communication failure error. This can usually
be left at 00 seconds.
l You can set a Max Time On-Line to limit the amount of time the datalogger remains

connected. When the datalogger is contacted, communication with it is terminated

when this time limit is exceeded. A value of 0 in this field indicates that there is no
time limit for maintaining a connection to the datalogger.
6. Click Next.
7. By default, the datalogger does not use a security code or a PakBus encryption key. There-
fore, the Security Code can be left at 0 and the PakBus Encryption Key can be left blank. If
either setting has been changed, enter the new code or key. See Datalogger security (p. 82)
for more information.
8. Click Next.
9. Review the Communication Setup Summary. If you need to make changes, click the Pre-
vious button to return to a previous window and change the settings.

Setup is now complete, and the EZSetup Wizard allows you click Finish or click Next to test com-
munications, set the datalogger clock, and send a program to the datalogger. See Testing com-
munications and completing EZ Setup (p. 32) for more information.

3.1.4.4 Configuring dataloggers to join a Wi-Fi network

By default, the CR300-WIFI dataloggers are configured to host a Wi-Fi network. To set them up
to join a network:

1. Ensure your CR300-WIFI is connected to an antenna and power.

2. Using Device Configuration Utility, connect to the datalogger.
3. On the Deployment tab, click the Wi-Fi sub-tab.
4. In the Configuration list, select the Join a Network option.
5. Next to the Network Name (SSID) box, click Browse to search for and select a Wi-Fi net-
work.
6. If the network is a secured network, you must enter the password in the Password box and
add any additional security in the Enterprise section of the window.
7. Enter the IP Address, Network Mask, and Gateway. These values should be provided by
your network administrator. A static IP address is recommended.
l Alternatively, you can use an IP address assigned to the datalogger via DHCP. To do

this, make sure the IP Address is set to 0.0.0.0. Click Apply to save the con-
figuration changes. Then reconnect. The IP information obtained through DHCP is
updated and displayed in the Status section of the Wi-Fi subtab. Note, however, that

3. Setting up the datalogger 22

this address is not static and may change. An IP address here of 169.254.###.###
means the datalogger was not able to obtain an address from the DHCP server.
Contact your network administrator for help.
8. Apply your changes.
9. For each datalogger you want to connect to network, you must follow the instruction in Set-
ting up Wi-Fi communications between the datalogger and the datalogger support soft-
ware (p. 21), using the IP address used to configure that datalogger (step 7 in this
instruction).

3.1.4.5 Wi-Fi LED indicator

When the datalogger is powered, the Wi-Fi LED will turn on according to Wi-Fi communication
states:

l Off: Insufficient power, Wi-Fi disabled, or datalogger failed to join or create a network
(periodic retries will occur).
l Solid for 2 seconds: Attempting to join or create a network.
l Flashing: Successfully joined or created a network. Flashes with network activity and once
every four seconds.

3.1.5 Cellular Communications

In addition to the IP capabilities inherent in the cellular connection (CELL models only), you can
use the SMSSend() and SMSRecv() instructions to send SMS messages and receive and store
messages in a string variable. Note that the SMSSend() and SMSRecv() instructions require a
cellular account that includes text messaging capabilities (many cellular data accounts do not
include this option). Contact your cellular provider for more information on your plan. See the
CRBasic help for further instruction on SMSSend() and SMSRecv().

NOTE:
See Cellular option specifications (p. 175) for more information and carrier compatibility.

1. Obtain an access point name (APN) from your cellular network provider. You will need this
to configure the connection.
2. Insert a supported SIM card into the back of the unit.

3. Setting up the datalogger 23

3. Ensure your CR300 series-CELL is connected to an antenna and power.
4. Plug the datalogger into your computer using a USB or RS-232 cable. Supply power to the
datalogger. Note that a USB connection supplies 5V power (as well as a communications
link), which is adequate for setup but a 12V battery will be needed to connect to the net-
work and obtain the IP address.
5. If this is the first time connecting this computer to your datalogger via USB, you need to
update the USB drivers. Open Device Configuration Utility, select your datalogger, and on
the main page, click Install USB Driver.
6. If you have a Fixed IP SIM Card and know the IP address of the card, proceed to step 7.
Otherwise:
l Connect to the datalogger using Device Configuration Utility.

l Click the Deployment tab, then click the Cellular sub-tab. Type your APN into the

box, then click Apply. This will disconnect the datalogger from Device Configuration
Utility.
l Reconnect the datalogger using Device Configuration Utility. From the same sub-tab,

copy the IP address from the Cellular Network Status box, then click the Disconnect
button.
7. Using datalogger support software, launch the EZSetup Wizard.
l PC400 users, click the Add Datalogger button ( ).
l LoggerNet users, click the Setup ( ) option, click the View menu to ensure you are
in the EZ (Simplified) view, then click the Add Datalogger button.
l
NOTE:
PC200W does not allow IP connections.

8. Click Next.
9. Select the datalogger from the list, type a name for your datalogger (for example, a site or
project name), and click Next.
10. Select the IP Port connection type and click Next.

3. Setting up the datalogger 24

11. Type or paste the IP Address (see step 6) into the box, append it with a colon and port num-
ber 6785 (for example 192.168.67.1:6785), and click Next.
12. The PakBus address must match the hardware settings for your datalogger. The default
PakBus address is 1.
l Set an Extra Response Time if you want the datalogger support software to wait a cer-

tain amount of time before returning a communications failure error.

l You can set a Max Time On-Line to limit the amount of time the datalogger remains

connected. When the datalogger is contacted, communication with it is terminated

when this time limit is exceeded. A value of 0 in this field indicates that there is no
time limit for maintaining a connection to the datalogger.
13. Click Next.
14. By default, the datalogger does not use a security code or a PakBus encryption key. There-
fore, the Security Code can be set to 0 and the PakBus Encryption Key can be left blank. If
either setting has been changed, enter the new code or key. See Datalogger security (p. 82)
for more information.
15. Click Next.
16. Review the Communication Setup Summary. If you need to make changes, click the Pre-
vious button to return to a previous window and change the settings.
17. Click Next to test communications and set the clock (see Testing communications and com-
pleting EZ Setup (p. 32) for more information).
18. Connect to the datalogger using datalogger support software (see Connecting the data-
logger to a computer (p. 33)).

3.1.5.1 Cellular (TX/RX) LED Indicator

When the datalogger is powered, the cellular LED will turn on according to cellular modem com-
munications states:

l Off: Cellular modem off, insufficient power, or failure to establish a connection with the
provider (periodic retries will occur).
l Solid: Cellular modem is powering up and attempting to establish a connection with a pro-
vider.
l Quick Flashing (approximately 1 second duration): Indicates successful network regis-
tration.
l Flashing: Flashes with network activity.

See also Cellular option specifications (p. 175). For Device Configuration Settings Editor Cellular
settings, see Cellular communications (p. 118).

3. Setting up the datalogger 25

3.1.6 Radio communications
CR300 series-RF dataloggers include radio options. The RF407-series frequency-hopping spread-
spectrum (FHSS) radio options include the RF407, RF412, RF422, and RF427. RF407-series are
designed for license-free use in several countries:

l The RF407 option has a 902 to 928 MHz operating-frequency range appropriate for use in
the United States and Canada (FCC / IC compliant).
l The RF412 option has a 915 to 928 MHz operating-frequency range appropriate for use in
Australia and New Zealand (ACMA compliant).
l The RF422 option has an 863 to 873 MHz operating-frequency range appropriate for use in
most of Europe and some of Asia (ETSI compliant).
l The RF427 option has a 902 to 907.5 MHz/915 to 928 MHz operating-frequency range
appropriate for use in Brazil.

NOTE:
This equipment has been tested and found to comply with the limits for a Class A digital
device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio frequency energy and, if
not installed and used in accordance with the instruction manual, may cause harmful inter-
ference to radio communications. Operation of this equipment in a residential area is likely to
cause harmful interference in which case the user will be required to correct the interference
at his or her own expense.

Radio options cannot be mixed within a network. An RF407 can only be used with other RF407-
type radios, an RF412 can only be used with other RF412-type radios, an RF422 can only be used
with other RF422-type radios, and an RF427 can only be used with other RF427-type radios.
Throughout these instructions, RF407-series represents each of the RF407, RF412, RF422, and
RF427 radio options, unless otherwise noted. Similarly, the RF407-series standalone, or inde-
pendent radio represents each of the RF407, RF412, RF422, and RF427 models, unless otherwise
noted.

3.1.6.1 Configuration options

The most frequently used configurations with the RF-series datalogger and RF-series radio
include the following:

3. Setting up the datalogger 26

For detailed instruction, see:

l RF407-Series radio communications with one or more dataloggers (p. 27)

l RF407-Series radio communications with multiple dataloggers using one datalogger as a
router (p. 29)

3.1.6.2 RF407-Series radio communications with one or more data-

loggers
To configure an RF407-series radio to communicate with the datalogger, you must complete the
following steps (instruction follows):

l Ensure your datalogger and RF407-series radio are connected to an antenna and power.
l Configure the connection to the RF407-series device using Device Configuration Utility.
l If you are connecting to multiple dataloggers, you will have to assign unique PakBus
addresses to each datalogger using Device Configuration Utility. (Connect to each data-
logger, set the PakBus Address on the Deployment | Datalogger tab.)
l Use datalogger support software to set up communications between the RF407-series radio
and the dataloggers.

NOTE:
This procedure assumes the RF407 series devices are using factory default settings.

3. Setting up the datalogger 27

Configuring the RF407-Series radio
Configure the RF407-Series radio connected to the computer (see image in Configuration
options (p. 26) for reference).

1. Ensure your RF407-series radio is connected to an antenna and power.

2. If connecting via USB for the first time, you must first install USB drivers using Device Con-
figuration Utility (select your radio, then on the main page, click Install USB Driver). Plug
the RF407-series radio to your computer using a USB or RS-232 cable.
3. Using Device Configuration Utility, select the Communication Port used for your radio and
connect to the RF407-series radio.
4. On the Main tab, set the Active Interface to USB or RS-232 (depending on how your com-
puter will be connected to the RF407-series radio).
5. Apply the changes.
6. Connect the RF407-Series radio to the computer communication port selected in the pre-
vious step.

Setting up communications between the RF407-Series datalogger and the com-

puter
These instructions provide an easy way to set up communications between the RF407-series data-
logger and the computer connected to the RF407-series radio (as configured in previous instruc-
tions). Follow these instructions multiple times to set up multiple dataloggers. In this case, each
datalogger must be given a unique PakBus address (see PakBus communications (p. 75) for more
information). For more complicated networks, it is recommended that you use Network Planner.

1. Supply 12 Vdc power to the datalogger.

2. Ensure the datalogger antenna is connected.
3. Using datalogger support software, launch the EZSetup Wizard and add the datalogger.
l PC200W and PC400 users, click Add Datalogger .
l LoggerNet users, click Setup , click the View menu to ensure you are in the EZ (Sim-
plified) view, then click Add Datalogger .
4. Click Next.
5. Select the CR300Series datalogger from the list, type a name for your datalogger (for
example, a site or project name), and click Next.
6. If prompted, select the Direct Connect connection type and click Next.
7. Select the communication port used to communicate with the RF407-series radio from the
COM Port list. (Note that the RF407-series radio to RF407-series datalogger link is not indic-
ated in the LoggerNet Setup Standard View.)

3. Setting up the datalogger 28

8. Accept the default value of 00 seconds in the COM Port Communication Delay - this box is
used to allow time for hardware devices to "wake up" and negotiate a communications
link. Click Next.
9. In the previous instruction "Configuring a Connection to an RF407-Series Radio," you were
asked to select an active interface option of USB or RS-232. If you selected USB as the act-
ive interface for the radio, you do not need to select a baud rate. If you selected RS-232, set
the baud rate to the one chosen during that step. The radio's default baud rate is 115200.
The PakBus address must match the hardware settings for your datalogger. The default
PakBus Address is 1.
10. Click Next.
11. By default, the datalogger does not use a security code or a PakBus encryption key. There-
fore, the Security Code can be left at 0 and the PakBus Encryption Key can be left blank. If
either setting has been changed, enter the new code or key. See Datalogger security (p. 82)
for more information.
12. Click Next.
13. Review the Communication Setup Summary. If you need to make changes, click the Pre-
vious button to return to a previous window and change the settings.

Setup is now complete, and the EZSetup Wizard allows you to click Finish or click Next to test
communications, set the datalogger clock, and send a program to the datalogger. See Testing
communications and completing EZ Setup (p. 32) for more information.
If you experience network communications problems, see Troubleshooting Radio Com-
munications (p. 100) for assistance.

3.1.6.3 RF407-Series radio communications with multiple dataloggers

using one datalogger as a router
This type of network configuration is useful for communicating around an obstacle, such as a hill
or building, or to reach longer distances.

To configure an RF407-series radio to communicate with multiple dataloggers through a router,

you must complete the following steps (instruction follows):

l Ensure your dataloggers and RF407-series radios are each connected to an antenna and
power.

3. Setting up the datalogger 29

l Configure your connection to the RF407-series devices using Device Configuration Utility.
l Assign unique PakBus addresses to each datalogger using Device Configuration Utility.
(Connect to each datalogger, and set the PakBus Address on the Deployment | Datalogger
tab.)
l Configure the datalogger acting as a router.
l Use datalogger support software to set up communications between the computer and the
dataloggers.

Configuring the RF407-Series radio

Configure the RF407-Series radio connected to the computer (see previous image for reference).

1. Ensure your RF407-series radio is connected to an antenna and power.

Configuring the datalogger acting as a router

1. Supply power to the datalogger. If connecting via USB for the first time, you must first
install USB drivers by using Device Configuration Utility (select your datalogger, then on
the main page, click Install USB Driver). Alternately, you can install the USB drivers using EZ
Setup. A USB connection supplies 5 V power (as well as a communication link), which is
adequate for setup, but a 12 V battery will be needed for field deployment. Ensure the data-
logger antenna is connected.
2. Using Device Configuration Utility, connect to the RF407-series datalogger that will serve
as a router.
3. On the Deployment|Datlogger tab, assign a unique PakBus Address (see PakBus com-
munications (p. 75) for more information).
4. On the Deployment tab, click the Com Ports Settings sub-tab.
5. From the Select the ComPort list, select RF.
6. Set the Beacon Interval to 60 seconds (or the amount of time you are willing to wait for the
leaf dataloggers in the network to be discovered).

3. Setting up the datalogger 30

NOTE:
A beacon is a packet broadcast at a specified interval intended to discover neighbor devices.

7. Set the Verify Interval to something slightly greater than the expected communications
interval between the router and the other (leaf) dataloggers in the network (for example,
90 seconds).
8. Click the Advanced sub-tab and set Is Router to True.
9. Apply your changes.

Adding routing datalogger to LoggerNet network

1. Using LoggerNet, click Setup and click the View menu to ensure you are in the Standard
view.
2. Click Add Root .
3. Click ComPort, then PakBusPort (PakBus Loggers), then CR300Series.
4. Click Close.
5. In the Entire Network pane on the left side of the window, select the ComPort.
6. On the Hardware tab on the right, click the ComPort Connection list and select the com-
munication port assigned to the RF407-series radio.
7. In the Entire Network pane on the left side of the window, select PakBusPort.
8. On the Hardware tab on the right, select the PakBus Port Always Open check box.
l If you would like to prevent the possibility of LoggerNet communicating with any

other dataloggers in the network without going through the router, set the Beacon
Interval to 00 h 00 m 00s.
9. In the Entire Network pane on the left side of the window, select the router datalogger
(CR300Series) from the list.
10. On the Hardware tab on the right, type the PakBus Address you assigned to the router data-
logger in Device Configuration Utility.
11. Optionally, click the Rename button ( ) to provide the datalogger a descriptive name.
12. Apply your changes.

Adding leaf dataloggers to the network

1. In the LoggerNet Standard Setup view (click the Setup ( ) option and click the View menu
to ensure you are in the Standard view), right-click on the router datalogger in the Entire
Network pane on the left side of the window and select CR300Series.
2. With the newly added datalogger selected in the Entire Network pane, set the PakBus
Address to the address that was assigned to the leaf datalogger in Device Configuration
Utility.
3. Click Rename. Enter a descriptive name for the datalogger.

3. Setting up the datalogger 31

4. Apply your changes.
5. Repeat these steps for each leaf datalogger in the network.

If you experience problems with network communications, see Troubleshooting Radio Com-
munications (p. 100) for assistance.

Using additional communications methods

Using similar instructions, a RF407-series datalogger can be used in a system with additional com-
munication methods. For example, in the following image, the router RF407-series datalogger
communicates with LoggerNet through an RV50 cellular modem connected to RF407-series data-
logger using the RS-232 port. The router RF407-series datalogger communicates with the leaf
RF407-series dataloggers over RF.

3.2 Testing communications and

completing EZ Setup
1. Using datalogger support software EZ Setup, access the Communication Test window. This
window is accessed during EZ Setup (see USB or RS-232 communications (p. 15) for more
information). Alternatively, you can double-click a datalogger from the station list to open
the EZ Setup Wizard and access the Communication Test step from the left side of the win-
dow.
2. Ensure the datalogger is connected to the computer, select Yes to test communications,
then click Next to initiate the test. To troubleshoot an unsuccessful test, see Tips and
troubleshooting (p. 93).
3. With a successful connection, the Datalogger Clock window displays the time for both the
datalogger and the computer.
l The Adjusted Server Date/Time displays the current reading of the clock for the com-

puter or server running your datalogger support software. If the Datalogger

Date/Time and Adjusted Server Date/Time don't match, you can set the datalogger
clock to the Adjusted Server Date/Time by clicking Set Datalogger Clock.
l Use the Time Zone Offset to specify a positive or negative offset to apply to the com-

puter time when setting the datalogger clock. This offset will allow you to set the

3. Setting up the datalogger 32

clock for a datalogger that needs to be set to a different time zone than the time
zone of the computer (or to accommodate for changes in daylight saving time).
4. Click Next.
5. The datalogger ships with a default QuickStart program. If the datalogger does not have a
program, you can choose to send one by clicking Select and Send Program. Click Next.
6. LoggerNet only - Watch a video or use the following instructions:
l The Datalogger Table Output Files window displays the data tables available to be

collected from the datalogger and the output file name. By default, all data tables set
up in the datalogger program will be included for collection. Make note of the Out-
put File Name and location. Click Next.
l Check Scheduled Collection Enabled to have LoggerNet automatically collect data

from the datalogger according to a schedule. When the Base Date and Time are in
the past, scheduled collection will begin on the first Collection Interval. Click Next
twice.
7. Click Finish.

3.3 Connecting the datalogger to a

computer
Once you have configured your hardware connection (see Setting up communications with the
datalogger (p. 14), your datalogger and computer can communicate.

l PC200W and PC400 users, select the datalogger from the list and click Connect .
l LoggerNet users, select Main and click Connect on the LoggerNet toolbar, select the
datalogger from the Stations list, then Connect .

To disconnect, click Disconnect .

3.4 Creating a program in Short Cut

Use the Short Cut software to generate a program for your datalogger. Short Cut is included with
your datalogger support software.
Use the following instructions or watch a video.

3. Setting up the datalogger 33

1. Using datalogger support software, launch Short Cut.
l PC200W and PC400 users, click Short Cut .
l LoggerNet users, click Program then Short Cut .
2. Click Create New Program.
3. Select CR300 Series datalogger and click Next.

NOTE:
The first time Short Cut is run, a prompt will ask for a noise rejection choice. Select 60 Hz
Noise Rejection for North America and areas using 60 Hz ac voltage. Select 50 Hz Noise Rejec-
tion for most of the Eastern Hemisphere and areas that operate at 50 Hz.

A second prompt lists sensor support options. Campbell Scientific, Inc. (US) is usually the best
fit outside of Europe.

To change the noise rejection or sensor support option for future programs, use the Program
menu.

4. A list of Available Sensors and Devices and Selected Measurements Available for Output dis-
play. Battery voltage BattV and internal temperature PTemp_C are selected by default.
During operation, battery and temperature should be recorded at least daily to assist in
monitoring system status.
5. Use the Search feature or expand folders to locate your sensor or device. Double-click on a
sensor or measurement in the Available Sensors and Devices list to configure the device (if
needed) and add it to the Selected list.
6. If the sensor or device requires configuration, a window displays with configuration
options. Click Help at the bottom of the window to learn more about any field or option.
7. Click OK.
8. Click Wiring Diagram on the left side of the window to see how to wire the sensor to the
datalogger. With the power disconnected from the datalogger, insert the wires as directed
in the diagram. Ensure you clamp the terminal on the conductor, not the wire insulation.
Use the included flat-blade screwdriver to open/close the terminals.

9. Click Sensors on the left side of the window to return to the sensor selection window.
10. Use the Output Setup options to specify how often measurements are to be made and how
often outputs are to be stored. Note that multiple output intervals can be specified, one for
each output table (Table1 and Table2 tabs).
11. In the Table Name box, type a name for the table.
12. Select a Data Output Storage Interval.
13. Click Next.

3. Setting up the datalogger 34

14. Select the measurement from the Selected Measurements Available for Output list, then
click an output processing option to add the measurement to the Selected Measurements
for Output list.

15. Click Finish to compile the program. Replace the untitled.cr300 default name and click
Save.
16. If LoggerNet or other datalogger support software is running on your computer, and the
datalogger is connected to the computer (see Connecting the datalogger to a computer (p.
33) for more information), you can choose to send the program.

NOTE:
A good practice is to always retrieve data from the datalogger before sending a program; oth-
erwise, data may be lost. See Collecting data (p. 38) for detailed instruction.

If your data acquisition requirements are simple, you can probably create and maintain a data-
logger program exclusively with Short Cut. If your data acquisition needs are more complex, the
files that Short Cut creates are a great source for programming code to start a new program or
add to an existing custom program using CRBasic. See the CRBasic Editor help for detailed
information on program structure, syntax, and each instruction available to the datalogger.

NOTE:
Once a Short Cut generated program has been edited with CRBasic Editor, it can no longer
be modified with Short Cut.

3.5 Sending a program to the datalogger

The datalogger requires a CRBasic program to direct measurement, processing, control, and data
storage operations. The program file may use the extension .CR300 or .DLD.
A good practice is to always retrieve data from the datalogger before sending a program; oth-
erwise, data may be lost. To collect data using LoggerNet, connect to your datalogger and click
Collect Now . Some methods of sending a program give the option to retain data when

3. Setting up the datalogger 35

possible. Regardless of the program upload tool used, data will be erased when a new program is
sent if any change occurs to one or more data table structures in the following list:

l Data table name(s) l Number of bytes per field

l Data output interval or offset l Field type, size, name, or position
l Number of fields per record l Number of records in table

Use the following instructions or watch a video.

1. Connect the datalogger to your computer (see Connecting the datalogger to a computer
(p. 33) for more information).
2. Using your datalogger support software, click Send New or Send Program (located in the
Current Program section on the right side of the window).
3. Navigate to the the program, select it, and click Open.
4. Confirm that you would like to proceed and erase all data tables saved on the datalogger.
The program will send, compile, then display results.

After sending a program, it is a good idea to monitor the data to make sure sensors are taking
good measurements. See Working with data (p. 37) for more information.

3.5.1 Program run options

When sending a program via File Control, Short Cut, or CRBasic, you can choose to have pro-
grams Run on Power-up and Run Now. Run Now will run the program when it is sent to the data-
logger. Run on Power-up runs the program when the datalogger is powered up. Selecting both
Run Now and Run on Power-up will invoke both options.

3. Setting up the datalogger 36

4. Working with data
By default, the datalogger includes three tables: Public, Status, and DataTableInfo. Each of these
tables only contains the most recent measurements and information.

l The Public table is configured by the datalogger program, and updated at the scan interval
set within the datalogger program, It shows measurement and calculation results as they
are made.
l The Status table includes information about the health of the datalogger and is updated
only when viewed.
l The DataTableInfo table reports statistics related to data tables. It also only updates when
viewed.
l User-defined data tables update at the schedule set within the program.

For information on collecting your data, see Collecting data (p. 38).
Use these instructions or follow a tutorial to monitor real-time data.

PC200W and PC400 users, click Connect , then Monitor Data. When this tab is first opened for
a datalogger, values from the Public table are displayed. To view data from other tables, click
Add ( ), select a table or field from the list, then drag it into a cell on the Monitor Data tab.

4. Working with data 37

LoggerNet users, select the Main category and Connect on the LoggerNet toolbar, select the
datalogger from the Stations list, then click Connect . Once connected, select a table to view
using the Table Monitor box.

4.1 Collecting data

The datalogger writes to data tables based on intervals and conditions set in the CRBasic pro-
gram (see Creating data tables in a program (p. 43) for more information). After the program has
been running for enough time to generate data records, data may be collected by using data-
logger support software. During data collection, data is copied to the computer but still remains
on the datalogger. Collections may be done manually, or automatically through scheduled col-
lections set in LoggerNet Setup. Use these instruction or follow a tutorial.

4.1.1 Collecting data using LoggerNet

1. LoggerNet users, select Main and Connect on the LoggerNet toolbar, select the data-
logger from the Stations list, then click Connect .
2. Click Collect Now .
3. After the data is collected, the Data Collection Results window displays the tables collected
and where they are stored on the computer.
4. Select a data file, then View File to view the data. Viewing historic data (p. 39)

4.1.2 Collecting data using PC200W or PC400

1. PC200W and PC400 users, click Connect .
2. Select the Collect Data tab.

4. Working with data 38

3. Select an option for What to Collect. Either option creates a new file if one does not
already exist.
l New data from datalogger (Append to data files): Collects only the data in the selec-

ted tables stored since the last data collection and appends this data to the end of
the existing table files on the computer. This is the default, and most often used
option.
l All data from datalogger (Overwrite data files): Collects all of the data in the selected

tables and replaces the existing data files on the computer.

4. By default, all tables set up in the datalogger program are selected for collection.
5. Click Start Data Collection.
6. After the data is collected, the Data Collection Results window displays the tables collected
and where they are stored on the computer.
7. Select a data file, then View File to view the data. Viewing historic data (p. 39)

4.2 Viewing historic data

Open data files using View Pro. View Pro contains tools for reviewing data in tabular form as well
as several graphical layouts for visualization. Use these instructions or follow a tutorial.

Once the datalogger has had enough time to store multiple records, you should collect and
review the data.

1. To view the most recent data, connect the datalogger to your computer and collect your
data (see Collecting data (p. 38) for more information).
2. Open View Pro:
l LoggerNet users select Data and click View Pro on the LoggerNet toolbar.
l PC200W and PC400 users click View Data Files via View Pro .
3. Click Open , navigate to the directory where you saved your tables (the default directory
is C:\Campbellsci\[your datalogger software application]).

4. Working with data 39

4.3 About data tables
A data table is essentially a file that resides in datalogger memory (for information on data table
storage, see Data memory (p. 45)). The file consists of five or more rows. Each row consists of
columns, or fields. The first four rows constitute the file header. Subsequent rows contain data
records. Data tables may store individual measurements, individual calculated values, or summary
data such as averages, maximums, or minimums.
Typically, files are written to based on time or event. The number of data tables is limited to 20.
You can retrieve data based on a schedule or by manually choosing to collect data using data-
logger support software (see Collecting data (p. 38)).

Table 4-1: Example data

TOA5, MyStation, CR300, 1142, CR300.Std.01, CPU:MyTemperature.CR300, 1958, OneMin
TIMESTAMP RECORD BattV_Avg PTemp_C_Avg Temp_C_Avg
TS RN Volts Deg C Deg C
Avg Avg Avg
2016-03-08 14:24:00 0 13.68 21.84 20.71
2016-03-08 14:25:00 1 13.65 21.84 20.63
2016-03-08 14:26:00 2 13.66 21.84 20.63
2016-03-08 14:27:00 3 13.58 21.85 20.62
2016-03-08 14:28:00 4 13.64 21.85 20.52
2016-03-08 14:29:00 5 13.65 21.85 20.64

4.3.1 Table definitions

Each data table is associated with descriptive information, referred to as a“table definition,” that
becomes part of the file header (first few lines of the file) when data is downloaded to a com-
puter. Table definitions include the datalogger type and OS version, name of the CRBasic pro-
gram associated with the data, name of the data table (limited to 20 characters), and
alphanumeric field names.

4.3.1.1 Header rows

The first header row of the data table is the environment line, which consists of eight fields. The
following list describes the fields using the previous table entries as an example:

4. Working with data 40

l TOA5 - Table output format. Changed via LoggerNet Setup ( ) Standard View, Data Files
tab.
l MyStation - Station name. Changed via LoggerNet Setup, Device Configuration Utility, or
CRBasic program.
l CR300 - Datalogger model.
l 1142 - Datalogger serial number.
l CR300.Std.01 - Datalogger OS version.
l CPU:MyTemperature.CR300 - Datalogger program name. Changed by sending a new pro-
gram (see Sending a program to the datalogger (p. 35) for more information).
l 1958 - Datalogger program signature. Changed by revising a program or sending a new pro-
gram (see Sending a program to the datalogger (p. 35) for more information).
l OneMin - Table name as declared in the running program (see Creating data tables in a
program (p. 43) for more information).

The second header row reports field names. Default field names are a combination of the vari-
able names (or aliases) from which data is derived, and a three-letter suffix. The suffix is an abbre-
viation of the data process that outputs the data to storage. A list of these abbreviations follows
in Data processing abbreviations (p. 42).
If a field is an element of an array, the field name will be followed by a indices within parentheses
that identify the element in the array. For example, a variable named Values, which is declared
as a two-by-two array in the datalogger program, will be represented by four field names: Val-
ues(1,1), Values(1,2), Values(2,1), and Values(2,2). There will be one value in
the second header row for each scalar value defined by the table.
If the default field names are not acceptable to the programmer, the FieldNames() instruc-
tion can be used in the CRBasic program to customize the names. TIMESTAMP, RECORD,
BattV_Avg, PTemp_C_Avg, and Temp_C_Avg are the default field names in the previous
Example data (p. 40).
The third header row identifies engineering units for that field. These units are declared at the
beginning of a CRBasic program using the optional Units() declaration. In Short Cut, units are
chosen when sensors or measurements are added. Units are strictly for documentation. The data-
logger does not make use of declared units, nor does it check their accuracy.
The fourth header row reports abbreviations of the data process used to produce the field of
data.

4. Working with data 41

Table 4-2: Data processing abbreviations
Data processing name Abbreviation
Totalize Tot
Average Avg
Maximum Max
Minimum Min
Sample at Max or Min SMM
Standard Deviation Std
Moment MMT
Sample No abbreviation
Histogram1 Hst
Histogram4D H4D
FFT FFT
Covariance Cov
Level Crossing LCr
WindVector WVc
Median Med
ET ETsz
Solar Radiation (from ET) RSo
Time of Max TMx
Time of Min TMn

4.3.1.2 Data records

Subsequent rows are called data records. They include observed data and associated record keep-
ing. The first field is a time stamp (TS), and the second field is the record number (RN).
The time stamp shown represents the time at the beginning of the scan in which the data is writ-
ten. Therefore, in record number 3 in the previous Example data (p. 40), Temp_C_Avg shows the
average of the measurements taken over the minute beginning at 14:26:01 and ending at
14:27:00. As another example, consider rainfall measured every second with a daily total rainfall
recorded in a data table written at midnight. The record time stamped 2016-03-08 00:00:00 will
contain the total rainfall beginning at 2016-03-07 00:00:01 and ending at 2016-03-08 00:00:00.

4. Working with data 42

4.4 Creating data tables in a program
Data is stored in tables as directed by the CRBasic program. In Short Cut, data tables are created
in the Output steps (see Creating a program in Short Cut (p. 33)). Data tables are created within
the CRBasic datalogger program using the DataTable()/EndTable instructions. They are
placed after variable declarations and before the BeginProg instruction. Between DataT-
able() and EndTable() are instructions that define what data to store and under what con-
ditions data is stored. A data table must be called by the CRBasic program for data processing
and storage to occur. Typically, data tables are called by the CallTable() instruction once
each Scan. These instructions include:
DataTable()
'Output Trigger Condition(s)
'Output Processing Instructions
EndTable

Use the DataTable() instruction to define the number of records, or rows, allocated to a data
table. You can set a specific number of records, which is recommended for conditional tables, or
allow your datalogger to auto-allocate table size. With auto-allocation, the datalogger balances
the memory so the tables “fill up” (newest data starts to overwrite the oldest data) at about the
same time. It is recommended you reserve the use of auto-allocation for data tables that store
data based only on time (tables that store data based on the DataInterval() instruction).
Event or conditional tables are usually set to a fixed number of records. View data table fill times
for your program on the Station Status | Table Fill Times tab (see Checking station status (p. 94)
for more information). An example of the Table Fill Times tab follows. For information on data
table storage, see the CRBasic help and Data memory (p. 45).

4. Working with data 43

4. Working with data 44
5. Data memory
The datalogger includes three types of memory: RAM, Flash, and Serial Flash.

5.1 Flash memory

The datalogger operating system is stored in a separate section of flash memory. To update the
operating system, see Updating the operating system (p. 89).

5.2 Serial flash memory

Serial flash memory holds the CPU drive, web page, and datalogger settings. Because flash
memory has a limited number of write/erase cycles, care must be taken to avoid continuously writ-
ing to files on the CPU drive. For this reason, extended data memory is allocated in serial flash
only when data tables are programmed to auto-allocate table size.

5.2.1 Data memory

Measurement data is primarily stored in data tables. Data is usually erased from this area when a
program is sent to the datalogger. Final-data memory for the CR300 series is organized in 4 KB
sectors of serial flash. Each sector is rated for 100,000 serial flash erases.
During data table initialization, memory sectors are assigned to each data table according to the
parameters set in the program. Program options that affect the allocation of memory include the
Size parameter of the DataTable() instruction, the Interval and Units parameters of
the DataInterval() instruction. The datalogger uses those parameters to assign sectors in a
way that maximizes the life of its memory.
By default, data memory sectors are organized as ring memory. When the ring is full, oldest data
is overwritten by newest data. Using the FillStop statement sets a program to stop writing to
the data table when it is full, and no more data is stored until the table is reset. To see the total
number of records that can be stored before the oldest data is overwritten, or to reset tables, go
to Station Status > Table Fill Times in your datalogger support software.
Data concerning the datalogger memory are posted in the Status and DataTableInfo tables.
For additional information on datalogger memory, visit the Campbell Scientific blog
article, "How to Know when Your Datalogger Memory is Getting Full."

5. Data memory 45
5.2.2 CPU drive
The serial flash memory CPU drive contains datalogger programs and other files. This memory is
managed in File Control.

NOTE:
When writing to files under program control, take care to write infrequently to prevent pre-
mature failure of serial flash memory. Internal chip manufacturers specify the flash tech-
nology used in Campbell Scientific CPU: drives at about 100,000 write/erase cycles. While
Campbell Scientific's in-house testing has found the manufacturers' specifications to be very
conservative, it is prudent to note the risk associated with repeated file writes via program con-
trol.

Also, see System specifications (p. 163) for information on datalogger memory.

5. Data memory 46
6. Measurements
6.1 Voltage measurements 47
6.2 Current-loop measurements 49
6.3 Resistance measurements 51
6.4 Period-averaging measurements 57
6.5 Pulse measurements 58
6.6 Vibrating wire measurements 63

6.1 Voltage measurements

Voltage measurements are made using an ADC. A high-impedance programmable-gain amp-
lifier amplifies the signal. Internal multiplexers route individual terminals within the amplifier.
The CRBasic measurement instruction controls the ADC gain and configuration – either single-
ended or differential input. Information on the differences between single-ended and differential
measurements can be found here: Deciding between single-ended or differential measurements
(p. 104).
A voltage measurement proceeds as follows:

1. Set PGIA gain for the voltage range selected with the CRBasic measurement instruction
parameter Range. Set the ADC for the first notch frequency selected with fN1.
2. If used, turn on excitation to the level selected with ExmV.
3. Multiplex selected terminals (SEChan or DiffChan).
4. Delay for the entered settling time (SettlingTime).
5. Perform the analog-to-digital conversion.
6. Repeat for input reversal as determined by parameter RevDiff.
7. Apply multiplier (Mult) and offset (Offset) to measured result.

Conceptually, analog voltage sensors output two signals: high and low. For example, a sensor
that outputs 1000 mV on the high signal and 0 mV on the low has an overall output of 1000 mV.
A sensor that outputs 2000 mV on the high signal and 1000 mV on the low also has an overall out-
put of 1000 mV. Sometimes, the low signal is simply sensor ground (0 mV). A single-ended meas-
urement measures the high signal with reference to ground; the low signal is tied to ground. A
differential measurement measures the high signal with reference to the low signal. Each con-
figuration has a purpose, but the differential configuration is usually preferred.

6. Measurements 47
In general, use the smallest input range that accommodates the full-scale output of the sensor.
This results in the best measurement accuracy and resolution (see Analog measurements spe-
cifications (p. 167) for more information).
A set overhead reduces the chance of overrange. Overrange limits are available in the spe-
cifications. The datalogger indicates a measurement overrange by returning a NAN for the meas-
urement.

WARNING:
Sustained voltages in excess of -6 V or +9 V (SE1, SE2), ±17 V (SE3 to SE6) applied to ter-
minals configured for analog input will damage CR300 series circuitry.

6.1.1 Single-ended measurements

A single-ended measurement measures the difference in voltage between the terminal con-
figured for single-ended input and the reference ground. For example, single-ended channel 1 is
comprised of terminals SE 1 and . Single-ended terminals are labeled in blue. For more inform-
ation, see Wiring panel and terminal (p. 4). The single-ended configuration is used with the fol-
lowing CRBasic instructions:
l VoltSE()
l BrHalf()
l BrHalf3W()
l TCSE()
l Therm107()
l Therm108()
l Therm109()

6.1.2 Differential measurements

A differential measurement measures the difference in voltage between two input terminals. For
example, DIFF channel 1 is comprised of terminals 1H and 1L, with 1H as high and 1L as low. For
more information, see Wiring panel and terminal (p. 4). The differential configuration is used
with the following CRBasic instructions:
l VoltDiff()
l BrFull()
l BrFull6W()
l BrHalf4W()
l TCDiff()

6. Measurements 48
For more information on voltage measurements, see Improving voltage measurement quality (p.
104) and Analog measurements specifications (p. 167).

6.2 Current-loop measurements

Terminals SE1 and SE2 can be configured to make analog current measurements using the Cur-
rentSE() instruction. Current is measured across the 100 Ω resistor with 140 Ω total resistance
to ground. The following image shows a simplified schematic of a current measurement.

Use a CURS100 terminal input module when an application needs more than 2 current inputs or
measurements. For detailed instructions, see http://www.campbellsci.com/curs100.

6.2.1 Voltage Ranges for Current Measurements

The datalogger measures the current through the use of a 100 Ω resistor. Thus, like a single-
ended voltage instruction, it requires a voltage range option. In general, use the smallest fixed-
input range that accommodates the full-scale output of the transmitter. This results in the best
measurement accuracy and resolution.
To select the appropriate voltage range, the expected current output range must be known.
Using Ohm’s Law, multiply the maximum expected current by 100 Ω to find the maximum voltage
to be measured. Because the maximum voltage input is 2500 mV, the maximum current input
must be 25 mA or less.

6.2.2 Example Current-Loop Measurement Connections

The following table shows example schematics for connecting typical current sensors and
devices. See also Current-loop measurement specifications (p. 170).

6. Measurements 49
Sensor Type Connection Example

2-wire transmitter using datalogger power

2-wire transmitter using external power

3-wire transmitter using datalogger power

3-wire transmitter using external power

6. Measurements 50
Sensor Type Connection Example

4-wire transmitter using datalogger power

4-wire transmitter using external power

6.3 Resistance measurements

Bridge resistance is determined by measuring the difference between a known voltage applied to
the excitation (input) of a resistor bridge and the voltage measured on the output arm. The data-
logger supplies a precise voltage excitation via VX terminals. Return voltage is measured on ana-
log input terminals configured for single-ended (SE) or differential (DIFF) input. The result of the
measurement is a ratio of measured voltages.
See also Resistance measurements specifications (p. 169).

6.3.1 Resistance measurements with voltage excitation

CRBasic instructions for measuring resistance with voltage excitation include:

l BrHalf() - half bridge

l BrHalf3W() - three-wire half bridge
l BrHalf4W() - four-wire half bridge
l BrFull() - four-wire full bridge
l BrFull6W() - six-wire full bridge

6. Measurements 51
Resistive-Bridge Type and CRBasic Instruction and
Relational Formulas
Circuit Diagram Fundamental Relationship
Half Bridge1

CRBasic Instruction:
BrHalf()
Fundamental Relationship:

Three Wire Half Bridge1,2

CRBasic Instruction:
BrHalf3W()
Fundamental Relationship:

Four Wire Half Bridge1,2

CRBasic Instruction:
BrHalf4W()
Fundamental Relationship:

6. Measurements 52
Resistive-Bridge Type and CRBasic Instruction and
Relational Formulas
Circuit Diagram Fundamental Relationship
Full Bridge1,2

CRBasic Instruction:
BrFull() These relationships
Fundamental Relationship: apply to
BrFull()
and BrFull6W()

Six Wire Full Bridge1

CRBasic Instruction:
BrFull6W()
Fundamental Relationship:

1 Key: V = excitation voltage; V , V = sensor return voltages; Rf = fixed, bridge or completion resistor; Rs = vari-
x 1 2
able or sensing resistor.
2 Campbell Scientific offers terminal input modules to facilitate this measurement.

Offset voltage compensation applies to bridge measurements. RevDiff and MeasOff para-
meters are discussed in Minimizing offset voltages (p. 114). Much of the offset error inherent in
bridge measurements is canceled out by setting RevDiff and MeasOff to True.
CRBasic Example 1: : Four-Wire Full Bridge Measurement and Processing

'This program example demonstrates the measurement and

'processing of a four-wire resistive full bridge.
'In this example, the default measurement stored
'in variable X is deconstructed to determine the
'resistance of the R1 resistor, which is the variable
'resistor in most sensors that have a four-wire

6. Measurements 53
CRBasic Example 1: : Four-Wire Full Bridge Measurement and Processing

'full-bridge as the active element.

'Declare Variables
Public X
Public X_1
Public R_1
Public R_2 = 1000 'Resistance of fixed resistor R2
Public R_3 = 1000 'Resistance of fixed resistor R3
Public R_4 = 1000 'Resistance of fixed resistor R4
'Main Program
BeginProg
Scan(500,mSec,1,0)
'Full Bridge Measurement:
BrFull(X,1,mV2500,1,Vx1,1,2500,False,True,0,60,1.0,0.0)
X_1 = ((-1 * X) / 1000) + (R_3 / (R_3 + R_4))
R_1 = (R_2 * (1 - X_1)) / X_1
NextScan
EndProg

6.3.2 Strain measurements

A principal use of the four-wire full bridge is the measurement of strain gages in structural stress
analysis. StrainCalc() calculates microstrain (µɛ) from the formula for the specific bridge
configuration used. All strain gages supported by StrainCalc() use the full-bridge schem-
atic. 'Quarter-bridge', 'half-bridge' and 'full-bridge' refer to the number of active elements in the
bridge schematic. In other words, a quarter-bridge strain gage has one active element, a half-
bridge has two, and a full-bridge has four.
StrainCalc() requires a bridge-configuration code. The following table shows the equation
used by each configuration code. Each code can be preceded by a dash (-). Use a code without
the dash when the bridge is configured so the output decreases with increasing strain. Use a
dashed code when the bridge is configured so the output increases with increasing strain. A
dashed code sets the polarity of Vr to negative.

6. Measurements 54
Table 6-1: StrainCalc() configuration codes
BrConfig Code Configuration
Quarter-bridge strain gage1:

Half-bridge strain gage1. One gage parallel to strain, the other at

90° to strain:
2

Half-bridge strain gage. One gage parallel to +ɛ, the other parallel
to -ɛ1:
3

Full-bridge strain gage. Two gages parallel to +ɛ, the other two par-
allel to -ɛ1:
4

6. Measurements 55
Table 6-1: StrainCalc() configuration codes
BrConfig Code Configuration
Full-bridge strain gage. Half the bridge has two gages parallel to +ɛ
and -ɛ, and the other half to +νɛ and -νɛ 1:
5

Full-bridge strain gage. Half the bridge has two gages parallel to +ɛ
and -νɛ , and the other half to -νɛ and +ɛ1:
6

1 Where

• ν : Poisson's Ratio (0 if not applicable).

• GF: Gage Factor.
• Vr: 0.001 (Source-Zero) if BRConfig code is positive (+).

• Vr: –0.001 (Source-Zero) if BRConfig code is negative (–).

and where:
• "source": the result of the full-bridge measurement (X = 1000 • V1 / Vx) when multiplier = 1 and offset = 0.
• "zero": gage offset to establish an arbitrary zero.

6.3.3 Accuracy for resistance measurements

Consult the following technical papers for in-depth treatments of several topics addressing
voltage measurement quality:

l Preventing and Attacking Measurement Noise Problems

l Benefits of Input Reversal and Excitation Reversal for Voltage Measurements
l Voltage Measurement Accuracy, Self- Calibration, and Ratiometric Measurements

NOTE:
Error discussed in this section and error-related specifications of the CR300 series do not
include error introduced by the sensor, or by the transmission of the sensor signal to the data-
logger.

6. Measurements 56
For accuracy specifications of ratiometric resistance measurements, see Resistance measurements
specifications (p. 169). Voltage measurement is variable V1 or V2 in Resistance measurements (p.
51). Offset is the same as that for simple analog voltage measurements.
Assumptions that support the ratiometric-accuracy specification include:

l Datalogger is within factory calibration specification.

l Effects due to the following are not included in the specification:
o Bridge-resistor errors
o Sensor noise
o Measurement noise

6.4 Period-averaging measurements

Use PeriodAvg() to measure the period (in microseconds) or the frequency (in Hz) of a signal
on a single-ended channel. For these measurements, the datalogger uses a high-frequency
digital clock to measure time differences between signal transitions, whereas pulse-count meas-
urements simply accumulate the number of counts. As a result, period-average measurements
offer much better frequency resolution per measurement interval than pulse-count meas-
urements. See also Pulse measurements (p. 58).
SE 1-4 terminals on the datalogger are configurable for measuring the period of a signal.
See also Period-averaging measurement specifications (p. 169).

TIP:
Both pulse count and period-average measurements are used to measure frequency output
sensors. However, their measurement methods are different. Pulse count measurements use
dedicated hardware - pulse count accumulators, which are always monitoring the input sig-
nal, even when the datalogger is between program scans. In contrast, period-average meas-
urements use program instructions that only monitor the input signal during a program scan.
Consequently, pulse count scans can occur less frequently than period-average scans. Pulse
counters may be more susceptible to low-frequency noise because they are always "listening",
whereas period-averaging measurements may filter the noise by reason of being "asleep"
most of the time.
Pulse count measurements are not appropriate for sensors that are powered off between
scans, whereas period-average measurements work well since they can be placed in the scan
to execute only when the sensor is powered and transmitting the signal.

6. Measurements 57
6.5 Pulse measurements
The output signal generated by a pulse sensor is a series of voltage waves. The sensor couples its
output signal to the measured phenomenon by modulating wave frequency. The datalogger
detects the state transition as each wave varies between voltage extremes (high-to-low or low-to-
high). Measurements are processed and presented as counts, frequency, or timing data. Both
pulse count and period-average measurements are used to measure frequency-output sensors.
For more information, see Period-averaging measurements (p. 57).
The datalogger includes terminals that are configurable for pulse input to measure counts or fre-
quency as shown in the following image.

Table 6-2: Pulse input terminals and the input types they can measure
Input Type Pulse Input Terminal Data Option

C (all)

High-frequency
SE 1-4
P_SW
P_LL l Counts
l Frequency
l Running average of fre-
Low-level ac
quency
P_LL

C (all)
Switch-closure

P_SW

6. Measurements 58
Using the PulseCount() instruction, P_LL, P_SW, SE 1-4, and C terminals are configurable for
pulse input to measure counts or frequency. Maximum input frequency is dependent on input
voltage. If pulse input voltages exceed the maximum voltage, third-party external-signal con-
ditioners should be employed. Do not measure voltages greater than 20 V.
Terminals configured for pulse input have internal filters that reduce electronic noise, and thus
reduce false counts. Internal ac coupling is used to eliminate dc offset voltages. For tips on work-
ing with pulse measurements, see Pulse measurement tips (p. 62).
See also Pulse measurement specifications (p. 170).

6.5.1 Low-level ac measurements

Low-level ac (alternating current or sine-wave) signals can be measured on P_LL terminals. Ac
generator anemometers typically output low-level ac.
Measurements include the following:

l Counts
l Frequency (Hz)
l Running average

Rotating magnetic-pickup sensors commonly generate ac voltage ranging from thousandths of

volts at low-rotational speeds to several volts at high-rotational speeds.
CRBasic instruction: PulseCount()

6.5.2 High-frequency measurements

High-frequency (square-wave) signals can be measured on P_LL, P_SW, SE 1-4, or C terminals.
Common sensors that output high-frequency pulses include:

l Photo-chopper anemometers
l Flow meters

Measurements include counts, frequency in hertz, and running average.

l CRBasic instruction: PulseCount()

6.5.3 Switch-closure and open-collector measurements

Switch-closure and open-collector (also called current-sinking) signals can be measured on P_
SW orC terminals. Mechanical switch-closures have a tendency to bounce before solidly closing.
Unless filtered, bounces can cause multiple counts per event. The datalogger automatically filters
bounce. Because of the filtering, the maximum switch-closure frequency is less than the max-

6. Measurements 59
imum high-frequency measurement frequency. Sensors that commonly output a switch-closure
or an open-collector signal include:

l Tipping-bucket rain gages

l Switch-closure anemometers
l Flow meters

Data output options include counts, frequency (Hz), and running average.

6.5.3.1 P_SW Terminal

An internal 100 kΩ pull-up resistor pulls an input to 3.3 Vdc with the switch open, whereas a
switch-closure to ground pulls the input to 0 V.

l CRBasic instruction: PulseCount()

Switch Closure on P Terminal Open Collector on P Terminal

6.5.3.2 C terminals
Switch-closure measurements on C terminals require a 100 kΩ pull-up resistor to 12 V. Switch-clos-
ure mode is a special case edge-count function that measures dry-contact switch-closures or
open collectors. The operating system filters bounces.

l CRBasic instruction: PulseCount()

6.5.4 Quadrature measurements

The Quadrature() instruction is used to measure shaft or rotary encoders. A shaft encoder
outputs a signal to represent the angular position or motion of the shaft. Each encoder will have
two output signals, an A line and a B line. As the shaft rotates the A and B lines will generate
digital pulses that can be read, or counted, by the datalogger.

6. Measurements 60
In the following example, channel A leads channel B, therefore the encoder is determined to be
moving in a clockwise direction. If channel B led channel A, it would be determined that the
encoder was moving in a counterclockwise direction.

Terminals SE1 and SE2 or C1 and C2 can be configured as digital pairs to monitor the two chan-
nels of an encoder. The Quadrature() instruction can return:

l The accumulated number of counts from channel A and channel B. Count will increase if
channel A leads channel B. Count will decrease if channel B leads channel A.
l The net direction.
l Number of counts in the A-leading-B direction.
l Number of counts in the B-leading-A direction.

Counting modes:

l Counting the increase on rising edge of channel A when channel A leads channel B. Count-
ing the decrease on falling edge of channel A when channel B leads channel A.
l Counting the increase at each rising and falling edge of channel A when channel A leads
channel B. Counting the decrease at each rising and falling edge of channel A when chan-
nel A leads channel B.
l Counting the increase at each rising and falling edge of both channels when channel A
leads channel B. Counting the decrease at each rising and falling edge of both channels
when channel B leads channel A.

For more information, see Pulse measurement specifications (p. 170).

6. Measurements 61
6.5.5 Pulse measurement tips
The PulseCount() instruction uses dedicated 32-bit counters to accumulate all counts over
the programmed scan interval. The resolution of pulse counters is one count or 1 Hz. Counters
are read at the beginning of each scan and then cleared. Counters will overflow if accumulated
counts exceed 4,294,967,296 (232), resulting in erroneous measurements.
Counts are the preferred PulseCount() output option when measuring the number of tips
from a tipping-bucket rain gage or the number of times a door opens. Many pulse-output
sensors, such as anemometers and flow meters, are calibrated in terms of frequency (Hz) so are
usually measured using the PulseCount() frequency-output option.
Use the LLAC4 module to convert non-TTL-level signals, including low-level ac signals, to TTL
levels for input to C terminals
Understanding the signal to be measured and compatible input terminals and CRBasic instruc-
tions is helpful. See Pulse input terminals and the input types they can measure (p. 58).

6.5.5.1 Input filters and signal attenuation

Terminals configured for pulse input have internal filters that reduce electronic noise. The elec-
tronic noise can result in false counts. However, input filters attenuate (reduce) the amplitude
(voltage) of the signal. Attenuation is a function of the frequency of the signal. Higher-frequency
signals are attenuated more. If a signal is attenuated too much, it may not pass the detection
thresholds required by the pulse count circuitry.See Pulse measurement specifications (p. 170) for
more information. The listed pulse measurement specifications account for attenuation due to
input filtering.

6.5.5.2 Pulse count resolution

Longer scan intervals result in better resolution. PulseCount() resolution is 1 pulse per scan.
On a 1 second scan, the resolution is 1 pulse per second. The resolution on a 10 second scan inter-
val is 1 pulse per 10 seconds, which is 0.1 pulses per second. The resolution on a 100 millisecond
interval is 10 pulses per second.
For example, if a flow sensor outputs 4.5 pulses per second and you use a 1 second scan, one
scan will have 4 pulses and the next 5 pulses. Scan to scan, the flow number will bounce back
and forth. If you did a 10 second scan (or saved a total to a 10 second table), you would get 45
pulses. The total is 45 pulses for every 10 seconds. An average will correctly show 4.5 pulses per
second. You wouldn't see the reading bounce on the longer time interval.

6. Measurements 62
6.6 Vibrating wire measurements
The datalogger can measure vibrating wire sensors through vibrating-wire interface modules.
Vibrating wire sensors are the sensor of choice in many environmental and industrial applications
that need sensor stability over very long periods, such as years or even decades. A thermistor
included in most sensors can be measured to compensate for temperature errors.

6.6.1 VSPECT®
Measuring the resonant frequency by means of period averaging is the classic technique, but
Campbell Scientific has developed static and dynamic spectral-analysis techniques (VSPECT) that
produce superior noise rejection, higher resolution, diagnostic data, and, in the case of dynamic
VSPECT, measurements up to 333.3 Hz. For detailed information on VSPECT, see Vibrating Wire
Spectral Analysis Technology.

6. Measurements 63
7. Communications
Dataloggers communicate with datalogger support software, other Campbell Scientific data-
loggers, and other hardware and software using a number of protocols including PakBus, Mod-
bus, DNP3, and TCP/IP. Several industry-specific protocols are also supported.See also
Communications specifications (p. 172).

7.1 General serial communications 65

7.2 Modbus communications 65
7.3 Internet Communications 74
7.4 DNP3 communications 75
7.5 PakBus communications 75
7.6 SDI-12 communications 76
Some communications services, such as satellite networks, can be expensive to send and receive
information. Best practices for reducing expense include:

l Declare Public only those variables that need to be public. Other variables should be
declared as Dim.
l Be conservative with use of string variables and string variable sizes. Make string variables
as big as they need to be and no more. The default size, if not specified, is 24 bytes, but the
minimum is 4 bytes. Declare string variables Public and sample string variables into data
tables only as needed.
l When using GetVariables() / SendVariables() to send values between data-
loggers, put the data in an array and use one command to get the multiple values. Using
one command to get 10 values from an array and swath of 10 is more efficient (requires
only 1 transaction) than using 10 commands to get 10 single values (requires 10 trans-
actions).
l Set the datalogger to be a PakBus router only as needed. When the datalogger is a router,
and it connects to another router like LoggerNet, it exchanges routing information with
that router and, possibly (depending on your settings), with other routers in the network.
Network Planner set this appropriately when it is used. This is also set through the IsRouter
setting in the Settings Editor.
l Set PakBus beacons and verify intervals properly. For example, there is no need to verify
routes every five minutes if communications are expected only every 6 hours. Network Plan-

7. Communications 64
ner will set this appropriately when it is used. This is also set through the Beacon and Verify
settings in the Settings Editor.

For information on Designing a PakBus network using the Network Planner tool in LoggerNet,
watch a video.

7.1 General serial communications

The datalogger supports two-way serial communications. These communications ports can be
used with smart sensors that deliver measurement data through serial data protocols, or with
devices such as modems, that communicate using serial data protocols. See Communications
ports (p. 10) for information on port configuration options.
CRBasic instructions for general serial communications include:

l SerialOpen()
l SerialClose()
l SerialIn()
l SerialInRecord()
l SerialInBlock()
l SerialOut()
l SerialOutBlock()

To communicate over a serial port, it is important to be familiar with protocol used by the device
with which you will be communicating. Refer to the manual of the sensor or device to find its pro-
tocol and then select the appropriate options for each CRBasic parameter. See the application
note Interfacing Serial Sensors with Campbell Scientific Dataloggers for more programming
details and examples.

NOTE:
Though Com1 uses RS-232 logic levels, it is limited to 0 V (logic high) and 5 V (logic low) out-
put. This may make Com1 incompatible with some serial devices.
Com1 is not capable of TTL logic levels and so is not compatible with TTL-to-RS-232 con-
verters for the purpose of presenting a true RS-232 interface.
Com1 also has a low input resistance that may make it incompatible with some serial devices
with the addition of in-line resistance.

7.2 Modbus communications

The datalogger supports Modbus RTU, Modbus ASCII, and Modbus TCP protocols and can be
programmed as a Modbus master or Modbus slave. These protocols are often used in SCADA

7. Communications 65
networks. Dataloggers can communicate using Modbus on all available communication ports.
The datalogger communicates using Modbus over RS-232 using a RS-232-to RS-485 adapter and
over TCP using an Ethernet or Wireless connection.
CRBasic Modbus instructions include (see CRBasic Editor help for the most recent information on
each of these instructions and for program examples):
l ModbusMaster()
l ModbusSlave()
l MoveBytes()

For additional information on Modbus, see:

l About Modbus (p. 66)

l Why Modbus Matters: An Introduction
l How to Access Live Measurement Data Using Modbus
l Using Campbell Scientific Dataloggers as Modbus Slave Devices in a SCADA Network

Because Modbus has a set command structure, programming the datalogger to get data from
field instruments can be much simpler than from some other serial sensors. Because Modbus uses
a common bus and addresses each node, field instruments are effectively multiplexed to a data-
logger without additional hardware.
When doing Modbus communications over RS-232, the datalogger, through Device Con-
figuration Utility or the Settings editor, can be set to keep communication ports open and awake,
but at higher power usage. Set RS-232Power to Always on. Otherwise, the datalogger goes into
sleep mode after 40 seconds of communications inactivity. Once asleep, two packets are required
before it will respond. The first packet awakens the datalogger; the second packet is received as
data. This would make a Modbus master fail to poll the datalogger, if not using retries.
More information on Modbus can be found at:

l www.simplyModbus.ca/FAQ.htm
l www.Modbus.org/tech.php
l www.lammertbies.nl/comm/info/modbus.html

7.2.1 About Modbus

Modbus is a communications protocol that enables communications among many devices con-
nected to the same network. Modbus is often used in supervisory control and data acquisition
(SCADA) systems to connect remote terminal units (RTUs) with a supervisory computer - allowing
them to relay measurement data, device status, control commands, and configuration inform-
ation.

7. Communications 66
The popularity of Modbus has grown because it is freely available and because its messaging
structure is independent of the type of physical interface or connection that is used. Modbus can
coexist with other types of connections on the same physical interface at the same time. You can
operate the protocol over several data links and physical layers.
Modbus is supported by many industrial devices, including those offered by Campbell Scientific.
Not only can intelligent devices such as microcontrollers and programmable logic controllers
(PLCs) communicate using Modbus, but many intelligent sensors have a Modbus interface that
enables them to send their data to host systems. Examples of using Modbus with Campbell
Scientific dataloggers include:

l Interfacing dataloggers and Modbus-enabled sensors.

l Sending and retrieving data between dataloggers and other industrial devices.
l Delivering environmental data to SCADA systems.
l Integrating Modbus data into PakBus networks, or PakBus data into Modbus networks.

7.2.2 Modbus protocols

There are three standard variants of Modbus protocols:

l Modbus RTU — Modbus RTU is the most common implementation available for Modbus.
Used in serial communications, data is transmitted in a binary format. The RTU format fol-
lows the commands/data with a cyclic redundancy check checksum.

7. Communications 67
NOTE:
The Modbus RTU protocol standard does not allow a delay between characters of 1.5 times or
more the length of time normally required to receive a character. This is analogous to “pizza”
being understood, and “piz za” being gibberish. It's important to note that communications
hardware used for Modbus RTU, such as radios, must transfer data as entire packets without
injecting delays in the middle of Modbus messages.

l Modbus ASCII — Used in serial communications, data is transmitted as an ASCII rep-

resentation of the hexadecimal values. Timing requirements are loosened, and a simpler
longitudinal redundancy check checksum is used.
l Modbus TCP/IP or Modbus TCP — Used for communications over TCP/IP networks. The
TCP/IP format does not require a checksum calculation, as lower layers already provide
checksum protection. The packet structure is similar to RTU, but utilizes a different header.
Devices labeled as Modbus gateways will convert from Modbus TCP to Modbus RTU.

Campbell Scientific dataloggers support Modbus RTU, Modbus ASCII, and Modbus TCP pro-
tocols. If the connection is over IP, Campbell Scientific dataloggers always use Modbus TCP. Mod-
bus slave functionality over other comports use RTU. When acting as a master, the datalogger
can be switched between ASCII and RTU protocols using an option in the ModbusMaster()
instruction.

7.2.3 Understanding Modbus Terminology

Many of the object types are named from using Modbus in driving relays: a single-bit physical
output is called a coil, and a single-bit physical input is called a discrete input or a contact.
Information is stored in the slave device in up to four different tables. Two tables store on/off dis-
crete values (coils) and two store numerical values (registers). The coils and registers each have a
read-only table and read/write table.

7.2.4 Connecting Modbus devices

Dataloggers can communicate with Modbus on all available communication ports. Consideration
should be given to proper surge protection of any cabled connection. Between systems of sig-
nificantly different ground potential, optical isolation may be appropriate. For additional inform-
ation on grounds, see Grounds (p. 9).
The datalogger communicates with Modbus over RS-232, or RS-485 using a RS-232-to RS-485
adapter and over TCP using an Ethernet or wireless connection .

7. Communications 68
7.2.5 About Modbus communications
Modbus is a master-slave protocol. The device requesting the information is called the Modbus
master, and the devices supplying information are Modbus slaves. In a standard Modbus net-
work, there is one master and up to 247 slaves. A master does not have a Modbus address.
However, each Modbus slave on a shared network has a unique address from 1 to 247.
A single Modbus master device initiates commands (requests for information), sending them to
one or more Modbus slave devices on the same network. Only the Modbus master can initiate
communications. Modbus slaves, in turn, remain silent, communicating only when responding to
requests from the Modbus master.
Every message from the master will begin with the slave address, followed by the function code,
function parameters, and a checksum. The slave will respond with a message beginning with its
address, followed by the function code, data, and a checksum. The amount of data in the packet
will vary, depending on the command sent to the slave. Slave devices only process one command
at a time. So, the master needs to wait for a response, or timeout before sending the next com-
mand.
A broadcast address is specified to allow simultaneous communications with all slaves. Because
response time of slave devices is not specified by the standard, and device manufacturers also
rarely specify a maximum response time, broadcast features are rarely used. When implementing
a system, timeouts in the master will need to be adjusted to account for the observed response
time of the slaves.
Campbell Scientific dataloggers can be programmed to be a Modbus master or Modbus slave -
or even both at the same time! This proves particularly helpful when your datalogger is a part of
two wider area networks. In one it uses Modbus to query data (as a master) from localized
sensors or other data sources, and then in the other, it serves that data up (as a slave) to another
Modbus master.

7.2.6 About Modbus programming

Modbus capability of the datalogger must be enabled through configuration or programming.
See the CRBasic Editor help for detailed information on program structure, syntax, and each
instruction available to the datalogger.
CRBasic Modbus instructions include:
l ModbusMaster()
l ModbusSlave()
l MoveBytes()

7. Communications 69
7.2.6.1 Endianness
Endianness refers to the sequential order in which bytes are arranged into larger numerical values
when stored in memory. Words may be represented in big-endian or little-endian format,
depending on whether bits or bytes or other components are ordered from the big end (most sig-
nificant bit) or the little end (least significant bit).
In big-endian format, the byte containing the most significant bit is stored first, then the fol-
lowing bytes are stored in decreasing significance order, with the byte containing the least sig-
nificant bit stored last. Little-endian format reverses this order: the sequence stores the least
significant byte first and the most significant byte last. Endinness is used in some Modbus pro-
gramming so it is important to note that the CR300 is a little-endian instrument.

7.2.6.2 Function codes

A function code tells the slave which storage entity to access and whether to read from or write to
that entity. Different devices support different functions (consult the device documentation for
support information). The most commonly used functions (codes 01, 02, 03, 04, 05, 15, and 16 )
are supported by Campbell Scientific dataloggers.
Most users only require the read- register functions. Holding registers are read with function
code 03. Input registers are read with function code 04. This can be confusing, because holding
registers are usually listed with an offset of 40,000 and input registers with an offset of 30,000.
Don’t mix up the function codes. Double check the register type in the device documentation.

Function Code Action Entity

01 (01 hex) Read Discrete Output Coils
05 (05 hex) Write single Discrete Output Coil
15 (0F hex) Write multiple Discrete Output Coils
02 (02 hex) Read Discrete Input
04 (04 hex) Read Input Registers
03 (03 hex) Read Holding Registers
06 (06 hex) Write single Holding Register
16 (10 hex) Write multiple Holding Registers

The write-register functions will only work on holding registers. Function 06 only changes one 16-
bit register, whereas function 16, changes multiple registers. Note, when writing registers, the
Variable parameter for the ModbusMaster() instruction refers to a source, not a des-
tination.

7. Communications 70
7.2.7 Modbus information storage
With the Modbus protocol, most of the data values you want to transmit or receive are stored in
registers. Information is stored in the slave device in four different entities. Two store on/off dis-
crete values (coils) and two store numerical values (registers). The four entities include:

l Coils – 1-bit registers, used to control discrete outputs (including Boolean values),
read/write.
l Discrete Input – 1-bit registers, used as inputs, read only.
l Input Registers – 16-bit registers, used as inputs, read only.
l Holding Registers – 16-bit registers; used for inputs, output, configuration data, or any
requirement for “holding” data; read/write.

7.2.7.1 Registers
In a 16-bit memory location, a 4-byte value takes up two registers. The Modbus protocol always
refers to data registers with a starting address number, and a length to indicate how many
registers to transfer.
Campbell Scientific uses 1-based numbering (a common convention for numbering registers in
equipment) in the ModbusMaster() instruction. With 1-based numbering, the first data loc-
ation is referred to as register number 1. Some equipment uses 0-based numbering (check the
equipment documentation). With 0-based numbering, the first register is referred to as 0.
Reading register numbers can be complicated by the fact that register numbers are often written
with an offset added. Input registers are written with an offset of 30000. So, the first input register
is written as 30001, with 1-based numbering. Holding registers are numbered with an offset of
40000. You must remove the offset before writing the number as the Start parameter of Mod-
busMaster().
There are rare instances when equipment is designed with the registers mapped including the off-
set. That means 40001 in the documentation is really register number 40001. Those are rare
instances, and the equipment is deviating from standards. If 1 or 2 don’t work for the Start para-
meter, try 40001 and 40002.

7.2.7.2 Coils
Discrete digital I/O channels in Modbus are referred to as coils. The term coil has its roots in
digital outputs operating solenoid coils in an industrial environment. Coils may be read only or
read/write. A read only coil would be a digital input. A read/write coil is used as an output. Coils
are read and manipulated with their own function codes, apart from the registers. Many modern
devices do not utilize coils at all.

7. Communications 71
When working with coils, the datalogger requires Boolean variables. When reading coils, each
Boolean in an array will hold the state of one coil. A value of True will set the coil, a value of
False will unset the coil.

7.2.7.3 Data Types

Modbus does not restrict what data types may be contained within holding and input registers.
Equipment manufacturers need to indicate what binary data types they are using to store data.
Registers are 16-bit, so 32-bit data types use 2 registers each. Some devices combine more
registers together to support longer data types like strings. The ModbusMaster() instruction
has a ModbusOption parameter that supports several different data types.
When data types use more than 1 register per value, the register order within the data value is
important. Some devices will swap the high and low bytes between registers. You can com-
pensate for this by selecting the appropriate ModbusOption.
Byte order is also important when communicating data over Modbus. Big Endian byte order is
the reverse of Little Endian byte order. It may not always be apparent which a device uses. If you
receive garbled data, try reversing the byte order. Reversing byte order is done using the
MoveBytes() instruction. There is an example in CRBasic help for reversing the bytes order of
a 32-bit variable.
After properly reading in a value from a Modbus device, you might have to convert the value to
proper engineering units. With integer data types, it is common to have the value transmitted in
hundredths or thousandths.

Unsigned 16-bit integer

The most basic data type used with Modbus is unsigned 16-bit integers. It is the original Modbus
data type with 1 register per value. On the datalogger, declare your destination variable as type
Long. A Long is a 32-bit signed integer that contains the value received. Select the appropriate
ModbusOption to avoid post-processing.

Signed 16-bit integer

Signed 16-bit integers use 1 register per value. On the datalogger, declare your destination vari-
able as type Long. A Long is a 32-bit signed integer that contains the value received . Select the
appropriate ModbusOption to avoid post-processing.

Signed 32-bit integer

Signed 32-bit integers require two registers per value. This data type corresponds to the native
Long variable type in Campbell dataloggers. Declare your variables as type Long before using

7. Communications 72
them as the Variable parameter in ModbusMaster(). Select the appropriate ModbusOption
to avoid post-processing.

Unsigned 32-bit integer

Unsigned 32-bit integers require two registers per value. Declare your variables as type Long
before using them as the Variable parameter in ModbusMaster(). The Long data type is a
signed integer, and does not have a range equal to that of an unsigned integer. If the integer
value exceeds 2,147,483,647 it will display incorrectly as a negative number. If the value does not
exceed that number, there are no issues with a variable of type Long holding it.

32-Bit floating point

32-bit floating point values use 2 registers each. This is the default FLOAT data type in Campbell
Scientific dataloggers . Select the appropriate ModbusOption to avoid post-processing.

7.2.8 Modbus tips and troubleshooting

Most of the difficulties with Modbus communications arise from deviations from the standards,
which are not enforced within Modbus. Whether you are connecting via Modbus to a solar
inverter, power meter, or flow meter, the information provided here can help you overcome the
challenges, and successfully gather data into a Campbell datalogger. Further information on
Modbus can be found at:

l www.simplyModbus.ca/FAQ.htm
l www.Modbus.org/tech.php
l www.lammertbies.nl/comm/info/modbus.html

7.2.8.1 Error codes

Modbus defines several error codes, which are reported back to a master from a slave. Mod-
busMaster() displays these codes as a negative number. A positive result code indicates no
response was received.

Result code -01: illegal function

The illegal function error is reported back by a Modbus slave when either it does not support the
function at all, or does not support that function code on the requested registers. Different
devices support different functions (consult the device documentation). If the function code is
supported, make sure you are not trying to write to a register labeled as read-only. It is common
for devices to have holding registers where read-only and read/write registers are mapped next to
each other.

7. Communications 73
An uncommon cause for the -01 result is a device with an incomplete implementation of Mod-
bus. Some devices do not fully implement parsing Modbus commands. Instead, they are hard-
coded to respond to certain Modbus messages. The result is that the device will report an error
when you try selectively polling registers. Try requesting all of the registers together.

Result code -02: illegal data address

The illegal data address error occurs if the slave rejects the combination of starting register and
length used. One possibility, is a mistake in your program on the starting register number. Refer
to the earlier section about register number and consult the device documentation for support
information. Also, too long of a length can trigger this error. The ModbusMaster() instruction
uses length as the number of values to poll. With 32-bit data types, it requests twice as many
registers as the length.
An uncommon cause for the -02 result is a device with an incomplete implementation of Mod-
bus. Some devices do not fully implement parsing Modbus commands. Instead, they are hard
coded to respond to certain Modbus messages. The result is that the device will report an error
when you try selectively polling registers. Try requesting all of the registers together.

Result code -11: COM port error

Result code -11 occurs when the datalogger is unable to open the COM port specified. For serial
connections, this error may indicate an invalid COM port number. For Modbus TCP, it indicates a
failed socket connection.
If you have a failed socket connection for Modbus TCP, check your TCPOpen() instruction. The
socket returned from TCPOpen() should be a number less than 99. Provided the datalogger
has a working network connection, further troubleshooting can be done with a computer run-
ning Modbus software. Connect the computer to the same network and attempt to open a Mod-
bus TCP connection to the problem slave device. Once you resolve the connection between the
computer and the slave device, the connection from the datalogger should work.

7.3 Internet Communications

The internet protocols listed in Communications specifications (p. 172), are supported by the
CR310 or when using a cell modem with the CR300 series. The most up-to-date information on
implementing these protocols is contained in CRBasic Editor help.
CRBasic instructions for internet communications include:

l EmailRelay() l HTTPPut()
l EmailSend() l IPInfo()
l EmailRcv() l PPPOpen()

7. Communications 74
l FTPClient()
l PPPClose()
l HTTPGet()
l TCPOpen()
l HTTPOut()
l TCPClose()
l HTTPPost()

7.4 DNP3 communications

DNP3 is designed to optimize transmission of data and control commands from a master com-
puter to one or more remote devices or outstations. The datalogger allows DNP3 com-
munications on all available communication ports. CRBasic DNP3 instructions include:
l DNP()
l DNPUpdate()
l DNPVariable()

See the CRBasic help for detailed information and program examples.
For additional information on DNP3 see:

l DNP3 with Campbell Scientific Dataloggers

l Getting to Know DNP3
l How to Access Your Measurement Data Using DNP3

7.5 PakBus communications

PakBus is a Campbell Scientific communications protocol. By using signed data packets, PakBus
increases the number of communication and networking options available to the datalogger.
The datalogger allows PakBus communications on all available communications ports. For addi-
tional information, see The Many Possibilities of PakBus Networking.
Advantages of PakBus include:

l Simultaneous communications between the datalogger and other devices.

l Peer-to-peer communications - no computer required. Special CRBasic instructions simplify
transferring data between dataloggers for distributed decision making or control.
l Data consolidation - other PakBus dataloggers can be used as "sensors" to consolidate all
data into one datalogger.
l Routing - the datalogger can act as a router, passing on messages intended for another
Campbell Scientific datalogger. PakBus supports automatic route detection and selection.
l Short distance networks - a datalogger can talk to another datalogger over distances up to
30 feet by connecting transmit, receive, and ground wires between the dataloggers.

7. Communications 75
In a PakBus network, each datalogger is assigned a unique address. The default PakBus address
in most devices is 1. To communicate with the datalogger, the datalogger support software must
know the datalogger PakBus address. The PakBus address is changed using Device Configuration
Utility, datalogger Settings Editor, or PakBus Graph software.
CRBasic PakBus instructions include:
l GetDataRecord()
l GetVariables()
l SendData()
l SendGetVariables()
l SendVariables()

7.6 SDI-12 communications

SDI-12 is a 1200 baud communications protocol that supports many smart sensors, probes and
devices. The datalogger supports SDI-12 communications through two modes — transparent
mode and programmed mode (see SDI-12 ports (p. 11) for wiring terminal information).
Transparent mode facilitates sensor setup and troubleshooting. It allows commands to be manu-
ally issued and the full sensor response viewed. Transparent mode does not record data. See SDI-
12 transparent mode (p. 76) for more information.
Programmed mode automates much of the SDI-12 protocol and provides for data recording. See
SDI-12 programmed mode/recorder mode (p. 78) for more information.
CRBasic SDI-12 instructions include:
l SDI12Recorder()
l SDI12SensorSetup()
l SDI12SensorResponse()
l SDI12Watch()

The datalogger uses SDI-12 version 1.3.

7.6.1 SDI-12 transparent mode

System operators can manually interrogate and enter settings in probes using transparent mode.
Transparent mode is useful in troubleshooting SDI-12 systems because it allows direct com-
munications with probes.
Transparent mode may need to wait for commands issued by the programmed mode to finish
before sending responses. While in transparent mode, the datalogger programs may not execute.
Datalogger security may need to be unlocked before transparent mode can be activated.

7. Communications 76
Transparent mode is entered while the computer is communicating with the datalogger through
a terminal emulator program such as through Device Configuration Utility or other datalogger
support software. Keyboard displays cannot be used. For how-to instructions for communicating
directly with an SDI-12 sensor using a terminal emulator, watch this video.
To enter the SDI-12 transparent mode, enter the datalogger support software terminal emulator:

1. Press Enter until the datalogger responds with the prompt CR300 series>.
2. Type SDI12 at the prompt and press Enter.
3. In response, the query Enter Cx Port is presented with a list of available ports. Enter
the port number assigned to the terminal to which the SDI-12 sensor is connected, and
press Enter. For example, 1 is entered for terminal C1.
4. An Entering SDI12 Terminal response indicates that SDI-12 transparent mode is
active and ready to transmit SDI-12 commands and display responses.

The terminal-mode utility allows monitoring of SDI-12 traffic by using the watch command
(sniffer mode). Watch an instructional this video or use the following instructions.

1. Enter the terminal mode as described previously.

2. Press Enter until a CR300 series> prompt appears.
3. Type W and then press Enter.
4. In response, the query Select: is presented with a list of available ports. Enter the port
number assigned to the terminal to which the SDI-12 sensor is connected, and press Enter.
5. In answer to Enter timeout (secs): type 100 and press Enter.
6. In response to the query ASCII (Y)?, type Y and press Enter.
7. SDI-12 communications are then opened for viewing.

7.6.1.1 SDI-12 transparent mode commands

SDI-12 commands and responses are defined by the SDI-12 Support Group (www.sdi-12.org) and
are available in the SDI-12 Specification. Sensor manufacturers determine which commands to
support. Commands have three components:

l Sensor address ( a): A single character and the first character of the command. Sensors are
usually assigned a default address of zero by the manufacturer. The wildcard address ( ?) is
used in the Address Query command. Some manufacturers may allow it to be used in

7. Communications 77
other commands. SDI-12 sensors accept addresses 0 through 9, a through z, and A through
Z.
l Command body (for example, M1): An upper case letter (the “command”) followed by
alphanumeric qualifiers.
l Command termination ( !): An exclamation mark.

An active sensor responds to each command. Responses have several standard forms and ter-
minate with <CR><LF> (carriage return–line feed).

7.6.2 SDI-12 programmed mode/recorder mode

The datalogger can be programmed to read SDI-12 sensors or act as an SDI-12 sensor itself. The
SDI12Recorder() instruction automates sending commands and recording responses. With
this instruction, the commands to poll sensors and retrieve data is done automatically with
proper elapsed time between the two. The datalogger automatically issues retries. See CRBasic
Editor help for more information on this instruction.
Commands entered into the SDIRecorder() instruction differ slightly in function from similar
commands entered in transparent mode. In transparent mode, for example, the operator manu-
ally enters aM! and aD0! to initiate a measurement and get data, with the operator providing
the proper time delay between the request for measurement and the request for data. In pro-
grammed mode, the datalogger provides command and timing services within a single line of
code. For example, when the SDI12Recorder() instruction is programmed with the M! com-
mand (note that the SDI-12 address is a separate instruction parameter), the datalogger issues the
aM! and aD0! commands with proper elapsed time between the two. The datalogger auto-
matically issues retries and performs other services that make the SDI-12 measurement work as
trouble free as possible.
For troubleshooting purposes, responses to SDI-12 commands can be captured in programmed
mode by placing a variable declared As String in the variable parameter. Variables not
declared As String will capture only numeric data.

7.6.3 Programming the datalogger to act as an SDI-12

sensor
The SDI12SensorSetup() / SDI12SensorResponse() instruction pair programs the
datalogger to behave as an SDI-12 sensor. A common use of this feature is to copy data from the
datalogger to other Campbell Scientific dataloggers over a single data-wire interface (terminal
configured for SDI-12 to terminal configured for SDI-12), or to copy data to a third-party SDI-12
recorder.

7. Communications 78
Details of using the SDI12SensorSetup() / SDI12SensorResponse() instruction pair
can be found in the CRBasic Editor help.
When programmed as an SDI-12 sensor, the datalogger will respond to SDI-12 commands M, MC,
C, CC, R, RC, V, ?, and I.
When acting as a sensor, the datalogger can be assigned only one SDI-12 address per SDI-12
port. For example, a datalogger will not respond to both 0M! and 1M! on SDI-12 port C1.
However, different SDI-12 ports can have unique SDI-12 addresses.

7.6.4 SDI-12 power considerations

When a command is sent by the datalogger to an SDI-12 probe, all probes on the same SDI-12
port will wake up. However, only the probe addressed by the datalogger will respond. All other
probes will remain active until the timeout period expires.
Example:
Probe: Water Content
Power Usage:

l Quiescent: 0.25 mA
l Active: 66 mA
l Measurement: 120 mA

Measurement time: 15 s
Timeout: 15 s
Probes 1, 2, 3, and 4 are connected to SDI-12 port C1.
The time line in the following table shows a 35-second power-usage profile example.
For most applications, total power usage of 318 mA for 15 seconds is not excessive, but if 16
probes were wired to the same SDI-12 port, the resulting power draw would be excessive. Spread-
ing sensors over several SDI-12 terminals helps reduce power consumption.

Table 7-1: Example power use for a network of SDI-12 probes

All Time
Time into Meas- Probe Probe Probe Probe Total
Command Probes Out
urement Processes 1 (mA) 2 (mA) 3 (mA) 4 (mA) (mA)
Awake Expires
Sleep 0.25 0.25 0.25 0.25 1
1 1M! Yes 120 66 66 66 318
2–14 120 66 66 66 318

7. Communications 79
Table 7-1: Example power use for a network of SDI-12 probes
All Time
Time into Meas- Probe Probe Probe Probe Total
Command Probes Out
urement Processes 1 (mA) 2 (mA) 3 (mA) 4 (mA) (mA)
Awake Expires
15 Yes 120 66 66 66 318
16 1D0! Yes 66 66 66 66 264
17-29 66 66 66 66 264
30 Yes 66 66 66 66 264
Sleep 0.25 0.25 0.25 0.25 1

7. Communications 80
8. Maintaining your datalogger
Protect the datalogger from humidity and moisture. When humidity levels reach the dewpoint,
condensation occurs, and damage to datalogger electronics can result. Adequate desiccant
should be placed in instrumentation enclosure to provide protection, and control humidity. Desic-
cant should be changed periodically.
If sending the datalogger to Campbell Scientific for calibration or repair, consult first with Camp-
bell Scientific. If the datalogger is malfunctioning, be prepared to perform some troubleshooting
procedures (see Tips and troubleshooting (p. 93)).
Also, consider checking, or posting your question to, the Campbell Scientific user forum
http://www.campbellsci.com/forum. Our web site https://www.campbellsci.com has additional
manuals (with example programs), FAQs, specifications and compatibility information for all of
our products.
Video tutorials https://www.campbellsci.com/videos and blog articles https://www.camp-
bellsci.com/blog are also useful troubleshooting resources.
If calibration or repair is needed, the procedure shown on: https://www.campbellsci.com/repair
should be followed when sending the product.

8.1 Datalogger calibration 81

8.2 Datalogger security 82
8.3 Datalogger enclosures 86
8.4 Internal battery 86
8.5 Electrostatic discharge and lightning protection 88
8.6 Power budgeting 89
8.7 Updating the operating system 89

8.1 Datalogger calibration

Campbell Scientific recommends factory recalibration every three years. During calibration, all
the input terminals, peripheral and communications ports, operating system, and memory areas
are checked; and the internal battery is replaced. The datalogger is checked to ensure that all
hardware operates within published specifications before it is returned. To request recalibration
for a product, see www.campbellsci.com/repair.

8. Maintaining your datalogger 81

It is recommended that you maintain a level of calibration appropriate to the datalogger applic-
ation. Consider the following factors when setting a calibration schedule:

l The importance of the measurements

l How long the datalogger will be used
l The operating environment
l How the datalogger will be handled

You can download and print calibration certificates for many products you have purchased by
logging in to the Campbell Scientific website and going to: https://www.camp-
bellsci.com/calcerts.

NOTE:
Note, you will need your product's serial number to access its certificate.

Watch an instructional video.

8.2 Datalogger security

Datalogger security concerns include:

l Collection of sensitive data

l Operation of critical systems
l Networks that are accessible to many individuals

Some options to secure your datalogger from mistakes or tampering include:

l Sending the latest operating system to the datalogger. See Updating the operating system
(p. 89) for more information.
l Disabling unused services and securing those that are used. This includes disabling HTTP,
HTTPS, FTP, Telnet, and Ping network services (Device Configuration Utility > Deployment
> Network Services tab). These services can be used to discover your datalogger on an IP
network.

NOTE:
FTP, Telnet, and Ping services are disabled by default.

l Setting security codes (see following information under "Security Codes").

l Setting a PakBus/TCP password. The PakBus TCP password controls access to PakBus com-
munication over a TCP/IP link. PakBusTCP passwords can be set in Device Configuration
Utility.
l Disabling FTP or setting an FTP username and password in Device Configuration Utility.

8. Maintaining your datalogger 82

l Setting a PakBus encryption (AES-128) key in Device Configuration Utility. This forces
PakBus data to be encrypted during transmission.
l Disabling HTTP/HTTPS or creating a .csipasswd file to secure HTTP/HTTPS (see Creat-
ing a .csipasswd file (p. 84) for more information).
l Enabling HTTPS and disabling HTTP. To prevent data collection via the web interface, both
HTTP and HTTPS must be disabled.
l Tracking Operating System, Run, and Program signatures.
l Encrypting program files if they contain sensitive information (see CRBasic help FileEn-
crypt() instruction or use the CRBasic Editor File menu, Save and Encrypt option).
l Hiding program files for extra protection (see CRBasic help FileManage() instruction).
l Monitoring your datalogger for changes by tracking program and operating system sig-
natures, as well as CPU file contents.
l Securing the physical datalogger and power supply under lock and key.

WARNING:
All security features can be subverted through physical access to the datalogger. If absolute
security is a requirement, the physical datalogger must be kept in a secure location.

8.2.1 Security codes

The datalogger employs a security scheme that includes three levels of security. Security codes
can effectively lock out innocent tinkering and discourage wannabe hackers on all com-
munication links. However, any serious hacker with physical access to the datalogger or to the
communications hardware can, with only minimal trouble, overcome the five-digit security codes.
Security codes are held in the datalogger Settings Editor.
The preferred methods of enabling security include the following:

l Device Configuration Utility: Security codes are set on the Deployment> Datalogger tab.
l Network Planner: Security codes can be set as dataloggers are added to the network.

Alternatively, in CRBasic the SetSecurity() instruction can be used. It is only executed at pro-
gram compile time. This is not recommended because deleting SetSecurity() from a
CRBasic program is not equivalent to SetSecurity(0,0,0). Settings persist when a new pro-
gram is downloaded that has no SetSecurity() instruction.
Up to three levels of security can be set. Valid security codes are 1 through 65535 ( 0 confers no
security). Security 1 must be set before Security 2. Security 2 must be set before Security 3. If any
one of the codes is set to 0, any security code level greater than it will be set to 0. For example, if
Security 2 is 0 then Security 3 is automatically set to 0. Security codes are unlocked in reverse
order: Security 3 before Security 2, Security 2 before Security 1.

8. Maintaining your datalogger 83

Table 8-1: Functions affected by security codes
Function Security code 1 set Security code 2 set Security code 3 set
Datalogger pro-
Cannot change or retrieve
gram
Settings editor
Writable variables cannot be changed
and Status table All communications pro-
Setting clock unrestricted Cannot change or set hibited

Writable variables cannot be

Public table unrestricted
changed
Collecting data unrestricted unrestricted

See Security (p. 119) for the related fields in the Settings Editor.
For additional information on datalogger security, see:

l 4 Ways to Make your Data More Secure

l Available Security Measures for Internet-Connected Dataloggers
l How to Use Datalogger Security Codes
l How Can Data be Made More Secure on a CRBasic PakBus Datalogger

8.2.2 Creating a .csipasswd file

The datalogger employs a security code scheme that includes three levels of security (see Data-
logger security (p. 82) for more information). This scheme can be used to limit access to a data-
logger that is publicly available. However, the security codes are visible in Device Configuration
Utility. In addition, the range of codes is relatively small. To provide a more robust means of secur-
ity, Basic access authentication was implemented with the HTTP API interface in the form of an
encrypted password file named .csipasswd. Read/write access to the web interface requires a
.csipasswd file. The web interface provides access to real-time and stored datalogger data.
For more information on the web interface, watch an instructional video.
When a file named .csipasswd is stored on the datalogger CPU drive, basic access authen-
tication is enabled in the datalogger and read/write access to the web interface can be defined.
Multiple user accounts with differing levels of access can be defined for one datalogger. Four
levels of access are available:

l None: Disable a user account.

l Read Only: Data collection is unrestricted. Clock and writable variables cannot be changed.
Programs cannot be viewed, stopped, deleted, or retrieved.

8. Maintaining your datalogger 84

l Read/Write: Data collection is unrestricted. Clock and writable variables can be changed.
Programs cannot be viewed, stopped, deleted, or retrieved.
l All: Data collection is unrestricted. Clock and writable variables can be changed. Programs
can be viewed, stopped, deleted and retrieved.

NOTE:
All levels of access allow data collection.

Create an encrypted password file or modify an existing password file using Device Configuration
Utility:

1. Connect to your device in Device Configuration Utility.

2. Click the Network Services tab, then the Edit .csipasswd File button.
3. Define user accounts and access levels.
4. Click Apply. The .csipasswd file is automatically saved to the datalogger CPU drive.

When a .csipasswd file is used, the PakBus/TCP Password security setting is not used when
accessing the datalogger via HTTP. If the .csipasswd file is blank or does not exist, the default
user name is "anonymous" with no password and a user level of read only.
When access to the datalogger web server is attempted without the appropriate security level,
the datalogger will prompt the web client to display a username and password request dialog. If
an invalid username or password is entered, the datalogger web server will default to the level of
access assigned to “anonymous”. As noted previously, anonymous is assigned a user level of
read-only, though this can be changed using Device Configuration Utility.
If the numeric security code has been enabled, and no .csipasswd file is on the datalogger,
then that numeric security code must be entered to access the datalogger. If a .csipasswd file
is on the datalogger, the username and password employed by the basic access authentication
will eliminate the need for entering the numeric security code.

8.2.2.1 Command syntax

Syntax for the commands sent to the web server generally follows the form of:
URL?command=CommandName&uri=DataSource&arguments
Arguments are appended to the command string using an ampersand (&). Some commands have
optional arguments, where omitting the argument results in a default being used. When applic-
able, optional arguments and their defaults are noted and examples are provided in the CRBasic
help (search Web Server/API Commands).

8. Maintaining your datalogger 85

8.3 Datalogger enclosures
The datalogger and most of its peripherals must be protected from moisture and humidity. Mois-
ture in the electronics will seriously damage the datalogger. In most cases, protection from mois-
ture is easily accomplished by placing the datalogger in a weather-tight enclosure with desiccant
and elevating the enclosure above the ground. Desiccant in enclosures should be changed peri-
odically.

WARNING:
Do not completely seal the enclosure if lead-acid batteries are present; hydrogen gas gen-
erated by the batteries may build to an explosive concentration.

The following details a typical installation using a Campbell Scientific enclosure. The datalogger
has mounting holes through which small screws are inserted into nylon anchors in the backplate.

8.4 Internal battery

The lithium battery powers the internal clock when the datalogger is not powered. The internal
lithium battery has a six-year life when no external power source is applied. Its life is extended
when the datalogger is installed with an external power source. If the datalogger is used in a
high-temperature application, the battery life is shortened.
To prevent clock and memory issues, it is recommended you proactively replace the battery every
5 years, or more frequently when operating continuously in high temperatures. For example,
replace at least every 2 years if operating continuously at 80 °C.

NOTE:
The battery is replaced during regular factory recalibration, which is recommended every 3
years. For more information, see Datalogger calibration (p. 81).

8. Maintaining your datalogger 86

When the lithium battery is removed (or is depleted and primary power to the datalogger is
removed), the CRBasic program and most settings are maintained, but the following are lost:

l Temporary program memory (current values for variables).

l Routing and communication logs (relearned without user intervention).
l Time. Clock will need resetting when the battery is replaced.

A replacement lithium battery can be purchased from Campbell Scientific or another supplier.

l 3 V coin cell CR2016 for battery-backed clock. 6-year life with no external power source.

See Power requirements (p. 164) for more information.

WARNING:
Misuse or improper installation of the internal lithium battery can cause severe injury. Fire,
explosion, and severe burns can result. Do not recharge, disassemble, heat above 100 °C (212
°F), solder directly to the cell, incinerate, or expose contents to water. Dispose of spent lith-
ium batteries properly.

NOTE:
The Status field Battery value and the destination variable from the Battery() instruction
(often called batt_volt) in the Public table reference the external battery voltage.

8.4.1 Replacing the internal battery

It is recommended that you send the datalogger in for scheduled calibration, which includes
internal battery replacement (see Datalogger calibration (p. 81)).

WARNING:
Any damage made to the datalogger during user replacement of the internal battery is not
covered under warranty.

1. Loosen or remove the screws from the sides of the datalogger.

2. Pull the bottom and top of the datalogger apart.
3. Carefully pinch each of the four plastic pins and pull the top circuit board away from the
mounts and connector. A wire connects the board, do not pull the board too far and dam-
age the wire connection.
4. Remove the lithium battery by gently prying it out with a small flat-bladed screwdriver.
5. Install new battery.
6. Reassemble the datalogger. Take particular care to ensure the board is reseated tightly
onto the plastic pins and connector.

8. Maintaining your datalogger 87

8.5 Electrostatic discharge and lightning
protection
WARNING:
Lightning strikes may damage or destroy the datalogger, associated sensors and power sup-
plies.

Electrostatic discharge (ESD) can originate from several sources, the most common and destruct-
ive are primary and secondary lightning strikes. Primary lightning strikes hit instrumentation dir-
ectly. Secondary strikes induce voltage in power lines or wires connected to instrumentation.
While elaborate, expensive, and nearly infallible lightning protection systems are on the market,
Campbell Scientific, for many years, has employed a simple and inexpensive design that protects
most systems in most circumstances. The system consists of a lightning rod, metal mast, heavy-
gauge ground wire, and ground rod to direct damaging current away from the datalogger. This
system, however, is not infallible. The following image displays a typical application of the sys-
tem:

8. Maintaining your datalogger 88

All critical inputs and outputs on the datalogger are ESD protected to 75 V. To be effective, the
earth ground lug must be properly connected to earth (chassis) ground.
Communications ports are another path for transients. You should provide communications
paths, such as telephone or short-haul modem lines, with spark-gap protection. Spark-gap pro-
tection is usually an option with these products; so, request it when ordering. Spark gaps must be
connected to earth (chassis) ground.
For detailed information on grounding, see Grounds (p. 9).

8.6 Power budgeting

In low-power situations, the datalogger can operate for several months on non-rechargeable bat-
teries. Power systems for longer-term remote applications typically consist of a charging source, a
charge controller, and a rechargeable battery. When ac line power is available, a Vac-to-Vdc wall
adapter, the onboard charging regulator, and a rechargeable battery can be used to construct an
uninterruptible power supply (UPS).
When designing a power supply, consider worst-case power requirements and environmental
extremes. For example, the power requirement of a weather station may be substantially higher
during extreme cold, while at the same time, the extreme cold constricts the power available from
the power supply. System operating time for batteries can be estimated by dividing the battery
capacity (ampere hours) by the average system current drain (amperes).
For more information see:

l Application Note - Power Supplies

l Power Budget Spreadsheet
l Video Tutorial - Power Budgeting

l Power input (p. 7)

l Power output (p. 8)
l Power requirements (p. 164)
l Power output specifications (p. 166)

8.7 Updating the operating system

Campbell Scientific posts operating system (OS) updates at www.campbellsci.com/downloads
when they become available. It is recommended that before deploying instruments, you check
operating system versions and update them as needed. The datalogger operating system version
is shown in the Status table, Station Status Summary, and Device Configuration Utility

8. Maintaining your datalogger 89

Deployment > Datalogger. An operating system may be sent through Device Configuration Util-
ity or through program-send procedures.

WARNING:
Because sending an OS resets datalogger memory and resets all settings on the datalogger to
factory defaults, data loss will certainly occur. Depending on several factors, the datalogger
may also become incapacitated for a time.

TIP:
It is recommended that you retrieve data from the datalogger and back up your programs
and settings before updating your OS. To collect data using LoggerNet, connect to your data-
logger and click Collect Now . To backup your datalogger, connect to it in Device Con-
figuration Utility, click the Backup menu and select Backup Datalogger.

8.7.1 Sending an operating system to a local datalogger

Send an OS using Device Configuration Utility. This method requires a direct connection
between your datalogger and computer.

1. Download the latest Operating System at www.campbellsci.com/downloads.

2. Locate the .exe download and double-click to run the file. This will extract the .obj OS file
to the C:\Campbellsci\Lib\OperatingSystems folder.
3. Supply power to the datalogger. If connecting via USB for the first time, you must first
install USB drivers by using Device Configuration Utility (select your datalogger, then on
the main page, click Install USB Driver). Alternately, you can install the USB drivers using EZ
Setup. A USB connection supplies 5 V power (as well as a communication link), which is
adequate for setup, but a 12 V battery will be needed for field deployment.
4. Physically connect your datalogger to your computer using a USB cable, then open Device
Configuration Utility and select your datalogger.
5. Select the communications port used to communicate with the datalogger from the COM
Port list (you do not need to click Connect).
6. Click the Send OS tab. At the bottom of the window, click Start.
7. On the Avoid Conflicts with the Local Server window, click OK.
8. Navigate to the C:\Campbellsci\Lib\OperatingSystems folder.
9. Ensure Datalogger Operating System Files (*.obj) is selected in the Files of type list, select
the new OS .obj file, and click Open to update the OS on the datalogger.

Watch a video: Sending an OS to a Local Datalogger.

8. Maintaining your datalogger 90

8.7.2 Sending an operating system to a remote data-
logger
CAUTION:
Sending an OS remotely to a datalogger with Operating System 4 or earlier is not recom-
mended. These dataloggers should be updated using the previous instruction (Sending an
operating system to a local datalogger (p. 90)).

If you have a datalogger that is already deployed, you can update the OS over a tele-
communications link by sending the OS to the datalogger as a program. In most instances, send-
ing an OS as a program preserves settings. This allows for sending supported operating systems
remotely (check the release notes). However, this should be done with great caution as updating
the OS may reset the datalogger settings, even settings critical to supporting the tele-
communication link.

1. Download the latest Operating System at www.campbellsci.com/downloads.

2. Locate the .exe download and double-click to run the file. This will extract the .obj OS file
to the C:\Campbellsci\Lib\OperatingSystems folder.
3. Using datalogger support software, connect to your datalogger.
l LoggerNet users, select Main and click Connect on the LoggerNet toolbar, select
the datalogger from the Stations list, then click Connect .
l PC200W and PC400 users, select the datalogger from the list and click Connect .
4. Select File Control at the top of the Connect window.
5. Click Send at the top of the File Control window.
6. Navigate to the C:\Campbellsci\Lib\OperatingSystems folder.
7. Ensure Datalogger Operating System Files (*.obj) is selected in the files of type list, select
the new OS .obj file, and click Open to update the OS on the datalogger.

8. Maintaining your datalogger 91

Note the following precautions when sending as a program:

l Any peripherals being powered through the SW12 terminal will be turned off until the pro-
gram logic turns them on again.
l Operating systems are very large files. Be cautious of data charges. Sending over a direct
serial or USB connection is recommended, when possible.

8. Maintaining your datalogger 92

9. Tips and troubleshooting
Start with these basic procedures if a system is not operating properly.

1. Using a voltmeter, check the voltage of the primary power source at the CHG and BAT ter-
minals on the face of the datalogger, it should be 10 to 18 Vdc. If connecting to a power
source via the CHG terminals, voltage measured should be 16 to 32 Vdc.
2. Check wires and cables for the following:
l Incorrect wiring connections. Make sure each sensor and device are wired to the ter-

minals assigned in the program. If the program was written in Short Cut, check wiring
against the generated wiring diagram. If written in CRBasic Editor, check wiring
against each measurement and control instruction.
l Loose connection points

l Faulty connectors

l Cut wires

l Damaged insulation, which allows water to migrate into the cable. Water, whether or

not it comes in contact with wire, can cause system failure. Water may increase the
dielectric constant of the cable sufficiently to impede sensor signals, or it may
migrate into the sensor, which will damage sensor electronics.
3. Check the CRBasic program. If the program was written solely with Short Cut, the program
is probably not the source of the problem. If the program was written or edited with
CRBasic Editor, logic and syntax errors could easily have crept in. To troubleshoot, create a
simpler version of the program, or break it up into multiple smaller units to test indi-
vidually. For example, if a sensor signal-to-data conversion is faulty, create a program that
only measures that sensor and stores the data, absent from all other inputs and data.
4. Reset the datalogger. Sometimes the easiest way to resolve a problem is by resetting the
datalogger (see Resetting the datalogger (p. 100) for more information).

For additional troubleshooting options, see:

9.1 Checking station status 94

9.2 Understanding NAN and INF occurrences 96
9.3 Timekeeping 97
9.4 CRBasic program errors 99
9.5 Troubleshooting Radio Communications 100
9.6 Reducing Out of Memory Errors 100

9. Tips and troubleshooting 93

9.7 Resetting the datalogger 100
9.8 Troubleshooting power supplies 102
9.9 Minimizing ground loop errors 103
9.10 Improving voltage measurement quality 104
9.11 Field calibration 115
9.12 File name and resource errors 115
9.13 Information tables and settings (advanced) 115
Also, consider checking, or posting your question to, the Campbell Scientific user forum
http://www.campbellsci.com/forum. Our web site https://www.campbellsci.com has additional
manuals (with example programs), FAQs, specifications and compatibility information for all of
our products.
Video tutorials https://www.campbellsci.com/videos and blog articles https://www.camp-
bellsci.com/blog are also useful troubleshooting resources.

9.1 Checking station status

View the condition of the datalogger using Station Status. Here you see the operating system ver-
sion of the datalogger, the name of the current program, program compile results, and other key
indicators. Items that may need your attention appear in red or blue. The following information
describes the significance of some entries in the station status window. Watch a video or use the
following instructions.

9.1.1 Viewing station status

Using your datalogger support software, access the Station Status to view the condition of the
datalogger.

l From LoggerNet: Click Connect , then Station Status to view the Summary tab.
l From PC200W and PC400: Select the Datalogger menu and Station Status to view the
Summary tab.

9.1.2 Watchdog errors

Watchdog errors indicate that the datalogger has crashed and reset itself. Experiencing a few
watchdog errors is normal. You can reset the Watchdog error counter in the Station Status >
Status Table.

9. Tips and troubleshooting 94

TIP:
Before resetting the counter, make note of the number accumulated and the date.

Watchdog errors could be due to:

l Transient voltage
l Incorrectly wired or malfunctioning sensor
l Poor ground connection on the power supply
l Numerous PortSet() instructions back-to-back with no delay
l High-speed serial data on multiple ports with very large data packets or bursts of data

The error "Results for Last Program Compiled: Warning: Watchdog Timer IpTask Triggered" can
result from:

l The IP communications on the datalogger got stuck, and the datalogger had to reboot
itself to recover. Or communications failures may cause the datalogger to reopen the IP
connections more than usual. Check your datalogger operating system version; recent oper-
ating system versions have improved stability of IP communications.

If any of these are not the apparent cause, contact Campbell Scientific for assistance (see
https://www.campbellsci.com/support). Causes that may require assistance include:

l Memory corruption
l Operating System problem
l Hardware problem
l IP communications problem

9.1.3 Results for last program compiled

Messages generated by the datalogger at program upload and as the program runs are reported
here. Warnings indicate that an expected feature may not work, but the program will still oper-
ate. Errors indicate that the program cannot run. For more information, see CRBasic program
errors (p. 99).

9.1.4 Skipped scans

Skipped scans are caused when a program takes longer to process than the scan rate allows. An
occasional skipped scan can be caused by memory formatting as discussed in Data memory (p.
45). If any scan skips repeatedly, the datalogger program may need to be optimized or reduced.
For more information, see: How to Prevent Skipped Scans and a Sunburn.

9. Tips and troubleshooting 95

9.1.5 Skipped records
Skipped records usually occur because a scan is skipped. They indicate that a record was not
stored to the data table when it should have been.

9.1.6 Variable out of bounds

Variable-out-of-bounds errors happen when an array is not sized to the demands of the pro-
gram. The datalogger attempts to catch out-of-bounds errors at compile time. However, it is not
always possible; so, these errors may occur during runtime. Variable-out-of-bounds errors are
always caused by programming problems.

9.1.7 Battery voltage

If powering through USB, reported battery voltage should be 0 V. If connecting to an external
power source, battery voltage should be reported at or near 12 V. See also:

l Power input (p. 7)

l Power requirements (p. 164)

9.2 Understanding NAN and INF

occurrences
NAN (not a number) and INF (infinite) are data words indicating an exceptional occurrence in
datalogger function or processing. INF indicates that the program has encountered an arithmetic
expression that is undefined. NAN indicates an invalid measurement. For more information, see
Tips and Tricks: Who's NAN?
NANs are expected in the following conditions:

l Input signals exceed the voltage range chosen for the measurement.
l An invalid SDI-12 command is sent
l An SDI-12 sensor does not respond or aborts without sending data
l Undefined arithmetic expressions, such as 0 ÷ 0.

NAN is a constant that can be used in expressions. This is shown in the following code snip that
sets a CRBasic variable to False when the wind direction is NAN:
If WindDir = NAN Then
WDFlag = False
Else
WDFlag = True
EndIf

9. Tips and troubleshooting 96

If an output processing instruction encounters a NAN in the values being processed, NAN will be
stored. For example, if one measurement in a data storage interval results in NAN, then the aver-
age, maximum and minimum will record NAN.

NOTE:
There is no such thing as NAN for integers. Values that are converted from float to integer
will be expressed in data tables as the most negative number for a given data type. For
example, the most negative number of data type FP2 is –7999; so, NAN for FP2 data will
appear in a data table as –7999. If the data type is Long, NAN will appear in the data table as
–2,147,483,648.

Because NAN is a constant, it can be used in conjunction with the disable variable parameter
(DisableVar) in output processing instructions. Use variable = NAN in the DisableVar
parameter to discard NANs from affecting the other good values.

9.3 Timekeeping
Measurement of time is an essential datalogger function. Time measurement with the onboard
clock enables the datalogger to run on a precise interval, attach time stamps to data, measure
the interval between events, and time the initiation of control functions. Details on clock accur-
acy and resolution are available in the System specifications (p. 163). An internal lithium battery
backs the clock when the datalogger is not externally powered (see Internal battery (p. 86)).

9.3.1 Clock best practices

When setting the clock with LoggerNet, initiate it manually during a maintenance period when
the datalogger is not actively writing to Data Tables. Click the Set button in the Clocks field of
the LoggerNet Connect Screen.
If you are going to use automated clock check with LoggerNet (clock settings can be found on
the LoggerNet Setup Standard View Clock tab). it is recommended that you do this on the order
of days (not hours). Set an allowed clock deviation that is appropriate for the expected jitter in
the network, and use the initial time setting to offset the clock check away from storage and
measurement intervals.
The amount of time required for a Clock Check command to reach the datalogger, be processed,
and for it to send its response is called round-trip time, or time-of-flight. To calculate an estimate
of this time-of-flight, LoggerNet maintains a history (in order) of the round-trip times for the ten
previous successful clock check transactions. It adds this average to the time values received from
the datalogger and subtracts it from any adjustment that it might make.

9. Tips and troubleshooting 97

9.3.2 Time stamps
A measurement without an accurate time reference often has little meaning. Data collected from
dataloggers is stored with time stamps. How closely a time stamp corresponds to the actual time
a measurement is taken depends on several factors.
The time stamp in common CRBasic programs matches the time at the beginning of the current
scan as measured by the real-time datalogger clock. If a scan starts at 15:00:00, data output dur-
ing that scan will have a time stamp of 15:00:00 regardless of the length of the scan, or when in
the scan a measurement is made. The possibility exists that a scan will run for some time before a
measurement is made. For instance, a scan may start at 15:00:00, execute a time-consuming part
of the program, then make a measurement at 15:00:00.51. The time stamp attached to the meas-
urement, if the CallTable() instruction is called from within the Scan() / NextScan con-
struct, will be 15:00:00, resulting in a time-stamp skew of 510 ms.

9.3.3 Avoiding time skew

Time skew between consecutive measurements is a function of settling and integration times,
ADC, and the number entered into the Reps parameter of CRBasic instructions. A close approx-
imation is:

time skew = reps * (settling time + integration time + ADC time) + instruction setup
time
where ADC time equals 170 µs, and instruction setup time is 15 µs.
If reps (repetitions) > 1 (multiple measurements by a single instruction), no setup
time is required. If reps = 1 for consecutive voltage instructions, include the setup
time for each instruction.

Time-stamp skew is not a problem with most applications because:

l Program execution times are usually short; so, time-stamp skew is only a few milliseconds.
Most measurement requirements allow for a few milliseconds of skew.
l Data processed into averages, maxima, minima, and so forth are composites of several
measurements. Associated time stamps only reflect the time of the scan when processing
calculations were completed; so, the significance of the exact time a specific sample was
measured diminishes.

Applications measuring and storing sample data wherein exact time stamps are required can be
adversely affected by time-stamp skew. Skew can be avoided by:

l Making measurements in the scan before time-consuming code.

9. Tips and troubleshooting 98

l Programming the datalogger such that the time stamp reflects the system time rather than
the scan time using the DataTime() instruction. See topics concerning data table declar-
ations in CRBasic Editor help for more information.

9.4 CRBasic program errors

Analyze data soon after deployment to ensure the datalogger is measuring and storing data as
intended. Most measurement and data-storage problems are a result of one or more CRBasic pro-
gram bugs. Watch a video: CRBasic | Common Errors - Identifying and fixing common errors in
the CRBasic programming language.

9.4.1 Program does not compile

When a program is compiled, the CRBasic Editor checks the program for syntax errors and other
inconsistencies. The results of the check are displayed in a message window at the bottom of the
main window. If an error can be traced to a specific line in the program, the line number will be
listed before the error. Double-click an error preceded by a line number and that line will be high-
lighted in the program editing window. Correct programming errors and recompile the program.
Occasionally, the CRBasic Editor compiler states that a program compiles OK; however, the pro-
gram may not compile in the datalogger itself. This is rare, but reasons may include:

l The datalogger has a different operating system than the computer compiler. Check the
two versions if in doubt. The computer compiler version is shown on the first line of the
compile results. Update the computer compiler by first downloading the executable OS file
from www.campbellsci.com. When run, the executable file updates the computer compiler.
To update the datalogger operating system, see Updating the operating system (p. 89).
l The program has large memory requirements for data tables or variables and the data-
logger does not have adequate memory. This normally is flagged at compile time in the
compile results. If this type of error occurs:
o Check the CPU drive for copies of old programs. The datalogger keeps copies of all

program files unless they are deleted, the drive is formatted, or a new operating sys-
tem is loaded with Device Configuration Utility.

9.4.2 Program compiles but does not run correctly

If the program compiles but does not run correctly, timing discrepancies may be the cause. If a
program is tight on time, look further at the execution times. Check the measurement and pro-
cessing times in the Status table (MeasureTime, ProcessTime, MaxProcTime) for all scans, then try
experimenting with the InstructionTimes() instruction in the program. Analyzing

9. Tips and troubleshooting 99

InstructionTimes() results can be difficult due to the multitasking nature of the data-
logger, but it can be a useful tool for fine-tuning a program.

9.5 Troubleshooting Radio

Communications
If there are intermittent communication problems when connecting via radio, there may be
another network in the area causing interference. To help remove the interference, use Device
Configuration Utility to change the Network ID and RF Hop Sequence in all RF407, RF412, and
RF422 radios within a network (standalone or included in a datalogger) to another value. Each of
these settings must have the same value in all radios and dataloggers within a network. For
example, the Network ID in all devices could be set to 1726, and the RF Hop Sequence in all
devices could be set to 1. The Network ID can be any number between 0 and 32767. The RF Hop
Sequence can be any number between 0 and 7 in an RF407 or RF412 network; it can be any num-
ber between 0 and 9 in an RF422 network.
See also Radio communications (p. 26). For specifications information, see RF radio option spe-
cifications (p. 173).

9.6 Reducing Out of Memory Errors

When the datalogger gives an “Out of memory” error upon program compile, it means that there
is no unused continuous section of memory large enough to fit an element of the program. The
most common cause of this error is a large variable array. In that case, split the large array into
smaller arrays until the datalogger compiler accepts the program.
See also Data memory (p. 45).

9.7 Resetting the datalogger

A datalogger reset is sometimes referred to as a "memory reset." Backing up the current data-
logger configuration before a reset makes it easy to revert to the old settings. To back up the
datalogger configuration, connect to the datalogger using Device Configuration Utility, and click
Backup > Back Up Datalogger. To restore a configuration after the datalogger has been reset,
connect and click Backup > Restore Datalogger.
The following features are available for complete or selective reset of datalogger memory:

l Processor reset
l Program send reset

9. Tips and troubleshooting 100

l Manual data table reset
l Formatting memory drives
l Full memory reset

9.7.1 Processor reset

To reset the processor, simply power cycle the datalogger. This resets its short-term memory,
restarts the current program, sets variables to their starting values, and clears communications
buffers. This does not clear data tables but may result in a skipped record. If the datalogger is
remote, a power cycle can be mimicked in a Terminal Emulator program (type REBOOT <Enter>).

9.7.2 Program send reset

Final-data memory is erased when user programs are uploaded, unless preserve / erase data
options are used and the program was not altered. Preserve / erase data options are presented
when sending programs using File Control Send command and CRBasic Editor Compile, Save
and Send.

TIP:
It is good practice to always collect data before sending a program to the datalogger.

When a program compiles, all variables are initialized. A program is recompiled after a power fail-
ure or a manual stop. For instances that require variables to be preserved through a program
recompile, the CR300 series have the PreserveVariables() and Pre-
serveOneVariable() instructions and User Settings. Entries in User Settings are not erased
when a program is recompiled.
User Settings can be entered manually in Device Configuration Utility in the Settings Editor >
User Settings tab, or they can be written through a CRBasic program using the SetSetting()
instruction.

NOTE:
User settings are stored in flash memory. To avoid corrupting the flash memory, edit these set-
tings infrequently.

9.7.3 Manual data table reset

Data table memory is selectively reset from:

l Datalogger support software: Station Status > Table Fill Times tab, Reset Tables.
l Device Configuration Utility: Data Monitor tab, Reset Table button.

9. Tips and troubleshooting 101

9.7.4 Formatting drives
CPU, , and USB (module required) drives can be formatted individually. Formatting a drive erases
all files on that drive. If the currently running user program is on the drive to be formatted, the
program will cease running and data associated with the program are erased. Drive formatting is
performed through the datalogger support software File Control > Format command.

9.7.5 Full memory reset

Full memory reset occurs when an operating system is sent to the datalogger using Device Con-
figuration Utility or when entering 98765 in the Status table field FullMemReset (see
FullMemReset (p. 122)). A full memory reset does the following:

l Clears and formats CPU drive (all program files erased)

l Clears data tables.
l Clears Status table fields.
l Restores settings to default.
l Initializes system variables.
l Clears communications memory.

See Updating the operating system (p. 89) for more information.

9.8 Troubleshooting power supplies

Power supply systems may include batteries, charging regulators, and a primary power source
such as solar panels or ac/ac or ac/dc transformers attached to mains power. All components may
need to be checked if the power supply is not functioning properly. Check connections and
check polarity of connections.
Base diagnostic: connect the datalogger to a new 12 V battery. (A small 12 V battery carrying a
full charge would be a good thing to carry in your maintenance tool kit.) Ensure correct polarity
of the connection. If the datalogger powers up and works, troubleshoot the datalogger power
supply.
When diagnosing or adjusting power equipment supplied by Campbell Scientific, it is recom-
mended you consider:

l Battery-voltage test
l Charging-circuit test (when using an unregulated solar panel)
l Charging-circuit test (when using a transformer)
l Adjusting charging circuit

9. Tips and troubleshooting 102

If power supply components are working properly and the system has peripherals with high cur-
rent drain, such as a satellite transmitter, verify that the power supply is designed to provide
adequate power. For additional information, see Power budgeting (p. 89).

9.9 Minimizing ground loop errors

When measuring soil moisture with a resistance block, or water conductivity with a resistance
cell, the potential exists for a ground loop error. In the case of an ionic soil matric potential (soil
moisture) sensor, a ground loop arises because soil and water provide an alternate path for the
excitation to return to datalogger ground. This example is modeled in the following image:

With Rg in the resistor network, the signal measured from the sensor is described by the fol-
lowing equation:

where

l Vx is the excitation voltage

l Rf is a fixed resistor
l Rs is the sensor resistance
l Rg is the resistance between the excited electrode and datalogger earth ground.

RsRf/Rg is the source of error due to the ground loop. When Rg is large, the error is negligible.
Note that the geometry of the electrodes has a great effect on the magnitude of this error. The
Delmhorst gypsum block used in the Campbell Scientific 227 probe has two concentric cylindrical

9. Tips and troubleshooting 103

electrodes. The center electrode is used for excitation; because it is encircled by the ground elec-
trode, the path for a ground loop through the soil is greatly reduced. Moisture blocks that consist
of two parallel plate electrodes are particularly susceptible to ground loop problems. Similar con-
siderations apply to the geometry of the electrodes in water conductivity sensors.
The ground electrode of the conductivity or soil moisture probe and the datalogger earth ground
form a galvanic cell, with the water/soil solution acting as the electrolyte. If current is allowed to
flow, the resulting oxidation or reduction will soon damage the electrode, just as if dc excitation
was used to make the measurement. Campbell Scientific resistive soil probes and conductivity
probes are built with series capacitors to block this dc current. In addition to preventing sensor
deterioration, the capacitors block any dc component from affecting the measurement.
See also Grounds (p. 9).

9.10 Improving voltage measurement

quality
The following topics discuss methods of generally improving voltage measurements:

9.10.1 Deciding between single-ended or differential measurements 104

9.10.2 Minimizing ground potential differences 105
9.10.3 Minimizing power-related artifacts 107
9.10.4 Filtering to Reduce Measurement Noise 108
9.10.5 Minimizing settling errors 110
9.10.6 Factors affecting accuracy 113
9.10.7 Minimizing offset voltages 114
Read More: Consult the following technical papers at www.campbellsci.com/app-notes for in-
depth treatments of several topics addressing voltage measurement quality:

l Preventing and Attacking Measurement Noise Problems

l Benefits of Input Reversal and Excitation Reversal for Voltage Measurements
l Voltage Accuracy, Self-Calibration, and Ratiometric Measurements

9.10.1 Deciding between single-ended or differential

measurements
Deciding whether a differential or single-ended measurement is appropriate is usually, by far, the
most important consideration when addressing voltage measurement quality. The decision

9. Tips and troubleshooting 104

requires trade-offs of accuracy and precision, noise cancellation, measurement speed, available
measurement hardware, and fiscal constraints.
In broad terms, analog voltage is best measured differentially because these measurements
include the following noise reduction features that are not included in single-ended meas-
urements.

l Passive Noise Rejection

o No voltage reference offset
o Common-mode noise rejection, which filters capacitively coupled noise

Reasons for using single-ended measurements, however, include:

l Not enough differential terminals are available. Differential measurements use twice as
many analog input terminals as do single-ended measurements.
l Rapid sampling is required. Single-ended measurement time is about half that of dif-
ferential measurement time.
l Sensor is not designed for differential measurements. Some Campbell Scientific sensors are
not designed for differential measurement, but the drawbacks of a single-ended meas-
urement are usually mitigated by large programmed excitation and/or sensor output
voltages.

Sensors with a high signal-to-noise ratio, such as a relative-humidity sensor with a full-scale out-
put of 0 to 1000 mV, can normally be measured as single-ended without a significant reduction
in accuracy or precision.
Sensors with a low signal-to-noise ratio, such as thermocouples, should normally be measured
differentially. However, if the measurement to be made does not require high accuracy or pre-
cision, such as thermocouples measuring brush-fire temperatures, which can exceed 2500 °C, a
single-ended measurement may be appropriate. If sensors require differential measurement, but
adequate input terminals are not available, an analog multiplexer should be acquired to expand
differential input capacity.
Because a single-ended measurement is referenced to datalogger ground, any difference in
ground potential between the sensor and the datalogger will result in an error in the meas-
urement. For more information on grounds, see Grounds (p. 9) and Minimizing ground potential
differences (p. 105).

9.10.2 Minimizing ground potential differences

Low-level, single-ended voltage measurements (<200 mV) are sensitive to ground potential fluc-
tuation due to changing return currents from SW12 and C terminals. The datalogger grounding
scheme is designed to minimize these fluctuations by separating signal grounds ( ) from power

9. Tips and troubleshooting 105

grounds (G). For more information on datalogger grounds, see Grounds (p. 9). To take advant-
age of this design, observe the following rules:

l Connect grounds associated with SW12 and C terminals to G terminals.

l Connect excitation grounds to the nearest terminal on the same terminal block.
l Connect the low side of single-ended sensors to the nearest terminal on the same ter-
minal block.
l Connect shield wires to the terminal nearest the terminals to which the sensor signal
wires are connected.

If offset problems occur because of shield or ground wires with large current flow, tying the prob-
lem wires into terminals next to terminals configured for excitation and pulse-count should help.
Problem wires can also be tied directly to the ground lug to minimize induced single-ended off-
set voltages.

9.10.2.1 Ground potential differences

Because a single-ended measurement is referenced to datalogger ground, any difference in
ground potential between the sensor and the datalogger will result in a measurement error. Dif-
ferential measurements MUST be used when the input ground is known to be at a different
ground potential from datalogger ground.
Ground potential differences are a common problem when measuring full-bridge sensors (strain
gages, pressure transducers, etc), and when measuring thermocouples in soil.

l Soil Temperature Thermocouple: If the measuring junction of a thermocouple is not insu-

lated when in soil or water, and the potential of earth ground is, for example, 1 mV greater
at the sensor than at the point where the datalogger is grounded, the measured voltage
will be 1 mV greater than the thermocouple output. With a Type T (copper-constantan)
thermocouple, 1 mV equates to approximately 25 °C measurement error.
l External Signal Conditioner: External instruments with integrated signal conditioners, such
as an infrared gas analyzer (IRGA), are frequently used to make measurements and send
analog information to the datalogger. These instruments are often powered by the same
Vac-line source as the datalogger. Despite being tied to the same ground, differences in
current drain and wire resistance result in different ground potentials at the two instru-
ments. For this reason, a differential measurement should be made on the analog output
from the external signal conditioner.

For additional information, see Minimizing offset voltages (p. 114).

9. Tips and troubleshooting 106

9.10.3 Minimizing power-related artifacts
Some Vac-to-Vdc power converters produce switching noise or ac ripple as an artifact of the ac-
to-dc rectification process. Excessive switching noise on the output side of a power supply can
increase measurement noise, and so increase measurement error. Noise from grid or mains
power also may be transmitted through the transformer, or induced electromagnetically from
nearby motors, heaters, or power lines.
High-quality power regulators typically reduce noise due to power regulation. Using the 50 Hz or
60 Hz first notch frequency (fN1) option for CRBasic analog input measurement instructions
often improves rejection of noise sourced from power mains. The CRBasic standard deviation out-
put instruction, StdDev(), can be used to evaluate measurement noise.
The datalogger includes adjustable digital filtering, which serves two purposes:

l Arrive as close as possible to the true input signal

l Filter out measurement noise at specific frequencies, the most common being noise at 50
Hz or 60 Hz, which originate from mains-power lines.

Filtering time is inversely proportional to the frequency being filtered.

9.10.3.1 Minimizing electronic noise

Electronic noise can cause significant error in a voltage measurement, especially when measuring
voltages less than 200 mV. So long as input limitations are observed, the PGIA ignores voltages,

9. Tips and troubleshooting 107

including noise, that are common to each side of a differential-input pair. This is the common-
mode voltage. Ignoring (rejecting or canceling) the common-mode voltage is an essential fea-
ture of the differential input configuration that improves voltage measurements. The following
image illustrates the common-mode component (Vcm) and the differential-mode component
(Vdm) of a voltage signal. Vcm is the average of the voltages on the V+ and V– inputs. So, Vcm =
(V+ + V–)/2 or the voltage remaining on the inputs when Vdm = 0. The total voltage on the V+
and V– inputs is given as VH = Vcm + Vdm/2, and VL = Vcm – Vdm/2, respectively.

9.10.4 Filtering to Reduce Measurement Noise

The datalogger applies an adjustable filter to analog measurements, reducing signal components
at selected frequencies. The following figures show the frequency response of the filters applied
when the first notch frequency (fN1) is set to 4000, 400, or 50/60 Hz, respectively. Note that the
same filter is applied when fN1 is set to either 50 or 60 Hz, simultaneously filtering both 50 and
60 Hz signal components. Commonly, fN1 is set at 50 or 60 Hz in order to filter 50 or 60 Hz sig-
nal components, reducing noise from ac power mains.
Filtering comes at the expense of measurement time. The time required for filtering is 0.5 ms
when fN1 is set to 4000 Hz, 6.226 ms when fN1 is 400 Hz, and 49.812 ms when fN1 is set to
either 50 or 60 Hz. Random noise in the measurement results decreases, while measurement time
increases, as fN1 is set to smaller values. The total time required for a single result includes set-
tling + filtering + overhead.
A faster filter may be preferred to achieve the following objectives:

l Minimize time skew between successive measurements Avoiding time skew (p. 98).
l Maximize throughput rate.
l Maximize life of the datalogger power supply.
l Minimize polarization of polar sensors such as those for measuring conductivity, soil mois-
ture, or leaf wetness. Polarization may cause measurement errors or sensor degradation.

9. Tips and troubleshooting 108

l Improve accuracy of an LVDT measurement. The induced voltage in an LVDT decays with
time as current in the primary coil shifts from the inductor to the series resistance; a long
integration may result in most of signal decaying before the measurement is complete.

Consult the following technical paper at www.campbellsci.com/app-notes for in-depth treatment

of measurement noise: Preventing and Attacking Measurement Noise Problems.
fN1 set to 4000 Hz:

fN1 set to 400 Hz:

fN1 set to 50 or 60 Hz:

9. Tips and troubleshooting 109

9.10.5 Minimizing settling errors
Settling time allows an analog voltage signal to rise or fall closer to its true magnitude prior to
measurement. Default settling times, those resulting when the SettlingTime parameter is set
to 0, provide sufficient settling in most cases. Additional settling time is often programmed when
measuring high-resistance (high-impedance) sensors, or when sensors connect to the input ter-
minals by long cables. The time to complete a measurement increases with increasing settling
time. For example, a 1 ms increase in settling time for a bridge instruction with input reversal and
excitation reversal results in a 4 ms increase in time to perform the instruction.
When sensors require long cable lengths, use the following general practices to minimize settling
errors:

l Do not use leads with PVC-insulated conductors. PVC has a high dielectric constant, which
extends input settling time.
l Where possible, run excitation leads and signal leads in separate shields to minimize tran-
sients.
l When measurement speed is not a prime consideration, additional time can be used to
ensure ample settling time.
l In difficult cases where measurement speed is a consideration, an appropriate settling time
can be determined through testing.

9.10.5.1 Measuring settling time

Settling time for a particular sensor and cable can be measured with the CR300 series. Pro-
gramming a series of measurements with increasing settling times will yield data that indicate at

9. Tips and troubleshooting 110

what settling time a further increase results in negligible change in the measured voltage. The
programmed settling time at this point indicates the settling time needed for the sensor / cable
combination.
The following CRBasic Example: Measuring Settling Time presents CRBasic code to help determ-
ine settling time for a pressure transducer using a high-capacitance semiconductor. The code con-
sists of a series of full-bridge measurements (BrFull()) with increasing settling times. The
pressure transducer is placed in steady-state conditions so changes in measured voltage are attrib-
utable to settling time rather than changes in pressure.
CRBasic Example 2: Measuring Settling Time

'This program example demonstrates the measurement of settling time

'using a single measurement instruction multiple times in succession.
Public PT(20) 'Variable to hold the measurements
DataTable(Settle,True,100)
Sample(20,PT(),IEEE4)
EndTable
BeginProg
Scan(1,Sec,3,0)
BrFull(PT(1),1,mV2500,1,Vx1,1,2500,False,True, 100,60,1.0,0)
BrFull(PT(2),1,mV2500,1,Vx1,1,2500,False,True, 200,60,1.0,0)
BrFull(PT(3),1,mV2500,1,Vx1,1,2500,False,True, 300,60,1.0,0)
BrFull(PT(4),1,mV2500,1,Vx1,1,2500,False,True, 400,60,1.0,0)
BrFull(PT(5),1,mV2500,1,Vx1,1,2500,False,True, 500,60,1.0,0)
BrFull(PT(6),1,mV2500,1,Vx1,1,2500,False,True, 600,60,1.0,0)
BrFull(PT(7),1,mV2500,1,Vx1,1,2500,False,True, 700,60,1.0,0)
BrFull(PT(8),1,mV2500,1,Vx1,1,2500,False,True, 800,60,1.0,0)
BrFull(PT(9),1,mV2500,1,Vx1,1,2500,False,True, 900,60,1.0,0)
BrFull(PT(10),1,mV2500,1,Vx1,1,2500,False,True,1000,60,1.0,0)
BrFull(PT(11),1,mV2500,1,Vx1,1,2500,False,True,1100,60,1.0,0)
BrFull(PT(12),1,mV2500,1,Vx1,1,2500,False,True,1200,60,1.0,0)
BrFull(PT(13),1,mV2500,1,Vx1,1,2500,False,True,1300,60,1.0,0)
BrFull(PT(14),1,mV2500,1,Vx1,1,2500,False,True,1400,60,1.0,0)
BrFull(PT(15),1,mV2500,1,Vx1,1,2500,False,True,1500,60,1.0,0)
BrFull(PT(16),1,mV2500,1,Vx1,1,2500,False,True,1600,60,1.0,0)
BrFull(PT(17),1,mV2500,1,Vx1,1,2500,False,True,1700,60,1.0,0)
BrFull(PT(18),1,mV2500,1,Vx1,1,2500,False,True,1800,60,1.0,0)
BrFull(PT(19),1,mV2500,1,Vx1,1,2500,False,True,1900,60,1.0,0)
BrFull(PT(20),1,mV2500,1,Vx1,1,2500,False,True,2000,60,1.0,0)
CallTable Settle
NextScan
EndProg

9. Tips and troubleshooting 111

The first six measurements are shown in the following table:

Table 9-1: Example data from Measuring Settling Time Program

Record PT(1) PT(2) PT(3) PT(4) PT(5) PT(6)
Timestamp
Number Smp Smp Smp Smp Smp Smp

8/3/2017 23:34 0 0.03638599 0.03901386 0.04022673 0.04042887 0.04103531 0.04123745

8/3/2017 23:34 1 0.03658813 0.03921601 0.04002459 0.04042887 0.04103531 0.0414396

8/3/2017 23:34 2 0.03638599 0.03941815 0.04002459 0.04063102 0.04042887 0.04123745

8/3/2017 23:34 3 0.03658813 0.03941815 0.03982244 0.04042887 0.04103531 0.04103531

8/3/2017 23:34 4 0.03679027 0.03921601 0.04022673 0.04063102 0.04063102 0.04083316

Each trace in the following image contains all twenty PT() mV/V values (left axis) for a given
record number and an average value showing the measurements as percent of final reading
(right axis). The reading has settled to 99.5% of the final value by the fourteenth measurement,
which is contained in variable PT(14). This is suitable accuracy for the application, so a settling
time of 1400 µs is determined to be adequate.

9. Tips and troubleshooting 112

9.10.6 Factors affecting accuracy
Accuracy describes the difference between a measurement and the true value. Many factors
affect accuracy. This topic discusses the effect percent-of-reading, offset, and resolution have on
the accuracy of an analog voltage measurement. Accuracy is defined as follows:

accuracy = percent-of-reading + offset

where percents-of-reading and offsets are displayed in the Analog measurements specifications
(p. 167).

NOTE:
Error discussed in this section and error-related specifications of the datalogger do not
include error introduced by the sensor, or by the transmission of the sensor signal to the data-
logger.

9.10.6.1 Measurement accuracy example

The following example illustrates the effect percent-of-reading and offset have on measurement
accuracy. The effect of offset is usually negligible on large signals.
Example:

l Sensor-signal voltage: approximately 2500 mV

l CRBasic measurement instruction: VoltDiff()
l Programmed input-voltage range (Range) : mV 2 500 (±-100 to 2500 mV)
l Input measurement reversal (RevDiff): True
l Datalogger circuitry temperature: 10° C

Accuracy of the measurement is calculated as follows:

accuracy = percent-of-reading + offset
where
percent-of-reading = 2500 mV • ±0.04%
= ±1 mV
and
offset = ±20 µV
Therefore,
accuracy = ±(1 mV + 20 µV) = ±1.02 mV

9. Tips and troubleshooting 113

9.10.7 Minimizing offset voltages
Voltage offset can be the source of significant error. For example, an offset of 3 μV on a 2500 mV
signal causes an error of only 0.00012%, but the same offset on a 0.25 mV signal causes an error
of 1.2%. Measurement offset voltages are unavoidable, but can be minimized. Offset voltages ori-
ginate with:

l Ground currents (see Minimizing ground potential differences (p. 105).

l Seebeck effect
l Residual voltage from a previous measurement

Remedies include:

l Connecting power grounds to power ground terminals (G).

l Automatic offset compensation for single-ended measurements when MeasOff =
False.
l Using MeasOff = True for better offset compensation.
l Programming longer settling times.

Single-ended measurements are susceptible to voltage drop at the ground terminal caused by
return currents from another device that is powered from the datalogger wiring panel, such as
another manufacturer's communications modem, or a sensor that requires a lot of power. Cur-
rents greater than 5 mA are usually undesirable. The error can be avoided by routing power
grounds from these other devices to a power ground G terminal, rather than using a signal
ground ( ) terminal. Ground currents can be caused by the excitation of resistive-bridge
sensors, but these do not usually cause offset error. These currents typically only flow when a
voltage excitation is applied. Return currents associated with voltage excitation cannot influence
other single-ended measurements because the excitation is usually turned off before the data-
logger moves to the next measurement. However, if the CRBasic program is written in such a way
that an excitation terminal is enabled during an unrelated measurement of a small voltage, an
offset error may occur.
The Seebeck effect results in small thermally induced voltages across junctions of dissimilar
metals as are common in electronic devices. Differential measurements are more immune to
these than are single-ended measurements because of passive voltage cancellation occurring
between matched high and low pairs such as 1H/1L. So, use differential measurements when
measuring critical low-level voltages, especially those below 200 mV, such as are output from
pyranometers and thermocouples.
When analog voltage signals are measured in series by a single measurement instruction, such as
occurs when VoltSE() is programmed with Reps = 2 or more, measurements on sub-
sequent terminals may be affected by an offset, the magnitude of which is a function of the
voltage from the previous measurement. While this offset is usually small and negligible when

9. Tips and troubleshooting 114

measuring large signals, significant error, or NAN, can occur when measuring very small signals.
This effect is caused by dielectric absorption of the integrator capacitor and cannot be overcome
by circuit design. Remedies include the following:

l Programing longer settling times.

l Using an individual instruction for each input terminal, the effect of which is to reset the
integrator circuit prior to filtering.
l Avoiding preceding a very small voltage input with a very large voltage input in a meas-
urement sequence if a single measurement instruction must be used.

9.11 Field calibration

Calibration increases accuracy of a measurement device by adjusting its output, or the meas-
urement of its output, to match independently verified quantities. Adjusting sensor output dir-
ectly is preferred, but not always possible or practical. By adding the FieldCal() or
FieldCalStrain() instruction to a CRBasic program, measurements of a linear sensor can
be adjusted by modifying the programmed multiplier and offset applied to the measurement,
without modifying or recompiling the CRBasic program. For more information, see the CRBasic
help.

9.12 File name and resource errors

The maximum file name size that can be stored, run as a program, or FTP transferred in the data-
logger is 59 characters. If the name + file extension is longer than 59 characters, an Invalid File-
name error is displayed. If several files are stored, each with a long file name, memory allocated
to the root directory can be exceeded before the actual memory of storing files is exceeded.
When this occurs, an Insufficient resources or memory full error is displayed.

9.13 Information tables and settings

(advanced)
Information tables and settings consist of fields, settings, and system information essential to
setup, programming, and debugging of many advanced CR300 series systems. In many cases, the
info tables and settings keyword can be used to pull that field into a running CRBasic program.
There are several locations where this system information and settings are stored or changed:

l Status table: The Status table is an automatically created data table. View the Status table
by connecting the datalogger to your computer (see Connecting the datalogger to a com-
puter (p. 33) for more information) Station Status , then clicking the Status Table tab.

9. Tips and troubleshooting 115

l DataTableInfo table: The DataTableInfo table is automatically created when a program pro-
duces other data tables. View the DataTableInfo table by connecting the datalogger to
your computer (see Connecting the datalogger to a computer (p. 33) for more inform-
ation).
l PC200W and PC400 users, click the Monitor Data tab and add the DataTableInfo to

display it.
l LoggerNet users, select DataTableInfo from the Table Monitor list.

l Device Configuration Utility Settings: Access settings, using Device Configuration Utility.
Clicking on a setting in Device Configuration Utility also provides information about that
setting.
l Terminal Mode: A list of setting field names is also available from the datalogger's terminal
mode (from Device Configuration Utility, click the Terminal tab) using command "F".
l Setting values may be accessed programmatically using Tablename.Fieldname syn-
tax. For example: Variable = Settings.Fieldname.

Communications and processor bandwidth are consumed when generating the Status and other
information tables. If datalogger is very tight on processing time, as may occur in very fast, long,
or complex operations, retrieving these tables repeatedly may cause skipped scans.
Settings that affect memory usage force the datalogger program to recompile, which may cause
loss of data. Before changing settings, it is a good practice to collect your data (see Collecting
data (p. 38) for more information). Examples of settings that force the datalogger program to
recompile:

l IP address
l PakBus encryption key
l IP default gateway
l PakBus/TCP server port
l Subnet mask
l HTTP service port
l PPP interface
l FTP service port
l PPP dial string
l PakBus/TCP service port
l PPP dial response
l PakBus/TCP client connections
l Baud rate change on control ports
l Communications allocation
l Maximum number of TLS server connections

9.13.1 Information tables directories

Use the following links to help you navigate through the Information Tables and Settings system:

l Find the PakBus address of the datalogger (p. 117)

l Communications (p. 117)
l Data (p. 119)
l OS and hardware versions (p. 119)

9. Tips and troubleshooting 116

l Power monitoring (p. 119)
l Security (p. 119)
l Signatures (p. 119)

9.13.1.1 Frequently used

Action Keywords
Find the PakBus address of the datalogger PakBusAddress
See messages pertaining to compilation of the
CompileResults
CRBasic program running in the datalogger
ProgErrors
ProgSignature
Programming Errors SkippedScan
StartUpCode
VarOutOfBound
DataFillDays
Data tables
SkippedRecord
MemoryFree
Memory
MemorySize
Datalogger auto-resets WatchdogErrors
OSDate
Operating system OSSignature
OSVersion
Battery
Power
LithiumBattery

9.13.1.2 Communications
For detailed information on communication protocols, see Communications (p. 64).

General communications
Baudrate
CommsMemAlloc
RS232Power
CommsMemFree

9. Tips and troubleshooting 117

PakBus communications
Beacon
Cen- PakBusAddress PakBusTCPClients
tralRouters PakBusEn- PakBusTCPPass-
IsRouter cryptionKey word
MaxPack- PakBusPort RouteFilters
etSize PakBusRoutes Verify
Neighbors

TCP_IP communications
HTTPPort
DNS
EthernetPower IPAddressEth IPTraceComport
FTPEnabled IPGateway PingEnabled
FTPPassword TelnetEnabled
FTPPort UDPBroadcastFilter
FTPUserName IPMaskEth
HTTPEnabled IPTraceCode

Cellular communications
CellAPN CellPDPAuth
CellRSRP
CellECIO CellPDPPassword
CellRSRQ
CellEnabled CellPDPUserName
CellRSSI
CellInfo CellPwrDuration
CellState
CellKeepAlive CellPwrRepeat
CellStatus
CellKeepAliveTime CellPwrStartTime

RF407-Series radio communications

RadioAvailFreq RadioModel RadioRetries
RadioChanMask RadioModuleVer RadioRSSI
RadioEnable RadioNetID RadioRSSIAddr
RadioHopSeq RadioProtocol RadioStats
RadioMAC RadioPwrMode RadioTxPwr

9. Tips and troubleshooting 118

Wi-Fi communications
WiFiChannel WiFiEapUser WiFiSSID
WiFiConfig WiFiEnable WiFiStatus
WiFiEapMethod WiFiPassword WiFiTxPowerLevel
WiFiEapPassword WiFiPowerMode WiFiNetworks

9.13.1.3 Background calibration

See About background calibration (p. 1) for more information.

CalGain
CalOffset

9.13.1.4 Data
DataFillDays DataTableName
SkippedRecord
DataRecordSize SecsPerRecord

9.13.1.5 OS and hardware versions

OSDate OSVersion
SerialNumber
OSSignature RevBoard

9.13.1.6 Power monitoring

See Power output (p. 8) for more information.

Battery
LithiumBattery

9.13.1.7 Security
See Datalogger security (p. 82) for more information.

PakBusTCPPassword
PakBusEncryptionKey
Security

9.13.1.8 Signatures
OSSignature ProgSignature RunSignature

9. Tips and troubleshooting 119

9.13.2 Information tables and settings descriptions
Information tables and settings consist of fields, settings, and system information essential to
setup, programming, and debugging of many advanced CR300 series systems. There are several
locations where this system information and settings are stored or changed.

l DataTableInfo Table System Information and Settings

l Status Table Information and Settings
l Device Configuration Utility Settings

9.13.2.1 DataTableInfo table system information and settings

The DataTableInfo table is automatically created when a program produces other data tables.
View the DataTableInfo table by connecting the datalogger to your computer (see Connecting
the datalogger to a computer (p. 33) for more information).

l PC200W and PC400 users, click the Monitor Data tab and add the DataTableInfo to display
it.
l LoggerNet users, select DataTableInfo from the Table Monitor list.

Keyword Information and Location

Reports the time required to fill a data table.
DataFillDays l Numeric data type
l Read only
Reports the number of records allocated to a data table.
DataRecordSize l Numeric data type
l Read only
Reports the names of data tables. Array elements are in the order the data
DataTableName tables are declared in the CRBasic program.
l String data type
l Read only
Record number is incremented when any one of the DataTableInfo fields
change, for example SkippedRecord.
RecNum
l Long data type
l Read only

9. Tips and troubleshooting 120

Keyword Information and Location
Reports the data output interval for a data table.
SecsPerRecord l Numeric data type
l Read only
Reports how many times records have been skipped in a data table. Array ele-
ments are in the order that data tables are declared in the CRBasic program.
SkippedRecord Enter 0 to reset.

l Numeric data type

Scan time that a record was generated
TimeStamp l NSEC data type
l Read only

9.13.2.2 Status Table system information and settings

The Status table is an automatically created data table and most of the settings are read only.
View the Status table by connecting the datalogger to your computer (see Connecting the data-
logger to a computer (p. 33) for more information).

Keyword Information and Location

Voltage (Vdc) of the battery powering the system. Updates when viewing the
Status table or via program code.
Battery
l Numeric data type
l Read only
Array of floating-point values reporting calibration gain (mV) for each integ-
ration / range combination.
CalGain
l Numeric data type
l Read only
Displays the offset calibration factor for the different voltage ranges.
CalOffSet l Numeric data type
l Read only

9. Tips and troubleshooting 121

Keyword Information and Location
Memory allocations for communications. Numbers outside of parentheses
reflect current memory allocation. Numbers inside parentheses reflect the low-
CommsMemFree est memory size reached.

l Numeric data type

l Read only
Contains error messages generated at compilation or during runtime.
Updated after compile. Also appended to at run time for run time errors such
CompileResults as variable out of bounds.
l String data type
l Read only
Provides information on the available bytes for the CPU drive.
CPUDriveFree l Numeric data type
l Read only
Serial flash storage bytes free.
DataStorageFree l Numeric data type
l Read only
CR300 series dataloggers with serial numbers 2812 and older have a 5 MB
CPU drive and 10 MB serial flash storage. CR300 series dataloggers with serial
numbers 2813 and newer, and all CR310 dataloggers have an 80 MB CPU drive
DataStorageSize and 30 MB serial flash storage.

l Numeric data type

l Read only
Enter 98765 to start a full-memory reset.
FullMemReset
l Numeric data type
Voltage of the internal lithium battery. Updated at CR300 series power up.
Status of the battery is indicated by either OK, ON POWER UP or FAIL,
LithiumBattery ON POWER UP. For battery information, see Internal battery (p. 86).
l String data type
l Read only

9. Tips and troubleshooting 122

Keyword Information and Location
Maximum time (μs) required to run through processing for the current scan.
Value is reset when the scan exits. Enter 0 to reset. Updated at the conclusion
MaxProcTime of scan processing, prior to waiting for the next scan.

l Numeric data type

Reports the time (μs) needed to make measurements in the current scan. Cal-
culated at compile time. Includes integration and settling time. Assumes all
measurement instructions will run each scan. Updated when a main scan
MeasureTime begins.

l Numeric data type

l Read only
Unallocated final storage memory on the CPU (bytes). All free memory may
not be available for data tables. As memory is allocated and freed, holes of
unallocated memory, which are unusable for final-storage memory, may be
MemoryFree created. Updated after compile completes.

l Numeric data type

l Read only
Total final storage memory size (bytes) in the CR300 series. Updated at star-
tup.
MemorySize
l Numeric data type
l Read only
Release date of the operating system in the format mmddyyyy. Updated at
startup.
OSDate
l String data type
l Read only
Signature of the operating system.
OSSignature l Numeric data type
l Read only
Version of the operating system in the CR300 series. Updated at OS startup.
OSVersion l String data type
l Read only

9. Tips and troubleshooting 123

Keyword Information and Location
Lists routes or router neighbors known to the datalogger at the time the set-
ting was read. Each route is represented by four components separated by
commas and enclosed in parentheses: (port, via neighbor address, pakbus
PakBusRoutes address, response time in ms). Updates when routes are added or deleted.

l String data type

l Read only
Current processor board temperature (°C). Updates when viewing the Status
table or via program code.
PanelTemp
l Float data type
l Read only
Provides information on the configuration settings (input, output, SDI-12,
COM port) for C terminals in numeric order of terminals. Default = Input.
PortConfig Updates when the port configuration changes.

l String data type

l Read only
States of C terminals configured for control. On/high (True) or off/low (False).
Array elements in numeric order of C terminals. Default = False. Updates
PortStatus when state changes.

l Boolean data type

Processing time (μs) of the last scan. Time is measured from the end of the
EndScan instruction (after the measurement event is set) to the beginning of
the EndScan (before the wait for the measurement event begins) for the sub-
ProcessTime sequent scan. Calculated on-the-fly. Updated at the conclusion of scan pro-
cessing, prior to waiting for the next scan.

l Numeric data type

l Read only
Number of compile or runtime errors for the running program. Updated after
compile.
ProgErrors
l Numeric data type
l Read only

9. Tips and troubleshooting 124

Keyword Information and Location
Name of current (running) program; updates at startup.
ProgName l String data type
l Read only
Signature of the running CRBasic program including comments. Does not
change with operating-system changes. Updates after compiling the pro-
ProgSignature gram.
l Numeric data type
l Read only
Record number increments only when the record is requested by support soft-
ware. Range = 0 to 232.
RecNum
l Long data type
l Read only
Electronics board revision in the form xxx.yyy, where xxx = hardware revision
number; yyy = clock chip software revision. Stored in flash memory. Updated
RevBoard at startup.

l String data type

l Read only
Signature of the running binary (compiled) program. Value is independent of
comments or non-functional changes. Often changes with operating-system
RunSignature changes. Updates after compiling and before running the program.

l Numeric data type

l Read only
CR300 series serial number assigned by the factory when the datalogger was
calibrated. Stored in flash memory. Updated at startup.
SerialNumber
l Numeric data type
l Read only
Reports on the serial flash health and provides the number of errors detected
in serial flash. 0 = No errors detected. For detailed information on serial flash,
SerialFlashErrors see Serial flash memory (p. 45).
l Numeric data type
l Read only

9. Tips and troubleshooting 125

Keyword Information and Location
Number of skipped program scans (see Checking station status (p. 94) for
more information) that have occurred while running the CRBasic program.
SkippedScan Does not include scans intentionally skipped as may occur with the use of
ExitScan and Do / Loop instructions. Updated when they occur.

l Numeric data type

Time (date and time) the CRBasic program started. Updates at beginning of
program compile.
StartTime
l NSEC data type
l Read only
Indicates how the running program was compiled. Updated at startup. 65 =
Run on powerup is running and normal powerup occurred. 0 = Normal shut-
StartUpCode down -1 = Restart due to a power loss. -2 = Restart due to watchdog reset.

l Numeric data type

l Read only
Station name stored in flash memory. This is not the same name as that is
entered into your datalogger support software. This station name can be
sampled into a data table, but it is not the name that appears in data file
StationName headers. Updated at startup or when the name is changed. This value is read-
only if the datalogger is currently running a program with CardOut() instruc-
tions.

l String data type

Status of switched, 12 Vdc terminal. True = on. Updates when the state
SW12Volts changes.

l Boolean data type

Scan-time that a record was generated.
TimeStamp l NSEC data type
l Read only

9. Tips and troubleshooting 126

Keyword Information and Location
Number of attempts to write to an array outside of the declared size. The
write does not occur. Indicates a CRBasic program error. If an array is used in a
loop or expression, the pre-compiler and compiler do not check to see if an
VarOutOfBound array is accessed out-of-bounds (i.e., accessing an array with a variable index
such as arr(index) = arr(index–1), where index is a variable). Updated at run
time when the error occurs. Enter 0 to reset.

l Numeric data type

Number of watchdog errors that have occurred while running this program.
Resets automatically when a new program is compiled. Enter 0 to reset.
WatchdogErrors Updated at startup and at occurrence.

l Numeric data type

9.13.2.3 Device Configuration Utility settings

Access settings, using Device Configuration Utility. Clicking on a setting in Device Configuration
Utility also provides information about that setting. See also:

l Cellular Settings
l RF407-Series Radio Settings
l Wi-Fi Settings

9. Tips and troubleshooting 127

Keyword Information and Location
This setting governs the baud rate that the datalogger will use for a
given port in order to support serial communications. For some ports
(COM), this setting also controls whether the port will be enabled for
serial communications.
Some ports (RS-232) support auto-baud synchronization while the other
ports support only fixed baud. With auto-baud synchronization, the
datalogger will attempt to match the baud rate to the rate used by
Baudrate another device based upon the receipt of serial framing errors and
invalid packets.

l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Com Ports Set-

tings | Baud Rate
This setting, in units of seconds, governs the rate at which the data-
logger will broadcast PakBus messages on the associated port in order
to discover any new PakBus neighboring nodes. If this setting value is
set to a value of 0 or 65,535, the datalogger will not broadcast beacon
messages on this port.
This setting will also govern the default verification interval if the value
of the Verify() setting for the associated port is zero. If the value of this
setting is non-zero, and the value of the Verify setting is zero, the effect-
Beacon ive verify interval will be calculated as 2.5 times the value for this setting.
If both the value of this setting and the value of the Verify setting is
zero, the effective verify interval will be 300 seconds (five minutes).

l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Com Ports Set-

tings | Beacon Interval
For dataloggers with integrated CELL modules, see Cellular settings (p.
Cell Settings
145).

9. Tips and troubleshooting 128

Keyword Information and Location
This setting specifies a list of PakBus addresses for routers that are able
to work as Central Routers. By specifying a non-empty list for this set-
ting, the datalogger will be configured as a Branch Router meaning that
it will not be required to keep track of neighbors of any routers except
those in its own branch. Configured in this fashion, the datalogger will
ignore any neighbor lists received from addresses in the central routers
setting and will forward any messages that it receives to the nearest
CentralRouters default router if it does not have the destination address for those mes-
sages in its routing table.

l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced | Cen-

tral Routers
Replaces PakBusNodes. Specifies the amount of memory that the data-
logger allocates for maintaining PakBus routing information and com-
munications buffers. This value represents roughly the maximum
number of PakBus nodes that the datalogger will be able to track in its
routing tables. This setting will also affect the amount of memory that
CommsMemAlloc the datalogger allocates for TCP/IP communications.

l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced |

Communication Allocation
This setting specifies the addresses of up to two domain name servers
that the datalogger can use to resolve domain names to IP addresses.
Note that if DHCP is used to resolve IP information, the addresses
obtained via DHCP will be appended to this list.
DNS l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Ethernet, PPP,

Wi-Fi | DNS Servers

9. Tips and troubleshooting 129

Keyword Information and Location
Reports the IP address, network mask, and default gateway for each of
the datalogger's active network interfaces. If DHCP is used for the inter-
face, this setting will report the value that was configured by the DHCP
server.

EthernetInfo l String data type

l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Ethernet | Net-

work Addresses
This setting specifies how the datalogger controls power to its Ethernet
interface. This setting provides a means of reducing the datalogger
power consumption while Ethernet is not connected. Always on, 1
Minute, or Disable.
EthernetPower
Where to find:

l Settings Editor tab in Device Configuration Utility: Ethernet | Eth-

ernet Power
This setting controls how the datalogger will handle incoming files with
specific extensions from various sources. There can be up to four spe-
cifications. Each specification has three required fields: PakBus Address,
File Name, and Count.
FilesManager l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced |

Files Manager
Set to 1 if to enable FTP service. Default is 0.

l Numeric data type

FTPEnabled Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | FTP Enabled

9. Tips and troubleshooting 130

Keyword Information and Location
Specifies the password that is used to log in to the FTP server.

l String data type

FTPPassword Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | FTP Password
Configures the TCP port on which the FTP service is offered. The default
value is usually sufficient unless a different value needs to be specified
to accommodate port mapping rules in a network address translation
firewall. Default = 21.
FTPPort l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | FTP Service Port
Specifies the user name that is used to log in to the FTP server. An
empty string (the default) inactivates the FTP server.

l String data type

FTPUserName
Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | FTP User Name
Specifies additions to the HTTP header in the web service response. It
can include multiple lines. Set to 1 to enable HTTP (web server) service
or 0 to disable it.

HTTPEnabled l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | HTTP Enabled

9. Tips and troubleshooting 131

Keyword Information and Location
Configures the TCP port on which the HTTP (web server) service is
offered. Generally, the default value is sufficient unless a different value
needs to be specified to accommodate port-mapping rules in a net-
work-address translation firewall. Default = 80.
HTTPPort l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | HTTP Service Port
Set to 1 to enable the HTTPS (secure web server) service.

l Numeric data type

HTTPSEnabled Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | HTTPS Enabled
Configures the TCP port on which the HTTPS (encrypted web server) ser-
vice is offered. Generally, the default value is sufficient unless a different
value needs to be specified to accommodate port mapping rules in a net-
work address translation firewall.
HTTPSPort l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | HTTPS Service Port

9. Tips and troubleshooting 132

Keyword Information and Location
This setting specifies the name of a file to be implicitly included at the
end of the current CRBasic program or can be run as the default pro-
gram. In order to work as an include file, the file referenced by this set-
ting cannot contain a BeginProg() statement or define any variable
names or tables that are defined in the main program file.
This setting must specify both the name of the file to run as well as on
the device (CPU:) on which the file is located. The extension of the file
IncludeFile must also be valid for a datalogger program (.dld, .cr300).
See also File management via powerup.ini (p. 1).

l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced

| Include File Name
Specifies the IP address used by the Ethernet interface. If this value is spe-
cified as "0.0.0.0" (the default), the datalogger will use DHCP to con-
figure the effective value for this setting as well as the Ethernet
Default Gateway and Ethernet Subnet Mask settings. This
setting is the equivalent to the IPAddressEth status table variable.
IPAddressEth
l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Ethernet | IP

Address
Specifies the IP address for the Wi-Fi Interface. If specified as zero, the
address, net mask, and gateway will be configured automatically using
DHCP. This setting is made available only if the WiFi module is in the
CR300 series.
IPAddressWiFi l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | IP

Address

9. Tips and troubleshooting 133

Keyword Information and Location
Specifies the IP address of the network gateway on the same subnet as
the Ethernet interface. If the value of the Ethernet IP Address setting is
set to "0.0.0.0" (the default), the datalogger will configure the effective
value of this setting using DHCP. This setting is the equivalent to the
IPGateway status table variable.
IPGateway
l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Ethernet | Gate-

way
Specifies the address of the IP router to which the datalogger will for-
ward all non-local IP packets for which it has no route. This setting is
made available only if the WiFi module is in the CR300 series.

IPGatewayWiFi l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | IP Gate-

way
Specifies the subnet mask for the Ethernet interface. If the value of the
Ethernet IP Address setting is set to "0.0.0.0" (the default), the data-
logger will configure the effective value of this setting using DHCP.

IPMaskEth l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Ethernet | Sub-

net Mask
Specifies the subnet mask for the WiFi interface. This setting is made
available only if the WiFi module is in the CR300 series.

l String data type

IPMaskEthWiFi
Where to find:

l Settings Editor tab in Device Configuration Utility: WiFi | Subnet

Mask

9. Tips and troubleshooting 134

Keyword Information and Location
IPTrace Discontinued; aliased to IPTraceComport
Controls what type of information is sent on the port specified by
IPTraceComport and via Telnet. Each bit in this integer represents a cer-
tain aspect of tracing that can be turned on or off. Values for particular
bits are described in the Device Configuration Utility. Default = 0, no
messages generated.
IPTraceCode
l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced | IP

Trace Code
Specifies the port (if any) on which TCP/IP trace information is sent.
Information type is controlled by IPTraceCode.
IPTraceComport Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced | IP

Trace COM Port

9. Tips and troubleshooting 135

Keyword Information and Location
This setting controls whether the datalogger is configured as a router or
as a leaf node. If the value of this setting is true, the datalogger will be
configured to act as a PakBus router. That is, it will be able to forward
PakBus packets from one port to another. To perform its routing duties,
a datalogger configured as a router will maintain its own list of neigh-
bors and send this list to other routers in the PakBus network. It will also
obtain and receive neighbor lists from other routers.
If the value of this setting is false, the datalogger will be configured to
act as a leaf node. In this configuration, the datalogger will not be able
IsRouter to forward packets from one port to another and it will not maintain a
list of neighbors. Under this configuration, the datalogger can still com-
municate with other dataloggers and wireless sensors. It cannot, how-
ever, be used as a means of reaching those other dataloggers. The
default value is false.

l Boolean data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced | Is

Router
Specifies the maximum number of bytes per data collection packet.

l Numeric data type

MaxPacketSize Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced | Max

Packet Size

9. Tips and troubleshooting 136

Keyword Information and Location
This setting specifies, for a given port, the explicit list of PakBus node
addresses that the datalogger will accept as neighbors. If the list is
empty (the default value) any node will be accepted as a neighbor. This
setting will not affect the acceptance of a neighbor if that neighbor's
address is greater than 3999.
Neighbors
l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Com Ports Set-

tings | Neighbors Allowed
This setting specifies the PakBus address for this device. Valid values are
in the range 1 to 4094. The value for this setting must be chosen such
that the address of the device will be unique in the scope of the data-
logger network. Duplication of PakBus addresses can lead to failures
and unpredictable behavior in the PakBus network.
When a device has an allowed neighbor list for a port, any device that
PakBusAddress has an address greater than or equal to 4000 will be allowed to connect
to that device regardless of the allowed neighbor list.

l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Datalogger |

PakBus Address
This setting specifies text that will be used to generate the key for
encrypting PakBus messages sent or received by this datalogger. If this
value is specified as an empty string, the datalogger will not use PakBus
encryption. If this value is specified as a non-empty string, however, the
datalogger will not respond to any PakBus message unless that message
PakBusEncryptionKey has been encrypted.
l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Datalogger |

PakBus Encryption Key

9. Tips and troubleshooting 137

Keyword Information and Location
PakBusNodes Discontinued; aliased to CommsMemAlloc
This setting specifies the TCP service port for PakBus communications
with the datalogger. Unless firewall issues exist, this setting probably
does not need to be changed from its default value. Default 6785.

PakBusPort l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | PakBus/TCP Service Port
This setting specifies outgoing PakBus/TCP connections that the data-
logger should maintain. Up to four addresses can be specified.

l String data type

PakBusTCPClients
Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | PakBus/TCP Client Connections
By default, PakBus TCP communications are enabled. To disable PakBus
TCP communications, set the PakBusPort setting to 65535.

l Numeric data type

PakBusTCPEnabled
Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | PakBus/TCP Service Port
This setting specifies a password that, if not empty, will make the data-
logger authenticate any incoming or outgoing PakBus/TCP connection.
This type of authentication is similar to that used by CRAM-MD5.

PakBusTCPPassword l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Datalogger |

PakBus/TCP Password

9. Tips and troubleshooting 138

Keyword Information and Location
Set to one to enable the ICMP ping service.

l Numeric data type

PingEnabled Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | Ping Enabled
Specifies the dial string that would follow the ATD command (#777 for
the Redwing CDMA).
Alternatively, this value can specify a list of AT commands where each
command is separated by a semi-colon (;). When specified in this fash-
ion, the datalogger will transmit the string up to the semicolon, transmit
a carriage return to the modem, and wait for two seconds before pro-
ceeding with the rest of the dial string (or up to the next semicolon). If
multiple semicolons are specified in succession, the datalogger will add
pppDial a delay of one second for each additional semicolon.
If a value of PPP is specified for this setting, will configure the data-
logger to act as a PPP client without any modem dialing. Finally, an
empty string (the default) will configure the datalogger to listen for
incoming PPP connections also without any modem dialing.

l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: PPP | PPP Dial

Specifies the response expected after dialing a modem before a PPP con-
nection can be established.

l String data type

pppDialResponse
Where to find:

l Settings Editor tab in Device Configuration Utility: PPP | PPP Dial

Response

9. Tips and troubleshooting 139

pppInfo l String data type

l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: PPP | PPP Net-

work Addresses
This setting controls which datalogger port PPP service will be con-
figured to use.

l Numeric data type

pppInterface
Where to find:

l Settings Editor tab in Device Configuration Utility: PPP |

PPP Interface
Specifies the IP address that will be used for the PPP interface if that
interface is active (the PPP Interface setting needs to be set to some-
thing other than Inactive).

pppIPAddr l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: PPP | IP

Address
Specifies the password that will be used for PPP connections when the
value of PPP Interface is set to something other than Inactive.

pppPassword l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: PPP | Password

9. Tips and troubleshooting 140

Keyword Information and Location
Specifies the user name that is used to log in to the PPP server.

l String data type

pppUsername Where to find:

l Settings Editor tab in Device Configuration Utility: PPP | User

Name
For dataloggers with integrated RF modules, see RF407-series radio set-
Radio Settings
tings (p. 152).
This setting configures the datalogger to restrict routing or processing of
some PakBus message types so that a "state changing" message can
only be processed or forwarded by this datalogger if the source address
of that message is in one of the source ranges and the destination
address of that message is in the corresponding destination range. If no
ranges are specified (the default), the datalogger will not apply any rout-
ing restrictions. "State changing" message types include set variable,
table reset, file control send file, set settings, and revert settings.

RouteFilters If a message is encoded using PakBus encryption, the router will forward
that message regardless of its content. If, however, the routes filter set-
ting is active in the destination node and the unencrypted message is of
a state changing type, the route filter will be applied by that end node.

l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced |

Route Filters
Controls whether the RS-232 port will remain active even when com-
munications are not taking place.

l Boolean data type

RS232Power
Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced |

RS232 Always On

9. Tips and troubleshooting 141

Keyword Information and Location
An array of three security codes. A value of zero for a given level will
grant access to that level's privileges for any given security code. For
more information, see Datalogger security (p. 82).
Security(1)
Security(2) l Numeric data type
Security(3) Where to find:

l Settings Editor tab in Device Configuration Utility: Datalogger |

Security Level 1, 2, or 3
Discontinued; replaced by/aliased to HTTPEnabled, PingEnabled, Tel-
ServicesEnabled
netEnabled.
TCPClientConnections
Discontinued; replaced by / aliased to PakBusTCPClients.

TCPPort Discontinued; replaced by / aliased to PakBusPort.

Enables (1) or disables (0) the Telnet service.

l Numeric data type

TelnetEnabled Where to find:

l Settings Editor tab in Device Configuration Utility: Network Ser-

vices | Telnet Enabled

9. Tips and troubleshooting 142

Keyword Information and Location
This setting controls the number of concurrent TLS (secure or encrypted)
client socket connections that the datalogger will be capable of hand-
ling at any given time. This will affect FTPS and HTTPS services. This
count will be increased by the number of DNP() instructions in the data-
logger's program.
This setting will control the amount of RAM that the datalogger will use
for TLS connections. For every connection, approximately 20KBytes of
TLSConnections RAM will be required. This will affect the amount of memory available
for program and data storage. Changing this setting will force the data-
logger to recompile its program so that it can reallocate memory

l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: TLS | Max TLS

Server Connections
This setting specifies the password that will be used to decrypt the TLS
Private Key setting.

l String data type

TLSPassword
Where to find:

l Settings Editor tab in Device Configuration Utility: TLS | Private

Key Password (setup available over USB or RS-232 only)
Reports the current status of the datalogger TLS network stack.

l String data type

TLSStatus l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: TLS | TLS Status

9. Tips and troubleshooting 143

Keyword Information and Location
Set to one if all broadcast IP packets should be filtered from IP inter-
faces. Do not set this if you use the IP discovery feature of the device
configuration utility or of LoggerLink. If this is set, the datalogger will
fail to respond to the broadcast requests.
Default = 0.
UDPBroadcastFilter
l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced | IP

Broadcast Filtered
Specifies the offset, in seconds, of the datalogger's clock from Coordin-
ated Universal Time (UTC, or GMT). For example, if the clock is set to
Mountain Standard Time in the U.S. (-7 Hours offset from UTC) then this
setting should be -25200 (-7*3600). This setting is used by the
NTP Server setting as well as EmailSend() and HTTP(), which require
Universal Time in their headers. This setting will also be adjusted by the
Daylight Savings functions if they adjust the clock.
UTCOffset
If a value of -1 is supplied for this setting, no UTC offset will be applied.

l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Advanced | UTC

Offset

9. Tips and troubleshooting 144

Keyword Information and Location
This setting specifies the interval, in units of seconds, that will be repor-
ted as the link verification interval in the PakBus hello transaction mes-
sages. It will indirectly govern the rate at which the datalogger will
attempt to start a hello transaction with a neighbor if no other com-
munications have taken place within the interval.
Verify
l Numeric data type

Where to find:

l Settings Editor tab in Device Configuration Utility: ComPorts Set-

tings | Verify Interval
For dataloggers with integrated WIFI modules, see Wi-Fi settings (p.
Wi-Fi Settings
157).

Cellular settings
Access cellular settings, using Device Configuration Utility. Clicking on a setting in Device Con-
figuration Utility also provides information about that setting. These settings are available for
dataloggers with integrated CELL modules.

Keyword Information and location

Specifies the APN, and is required. The APN is the gateway between the cell
network and the internet. APN must be obtained from your cellular network
provider.
CellAPN l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | APN

Global control for cell modem. This overrides the power schedule setting
and CRBasic IPNetpower instruction. 0 Disabled, 1 or <>0 Enabled.

l Boolean data type

CellEnabled
Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | Cell

Modem Enable

9. Tips and troubleshooting 145

Keyword Information and location
Cellular diagnostic information. Reports the PPP state, IMEI, IMSI, and ICCID
for the datalogger.

l String data type

CellInfo l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | Cell Dia-

gnostic Info
URL for ping to verify network connectivity. This is only sent if there has
been no network activity within the CellKeepAliveTime setting. If there is no
ping response, the network connection is re-established. To disable keep
alive pings, leave this setting blank.
CellKeepAlive l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | Ping Keep

Alive URL
Ping keep alive timeout (in seconds).

l Long data type

CellKeepAliveTime Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | Ping Keep

Alive Timeout Value
Specifies the PDP authentication type (if used). PDP Authentication is only
used if there is a PDP Username and Password AND the PAP or CHAP
authentication is required. If a PDP Authentication Type is required, it will
be provided by your cellular provider with the APN. 0 None, 1 PAP, 2 CHAP

CellPDPAuth l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular |

PDP Authentication Type, PPP Authentication User Name,
PPP Authentication Password

9. Tips and troubleshooting 146

Keyword Information and location
Specifies the PDP password used for authentication. Often there is no pass-
word, and this field can be left blank. If a password is required, it will be
provided by your cellular provider with the APN.

CellPDPPassword l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | PDP Cell

Authentication Password
Specifies the username used for PDP authentication. Often there is no user-
name, and this field can be left blank. If a Username is required, it will be
provided by your cellular provider with the APN.

CellPDPUserName l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | PDP Cell

Authentication Username

9. Tips and troubleshooting 147

Keyword Information and location
Specifies the interval, in minutes, over which the datalogger will power its
cellular interface. This can be done to save on battery life or cellular charges.
This is adjusted using three components:

l Start (Power-On) Time: Specifies the time of day in terms of hours and
minutes in which the datalogger will first enable the cellular interface.
If left at the default value of Always On, the datalogger will power the
cellular interface at all times.
l On Duration: Specifies the interval, in minutes, to power the data-
logger cellular interface for the first time of any day as well as for any
repeat cycles (if applicable).
CellPwrDuration l Repeat Cycle: Specifies the interval after the first time that the data-
logger powers on its cellular interface, that the datalogger will power
its cellular interface at subsequent times throughout the day.

For example, setting a Start Time of 08:00, with an On Duration of 15

minutes, and a Repeat Cycle of Every Hour, will result in the cellular module
being powered on at 8:00AM for 15 minutes every hour until midnight.

l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | On dur-

ation
Specifies the interval in minutes to power on the cellular interface following
the first time of the day that the datalogger powers on its cellular interface.
For example usage, see CellPwrDuration.

CellPwrRepeat l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | Repeat

cycle

9. Tips and troubleshooting 148

Keyword Information and location
Specifies time of day in minutes when the datalogger will first enable the cel-
lular interface. Examples:

l 15 = 00:15 ’15 minutes after midnight

l 180 = 03:00 ‘3:00 am
l 1380 = 23:00 ’11:00 pm
l 1440 = Always On
CellPwrStartTime
For example usage, see CellPwrDuration.

l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | Start

(power-on) time
Specifies the signal quality of the modem. For 3G, this is ECIO (Energy to
Interference Ratio). For 4G, this is RSRQ (Reference Signal Received Quality).
Updated when queried by your datalogger support software or a program.
Ranges expected for Signal Quality for 3G/4G:
Excellent: 0 to -6 (3G), >-9 (4G)
Good: -7 to -10 (3G), -9 to -12 (4G)
CellRSRQ
Fair to Poor: -11 to -20 (3G), -13 or less (4G)
CellECIO
l Float data type
l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | Signal

Quality

9. Tips and troubleshooting 149

Keyword Information and location
Specifies the signal strength of the modem in -dBm. For 3G, this is RSSI
(Received Signal Strength Indicator). For 4G, this is RSRP (Reference Signal
Received Power). Updated when queried by your datalogger support soft-
ware or a program. Ranges expected for Signal Strength for 3G/4G:
Excellent: -70dBm or less (3G), -90dBm or less (4G)
Good: -70dBm to -85dBm (3G), -90dBm to -105dBm (4G)
CellRSSI Fair: -86dBm to -100dBm (3G), -106dBm to -115dBm (4G)
CellRSRP Poor: >-100dBm (3G), >-115dBm (4G)

l Long data type

l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | Signal

Strength

9. Tips and troubleshooting 150

Keyword Information and location
Specifies the current communications state with the cell modem and the net-
work. The following states are available:

l Power off
l Powering up
l Powered up
l SIM authorized
l Setting baud rate
l Waiting for baud rate
l Baud rate set
l Baud rate failure
l Power off. Waiting for retry
l Powered up. SIM auth failure
l Querying modem
l Waiting for network registration
l Configuring modem
l Dialing
l Dialing (retry)
CellState
l Dialed
l PPP negotiation
l Network ready
l PPP closing
l PPP paused
l PPP dropped
l Terminal AT command mode
l Firmware update mode
l Shutting down

l String data type

l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | Cellular

State

9. Tips and troubleshooting 151

Keyword Information and location
Cellular network/state information. Reports the cellular IP address, default
gateway, DNS, network state, cell carrier, connection type, phone number
associated with the SIM card, and data usage.

l String data type

CellStatus l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Cellular | Dia-

gnostic Info

RF407-series radio settings

Access RF407-series radio settings, using Device Configuration Utility. Clicking on a setting in
Device Configuration Utility also provides information about that setting. These settings are avail-
able for RF407-series dataloggers.

Keyword Information and location

Displays the bitfield of the frequencies that are available in the module’s
region of operation.

l String data type

RadioAvailFreq l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Available Fre-

quencies
The channel mask allows channels to be selectively enabled or disabled. This
allows you to avoid using frequencies that experience unacceptable levels of
RF interference.

RadioChanMask l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Radio Chan-

nel Mask

9. Tips and troubleshooting 152

Keyword Information and location
Global control for the internal radio module.
RadioEnable Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Radio Enable

Specifies the radio channel hop sequence. This setting must match in all
radios in the same RF network. This setting can also be used to prevent radios
in one RF network from listening to transmissions of another.

RadioHopSeq l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | RF Hop

Sequence
Radio serial number.

l String data type

l Read only
RadioMAC
Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Radio

MAC Address
Reports the model of the internal radio module.

l String data type

RadioModel l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Radio Model

Radio hardware version.

l Long data type

l Read only
RadioModuleVer
Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Radio Hard-

ware Version

9. Tips and troubleshooting 153

Keyword Information and location
The RadioNetID specifies the identifier for the RF network. The radio will
ignore any packets received that do not use this network identifier - therefore,
all radios in the network must use the same value. Valid entries are between 0
and 32767.
RadioNetID
l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Network ID

Specifies the protocol mode that will be used by the radio.
Transparent: Provides a transparent link with no interpretation of the data
packet. This mode is most commonly used with array based dataloggers, and
it must be used when communicating with other transparent devices such as
the RF407/412/422, CR300-RF407/CR300-RF412/CR300-RF422, and CR6-
RF407. This mode is also used for non PakBus protocols like Modbus. When
used this way, Retry Level must be set to None.
PakBus Aware: This is the most commonly used protocol setting for PakBus
networks. The radio will automatically inherit an RF identifier equal to the
RadioProtocol
PakBus address of the device to which it is serially attached. In this mode, the
radio will be capable of performing RF level retries and acknowledgments and
provide a more reliable link than Transparent mode used for broadcast mes-
saging. You do not need to manually set a unique RF Radio Address or a
unique PakBus Address. This device will not appear in PakBus Graph.

l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Protocol

9. Tips and troubleshooting 154

Keyword Information and location
This setting governs the duty cycle that the radio will use for powering its
receiver circuit. As such, it governs the amortized current drain for the radio.
This setting should be set the same for all radios in the same network. Power
Modes include:
Always On: The radio is always on and does not transmit a wakeup header.
.5 Second: The radio wakes every 0.5 seconds for a 100 msec interval to listen
for RF activity. It will transmit a 700 msec wakeup header with the first trans-
mission following a period of RF inactivity.
1 Second: The radio wakes every 1 second for a 100 msec interval to listen for
RadioPwrMode
RF activity. It will transmit a 1200 msec wakeup header with the first trans-
mission following a period of RF inactivity.
4 Second: The radio wakes every 4 seconds for a 100 msec interval to listen for
RF activity. It will transmit a 4200 msec wakeup header with the first trans-
mission following a period of RF inactivity.

l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Power Mode

Specifies the level to which the radio should retry to deliver an unac-
knowledged RF packet transmission. When an RF packet fails to be acknow-
ledged by the destination, the radio will resend the packet again. A receiving
radio responds to the sending radio with an ACK packet for every radio
packet that it receives that is addressed to it and has a valid CRC. Retry levels
and counts:

l None - 0
l Low - 2
RadioRetries l Medium - 4
l High - 6

Set Retry Level to None when the Protocol setting is set to Transparent for the
purpose of communicating with other RF407 series radios.

l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Retry Level

9. Tips and troubleshooting 155

Keyword Information and location
Indicates the signal strength of the last packet received by this radio.
The units of the RSSI are dBm; -40 is a stronger signal than -70. Because the
received signal strength can vary due to multipath, interference, or other envir-
onmental effects; this setting may not give a true indication of com-
munication performance or range. However, received signal strength can be
useful for activities such as:

l Determining the optimal direction to aim a Yagi antenna.

RadioRSSI l Determining the effects of antenna height and location.
l Trying alternate (reflective) paths.
l Seeing the effect of vegetation and weather over time.

l Long data type

l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | RFSignalLevel

(first number)
Indicates the PakBus address of the RadioRSSI signal radio.

l Long data type

l Read only
RadioRSSIAddr
Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | RFSignalLevel

(second number)

9. Tips and troubleshooting 156

Keyword Information and location
Provides the performance statistics for the integrated radio for the datalogger.
The datalogger will maintain a radio routing table for each PakBus neighbor
accessed using the integrated radio and this setting is generated from that
table. The fields reported for this setting are as follows:

l PakBus Address: Specifies the PakBus address of the neighbor reached

through an integrated radio link.
l Sent Packets: Reports the number of radio packets that have been trans-
mitted to the PakBus neighbor using the integrated radio link.
l Received Packets: Reports the number of radio packets that have been
received from the PakBus neighbor using the integrated radio link.
RadioStats
l Packet Retries: Reports the number of radio packet transmissions to the
PakBus neighbor using the integrated radio link that had to be retrans-
mitted by the radio module.
l Packet Failures: Reports the number of radio packet transmissions to
the PakBus neighbor that were never acknowledged.

l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio |

Radio Performance Statistics
Specifies the power level at which the RF module transmits.
Levels are approximate. It is very important that the TX power level selected
and the gain of the attached antenna do not exceed the maximum allowed
ERP permitted by local laws. These rules vary from region to region.
RadioTxPwr
l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Radio | Radio TX

Power Level

Wi-Fi settings
Access Wi-Fi settings, using Device Configuration Utility. Clicking on a setting in Device Con-
figuration Utility also provides information about that setting. These settings are available for
dataloggers with integrated WIFI modules.

9. Tips and troubleshooting 157

Keyword Information and location
This setting is only applicable when the device is configured to create a net-
work (WiFiConfig). It then specifies in which channel the network should be
created. If Auto is selected, the device will select to operate on a channel
that has minimal interference from other networks detected in the area.
When manually selecting a channel, it should be noted that two Wi-Fi net-
works operating on the same channel will interfere with each other and will
have to compete for bandwidth. The center frequencies of adjacent channels
WiFiChannel are 5 MHz apart and the bandwidth of each channel is 20 MHz which means
that adjacent channels overlap. To completely avoid interference there must
be a spacing of at least 5 channels between each Wi-Fi network. It is there-
fore recommended to use channels 1, 6, and 11.

l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | Channel

Configure the WiFi network. Disable, join a network, or create a network.

l Long data type

WiFiConfig Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | Con-

figuration
The EAP Method must be chosen to match the EAP method being used by
the Enterprise Security network. The inner EAP Methods supported are
MSCHAPv2, MSCHAP, CHAP, and PAP.
WiFiEapMethod l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | EAP Method

9. Tips and troubleshooting 158

Keyword Information and location
If joining an Enterprise Security-enabled network then this is where the pass-
word is entered.

l String data type

WiFiEapPassword
Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi |

EAP Password
If joining an Enterprise Security-enabled network then this is where the user
name is entered.

WiFiEapUser l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | EAP User

Set to enable or disable the WiFi service. By default, WiFi is enabled. To dis-
able, set the Configuration option to Disable. 0 Disabled, 1 or <>0 Enabled.

l Boolean data type

WiFiEnable
Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | Con-

figuration

9. Tips and troubleshooting 159

Keyword Information and location
If joining a WPA or WPA2 security enabled network then this is where the
passphrase is entered. If joining a WEP security enabled network then this is
where the WEP key is entered.
If creating a network and a password is supplied, the network will be created
using WPA2 encryption. The password must be at least 8 characters. If a pass-
word is not supplied, an open (unencrypted) network will be created.
When joining a network the device supports 64-bit WEP and 128-bit WEP.
WiFiPassword
For 64-bit WEP enter a 40 bit key in the form of 5 ASCII characters or 10 hexa-
decimal digits (0-9, A-F). For 128-bit WEP enter a 104 bit key in the form of
13 ASCII characters or 26 hexadecimal digits (0-9, A-F).

l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | Password

This setting controls the power saving mode of the device. Regardless of the
Power Mode setting, the device enables power-save mode when com-
munications are not active. Power Mode determines how the device acts
when communications are ongoing. This setting only applies when the
WiFiPowerMode device is configured to Join a Network using the WiFiConfig option.
l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | Power Mode

9. Tips and troubleshooting 160

Keyword Information and location
The Network Name (SSID) is the name that identifies a wireless network (31
character maximum). The SSID differentiates one wireless network from
another, so all devices attempting to connect to the same network must use
the same SSID. If the device is configured to 'Join a Network', then enter the
SSID of the network to join here. If no SSID is specified, the device will join
the first open network it finds. If the device is configured to Create a Net-
WiFiSSID work using the WiFiConfig option, then the SSID entered here will be the
SSID of the network created.

l String data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | Network

Name (SSID)
Specifies the current status of the Wi-fi module.

l String data type

WiFiStatus l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | Wi-Fi Status

9. Tips and troubleshooting 161

Keyword Information and location
This fixes the transmit power level of the Wi-fi module. This value can be set
as follows: Low (7 +/- 1 dBm), Medium (10 +/- 1 dBm), High (15 +/- 2 dBm).
The value of this setting does not affect power consumption.

WiFiTxPowerLevel l Long data type

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | Tx Power

Level
Lists the networks available in the area. Information listed for each network is
shown as {SSID, RSSI / Signal Strength, Channel, Security}. Sometimes areas
are covered by multiple access points configured with the same network
name (SSID). In that case multiple unique access points possessing the same
network name (SSID) may be listed here.
WiFiNetworks l String data type
l Read only

Where to find:

l Settings Editor tab in Device Configuration Utility: Wi-Fi | Wireless Net-

works in Area

9. Tips and troubleshooting 162

10. Specifications
Electrical specifications are valid over a -40 to +70 °C, non-condensing environment, unless oth-
erwise specified. Recalibration is recommended every three years. Critical specifications and sys-
tem configuration should be confirmed with Campbell Scientific before purchase.

10.1 System specifications 163

10.2 Physical specifications 164
10.3 Power requirements 164
10.4 Power output specifications 166
10.5 Analog measurements specifications 167
10.6 Pulse measurement specifications 170
10.7 Digital input/output specifications 171
10.8 Communications specifications 172
10.9 Standards compliance specifications 177

Specifications

10.1 System specifications

Processor: ARM Cortex M4 running at 144 MHz
Memory:

l CPU Drive: 80 MB serial flash

l Data Storage: 30 MB serial flash
l Operating System: 2 MB flash
l Settings, Calibration, TLS Certificates and Key, System Information: 3 MB serial flash
l Background Tasks, Buffers, System Memory, Program Memory, Table Memory, Program
Variables: 756 KB RAM

NOTE:
CR300 series dataloggers with serial numbers 2812 and older have a 5 MB CPU drive and 10
MB serial flash storage. CR300 series dataloggers with serial numbers 2813 and newer, and all
CR310 dataloggers have an 80 MB CPU drive and 30 MB serial flash storage.

10. Specifications 163

Program Execution: 100 ms to 1 day
Real-Time Clock:

l Battery backed while external power is disconnected

l Resolution: 1 ms
l Accuracy: ±1 minute per month

Wiring Panel Temperature: Measured using a thermistor, located on the processor board.

NOTE:
The measurement from the PanelTemp() instruction does not accurately reflect the tem-
perature of the wiring panel, since it measures the temperature of the main processing board.
Therefore, if the datalogger processor, or charge (CHG) input are active, the PanelTemp()
measurement will be warmer than ambient. This should be taken into consideration if this
measurement is used as a reference temperature for other measurements such as ther-
mocouples.

10.2 Physical specifications

Dimensions (additional clearance required for cables and wires):

l CR300: 13.97 x 7.62 x 4.56 cm (5.5 x 3.0 x 1.8 in). For CAD files, see CR300 Images and CAD
2D Drawings.
l CR310: 16.26 x 7.62 x 5.68 cm (6.4 x 3.0 x 2.2 in). For CAD files, see CR310 Images and CAD
2D Drawings.

Weight/Mass

l CR300: 242 g (0.53 lb)

l CR310: 288 g (0.64 lb)
l CR300-WIFI/RF407/RF412/RF422: 249.5 g (0.55 lb)
l CR300-WIFI/RF407/RF412/RF422: 306 g (0.68 lb)

Case Material: Powder-coated aluminum

10.3 Power requirements

Power specifications for a communications option are shown within the specifications section for
that option.
Protection: Power inputs are protected against surge, over-voltage, over-current, and reverse
power.

10. Specifications 164

Charger Input (CHG+ and CHG- terminals):

l 16 – 32 Vdc
l Current limited to 0.9 A maximum
l Power converter or solar panel input

External Batteries (BAT+ and BAT- terminals):

l 10 – 18 Vdc input
l 12 Vdc, lead-acid 7 Ah battery, typical

Internal Lithium Battery (see Internal battery (p. 86) for more information): 3 V coin cell CR2016
for battery-backed clock. 6-year life with no external power source.
Average Current Drain (assumes 12 Vdc on BAT terminals — add 2 mA if using CHG terminals):

l Idle: 1.5 mA
l Active 1 Hz Scan with One Analog Measurement: 5 mA
l Serial (RS-232): Active + 25 mA
l Active (Processor Always On): 23 mA
l Ethernet Power Requirements (CR310 Only):
o Ethernet Idle: 32 mA
o Ethernet Link: Active + 51 mA

USB Power: Functions that will be active with USB 5 Vdc include sending programs, adjusting
datalogger settings, and making some measurements. If USB is the only power source, then the
VX1 – VX2 range is reduced to 150 to 2500 mV, the SW12V terminal will not be operational,
voltage output for the control terminals (C1, C2) is limited to 4.75 V, and current output for the
control terminals (C1, C2) is limited to 8 mA.
Wi-Fi Additional Current Contribution at 12 Vdc:

l Client mode communicating: 70 mA typical

l Client mode idle: 7 mA typical
l Access point mode communicating: 65 mA
l Access point mode idle: 62 mA typical
l Sleep (sleep forced with a setting or CRBasic program): <0.1 mA

RF Average Additional Current Contribution at 12 Vdc

l Transmit
o RF407, RF412, and RF427: < 80 mA
o RF422: 20 mA

10. Specifications 165

l Idle On
o RF407, RF412, and RF427:12 mA
o RF422: 9.5 mA

l Idle 0.5 sec Power Mode

o RF407, RF412, and RF427:4 mA
o RF422: 3.5 mA

l Idle 1 sec Power Mode

o RF407, RF412, and RF427:3 mA
o RF422: 2.5 mA

l Idle 4 sec Power Mode

o RF407, RF412, and RF427:1.5 mA
o RF422: 1.5 mA

10.4 Power output specifications

VX: Two independently configurable voltage terminals (VX1-VX2). When providing voltage excit-
ation, a single 12-bit DAC shared by all VX outputs produces a user-specified voltage during
measurement only. In this case, these terminals are regularly used with resistive-bridge meas-
urements (see Resistance measurements (p. 51) for more information). VX terminals can also be
used to supply a switched, regulated 5 Vdc power source to power digital sensors and toggle con-
trol lines.

NOTE:
CR300 series dataloggers are not capable of applying reverse excitation. Set the RevEx para-
meter of all bridge measurement instructions to False.

l Range: 150 to 5000 mV

l Resolution: 4.5 mV
l Maximum Source or Sink Current: 50 mA total, concurrently or independently.

10. Specifications 166

o 830 mA @ 70 °C

l SE1-SE4, P_SW: 3.3 V Logic Level Drive Capacity = 100 µA at 3.0 V

l C1-C2: 3.3 V Logic Level Drive Capacity = 10 mA at 3.5 V

10.5 Analog measurements specifications

6 single-ended (SE) or 3 differential (DIFF) terminals individually configurable for voltage, ther-
mocouple, current loop, ratiometric, and period average measurements, using a 24-bit ADC. One
channel at a time is measured.

10.5.1 Voltage measurements

Terminals:
Input Resistance:

l 5 GΩ typical (fN1 = 50/60 Hz)

l 300 MΩ typical (fN1 = 4000 Hz)

Input Limits: -100 to +2500 mV

Sustained Input Voltage without Damage:

l SE 1-2: –6 V, +9 V
l SE 3-6: ±17 V

Dc Common Mode Rejection:

l >120 dB with input reversal

l ≥90 dB without input reversal

Normal Mode Rejection:

l >71 dB at 50 Hz
l >74 dB at 60 Hz

Input Current @ 25 °C: ± nA typical

l ±.08 nA typical (fN1 = 50/60 Hz)

l ±13 nA typical (fN1 = 4000 Hz)

10. Specifications 167

Filter First Notch Frequency (fN1) Range: 50/60, 400,4000 Hz (user specified)
Analog Range and Resolution:

Differential with Single-Ended and Differential

Input Reversal without Input Reversal
Notch Frequency (f N1) Range1
RMS (µV) Bits2 RMS (µV) Bits2
(Hz) (mV)
–100 to
+2500 23 16.8 33 16.3
4000
–34 to 3.0 14.5 4.2 14.0
+34
–100 to
+2500 3.8 19.4 5.4 18.9
400
–34 to 0.58 16.8 0.82 16.3
+34
–100 to
+2500 1.6 20.6 2.3 20.1
50/603
–34 to 0.23 18.2 0.33 17.7
+34
1 Range overhead of ~10% on all ranges guarantees that full-scale values will not cause over range
2 Typical effective resolution (ER) in bits; computed from ratio of full-scale range to RMS resolution.
3 50/60 corresponds to rejection of 50 and 60 Hz ac power mains noise.

Accuracy (does not include sensor or measurement noise):

l 0 to 40 °C: ±(0.04% of measurement + offset)

l –40 to 70 °C: ±(0.1% of measurement+ offset)

Voltage Measurement Accuracy Offsets:

Range (mV) Typical Offset (µV RMS)

Differential Differential
Single-Ended
with Input Reversal without Input Reversal
–100 to +2500 ±20 ±40 ±60
–34 to +34 ±6 ±14 ±20

Measurement Settling Time: 20 µs to 600 ms; 500 µs default

10. Specifications 168

Multiplexed Measurement Time:
These are not maximum speeds. Multiplexed denotes circuitry inside the datalogger that switches
signals into the ADC.
Measurement time = (multiplexed measurement time + settling time) • reps +0.8 ms

Differential Single-Ended or Differential

with Input Reversal without Input Reversal
Example fN11 (Hz) Time2 (ms) Time2 (ms)
4000 2.9 1.4
400 14.6 7.3
50/60 103 51.5
1 Notch frequency (1/integration time).

2 Default settling time of 500 µs used.

10.5.2 Resistance measurements specifications

The datalogger makes ratiometric-resistance measurements for four- and six-wire full-bridge cir-
cuits and two-, three-, and four-wire half-bridge circuits using voltage excitation. Typically, at
least one terminal is configured for excitation output. Multiple sensors may be able to use a com-
mon excitation terminal.
Accuracy: Assumes input reversal for differential measurements RevDiff. Does not include
bridge resistor errors or sensor and measurement noise.
Ratiometric accuracy, rather than absolute accuracy, determines overall measurement accuracy.
Offset is the same as specified for analog voltage measurements.

l 0 to 40 °C: ±(0.05% of voltage measurement + offset)

l –40 to 70 °C: ±(0.06% of voltage measurement + offset)

10.5.3 Period-averaging measurement specifications

Use PeriodAvg() to measure the period (in microseconds) or the frequency (in Hz) of a signal
on a single-ended channel.
Terminals: SE terminals 1-4
Accuracy: ±(0.01% of measurement + resolution), where resolution is 0.13 µs divided by the num-
ber of cycles to be measured

10. Specifications 169

Voltage Range: 0 to 3.3 V
Minimum Pulse Width: 2.5 µs
Voltage Threshold: Counts cycles on transition from <0.9 Vdc to >2.1 Vdc
See also Period-averaging measurements (p. 57).

10.5.4 Current-loop measurement specifications

Two analog inputs terminals may be configured as independent, non-isolated 0-20 mA or 4-to-
20 mA current-loop inputs. One channel at a time is measured. Current is measured using a 24-
bit ADC.
Terminals: SE terminals 1-2
Range: 0 to 25 mA
Accuracy

l 0 to 40 °C: ±0.14% of reading

l –40 to 70 °C: ±0.26% of reading

10.6 Pulse measurement specifications

Terminals are individually configurable for switch closure, high-frequency pulse, or low-level AC
measurements.
Maximum Input Voltage: ±20 Vdc

10.6.1 Switch-closure input

Terminals:

l P_SW
l C1-C2 (Requires an external 100 kΩ resistor connected from the terminal to BAT+.)

Minimum Switch Closed Time: 3 ms

Minimum Switch Open Time: 3 ms
Maximum Bounce Time: 1 ms open without being counted
Maximum Input Frequency: 150 Hz
Maximum Input Voltage: ±17 Vdc

10. Specifications 170

10.6.2 High-frequency input
Terminals:

l SE terminals 1-4
l P_LL
l P_SW
l C1-C2

Maximum Input Frequency:

l SE 1-4: 35 kHz
l P_LL: 20 kHz
l P_SW: 35 kHz
l C1-C2: 3 kHz

10.6.3 Low-level ac input

Terminal: P_LL
Dc-offset Rejection: Internal ac coupling eliminates dc-offset voltages up to ±0.05 Vdc
Input Hysteresis: 12 mV at 1 Hz
Low-Level Ac Pulse Input Ranges:

l Sine Wave Input 20 mv RMS, Input Frequency Range 1.0 to 20 Hz

l Sine Wave Input 200 mv RMS, Input Frequency Range 0.5 to 200 Hz
l Sine Wave Input 2000 mv RMS, Input Frequency Range 0.3 to 10,000 Hz
l Sine Wave Input 5000 mv RMS, Input Frequency Range 0.3 to 20,000 Hz

10.6.4 Quadrature input

Terminals: SE1 and SE2 or C1 and C2 can be configured as digital terminal pairs to monitor the
two sensing channels of an encoder.
Maximum Frequency: 2.5 kHz
See Digital input/output specifications (p. 171) and Pulse measurements (p. 58) for additional
information.

10.7 Digital input/output specifications

Up to seven terminals may be configured for digital input or output (I/O).

10. Specifications 171

Terminals:

l SE terminals 1-4
l P_SW
l C1-C2

Digital I/O Voltage Levels:

Terminal High State Low State Current Source Maximum Input Voltage

C1 5.0 V output
0V 10 mA at 3.5 V –10 V, +15 V
C2 3.3V input
SE1
3.3 V 0V 100 µA at 3.0 V –6 V, +9 V
SE2
SE3
SE4 3.3 V 0V 100 µA at 3.0 V ±17 V
P_SW

See also Power output (p. 8) and Pulse measurement specifications (p. 170).

10.7.1 Pulse-width modulation specifications

Terminals: SE terminals 1-4
Period Maximum: 2047 ms
Resolution

l 0 – 5 ms: 83.33 ns or 12 MHz

l 5 – 325 ms: 5.00 µs or 200 kHz
l > 325 ms: 31.25 µs or 32 kHz

See Digital input/output specifications (p. 171) for more information.

10.8 Communications specifications

A datalogger is normally part of a two-way conversation started by a computer. In applications
with some types of interfaces, the datalogger can also initiate the call (callback) when needed. In
satellite applications, the datalogger may simply send bursts of data at programmed times
without waiting for a response.
Ethernet Port (CR310 Only): RJ45/ jack, 10/100Base Mbps, full and half duplex, Auto-MDIX, mag-
netic isolation, and TVS surge protection. See also Ethernet communications (p. 17).

10. Specifications 172

Internet Protocols: Ethernet, PPP, CS I/O IP, RNDIS, ICMP/Ping, Auto-IP(APIPA), IPv4, IPv6, UDP,
TCP, TLS, DNS, DHCP, SLAAC, NTP, Telnet, HTTP(S), FTP(S), SMTP/TLS, POP3/TLS
Additional Protocols: PakBus, PakBus Encryption, SDM, SDI-12, Modbus RTU / ASCII / TCP,
DNP3, NMEA 0183, I2C, SPI, custom user definable over serial, UDP
Data File Formats: TOA5, TOB1, TOB3, CSV, XML, JSON, binary, encrypted
USB: Micro-B device for computer connectivity
RS-232: Female RS-232, 9-pin interface, 1200 to 115.2 kbps
SDI-12 (C1, C2): Two independent SDI-12 compliant terminals are individually configured and
meet SDI-12 Standard v 1.4.

10.8.1 Wi-Fi option specifications

WLAN (Wi-Fi) (CR300-WIFI only)
Maximum Possible Over-the-Air Data Rates: <11 Mbps over 802.11b, <54 Mbps over 802.11g, <72
Mbps over 802.11n
Operating Frequency: 2.4 GHz, 20 MHz bandwidth
Antenna Connector: Reverse Polarity SMA (RPSMA)
Antenna (shipped with datalogger): Unity gain (0 dBd), 1/2 wave whip, omnidirectional. Features
an articulating knuckle joint that can be oriented vertically or at right angles
Supported Technologies: 802.11 a/b/g/n, WPA/WPA2-Personal, WPA/WPA2-Enterprise Security,
WEP
Client Mode: WPA/WPA2-Personal and Enterprise, WEP
Access Point Mode: WPA2-Personal
WiFi Average Additional Current Contribution @ 12 Vdc:

l Client Mode: 7 mA idle, 70 mA communicating

l Access Point Mode: 62 mA idle, 70 mA communicating
l Sleep (using IPNetPower or DevConfig setting to disable): 4 mA

Receive Sensitivity: -97 dBm

10.8.2 RF radio option specifications

Antenna Terminal: Reverse Polarity SMA (RPSMA)

10. Specifications 173

Radio Type

l RF407, RF412, andRF427: Frequency Hopping Spread Spectrum (FHSS)

l RF422: SRD860 Radio with Listen before Talk (LBT) and Automatic Frequency Agility (AFA)

Frequency

l RF407: 902 to 928 MHz (US, Canada)

l RF412: 915 to 928 MHz (Australia, New Zealand)
l RF422: 863 to 870 MHz (European Union)
l RF427: 902 to 907.5 MHz/915 to 928 MHz (Brazil)

Transmit Power Output (software selectable)

l RF407 and RF412: 5 to 250 mW

l RF422: 2 to 25 mW
l RF427: 5 to 250 mW

Channel Capacity

l RF407: Eight 25-channel hop sequences sharing 64 available channels.

l RF412: Eight 25-channel hop sequences sharing 31 available channels.
l RF422: Ten 30-channel hop sequences (default), software configurable to meet local reg-
ulations; 10 sequences for reducing interference through channel hop.
l RF427: Eight 25-channel hop sequences sharing 43 available channels.

Receive Sensitivity

l RF407, RF412, and RF427: –101 dBm

l RF422: –106 dBm

RF Data Rate

l RF407, RF412, and RF427: 200 kbps

l RF422: 10 kbps

For RF additional current contribution specifications, see Power requirements (p. 164).
See also Radio communications (p. 26).

10. Specifications 174

10.8.3 Cellular option specifications
Cell Technology:

Option Cellular Protocol Market Verizon AT&T T-Mobile International

-CELL200 3G, 2G International * ü
4G LTE with automatic
-CELL205 North America ü ü
3G fallback
-CELL210 4G LTE CAT-1 United States ü
4G LTE with automatic
-CELL215 EMEA ü
3G fallback
4G LTE with automatic Australia and
-CELL220 ü
3G fallback New Zealand
* Confirm modem compliance for country/carrier where services are needed.

Antenna Terminal: SMA

Average Additional Current Contribution at 12 Vdc:

l Idle: Connected to network, no data transfer.

l -CELL200 minimum = 2 mA, average = 10 mA

l -CELL205 minimum = 2 mA, average = 14 mA

l -CELL210 minimum = 2 mA, average = 28 mA

l -CELL215 minimum = 2 mA, average = 14 mA

l -CELL220 minimum = 2 mA, average = 14 mA

l Transfer/Receive:
l -CELL200 minimum = 20 mA. Average = 105 mA

l -CELL205 minimum = 20 mA. Average = 75 mA

l -CELL210 minimum = 20 mA. Average = 90 mA

l -CELL215 minimum = 20 mA. Average = 75 mA

l -CELL220 minimum = 20 mA. Average = 75 mA

SIM Slot: Industry standard 3FF micro-SIM

10.8.3.1 -CELL200 (International)

The -CELL200 option is not compatible with a Verizon cellular network.

10. Specifications 175

Maximum Data Rate Maximum Data Rate
Technology Frequency Bands (MHz)
Downlink Uplink
UMTS/HSPA+ (3G) 800, 850, 900, 1900, 2100 7.2 Mbps 5.7 Mbps
GSM/GPRS/EDGE (2G) 850, 900, 1800, 1900 236.8 Kbps 236.8 Kbps

10.8.3.2 -CELL205 (North America)

The -CELL205 option is not compatible with a Verizon cellular network.

Maximum Data Maximum Data

Technology Frequency Bands (MHz) Rate Rate
Downlink Uplink
700, 850, 1700/2100 (AWS-1),
LTE CAT-1 (4G) 10.2 Mbps 5.2 Mbps
1900
UMTS/HSPA+
850, 1700/2100 (AWS), 1900 7.2 Mbps 5.7 Mbps
(3G)

10.8.3.3 -CELL210 (United States)

Maximum Data Rate Maximum Data Rate
Technology Frequency Bands (MHz)
Downlink Uplink
LTE CAT-1 (4G) 700, 850, 1700, 1900, 2100 10.2 Mbps 5.2 Mbps

10.8.3.4 -CELL215 (EMEA)

Maximum Maximum
Technology Frequency Bands (MHz) Data Rate Data Rate
Downlink Uplink
4G LTE with automatic 2100(B1), 1800(B3), 850(B5), 2600(B7),
10.0 Mbps 5.0 Mbps
3G fallback 900(B8), 800(B20)

10. Specifications 176

10.8.3.5 -CELL220 (Australia and New Zealand)
Maximum Maximum
Technology Frequency Bands (MHz) Data Rate Data Rate
Downlink Uplink
LTE 10.0 LTE 5.0
4G LTE with auto- LTE 2100(B1), 1800(B3), 850(B5), 2600(B7), 700 Mbps Mbps
matic 3G fallback (B28) WCDMA 2100(B1), 850(B5) WCDMA WCDMA
384 Kbps 384 Kbps

10.9 Standards compliance specifications

View EU Declarations of Conformity at www.campbellsci.com/cr300 and www.camp-
bellsci.com/cr310.
Shock and Vibration: ASTM D4169-09
Protection: IP30
EMI and ESD protection:

l Immunity: Meets or exceeds following standards:

o ESD: per IEC 61000-4-2; ±8 kV air, ±4 kV contact discharge
o RF: per IEC 61000-4-3; 3 V/m, 80-1000 MHz
o EFT: per IEC 61000-4-4; 1 kV power, 500 V I/O
o Surge: per IEC 61000-4-5; 1 kV power and I/O
o Conducted: per IEC 61000-4-6; 3 V 150 kHz-80 MHz

l Emissions and immunity performance criteria available on request.

RF407 Option

l United States FCC Part 15.247: MCQ-XB900HP

l Industry Canada (IC): 1846A-XB900HP
l Mexico IF: RCPDIXB15-0672-A1

RF412 Option

l ACMA RCM
l United States FCC Part 15.247:
l MCQ-XB900HP
l Industry Canada (IC): 1846A-XB900HP

RF422 Option: View EU Declarations of Conformity at at www.campbellsci.com/cr300 and

www.campbellsci.com/cr310.

10. Specifications 177

RF427 Option: Brazil ANATEL standards in Resolution No. 506: 08335-17-10644
WIFI Option

l United States FCC ID: XF6-RS9113SB

l Industry Canada (IC): 8407A-RS9113SB

NOTE:
The user is responsible for emissions if changing the antenna type or increasing the gain.

10. Specifications 178

11. Glossary
A

ac
Alternating current (see Vac).

accuracy
The degree to which the result of a measurement, calculation, or specification conforms
to the correct value or a standard.

ADC
Analog to digital conversion. The process that translates analog voltage levels to digital
values.

alias
A second name assigned to variable in CRBasic.

allowed neighbor list

In PakBus networking, an allowed neighbor list is a list of neighbors with which a device
will communicate. If a device address is entered in an allowed neighbor list, a hello
exchange will be initiated with that device. Any device with an address between 1 and
3999 that is not entered in the allowed neighbor list will be filtered from communicating
with the device using the list.

amperes (A)
Base unit for electric current. Used to quantify the capacity of a power source or the
requirements of a power-consuming device.

analog
Data presented as continuously variable electrical signals.

11. Glossary 179

APN
Cellular Access Point Name (obtained from your cellular network provider)

argument
Part of a procedure call (or command execution).

array
A group of variables as declared in CRBasic.

ASCII/ANSI
Abbreviation for American Standard Code for Information Interchange / American
National Standards Institute. An encoding scheme in which numbers from 0-127 (ASCII)
or 0-255 (ANSI) are used to represent pre-defined alphanumeric characters. Each number
is usually stored and transmitted as 8 binary digits (8 bits), resulting in 1 byte of storage
per character of text.

asynchronous
The transmission of data between a transmitting and a receiving device occurs as a series
of zeros and ones. For the data to be "read" correctly, the receiving device must begin
reading at the proper point in the series. In asynchronous communication, this coordin-
ation is accomplished by having each character surrounded by one or more start and stop
bits which designate the beginning and ending points of the information. Also indicates
the sending and receiving devices are not synchronized using a clock signal.

AWG
AWG ("gauge") is the accepted unit when identifying wire diameters. Larger AWG values
indicate smaller cross-sectional diameter wires. Smaller AWG values indicate large-dia-
meter wires. For example, a 14 AWG wire is often used for grounding because it can carry
large currents. 22 AWG wire is often used as sensor wire since only small currents are car-
ried when measurements are made.

11. Glossary 180

baud rate
The rate at which data is transmitted.

beacon
A signal broadcasted to other devices in a PakBus network to identify "neighbor" devices.
A beacon in a PakBus network ensures that all devices in the network are aware of other
devices that are viable. If configured to do so, a clock-set command may be transmitted
with the beacon. This function can be used to synchronize the clocks of devices within
the PakBus network.

binary
Describes data represented by a series of zeros and ones. Also describes the state of a
switch, either being on or off.

BOOL8
A one-byte data type that holds eight bits (0 or 1) of information. BOOL8 uses less space
than the 32 bit BOOLEAN data type.

boolean
Name given a function, the result of which is either true or false.

boolean data type

Typically used for flags and to represent conditions or hardware that have only two states
(true or false) such as flags and control ports.

burst
Refers to a burst of measurements. Analogous to a burst of light, a burst of meas-
urements is intense, such that it features a series of measurements in rapid succession,
and is not continuous.

11. Glossary 181

calibration wizard
The calibration wizard facilitates the use of the CRBasic field calibration instructions
FieldCal() and FieldCalStrain(). It is found in LoggerNet (4.0 and later) or RTDAQ.

callback
A name given to the process by which the datalogger initiates communications with a
computer running appropriate Campbell Scientific datalogger support software. Also
known as "Initiate Comms."

CardConvert software
A utility to retrieve binary final data from memory cards and convert the data to ASCII or
other formats.

CD100
An optional enclosure mounted keyboard/display for use with dataloggers.

CDM/CPI
CPI is a proprietary interface for communications between Campbell Scientific data-
loggers and Campbell Scientific CDM peripheral devices. It consists of a physical layer
definition and a data protocol. CDM devices are similar to Campbell Scientific SDM
devices in concept, but the use of the CPI bus enables higher data-throughput rates and
use of longer cables. CDM devices require more power to operate in general than do
SDM devices.

CF
CompactFlash®

code
A CRBasic program, or a portion of a program.

11. Glossary 182

Collect button
Button or command in datalogger support software that facilitates collection-on-demand
of final-data memory. This feature is found in PC200W, PC400, LoggerNet, and RTDAQ
software.

Collect Now button

Button or command in datalogger support software that facilitates collection-on-demand
of final-data memory. This feature is found in PC200W, PC400, LoggerNet, and RTDAQ
software.

COM port
COM is a generic name given to physical and virtual serial communication ports.

COM1
When configured as a communication port, terminals C1 and C2 act as a pair to form
Com1.

command
An instruction or signal that causes a computer to perform one of its basic functions (usu-
ally in CRBasic).

command line
One line in a CRBasic program. Maximum length, even with the line continuation char-
acters <space> <underscore> ( _), is 512 characters. A command line usually consists of
one program statement, but it may consist of multiple program statements separated by a
<colon> (:).

CompactFlash
CompactFlash® (CF) is a memory-card technology used in some Campbell Scientific
card-storage modules.

11. Glossary 183

compile
The software process of converting human-readable program code to binary machine
code. Datalogger user programs are compiled internally by the datalogger operating sys-
tem.

conditioned output
The output of a sensor after scaling factors are applied.

connector
A connector is a device that allows one or more electron conduits (wires, traces, leads,
etc) to be connected or disconnected as a group. A connector consists of two parts —
male and female. For example, a common household ac power receptacle is the female
portion of a connector. The plug at the end of a lamp power cord is the male portion of
the connector.

constant
A packet of memory given an alpha-numeric name and assigned a fixed number.

control I/O
C terminals configured for controlling or monitoring a device.

CoraScript
CoraScript is a command-line interpreter associated with LoggerNet datalogger support
software.

CPU
Central processing unit. The brains of the datalogger.

cr
Carriage return.

11. Glossary 184

CRBasic
Campbell Scientific's BASIC-like programming language that supports analog and digital
measurements, data processing and analysis routines, hardware control, and many com-
munications protocols.

CRBasic Editor
The CRBasic programming editor; supplied as part of LoggerNet, PC400, and RTDAQ soft-
ware.

CRC
Cyclic Redundancy Check

CRD
An optional memory drive that resides on a memory card.

CS I/O
Campbell Scientific proprietary input/output port. Also, the proprietary serial com-
munications protocol that occurs over the CS I/O port.

CVI
Communication verification interval. The interval at which a PakBus® device verifies the
accessibility of neighbors in its neighbor list. If a neighbor does not communicate for a
period of time equal to 2.5 times the CVI, the device will send up to four Hellos. If no
response is received, the neighbor is removed from the neighbor list.

DAC
Digital to analog conversion. The process that translates digital voltage levels to analog
values.

11. Glossary 185

data bits
Number of bits used to describe the data and fit between the start and stop bit. Sensors
typically use 7 or 8 data bits.

data cache
The data cache is a set of binary files kept on the hard disk of the computer running the
datalogger support software. A binary file is created for each table in each datalogger.
These files mimic the storage areas in datalogger memory, and by default are two times
the size of the datalogger storage area. When the software collects data from a data-
logger, the data is stored in the binary file for that datalogger. Various software functions
retrieve data from the data cache instead of the datalogger directly. This allows the sim-
ultaneous sharing of data among software functions.

data output interval

The interval between each write of a record to a final-storage memory data table.

data output processing instructions

CRBasic instructions that process data values for eventual output to final-data memory.
Examples of output-processing instructions include Totalize(), Maximize(), Minimize(),
and Average(). Data sources for these instructions are values or strings in variable
memory. The results of intermediate calculations are stored in data output processing
memory to await the output trigger. The ultimate destination of data generated by data
output processing instructions is usually final-storage memory, but the CRBasic program
can be written to divert to variable memory by the CRBasic program for further pro-
cessing. The transfer of processed summaries to final-data memory takes place when the
Trigger argument in the DataTable() instruction is set to True.

data output processing memory

SRAM memory automatically allocated for intermediate calculations performed by
CRBasic data output processing instructions. Data output processing memory cannot be
monitored.

11. Glossary 186

data point
A data value which is sent to final-data memory as the result of a data-output processing
instruction. Data points output at the same time make up a record in a data table.

data table
A concept that describes how data is organized in memory, or in files that result from col-
lecting data in memory. The fundamental data table is created by the CRBasic program as
a result of the DataTable() instruction and resides in binary form in main-memory SRAM.
The data table structure also resides in the data cache, in discrete data files on datalogger
drives, and in binary or ASCII files that result from collecting final-data memory with data-
logger support software.

datalogger support software

LoggerNet, PC400, and PC200W - these Campbell Scientific software applications
includes at least the following functions: datalogger communications, downloading pro-
grams, clock setting, and retrieval of measurement data.

DC
Direct current.

DCE
Data Communication Equipment. While the term has much wider meaning, in the limited
context of practical use with the datalogger, it denotes the pin configuration, gender,
and function of an RS-232 port. The RS-232 port on the datalogger is DCE. Interfacing a
DCE device to a DCE device requires a null-modem cable.

desiccant
A hygroscopic material that absorbs water vapor from the surrounding air. When placed
in a sealed enclosure, such as a datalogger enclosure, it prevents condensation.

Device Configuration Utility

Configuration tool used to set up dataloggers and peripherals, and to configure PakBus
settings before those devices are deployed in the field and/or added to networks.

11. Glossary 187

DHCP
Dynamic Host Configuration Protocol. A TCP/IP application protocol.

differential
A sensor or measurement terminal wherein the analog voltage signal is carried on two
wires. The phenomenon measured is proportional to the difference in voltage between
the two wires.

Dim
A CRBasic command for declaring and dimensioning variables. Variables declared with
Dim remain hidden during datalogger operations.

dimension
To code a CRBasic program for a variable array as shown in the following examples: DIM
example(3) creates the three variables example(1), example(2), and example(3); DIM
example(3,3) creates nine variables; DIM example(3,3,3) creates 27 variables.

DNP3
Distributed Network Protocol is a set of communications protocols used between com-
ponents in process automation systems. Its main use is in utilities such as electric and
water companies.

DNS
Domain name server. A TCP/IP application protocol.

DTE
Data Terminal Equipment. While the term has much wider meaning, in the limited con-
text of practical use with the datalogger, it denotes the pin configuration, gender, and
function of an RS-232 port. The RS-232 port on the datalogger is DCE. Attachment of a
null-modem cable to a DCE device effectively converts it to a DTE device.

11. Glossary 188

duplex
A serial communication protocol. Serial communications can be simplex, half-duplex, or
full-duplex.

duty cycle
The percentage of available time a feature is in an active state. For example, if the data-
logger is programmed with 1 second scan interval, but the program completes after only
100 milliseconds, the program can be said to have a 10% duty cycle.

earth ground
A grounding rod or other suitable device that electrically ties a system or device to the
earth. Earth ground is a sink for electrical transients and possibly damaging potentials,
such as those produced by a nearby lightning strike. Earth ground is the preferred ref-
erence potential for analog voltage measurements. Note that most objects have a "an
electrical potential" and the potential at different places on the earth - even a few meters
away - may be different.

endian
The sequential order in which bytes are arranged into larger numerical values when
stored in memory.

engineering units
Units that explicitly describe phenomena, as opposed to, for example, the datalogger
base analog-measurement unit of millivolts.

ESD
Electrostatic discharge.

ESS
Environmental sensor station.

11. Glossary 189

excitation
Application of a precise voltage, usually to a resistive bridge circuit.

execution interval
The time interval between initiating each execution of a given Scan() of a CRBasic pro-
gram. If the Scan() Interval is evenly divisible into 24 hours (86,400 seconds), it is syn-
chronized with the 24 hour clock, so that the program is executed at midnight and every
Scan() Interval thereafter. The program is executed for the first time at the first occurrence
of the Scan() Interval after compilation. If the Scan() Interval does not divide evenly into
24 hours, execution will start on the first even second after compilation.

execution time
Time required to execute an instruction or group of instructions. If the execution time of
a program exceeds the Scan() Interval, the program is executed less frequently than pro-
grammed and the Status table SkippedScan field will increment.

expression
A series of words, operators, or numbers that produce a value or result.

FAT
File Allocation Table - a computer file system architecture and a family of industry-stand-
ard file systems utilizing it.

FFT
Fast Fourier Transform. A technique for analyzing frequency-spectrum data.

field
Data tables are made up of records and fields. Each row in a table represents a record and
each column represents a field. The number of fields in a record is determined by the
number and configuration of output processing instructions that are included as part of
the DataTable() declaration.

11. Glossary 190

File Control
File Control is a feature of LoggerNet, PC400, PC200W, Device Configuration Utility, and
RTDAQ datalogger support software. It provides a view of the datalogger file system and
a menu of file management commands.

fill and stop memory

A memory configuration for data tables forcing a data table to stop accepting data when
full.

final-storage data
Data that resides in final-data memory.

final-storage memory
The portion of SRAM memory allocated for storing data tables with output arrays. Once
data is written to final-data memory, they cannot be changed but only overwritten when
they become the oldest data. Final-data memory is configured as ring memory by default,
with new data overwriting the oldest data.

Flash
A type of memory media that does not require battery backup. Flash memory, however,
has a lifetime based on the number of writes to it. The more frequently data is written,
the shorter the life expectancy.

FLOAT
Four-byte floating-point data type. Default datalogger data type for Public or Dim vari-
ables. Same format as IEEE4.

FP2
Two-byte floating-point data type. Default datalogger data type for stored data. While
IEEE4 four-byte floating point is used for variables and internal calculations, FP2 is
adequate for most stored data. FP2 provides three or four significant digits of resolution,
and requires half the memory as IEEE4.

11. Glossary 191

frequency domain
Frequency domain describes data graphed on an X-Y plot with frequency as the X axis.
VSPECT vibrating wire data is in the frequency domain.

frequency response
Sample rate is how often an instrument reports a result at its output; frequency response
is how well an instrument responds to fast fluctuations on its input. By way of example,
sampling a large gage thermocouple at 1 kHz will give a high sample rate but does not
ensure the measurement has a high frequency response. A fine-wire thermocouple,
which changes output quickly with changes in temperature, is more likely to have a high
frequency response.

FTP
File Transfer Protocol. A TCP/IP application protocol.

full-duplex
A serial communication protocol. Simultaneous bi-directional communications. Com-
munications between a serial port and a computer is typically full duplex.

garbage
The refuse of the data communication world. When data is sent or received incorrectly
(there are numerous reasons why this happens), a string of invalid, meaningless char-
acters (garbage) often results. Two common causes are: 1) a baud-rate mismatch and 2)
synchronous data being sent to an asynchronous device and vice versa.

global variable
A variable available for use throughout a CRBasic program. The term is usually used in
connection with subroutines, differentiating global variables (those declared using Public
or Dim) from local variables, which are declared in the Sub() and Function() instructions.

11. Glossary 192

ground
Being or related to an electrical potential of 0 volts.

ground currents
Pulling power from the datalogger wiring panel, as is done when using some com-
munication devices from other manufacturers, or a sensor that requires a lot of power,
can cause voltage potential differences between points in datalogger circuitry that are
supposed to be at ground or 0 Volts. This difference in potentials can cause errors when
measuring single-ended analog voltages.

half-duplex
A serial communication protocol. Bi-directional, but not simultaneous, communications.
SDI-12 is a half-duplex protocol.

handshake
The exchange of predetermined information between two devices to assure each that it is
connected to the other. When not used as a clock line, the CLK/HS (pin 7) line in the data-
logger CS I/O port is primarily used to detect the presence or absence of peripherals.

hello exchange
In a PakBus network, this is the process of verifying a node as a neighbor.

hertz
SI unit of frequency. Cycles or pulses per second.

HTML
Hypertext Markup Language. Programming language used for the creation of web pages.

HTTP
Hypertext Transfer Protocol. A TCP/IP application protocol.

11. Glossary 193

hysteresis
The dependence of the state of the system on its history.

Hz
SI unit of frequency. Cycles or pulses per second.

I2C
Inter-Integrated Circuit is a multi-master, multi-slave, packet switched, single-ended,
serial computer bus.

IEEE4
Four-byte, floating-point data type. IEEE Standard 754. Same format as Float.

Include file
A file containing CRBasic code to be included at the end of the current CRBasic program,
or it can be run as the default program.

INF
A data word indicating the result of a function is infinite or undefined.

initiate comms
A name given to a processes by which the datalogger initiates communications with a
computer running LoggerNet. Also known as Callback.

input/output instructions
Used to initiate measurements and store the results in input storage or to set or read con-
trol/logic ports.

instruction
Usually refers to a CRBasic command.

11. Glossary 194

integer
A number written without a fractional or decimal component. 15 and 7956 are integers;
1.5 and 79.56 are not.

intermediate memory
SRAM memory automatically allocated for intermediate calculations performed by
CRBasic data output processing instructions. Data output processing memory cannot be
monitored.

IP
Internet Protocol. A TCP/IP internet protocol.

IP address
A unique address for a device on the internet.

IP trace
Function associated with IP data transmissions. IP trace information was originally
accessed through the CRBasic instruction IPTrace() and stored in a string variable. Files
Manager setting is now modified to allow for creation of a file on a datalogger memory
drive, such as USR:, to store information in ring memory.

isolation
Hardwire communication devices and cables can serve as alternate paths to earth ground
and entry points into the datalogger for electromagnetic noise. Alternate paths to ground
and electromagnetic noise can cause measurement errors. Using opto-couplers in a con-
necting device allows communication signals to pass, but breaks alternate ground paths
and may filter some electromagnetic noise. Campbell Scientific offers optically isolated
RS-232 to CS I/O interfaces as an accessory for use on the CS I/O port.

11. Glossary 195

JSON
Java Script Object Notation. A data file format available through the datalogger or Log-
gerNet.

keep memory
keep memory is non-volatile memory that preserves some settings during a power-up or
program start up reset. Examples include PakBus address, station name, beacon intervals,
neighbor lists, routing table, and communication timeouts.

keyboard/display
The datalogger has an optional external keyboard/display.

leaf node
A PakBus node at the end of a branch. When in this mode, the datalogger is not able to
forward packets from one of its communication ports to another. It will not maintain a list
of neighbors, but it still communicates with other PakBus dataloggers and wireless
sensors. It cannot be used as a means of reaching (routing to) other dataloggers.

lf
Line feed. Often associated with carriage return (<cr>). <cr><lf>.

linearity
The quality of delivering identical sensitivity throughout the measurement.

local variable
A variable available for use only by the subroutine in which it is declared. The term dif-
ferentiates local variables, which are declared in the Sub() and Function() instructions,
from global variables, which are declared using Public or Dim.

11. Glossary 196

LoggerLink
Mobile applications that allow a mobile device to communicate with IP, wi-fi, or
Bluetooth enabled dataloggers.

LoggerNet
Campbell Scientific's datalogger support software for programming, communications,
and data retrieval between dataloggers and a computer.

LONG
Data type used when declaring integers.

loop
A series of instructions in a CRBasic program that are repeated for a programmed number
of times. The loop ends with an End instruction.

loop counter
Increments by one with each pass through a loop.

LSB
Least significant bit (the trailing bit).

LVDT
The linear variable differential transformer (LVDT) is a type of electrical transformer used
for measuring linear displacement (position).

mains power
The national power grid.

11. Glossary 197

manually initiated
Initiated by the user, usually with a Keyboard/Display, as opposed to occurring under pro-
gram control.

mass storage device

A mass storage device may also be referred to as an auxiliary storage device. The term is
commonly used to describe USB mass storage devices.

MD5 digest
16 byte checksum of the TCP/IP VTP configuration.

micro SD
A removable memory-card technology used in CR6 and CR1000X dataloggers.

milli
The SI prefix denoting 1/1000 of a base SI unit.

Modbus
Communication protocol published by Modicon in 1979 for use in programmable logic
controllers (PLCs).

modem/terminal
Any device that has the following: ability to raise the ring line or be used with an optically
isolated interface to raise the ring line and put the datalogger in the communication com-
mand state, or an asynchronous serial communication port that can be configured to
communicate with the datalogger.

modulo divide
A math operation. Result equals the remainder after a division.

MSB
Most significant bit (the leading bit).

11. Glossary 198

multimeter
An inexpensive and readily available device useful in troubleshooting data acquisition sys-
tem faults.

multiplier
A term, often a parameter in a CRBasic measurement instruction, that designates the
slope (aka, scaling factor or gain) in a linear function. For example, when converting °C
to °F, the equation is °F = °C*1.8 + 32. The factor 1.8 is the multiplier.

mV
The SI abbreviation for millivolts.

NAN
Not a number. A data word indicating a measurement or processing error. Voltage over-
range, SDI-12 sensor error, and undefined mathematical results can produce NAN.

neighbor device
Device in a PakBus network that communicates directly with a device without being
routed through an intermediate device.

Network Planner
Campbell Scientific software designed to help set up dataloggers in PakBus networks so
that they can communicate with each other and the LoggerNet server. For more inform-
ation, see https://www.campbellsci.com/loggernet.

NIST
National Institute of Standards and Technology.

node
Devices in a network — usually a PakBus network. The communications server dials
through, or communicates with, a node. Nodes are organized as a hierarchy with all

11. Glossary 199

nodes accessed by the same device (parent node) entered as child nodes. A node can be
both a parent and a child.

NSEC
Eight-byte data type divided up as four bytes of seconds since 1990 and four bytes of
nanoseconds into the second.

null modem
A device, usually a multi-conductor cable, which converts an RS-232 port from DCE to
DTE or from DTE to DCE.

Numeric Monitor
A digital monitor in datalogger support software or in a keyboard/display.

offset
A term, often a parameter in a CRBasic measurement instruction, that designates the y-
intercept (aka, shifting factor or zeroing factor) in a linear function. For example, when
converting °C to °F, the equation is °F = °C*1.8 + 32. The factor 32 is the offset.

ohm
The unit of resistance. Symbol is the Greek letter Omega (Ω). 1.0 Ω equals the ratio of 1.0
volt divided by 1.0 ampere.

Ohm's Law
Describes the relationship of current and resistance to voltage. Voltage equals the
product of current and resistance (V = I • R).

on-line data transfer

Routine transfer of data to a peripheral left on-site. Transfer is controlled by the program
entered in the datalogger.

11. Glossary 200

operating system
The operating system (also known as "firmware") is a set of instructions that controls the
basic functions of the datalogger and enables the use of user written CRBasic programs.
The operating system is preloaded into the datalogger at the factory but can be re-
loaded or upgraded by you using Device Configuration Utility software. The most recent
datalogger operating system .obj file is available at www.campbellsci.com/downloads.

output
A loosely applied term. Denotes a) the information carrier generated by an electronic
sensor, b) the transfer of data from variable memory to final-data memory, or c) the trans-
fer of electric power from the datalogger or a peripheral to another device.

output array
A string of data values output to final-data memory. Output occurs when the data table
output trigger is True.

output interval
The interval between each write of a record to a data table.

output processing instructions

CRBasic instructions that process data values for eventual output to final-data memory.
Examples of output-processing instructions include Totalize(), Maximum(), Minimum(),
and Average(). Data sources for these instructions are values or strings in variable
memory. The results of intermediate calculations are stored in data output processing
memory to await the output trigger. The ultimate destination of data generated by data
output processing instructions is usually final-data memory, but the CRBasic program can
be written to divert to variable memory for further processing. The transfer of processed
summaries to final-data memory takes place when the Trigger argument in the DataTable
() instruction is set to True.

output processing memory

SRAM memory automatically allocated for intermediate calculations performed by
CRBasic data output processing instructions. Data output processing memory cannot be
monitored.

11. Glossary 201

PakBus
® A proprietary communication protocol developed by Campbell Scientific to facilitate
communications between Campbell Scientific devices. Similar in concept to IP (Internet
Protocol), PakBus is a packet-switched network protocol with routing capabilities. A
registered trademark of Campbell Scientific, Inc.

PakBus Graph
Software that shows the relationship of various nodes in a PakBus network and allows for
monitoring and adjustment of some registers in each node.

parameter
Part of a procedure (or command) definition.

PC200W
Basic datalogger support software for direct connect. It supports a connection between
computer and datalogger and includes Short Cut for creating datalogger programs. Tools
for setting the datalogger clock, sending programs, monitoring sensors, and on-site view-
ing and collection of data is also included.

PC400
Datalogger support software that supports a variety of communication options, manual
data collection, and data monitoring displays. Short Cut and CRBasic Editor are included
for creating datalogger programs. PC400 does not support complex communication
options, such as phone-to-RF, PakBus® routing, or scheduled data collection.

PDP
Packet Data Protocol

period average
A measurement technique using a high-frequency digital clock to measure time dif-
ferences between signal transitions. Sensors commonly measured with period average
include water-content reflectometers.

11. Glossary 202

peripheral
Any device designed for use with the datalogger. A peripheral requires the datalogger to
operate. Peripherals include measurement, control, and data retrieval and com-
munication modules.

PGIA
Programmable Gain Input Amplifier

ping
A software utility that attempts to contact another device in a network.

pipeline mode
A CRBasic program execution mode wherein instructions are evaluated in groups of like
instructions, with a set group prioritization.

PLC
Programmable Logic Controllers

Poisson ratio
A ratio used in strain measurements.

ppm
Parts per million.

precision
The amount of agreement between repeated measurements of the same quantity (AKA
repeatability).

PreserveVariables
CRBasic instruction that protects Public variables from being erased when a program is
recompiled.

11. Glossary 203

print device
Any device capable of receiving output over pin 6 (the PE line) in a receive-only mode.
Printers, "dumb" terminals, and computers in a terminal mode fall in this category.

print peripheral
Any device capable of receiving output over pin 6 (the PE line) in a receive-only mode.
Printers, "dumb" terminals, and computers in a terminal mode fall in this category.

processing instructions
CRBasic instructions used to further process input-data values and return the result to a
variable where it can be accessed for output processing. Arithmetic and transcendental
functions are included.

program control instructions

Modify the execution sequence of CRBasic instructions. Also used to set or clear flags.

Program Send command

Program Send is a feature of datalogger support software.

program statement
A complete program command construct confined to one command line or to multiple
command lines merged with the line continuation characters <space><underscore> ( _).
A command line, even with line continuation, cannot exceed 512 characters.

public
A CRBasic command for declaring and dimensioning variables. Variables declared with
Public can be monitored during datalogger operation.

pulse
An electrical signal characterized by a rapid increase in voltage follow by a short plateau
and a rapid voltage decrease.

11. Glossary 204

ratiometric
Describes a type of measurement or a type of math. Ratiometric usually refers to an
aspect of resistive-bridge measurements - either the measurement or the math used to
process it. Measuring ratios and using ratio math eliminates several sources of error from
the end result.

record
A record is a complete line of data in a data table or data file. All data in a record share a
common time stamp. Data tables are made up of records and fields. Each row in a table
represents a record and each column represents a field. The number of fields in a record
is determined by the number and configuration of output processing instructions that are
included as part of the DataTable() declaration.

regulator
A setting, a Status table element, or a DataTableInformation table element. Also a device
for conditioning an electrical power source. Campbell Scientific regulators typically con-
dition ac or dc voltages greater than 16 Vdc to about 14 Vdc.

resistance
A feature of an electronic circuit that impedes or redirects the flow of electrons through
the circuit.

resistor
A device that provides a known quantity of resistance.

resolution
The smallest interval measurable.

ring line
Ring line is pulled high by an external device to notify the datalogger to commence RS-
232 communications. Ring line is pin 3 of a DCE RS-232 port.

11. Glossary 205

ring memory
A memory configuration that allows the oldest data to be overwritten with the newest
data. This is the default setting for data tables.

ringing
Oscillation of sensor output (voltage or current) that occurs when sensor excitation
causes parasitic capacitances and inductances to resonate.

RMS
Root-mean square, or quadratic mean. A measure of the magnitude of wave or other vary-
ing quantities around zero.

RNDIS
Remote Network Driver Interface Specification - a Microsoft protocol that provides a vir-
tual Ethernet link via USB.

router
A device configured as a router is able to forward PakBus packets from one port to
another. To perform its routing duties, a datalogger configured as a router maintains its
own list of neighbors and sends this list to other routers in the PakBus network. It also
obtains and receives neighbor lists from other routers. Routers maintain a routing table,
which is a list of known nodes and routes. A router will only accept and forward packets
that are destined for known devices. Routers pass their lists of known neighbors to other
routers to build the network routing system.

RS-232
Recommended Standard 232. A loose standard defining how two computing devices can
communicate with each other. The implementation of RS-232 in Campbell Scientific data-
loggers to computer communications is quite rigid, but transparent to most users.
Features in the datalogger that implement RS-232 communication with smart sensors are
flexible.

11. Glossary 206

RS-485
Recommended Standard 485. A standard defining how two computing devices can com-
municate with each other.

RTDAQ
Datalogger support software for industrial and real-time applications.

RTU
Remote Telemetry Units

Rx
Receive

sample rate
The rate at which measurements are made by the datalogger. The measurement sample
rate is of interest when considering the effect of time skew, or how close in time are a
series of measurements, or how close a time stamp on a measurement is to the true time
the phenomenon being measured occurred. A 'maximum sample rate' is the rate at which
a measurement can repeatedly be made by a single CRBasic instruction. Sample rate is
how often an instrument reports a result at its output; frequency response is how well an
instrument responds to fast fluctuations on its input. By way of example, sampling a large
gage thermocouple at 1 kHz will give a high sample rate but does not ensure the meas-
urement has a high frequency response. A fine-wire thermocouple, which changes out-
put quickly with changes in temperature, is more likely to have a high frequency
response.

SCADA
Supervisory Control And Data Acquisition

11. Glossary 207

scan interval
The time interval between initiating each execution of a given Scan() of a CRBasic pro-
gram. If the Scan() Interval is evenly divisible into 24 hours (86,400 seconds), it is syn-
chronized with the 24 hour clock, so that the program is executed at midnight and every
Scan() Interval thereafter. The program is executed for the first time at the first occurrence
of the Scan() Interval after compilation. If the Scan() Interval does not divide evenly into
24 hours, execution will start on the first even second after compilation.

scan time
When time functions are run inside the Scan() / NextScan construct, time stamps are
based on when the scan was started according to the datalogger clock. Resolution of
scan time is equal to the length of the scan.

SDI-12
Serial Data Interface at 1200 baud. Communication protocol for transferring data
between the datalogger and SDI-12 compatible smart sensors.

SDK
Software Development Kit

SDM
Synchronous Device for Measurement. A processor-based peripheral device or sensor that
communicates with the datalogger via hardwire over a short distance using a protocol
proprietary to Campbell Scientific.

Seebeck effect
Induces microvolt level thermal electromotive forces (EMF) across junctions of dissimilar
metals in the presence of temperature gradients. This is the principle behind ther-
mocouple temperature measurement. It also causes small, correctable voltage offsets in
datalogger measurement circuitry.

11. Glossary 208

semaphore
(Measurement semaphore.) In sequential mode, when the main scan executes, it locks
the resources associated with measurements. In other words, it acquires the measurement
semaphore. This is at the scan level, so all subscans within the scan (whether they make
measurements or not), will lock out measurements from slow sequences (including the
auto self-calibration). Locking measurement resources at the scan level gives non-inter-
rupted measurement execution of the main scan.

send button
Send button in datalogger support software. Sends a CRBasic program or operating sys-
tem to a datalogger.

sequential mode
A CRBasic program execution mode wherein each statement is evaluated in the order it is
listed in the program.

serial
A loose term denoting output of a series of ASCII, HEX, or binary characters or numbers in
electronic form.

Settings Editor
An editor for observing and adjusting settings. Settings Editor is a feature of Log-
gerNet|Connect, PakBus Graph, and Device Configuration Utility.

Short Cut
A CRBasic programming wizard suitable for many datalogger applications. Knowledge of
CRBasic is not required to use Short Cut.

SI
Système Internationale. The uniform international system of metric units. Specifies accep-
ted units of measure.

11. Glossary 209

signature
A number which is a function of the data and the sequence of data in memory. It is
derived using an algorithm that assures a 99.998% probability that if either the data or
the data sequence changes, the signature changes.

simplex
A serial communication protocol. One-direction data only. Serial communications
between a serial sensor and the datalogger may be simplex.

single-ended
Denotes a sensor or measurement terminal wherein the analog voltage signal is carried
on a single wire and measured with respect to ground (0 V).

skipped scans
Occur when the CRBasic program is too long for the scan interval. Skipped scans can
cause errors in pulse measurements.

slow sequence
A usually slower secondary scan in the CRBasic program. The main scan has priority over
a slow sequence.

SMS
Short message service. A text messaging service for web and mobile device systems.

SMTP
Simple Mail Transfer Protocol. A TCP/IP application protocol.

SNP
Snapshot file.

SP
Space.

11. Glossary 210

SPI
Serial Peripheral Interface - a clocked synchronous interface, used for short distance com-
munications, generally between embedded devices.

SRAM
Static Random-Access Memory

start bit
The bit used to indicate the beginning of data.

state
Whether a device is on or off.

Station Status command

A command available in most datalogger support software.

stop bit
The end of the data bits. The stop bit can be 1, 1.5, or 2.

string
A datum or variable consisting of alphanumeric characters.

support software
Campbell Scientific software that includes at least the following functions: datalogger
communications, downloading programs, clock setting, and retrieval of measurement
data.

synchronous
The transmission of data between a transmitting and a receiving device occurs as a series
of zeros and ones. For the data to be "read" correctly, the receiving device must begin
reading at the proper point in the series. In synchronous communication, this coordin-

11. Glossary 211

ation is accomplished by synchronizing the transmitting and receiving devices to a com-
mon clock signal (see also asynchronous).

system time
When time functions are run outside the Scan() / NextScan construct, the time registered
by the instruction will be based on the system clock, which has a 10 ms resolution.

table
See data table.

task
Grouping of CRBasic program instructions automatically by the datalogger compiler.
Tasks include measurement, SDM or digital, and processing. Tasks are prioritized when
the CRBasic program runs in pipeline mode. Also, a user-customized function defined
through LoggerNet Task Master.

TCP/IP
Transmission Control Protocol / Internet Protocol.

TCR
Temperature Coefficient of Resistance. TCR tells how much the resistance of a resistor
changes as the temperature of the resistor changes. The unit of TCR is ppm/°C (parts-per-
million per degree Celsius). A positive TCR means that resistance increases as temperature
increases. For example, a resistor with a specification of 10 ppm/°C will not increase in res-
istance by more than 0.000010 Ω per ohm over a 1 °C increase of the resistor temperature
or by more than .00010 Ω per ohm over a 10 °C increase.

Telnet
A software utility that attempts to contact and interrogate another specific device in a net-
work. Telnet is resident in Windows OS.

11. Glossary 212

terminal
Point at which a wire (or wires) connects to a wiring panel or connector. Wires are usually
secured in terminals by screw- or lever-and-spring actuated gates with small screw- or
spring-loaded clamps.

terminal emulator
A command-line shell that facilitates the issuance of low-level commands to a datalogger
or some other compatible device. A terminal emulator is available in most datalogger sup-
port software available from Campbell Scientific.

thermistor
A thermistor is a temperature measurement device with a resistive element that changes
in resistance with temperature. The change is wide, stable, and well characterized. The
output of a thermistor is usually non-linear, so measurement requires linearization by
means of a Steinhart-Hart or polynomial equation. CRBasic instructions Therm107(),
Therm108(), and Therm109() use Steinhart-Hart equations.

throughput rate
Rate that a measurement can be taken, scaled to engineering units, and the stored in a
final-memory data table. The datalogger has the ability to scan sensors at a rate exceed-
ing the throughput rate. The primary factor determining throughput rate is the pro-
cessing programmed into the CRBasic program. In sequential-mode operation, all
processing called for by an instruction must be completed before moving on to the next
instruction.

time domain
Time domain describes data graphed on an X-Y plot with time on the X axis. Time series
data is in the time domain.

TLS
Transport Layer Security. An Internet communication security protocol.

11. Glossary 213

toggle
To reverse the current power state.

TTL
Transistor-to-Transistor Logic. A serial protocol using 0 Vdc and 5 Vdc as logic signal
levels.

Tx
Transmit

UART
Universal Asynchronous Receiver/Transmitter for asynchronous serial communications.

UINT2
Data type used for efficient storage of totalized pulse counts, port status (status of 16
ports stored in one variable, for example) or integer values that store binary flags.

unconditioned output
The fundamental output of a sensor, or the output of a sensor before scaling factors are
applied.

UPS
Uninterruptible Power Supply. A UPS can be constructed for most datalogger applic-
ations using ac line power, a solar panel, an ac/ac or ac/dc wall adapter, a charge con-
troller, and a rechargeable battery.

URI
Uniform Resource Identifier

11. Glossary 214

URL
Uniform Resource Locator

user program
The CRBasic program written by you in Short Cut program wizard.

USR drive
A portion of memory dedicated to the storage of image or other files.

Vac
Volts alternating current.

variable
A packet of SRAM given an alphanumeric name. Variables reside in variable memory.

Vdc
Volts direct current.

VisualWeather
Datalogger support software specialized for weather and agricultural applications. The
software allows you to initialize the setup, interrogate the station, display data, and gen-
erate reports from one or more weather stations.

volt meter
An inexpensive and readily available device useful in troubleshooting data acquisition sys-
tem faults.

voltage divider
A circuit of resistors that ratiometrically divides voltage. For example, a simple two-res-
istor voltage divider can be used to divide a voltage in half. So, when fed through the

11. Glossary 215

voltage divider, 1 mV becomes 500 µV, 10 mV becomes 5 mV, and so forth. Resistive-
bridge circuits are voltage dividers.

volts
SI unit for electrical potential.

VSPECT®
® A registered trademark for Campbell Scientific's proprietary spectral-analysis, fre-
quency domain, vibrating wire measurement technique.

watchdog timer
An error-checking system that examines the processor state, software timers, and pro-
gram-related counters when the CRBasic program is running. The following will cause
watchdog timer resets, which reset the processor and CRBasic program execution: pro-
cessor bombed, processor neglecting standard system updates, counters are outside the
limits, voltage surges, and voltage transients. When a reset occurs, a counter is incre-
mented in the WatchdogTimer entry of the Status table. A low number (1 to 10) of watch-
dog timer resets is of concern, but normally indicates that the situation should just be
monitored. A large number of errors (>10) accumulating over a short period indicates a
hardware or software problem. Consult with a Campbell Scientific support engineer.

weather-tight
Describes an instrumentation enclosure impenetrable by common environmental con-
ditions. During extraordinary weather events, however, seals on the enclosure may be
breached.

web API
Application Programming Interface

wild card
A character or expression that substitutes for any other character or expression.

11. Glossary 216

XML
Extensible markup language.

τ
Time constant

11. Glossary 217

12. Index
communication options 11, 14, 65
A
cellular 23
accuracy factors 56, 113
Ethernet 17, 19
analog measurements
internet 172
input resistance and current spe-
radio 26-27, 29
cifications 167
RS-232 15
auto self-calibration 116
SDI-12 76, 78-79

B USB 15

backup 89 wifi 20

band-rejection filter 108 communication ports 10, 12

bandwidth 64 RS-232 11

BAT terminals 7 serial 65

battery 86 communication protocols 64, 116

voltage status 94 DNP3 75

big-endian 70 Modbus 65

bridge resistance 51, 56 PakBus 75

bridge strain 54 compliance 177

configuring communications 14-15
C Ethernet 17, 19
C terminals 7, 11-12 radio 26-27, 29

programmable logic control 12 USB 15

calibrating 81, 115 wifi 20
cellular 23, 175 CPU drive 46
CHG terminals 7 CR300 series 4
clock 97 CRBasic 4

collecting data 38 csi password 16, 82, 84

Com1 65 csipasswd 82, 84

12. Index 218

csipassword 84 DNP3 75
current measurements 49 drives
formatting 100
D

data E

collecting 38 earth ground 9

historic 39 electronic noise 107
keywords 116 electrostatic discharges 88
monitoring 37 enclosures 86
viewing 39 endian 70
data acquisition system 1 Ethernet 17, 19, 172
data records 40 virtual over USB 16
data storage 45 Ethernet LEDs 18
data tables 40, 121 EU Declarations of Conformity 177
example program 43 extra response time 16, 19, 22, 25
instructions 43
F
memory 100
datalogger as router 32 field calibration 115

datalogger clock 16, 19, 22, 25, 32 field name 41

dataloggers fieldname 41

current status 94 file names 115

maintenance 81 filter 108

protection 86 first notch frequency 108

resetting 93, 100 flash memory 45

datatable 40 fN1 108

DataTableInfo 37, 115 formatting drives 100

dessicant 86 full-bridge measurement 169

differential measurements 47, 104

G
digital I/O 9, 167, 171
G terminals 9

12. Index 219

ground terminals 9, 103, 105, 114 measurements
0-20mA 49
H
4-20mA 49
half-bridge measurments 169 current-loop 49
high frequency signal measurements 59, differential 47, 104
170
high-frequency signal 59
historic data 39
high frequency 170
humidity protection 86
low-level ac 59, 170

I
period-averaging 57
pulse 58-59, 62, 170
INF 96
quadrature 60
info tables 116, 121
resistance 51, 56
internal battery 86
single-ended 47, 104
internet communications 74, 172
strain 54
over USB 16
switch closure 170
K vibrating wire 63

keywords 115-116, 121 voltage 47, 166

memory 45, 100, 116
L insufficient 115
LEDs resetting 100
Ethernet 18 Modbus 65
lightening protection 88 moisture protection 86
lithium battery 86
N
little-endian 70
low-level ac measurements 59, 170 NAN 96
noise rejection 33, 107
M notch filter 108
maintenance 81
O
max time online 16, 19, 22, 25
offset voltages 105, 113-114

12. Index 220

open collector 59 programmed mode 76, 78
OS updates 89, 116 programs
creating 33
P
errors 99
P_SW terminals 9 run options 36
PakBus 75 sending 35
PakBus encryption key 16, 19, 22, 25 protection 86
pass code 82 Public table 37
password 82 pulse-width modulation 172
percent-of-reading 113 pulse measurements 12, 58-59, 62, 170
period-averaging measurements 57, 169 pulse width modulation 12
PLC 12
ports Q

communication 10 quadrature 171

Ethernet 17, 172 quadrature measurements 60
RS-232 11, 15
R
USB 15
power 8, 116, 164 radio 26-27, 29, 100, 173

12V 8 ratiometric-resistance measurements 56

budgeting 89 recorder mode 76, 78

ground 9 resetting 100

I/O 7 resistance measurements 51, 56, 169

inputs 7 resolution 113

noise 107 restore 89

output 8 RF 26-27, 29, 100, 173

supplies 7, 89, 102 RNDIS 16

USB 7, 165 router 32

process names 40 RS-232 11, 15

programmable logic control 12

12. Index 221

spark-gap protection 88
S
specifications 163
SCADA 65
standards compliance 177
scheduling collections 33
station status 94
SDI-12 11, 76, 78-79
Status table 37, 115
SE terminals 7, 9
strain measurements 54
security 82, 84, 116
SW12 8, 12
security code 16, 19, 22, 25
SW12 terminals
Seebeck effect 114
programmable logic control 12
sending a program 32
switch closure 59, 170
sending OS 89
switched voltage 166
sending programs 35
switching noise 107
sensors 2
wiring diagram 33 T
serial communications 65 table def 40
serial flash 45 table definition 40
SetSettings 115 tables 40
settings 115 DataTableInfo 37
settling errors 110 Public 37
settling time 110 Status 37
Short Cut 33 terminal definitions 4
signal ground 9 terminals
signal settling 110 BAT 7
signatures 116 C 7, 11-12, 59, 62
single-ended measurments 47, 104 CHG 7
sink limits 8 defined 4
skipped records 94 digital I/O 9
skpped scans 94 ground 9, 103, 105, 114
source limits 8 P 59, 62

12. Index 222

P_SW 9
W
pulse 58-59
watchdog error 94
SE 7, 9
web access 16
VX 7
wifi 20
testing communication 32
wiring 4
time
power I/O 7
keeping 97
wiring diagram
skew 98
0-20mA devices 49
stamps 97-98
4-20mA devices 49
TOA5 40
sensors 33
transparent mode 76
wiring panel 4
troubleshooting 93

updating OS 89
USB 7, 10, 15, 165
Ethernet 16

variable out of bounds 94

vibrating wire measurements 63
View Pro 39
voltage excitation 166
voltage measurements 47, 166
improving 104
VSPECT 63
VX terminals 7
programmable logic control 13

12. Index 223

Campbell Scientific Worldwide Offices

Australia Germany
Location: Garbutt, QLD Australia Location: Bremen, Germany
Email: info@campbellsci.com.au Email: info@campbellsci.de
Website: www.campbellsci.com.au Website: www.campbellsci.de

Brazil South Africa

Location: São Paulo, SP Brazil Location: Stellenbosch, South Africa
Email: andread@campbellsci.com.br Email: sales@csafrica.co.za
Website: www.campbellsci.com.br Website: www.campbellscientific.co.za

Canada Southeast Asia

Location: Edmonton, AB Canada Location: Bangkok, Thailand
Email: dataloggers@campbellsci.ca Email: info@campbellsci.asia
Website: www.campbellsci.ca Website: www.campbellsci.asia

China Spain
Location: Beijing, P. R. China Location: Barcelona, Spain
Email: info@campbellsci.com.cn Email: info@campbellsci.es
Website: www.campbellsci.com.cn Website: www.campbellsci.es

Costa Rica UK
Location: San José, Costa Rica Location: Shepshed, Loughborough, UK
Email: info@campbellsci.cc Email: sales@campbellsci.co.uk
Website: www.campbellsci.cc Website: www.campbellsci.co.uk

France USA
Location: Antony, France Location: Logan, UT USA
Email: info@campbellsci.fr Email: info@campbellsci.com
Website: www.campbellsci.fr Website: www.campbellsci.com

Please visit www.campbellsci.com/contact to obtain contact information

for your local US or international representative.

GM Supplier Training CONDOR SPANISH 011521
No ratings yet
GM Supplier Training CONDOR SPANISH 011521
82 pages
ZAU-2200285-MAN-VVVF - Danfoss Vacon NXP Manuale - Cavotec - Eng - v324
No ratings yet
ZAU-2200285-MAN-VVVF - Danfoss Vacon NXP Manuale - Cavotec - Eng - v324
64 pages
Kobold Press - Empire of Ghouls PDF
100% (18)
Kobold Press - Empire of Ghouls PDF
355 pages
Pushrod Cable Retermination Guide en
100% (1)
Pushrod Cable Retermination Guide en
60 pages
HPX6 59 P1a
No ratings yet
HPX6 59 P1a
3 pages
Manual Horner Ocs He-Xe102
No ratings yet
Manual Horner Ocs He-Xe102
112 pages
HP Uses OR
No ratings yet
HP Uses OR
14 pages
Ingersoll Rand IRN150-OF-150A - CAGI
No ratings yet
Ingersoll Rand IRN150-OF-150A - CAGI
1 page
Comparación Entre Bombas API y ASME
100% (1)
Comparación Entre Bombas API y ASME
2 pages
Manual de StatFit
No ratings yet
Manual de StatFit
112 pages
300B Technical Manual PDF
No ratings yet
300B Technical Manual PDF
20 pages
S1-1054/2 10kV Digital Insulation Tester: User Manual
No ratings yet
S1-1054/2 10kV Digital Insulation Tester: User Manual
24 pages
Ups Centiel Trifásica 10kva
No ratings yet
Ups Centiel Trifásica 10kva
8 pages
ACS2000 Catalogo
No ratings yet
ACS2000 Catalogo
34 pages
Radc RDH-376
No ratings yet
Radc RDH-376
416 pages
Permalast Sintetico
No ratings yet
Permalast Sintetico
1 page
Intelecool 2
No ratings yet
Intelecool 2
8 pages
MIC900 - 1100 - 3000 V00.21 - User - Manual - en - 01
No ratings yet
MIC900 - 1100 - 3000 V00.21 - User - Manual - en - 01
52 pages
Anexo 5 MANUAL CELDAS GIS RVAC - EATON
100% (1)
Anexo 5 MANUAL CELDAS GIS RVAC - EATON
34 pages
Speedline MPM Accela Spare Parts
100% (1)
Speedline MPM Accela Spare Parts
5 pages
Citizen A32 Brochure
No ratings yet
Citizen A32 Brochure
4 pages
PLANOS ELECTRICOS ALPS 150 SN 2053
No ratings yet
PLANOS ELECTRICOS ALPS 150 SN 2053
7 pages
Ge RRTD Manual PN 1601-0104-b7
100% (1)
Ge RRTD Manual PN 1601-0104-b7
82 pages
Caja de Conexion Metálica Wet Location - Hangzhou - Ul - E483162 - 2022.08
No ratings yet
Caja de Conexion Metálica Wet Location - Hangzhou - Ul - E483162 - 2022.08
16 pages
WEB bbb4 Catalog PDF
No ratings yet
WEB bbb4 Catalog PDF
128 pages
Coursera
No ratings yet
Coursera
12 pages
Manual Bateria Gil 7641-20
No ratings yet
Manual Bateria Gil 7641-20
36 pages
Obsolescence Notification GS April 2017
No ratings yet
Obsolescence Notification GS April 2017
8 pages
Slim Line Ceiling Concealed Ducted Split Systems: 53QDMT 12-18-24-30-36-42-48-60 Heat Pump
No ratings yet
Slim Line Ceiling Concealed Ducted Split Systems: 53QDMT 12-18-24-30-36-42-48-60 Heat Pump
49 pages
Controlnet Fiber-Optic Ring Repeater Modules: Installation Instructions
No ratings yet
Controlnet Fiber-Optic Ring Repeater Modules: Installation Instructions
40 pages
Lista Chint Exel
0% (1)
Lista Chint Exel
27 pages
Center 531
No ratings yet
Center 531
1 page
Weight Indicating Instrument: Technical and Operation Manual
No ratings yet
Weight Indicating Instrument: Technical and Operation Manual
94 pages
Reporte Dialux Hospital Ejemplo
No ratings yet
Reporte Dialux Hospital Ejemplo
27 pages
Ni 9024
No ratings yet
Ni 9024
20 pages
Achieving Better Indoor Air Quality With IoT Systems
No ratings yet
Achieving Better Indoor Air Quality With IoT Systems
14 pages
NTC 1580
No ratings yet
NTC 1580
5 pages
490NAA271XX
No ratings yet
490NAA271XX
2 pages
Fichas de Aprendizaje IBM Data Science Quiz Questions - Quizlet
No ratings yet
Fichas de Aprendizaje IBM Data Science Quiz Questions - Quizlet
16 pages
Ut511 en
No ratings yet
Ut511 en
31 pages
Lista Sites CLARO
No ratings yet
Lista Sites CLARO
734 pages
Leica HDS4500 25m and 53m
No ratings yet
Leica HDS4500 25m and 53m
2 pages
Catálogo Basorfil - 2023
No ratings yet
Catálogo Basorfil - 2023
12 pages
CET Power - T2S ETH - User Manual - V1.1
No ratings yet
CET Power - T2S ETH - User Manual - V1.1
66 pages
Cambridge Cooling Systems: Global Operations Strategy
No ratings yet
Cambridge Cooling Systems: Global Operations Strategy
10 pages
Vacon NXP Grid Converter Application Manual DPD01599B UK
No ratings yet
Vacon NXP Grid Converter Application Manual DPD01599B UK
138 pages
Manual Del Raptor Ver - 7
No ratings yet
Manual Del Raptor Ver - 7
405 pages
7PA22 23 Catalog SIP-2008 en
No ratings yet
7PA22 23 Catalog SIP-2008 en
4 pages
Formulas TPM
No ratings yet
Formulas TPM
9 pages
DC3000 Product Reference and Installation Guide (English)
No ratings yet
DC3000 Product Reference and Installation Guide (English)
206 pages
Motor Starters Type 2 Coordination AllenBradley
No ratings yet
Motor Starters Type 2 Coordination AllenBradley
4 pages
Retrofit Solution For Circuit Breaker Type EDF: Desiccant Canister Helps Improving SF Gas Quality
No ratings yet
Retrofit Solution For Circuit Breaker Type EDF: Desiccant Canister Helps Improving SF Gas Quality
2 pages
Modeling and Simulation The Current Transformer For Measuring Current Harmonics Using MATLAB-SIMULINK PDF
No ratings yet
Modeling and Simulation The Current Transformer For Measuring Current Harmonics Using MATLAB-SIMULINK PDF
10 pages
86000, 86106, and 86004 Sonic Anemometers: Campbell Scientific (Canada) Corp
No ratings yet
86000, 86106, and 86004 Sonic Anemometers: Campbell Scientific (Canada) Corp
37 pages
CCFC Man
No ratings yet
CCFC Man
142 pages
CR 300
No ratings yet
CR 300
128 pages
Electrically Heated Rain and Snow Gage: Revision: 4/15
No ratings yet
Electrically Heated Rain and Snow Gage: Revision: 4/15
27 pages
Revision: 11/2018: Campbell Scientific, Inc
100% (1)
Revision: 11/2018: Campbell Scientific, Inc
47 pages
CR1000 Datalogger
No ratings yet
CR1000 Datalogger
630 pages
Si 111
No ratings yet
Si 111
19 pages
cr800 cr850 PDF
No ratings yet
cr800 cr850 PDF
598 pages
N I Act Esaay
100% (2)
N I Act Esaay
55 pages
Assignment
No ratings yet
Assignment
3 pages
Sample Memorial
No ratings yet
Sample Memorial
18 pages
The Role of Probiotics in Gut Health and Disease (WWW - Kiu.ac - Ug)
No ratings yet
The Role of Probiotics in Gut Health and Disease (WWW - Kiu.ac - Ug)
4 pages
Summer Vacation BST Holiday Homework
No ratings yet
Summer Vacation BST Holiday Homework
22 pages
Cu Mid Year Listening Test
No ratings yet
Cu Mid Year Listening Test
2 pages
Art and Design Asthetics
No ratings yet
Art and Design Asthetics
30 pages
Artist: Eminem /album: The Marshall Mathers LP (2000) /song: Drug Ballad
No ratings yet
Artist: Eminem /album: The Marshall Mathers LP (2000) /song: Drug Ballad
9 pages
Fhsis Report
No ratings yet
Fhsis Report
2 pages
Environmental Studies: Griha Water Conservation Case Studies Semester - 8 Rizvicollege of Architecture
No ratings yet
Environmental Studies: Griha Water Conservation Case Studies Semester - 8 Rizvicollege of Architecture
3 pages
Vision and Mission Vision Statement: United Schools of Science and Technology (USST) Colleges San Isidro, Tarlac City
100% (1)
Vision and Mission Vision Statement: United Schools of Science and Technology (USST) Colleges San Isidro, Tarlac City
8 pages
Domestic Violence Final
100% (1)
Domestic Violence Final
20 pages
Cat Driver Information Card - LEDT7022
No ratings yet
Cat Driver Information Card - LEDT7022
2 pages
Computer Aided Machine Drawing
0% (1)
Computer Aided Machine Drawing
16 pages
De Vries, Unsung Friendship
No ratings yet
De Vries, Unsung Friendship
6 pages
Kamp (1974) Free Choice Permission
No ratings yet
Kamp (1974) Free Choice Permission
18 pages
Inflations, Its Types and Causes of Inflation in Pakistan
No ratings yet
Inflations, Its Types and Causes of Inflation in Pakistan
5 pages
SFBT Course Handbook
100% (1)
SFBT Course Handbook
19 pages
SAN BEDA COLLEGE Mendiola Manila Departm PDF
No ratings yet
SAN BEDA COLLEGE Mendiola Manila Departm PDF
8 pages
Pre-Trial Report
100% (1)
Pre-Trial Report
10 pages
TYS Questions by Topics (Full)
No ratings yet
TYS Questions by Topics (Full)
10 pages
Ministries PPT For SHS - 23.9.2023 - V2
No ratings yet
Ministries PPT For SHS - 23.9.2023 - V2
25 pages
Chapter 703
No ratings yet
Chapter 703
14 pages
(Journal) Mapping The Policy Space of Public Consultations Evidence From The European Union - Supp
No ratings yet
(Journal) Mapping The Policy Space of Public Consultations Evidence From The European Union - Supp
7 pages
Pradeep Thesis Final Draft - 12062020
No ratings yet
Pradeep Thesis Final Draft - 12062020
105 pages
Neuro PT Assessment
No ratings yet
Neuro PT Assessment
26 pages
Second Year - English
No ratings yet
Second Year - English
128 pages
Grade 10 Data Handling QP 2024
No ratings yet
Grade 10 Data Handling QP 2024
6 pages
DL 650 Am 3
No ratings yet
DL 650 Am 3
108 pages

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.

CR310 Manual

Uploaded by

CR310 Manual

Uploaded by

Revision: 12/19/2018

Copyright © 2000 – 2018

Utility and Electrical

Elevated Work and Weather

l Exercise extreme caution when performing elevated work.

l Protect from over-voltage.

IMPORTANT: Note the following about the internal battery:

2. Wiring panel and terminal 4

3. Setting up the datalogger 14

4. Working with data 37

Table of Contents - iii

8. Maintaining your datalogger 81

9. Tips and troubleshooting 93

10. Specifications 163

11. Glossary 179

12. Index 218

Table of Contents - vii

Following is a list of typical data acquisition system components:

1. Data acquisition system components 1

1. Data acquisition system components 2

1.2.1 CR300 Series Product Line

l RF407: US and Canada

1. Data acquisition system components 3

2. Wiring panel and terminal

2. Wiring panel and terminal 4

Table 2-1: Analog input terminal functions

Table 2-2: Pulse counting terminal functions

2. Wiring panel and terminal 5

Table 2-4: Voltage1 output terminal functions

Table 2-5: Communications terminal functions

Table 2-6: Digital I/O terminal functions

2. Wiring panel and terminal 6

l 10 to 18 Vdc applied to the BAT + and – terminals

2. Wiring panel and terminal 7

2.1.1 Power LED indicator

l Off: No power, no program running.

2.2 Power output

l Continuous 12 V: BAT + and – provide a connection to the unregulated, nominal 12 Vdc

2. Wiring panel and terminal 8

See also Power requirements (p. 164).

2. Wiring panel and terminal 9

l Minimizing ground loop errors (p. 103)

2.4 Communications ports

Campbell Scientific datalogger communications ports include:

2.4.1 USB port

2. Wiring panel and terminal 10

2.4.2 Ethernet port

2.4.3 C terminals for communications

2.4.3.1 SDI-12 ports

2.4.4 RS-232 Port

2. Wiring panel and terminal 11

2.5 Programmable logic control

l Controlling cellular modem or GPS receiver to conserve power.

2. Wiring panel and terminal 12

2. Wiring panel and terminal 13

1. Configuring your communications connection.

3.1 Setting up communications with the

l USB or RS-232 communications (p. 15)

3. Setting up the datalogger 14

1. Using datalogger support software, launch the EZSetup Wizard.

3. Setting up the datalogger 15

3.1.2 Virtual Ethernet over USB (RNDIS)

3.1.2.1 Connecting to your datalogger via RNDIS

3. Setting up the datalogger 16

3.1.3 Ethernet communications

3.1.3.1 Configuring datalogger Ethernet settings

3. Setting up the datalogger 17

3.1.3.2 Ethernet LEDs

l Solid Yellow: Valid Ethernet link.

3. Setting up the datalogger 18

1. Using datalogger support software, open EZSetup.

tain amount of time before returning a communications failure error.

the datalogger remains connected. When the datalogger is contacted, com-

3. Setting up the datalogger 19

3.1.4 Wi-Fi communications

See also Communications specifications (p. 172).