How it Works
Campbell Scientific
Loading...
CR300
User Manual
258 pgs4.63 Mb0
User Manual
24 pgs1.79 Mb0
Table of contents
Loading...

Campbell Scientific CR300 User Manual

Download
Page 1
Revision: 07/10/2020
Copyright © 2000 – 2020
Campbell Scientific, Inc.
Page 2
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
Page 3
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
Page 4
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
Page 5
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
Page 6
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
Page 7
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
Page 8
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
Page 9
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
Page 10
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
Page 11
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
Page 12
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
Page 13
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
Page 14

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
Page 15
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
Page 16

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
Page 17
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
Page 18

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
Page 19
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
Page 20
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
Page 21
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
Page 22

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
Page 23

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
Page 24
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
Page 25

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
Page 26
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
Page 27
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
Page 28

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
Page 29

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
Page 30

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
Page 31
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 data logger. 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 data loggers 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 data logger support software to wait a certain amount of time before returning a communication failure error.
11. LoggerNet and PC400 users can set a Max Time On-Line to limit the amount of time the data logger remains connected. When the data logger 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 data logger.
12. Click Next.
13. By default, the data logger does not use a security code or a PakBus encryption key. Therefore, 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 Data logger
security (p. 104) for more information.
14. Click Next.
15. Review the 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 data logger clock, and send a program to the data logger. See Test the
connection (p. 40) for more information.
4. USB or RS-232 communications 18
Page 32

5. Virtual Ethernet over USB (RNDIS)

CR300 series dataloggers with OS version 6 or greater support RNDIS (virtual Ethernet over USB). This allows the data logger to communicate via TCP/IP over USB. Watch a video
https://www.campbellsci.com/videos/ethernet-over-usb or use the following instructions.
1. Supply power to the data logger. If connecting via USB for the first time, you must first install USB drivers by using Device Configuration Utility (select your data logger, 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.
NOTE: Ensure the data logger 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 data logger to your computer using a USB cable, then open Device Configuration Utility and select your data logger.
3. Select the communication port used to communicate with the data logger 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.
5. Virtual Ethernet over USB (RNDIS) 19
Page 33
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 data loggers in your network, more than one data logger may be returned. Ensure you select the correct data logger by verifying the data logger serial number or station name (if assigned).
7. A virtual IP address can be used to connect to the data logger using Device Configuration Utility or other computer software, or to view the data logger 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 data logger from others who have access to your network, we recommend that you set security. For more information, see Data logger security (p. 104).
NOTE: Ethernet over USB (RNDIS) is considered a direct communications connection. Therefore, it is a trusted connection and csipasswd does not apply.
5. Virtual Ethernet over USB (RNDIS) 20
Page 34

6. Ethernet communications option

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 data logger. If you already have the data logger IPinformation, you can skip these steps and go directly to Setting up Ethernet communications between the
data logger and computer (p. 22). Watch a video https://www.campbellsci.com/videos/datalogger-ethernet-configuration or use the following
instructions.

6.1 Configuring data logger Ethernet settings

1. Supply power to the data logger. If connecting via USB for the first time, you must first install USB drivers by using Device Configuration Utility (select your data logger, 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.
2. Connect an Ethernet cable to the 10/100 Ethernet port on the data logger. 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. 22).
3. Using data logger support software (LoggerNet, PC400, or PC200W), open Device Configuration Utility .
4. Select the CR300 Series data logger from the list
5. Select the port assigned to the data logger from the Communication Port list. If connecting via Ethernet, select Use IPConnection.
6. By default, this data logger does not use a PakBus encryption key; so, the PakBus Encryption Key box can be left blank. If this setting has been changed, enter the new code or key. See Data logger security (p. 104) for more information.
6. Ethernet communications option 21
Page 35
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 data logger. If there is no Ethernet connection, the data logger 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 data logger 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 data logger was not able to obtain an address from the DHCP server. Contact your network administrator for help.
11. Apply to save your changes.

6.2 Ethernet LEDs

When the data logger 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.

6.3 Setting up Ethernet communications between the data logger 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 data logger over
Ethernet. Watch a video https://www.campbellsci.com/videos/ezsetup-ethernet-connection or use the following instructions.
This procedure only needs to be followed once per data logger. However, these settings can be revised using the data logger support software Edit Datalogger Setup option .
6. Ethernet communications option 22
Page 36
1. Using data logger support software, open EZSetup.
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 Add Datalogger.
l
PC400 users, click Add Datalogger .
NOTE: PC200W does not support IP connections.
2. Click Next.
3. Select the CR300 Series from the list, enter a name for your station (for example, a site or project name), Next.
4. Select the IPPort connection type and click Next.
5. Type the data logger 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
communications option (p. 21)) 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:db8::1234:5678]:6785
6. The PakBus address must match the hardware settings for your data logger. The default PakBus address is1.
l Set an Extra Response Time if you want the data logger support software to wait a
certain 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 data logger remains connected. When the data logger is contacted, communications 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 data logger does not use a security code or a PakBus encryption key. Therefore 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 Data logger
security (p. 104). 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.
6. Ethernet communications option 23
Page 37
Setup is now complete, and the EZSetup Wizard allows you Finish or select Next. The Next steps take you through testing communications, setting the data logger clock, and sending a program to the data logger. See Testing communications with EZSetup (p. 50) for more information.
6. Ethernet communications option 24
Page 38

7. Wi-Fi communications option

By default, the CR300 series-WIFI is configured to host a Wi-Fi network. The LoggerLink 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.
See also Communications specifications (p. 193).
7.1 Configuring the data logger to host a Wi-Fi network
By default, the CR300-WIFI is configured to host a Wi-Fi network. If the settings have changed, you can follow these instructions to reconfigure it.
1. Ensure your CR300-WIFI is connected to an antenna and power.
2. Using Device Configuration Utility, connect to the data logger.
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 password in the Password box (recommended).
6. Apply your changes.
7. Wi-Fi communications option 25
Page 39

7.2 Connecting your computer to the data logger over Wi-Fi

1. Open the Wi-Fi network settings on your computer.
2. Select the Wi-Fi-network hosted by the data logger. The default name is CR300 followed by the serial number of the data logger. 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.

7.3 Setting up Wi-Fi communications between the data logger and the data logger 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.
7. Wi-Fi communications option 26
Page 40
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 data logger IPaddress created when the CR300-WIFI creates a network.
4. Click Next.
5. The PakBus address must match the hardware settings for your data logger. The default PakBus address is 1.
l Set an Extra Response Time if you want the data logger support software to wait a
certain 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 data logger remains
connected. When the data logger 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 data logger.
6. Click Next.
7. By default, the data logger does not use a security code or a PakBus encryption key. Therefore, 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 Data logger
security (p. 104) for more information.
8. Click Next.
9. Review the Communication Setup Summary. If you need to make changes, click the Previous 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 communications, set the data logger clock, and send a program to the data logger. See Testing
communications with EZSetup (p. 50) for more information.

7.4 Configuring data loggers to join a Wi-Fi network

By default, the CR300-WIFI is configured to host a Wi-Fi network. To set it 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 data logger.
3. On the Deployment tab, click the Wi-Fi sub-tab.
4. In the Configuration list, select the Join a Network option.
7. Wi-Fi communications option 27
Page 41
5.
Next to the Network Name (SSID) box, click Browse to search for and select a Wi-Fi network.
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 data logger via DHCP. To do
this, make sure the IP Address is set to 0.0.0.0. Click Apply to save the configuration 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 this address is not static and may change. An IP address here of
169.254.###.### means the data logger was not able to obtain an address from the DHCP server. Contact your network administrator for help.
8. Apply your changes.
9. For each data logger you want to connect to network, you must follow the instruction in
Setting up Wi-Fi communications between the data logger and the data logger support software (p. 26), using the IP address used to configure that data logger (step 7 in this
instruction).

7.5 Wi-Fi LED indicator

When the data logger is powered, the Wi-Fi LED will turn on according to Wi-Fi communication states:
l Off: Insufficient power, Wi-Fi disabled, or data logger 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.
7. Wi-Fi communications option 28
Page 42

8. Cellular communications option

The CR300-CELL and CR310-CELL can be purchased with an integrated 4G LTE cellular module. This section refers to the CR300-CELL but it also applies to the CR310-CELL.
Use of the CR300-CELL requires a cellular line of service. The products compatible with Verizon, AT&T, T-Mobile, Vodafone, and Telstra are shown in the following table.
Product
CELL205
CELL210 4G LTE CAT-1
CELL215
CELL220
Cellular
protocol
4G LTE
with
automatic
3G fallback
4G LTE
with
automatic
3G and
2G fallback
4G LTE
with
automatic
3G fallback
Market Verizon AT&T T-Mobile Vodafone Telstra Other
North
America
United
✓
States
EMEA ✓ ✓
Australia
and New
Zealand
✓ ✓ ✓
✓ ✓
1
CELL225 4G LTE Japan ✓
1
More than 600 other providers are available worldwide through Campbell Scientific.

8.1 Pre-installation

8.1.1 Establish cellular service 30
8.1.2 Install the SIM card 30
8. Cellular communications option 29
Page 43
8.1.3 Konect PakBus Router setup 31

8.1.1 Establish cellular service

For better security, we recommend using Konect PakBus® Router with a private dynamic IP address. This method allows only incoming PakBus communication. No other incoming communication is supported. However, all forms of outbound communication from the data logger are supported, including but not limited to PakBus, email, and FTP.
Private dynamic IP addresses are standard with Telstra SIMs if no additional services have been provisioned on the account by a Telstra partner.
A public static IP address can also be used. This provides more incoming communication functionality, but is less secure and more vulnerable to unsolicited traffic.
8.1.1.1 Selecting a data service
Before installing a data logging system with telemetry, you will need a SIM card and data plan. For most applications, Telstra will offer the best coverage, especially in regional areas. Telstra and Optus coverage maps can be found on each provider's respective websites.
The CELL220 and CR300-CELL220 will work with standard data plans. No extra steps are necessary because of the complimentary Konect Pakbus Router service. A micro-SIM (3FF) is the correct size for use with the CELL220.

8.1.2 Install the SIM card

1. Remove the SIM card cover.
2. Note the location of the notched corner for correct alignment. The gold contact points of the SIM face down when inserting the SIM card as shown in the following figure. Gently slide the card into the slot until it stops and locks into place. To eject the SIM card, press it in slightly and release.
3. Replace the SIM card cover.
8. Cellular communications option 30
Page 44
FIGURE 8-1. SIM card installation

8.1.3 Konect PakBus Router setup

8.1.3.1 Get started
You will need the Konect PakBus Router redemption code that came on a card with the CR300­CELL.
Open a web browser and go to www.konectgds.com.
First-time users need to create a free account. After you submit your information, you will receive two emails up to five minutes apart. One email will contain a Passport ID and the other your Password. If emails are not received, check your email junk folder.
8. Cellular communications option 31
Page 45
8.1.3.2 Set up Konect PakBus Router
1. Sign in to www.konectgds.com using your Passport ID and Password found in the two received emails. Once logged in, you will be at the Welcome page.
2.
Click Devices and services on the command bar to the left and select Redeem PakBus Router Code. Enter your complimentary Router Code found on the included card with your cellular-enabled device and click Submit.
3. The next screen shows the assigned DNS address and Port for the router. Enter a TCP Password and select a unique PakBus Address for your data logger.
TIP: Make note of this information; it will be required for data logger configuration as well as LoggerNet setup. Please note your DNS, Port, TCP Password and PakBus address; you will need them later.
8. Cellular communications option 32
Page 46

8.2 Installation

8.2.1 Modules using Konect PakBus Router (private dynamic IP) 33
8.2.2 Modules using a public static IP 37

8.2.1 Modules using Konect PakBus Router (private dynamic IP)

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.1.1 Configure data logger
1. Connect the cellular antenna, if it is not already connected. When using a MIMO antenna with multiple cellular connections, connect the primary cable to Cellular and the secondary to Diversity. If the cables are not marked in this way, they can be connected to either antennna port.
2. Connect to your data logger by using Device Configuration Utility.
8. Cellular communications option 33
Page 47
3. On the Datalogger tab, change the data logger PakBus Address and PakBus/TCP Password to match the values entered in the Konect PakBus Router setup.The PakBus/TCP Password will make the data logger authenticate any incoming or outgoing PakBus/TCP connection.
4. On the Network Services tab in the PakBus/TCP Client field, enter the DNS address and Port number noted during the Konect PakBus Router setup.
5. (Optional) If your cellular carrier requires user name and password authentication, on the Settings Editor > Cellular tab, set PDP Authentication Type, PPP Authentication Username and PPP Authentication Password.
6. On the Cellular tab, enter the APN provided by your cellular provider. For standard Telstra SIMs, this will be telstra.internet.
7. Click Apply to save the changes. Verify the settings in the summary window. (Recommended) Save a copy of the settings to a file on the computer. Click OK.
8. Click Connect to reconnect in the Device Configuration Utility.
9. Go to the Settings Editor > Network Services. Set Maximum TCP Segment Size to 1000 for compatibility with all cellular networks.
8. Cellular communications option 34
Page 48
10. Click Apply to save the changes. Verify the settings in the summary window. (Recommended) Save a copy of the settings to a file on the computer. Click OK.
11. Click Disconnect and close Device Configuration Utility.
8.2.1.2 Set up LoggerNet
The LoggerNet Network Map is configured from the LoggerNet Setup screen.
NOTE: Setup has two options, EZ (simplified) and Standard. Click on the View menu at the top of the Setup screen, and select Standard view.
From the LoggerNet toolbar, click Main > Setup and configure the Network Map as described in the following steps:
1. Select Add Root > IPPort.
2. Select PakBusPort and pbRouter for PakBus data loggers such as the CR6 or CR1000X.
NOTE: PakBus data loggers include the following models:GRANITE-series, CR6, CR3000, CR1000X, CR800-series, CR300-series, CR1000, and CR200(X)-series.
3. Add a data logger to the pbRouter.
4. From the Entire Network, on the left side, select the IPPort. Enter the Konect PakBus Router DNS address and port number as noted in the Konect PakBus Router setup (Set up Konect
PakBus Router (p. 32)). Enter them into the Internet IP Address field in the format DNS:Port
with a colon separating DNS and Port. For example, axanar.konectgds.com:pppp where pppp is the port number.
8. Cellular communications option 35
Page 49
5. Leave the default settings for the PakBusPort. PakBus Port Always Open should not be checked. In the TCP Password field enter the TCP Password; this must match the value entered in the Konect PakBus Router setup and LoggerNet setup.
6. Select the pbRouter in the Network Map and set the PakBus Address to 4070.
7. Select the data logger in the Network Map and set the PakBus Address to match that of the data logger (default address in the data logger is 1). If a PakBus Encryption Key was entered during data logger setup, also enter it here. Click Apply to save the changes.
8. Cellular communications option 36
Page 50
8.2.1.3 Test the connection
Use the Connect screen to test the connection. Click on the appropriate station and click Connect to initiate a call to the data logger. The data logger must have 12 V power.
TIP: The connection time is subject to many external factors. It is often less than 30 seconds but could be up to 15 minutes. Be patient.
If the connection is successful, the connectors at the bottom of the screen will come together and clock information from the data logger will be displayed in the Station Date/Time field. If the connection fails, a Communications Failure message will be displayed.

8.2.2 Modules using a public static IP

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.2.2.1 Configure data logger
1. Connect the cellular antenna, if it is not already connected. When using a MIMO antenna with multiple cellular connections, connect the primary cable to Cellular and the secondary to Diversity. If the cables are not marked in this way, they can be connected to either antennna port.
2. Connect to your data logger by using Device Configuration Utility.
3. (Optional) If your cellular carrier requires user name and password authentication, on the Settings Editor > Cellular tab, set PDP Authentication Type, PPP Authentication Username and PPP Authentication Password.
8. Cellular communications option 37
Page 51
4. On the Cellular tab, enter the APN provided by your cellular provider.
5. (Optional) By default, the CR300-CELL will accept incoming communications from any IP address. This can be a security risk. You may specify up to four IP addresses, with wild cards, to limit connections to only those trusted sources. Use an asterisk (*) as a wild card. For example, a setting of 166.22.*.* would allow connections from devices that have IP addresses starting with 166.22. Both IPv4 and IPv6 addresses are supported.
CAUTION: Only set a Trusted IP address if you are familiar with their use. Consult your IT department or Campbell Scientific for assistance.
NOTE: This setting does not affect outbound connections, only incoming connections.
In the Device Configuration Utility go to the Settings Editor then Network Services. Next to the Trusted Hosts field, click Edit and Add your trusted IP addresses, one at a time.
6. Click Apply to save the changes.
8.2.2.2 Set up LoggerNet
The LoggerNet Network Map is configured from the LoggerNet Setup screen.
8. Cellular communications option 38
Page 52
NOTE: Setup has two options, EZ (simplified) and Standard. Click on the View menu at the top of the Setup screen, and select Standard view.
From the LoggerNet toolbar, click Main > Setup and configure the Network Map as described in the following steps:
1. Select Add Root > IPPort.
2. Select PakBusPort
3. Add a data logger to the PakBusPort.
4. Select the IPPort in the Network Map. Enter the CR300-CELL IP address and port number. The IP address and port number are input in the Internet IP Address field separated by a colon. Preceding zeros are not entered in the Internet IP Address (for example,
070.218.074.247 is entered as 70.218.74.247). The default port number is 6785.
5. For PakBus data loggers, leave the default settings for the PakBusPort. PakBus Port Always Open should not be checked. If used, enter the TCP Password.
8. Cellular communications option 39
Page 53
6. For PakBus data loggers, select the data logger in the Network Map and set the PakBus Address to match that of the data logger (default address in the data logger is 1). If a PakBus Encryption Key was entered during data logger setup, also enter it here. Click Apply to save the changes.
8.2.2.3 Test the connection
Use the Connect screen to test the connection. Click on the appropriate station and click Connect to initiate a call to the data logger. The data logger must have 12 V power.
TIP: The connection time is subject to many external factors. It is often less than 30 seconds but could be up to 15 minutes. Be patient.
If the connection is successful, the connectors at the bottom of the screen will come together and clock information from the data logger will be displayed in the Station Date/Time field. If the connection fails, a Communications Failure message will be displayed.
8. Cellular communications option 40
Page 54

8.3 Cellular (TX/RX) LED Indicator

When the data logger is powered, the cellular LED will turn on according to cellular modem communications 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
provider.
l Quick Flashing (approximately 1 second duration): Indicates successful network
registration.
l Flashing: Flashes with network activity.

8.4 Signal strength

Signal strength may indicate the quality of connection to a cellular tower. For 3G networks, this is reported as RSSl (Received Signal Strength Indicator). For 4G, it is RSRP (Reference Signal Received Power).
Signal strength units are –dBm; –70 is a stronger signal than –100.
Table 8-1: Signal strength
RSSI (3G)
RSRP (4G)
Quality estimate
dBm
dBm
Excellent -70 or greater -90 or greater
Good -71 to -85 -91 to -105
Fair -86 to -100 -106 to -115
Poor less than -100 less than -115
Because signal strength can vary due to multipath, interference, or other environmental effects, it may not give a true indication of communications performance or range. However, it can be useful for activities such as:
l determining the optimal direction to aim a Yagi antenna l determining the effects of antenna height and location l trying alternate Yagi antenna (reflective) paths l seeing the effect of vegetation and weather over time
8. Cellular communications option 41
Page 55

9. Radio communications option

CR300 series-RF data loggers 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 interference 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 independent radio represents each of the RF407, RF412, RF422, and RF427 models, unless otherwise noted.
9. Radio communications option 42
Page 56

9.1 Configuration options

The most frequently used configurations with the RF-series data logger and RF-series radio include the following:
See also RF radio option specifications (p. 194).

9.2 RF407-Series radio communications with one or more data loggers

To configure an RF407-series radio to communicate with the data logger, you must complete the following steps (instruction follows):
l Ensure your data logger 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 data loggers, you will have to assign unique PakBus
addresses to each data logger using Device Configuration Utility. (Connect to each data logger, set the PakBus Address on the Deployment | Datalogger tab.)
l Use data logger support software to set up communications between the RF407-series
radio and the data loggers.
9. Radio communications option 43
Page 57
NOTE: This procedure assumes the RF407 series devices are using factory default settings.

9.2.1 Configuring the RF407-Series radio

Configure the RF407-Series radio connected to the computer (see image in Configuration
options (p. 43) 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 Configuration 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 computer 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 previous step.
9.2.2 Setting up communications between the RF407­Series data logger and the computer
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 instructions). Follow these instructions multiple times to set up multiple data loggers. In this case, each data logger must be given a unique PakBus address (see PakBus communications (p. 97) for more information). For more complicated networks, it is recommended that you use Network Planner.
1. Supply 12 VDC power to the data logger.
2. Ensure the data logger antenna is connected.
3. Using data logger support software, launch the EZSetup Wizard and add the data logger.
l
PC200W and PC400 users, click Add Datalogger .
l
LoggerNet users, click Setup , click the View menu to ensure you are in the EZ (Simplified) view, then click Add Datalogger .
4. Click Next.
9. Radio communications option 44
Page 58
5. Select the CR300Series data logger from the list, type a name for your data logger (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 data logger link is not indicated in the LoggerNet Setup Standard View.)
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 active 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 data logger. The default PakBus Address is 1.
10. Click Next.
11. By default, the data logger does not use a security code or a PakBus encryption key. Therefore, 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 Data logger
security (p. 104) for more information.
12. Click Next.
13. Review the Communication Setup Summary. If you need to make changes, click the Previous 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 data logger clock, and send a program to the data logger. See Testing
communications with EZSetup (p. 50) for more information.
If you experience network communications problems, see Troubleshooting Radio
Communications (p. 125) for assistance.
9. Radio communications option 45
Page 59

9.3 RF407-Series radio communications with multiple data loggers using one data logger 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 data loggers through a router, you must complete the following steps (instruction follows):
l Ensure your data loggers and RF407-series radios are each connected to an antenna and
power.
l Configure your connection to the RF407-series devices using Device Configuration Utility. l Assign unique PakBus addresses to each data logger using Device Configuration Utility.
(Connect to each data logger, and set the PakBus Address on the Deployment | Datalogger tab.)
l Configure the data logger acting as a router. l Use data logger support software to set up communications between the computer and the
data loggers.

9.3.1 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.
2. If connecting via USB for the first time, you must first install USBdrivers using Device Configuration 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.
9. Radio communications option 46
Page 60
4. On the Main tab, set the Active Interface to USB or RS-232 (depending on how your computer 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 previous step.

9.3.2 Configuring the data logger acting as a router

1. Supply power to the data logger. If connecting via USB for the first time, you must first install USB drivers by using Device Configuration Utility (select your data logger, 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 data logger that will serve as a router.
3. On the Deployment > Datalogger tab, assign a unique PakBus Address (see PakBus
communications (p. 97) 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 data loggers in the network to be discovered).
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) data loggers in the network (for example, 90 seconds).
8. Click the Advanced sub-tab and set Is Router to True.
9. Apply your changes.
9.3.2.1 Adding routing data logger to LoggerNet network
1.
Using LoggerNet, click Setup and click the View menu to ensure you are in the Standard view.
9. Radio communications option 47
Page 61
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 communication 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 data loggers 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 data logger (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 data logger a descriptive name.
12. Apply your changes.
9.3.2.2 Adding leaf data loggers 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 data logger in the Entire Network pane on the left side of the window and select CR300Series.
2. With the newly added data logger selected in the Entire Network pane, set the PakBus Address to the address that was assigned to the leaf data logger in Device Configuration Utility.
3. Click Rename. Enter a descriptive name for the data logger.
4. Apply your changes.
5. Repeat these steps for each leaf data logger in the network.
If you experience problems with network communications, see Troubleshooting Radio
Communications (p. 125) for assistance.
9. Radio communications option 48
Page 62

9.3.3 Using additional communications methods

Using similar instructions, a RF407-series data logger can be used in a system with additional communication methods. For example, in the following image, the router RF407-series data logger communicates with LoggerNet through an RV50 cellular modem connected to RF407­series data logger using the RS-232 port. The router RF407-series data logger communicates with the leaf RF407-series data loggers over RF.
9. Radio communications option 49
Page 63

10. Testing communications with EZSetup

1. Using data logger support software EZSetup, access the Communication Test window. This window is accessed during EZ Setup (see USB or RS-232 communications (p. 17) for more information). Alternatively, you can double-click a data logger from the station list to open the EZ Setup Wizard and access the Communication Test step from the left side of the window.
2. Ensure the data logger 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. 117).
3. With a successful connection, the Datalogger Clock window displays the time for both the data logger and the computer.
l The Adjusted Server Date/Time displays the current reading of the clock for the
computer or server running your data logger support software. If the Datalogger Date/Time and Adjusted Server Date/Time don't match, you can set the data logger
10. Testing communications with EZSetup 50
Page 64
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
computer time when setting the data logger clock. This offset will allow you to set the clock for a data logger 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 data logger ships with a default QuickStart program. If the data logger does not have a program, you can choose to send one by clicking Select and Send Program. Click Next.
6. LoggerNet only - Use the following instructions or watch the Scheduled/Automatic Data
Collection video :
l The Datalogger Table Output Files window displays the data tables available to be
collected from the data logger and the output file name. By default, all data tables set up in the data logger program will be included for collection. Make note of the Output File Name and location. Click Next.
l Check Scheduled Collection Enabled to have LoggerNet automatically collect data
from the data logger on the Collection Interval entered. When the Base Date and Time are in the past, scheduled collection will begin immediately after finishing the EZSetup wizard. Click Next twice.
7. Click Finish.

10.1 Making the software connection

Once you have configured your hardware connection (see Setting up communications with the
data logger (p. 16), your data logger and computer can communicate. You'll use the Connect
screen to send a program, set the clock, view real-time data, and manually collect data.
l
LoggerNet users, select Main and Connect on the LoggerNet toolbar, select the data logger from the Stations list, then Connect .
l
PC400 and PC200W users, select the data logger from the list and click Connect .
To disconnect, click Disconnect .
For more information see the Connect Window Tutorial .
10. Testing communications with EZSetup 51
Page 65

11. Creating a Short Cut data logger program

You must provide a program for the data logger in order for it to make measurements, store data, or control external devices. There are several ways to write a program. The simplest is to use the program generator called Short Cut. For more complex programming the CRBasic editor is used. The program file may use the extension .CR300, .CRB or .DLD.
Data logger programs are executed on a precise schedule termed the scan interval, based on the data logger internal clock.
Measurements are first stored in temporary memory called variables in the Public Table. Variables are usually overwritten each scan. Periodically, generally on a time interval, the data logger stores data in tables. The Data Tables are later copied to a computer using your data logger support software.
Use the Short Cut software to generate a program for your data logger. ShortCut is included with your data logger support software.
This section will guide you through programming a CR300 series data logger to measure the voltage of the data logger power supply, the internal temperature of the data logger, and a thermocouple. With minor changes, these steps can apply to other measurements. Use the
following instructions or watch the Quickstart part 3 video .
1. Using data logger support software, launch ShortCut.
l
LoggerNet users, click Program then ShortCut .
l
PC400 and PC200W users, click ShortCut .
2. Click Create New Program.
3. Select CR300 Series 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 Rejection 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.
11. Creating a Short Cut data logger program 52
Page 66
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
display. 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. For the example program, expand the Sensors/Temperature folder and double-click Type T Thermocouple.
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. For the example program, accept the default options:
l 1 Type TTCsensor l Temp_C as the Temperature label, and set the units to Deg C l PTemp_C as the Reference Temperature Measurement.
7. Click OK.
8. Click Wiring Diagram on the left side of the window to see how to wire the sensor to the data logger. With the power disconnected from the data logger, 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, then click Next at the bottom of the window.
10. Type 1 in the How often should the data logger measure its sensor(s)? box.
11. 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). For the example program, only one table is needed. Click the Table2 tab and click Delete Table.
12. In the Table Name box, type a name for the table. For example:OneMin.
13. Select a Data Output Storage Interval. For example: to 1 minute.
14. Click Next.
15. 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
11. Creating a Short Cut data logger program 53
Page 67
for Output list. For the example program, select BattV and click the Average button to add it to the Selected Measurements for Output list. Repeat this procedure for PTemp_C and Temp_C.
16. Click Finish and give the program a meaningful name such as a site identifier. Click Save.
17. If LoggerNet or other data logger support software is running on your computer, and the data logger is connected to the computer (see Making the software connection (p. 51) for more information), you can choose to send the program. Generally it is best to collect data first; so, we recommend sending the program using the instructions in Sending a program
to the data logger (p. 54).
TIP: It is good practice is to always retrieve data from the data logger before sending a program; otherwise, data may be lost. See Collecting data (p. 57) 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 data logger.
NOTE: Once a Short Cut generated program has been edited with CRBasic Editor, it can no longer be modified with ShortCut.

11.1 Sending a program to the data logger

TIP: It is good practice is to always retrieve data from the data logger before sending a program; otherwise, data may be lost. See Collecting data (p. 57) for detailed instruction.
11. Creating a Short Cut data logger program 54
Page 68
Some methods of sending a program give the option to retain data when 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 Data output interval or offset l Number of fields per record
l Number of bytes per field l Field type, size, name, or position l Number of records in table
Use the following instructions or watch the Quickstart part 4 video .
1. Connect the data logger to your computer (see Making the software connection (p. 51) for more information).
2. Using your data logger 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 program, select it, and click Open. For example: navigate to C:\Campbellsci\SCWin and select MyTemperature.CR300.
4. Confirm that you would like to proceed and erase all data tables saved on the data logger. The program will send and compile.
5. Review the Compile Results window for errors, messages and warnings.
6. Click Details, select the Table Fill Times tab. Ensure that the times shown are expected for your application. Click OK.
After sending a program, it is a good idea to monitor the Public Table to make sure sensors are taking good measurements. See Working with data (p. 56) for more information.
11. Creating a Short Cut data logger program 55
Page 69

12. Working with data

12.1 Default data tables

By default, the data logger 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 data logger program, and updated at the scan
interval set within the data logger program, It shows measurement and calculation results as they are made.
l The Status table includes information about the health of the data logger 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. 57).
Use these instructions or follow the Connect Window tutorial to monitor real-time data.
LoggerNet users, select the Main category and Connect on the LoggerNet toolbar, select the data logger from the Stations list, then click Connect . Once connected, select a table to view
using the Table Monitor.
PC400 and PC200Wusers, click Connect , then Monitor Data. When this tab is first opened for a data logger, 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.
12. Working with data 56
Page 70

12.2 Collecting data

The data logger writes to data tables based on intervals and conditions set in the CRBasic program (see Creating data tables in a program (p. 64) 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 and still remains on the data logger. Collections may be done manually, or automatically through scheduled
collections set in LoggerNet Setup. Use these instruction or follow the Collect Data Tutorial .

12.2.1 Collecting data using LoggerNet

1.
From the LoggerNet toolbar, click Main and Connect , select the data logger from the Stations list, then 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. See Viewing historic data (p. 58)

12.2.2 Collecting data using PC200W or PC400

1.
Click Connect on the main PC200W or PC400 window.
2. Go to the Collect Data tab.
12. Working with data 57
Page 71
3. Select an option for What to Collect. Either option creates a new file if one does not already exist.
l New data from data logger (Append to data files): Collects only the data in the
selected 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 data logger (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 output tables set up in the data logger 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. See Viewing historic data (p. 58)

12.3 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 the View Data
Tutorial .
Once the data logger has had enough time to store multiple records, you should collect and review the data.
1. To view the most recent data, connect the data logger to your computer and collect your data (see Collecting data (p. 57) for more information).
2. Open View Pro:
l
LoggerNet users click Data then 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 data logger software application]). For example: navigate to the C:\Campbellsci\LoggerNet folder and select OneMin.dat.

12.4 Data types and formats

Data takes different formats as it is created and manipulated in the data logger, as it is displayed through software, and as it is retrieved to a computer file. It is important to understand the different data types, formats and ranges, and where they are used.
12. Working with data 58
Page 72
Table 12-1: Data types, ranges and resolutions
Data type Description Range Resolution Where used
Float
IEEE four-byte
floating point
four-byte
Long
signed integer
four-byte
Boolean
signed integer
+/–1.8 *10^–38 to
+/–3.4 *10^38
–2,147,483,648 to
+2,147,483,647
–1, 0
24 bits
variables
(about 7 digits)
1 bit variables, output
True (–1) or
False ( 0)
variables,
sample output
variables,
String ASCII String
sample output
FP2
Campbell Scientific
–7999 to +7999
two-byte floating point
13 bits
output
(about 4 digits)
NSEC eight-byte time stamp nanoseconds variables, output

12.4.1 Variables

In CRBasic, the declaration of variables (via the DIM or the PUBLIC statement) allows an optional type descriptor As that specifies the data type. The data types are Float, Long,
Boolean, and String. The default type is Float.
Example variables declared with optional data types
Public PTemp As Float, Batt_volt Public Counter As Long Public SiteName As String * 24
As Float specifies the default data type. If no data type is explicitly specified with the As
statement, then Float is assumed. Measurement variables are stored and calculations are performed internally in IEEE 4 byte floating point with some operations calculated in double precision. A good rule of thumb is that resolution will be better than 1 in the seventh digit.
As Long specifies the variable as a 32 bit integer. There are two possible reasons a user would
do this: (1) speed, since the CR300 series Operating System can do math on integers faster than with Floats, and (2) resolution, since the Long has 31 bits compared to the 24 bits in the
Float. A good application of the As Long declaration is a counter that is expected to get very
large.
As Boolean specifies the variable as a 4 byte Boolean. Boolean variables are typically used for
flags and to represent conditions or hardware that have only 2 states (e.g., On/Off, High/Low). A Boolean variable uses the same 32 bit long integer format as a Long but can set to only one of two values: True, which is represented as –1, and false, which is represented with 0. When a
12. Working with data 59
Page 73
Float or Long integer is converted to a Boolean, zero is False (0), any non-zero value will set
the Boolean to True (-1). The Boolean data type allows application software to display it as an On/Off, True/False, Red/Blue, etc.
The CR300 series uses –1 rather than some other non-zero number because the AND and OR operators are the same for logical statements and binary bitwise comparisons. The number -1 is expressed in binary with all bits equal to 1, the number 0 has all bits equal to 0. When –1 is anded with any other number the result is the other number, ensuring that if the other number is non­zero (true), the result will be non-zero.
As String * size specifies the variable as a string of ASCII characters, NULL terminated,
with an optional size specifying the maximum number of characters in the string. A string is convenient in handling serial sensors, dial strings, text messages, etc. When size is not specified, a default of 24 characters will be used (23 usable bytes and 1 terminating byte).
As a special case, a string can be declared As String * 1. This allows the efficient storage of a single character. The string will take up 4 bytes in memory and when stored in a data table, but it will hold only one character.

12.4.2 Data storage

Data can be stored in either IEEE4 or FP2 formats. The format is selected in the program instruction that outputs the data, i.e. minimum, maximum, etc.
While Float (IEEE 4 byte floating point) is used for variables and internal calculations, FP2 is adequate for most stored data. Campbell Scientific 2 byte floating point (FP2)provides 3 or 4 significant digits of resolution, and requires half the memory space as IEEE4 (2 bytes per value vs 4).
Table 12-2: Resolution and range limits of FP2 data
Zero Minimum magnitude Maximum Magnitude
0.000 ±0.001 ±7999.
The resolution of FP2 is reduced to 3 significant digits when the first (left most) digit is 8 or greater. Thus, it may be necessary to use IEEE4 output or an offset to maintain the desired resolution of a measurement. For example, if water level is to be measured and output to the nearest 0.01 foot, the level must be less than 80 feet for FP2 output to display the 0.01 foot increment. If the water level is expected to range from 50 to 90 feet the data could either be output in IEEE4 or could be offset by 20 feet (transforming the range to 30 to 70 feet).
12. Working with data 60
Page 74
Table 12-3: FP2 decimal location
Absolute value Decimal location
0 – 7.999 X.XXX
8 – 79.99 XX.XX
80 – 799.9 XXX.X
800 – 7999. XXXX.
NOTE:
String and Boolean variables can be output with the Sample() instruction. Results of
Sampling a Boolean variable will be either -1 or 0 in the collected Data Table. A Boolean displays in the Numeric Monitor Public and Data Tables as true or false.

12.5 About data tables

A data table is essentially a file that resides in data logger memory (for information on data table storage, see Data memory (p. 66)). 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. 57)).
Table 12-4: 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
2019-03-08 14:24:00 0 13.68 21.84 20.71
2019-03-08 14:25:00 1 13.65 21.84 20.63
2019-03-08 14:26:00 2 13.66 21.84 20.63
2019-03-08 14:27:00 3 13.58 21.85 20.62
12. Working with data 61
Page 75
Table 12-4: 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
2019-03-08 14:28:00 4 13.64 21.85 20.52
2019-03-08 14:29:00 5 13.65 21.85 20.64

12.5.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 computer. Table definitions include the data logger type and OS version, name of the CRBasic program associated with the data, name of the data table (limited to 20 characters), and alphanumeric field names.
12.5.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:
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 - Data logger model. l 1142 - Data logger serial number. l CPU:MyTemperature.CR300 - Data logger program name. Changed by sending a new
program (see Sending a program to the data logger (p. 54) for more information).
l 1958 - Data logger program signature. Changed by revising a program or sending a new
program (see Sending a program to the data logger (p. 54) for more information).
l OneMin - Table name as declared in the running program (see Creating data tables in a
program (p. 64) for more information).
The second header row reports field names. Default field names are a combination of the variable names (or aliases) from which data is derived, and a three-letter suffix. The suffix is an abbreviation of the data process that outputs the data to storage. A list of these abbreviations follows in Data processing abbreviations (p. 63).
12. Working with data 62
Page 76
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 data logger program, will be represented by four field names: Values(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() instruction 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. 61).
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.
Table 12-5: Data processing abbreviations
Data processing name Abbreviation
Totalize
Average
Maximum
Minimum
Sample at Max or Min
Standard Deviation
Moment
Tot
Avg
Max
Min
SMM
Std
MMT
Sample No abbreviation
Histogram1
Histogram4D
FFT
Covariance
Hst
H4D
FFT
Cov
Level Crossing
WindVector
LCr
WVc
12. Working with data 63
Page 77
Table 12-5: Data processing abbreviations
Data processing name Abbreviation
Median
ET
Solar Radiation (from ET)
Time of Max
Time of Min
Med
ETsz
RSo
TMx
TMn
12.5.1.2 Data records
Subsequent rows are called data records. They include observed data and associated record keeping. 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 written. Therefore, in record number 3 in the previous Example data (p. 61), 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 2019-03-08 00:00:00 will contain the total rainfall beginning at 2019-03-07 00:00:01 and ending at 2019-03-08 00:00:00.

12.6 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 Short Cut data logger program (p. 52)). Data tables are created within the CRBasic data logger program using the DataTable()/EndTable instructions. They are placed after variable declarations and before the BeginProg instruction. Between DataTable() and EndTable() are instructions that define what data to store and under what conditions 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
See the CRBasic Editor help for detailed instruction information and program examples:
https://help.campbellsci.com/crbasic/cr300/.
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
12. Working with data 64
Page 78
allow your data logger to auto-allocate table size. With auto-allocation, the data logger 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. 118) for more information). An example of the Table Fill Times tab follows. For information on data table storage see Data memory (p. 66).
12. Working with data 65
Page 79

13. Data memory

The data logger includes three types of memory: RAM, Flash, and Serial Flash.

13.1 Data tables

Measurement data is primarily stored in data tables. Data is usually erased from this area when a program is sent to the data logger. 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 data logger uses those parameters to assign sectors in a way that maximizes the life of its memory. See the CRBasic Editor help for detailed instruction information and program examples: https://help.campbellsci.com/crbasic/cr300/.
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 data logger support software.
Data concerning the data logger memory are posted in the Status and DataTableInfo tables. For additional information on these tables, see Information tables and settings (advanced) (p. 150).
For additional information on data logger memory, visit the Campbell Scientific blog article,"How to Know when Your Datalogger Memory is Getting Full."

13.2 Flash memory

The data logger operating system is stored in a separate section of flash memory. To update the operating system, see Updating the operating system (p. 113).
Serial flash memory holds the CPU drive, web page, and data logger settings. Because flash memory has a limited number of write/erase cycles, care must be taken to avoid continuously writing to files on the CPU drive.
13. Data memory 66
Page 80

13.2.1 CPU drive

The serial flash memory CPU drive contains data logger 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 premature failure of serial flash memory. Internal chip manufacturers specify the flash technology 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 control.
See also Information tables and settings (advanced) (p. 150).
Also, see System specifications (p. 183) for information on data logger memory.
13. Data memory 67
Page 81

14. Measurements

14.1 Voltage measurements 68
14.2 Current-loop measurements 70
14.3 Resistance measurements 72
14.4 Period-averaging measurements 78
14.5 Pulse measurements 78
14.6 Vibrating wire measurements 84

14.1 Voltage measurements

Voltage measurements are made using an Analog-to-Digital Converter (ADC). A high­impedance Programmable-Gain Amplifier (PGA) 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. 138).
A voltage measurement proceeds as follows:
1. Set PGA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 output of 1000 mV. Sometimes, the low signal is simply sensor ground (0 mV). A single-ended measurement measures the high signal with reference to ground; the low signal is tied to
14. Measurements 68
Page 82
ground. A differential measurement measures the high signal with reference to the low signal. Each configuration has a purpose, but the differential configuration is usually preferred.
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 measurement
specifications (p. 187) for more information).
A set overhead reduces the chance of overrange. Overrange limits are available in the specifications. The data logger indicates a measurement overrange by returning a NAN for the measurement.
WARNING: Sustained voltages in excess of -6 V or +9 V (SE1, SE2), ±17 V (SE3 to SE6) applied to terminals configured for analog input will damage CR300 series circuitry.

14.1.1 Single-ended measurements

A single-ended measurement measures the difference in voltage between the terminal configured 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 information, see Wiring panel and terminal functions (p. 5). The single-ended configuration is used with the following CRBasic instructions:
l
VoltSE()
l
BrHalf()
l
BrHalf3W()
l
TCSE()
l
Therm107()
l
Therm108()
l
Therm109()
See the CRBasic Editor help for detailed instruction information and program examples:
https://help.campbellsci.com/crbasic/cr300/.

14.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 functions (p. 5). The differential configuration is used with the following CRBasic instructions:
l
VoltDiff()
l
BrFull()
14. Measurements 69
Page 83
l
BrFull6W()
l
BrHalf4W()
l
TCDiff()
For more information on voltage measurements, see Improving voltage measurement quality (p.
137) and Analog measurement specifications (p. 187).

14.2 Current-loop measurements

Terminals SE1 and SE2 can be configured to make analog current measurements using the
CurrentSE() 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.

14.2.1 Voltage Ranges for Current Measurements

The data logger 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.
14. Measurements 70
Page 84

14.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. 190).
Sensor Type Connection Example
2-wire transmitter using data logger power
2-wire transmitter using external power
3-wire transmitter using data logger power
14. Measurements 71
Page 85
Sensor Type Connection Example
3-wire transmitter using external power
4-wire transmitter using data logger power
4-wire transmitter using external power

14.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
14. Measurements 72
Page 86
analog 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 measurement specifications (p. 189).

14.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
See the CRBasic Editor help for detailed instruction information and program examples:
https://help.campbellsci.com/crbasic/cr300/.
Resistive-Bridge Type and
Circuit Diagram
Half Bridge
Three Wire Half Bridge
1
1,2
CRBasic Instruction and
Relational Formulas
Fundamental Relationship
CRBasic Instruction:
BrHalf()
Fundamental Relationship:
CRBasic Instruction:
BrHalf3W()
Fundamental Relationship:
14. Measurements 73
Page 87
Resistive-Bridge Type and
Circuit Diagram
CRBasic Instruction and
Relational Formulas
Fundamental Relationship
Four Wire Half Bridge
Full Bridge
1,2
1,2
CRBasic Instruction:
BrHalf4W()
Fundamental Relationship:
CRBasic Instruction:
BrFull()
Fundamental Relationship:
These relationships apply to
BrFull()
and BrFull6W()
Six Wire Full Bridge
1
CRBasic Instruction:
BrFull6W()
Fundamental Relationship:
1
Key: Vx= excitation voltage; V1, V2= sensor return voltages; Rf= fixed, bridge or completion resistor; Rs=
variable or sensing resistor.
2
Campbell Scientific offers terminal input modules to facilitate this measurement.
14. Measurements 74
Page 88
Offset voltage compensation applies to bridge measurements. RevDiff and MeasOff parameters are discussed in Minimizing offset voltages (p. 147). 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 '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

14.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 schematic. '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 Vrto negative.
14. Measurements 75
Page 89
Table 14-1: StrainCalc() configuration codes
BrConfig Code Configuration
Quarter-bridge strain gage:
1
Half-bridge strain gage. One gage parallel to strain, the other at 90° to strain:
2
Half-bridge strain gage. One gage parallel to +ɛ, the other parallel to -ɛ:
3
Full-bridge strain gage. Two gages parallel to +ɛ, the other two parallel to -ɛ:
4
14. Measurements 76
Page 90
Table 14-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 -νɛ
5
Full-bridge strain gage. Half the bridge has two gages parallel to +ɛ
and -νɛ , and the other half to -νɛ and +ɛ:
6
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.

14.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.
For accuracy specifications of ratiometric resistance measurements, see Resistance measurement
specifications (p. 189). Voltage measurement is variable V1or V2in resistance measurements.
Offset is the same as that for simple analog voltage measurements.
14. Measurements 77
Page 91
Assumptions that support the ratiometric-accuracy specification include:
l Data logger 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

14.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 data logger uses a high-frequency digital clock to measure time differences between signal transitions, whereas pulse-count measurements simply accumulate the number of counts. As a result, period-average measurements offer much better frequency resolution per measurement interval than pulse­count measurements. See also Pulse measurements (p. 78).
SE 1-4 terminals on the data logger are configurable for measuring the period of a signal.
See also Period-averaging measurement specifications (p. 190).
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 signal, even when the data logger is between program scans. In contrast, period-average measurements 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.

14.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 data logger 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
14. Measurements 78
Page 92
pulse count and period-average measurements are used to measure frequency-output sensors. For more information, see Period-averaging measurements (p. 78).
The data logger includes terminals that are configurable for pulse input as shown in the following image.
Table 14-2: Pulse input terminals and the input types they can measure
Input Type Pulse Input Terminal
C (all)
High-frequency
SE 1-4 P_SW
P_LL
Low-level AC
P_LL
C (all)
Switch-closure
P_SW
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 conditioners should be employed. Do not measure voltages greater than 20 V.
14. Measurements 79
Page 93
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 working with pulse measurements, see Pulse measurement tips (p. 83).
Output can be recorded as counts, frequency or a running average of frequency.
See also Pulse measurement specifications (p. 191).
See the CRBasic Editor help for detailed instruction information and program examples:
https://help.campbellsci.com/crbasic/cr300/.

14.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.
Measurement output options include the following:
l Counts l Frequency (Hz) l Running average
Rotating magnetic-pickup sensors commonly generate ac voltage ranging from millivolts at low­rotational speeds to several volts at high-rotational speeds.
CRBasic instruction: PulseCount(). See the CRBasic Editor help for detailed instruction information and program examples: https://help.campbellsci.com/crbasic/cr300/.
Low-level AC signals cannot be measured directly by C terminals. Peripheral terminal expansion modules, such as the Campbell Scientific LLAC4, are available for converting low-level AC signals to square-wave signals measurable by C terminals.
For more information, see Pulse measurement specifications (p. 191).

14.5.2 High-frequency measurements

High-frequency (square-wave) signals can be measured on terminals:
l P_LL, P_SW, SE 1-4 or C
Common sensors that output high-frequency pulses include:
l Photo-chopper anemometers l Flow meters
Measurement output optionss include counts, frequency in hertz, and running average.
l CRBasic instruction: PulseCount()
14. Measurements 80
Page 94

14.5.3 Switch-closure and open-collector measurements

Switch-closure and open-collector (also called current-sinking) signals can be measured on terminals:
l P_SW or C
Mechanical switch-closures have a tendency to bounce before solidly closing. Unless filtered, bounces can cause multiple counts per event. The data logger automatically filters bounce. Because of the filtering, the maximum switch-closure frequency is less than the maximum 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.
14.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(). See the CRBasic Editor help for detailed instruction
information and program examples: https://help.campbellsci.com/crbasic/cr300/.
Switch Closure on P Terminal Open Collector on P Terminal
14.5.3.2 C terminals
Switch-closure measurements on C terminals require a 100 kΩ pull-up resistor to 12 V. Switch­closure mode is a special case edge-count function that measures dry-contact switch-closures or open collectors. The operating system filters bounces.
14. Measurements 81
Page 95
l CRBasic instruction: PulseCount().
See alsoPower output specifications (p. 186).

14.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 data logger.
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 channels 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.
Counting 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 channel A leads channel B.
14. Measurements 82
Page 96
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. 191).

14.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. 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. See the CRBasic Editor help for detailed instruction information and program examples:
https://help.campbellsci.com/crbasic/cr300/.
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 instructions is helpful. See Pulse input terminals and the input types they can measure (p. 79).
14.5.5.1 Input filters and signal attenuation
Terminals configured for pulse input have internal filters that reduce electronic noise. The electronic 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. 191) for more information. The listed pulse measurement specifications account for attenuation due to input filtering.
14.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 interval 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.
14. Measurements 83
Page 97
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.

14.6 Vibrating wire measurements

The data logger 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.

14.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.
14. Measurements 84
Page 98

15. Communications protocols

Data loggers communicate with data logger support software, other Campbell Scientific data loggers, and other hardware and software using a number of protocols including PakBus, Modbus, DNP3, and TCP/IP. Several industry-specific protocols are also supported. See also
Communications specifications (p. 193).
15.1 General serial communications 86
15.2 Modbus communications 87
15.3 Internet Communications 96
15.4 DNP3 communications 97
15.5 PakBus communications 97
15.6 SDI-12 communications 98
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 transactions). See the CRBasic Editor help for detailed instruction information and program examples: https://help.campbellsci.com/crbasic/cr300/.
15. Communications protocols 85
Page 99
l Set the data logger to be a PakBus router only as needed. When the data logger 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. For more information, see the Device Configuration Settings Editor Information tables and settings (advanced) (p. 150).
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 Plannerwill set this appropriately when it is used. This is also set through the Beacon and Verify settings in the Settings Editor. For more information, see the Device Configuration Settings Editor Beacon() and Verify() settings.
For information on Designing a PakBus network using the Network Planner tool in LoggerNet, watch the following video:

15.1 General serial communications

The data logger 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.
CRBasic instructions for general serial communications include:
l
SerialOpen()
l
SerialClose()
l
SerialIn()
l
SerialInRecord()
l
SerialInBlock()
l
SerialOut()
l
SerialOutBlock()
See the CRBasic Editor help for detailed instruction information and program examples:
https://help.campbellsci.com/crbasic/cr300/.
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
15. Communications protocols 86
Page 100
protocol 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 (C1/C2) uses RS-232 logic levels, it is limited to 0 V (logic high) and 5 V (logic low) output. 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 converters 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.

15.2 Modbus communications

The data logger 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 networks. Data loggers can communicate using Modbus on all available communication ports. The data logger 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:
l
ModbusMaster()
l
ModbusSlave()
l
MoveBytes()
See the CRBasic Editor help for detailed instruction information and program examples:
https://help.campbellsci.com/crbasic/cr300/.
For additional information on Modbus, see:
l About Modbus (p. 88) 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 data logger 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.
15. Communications protocols 87
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use