Campbell Scientific CR300 User Manual

Revision: 07/10/2020
Copyright © 2000 – 2020
Campbell Scientific, Inc.
Table of Contents
1. CR300 series data acquisition system components 1
1.1 The CR300 Series Datalogger 2
1.1.1 CR300 Series Product Line 2
1.1.2 Overview 3
1.1.3 Operations 3
1.1.4 Programs 3
1.2 Sensors 3
2. Wiring panel and terminal functions 5
2.1 Power input 7
2.1.1 Power LED indicator 9
2.2 Power output 9
2.3 Grounds 10
2.4.1 USB device port 11
2.4.2 Ethernet port 11
2.4.3 C terminals for communications 12
2.4.3.1 SDI-12 ports 12
2.4.4 RS-232 Port 12
2.4.4.1 RS-232 Power States 12
2.5 Programmable logic control 13
3. Setting up the CR300 series 15
4. Setting up communications with the data logger 16
4. USB or RS-232 communications 17
5. Virtual Ethernet over USB (RNDIS) 19
6. Ethernet communications option 21
6.2 Ethernet LEDs 22
6.3 Setting up Ethernet communications between the data logger and computer 22
7. Wi-Fi communications option 25
Table of Contents - i
7.1 Configuring the data logger to host a Wi-Fi network 25
7.2 Connecting your computer to the data logger over Wi-Fi 26
7.3 Setting up Wi-Fi communications between the data logger and the data logger support software 26
7.4 Configuring data loggers to join a Wi-Fi network 27
7.5 Wi-Fi LED indicator 28
8. Cellular communications option 29
8.1 Pre-installation 29
8.1.1 Establish cellular service 30
8.1.1.1 Selecting a data service 30
8.1.2 Install the SIM card 30
8.1.3 Konect PakBus Router setup 31
8.1.3.1 Get started 31
8.1.3.2 Set up Konect PakBus Router 32
8.2 Installation 33
8.2.1 Modules using Konect PakBus Router (private dynamic IP) 33
8.2.1.1 Configure data logger 33
8.2.1.2 Set up LoggerNet 35
8.2.1.3 Test the connection 37
8.2.2 Modules using a public static IP 37
8.2.2.1 Configure data logger 37
8.2.2.2 Set up LoggerNet 38
8.2.2.3 Test the connection 40
8.3 Cellular (TX/RX) LED Indicator 41
8.4 Signal strength 41
9. Radio communications option 42
9.1 Configuration options 43
9.2 RF407-Series radio communications with one or more data loggers 43
9.2.1 Configuring the RF407-Series radio 44
9.2.2 Setting up communications between the RF407-Series data logger and the computer 44
9.3 RF407-Series radio communications with multiple data loggers using one data logger as a router 46
9.3.1 Configuring the RF407-Series radio 46
9.3.2 Configuring the data logger acting as a router 47
9.3.2.1 Adding routing data logger to LoggerNet network 47
Table of Contents - ii
9.3.2.2 Adding leaf data loggers to the network 48
9.3.3 Using additional communications methods 49
10. Testing communications with EZSetup 50
11. Creating a Short Cut data logger program 52
11.1 Sending a program to the data logger 54
12. Working with data 56
12.1 Default data tables 56
12.2 Collecting data 57
12.2.1 Collecting data using LoggerNet 57
12.2.2 Collecting data using PC200W or PC400 57
12.3 Viewing historic data 58
12.4 Data types and formats 58
12.4.1 Variables 59
12.4.2 Data storage 60
12.5.1 Table definitions 62
12.5.1.1 Header rows 62
12.5.1.2 Data records 64
12.6 Creating data tables in a program 64
13. Data memory 66
13.1 Data tables 66
13.2 Flash memory 66
13.2.1 CPU drive 67
14. Measurements 68
14.1 Voltage measurements 68
14.1.1 Single-ended measurements 69
14.1.2 Differential measurements 69
14.2 Current-loop measurements 70
14.2.1 Voltage Ranges for Current Measurements 70
14.2.2 Example Current-Loop Measurement Connections 71
14.3 Resistance measurements 72
14.3.1 Resistance measurements with voltage excitation 73
14.3.2 Strain measurements 75
Table of Contents - iii
14.3.3 Accuracy for resistance measurements 77
14.4 Period-averaging measurements 78
14.5 Pulse measurements 78
14.5.1 Low-level AC measurements 80
14.5.2 High-frequency measurements 80
14.5.3 Switch-closure and open-collector measurements 81
14.5.3.1 P_SW Terminal 81
14.5.3.2 C terminals 81
14.5.4 Quadrature measurements 82
14.5.5 Pulse measurement tips 83
14.5.5.1 Input filters and signal attenuation 83
14.5.5.2 Pulse count resolution 83
14.6 Vibrating wire measurements 84
14.6.1 VSPECT® 84
15. Communications protocols 85
15.1 General serial communications 86
15.2 Modbus communications 87
15.2.1 About Modbus 88
15.2.2 Modbus protocols 89
15.2.3 Understanding Modbus Terminology 90
15.2.4 Connecting Modbus devices 90
15.2.5 Modbus master-slave protocol 90
15.2.6 About Modbus programming 91
15.2.6.1 Endianness 91
15.2.6.2 Function codes 92
15.2.7 Modbus information storage 92
15.2.7.1 Registers 93
15.2.7.2 Coils 93
15.2.7.3 Data Types 93 Unsigned 16-bit integer 94 Signed 16-bit integer 94 Signed 32-bit integer 94 Unsigned 32-bit integer 94 32-Bit floating point 95
15.2.8 Modbus tips and troubleshooting 95
15.2.8.1 Error codes 95
Table of Contents - iv
Result code -01: illegal function 95 Result code -02: illegal data address 95 Result code -11: COM port error 96
15.3 Internet Communications 96
15.4 DNP3 communications 97
15.5 PakBus communications 97
15.6 SDI-12 communications 98
15.6.1 SDI-12 transparent mode 98
15.6.1.1 SDI-12 transparent mode commands 100
15.6.2 SDI-12 programmed mode/recorder mode 100
15.6.3 Programming the data logger to act as an SDI-12 sensor 101
15.6.4 SDI-12 power considerations 101
16. CR300 series maintenance 103
16.1 Data logger calibration 103
16.2 Data logger security 104
16.2.1 TLS 105
16.2.2 Security codes 106
16.2.3 Creating a .csipasswd file 107
16.2.3.1 Command syntax 108
16.3 Data logger enclosures 108
16.4 Internal battery 109
16.4.1 Replacing the internal battery 110
16.6 Power budgeting 113
16.7 Updating the operating system 113
16.7.1 Sending an operating system to a local data logger 114
16.7.2 Sending an operating system to a remote data logger 115
17. Tips and troubleshooting 117
17.1 Checking station status 118
17.1.1 Viewing station status 119
17.1.2 Watchdog errors 119
17.1.3 Results for last program compiled 120
17.1.4 Skipped scans 120
17.1.5 Skipped records 120
17.1.6 Variable out of bounds 120
Table of Contents - v
17.1.7 Battery voltage 120
17.2 Understanding NAN and INF occurrences 120
17.3 Timekeeping 121
17.3.1 Clock best practices 122
17.3.2 Time stamps 122
17.3.3 Avoiding time skew 123
17.4 CRBasic program errors 123
17.4.1 Program does not compile 124
17.4.2 Program compiles but does not run correctly 124
17.5 Troubleshooting Radio Communications 125
17.6 Reducing out of memory errors 125
17.7 Resetting the data logger 125
17.7.1 Processor reset 126
17.7.2 Program send reset 126
17.7.3 Manual data table reset 126
17.7.4 Formatting drives 127
17.7.5 Full memory reset 127
17.8 Troubleshooting power supplies 127
17.9 Using terminal mode 128
17.9.1 Serial talk through and comms watch 130
17.9.2 SDI-12 transparent mode 130
17.9.2.1 SDI-12 transparent mode commands 132
17.9.3 Terminal master 132
17.10 Ground loops 133
17.10.1 Common causes 133
17.10.2 Detrimental effects 134
17.10.3 Severing a ground loop 135
17.10.4 Soil moisture example 136
17.11 Improving voltage measurement quality 137
17.11.1 Deciding between single-ended or differential measurements 138
17.11.2 Minimizing ground potential differences 139
17.11.2.1 Ground potential differences 139
17.11.3 Minimizing power-related artifacts 140
17.11.3.1 Minimizing electronic noise 141
17.11.4 Filtering to Reduce Measurement Noise 141
17.11.5 Minimizing settling errors 144
17.11.5.1 Measuring settling time 144
Table of Contents - vi
17.11.6 Factors affecting accuracy 146
17.11.6.1 Measurement accuracy example 146
17.11.7 Minimizing offset voltages 147
17.12 Field calibration 148
17.13 File name and resource errors 149
18. Information tables and settings (advanced) 150
18.1.1 DataFillDays 151
18.1.2 DataRecordSize 151
18.1.3 DataTableName 151
18.1.4 RecNum 151
18.1.5 SecsPerRecord 152
18.1.6 SkippedRecord 152
18.1.7 TimeStamp 152
18.2 Status table system information 152
18.2.1 Battery 152
18.2.2 CalGain 152
18.2.3 CalOffset 152
18.2.4 CommsMemFree 153
18.2.5 CompileResults 153
18.2.6 CPUDriveFree 153
18.2.7 DataStorageFree 153
18.2.8 DataStorageSize 153
18.2.9 FullMemReset 153
18.2.10 LastSlowScan 153
18.2.11 LithiumBattery 153
18.2.12 MaxProcTime 154
18.2.13 MaxSlowProcTime 154
18.2.14 MeasureTime 154
18.2.15 MemoryFree 154
18.2.16 MemorySize 154
18.2.17 OSDate 154
18.2.18 OSSignature 154
18.2.19 OSVersion 154
18.2.20 PakBusRoutes 155
18.2.21 PanelTemp 155
Table of Contents - vii
18.2.22 PortConfig 155
18.2.23 PortStatus 155
18.2.24 ProcessTime 155
18.2.25 ProgErrors 155
18.2.26 ProgName 156
18.2.27 ProgSignature 156
18.2.28 RecNum 156
18.2.29 RevBoard 156
18.2.30 RunSignature 156
18.2.31 SerialNumber 156
18.2.32 SerialFlashErrors 156
18.2.33 SkippedScan 157
18.2.34 SlowProcTime 157
18.2.35 StartTime 157
18.2.36 StartUpCode 157
18.2.37 StationName 157
18.2.38 SW12Volts 157
18.2.39 TimeStamp 158
18.2.40 VarOutOfBound 158
18.2.41 WatchdogErrors 158
18.2.42 WiFiUpdateReq 158
18.3 Settings 158
18.3.1 Baudrate 159
18.3.2 Beacon 159
18.3.3 Cell Settings 159
18.3.4 CentralRouters 159
18.3.5 CommsMemAlloc 160
18.3.6 DNS 160
18.3.7 EthernetInfo 160
18.3.8 EthernetPower 160
18.3.9 FilesManager 160
18.3.10 FTPEnabled 160
18.3.11 FTPPassword 161
18.3.12 FTPPort 161
18.3.13 FTPUserName 161
18.3.14 HTTPEnabled 161
18.3.15 HTTPPort 161
Table of Contents - viii
18.3.16 HTTPSEnabled 161
18.3.17 HTTPSPort 161
18.3.18 IncludeFile 161
18.3.19 IPAddressEth 162
18.3.20 IPGateway 162
18.3.21 IPMaskEth 162
18.3.22 IPMaskWiFi 162
18.3.23 IPTrace 162
18.3.24 IPTraceCode 163
18.3.25 IPTraceComport 163
18.3.26 IsRouter 163
18.3.27 MaxPacketSize 163
18.3.28 Neighbors 163
18.3.29 PakBusAddress 164
18.3.30 PakBusEncryptionKey 164
18.3.31 PakBusNodes 164
18.3.32 PakBusPort 164
18.3.33 PakBusTCPClients 164
18.3.34 PakBusTCPEnabled 164
18.3.35 PakBusTCPPassword 165
18.3.36 PingEnabled 165
18.3.37 pppDial 165
18.3.38 pppDialResponse 165
18.3.39 pppInfo 165
18.3.40 pppInterface 166
18.3.41 pppIPAddr 166
18.3.42 pppPassword 166
18.3.43 pppUsername 166
18.3.44 RouteFilters 166
18.3.45 RS232Power 167
18.3.46 Security(1), Security(2), Security(3) 167
18.3.47 ServicesEnabled 167
18.3.48 TCPClientConnections 167
18.3.49 TCPPort 167
18.3.50 TelnetEnabled 167
18.3.51 TLSConnections 167
18.3.52 TLSPassword 167
Table of Contents - ix
18.3.53 TLSStatus 168
18.3.54 UDPBroadcastFilter 168
18.3.55 UTCOffset 168
18.3.56 Verify 168
18.3.57 Cellular settings 168
18.3.57.1 CellAPN 169
18.3.57.2 CellEnabled 169
18.3.57.3 CellInfo 169
18.3.57.4 CellKeepAlive 169
18.3.57.5 CellKeepAliveTime 170
18.3.57.6 CellPDPAuth 170
18.3.57.7 CellPDPPassword 170
18.3.57.8 CellPDPUserName 170
18.3.57.9 CellPwrDuration 171
18.3.57.10 CellPwrRepeat 171
18.3.57.11 CellPwrStartTime 171
18.3.57.12 CellRSRQ 172
18.3.57.13 CellRSSI 172
18.3.57.14 CellState 173
18.3.57.15 CellStatus 173
18.3.58 RF407-series radio settings 174
18.3.58.1 RadioAvailFreq 174
18.3.58.2 RadioChanMask 174
18.3.58.3 RadioEnable 174
18.3.58.4 RadioHopSeq 175
18.3.58.5 RadioMAC 175
18.3.58.6 RadioModel 175
18.3.58.7 RadioModuleVer 175
18.3.58.8 RadioNetID 176
18.3.58.9 RadioProtocol 176
18.3.58.10 RadioPwrMode 176
18.3.58.11 RadioRetries 177
18.3.58.12 RadioRSSI 177
18.3.58.13 RadioRSSIAddr 178
18.3.58.14 RadioStats 178
18.3.58.15 RadioTxPwr 179
18.3.59 Wi-Fi settings 179
Table of Contents - x
18.3.59.1 IPAddressWiFi 179
18.3.59.2 IPGatewayWiFi 179
18.3.59.3 IPMaskWiFi 180
18.3.59.4 WiFiChannel 180
18.3.59.5 WiFiConfig 180
18.3.59.6 WiFiEAPMethod 180
18.3.59.7 WiFiEAPPassword 180
18.3.59.8 WiFiEAPUser 181
18.3.59.9 Networks 181
18.3.59.10 WiFiEnable 181
18.3.59.11 WiFiPassword 181
18.3.59.12 WiFiPowerMode 181
18.3.59.13 WiFiSSID (Network Name) 182
18.3.59.14 WiFiStatus 182
18.3.59.15 WiFiTxPowerLevel 182
18.3.59.16 WLANDomainName 182
19. CR300 series Specifications 183
19.1 System specifications 183
19.2 Physical specifications 184
19.3 Power requirements 184
19.4 Power output specifications 186
19.5 Analog measurement specifications 187
19.5.1 Voltage measurements 187
19.5.2 Resistance measurement specifications 189
19.5.3 Period-averaging measurement specifications 190
19.5.4 Current-loop measurement specifications 190
19.6.1 Switch-closure input 191
19.6.2 High-frequency input 191
19.6.3 Low-level AC input 191
19.6.4 Quadrature input 192
19.7 Digital input/output specifications 192
19.7.1 Pulse-width modulation 193
19.8 Communications specifications 193
19.8.1 Wi-Fi option specifications 193
19.8.2 RF radio option specifications 194
Table of Contents - xi
19.8.3 Cellular option specifications 195
19.9 Standards compliance specifications 195
Appendix A. Configure cellular settings and retrieve status information with SetSetting() 197
Appendix B. Cellular module regulatory information 201
B.1 Important information for Australian users 201 B.2 RF exposure 201 B.3 EU 202 B.4 Declaration of conformity 202
Appendix C. Glossary 203
Table of Contents - xii

1. CR300 series 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. 3) for more information).
l Data logger - The data logger measures electrical signals or reads serial characters. It
converts 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 data logger,
usually to a computer, by one or more methods using data logger support software. Most communications options are bi-directional, which allows programs and settings to be sent
1. CR300 series data acquisition system components 1
to the data logger. For more information, see Sending a program to the data logger (p.
54).
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 data logger is adept at programmable logic control. See Programmable logic control (p. 13) for more information.

1.1 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 requirements, 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 perform 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.1.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 Ethernet 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
NOTE: Throughout this document CR300 series refers to all of the models unless specified otherwise.
1. CR300 series data acquisition system components 2

1.1.2 Overview

The CR300 series data logger is the main part of a data acquisition system (see CR300 series 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 data logger to operate for extended time on a battery recharged with a solar panel, eliminating the need for ac power. The CR300 series temporarily suspends operations when primary power drops below 9.6 V, reducing the possibility of inaccurate measurements.

1.1.3 Operations

The CR300 series measures almost any sensor with an electrical response, drives direct communications and telecommunications, reduces data to statistical values, performs calculations, and controls external devices. After measurements are made, data is stored in onboard, nonvolatile 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.1.4 Programs

A program directs the data logger 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 use the extensive help available within the CRBasic Editor (also see https://help.campbellsci.com/CRBasic/CR300/ for searchable, CRBasic online help).

1.2 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.
1. CR300 series data acquisition system components 3
Most electronic sensors, regardless of manufacturer, will interface with the data logger. Some sensors require external signal conditioning. The performance of some sensors is enhanced with specialized input modules. The data logger, 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. CR300 series data acquisition system components 4

2. Wiring panel and terminal functions

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 data logger functions so studying it is a good way to get acquainted with the data logger. 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 l Power output l Power ground l Signal ground
2. Wiring panel and terminal functions 5
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
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
Period Average
Table 2-3: Analog output terminal functions
VX1 VX2
Switched Voltage
Excitation
Table 2-4: Voltage output terminal functions
C1 C2 SE1-4 VX1 VX2 P_SW SW12V
3.3 VDC
5 VDC
BAT +
2. Wiring panel and terminal functions 6
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
Communications 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.1 Power input

The data logger 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 data logger 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 data logger 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 lead-acid battery to the BAT terminals. See Power budgeting (p. 113) for more information.
2. Wiring panel and terminal functions 7
WARNING: Sustained input voltages in excess of 32 VDC on CHGor BAT terminals can damage the transient 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. 127) for more information.
Following is a list of CR300 series power input terminals and the respective power types supported.
l BAT terminals: Voltage input is 10 to 18 VDC. This connection uses the least current since
the internal data logger charging circuit is bypassed. If the voltage on the BAT terminals exceeds 19 VDC, power is shut off to certain parts of the data logger 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 battery at the current data logger 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 logger through the CHG terminals. The onboard charging regulator is designed for efficiently 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 data logger 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. 109).
2. Wiring panel and terminal functions 8

2.1.1 Power LED indicator

When the data logger 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 data logger can be used as a power source for communications devices, sensors and peripherals. Take precautions to prevent damage to these external devices due to over- or under­voltage conditions, and to minimize 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 data logger supply voltage. CRBasic instruction SW12() controls the SW12 terminal. See the CRBasic Editor help for detailed instruction information and program examples: https://help.campbellsci.com/crbasic/cr300/.
l VX terminals: supply precise output voltage used by analog sensors to generate high
resolution and accurate signals. In this case, these terminals are regularly used with resistive-bridge measurements (see Resistance measurements (p. 72) 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.
l C, SE 1-4, and P_SW terminals: 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. 192).
See also Power requirements (p. 184).
2. Wiring panel and terminal functions 9

2.3 Grounds

Proper grounding lends stability and protection to a data acquisition system. Grounding the data logger with its peripheral devices and sensors is critical in all applications. Proper grounding will ensure maximum ESD protection and measurement accuracy. It is the easiest and least expensive insurance against data loss, and often the most neglected. The following terminals are provided for connection of sensor and data logger grounds:
l Signal Ground ( ) - reference for single-ended analog inputs, excitation returns, and a
ground for sensor shield wires.
o
5 common terminals
l Power Ground (G) - return for 3.3 V, 5 V, 12 V, current loops, and digital sensors. Use of G
grounds for these outputs minimizes potentially large current flow through the analog­voltage-measurement section of the wiring panel, which can cause single-ended voltage measurement errors.
o
6 common terminals
l Earth Ground Lug ( ) - connection point for heavy-gage earth-ground wire. A good earth
connection is necessary to secure the ground potential of the data logger and shunt transients away from electronics. Campbell Scientific recommends 14 AWG wire, minimum.
NOTE: Several ground wires can be connected to the same ground terminal.
A good earth (chassis) ground will minimize damage to the data logger and sensors by providing a low-resistance path around the system to a point of low potential. Campbell Scientific recommends that all data loggers be earth grounded. All components of the system (data loggers, sensors, external power supplies, mounts, housings) should be referenced to one common earth ground.
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,
2. Wiring panel and terminal functions 10
also ground the system through the building plumbing, or use another verified connection to earth ground.
See also:
l Ground loops (p. 133) l Minimizing ground potential differences (p. 139)

2.4 Communications ports

The data logger is equipped with ports that allow communications with other devices and networks, 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 data loggers
Campbell Scientific data logger communications ports include:
l RS-232 l USB Device l Ethernet l C terminals

2.4.1 USB device port

One USB device port supports communicating with a computer through data logger support software or through virtual Ethernet (RNDIS), and provides 5 VDC power to the data logger (powering through the USB port has limitations - details are available in the specifications). The data logger USB device 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

The RJ45 10/100 Ethernet port is used for IP communications.(CR310 only.)
2. Wiring panel and terminal functions 11

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 specific terminals. This is shown in the data logger 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 configured 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. 98).
See also Communications specifications (p. 193).

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. 17).
One nine-pin DCE port, labeled RS-232, normally is used to communicate with a computer running data logger 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.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 data logger support software because it sends information as part of the protocol that lets the data logger know it can shut down the port.
2. Wiring panel and terminal functions 12
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. See the CRBasic Editor help for detailed instruction information and program examples:
https://help.campbellsci.com/crbasic/cr300/.
When the data logger 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.
See also Wiring panel and terminal functions (p. 5).

2.5 Programmable logic control

The data logger 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 provisions for simple on/off control. Control modules and relay drivers are available to expand and augment data logger 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 the CRBasic Editor help for detailed instruction information and program examples: https://help.campbellsci.com/crbasic/cr300/. 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.
l VX terminals can be set low or high using the PortSet() or SWVX() instruction. For
more information on these instructions, see the CRBasic help.
l SW12 terminals can be set low (0 V) or high (12 V) using the SW12() instruction (see the
CRBasic help for more information).
2. Wiring panel and terminal functions 13
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 connect its power wire to a data logger 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 functions 14

3. Setting up the CR300 series

The basic steps for setting up your data logger to take measurements and store data are included in the following sections:
l Setting up communications with the data logger (p. 16) l Virtual Ethernet over USB (RNDIS) (p. 19) l Ethernet communications option (p. 21) l Wi-Fi communications option (p. 25) l Cellular communications option (p. 29) l Radio communications option (p. 42) l Testing communications with EZSetup (p. 50) l Creating a Short Cut data logger program (p. 52)
3. Setting up the CR300 series 15

4. Setting up communications with the data logger

The first step in setting up and communicating with your data logger is to configure your connection. Communications peripherals, data loggers, and software must all be configured for communications. Additional information is found in your specific peripheral manual, and the data logger support software manual and help.
The default settings for the data logger allow it to communicate with a computer via USB, RS­232, or Ethernet (on CR310 models). For other communications methods or more complex applications, some settings may need adjustment. Settings can be changed through Device Configuration Utility or through data logger 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. 17) l Virtual Ethernet over USB (RNDIS) (p. 19) l Ethernet communications option (p. 21) (CR310 models only) l Wi-Fi communications option (p. 25) (WIFI models only) l Cellular communications option (p. 29) (CELLmodels only) l Radio communications option (p. 42) (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 data logger networks, use Network Planner. For more information on using the Network Planner, watch a video at https://www.campbellsci.com/videos/loggernet-software-
network-planner .
4. Setting up communications with the data logger 16

4. 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 data logger. Use the following
instructions or watch the Quickstart videos at https://www.campbellsci.com.au/videos .
Follow these steps to get started. These settings can be revisited using the data logger support software Edit Datalogger Setup option .
1. Using data logger support software, launch the EZSetup Wizard.
l
LoggerNet users, click Setup , click the View menu to ensure you are in the EZ (Simplified) view, then click Add Datalogger.
l
PC400 and PC200W users, click Add Datalogger .
2. Click Next.
3. Select your data logger from the list, type a name for your data logger (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 data logger, click Install, and follow the prompts to install the USBdrivers.
6. Plug the data logger 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 power source is necessary to power cellular functions of CR300-CELL models. A 12V battery will be needed for field deployment. If using RS-232, external power must be provided to the data logger.
NOTE: The Power LED on the data logger indicates the program and power state. Because the data logger 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 data logger.
4. USB or RS-232 communications 17
Loading...
+ 228 hidden pages