Example Current Measurement Connections Ratiometric Resistance Measurements Resistive-Bridge Measurements and Voltage Excitation...

Transcription

1

2

3 Table of Contents DATA ACQUISITION SYSTEM COMPONENTS... 1 Sensors... 2 Supported Sensor Types... 2 The CR1000X Datalogger... 2 Components... 2 Operations... 3 Programs... 3 CR1000X Wiring Panel... 3 Power Input... 5 Power Output... 6 Grounds... 7 Communication Ports... 8 Programmable Logic Control SETTING UP THE DATALOGGER Setting up Communications with the Datalogger Configuring Settings to Communicate over USB or RS Configuring Settings to Communicate over Ethernet Testing Communication and Completing EZ Setup Connecting the Datalogger to a Computer Creating a Program in Short Cut Sending a Program to the Datalogger Sending a Program Using Datalogger Support Software Program Run Options WORKING WITH DATA Monitoring Data Collecting Data Collecting Data Using LoggerNet Collecting Data Using PC200W or PC400W Viewing Historic Data About Data Tables Table Definitions First Header Row Second Header Row Third Header Row Fourth Header Row Data Records Creating Data Tables in a Program Memory and Data Storage Memory Allocation CPU Drive SRAM USR Drive MicroSD (CRD: Drive) Storage Managing Memory via Powerup.ini MEASUREMENTS Voltage Measurements Single-Ended Measurements Differential Measurements Current Measurements... 30

4 Example Current Measurement Connections Ratiometric Resistance Measurements Resistive-Bridge Measurements and Voltage Excitation Strain Measurements Ac Excitation Accuracy for Ratiometric Resistance Measurements Thermocouple Measurements Period-Averaging Measurements Pulse Measurements Low-Level Ac Measurements High Frequency Measurements Switch-Closure and Open-Collector Measurements Edge Timing and Edge Counting Pulse Measurement Tips Vibrating Wire Measurements COMMUNICATION PROTOCOLS General Serial Communications Modbus Communications Internet Communications IP Address HTTPS DNP3 Communications PakBus Communications SDI-12 Communication SDI-12 Transparent Mode SDI-12 Programmed Mode/Recorder Mode Programming the Datalogger to Act as an SDI-12 Sensor SDI-12 Power Considerations Serial Peripheral Interface (SPI) and I2C MAINTAINING YOUR DATALOGGER Datalogger Calibration About Background Calibration Datalogger Security Security Codes Creating a.csipasswd File Datalogger Enclosures Internal Battery Internal Lithium Battery Specifications Replacing the Internal Battery Electrostatic Discharge and Lightning Protection Power Budgeting Updating the Operating System TIPS AND TROUBLESHOOTING Checking Station Status Viewing Station Status Watchdog Errors Results for Last Program Compiled Skipped Scans Skipped Records Variable Out of Bounds Battery Voltage Understanding NAN and INF Occurrences Time Keeping... 61

5 Clock Best Practices Time Stamps Avoiding Time Skew CRBasic Program Errors Program Does Not Compile Program Compiles but Does Not Run Correctly Resetting the Datalogger Processor Reset Program Send Reset Manual Data Table Reset Formatting Drives Full Memory Reset Troubleshooting Power Supplies Minimizing Ground Loop Errors Improving Voltage Measurement Quality Deciding Between Single-Ended or Differential Measurements Minimizing Ground Potential Differences Detecting Open Inputs Minimizing Power-Related Artifacts Minimizing Settling Errors Factors Affecting Accuracy Minimizing Offset Voltages File System Error Codes File Name and Resource Errors Background Calibration Errors SPECIFICATIONS System Specifications Physical Specifications Power Requirements Ground Specifications Power Output Specifications Analog Specifications Voltage Measurements Ratiometric-Resistance Measurements Specifications Period Averaging Specifications Current Measurements Specifications Pulse Counting Specifications Switch Closure Input High-Frequency Input Low-Level Ac Input Digital I/O Specifications Switch Closure Input High-Frequency Input Edge Timing Communications Specifications SUPPORT Product Assistance Precautions Warranty Acknowledgements GLOSSARY INDEX

6

7

8 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 concept of a data acquisition system is illustrated in the following figure. Following is a list of typical data acquisition system components: Sensors - Electronic sensors convert the state of a phenomenon to an electrical signal (see "Sensors" on page 2 for more information). Datalogger - The datalogger 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 are stored in memory to await transfer to a computer by way of an external storage device or a communication link. Data Retrieval and Communications - Data are copied (not moved) from the datalogger, usually to a computer, by one or more methods using datalogger support software. Most communication options are bi-directional, which allows programs and settings to be sent to the datalogger. For more information, see "Sending a Program to the Datalogger" on page 18. Datalogger Support Software - Software retrieves data, sends programs, and sets settings. The software manages the communication link and has options for data display. Programmable Logic Control - Some data acquisition systems require the control of external devices to facilitate a measurement or to control a device based on measurements. This datalogger is adept at programmable logic control. See "Programmable Logic Control" on page 9 for more information. Measurement and Control Peripherals - Sometimes, system requirements exceed the capacity of the datalogger. The excess can usually be handled by addition of input and output expansion modules. Data Acquisition System Components 1

9 Sensors Sensors transduce phenomena into measurable electrical forms by modulating voltage, current, resistance, status, or pulse output signals. Suitable sensors do this with accuracy and precision. Smart sensors have internal measurement and processing components and simply output a digital value in binary, hexadecimal, or ASCII character form. Most electronic sensors, regardless of manufacturer, will interface with the datalogger. Some sensors require external signal conditioning. The performance of some sensors is enhanced with specialized input modules. The datalogger, sometimes with the assistance of various peripheral devices, can measure or read nearly all electronic sensor output types. The following list may not be comprehensive. A library of sensor manuals and application notes are available at to assist in measuring many sensor types. SUPPORTED SENSOR TYPES Analog o Voltage o Current o Strain o Thermocouples o Resistive bridges Pulse o High frequency o Switch-closure o Low-level ac Period average Vibrating wire (through interface modules) Smart sensors o SDI-12 o RS-232 o Modbus o DNP3 o TCP/IP o RS-485 The CR1000X Datalogger The CR1000X is used in a broad range of measurement and control functions. Rugged enough for extreme conditions and reliable enough for remote environments, it is also robust enough for complex configurations. Used in applications all over the world, it is a powerful core component for your data acquisition system. COMPONENTS The CR1000X datalogger is the main part of a data acquisition system (see "Components of Data Acquisition Systems" on page 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 2 Data Acquisition System Components

10 (firmware) coordinates the functions of these parts in conjunction with the onboard clock and the CRBasic application program. The CR1000X can simultaneously provide measurement and communication functions. Low power consumption allows the CR1000X to operate for extended time on a battery recharged with a solar panel, eliminating the need for ac power. The CR1000X suspends execution when primary power drops below 9.6 V, reducing the possibility of inaccurate measurements. The electronics are RF shielded and glitch protected by the sealed, stainless-steel canister, making the CR1000X economical, small, and very rugged. A battery-backed clock assures accurate timekeeping. OPERATIONS The CR1000X 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 are stored in onboard, nonvolatile memory awaiting transfer to the computer. 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. Programs are run by the CR1000X in either sequential mode or pipeline mode. In sequential mode, each instruction is executed sequentially in the order it appears in the program. In pipeline mode, the CR1000X determines the order of instruction execution to maximize efficiency. PROGRAMS A program directs the datalogger on how and when sensors are to be measured, calculations made, and data stored. The application program for the CR1000X is written in CRBasic, which is a programming language that includes measurement, data processing, and analysis routines, as well as the standard BASIC instruction set. For simpler applications, Short Cut, a user-friendly program generator, can be used to write the program. For more demanding programs, use CRBasic Editor. If you are programming with CRBasic, you can utilize the extensive help available with the CRBasic Editor software. Formal training is also available from Campbell Scientific. CR1000X Wiring Panel The CR1000X wiring panel provides ports and removable terminals for connecting sensors, power, and communication devices. It is protected against surge, over-voltage, over-current, and reverse power. The wiring panel is the interface to most datalogger functions so studying it is a good way to get acquainted with the datalogger. Functions of the terminals are broken down into the following categories: Analog input Pulse counting Period averaging Analog output Communications Digital I/O Power input Power output Ground terminals Data Acquisition System Components 3

11 Analog Input Functions SE 1 2 DIFF H L H L H L H L H L H L H L H L Single-Ended Voltage Differential Voltage H L H L H L H L H L H L H L H L VX1-VX4 RG1 RG2 Current Loop Ratiometric/Bridge Thermocouple Period Average Pulse Counting Functions P1 P2 C1-C8 Switch-Closure High Frequency Low-level Ac Analog Output Functions VX1-VX4 5V 12V SW12-1 SW12-2 Switched Voltage Excitation 5 Vdc Regulated Supply 3.3 Vdc Regulated Supply 12 Vdc Source 4 Data Acquisition System Components

12 Communications Functions C1 C2 C3 C4 C5 C6 C7 C8 RS-232/CPI SDI-12 GPS Time Sync PPS Rx TTL 0-5 V Tx Rx Tx Rx Tx Rx Tx Rx LVTTL V Tx Rx Tx Rx Tx Rx Tx Rx RS-232 Tx Rx Tx Rx RS-485 (Half Duplex) A- B+ A- B+ RS-485 (Full Duplex) Tx- Tx+ Rx- Rx+ I2C SCL SDA SCL SDA SCL SDA SCL SDA SPI SCLK MOSI MISO SCLK MOSI MISO SDM 1 Data Clk Enable Data Clk Enable CPI/CDM 1 SDM can be on either C1-C3 or C5-C7, but not both at the same time. Communication Functions also include Ethernet via Ethernet port and USB via USB port. Digital I/O Functions General I/O Pulse-Width Modulation Output Timer Input Interrupt C1-C8 POWER INPUT The datalogger requires a power supply (see "Troubleshooting Power Supplies" on page 64). The datalogger operates with external power connected to the green POWER IN port on the face of the wiring panel (see "CR1000X Wiring Panel" on page 3). The positive power lead connects to 12V. The negative lead connects to G. The connection is internally reverse-polarity protected (it protects against accidental polarity reversal) and high voltage transients. Warning: Sustained input voltages in excess of those listed in the "Power Output Specifications" on page 78, can damage the transient voltage suppression. Be sure that power supply components match the specifications of the device to which they are connected. When connecting power, first switch off the power supply then insert the connector. Once you make the connection, turn the power supply on. A UPS is often the best power source for long-term installations. An external UPS consists of a primarypower source, a charging regulator external to the datalogger, and an external battery. The primary power source, which is often a transformer, power converter, or solar panel, connects to the charging regulator, as does a nominal 12 Vdc sealed rechargeable battery. A third connection connects the charging regulator to the 12V and G terminals of the POWER IN port. If external alkaline power is used, the alkaline battery pack is connected directly to the POWER IN port. The CR1000X can receive power via the POWER IN port as well as 5 Vdc via a USB connection. If both POWER IN and USB are connected, power will be supplied by whichever has the highest voltage. If USB is the only power source, then the CS I/O port and the 12V, SW12, and 5V terminals will not be operational. Functions that will be active with a 5 Vdc source (USB) include sending programs, adjusting datalogger settings, and making some measurements. Data Acquisition System Components 5

13 Powering A Datalogger with a Vehicle If a datalogger is powered by a motor-vehicle power supply, a second power supply may be needed. When starting the motor of the vehicle, battery voltage often drops below the voltage required for datalogger operation. This may cause the datalogger to stop measurements until the voltage again equals or exceeds the lower limit. A second supply or charge regulator can be provided to prevent measurement lapses during vehicle starting. In vehicle applications, the earth ground lug should be firmly attached to the vehicle chassis with 12 AWG wire or larger. Power LED Indicator When the datalogger is powered, the Power LED will turn on according to power and program states: Off: No power, no program running. 1 flash every 10 seconds: Powered, program running. 3 flashes every 10 seconds: Powered via USB, program running. Always on: Powered, no program running. POWER OUTPUT The datalogger can be used as a power source for sensors and peripherals. Take precautions to prevent damage to sensors or peripherals from over- or under-voltage conditions, and to minimize the error associated with the measurement of underpowered sensors. 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: 12V terminals: unregulated nominal 12 Vdc. This supply closely tracks the primary datalogger supply voltage, so it may rise above or drop below the power requirement of the sensor or peripheral. Precautions should be taken to prevent damage to sensors or peripherals from overor under-voltage conditions, and to minimize the error associated with the measurement of underpowered sensors. 5V terminals: regulated 5 Vdc. The 5 Vdc supply is regulated to within a few millivolts of 5 Vdc so long as the main power supply for the datalogger does not drop below the minimum supply voltage. It is intended for power sensors or devices requiring a 5 Vdc power supply. It is not intended as an excitation source for bridge measurements. SW12 terminal: program-controlled, switched 12 Vdc terminal. Often used to power devices such as sensors that require 12 Vdc during measurement. Voltage on a SW12 terminal will change with datalogger supply voltage. CRBasic instruction SW12() controls the SW12 terminal. CS I/O port: used to communicate with and often supply power to Campbell Scientific peripheral devices Caution: Voltage levels at the 12V and switched SW12 terminals, and pin 8 on the CS I/O port, are tied closely to the voltage levels of the main power supply. For example, if the power received at the POWER IN 12V and G terminals is 16 Vdc, the 12V and SW12 terminals, and pin 8 on the CS I/O port, will supply 16 Vdc to a connected peripheral. If the connected peripheral or sensor is not designed for that voltage level, it may be damaged. 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" on page 32 for more information). Using the 6 Data Acquisition System Components

14 SWVX() instruction, VX terminals can also be used to supply a selectable, switched, regulated 3.3 or 5 Vdc power source to power digital sensors and toggle control lines. C terminals: can be set low or high as output terminals. With limited drive capacity, digital output terminals are normally used to operate external relay-driver circuits. See also "Power Output Specifications" on page 78. GROUNDS Proper grounding lends stability and protection to a data acquisition system. Grounding the datalogger 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 datalogger grounds: Signal Ground ( ) - reference for single-ended analog inputs, excitation returns, and as a ground for sensor shield wires. Power Ground (G) - return for 5V, 12V, 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. Resistive Ground (RG) - terminal for decoupling ground on RS-485 signals. Includes 101 Ω resistance to ground. Also used for measuring Current (see "Current Measurements" on page 30 for more information). Earth Ground Lug ( ) - connection point for heavy-gauge earth-ground wire. A good earth connection is necessary to secure the ground potential of the datalogger and shunt transients away from electronics. 14 AWG wire, minimum, is recommended. Note: Several ground wires can be connected to the same ground terminal. A good earth (chassis) ground will minimize damage to the datalogger and sensors by providing a lowresistance path around the system to a point of low potential. Campbell Scientific recommends that all dataloggers be earth (chassis) grounded. All components of the system (dataloggers, sensors, external power supplies, mounts, housings, etc.) should be referenced to one common earth (chassis) 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 the verification that it carries no current. If the integrity of the Vac power ground is in doubt, also ground the system through the building plumbing, or use another verified connection to earth ground. In vehicle applications, the earth ground lug should be firmly attached to the vehicle chassis with 12 AWG wire or larger (see "Powering A Datalogger with a Vehicle" on page 6 for more information). See also: "Minimizing Ground Loop Errors" on page 65 "Minimizing Ground Potential Differences" on page 67 Data Acquisition System Components 7

15 COMMUNICATION PORTS The datalogger is equipped with ports that allow communication with other devices and networks, such as: Computers Smart sensors Modbus and DNP3 networks Ethernet Modems Campbell Scientific PakBus networks Other Campbell Scientific dataloggers Campbell Scientific datalogger communication ports include: CS I/O RS-232/CPI USB Ethernet C1-C8 terminals USB Port One micro-b USB port, labeled USB, for communicating with a computer through datalogger support software, supporting virtual Ethernet (RNDIS), and providing 5 Vdc power to the datalogger (powering through the USB port has limitations, see "Power Input" on page 5 for more information). The datalogger USB port does not support USB flash or thumb drives. Ethernet Port RJ45 10/100 Ethernet port used for IP communications. C1 - C8 Terminals for Communications C Terminals are configurable for the following communication types: SDI-12 RS-232 RS-485 TTL (0 to 5 V) LVTTL (0 to 3.3 V) SDM Some communication types require more than one terminal, and some are only available on specific terminals. This is shown in the datalogger specifications. SDI-12 Port SDI-12 is a 1200 baud protocol that supports many smart sensors. C1, C3, C5, and C7 can be configured as SDI-12 ports. SDI-12 standard 1.4 sensors accept addresses 0 through 9, a through z, and A through Z. 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 Communication" on page Data Acquisition System Components

16 RS-232, RS-485, TTL, and LVTTL Ports RS-232, RS-485, TTL, and LVTTL communications are typically used for the following: Reading sensors with serial output Creating a multi-drop network Communication with other dataloggers or devices over long cables Configure C terminals as serial ports using Device Configuration Utility or by using the SerialOpen() CRBasic instruction. Terminals C1-C8 can be configured for RS-232 or RS-485 communications. The terminals are configured in pairs for RS-232 or half-duplex RS-485. For full-duplex RS-485, all four terminals are required. See also "Communication Protocols" on page 43. SDM Port SDM is a protocol proprietary to Campbell Scientific that supports several Campbell Scientific digital sensor and communication input and output expansion peripherals and select smart sensors. It uses a common bus and addresses each node. CRBasic SDM device and sensor instructions configure terminals C1, C2, and C3 together to create an SDM port. Alternatively, terminals C5, C6, and C7 can be configured together to be used as the SDM port by using the SDMBeginPort() instruction. See also "Communications Specifications" on page 84. CS I/O Port CS I/O is a Campbell Scientific proprietary input/output port as well as the proprietary serial communication protocol that occurs over this port. One nine-pin port, labeled CS I/O, for communicating with a computer or modem through Campbell Scientific communication interfaces, modems, or peripherals. It is recommended that you keep CS I/O cables short (maximum of a few feet). See also "Communications Specifications" on page 84. RS-232/CPI Port The datalogger includes one RJ45 module jack labeled RS-232-CPI. CPI is a proprietary interface for communications between Campbell Scientific dataloggers and Campbell Scientific CDM peripheral devices. It consists of a physical layer definition and a data protocol. CDM devices are similar to Campbell Scientific SDM devices in concept, but the use of the CPI bus enables higher data-throughput rates and use of longer cables. CDM devices require more power to operate in general than do SDM devices. CPI ports also enable networking between compatible Campbell Scientific dataloggers. Consult the manuals for CDM modules for more information. CPI has the following power levels: Off: Not used. High power: Fully active. Low-power standby: Whenever possible. Low-power bus: Sets bus and modules to low power. When used with an RJ45-to-DB9 converter cable, the RS-232/CPI port can be used as an RS-232 port. It defaults to bps (in autobaud mode), 8 data bits, no parity, and 1 stop bit. Use Device Configuration Utility or the SerialOpen() CRBasic instruction to change these options. Data Acquisition System Components 9

17 PROGRAMMABLE LOGIC CONTROL The datalogger can control instruments and devices such as: Controlling wireless cellular modem or GPS receiver to conserve power. Triggering a water sampler to collect a sample. Triggering a camera to take a picture. Activating an audio or visual alarm. Moving a head gate to regulate water flows in a canal system. Controlling ph dosing and aeration for water quality purposes. Controlling a gas analyzer to stop operation when temperature is too low. 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, or SW12 terminals. Short Cut has provisions for simple on/off control. Control modules and relay drivers are available to expand and augment datalogger control capacity. C terminals are selectable as binary inputs, control outputs, or communication ports. C terminals can be set low (0 Vdc) or high (3.3 or 5 Vdc) using the PortSet() or WriteIO() instructions. Other functions include device-driven interrupts, asynchronous communications and SDI-12 communications. The high voltage for C terminals defaults to 5 V, but it can be changed to 3.3 V using the PortPairConfig() instruction. Terminals C4, C5, and C7 can also be configured for pulse width modulation with a maximum period of 36.4 s. A C terminal configured for digital I/O is normally used to operate an external relay-driver circuit because the port itself has limited drive capacity. VX terminals can be set low (0 V) or high (3.3 or 5 V) using the SWVX() instruction. SW12 terminals can be set low (0 V) or high (12 V) using the SW12() instruction. 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). 10 Data Acquisition System Components

18 Example: Turn Modem on for 10 Minutes Hourly 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 datalogger SW12 terminal. The following code snip turns the modem on for the first ten minutes of every hour using the TimeIsBetween() instruction embedded in an If/Then logic statement: If TimeIsBetween(0,10,60,Min) Then SW12(SW12_1,1,1) 'Turn phone on. Else SW12(SW12_1,0,1) 'Turn phone off. EndIf Data Acquisition System Components 11

19 Setting Up the Datalogger The basic steps to setting up your datalogger to measure data include: 1. Configuring your connection. 2. Testing communication (optional). 3. Connecting the datalogger to the computer. 4. Creating a program and sending that program to the datalogger. Setting up Communications with the Datalogger The first step in setting up and communicating with your datalogger is to configure your connection. Communication peripherals, dataloggers, and software must all be configured for communication. In addition to this instruction and manuals for your specific peripherals, refer to your datalogger support software manual and help for guidance. The default settings for the datalogger allow it to communicate with a computer via USB, RS-232, or Ethernet, and to accept and execute user application programs. For other communication methods or more complex applications, some settings may need adjustment. Settings can be changed through Device Configuration Utility or through datalogger support software. You can configure your connection using any of the following options. The simplest is via USB. "Configuring Settings to Communicate over USB or RS-232" on page 12 "Configuring Settings to Communicate over Ethernet" on page 13 For other configurations, see the LoggerNet EZSetup Wizard help. Context-specific help is given in each step of the wizard by clicking on the Help button in the bottom right corner of the window. For complex datalogger networks, use Network Planner. CONFIGURING SETTINGS TO COMMUNICATE OVER USB OR RS-232 Setting up a USB or RS-232/CPI connection is a good way to begin communicating with your datalogger. Because these connections do not require configuration (like an IP address), you need only set up the communication between your computer and the datalogger. Watch a video or use the following instructions. Initial setup instruction follows. These settings can be revisited using the datalogger support software Edit Datalogger Setup option ( ). 1. Using datalogger support software, launch the EZSetup Wizard. PC200W and PC400 users, click the Add Datalogger button ( ). LoggerNet users, click the Setup ( ) option, click the View menu to ensure you are in the EZ (Simplified) view, then click the Add Datalogger button. 2. Click Next. 3. Select your datalogger from the list, type a name for your datalogger (for example, a site or project name), and click Next. 4. If prompted, select the Direct Connect connection type and click Next. 5. If this is the first time connecting this computer to a CR1000X via USB, click the Install USB Driver button, select your datalogger, click Install, and follow the prompts to install the USB drivers. 12 Setting Up the Datalogger

20 6. Plug the datalogger into your computer using a USB or RS-232 cable. The USB connection supplies 5V power as well as a communication link, which is adequate for setup, but a 12V battery will be needed for field deployment. If using RS-232, external power must be provided to the datalogger and a CPI/RS-232 RJ45 to DB9 cable is required for connection to a serial cable. Note: The Power LED on the datalogger indicates the program and power state. Because the datalogger ships with a program set to run on power-up, the Power LED flashes 3 times every 10 seconds when powered over USB. When powered with a 12 V battery, it flashes 1 time every 10 seconds. 7. From the COM Port list, select the COM port used for your datalogger. 8. USB and RS-232 connections do not typically require a COM Port Communication Delay - this allows time for the hardware devices to "wake up" and negotiate a communication link. Accept the default value of 00 seconds and click Next. 9. The baud rate and PakBus address must match the hardware settings for your datalogger. A USB connection does not require a baud rate selection, RS-232 connections default to baud, and the default PakBus address is 1. Set an Extra Response Time if you have a difficult or marginal connection and you want the datalogger support software to wait a certain amount of time before returning a communication failure error. LoggerNet and PC400 users can set a Max Time On-Line to limit the amount of time the datalogger remains connected. When the datalogger is contacted, communication with it is terminated when this time limit is exceeded. A value of 0 in this field indicates that there is no time limit for maintaining a connection to the datalogger. 10. Click Next. 11. By default, the datalogger 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 "Datalogger Security" on page 51 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 to you click Finish or click Next to test your communication, set the datalogger clock, and send a program to the datalogger. CONFIGURING SETTINGS TO COMMUNICATE OVER ETHERNET The CR1000X offers a 10/100 Ethernet connection you can configure using Device Configuration Utility. You will use this utility to enter the datalogger IP Address, Subnet Mask, and IP Gateway address. After this, you can use the EZSetup Wizard to set up communications with the datalogger (see "Configuring Ethernet Communication with the Datalogger" on page 14). If you already have the datalogger IP information, you can skip these steps and go directly to "Configuring Ethernet Communication with the Datalogger" on page Supply power to the datalogger. A USB connection supplies 5V power (as well as a communication link), which is adequate for setup, but a 12V battery will be needed for field deployment. If powering via USB, first install USB drivers during EZ Setup or by using Device Configuration Utility (select your datalogger, then on the main page, click Install USB Driver). 2. Connect an Ethernet cable to the 10/100 Ethernet port on the datalogger. The yellow and green Ethernet port LEDs display activity approximately one minute after connecting. If you do not see activity, contact your network administrator. For more information, see "Ethernet LEDs" on page 14. Setting Up the Datalogger 13

21 3. Using datalogger support software (LoggerNet, PC400, or PC200W), enter the Device Configuration Utility ( ). 4. Select the CR1000X Series datalogger from the list 5. Select the port assigned to the datalogger from the Communication Port list. If connecting via Ethernet, check the Use IP Connection button. 6. By default, this datalogger 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 "Datalogger Security" on page 51 for more information. 7. Click Connect. 8. On the Deployment tab, click the Ethernet subtab. 9. The Ethernet Power setting allows you to reduce the power consumption of the datalogger. If there is no Ethernet connection, the datalogger will turn off its Ethernet interface for the time specified before turning it back on to check for a connection. Select an option from the list. 10. Enter the IP Address, Subnet Mask, and IP Gateway. These values should be provided by your network administrator. A static IP address is recommended. If you are using DHCP, note the IP address assigned to the datalogger on the right side of the window. When the IP Address is set to , the default, 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 ###.### means the datalogger was not able to obtain an address from the DHCP server. Contact your network administrator for help. 11. Click Apply to save your changes. Ethernet LEDs When the datalogger is powered, the 10/100 Ethernet port will turn on with Ethernet activity: Solid Yellow: Valid Ethernet link. No Yellow: Invalid Ethernet link. Flashing Yellow: Ethernet activity. Solid Green: 100 Mbps link. No Green: 10 Mbps link. Configuring Ethernet Communication with the Datalogger Once you have configured the Ethernet settings or obtained the IP information for your datalogger, you can set up communication between your computer and the datalogger over Ethernet. Initial setup instruction follows. These settings can be revisited using the datalogger support software Edit Datalogger Setup option ( ). 1. Using datalogger support software, launch the EZSetup Wizard. PC400 users, click the Add Datalogger button ( ). LoggerNet users, click the Setup ( ) option, click the View menu to ensure you are in the EZ (Simplified) view, then click the Add Datalogger button. Note: PC200W does not allow IP connections. 2. Click Next. 3. Select the CR1000X Series from the list, type a name for your datalogger (for example, a site or project name), and click Next. 4. Select the IP Port connection type and click Next. 14 Setting Up the Datalogger

22 5. Supply power to the datalogger. A USB connection supplies 5V power (as well as a communication link), which is adequate for setup, but a 12V battery will be needed for field deployment. If powering via USB, first install USB drivers during EZ Setup or by using Device Configuration Utility (select your datalogger, then on the main page, click Install USB Driver). 6. Connect an Ethernet cable to the 10/100 Ethernet port on the datalogger. The yellow and green Ethernet port LEDs display activity approximately one minute after connecting. If you do not see activity, contact your network administrator. For more information, see "Ethernet LEDs" on page Type the datalogger IP address followed by a colon, then the port number of the datalogger in the Internet IP Address field (these were set up when "Configuring Settings to Communicate over Ethernet" on page 13). They can be accessed in Device Configuration Utility on the Ethernet subtab. Leading 0s must be omitted. For example: IPv4 addresses are entered as :6785 IPv6 addresses must be enclosed in square brackets. They are entered as [2001:db8::1234:5678]: The PakBus address must match the hardware settings for your datalogger. The default PakBus address is 1. Set an Extra Response Time if you want the datalogger support software to wait a certain amount of time before returning a communication failure error. LoggerNet and PC400 users can set a Max Time On-Line to limit the amount of time the datalogger remains connected. When the datalogger is contacted, communication with it is terminated when this time limit is exceeded. A value of 0 in this field indicates that there is no time limit for maintaining a connection to the datalogger. 9. Click Next. 10. By default, the datalogger 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 "Datalogger Security" on page 51 for more information. 11. Click Next. 12. 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 your communication, set the datalogger clock, and send a program to the datalogger. Testing Communication and Completing EZ Setup 1. Using datalogger support software EZ Setup, access the Communication Test window. Accessed during EZ Setup (see "Configuring Settings to Communicate over USB or RS- 232" on page 12 for more information). Alternatively, you can double-click a datalogger from the station list to open the EZ Setup Wizard and access the Communication Test step from the left side of the window. 2. Ensure the datalogger is connected to the computer, select Yes to test the communication, then click Next to initiate the test. To troubleshoot an unsuccessful test, see "Troubleshooting the Datalogger" on page 59. Setting Up the Datalogger 15

23 3. With a successful connection, the Datalogger Clock window displays the time for both the datalogger and the computer. The Adjusted Server Date/Time displays the current reading of the clock for the computer or server running your datalogger support software. If the Datalogger Date/Time and Adjusted Server Date/Time don't match, you can set the datalogger clock to the Adjusted Server Date/Time by clicking Set Datalogger Clock. Use the Time Zone Offset to specify a positive or negative offset to apply to the computer time when setting the datalogger clock. This offset will allow you to set the clock for a datalogger that needs to be set to a different time zone than the time zone of the computer (or to accommodate for changes in daylight saving time). 4. Click Next. 5. The datalogger ships with a default GettingStarted program. If the datalogger does not have a program, you can choose to send one by clicking the Select and Send Program button. Click Next. 6. LoggerNet only - watch a video or use the following instructions: The Datalogger Table Output Files window displays the data tables available to be collected from the datalogger and the output file name. To include a data table in scheduled collection, select the data table from the Tables list and check the Table Collected During Data Collection box. Select a Data File Option: Append to End of File adds new data to the end of the existing data file, Overwrite Existing File replaces the existing file with a newly created file, and No Output File results in no data file being written to disk. Make note of the Output File Name and location. Click Next. Check Scheduled Collection Enabled to have LoggerNet collect data from the datalogger according to a schedule. Set the Base Date and Time to begin scheduled collections. Set a Collection Interval, then click Next. 7. Click Finish. Connecting the Datalogger to a Computer Once you have configured your connection (see "Setting up Communications with the Datalogger" on page 12 for more information), you can connect the datalogger to your computer. PC200W and PC400 users, select the datalogger from the list and click the Connect button ( ). LoggerNet users, select Main and click the Connect button ( the datalogger from the Stations list, then click the Connect button ( ). To disconnect, click the Disconnect button ( ). See also "Communication Protocols" on page 43. Creating a Program in Short Cut ) on the LoggerNet toolbar, select Use the Short Cut software to generate a program for your datalogger. Short Cut is included with your datalogger support software. Watch a video or use the following instructions. 1. Using datalogger support software, launch Short Cut. PC200W and PC400 users, click the Short Cut button ( ). LoggerNet users, click Program then click the Short Cut button ( ). 16 Setting Up the Datalogger

24 2. Click Create New Program. 3. Select the CR1000XSeries datalogger and click Next. Note: The first time Short Cut is run, a prompt will appear asking for a choice of noise rejection. 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 probably the best fit if you are outside Europe. To change the noise rejection or sensor support option for future programs, use the Program menu. 4. A list of Available Sensors and Devices and Selected Measurements Available for Output 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. 6. If the sensor or device requires configuration, a window displays with configuration options. Click Help at the bottom of the window to learn more about any field or option. 7. Click OK. 8. Click Wiring Diagram on the left side of the window to see how to wire the sensor to the datalogger. With the power disconnected from the datalogger, insert the wires as directed in the diagram. Ensure you clamp the terminal on the conductor, not the wire insulation. Use the included flat-blade screwdriver to open/close the terminals. 9. Click Sensors on the left side of the window to return to the sensor selection window. 10. Use the Output Setup options to specify how often measurements are to be made and how often outputs are to be stored. Note that multiple output intervals can be specified, one for each output table (Table1 and Table2 tabs). 11. In the Table Name box, type a name for the table. 12. Select a Data Output Storage Interval. 13. Scroll down and optionally, select to copy the table to an external storage device. 14. Check the Advanced Outputs option if you want to specify the number of records and data events to store, set output intervals, specify measurements to evaluate, and set flags based on the value of a variable. 15. Click Next. 16. Select the measurement from the Selected Measurements Available for Output list, then click an output processing option to add the measurement to the Selected Measurements for Output list. Setting Up the Datalogger 17

25 17. Click Finish to compile the program. Replace the untitled.cr1x default name and click Save. 18. If LoggerNet or other datalogger support software is running on your computer, and the datalogger is connected to the computer (see "Connecting the Datalogger to a Computer" on page 16 for more information), you can choose to send the program. Note: A good practice is to always retrieve data from the datalogger before sending a program; otherwise, data may be lost. See "Collecting Data" on page 20 for detailed instruction. If your data acquisition requirements are simple, you can probably create and maintain a datalogger program exclusively with Short Cut. If your data acquisition needs are more complex, the files that Short Cut creates are a great source for programming code to start a new program or add to an existing custom program using CRBasic. See the CRBasic Editor help for detailed information on program structure, syntax, and each instruction available to the datalogger. Note: Once a Short Cut generated program has been edited with CRBasic Editor, it can no longer be modified with Short Cut. Sending a Program to the Datalogger The CR1000X datalogger requires a CRBasic program to direct measurement, processing, control, and data storage operations. The program file may use the extension.cr1x or.dld. A good practice is to always retrieve data from the datalogger before sending a program; otherwise, data may be lost. To collect data using LoggerNet, connect to your datalogger and click the Collect Now button ( ). 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 structure in the following list: Data table name(s) Data output interval or offset Number of fields per record Number of bytes per field Field type, size, name, or position Number of records in table SENDING A PROGRAM USING DATALOGGER SUPPORT SOFTWARE Watch an video on sending a program using LoggerNet or PC200W or use the following instructions. 1. Connect the datalogger to your computer (see "Connecting the Datalogger to a Computer" on page 16 for more information). 2. Using your datalogger support software, click Send New or Send Program (located in the Current Program section on the right side of the window). 3. Navigate to the location of the program, select it, and click Open. 4. Confirm that you would like to proceed and erase all data tables saved on the datalogger. The program will send, compile, then display results. After sending a program, it is a good idea to monitor the data to make sure it is measuring as you expect. See "Monitoring Data" on page 19 for more information. PROGRAM RUN OPTIONS When sending a program via File Control, Short Cut, or CRBasic, you can choose to have programs Run on Power-up and Run Now. Run Now will run the program when it is sent to the datalogger. Run on Power-up runs the program when the datalogger is powered-up. Selecting both Run Now and Run on Power-up will invoke both options. 18 Setting Up the Datalogger

26 Working with Data By default, the datalogger includes three tables: Public, Status, and DataTableInfo. Each of these tables only contains the most recent measurements and information. The Public table contains the measurements as they are made. It is updated at the scan interval set within the datalogger program. The Status table includes information on the health of the datalogger and is updated only when viewed. The DataTableInfo table reports statistics related to data tables. It also only updates when viewed. User-defined data tables update at the schedule set within the program. Monitoring Data Follow a tutorial or use the following instructions: PC200W and PC400 users, click the Connect button ( ), then click the Monitor Data tab. When this tab is first opened for a datalogger, values from the Public table are displayed. To view data from other tables, click the Add button ( ), select a table or field from the list, then drag it into a cell on the Monitor Data tab. LoggerNet users, select Main and click the Connect button ( ) on the LoggerNet toolbar, select the datalogger from the Stations list, then click the Connect button ( ). Once connected, you can select a table to view using the Table Monitor list. Working with Data 19

27 Collecting Data The datalogger writes to data tables according to the schedule set within the CRBasic program (see "Creating Data Tables in a Program" on page 23 for more information). After the program has been running for enough time to generate data records, data may be collected and reviewed via your datalogger support software. Collections may be done manually, or automatically through scheduled collections set in LoggerNet Setup. Follow a tutorial or use the following instructions. COLLECTING DATA USING LOGGERNET 1. LoggerNet users, select Main and click the Connect button ( ) on the LoggerNet toolbar, select the datalogger from the Stations list, then click the Connect button ( ). 2. Click the Collect Now button ( ). 3. After the data is collected, the Data Collection Results window displays the tables collected and where they are stored on the computer. 4. Click View File to view the data. See "Viewing Historic Data" on page 20 for more information. COLLECTING DATA USING PC200W OR PC400W 1. PC200W and PC400 users, click the Connect button ( ). 2. Click the Collect Data tab. 3. Select an option for What to Collect. Either option creates a new file if one does not already exist. New data from datalogger (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. All data from datalogger (Overwrite data files): Collects all of the data in the selected tables and replaces the existing table files on the computer. 4. Select the tables to collect from the list at the bottom of the window. 5. Click Start Data Collection. 6. The Data Collection Results window displays the tables collected and where they are stored on the computer. 7. Click View File to view the data. Viewing Historic Data View historic data in a spreadsheet format using View Pro. View Pro also contains tools for visualizing data in several graphical layouts. Follow a tutorial or use the following instructions: Once the datalogger has had ample time to take multiple measurements, you can collect and review the data. 1. To view the most recent data, connect the datalogger to your computer and collect your data (see "Collecting Data" on page 20 for more information). 2. Open View Pro: LoggerNet users select Data and click View Pro ( ) on the LoggerNet toolbar. PC200W and PC400 users click the View Data Files via View Pro toolbar button ( ). 3. Click the Open toolbar button ( ), navigate to the directory where you saved your tables (the default directory is C:\Campbellsci\[your datalogger software application]). 20 Working with Data

28 About Data Tables A data table is essentially a file that resides in datalogger memory. 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, maxima, or minima. The file is written to each time data are directed to that file. The datalogger records data based on time or event. You can retrieve data based on a schedule or by manually choosing to collect data using datalogger support software (see "Collecting Data" on page 20). The number of data tables is limited to 250. Example of a typical data table TOA5, MyStation, CR1000X, 142, CRxxx.Std.01, CPU:MyTemperature.CR1X, 1958, OneMin TIMESTAMP RECORD BattV_Avg PTemp_C_Avg Temp_C_Avg TS RN Volts Deg C Deg C Avg Avg Avg :24: :25: :26: :27: :28: :29: By default, the datalogger includes three tables: Public, Status, and DataTableInfo. Each of these tables only contains the most recent measurements and information. The Public table contains the measurements as they are made. It is updated at the scan interval set within the datalogger program. The Status table includes information on the health of the datalogger and is updated only when viewed. The DataTableInfo table reports statistics related to data tables. It also only updates when viewed. User-defined data tables update at the schedule set within the program. TABLE DEFINITIONS Each data table is associated with overhead information, referred to as table definitions, that becomes part of the file header (first few lines of the file) when data are downloaded to a computer. These include the table format, datalogger type and OS, name of the CRBasic program running in the datalogger, name of the data table (limited to 20 characters), and the alphanumeric field names to attach at the head of data columns, FIRST HEADER ROW 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: 1: TOA5 - Table output format. Changed via LoggerNet Setup ( ) Standard View, Data Files tab. 2: MyStation - Station name. Changed via LoggerNet Setup, Device Configuration Utility, or CRBasic program. 3: CR1000X - Datalogger model. 4: Datalogger serial number. Working with Data 21

29 5: CRxxx.Std.01 - Datalogger OS version. Changed via installation of a new OS. 6: CPU:MyTemperature.CR1X - Datalogger program name. Changed by sending a new program (see "Sending a Program to the Datalogger" on page 18 for more information). 7: Datalogger program signature. Changed by revising a program or sending a new program (see "Sending a Program to the Datalogger" on page 18 for more information). 8: OneMin - Table name. Changed by revising a program (see "Creating Data Tables in a Program" on page 23 for more information). SECOND HEADER ROW The second header row reports field names. Default field names are a combination of the variable names (or aliases) from which data are 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 Process Names and Abbreviations" on page 22. If a field is an element of an array, the field name will be followed by a list of subscripts within parentheses that identifies the array index. For example, a variable named Values, which is declared as a two-by-two array in the datalogger program, will be represented by four field names: Values(1,1), Values(1,2), Values(2,1), and Values(2,2). Scalar variables will not have array subscripts. There will be one value on this line 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 of a typical data table" on page 21. THIRD HEADER ROW The third header row identifies engineering units for that field of data. These units are declared at the beginning of a CRBasic program, as shown in "Creating Data Tables in a Program" on page 23. In Short Cut, units are chosen when sensors or measurements are added. Units are strictly for documentation. The datalogger does not make use of declared units, nor does it check their accuracy. FOURTH HEADER ROW The fourth header row reports abbreviations of the data process used to produce the field of data. Data Process Names and Abbreviations Totalize Tot Average Avg Maximum Max Minimum Min Sample at Max or Min SMM Standard Deviation Std Moment MMT Sample No abbreviation Histogram 1 Hst Histogram4D H4D FFT FFT Covariance Cov Level Crossing LCr 22 Working with Data

30 WindVector WVc Median Med ET ETsz Solar Radiation (from ET) RSo Time of Max TMx Time of Min TMn 1 Hst is reported in the form Hst,20,1.0000e+00,0.0000e+00,1.0000e+01 where Hst denotes a histogram, 20 = 20 bins, 1 = weighting factor, 0 = lower bound, 10 = upper bound. DATA RECORDS Subsequent rows are called data records. They include observed data and associated record keeping. The first field is a timestamp (TS), and the second field is the record number (RN). The timestamp shown represents the time at which the data is written. Therefore, because the scan rate of the program MyTemperature.CR1X is 1 second, Temp_C_Avg in record number 3 in the previous "Example of a typical data table" on page 21, 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 timestamped :00:00 will contain the total rainfall beginning at :00:01 and ending at :00:00. Creating Data Tables in a Program Data are stored in tables as directed by the CRBasic program. In Short Cut, data tables are created in the Output steps (see "Creating a Program in Short Cut" on page 16). Data tables are created within the CRBasic datalogger program using the DataTable()/EndTable instructions. They are placed after variable declarations and before the BeginProg instruction. Between DataTable() and EndTable() are instructions that define what data to store and under what conditions data are stored. A data table must be called by the CRBasic program for data storage processing 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 For more information, see the CRBasic help. Memory and Data Storage 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, and the Interval and Units parameters of the Scan() instruction. The datalogger uses those parameters to assign sectors in a way that maximizes the life of its memory. By default, data storage memory sectors are organized as ring memory. When the ring is full, oldest data are 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 are stored until the table is reset. To see the total number of records that can be stored before the oldest data are overwritten, or to reset tables, go to Station Status Table Fill Times in your datalogger support software. Data concerning the datalogger memory are posted in the Status and DataTableInfo tables. Working with Data 23

31 MEMORY ALLOCATION Data table SRAM and the CPU drive are automatically partitioned for use in the datalogger. The USR drive can be partitioned as needed. The USB drive is automatically partitioned when a Campbell Scientific mass-storage device is connected. The CRD drive is automatically partitioned when a memory card is installed. Primary storage for measurement data are those areas in SRAM allocated to data tables. The CPU and USR drives use the FAT32 file system. There is no limit, beyond practicality and available memory, to the number of files that can be stored. While a FAT file system is subject to fragmentation, performance degradation is not likely to be noticed since the drive has a relatively small amount of solid state RAM and so is accessed very quickly. CPU DRIVE The serial flash memory CPU drive contains datalogger programs and other files. It holds a copy of final-data memory when the TableFile() instruction is used. It provides memory for FileRead() and FileWrite() operations. This memory is managed in File Control. When writing to files under program control, take care to write infrequently in order to prevent premature failure of serial flash memory. SRAM Measurement data is stored in data tables within SRAM. Data are usually erased from this area when a program is sent to the datalogger. USR DRIVE SRAM can be partitioned to create a FAT32 USR drive, analogous to partitioning a second drive on a computer hard disk. Certain types of files are stored to USR to reserve limited CPU drive memory for datalogger programs and calibration files. Partitioning also helps prevent interference from data table SRAM. The USR drive holds any file type within the constraints of the size of the drive and the limitations on filenames. Files typically stored include image files from cameras, certain configuration files, files written for FTP retrieval, HTML files for viewing with web access, and files created with the TableFile() instruction. Measurement data can also be stored on USR as discrete files by using the TableFile() instruction. Files on USR can be collected using the datalogger support software Retrieve command in File Control, or automatically using the LoggerNet Setup File Retrieval tab functions. USR is not affected by program recompilation or formatting of other drives. It will only be reset if the USR drive is formatted, a new operating system is loaded, or the size of USR is changed. USR size is set manually by accessing it in the Settings Editor, or programmatically by loading a CRBasic program with a USR drive size entered in a SetStatus() or SetSetting() instruction. Partition the USR drive to at least bytes in 512-byte increments. If the value entered is not a multiple of 512 bytes, the size is rounded up. Maximum size of USR bytes. Note: Placing an optional USR size setting in the CRBasic program overrides manual changes to USR size. When USR size is changed manually, the CRBasic program restarts and the programmed size for USR takes immediate effect. Files in the USR drive can be managed through datalogger support software File Control or through the FileManage() instruction in CRBasic program. 24 Working with Data

32 MICROSD (CRD: DRIVE) STORAGE The datalogger has a microsd card slot for removable, supplemental storage. The card can be configured as an extension of the datalogger final storage memory or as a repository of discrete data files. In data file mode, sub folders are not supported. The CRD: drive uses microsd cards exclusively. Its primary purpose is the storage of data files in a compact binary format. Campbell Scientific recommends and supports only the use of microsd cards obtained from Campbell Scientific. These cards are industrial-grade and have passed Campbell Scientific hardware testing. Use of consumer grade cards substantially increases the risk of data loss. Following are listed advantages Campbell Scientific cards have over less expensive commercial-grade cards: Less susceptible to failure and data loss. Match the datalogger operating temperature range. Provide faster read/write times. Include vibration and shock resistance. Have longer life spans (more read/write cycles). A maximum of 30 data tables can be created on a microsd card. When a data table is sent to a microsd card, a data table of the same name in SRAM is used as a buffer for transferring data to the card. When the card is present, the Status table will show the size of the table on the card. If the card is removed, the size of the table in SRAM is shown. When a new program is compiled that sends data to the card, the datalogger checks if a card is present and if the card has adequate space for the data tables. If no card is present, or if space is inadequate, the datalogger will warn that the card is not being used. However, the CRBasic program runs anyway and data are stored to SRAM. When a card is inserted later, data accumulated in the SRAM table are copied to the card. A microsd card can also facilitate the use of powerup.ini (see "Managing Memory via Powerup.ini" on page 26 for more information). Formatting MicroSD Cards The datalogger accepts microsd cards formatted as FAT16 or FAT32; however, FAT32 is recommended. Otherwise, some functionality, such as the ability to manage large numbers of files (>254) is lost. The datalogger formats memory cards as FAT32. Because of the way the FAT32 card format works, you can avoid long datalogger compile times with a freshly formatted card by first formatting the new card on a computer, then copying a small file to the card from the computer, and then deleting the file with the computer. When the small file is copied to the card, the computer updates a sector on the card that which allows the datalogger program to compile faster. This only needs to be done once when the card is formatted. If you have the datalogger update the card sector, the first datalogger program compile with the card can take as long as 30 minutes. After that, compile times will be normal. Working with Data 25

33 MicroSD Card Precautions Observe the following precautions when using optional storage cards: Before removing a card from the datalogger, disable the card by pressing the Eject button, and waiting for the green LED. You then have 15 seconds to pull the card before normal operations resume. Do not remove a storage card while the drive is active, or data corruption and damage to the card may result. Prevent data loss by collecting data before sending a program from the storage card to the datalogger. Sending a program from the storage card to the datalogger often erases all data. MicroSD LED Indicator When the datalogger is powered and a microsd is connected, the microsd LED will turn on according to power and program states: Red flash: Card read/write activity. Solid green: Formatted card inserted, powered up. This LED also indicates it is OK to remove card. The Eject button must be pressed before removing a card to allow the datalogger to store buffered data to the card and then power it off. Solid orange: Error. Dim/flashing orange: Card has been removed and has been out long enough that CPU memory has wrapped and data is being overwritten without being stored to the card. MANAGING MEMORY VIA POWERUP.INI Another way to upload a program, install a datalogger OS, or format a drive is to create a powerup.ini program. The program is created with a text editor and saved to a memory card or SC115, along with associated files. Alternatively, the powerup.ini program and associated files can be saved directly to the datalogger using the datalogger support software File Control Send command. With the memory card or SC115 connected, or with the powerup.ini file saved in the datalogger memory, a power cycle to the datalogger begins the process chosen in the powerup.ini program. When uploading a program, the following rules determine what datalogger program to run: If the Run Now program is changed, then it is the program that runs. If no change is made to the Run Now program, but the Run on Power Up program is changed, the new Run on Power Up program runs. If neither Run on Power Up nor Run Now programs are changed, the previous Run on Power Up program runs. Syntax for the powerup.ini program and available options follow. Syntax Syntax for powerup.ini is: Command,File,Device where, Command is one of the numeric commands in the following table. File is the accompanying operating system or user program file. File name can be up to 22 characters long. 26 Working with Data

34 Device is the datalogger memory drive to which the accompanying operating system or user program file is copied (usually CPU). If left blank or with an invalid option, default device will be CPU. Use the same drive designation as the transporting external device if the preference is to not copy the file. Command Action Details 1 1 Run always, preserve data Copies a program file to a drive and sets the program to both Run Now and Run on Power Up. Data on a memory card from the previously running program will be preserved if table structures have not changed. Run on power Copies a program file to a drive and sets the program to Run Always unless 2 up command 6 or 14 is used to set a separate Run Now program. 5 Format Formats a drive. Copies a program file to a drive and sets the program to Run Now. Data on a Run now, 6 1 memory card from the previously running program will be preserved if table preserve data structures have not changed. 7 Copy files Copies a file, such as an Include or program support file, to the specified drive. Load OS Loads an.obj file to the CPU drive and then loads the.obj file as the new 9 (File=.obj) datalogger operating system. 13 Run always, erase data Copies a program to a drive and sets the program to both Run Now and Run on Power Up. Data on a memory card from the previously running program will be erased. Run now, Copies a program to a drive and sets the program to Run Now. Data on a memory 14 erase data card from the previously running program will be erased. 15 Move file Moves a file, such as an Include or program support file, to the specified drive. 1 Use PreserveVariables() instruction in the CRBasic program in conjunction with powerup.ini script commands 1 and 6 to preserve data and variables. Example Powerup.ini Programs Comments can be added to the file by preceding them with a single-quote character ('). All text after the comment mark on the same line is ignored. Caution: Test the powerup.ini file and procedures in the lab before going to the field. Always carry a laptop or mobile device (with datalogger support software) into difficult- or expensive-to-access places as backup. Example: Code Format and Syntax 'Command = numeric power up command 'File = file associated with the action 'Device = device to which File is copied. Defaults to CPU 'Command,File,Device 13,Write2CRD_2.cr1x,cpu: Example: Run Program on Power Up 'Copy program file pwrup.cr1x from the external drive to CPU: 'File will run only when the datalogger is powered-up later. 2,pwrup.cr1x,cpu: Example: Format the USR Drive 5,,usr: Example: Send OS on Power Up 'Load an operating system (.obj) file into FLASH as the new OS 9,CR1000X.Std.01.obj Working with Data 27

35 Example: Run Program from SC115 Flash Memory Drive 'A program file is carried on an SC115 Flash Memory drive. 'Do not copy program file from SC115. Run program always, erase data. 13,toobigforcpu.cr1x,usb: Example: Always Run Program, Erase Data 13,pwrup_1.cr1x,cpu: Example: Run Program Now and Erase Data Now 14,run.cr1x,cpu: 28 Working with Data

36 Measurements Voltage Measurements Current Measurements Ratiometric Resistance Measurements Thermocouple Measurements Period-Averaging Measurements Pulse Measurements Vibrating Wire Measurements Voltage Measurements Voltage measurements are made using an ADC. A high-impedance programmable-gain amplifier 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" on page 66. A voltage measurement proceeds as follows: 1. Set PGIA gain for the voltage range selected with the CRBasic measurement instruction parameter Range. Set the ADC for the first notch frequency selected with fn1. 2. If used, turn on excitation to the level selected with ExmV. 3. Multiplex selected terminals (InChan, SEChan, or DiffChan). 4. Delay for the entered settling time (SettlingTime). 5. Perform the ADC. 6. Repeat for input reversal as determined by parameters RevEx and RevDiff. 7. Apply multiplier (Mult) and offset (Offset) to measured result. 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 Specifications" on page 80 for more information). A set overhead reduces the chance of overrange. Overrange limits are available in the specifications. The datalogger indicates a measurement overrange by returning a NAN for the measurement. Warning: Sustained voltages in excess of ±20 V applied to terminals configured for analog input will damage CR1000X circuitry. 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 "CR1000X Wiring Panel" on page 3. The single-ended configuration is used with the following CRBasic instructions: VoltSE() BrHalf() BrHalf3W TCSE() Therm107() Therm108() Therm109() Measurements 29

37 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 "CR1000X Wiring Panel" on page 3. The differential configuration is used with the following CRBasic instructions: VoltDiff() BrFull() BrFull6W() BrHalf4W() TCDiff() Reverse Differential Differential measurements have the advantage of an input reversal option, RevDiff. When RevDiff is set to True, two differential measurements are made, the first with a positive polarity and the second reversed. Subtraction of opposite polarity measurements cancels some offset voltages associated with the measurement. Current Measurements RG terminals can be configured to make analog current measurements using the CurrentSE() instruction. When configured to measure current, terminals each have an internal resistance of 101 Ω which is placed in the current measurement loop. The return path of the sensor must be connected directly to the G terminal closest to the terminal used. The following image shows a simplified schematic of a current measurement. EXAMPLE CURRENT MEASUREMENT CONNECTIONS The following table shows example schematics for connecting typical current sensors and devices. Sensor Type Connection Example 2-wire transmitter using datalogger power 30 Measurements

38 Sensor Type Connection Example 2-wire transmitter using external power 3-wire transmitter using datalogger power 3-wire transmitter using external power 4-wire transmitter using datalogger power 4-wire transmitter using external power See also "Current Measurements Specifications" on page 83. Measurements 31

39 Ratiometric 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 datalogger supplies a precise voltage excitation via VX terminals. Return voltage is measured on analog input terminals configured for single-ended (SE) or differential (DIFF) input. The result of the measurement is a ratio of measured voltages, as shown in the following table. CRBasic instructions for measuring resistance include: BrHalf() - half-bridge BrHalf3W() - three-wire half-bridge BrHalf4W() - four-wire half-bridge BrFull() - four-wire full-bridge BrFull6W() - six-wire full-bridge Resistive-Bridge Type and Circuit Diagram Half-Bridge 1 CRBasic Instruction and Fundamental Relationship CRBasic Instruction: BrHalf() Fundamental Relationship 2 : Relational Formulas Three-Wire Half-Bridge 1,3 CRBasic Instruction: BrHalf3W() Fundamental Relationship 2 : 32 Measurements

40 Resistive-Bridge Type and Circuit Diagram Four-Wire Half-Bridge 1,3 CRBasic Instruction and Fundamental Relationship CRBasic Instruction: BrHalf4W() Fundamental Relationship 2 : Relational Formulas Full-Bridge 1,3 CRBasic Instruction: BrFull() Fundamental Relationship 2 : These relationships apply to BrFull() and BrFull6W() Six-Wire Full Bridge 1 CRBasic Instruction: BrFull6W() Fundamental Relationship 2 : 1 Key: V x = excitation voltage; V 1, V 2 = sensor return voltages; R f = fixed, bridge or completion resistor; R s = variable or sensing resistor. 2 Where X = result of the CRBasic bridge measurement instruction with a multiplier of 1 and an offset of 0. 3 Campbell Scientific offers a list of available terminal input modules to facilitate this measurement. Measurements 33

41 RESISTIVE-BRIDGE MEASUREMENTS AND VOLTAGE EXCITATION Offset voltage compensation applies to bridge measurements. In addition to RevDiff and MeasOff parameters discussed in "Minimizing Offset Voltages" on page 72, CRBasic bridge measurement instructions include the RevEx parameter that provides the option to program a second set of measurements with the excitation polarity reversed. Much of the offset error inherent in bridge measurements is canceled out by setting RevDiff, RevEx, and MeasOff to True. Measurement speed can be slowed when using RevDiff, MeasOff, and RevEx. When more than one measurement per sensor are necessary, such as occur with the BrHalf3W(), BrHalf4W(), and BrFull6W instructions, input and excitation reversal are applied separately to each measurement. For example, in the four-wire half-bridge (BrHalf4W()), when excitation is reversed, the differential measurement of the voltage drop across the sensor is made with excitation at both polarities and then excitation is again applied and reversed for the measurement of the voltage drop across the fixed resistor. The results of measurement instructions (X) must then be processed further to obtain the resistance value, which requires additional program execution time. CRBasic Example: 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 R2 Public R_4 = 1000 'Resistance of fixed resistor R4 'Main Program BeginProg Scan(500,mSec,1,0) 'Full Bridge Measurement: BrFull(X,1,mV200,1,Vx1,1,4000,True,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 See also "Ratiometric-Resistance Measurements Specifications" on page 81. 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 particular strain bridge configuration used. All strain gages supported by StrainCalc() use the full-bridge schematic. In strain-gage parlance, 'quarter-bridge', 'half-bridge' and 'full-bridge' refer to the number of active 34 Measurements

42 elements in the full-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 V r to negative. StrainCalc() BrConfig Code 1 Quarter-bridge strain gage 1 : Configuration 2 Half-bridge strain gage 1. One gage parallel to strain, the other at 90 to strain: 3 Half-bridge strain gage. One gage parallel to +ɛ, the other parallel to -ɛ 1 : 4 Full-bridge strain gage. Two gages parallel to +ɛ, the other two parallel to -ɛ 1 : 5 Full-bridge strain gage. Half the bridge has two gages parallel to +ɛ and -ɛ, and the other half to + ɛ and - ɛ 1: 6 Full-bridge strain gage. Half the bridge has two gages parallel to +ɛ and - ɛ, and the other half to - ɛ and +ɛ 1 : 1 : Poisson's Ratio (0 if not applicable). GF: Gage Factor. Vr: (Source-Zero) if BRConfig code is positive (+). Vr: (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. Measurements 35

43 AC EXCITATION Some resistive sensors require ac excitation. Ac excitation is defined as excitation with equal positive (+) and negative ( ) duration and magnitude. These include electrolytic tilt sensors, soil moisture blocks, water-conductivity sensors, and wetness-sensing grids. The use of single polarity dc excitation with these sensors can result in polarization of sensor materials and the substance measured. Polarization may cause erroneous measurement, calibration changes, or rapid sensor decay. Other sensors, for example, LVDTs (linear variable differential transformers), require ac excitation because they require inductive coupling to provide a signal. Dc excitation in an LVDT will result in no measurement. CRBasic bridge-measurement instructions have the option to reverse polarity to provide ac excitation by setting the RevEx parameter to True. Note: Take precautions against ground loops when measuring sensors that require ac excitation. See also "Minimizing Ground Loop Errors" on page 65. ACCURACY FOR RATIOMETRIC RESISTANCE MEASUREMENTS Consult the following technical papers for in-depth treatments of several topics addressing voltage measurement quality: Preventing and Attacking Measurement Noise Problems Benefits of Input Reversal and Excitation Reversal for Voltage Measurements Voltage Measurement Accuracy, Self- Calibration, and Ratiometric Measurements Note: Error discussed in this section and error-related specifications of the CR1000X do not include error introduced by the sensor or by the transmission of the sensor signal to the datalogger. For accuracy specifications for ratiometric resistance measurements, see "Ratiometric-Resistance Measurements Specifications" on page 81. Voltage measurement is variable V1 or V2 in "Resistance Measurements" on page 32. Offset is the same as that for simple analog voltage measurements. Assumptions that support the ratiometric-accuracy specification include: Datalogger is within factory calibration specification. Input reversal for differential measurements and excitation reversal for excitation voltage are within specifications. Effects due to the following are not included in the specification: o Bridge-resistor errors o Sensor noise o Measurement noise Thermocouple Measurements Thermocouple measurements are special case voltage measurements. Note: Thermocouples are inexpensive and easy to use. However, they pose several challenges to the acquisition of accurate temperature data, particularly when using external reference junctions. A thermocouple consists of two wires, each of a different metal or alloy, joined at one end to form the measurement junction. At the opposite end, each lead connects to terminals of a voltage measurement 36 Measurements

44 device, such as the datalogger. These connections form the reference junction. If the two junctions (measurement and reference) are at different temperatures, a voltage proportional to the difference is induced in the wires. This phenomenon is known as the Seebeck effect. Measurement of the voltage between the positive and negative terminals of the voltage-measurement device provides a direct measure of the temperature difference between the measurement and reference junctions. A third metal (e.g., solder or datalogger terminals) between the two dissimilar-metal wires form parasitic-thermocouple junctions, the effects of which cancel if the two wires are at the same temperature. Consequently, the two wires at the reference junction are placed in close proximity so they remain at the same temperature. Knowledge of the reference junction temperature provides the determination of a reference junction compensation voltage, corresponding to the temperature difference between the reference junction and 0 C. This compensation voltage, combined with the measured thermocouple voltage, can be used to compute the absolute temperature of the thermocouple junction. TCDiff() and TCSe() thermocouple instructions determine thermocouple temperatures using the following sequence. First, the temperature ( C) of the reference junction is determined. Next, a reference junction compensation voltage is computed based on the temperature difference between the reference junction and 0 C. If the reference junction is the datalogger analog-input terminals, the temperature is conveniently measured with the PanelTemp() instruction. The actual thermocouple voltage is measured and combined with the reference junction compensation voltage. It is then used to determine the thermocouple-junction temperature based on a polynomial approximation of NIST thermocouple calibrations. Period-Averaging Measurements Period-averaging measurements use 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" on page 37. SE terminals on the datalogger are configurable for measuring the period of a signal. The measurement is performed as follows: low-level signals are amplified prior to a voltage comparator. The internal voltage comparator is referenced to the programmed threshold. The threshold parameter allows referencing the internal voltage comparator to voltages other than 0 V. For example, a threshold of 2500 mv allows a 0 to 5 Vdc digital signal to be sensed by the internal comparator without the need for additional input conditioning circuitry. The threshold allows direct connection of standard digital signals, but it is not recommended for small-amplitude sensor signals. A threshold other than zero results in offset voltage drift, limited accuracy ( ±10 mv) and limited resolution ( 1.2 mv). See also "Period Averaging Specifications" on page 81. Pulse Measurements The output signal generated by a pulse sensor is a series of voltage waves. The sensor couples its output signal to the measured phenomenon by modulating wave frequency. The datalogger detects the state transition as each wave varies between voltage extremes (high-to-low or low-to-high). Measurements are processed and presented as counts, frequency, or timing data. Measurements 37

45 The datalogger includes terminals that are configurable for pulse input to measure counts or frequency as shown in the following image. Pulse input terminals and the input types they can measure: Input Type Pulse Input Terminal Data Option High-frequency P1 P2 C (all) Counts Low-level ac Switch-closure P1 P2 P1 P2 C (all) Frequency Running average of frequency Using the PulseCount() instruction, P and C terminals are configurable for pulse input to measure counts or frequency. Maximum input frequency is dependent on input voltage (see "Pulse Counting Specifications" on page 82 for more information). If pulse input voltages exceed the maximum voltage, third-party external-signal conditioners should be employed. Under no circumstances should voltages greater than 20 V be measured. P and C 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. High-frequency pulse inputs are routed to an inverting CMOS input buffer with input hysteresis. For tips on working with pulse measurements, see "Pulse Measurement Tips" on page 41. For more information, see "Pulse Counting Specifications" on page 82. LOW-LEVEL AC MEASUREMENTS Low-level ac (sine-wave) signals can be measured on P terminals. Ac generator anemometers typically output low-level ac. Measurements include the following: Counts Frequency (Hz) Running average Rotating magnetic-pickup sensors commonly generate ac voltage ranging from thousandths of volts at low-rotational speeds to several volts at high-rotational speeds. CRBasic instruction: PulseCount() 38 Measurements

46 Low-level ac signals cannot be measured directly by C terminals. Peripheral terminal expansion modules are available for converting low-level ac signals to square-wave signals measurable by C terminals. For more information, see "Pulse Counting Specifications" on page 82. HIGH FREQUENCY MEASUREMENTS High-frequency (square-wave) signals can be measured on P or C terminals. Common sensors that output high-frequency include: Photo-chopper anemometers Flow meters Measurements include counts, frequency in hertz, and running average. Note that the resolution of a frequency measurement can be different depending on whether the measurement is made with the PulseCount() or TimerIO() instruction. See the CRBasic help for more information. P Terminals CRBasic instructions: PulseCount() High-frequency pulse inputs are routed to an inverting CMOS input buffer with input hysteresis. C Terminals CRBasic instructions: PulseCount(), TimerIO() See "Specifications" on page 77 for more information. SWITCH-CLOSURE AND OPEN-COLLECTOR MEASUREMENTS Switch-closure and open-collector signals can be measured on P or C terminals. Mechanical switchclosures have a tendency to bounce before solidly closing. Unless filtered, bounces can cause multiple counts per event. The datalogger automatically filters bounce. Because of the filtering, the maximum switch-closure frequency is less than the maximum high-frequency measurement frequency. Sensors that commonly output a switch-closure or open-collector signal include: Tipping-bucket rain gages Switch-closure anemometers Flow meters Data output options include counts, frequency (Hz), and running average. P Terminals An internal 100 kω pull-up resistor pulls an input to 5 Vdc with the switch open, whereas a switchclosure to ground pulls the input to 0 V. An internal hardware debounce filter has a 3.3 ms time constant. CRBasic instruction: PulseCount() Measurements 39

47 Switch Closure on P Terminal Open Collector on P Terminal C Terminals Switch-closure mode is a special case edge-count function that measures dry-contact switch-closures or open collectors. The operating system filters bounces. CRBasic instruction: PulseCount() See also "Pulse Counting Specifications" on page 82. EDGE TIMING AND EDGE COUNTING Edge time, period, and counts can be measured on P or C terminals. Measurements for feedback control using pulse-width modulation (PWM) are an example of an edge timing application. Single Edge Timing A single edge or state transition can be measured on P or C terminals. Measurements can be expressed as a frequency (Hz) or period (µs): CRBasic instructions: TimerInput() available on C1 C8 PulseCount() available on C1 C8 and P1 P2 PeriodAvg() available on SE1 SE16 Multiple Edge Counting Time between edges, time from an edge on the previous channel, and edges that span the scan interval can be measured on C terminals: CRBasic instruction: TimerInput()- available on C1 C8 Timer Input on NAN Conditions NAN is the result of a TimerInput() measurement if one of the following occurs: Measurement timer expires. The signal frequency is too fast. For more information, see: "Pulse Counting Specifications" on page 82 "Digital I/O Specifications" on page 83 "Period Averaging Specifications" on page Measurements

48 PULSE MEASUREMENT TIPS The PulseCount() instruction uses dedicated 32-bit counters to accumulate all counts over the programmed scan interval. The resolution of pulse counters is one count or 1 Hz. Counters are read at the beginning of each scan and then cleared. Counters will overflow if accumulated counts exceed 4,294,967,296 (2 32 ), resulting in erroneous measurements. Counts are the preferred PulseCount() output option when measuring the number of tips from a tipping-bucket rain gage or the number of times a door opens. Many pulse-output sensors, such as anemometers and flow meters, are calibrated in terms of frequency (Hz) so are usually measured using the PulseCount() frequency-output option. Use the LLAC4 module to convert non-ttl-level signals, including low-level ac signals, to TTL levels for input into 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 on page 38.Pulse input terminals and the input types they can measurepulse input terminals and the input types they can measure Input Filters and Signal Attenuation P and C 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 enough, it may not pass the detection thresholds required by the pulse count circuitry. The metric for filter effectiveness is τ, the filter time constant. The higher the τ value, the less noise that gets through the filter, but the lower the signal frequency must be to pass the detection thresholds. While a C terminal measured with the TimerIO() frequency measurement may be superior for clean signals, a P terminal filter (much higher τ) may be required to get a measurement on an electronically noisy signal. For example, increasing voltage is required for low-level ac inputs to overcome filter attenuation on P terminals configured for low-level ac: 8.5 ms time constant filter (19 Hz 3 db frequency) for low-amplitude signals. 1 ms time constant (159 Hz 3 db frequency) for larger (> 0.7 V) amplitude signals. An example showing the amplitude reduction that results from τ in high-frequency pulse input mode is illustrated in the following image: Measurements 41

49 Vibrating Wire Measurements The datalogger can measure vibrating wire sensors through vibrating-wire interface modules. Vibrating wire sensors are the sensor of choice in many environmental and industrial applications that need sensor stability over very long periods, such as years or even decades. A thermistor included in most sensors can be measured to compensate for temperature errors. 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 Hz. For detailed information on VSPECT, see Vibrating Wire Spectral Analysis Technology. 42 Measurements

50 Communication Protocols Dataloggers communicate with datalogger support software and other Campbell Scientific dataloggers using a number of protocols including PakBus, Modbus, DNP3, CPI, SPI, and TCP/IP. Several industryspecific protocols are also supported. CAN bus is supported when using the Campbell Scientific SDM- CAN communication module. See also "Communications Specifications" on page 84. General Serial Communications Modbus Communications Internet Communications DNP3 Communications PakBus Communications SDI-12 Communication Serial Peripheral Interface (SPI) and I2C Some communication services, such as satellite networks, can be expensive to send and receive information. Best practices for reducing expense include: Declare Public only those variables that need to be public. Other variables should be declared as Dim. 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. Specify the size if 24 bytes of possibly unused space is not desired. Declare string variables Public and sample string variables into data tables only as needed. When using GetVariables() / SendVariables() to send values between dataloggers, 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 much more efficient (requires only 1 transaction) than using 10 commands to get 10 single values (requires 10 transactions). Set the datalogger to be a PakBus router only as needed. When the datalogger is a router, and it connects to another router like LoggerNet, it exchanges routing information with that router and, possibly (depending on your settings), with other routers in the network. Network Planner set this appropriately when it is used. This is also set through the IsRouter setting in the Settings Editor. 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 Planner will set this appropriately when it is used. This is also set through the Beacon and Verify settings in the Settings Editor. For information on Designing a PakBus network using the Network Planner tool in LoggerNet, watch the following video. General Serial Communications The datalogger supports two-way serial communication. These communication ports can be used with smart sensors that deliver measurement data through serial data protocols or with devices, such as modems, that communicate using serial data protocols. See "Communication Ports" on page 12 for information on port configuration options. Communication Protocols 43

51 CRBasic instructions for general serial communications include: SerialOpen() SerialClose() SerialIn() SerialInRecord() SerialInBlock() SerialOut() SerialOutBlock() To communicate over a serial port, it is important to be familiar with the protocol of the sensor or device. Refer to the manual of the sensor or device to find its 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. Modbus Communications The datalogger supports Modbus RTU, Modbus ASCII, and Modbus TCP protocols and can be programmed as a Modbus master or Modbus slave. These protocols are often used in Modbus SCADA networks. Dataloggers can communicate with Modbus on all available communication ports. The datalogger supports RTU and ASCII communication modes on RS-232 and RS-485 connections. Modbus has a set command structure. It uses a common bus and addresses each node. CRBasic Modbus instructions include (see CRBasic Editor help for the most recent information on each of these instructions and for program examples): ModbusMaster() ModbusSlave() MoveBytes() For additional information on Modbus, see: Why Modbus Matters: An Introduction How to Access Live Measurement Data Using Modbus Using Campbell Scientific Dataloggers as Modbus Slave Devices in a SCADA Network Because Modbus has a set command structure, programming the datalogger to get data from field instruments is much simpler than from serial sensors. Because Modbus uses a common bus and addresses each node, field instruments are effectively multiplexed to a datalogger without additional hardware. A datalogger goes into sleep mode after 40 seconds of communication inactivity. Once asleep, two packets are required before it will respond. The first packet awakens the datalogger; the second packet is received as data. This would make a Modbus master fail to poll the datalogger, if not using retries. The datalogger, through Device Configuration Utility or the Status table, can be set to keep communication ports open and awake, but at higher power usage. Further information on Modbus can be found at: Communication Protocols

52 Internet Communications See the "Communications Specifications" on page 84 for a list of the internet protocols supported by the datalogger. CRBasic instructions for internet communications include: Relay() Send() Recv() FTPClient() HTTPGet() HTTPOut() HTTPPost() HTTPPut IPInfo() PPPOpen() PPPClose() TCPOpen() TCPClose() Once the hardware has been configured, basic PakBus communication over TCP/IP is possible. These functions include the following: Sending programs Retrieving programs Setting the datalogger clock Collecting data Displaying the current record in a data table Data callback and datalogger-to-datalogger communications are also possible over TCP/IP. For details and example programs for callback and datalogger-to-datalogger communications, consult your network link manual (see IP ADDRESS When connected to a server with a list of IP addresses available for assignment, the datalogger will automatically request and obtain an IP address through DHCP. Once the address is assigned, look in the Settings Editor: Ethernet {information box} to see the assigned IP address. The CR1000X provides a DNS client that can query a DNS server to determine if an IP address has been mapped to a hostname. If it has, then the hostname can be used interchangeably with the IP address in some datalogger instructions. HTTPS The datalogger has the ability to act as an HTTPS server. This can be configured using Device Configuration Utility. DNP3 Communications DNP3 is designed to optimize transmission of data and control commands from a master computer to one or more remote devices or outstations. The datalogger allows DNP3 communication on all available communication ports. CRBasic DNP3 instructions include: DNP() DNPUpdate() DNPVariable() Communication Protocols 45

53 See the CRBasic help for detailed information and program examples. For additional information on DNP3 see: DNP3 with Campbell Scientific Dataloggers Getting to Know DNP3 How to Access Your Measurement Data Using DNP3 PakBus Communications PakBus is a protocol similar in concept to IP (Internet Protocol). By using signatured data packets, PakBus increases the number of communication and networking options available to the datalogger. The datalogger allows PakBus communication on all available communication ports. For additional information, see The Many Possibilities of PakBus Networking. Advantages of PakBus are as follows: Simultaneous communication between the datalogger and other devices. Peer-to-peer communication - no computer required. Special CRBasic instructions simplify transferring data between dataloggers for distributed decision making or control. Data consolidation - other PakBus dataloggers can be used as "sensors" to consolidate all data into one datalogger. Routing - the datalogger can act as a router, passing on messages intended for another Campbell Scientific datalogger. PakBus supports automatic route detection and selection. Short distance networks - a datalogger can talk to another datalogger over distances up to 30 feet by connecting transmit, receive, and ground wires between the dataloggers. In a PakBus network, each datalogger is set to a unique address. The default PakBus address in most devices is 1. To communicate with the datalogger, the datalogger support software must know the datalogger PakBus address. The PakBus address is changed using Device Configuration Utility, datalogger Status table, Settings Editor, or PakBusGraph software. CRBasic PakBus instructions include: GetDataRecord() GetVariables() SendData() SendGetVariables() SendVariables() SDI-12 Communication SDI-12 is a 1200 baud protocol that supports many smart sensors. The datalogger supports SDI-12 communication through two modes transparent mode and programmed mode (see "SDI-12 Port" on page 8 for wiring terminal information). Transparent mode facilitates sensor setup and troubleshooting. It allows commands to be manually issued and the full sensor response viewed. Transparent mode does not record data. See "SDI-12 Transparent Mode" on page 47 for more information. Programmed mode automates much of the SDI-12 protocol and provides for data recording. See "SDI-12 Programmed Mode/Recorder Mode" on page 48 for more information. 46 Communication Protocols

54 CRBasic SDI-12 instructions include: SDI12Recorder() SDI12SensorSetup() SDI12SensorResponse() SDI-12 TRANSPARENT MODE System operators can manually interrogate and enter settings in probes using transparent mode. Transparent mode is useful in troubleshooting SDI-12 systems because it allows direct communication with probes. Transparent mode may need to wait for commands issued by the programmed mode to finish before sending responses. While in transparent mode, the datalogger programs may not execute. Datalogger security may need to be unlocked before transparent mode can be activated. Transparent mode is entered while the computer is in communication with the datalogger through a terminal emulator program. It is easily accessed through a terminal emulator available with Device Configuration Utility and other datalogger support software. Keyboard displays cannot be used. For how-to instructions for communicating directly with an SDI-sensor using a terminal emulator, watch this video. To enter the SDI-12 transparent mode, enter the datalogger support software terminal emulator: 1. Press Enter until the datalogger responds with the prompt CR1000X>. 2. Type SDI12 at the prompt and press Enter. 3. In response, the query Enter Cx Port is presented with a list of available ports. Enter the port number assigned to the terminal to which the SDI-12 sensor is connected, and press Enter. For example, 1 is entered for terminal C1. 4. An Entering SDI12 Terminal response indicates that SDI-12 transparent mode is active and ready to transmit SDI-12 commands and display responses. The terminal-mode utility allows monitoring of SDI-12 traffic by using the watch command (sniffer mode). Watch an instructional this video. or use the following instructions. 1. Enter the terminal mode as described previously. 2. Press Enter until a CR1000X> prompt appears. 3. Type W and then press Enter. 4. In response, the query Select: is presented with a list of available ports. Enter the port number assigned to the terminal to which the SDI-12 sensor is connected, and press Enter. 5. In answer to Enter timeout (secs): type 100 and press Enter. 6. In response to the query ASCII (Y)?, type Y and press Enter. 7. SDI-12 communications are then opened for viewing. Communication Protocols 47

55 SDI-12 Transparent Mode Commands SDI-12 commands and responses are defined by the SDI-12 Support Group ( and are available in the SDI-12 Specification. Sensor manufacturers determine which commands to support. Commands have three components: Sensor address (a): A single character and the first character of the command. Sensors are usually assigned a default address of zero by the manufacturer. The wildcard address (?) is used in the Address Query command. Some manufacturers may allow it to be used in other commands. Command body (for example, M1): An upper case letter (the command ) followed by alphanumeric qualifiers. Command termination (!): An exclamation mark. An active sensor responds to each command. Responses have several standard forms and terminate with <CR><LF> (carriage return line feed). SDI-12 PROGRAMMED MODE/RECORDER MODE The datalogger can be programmed to act as an SDI-12 data recorder or as an SDI-12 sensor using a terminal configured for SDI-12. The SDI12Recorder() instruction automates sending commands and recording responses. With this instruction, the commands to poll sensors and retrieve data are done automatically with proper elapsed time between the two. The datalogger automatically issues retries. See CRBasic Editor help for more information on this instruction. Commands entered into the SDIRecorder() instruction differ slightly in function from similar commands entered in transparent mode. In transparent mode, for example, the operator manually enters am! and ad0! to initiate a measurement and get data, with the operator providing the proper time delay between the request for measurement and the request for data. In programmed mode, the datalogger provides command and timing services within a single line of code. For example, when the SDI12Recorder() instruction is programmed with the M! command (note that the SDI-12 address is a separate instruction parameter), the datalogger issues the am! and ad0! commands with proper elapsed time between the two. The datalogger automatically issues retries and performs other services that make the SDI-12 measurement work as trouble free as possible. For troubleshooting purposes, responses to SDI-12 commands can be captured in programmed mode by placing a variable declared As String in the variable parameter. Variables not declared As String will capture only numeric data. PROGRAMMING THE DATALOGGER TO ACT AS AN SDI-12 SENSOR The SDI12SensorSetup() / SDI12SensorResponse() instruction pair programs the datalogger to behave as an SDI-12 sensor. A common use of this feature is the transfer of data from the datalogger to other Campbell Scientific dataloggers over a single-wire interface (terminal configured for SDI-12 to terminal configured for SDI-12), or to transfer data to a third-party SDI-12 recorder. Details of using the SDI12SensorSetup() / SDI12SensorResponse() instruction pair can be found in the CRBasic Editor help. When programmed as an SDI-12 sensor, the datalogger will respond to SDI-12 commands M, MC, C, CC, R, RC, V,?, and I. The following rules apply: A datalogger can be assigned only one SDI-12 address per SDI-12 port. For example, a datalogger will not respond to both 0M! AND 1M! on SDI-12 port C1. However, different SDI-12 ports can have unique SDI-12 addresses. Use a separate SlowSequence for each SDI-12 port configured as a sensor. 48 Communication Protocols

56 SDI-12 POWER CONSIDERATIONS When a command is sent by the datalogger to an SDI-12 probe, all probes on the same SDI-12 port will wake up. However, only the probe addressed by the datalogger will respond. All other probes will remain active until the timeout period expires. Example: Probe: Water Content Power Usage: Quiescent: 0.25 ma Active: 66 ma Measurement: 120 ma Measurement time: 15 s Timeout: 15 s Probes 1, 2, 3, and 4 are connected to SDI-12 port C1. The time line in the following table shows a 35-second power-usage profile example. For most applications, total power usage of 318 ma for 15 seconds is not excessive, but if 16 probes were wired to the same SDI-12 port, the resulting power draw would be excessive. Spreading sensors over several SDI-12 terminals helps reduce power consumption. Example Power Usage Profile for a Network of SDI-12 Probes Time into Measurement Processes Command All Probes Awake Time Out Expires Probe 1 (ma) Probe 2 (ma) Probe 3 (ma) Probe 4 (ma) Total (ma) Sleep M! Yes Yes D0! Yes Yes Sleep Serial Peripheral Interface (SPI) and I2C Serial Peripheral Interface is a clocked synchronous interface, used for short distance communications, generally between embedded devices. I2C is a multi-master, multi-slave, packet switched, singleended, serial computer bus. I2C is typically used for attaching lower-speed peripheral ICs to processors and microcontrollers in short-distance, intra-board communication. I2C and SPI are protocols supported by the operating system. See CRBasic Editor help for instructions that support these protocols. For additional information on I2C, see Communication Protocols 49

57 Maintaining Your Datalogger Protect the datalogger from humidity and moisture. When humidity levels reach the dewpoint, condensation occurs, and damage to datalogger electronics can result. Adequate desiccant should be placed in the instrumentation enclosure to provide protection and control humidity, and it should be changed periodically. If sending the datalogger to Campbell Scientific for calibration or repair, consult first with Campbell Scientific. If the datalogger is malfunctioning, be prepared to perform some troubleshooting procedures (see "Troubleshooting the Datalogger" on page 59). Many problems can be resolved with a telephone conversation. If calibration or repair is needed, the procedure shown here should be followed when sending the product. Maintenance for your datalogger components include: Datalogger Calibration Datalogger Security Datalogger Enclosures Internal Battery Electrostatic Discharge and Lightning Protection Power Budgeting Updating the Operating System Datalogger Calibration Campbell Scientific recommends factory recalibration every three years. During calibration, all the input terminals, peripheral and communications terminals, operating system, and Flash EEPROM are checked; and the internal battery is replaced. The datalogger is checked to ensure that all hardware operates within published specifications before it is returned. For calibration information, see It is recommended that you maintain a level of calibration appropriate to the application of the datalogger. Consider the following factors when setting a calibration schedule: The importance of the measurements. How long the datalogger will be used. The operating environment. How the datalogger will be handled. See also "About Background Calibration" on page 50. ABOUT BACKGROUND CALIBRATION The datalogger uses an internal voltage reference to routinely self-calibrate to compensate for changes caused by changing operating temperatures and aging. Background calibration calibrates only the coefficients necessary to run the current CRBasic program. These coefficients are reported in the Status table as CalVolts(), CalGain(), CalOffset(), and CalCurrent(). Auto background calibration will be disabled automatically when the scan rate is too high for the background calibration measurements to occur in addition to the measurements contained within the program. The Calibrate() instruction can be used to override or disable background calibration. Disable this background calibration when it interferes with execution of very fast programs and less accuracy can be tolerated. With background calibration disabled, measurement accuracy over the 50 Maintaining Your Datalogger

58 operational temperature range is specified as less accurate by a factor of 10. That is, over the extended temperature range of 55 C to 85 C, the accuracy specification of ±0.08 % of reading can degrade to ±0.8 % of reading with background calibration disabled. If the temperature of the datalogger remains the same, there is little calibration drift if background calibration is disabled. Datalogger Security Datalogger security concerns include: Collection of sensitive data Operation of critical systems Networks accessible by many individuals Some options to secure your datalogger from mistakes or tampering include: Sending the latest operating system to the datalogger. See "Updating the Operating System" on page 57 for more information. Disabling unused services and securing those that are used. This includes disabling Ping to prevent discovery of a datalogger on your network. Setting security codes (see following information under "Security Codes"). Setting a PakBus/TCP password. The PakBus TCP password controls access to PakBus communication over a TCP/IP link. PakBusTCP passwords can be set in Device Configuration Utililty. The following CRBasic instructions also offer provisions for PakBus password protection: o ModemCallBack() o SendVariables() o SendGetVariables() o SendFile() o GetVariables() o GetFile() o GetDataRecord() Setting an FTP username and password in Device Configuration Utility. Setting an AES-128 PakBus encryption key in Device Configuration Utility. This enables encrypted PakBus data transmission. Creating a.csipasswd file for securing HTTP/HTTPS and for providing web interface permissions (see "Creating a.csipasswd File" on page 52 for more information). Enabling HTTPS and disabling HTTP. Tracking signatures. Encrypting program files if they contain sensitive information (see CRBasic help Include() instruction or use the CRBasic Editor File menu, Save and Encrypt option). Hiding program files for extra protection (see CRBasic help FileManage() instruction). Securing the physical datalogger and power supply under lock and key. Monitoring your datalogger for changes by tracking program and operating system signatures, as well as CPU, USR, and CRD file contents. Warning: All security features can be subverted through physical access to the datalogger. If absolute security is a requirement, the physical datalogger must be kept in a secure location. Maintaining Your Datalogger 51

59 SECURITY CODES The datalogger employs a security scheme that includes three levels of security. Security codes can effectively lock out innocent tinkering and discourage wannabe hackers on non-ip based communication links. However, any serious hacker with physical access to the datalogger or to the communications hardware can, with only minimal trouble, overcome the five-digit security codes. Systems adequately secured with security codes are probably limited to the following: Private, non-ip radio networks. Direct links (hardwire RS-232, short haul, multidrop, fiber optic). Non-IP satellite. Landline, non-ip based telephone, where the telephone number is not published. Cellular phone wherein IP has been disabled, providing a strictly serial connection. Methods of enabling security codes include the following: Settings: Security(1), Security(2), and Security(3) are writable variables in the Status table. Device Configuration Utility: Security codes are set on the Deployment tab. SetSecurity() instruction in CRBasic: SetSecurity() is only executed at program compile time. Note: Deleting SetSecurity() from a CRBasic program is not equivalent to SetSecurity(0,0,0). Settings persist when a new program is downloaded that has no SetSecurity() instruction. Up to three levels of security codes can be set. Valid security codes are 1 through (0 confers no security). Security 1 must be set before Security 2. Security 2 must be set before Security 3. If any one of the codes is set to 0, any security code level greater than it will be set to 0. For example, if Security 2 is 0 then Security 3 is automatically set to 0. Security codes are unlocked in reverse order: Security 3 before Security 2, Security 2 before Security 1. Functions affected by each level of security are: Security 1: Collecting data, setting the clock, and setting variables in the Public table are unrestricted, requiring no security code. If Security 1 code is entered, read/write values in the Status, Settings, and DataTableInfo tables can be changed; fields can be edited in the ConstTable; and the datalogger program can be changed or retrieved. Security 2: Data collection is unrestricted, requiring no security code. If the user enters the Security 2 code, the datalogger clock can be changed, values in the Public table can be changed, and read/write DataTable Sample fields can be edited. Security 3: When this level is set, all communication with the datalogger is prohibited if no security code is entered. If Security 3 code is entered, data can be viewed and collected from the datalogger (except data suppressed by the TableHide() instruction). CREATING A.CSIPASSWD FILE The datalogger employs a security scheme that includes three levels of security (see "Datalogger Security" on page 51 for more information). This scheme can be used to limit access to a datalogger that is publicly available. However, the security code is visible in Device Configuration Utility and in the program. In addition, the range of codes is relatively small. To provide a more robust means of security, Basic Access Authentication was implemented with the HTTP API interface in the form of an encrypted password file named.csipasswd. In order to provide read/write access to the web interface, you must create a.csipasswd file. 52 Maintaining Your Datalogger

60 When a file named.csipasswd is stored on the datalogger's CPU drive, basic access authentication is enabled in the datalogger and read/write access to the web interface can be defined. Four levels of access are available: all access denied (0), all access allowed (1), set variables allowed (2), and readonly access (3). Multiple user accounts/levels of access can be defined for one datalogger. Create an encrypted password file or modify an existing password file using Device Configuration Utility: 1. Connect to your device in Device Configuration Utility. 2. Click the Network Services tab, then click the Edit.csipasswd File button. 3. Define your user accounts and access levels. 4. Click Apply. The.csipasswd file is automatically saved to the datalogger s CPU drive. When a.csipasswd file enables basic access authentication, the datalogger's PakBus/TCP Password security setting is not used when accessing the datalogger via HTTP. If the.csipasswd file is blank or does not exist, the default user name is "anonymous" with no password and a user level of read-only. When access to the datalogger web server is attempted without the appropriate security level, the datalogger will return a 401 Authorization Required response, which will prompt the web client to display a user name/password request dialog. If an invalid username or password is entered, the datalogger web server will default to the level of access assigned to anonymous. As noted above, anonymous is assigned a user level of read-only, though this can be changed using Device Configuration Utility. If the numeric security code has been enabled using Device Configuration Utility, the SetSecurity(), instruction, or the Security() Status table settings, and no.csipasswd file is on the datalogger, then that numeric security code must be entered to access the datalogger. If a.csipasswd file is on the datalogger, the User Name and Password employed by the Basic Access Authentication will eliminate the need for entering the numeric security code. Command Syntax Syntax for the commands sent to the web server generally follows the form of: URL?command=CommandName&uri=DataSource&arguments Arguments are appended to the command string using an ampersand (&). Some commands have optional arguments, where omitting the argument results in a default being used. When applicable, optional arguments and their defaults are noted and examples are provided in the CRBasic help (search Web Server/API Commands). Datalogger Enclosures The datalogger and most of its peripherals must be protected from moisture and humidity. Moisture in the electronics will seriously damage the datalogger. In most cases, protection from moisture is easily accomplished by placing the datalogger in a weather-tight enclosure with desiccant and elevating the enclosure above the ground. Desiccant in enclosures should be changed periodically. Warning: Do not completely seal the enclosure if lead-acid batteries are present; hydrogen gas generated by the batteries may build up to an explosive concentration. The following details a typical installation using a Campbell Scientific enclosure. The datalogger has mounting holes through which small screws are inserted into nylon anchors in the backplate. 1. Insert the included nylon anchors into the backplate. Position them to align with the mounting holes on the base of the CR1000X. 2. Holding the CR1000X to the backplate, screw the screws into the nylon anchors. Maintaining Your Datalogger 53

61 Internal Battery The lithium battery powers the internal clock and SRAM when the datalogger is not powered. This voltage is displayed in the LithiumBattery field in the Status table. Replace the battery when voltage is approximately 2.7 Vdc. The internal lithium battery has a three-year life when no external power source is applied. Its life is extended when the datalogger is installed with an external power source. If the datalogger is used in a high-temperature application, the battery life is shortened. To prevent clock and memory issues, it is recommended you proactively replace the battery every 2-3 years, or more frequently when operating continuously in high temperatures. Note: The battery is replaced during regular factory recalibration, which is recommended every 3 years. For more information, see "Datalogger Calibration" on page 50. When the lithium battery is removed (or is depleted and primary power to the datalogger is removed), the CRBasic program and most settings are maintained, but the following are lost: Run-now and run-on power-up settings. Routing and communication logs (relearned without user intervention). Time. Clock will need resetting when the battery is replaced. Final-memory data tables. A replacement lithium battery can be purchased from Campbell Scientific or another supplier. See "Power Requirements" on page 77 for more information. Warning: Misuse or improper installation of the internal lithium battery can cause severe injury. Fire, explosion, and severe burns can result. Do not recharge, disassemble, heat above 100 C (212 F), solder directly to the cell, incinerate, or expose contents to water. Dispose of spent lithium batteries properly. INTERNAL LITHIUM BATTERY SPECIFICATIONS Manufacturer: Tadiran Tadiran Model Number: TL-5903/S Voltage: 3.6 V Capacity: 2.4 Ah Self-discharge Rate: 20 C Operating Temperature Range: 55 to Maintaining Your Datalogger

62 REPLACING THE INTERNAL BATTERY It is recommended that you send the datalogger in for scheduled calibration, which includes internal battery replacement (see "Datalogger Calibration" on page 50). Warning: Any damage made to the datalogger during replacement of the internal battery is not covered under warranty. Remove the two Phillips screws from the back of the panel. 2. Pull one edge of the canister away from the wiring panel to loosen it from the internal connector seatings. 3. Lift the canister edge out of the enclosure tabs. 4. Remove the nuts, then open the clam shell. 5. Remove the lithium battery by gently prying it out with a small slot head screwdriver. 6. Reassemble the datalogger. Take particular care to ensure the canister is reseated tightly into the connectors by firmly pressing them together by hand. Maintaining Your Datalogger 55