Campbell LoggerNet Instruction Manual

Table of Contents

Quick Links

Download this manual

LoggerNet

Version 4.2

Revision: 7/13

C o p y r i g h t

1 9 9 9 - 2 0 1 3

C a m p b e l l

S c i e n t i f i c ,

I n c .

Table of Contents

Troubleshooting

Need help?

Do you have a question about the LoggerNet and is the answer not in the manual?

Questions and answers

Summary of Contents for Campbell LoggerNet

Page 1 LoggerNet Version 4.2 Revision: 7/13 C o p y r i g h t © 1 9 9 9 - 2 0 1 3 C a m p b e l l S c i e n t i f i c ,...
Page 3 The installation and use of this software constitutes an agreement to abide by the provisions of this license agreement. Campbell Scientific grants you a non-exclusive license to use this software in accordance with the following: (1) The purchase of this software allows you to install and use the software on one computer only.
Page 4: Limited Warranty
Campbell Scientific has been advised of the possibility of such damages. Campbell Scientific is not responsible for any costs incurred as a result of lost profits or revenue, loss of use of the software, loss of data, cost of re-creating lost data, the cost of any substitute program, telecommunication access costs, claims by any party other than licensee, or for other similar costs.
Page 5: Table Of Contents
What is LoggerNet? ................. 3-1 3.1.1 What Next? ................3-1 Overview of Major LoggerNet Functions and Associated Software Applications ..............3-2 3.2.1 The Heart of it All – LoggerNet Toolbar ........3-2 3.2.1.1 Toolbar Views ..............3-2 3.2.1.2 Favorites Category ............3-3 3.2.1.3...
Page 6 Table of Contents 3.2.9 Automating Tasks with Task Master........3-10 3.2.10 Managing External Data Storage Devices....... 3-10 3.2.11 Optional Client Products Compatible with LoggerNet ... 3-10 3.2.11.1 LoggerNetData ............. 3-10 3.2.11.2 Data Display Clients............. 3-11 3.2.11.3 Baler ................3-11 3.2.11.4 CSIOPC Server (PC-OPC) ........... 3-11 3.2.11.5 Software Development Kit ...........
Page 7 Avoiding Conflicts with the LoggerNet Server ............. 4-74 4.3.8.1.2 Settings Generated..........4-75 4.3.8.2 Configuring a LoggerNet Server ........4-75 4.3.9 Saving Your Work ..............4-78 4.3.10 Arranging Screen Components ..........4-79 Device Configuration Utility............4-79 5. Real-Time Tools ............5-1 The Connect Screen ................. 5-1 5.1.1 Connecting to the Datalogger —...
Page 8 Table of Contents 5.1.7 Data Displays ................5-13 5.1.7.1 Data Display Limitations..........5-14 5.1.7.2 Numeric Display Screens ..........5-14 5.1.7.2.1 Adding and Removing Values ......5-15 5.1.7.2.2 Display Options ..........5-17 5.1.7.2.3 Right Click Menu Options ......... 5-18 5.1.7.3 Graphical Display Screens..........5-18 5.1.7.3.1 Displaying Values on a Graph ......
Page 9 6.5.2 Buttons ..................6-20 6.5.3 Archiving Troubleshooter Results .......... 6-26 6.5.4 Other Tools in Troubleshooter ..........6-27 LoggerNet Server Monitor ............. 6-27 7. Creating and Editing Datalogger Programs ..7-1 Review of CSI Datalogger Models ..........7-1 Short Cut ..................7-2 7.2.1 Overview...................
Page 10 Table of Contents 7.3.3.8.2 Instruction Panel Preferences......7-35 7.3.3.8.3 Other Options............. 7-35 7.3.3.9 CRBasic Editor Tools Menu......... 7-36 7.3.3.9.1 Edit Instruction Categories ........ 7-36 7.3.3.9.2 Constant Customization ........7-37 7.3.3.9.3 Other Options............. 7-39 7.3.3.10 Available Help Information.......... 7-40 7.3.4 CRBasic Programming............7-40 7.3.4.1 Programming Sequence..........
Page 11 Opening a Data File............8-4 8.1.3.2 Opening Other Types of Files ........8-4 8.1.3.3 Opening a File in Hexadecimal Format......8-4 8.1.4 Viewing a LoggerNet Database Table ........8-4 8.1.4.1 Selecting a Database............8-4 8.1.4.2 Selecting a Table ............8-8 8.1.5 Importing a CSV File..............
Page 12 Table of Contents 8.1.7.3 XY Plot................. 8-22 8.1.7.3.1 Selecting Data to be Plotted ....... 8-23 8.1.7.3.2 XY Plot Toolbar..........8-23 8.1.7.4 Rainflow Histogram ............. 8-24 8.1.7.4.1 Selecting Data to be View........8-25 8.1.7.4.2 Options............... 8-26 8.1.7.4.3 Rainflow Histogram Toolbar ......8-26 8.1.7.5 FFT ................
Page 13 CoraScript ..................10-7 10.2.1 CoraScript Fundamentals ............10-7 10.2.2 Useful CoraScript Operations ..........10-7 10.2.2.1 Connecting to the LoggerNet Server......10-8 10.2.2.2 Checking and Setting Device Settings ......10-8 10.2.2.3 Creating and using a Network Backup File....10-8 10.2.2.4 Hole Management ............10-9 10.2.2.5 Scripting CoraScript Commands........
Page 14 Table of Contents 10.3.3.4 Clock Settings............. 10-16 10.3.3.5 Data Tab ..............10-18 10.3.4 Deleting a Station ..............10-18 10.3.5 Organization of RWIS Data in LoggerNet ......10-18 10.4 File Format Convert ..............10-19 10.4.1 Overview ................10-19 10.4.2 Options .................. 10-20 10.5...
Page 15 14. Troubleshooting Guide .........14-1 14.1 What’s Changed? ................14-1 14.2 LoggerNet Server Problems ............14-1 14.2.1 Starting LoggerNet and Connecting to the Server ....14-1 14.2.2 Socket Errors................14-2 14.2.3 Data Collection Issues............. 14-4 14.3 Application Screen Problems ............14-4 14.4...
Page 16 Table Data Overview............... C-5 Default Tables ................. C-6 D. Software Organization ..........D-1 LoggerNet/Client Architecture ............D-1 LoggerNet Server Data Cache............D-1 D.2.1 Organization ................D-1 D.2.2 Operation.................. D-1 D.2.3 Retrieving Data from the Cache ..........D-2 D.2.4 Updating Table Definitions ............D-2...
Page 17 Table of Contents Directory Organization..............D-3 D.3.1 C:\CampbellSci Directory (Working Directory)...... D-3 D.3.2 C:\Program Files\CampbellSci\LoggerNet Directory (Program File Directory) ............D-4 E. Log Files ..............E-1 Event Logging..................E-1 E.1.1 Log Categories ................E-1 E.1.2 Enabling Log Files ..............E-2 E.1.3 Log File Message Formats ............E-2 E.1.3.1...
Page 18 Table of Contents 7-5. Operators and Functions..............7-59 7-6. Editor Keystrokes ................7-64 8-1. Comma Separated, Field Formatted, Printable ASCII, and Table Oriented ASCII Input File Format Types ......8-41 8-2. Example of Event Driven Test Data Set......... 8-50 8-3. Processed Data File Using Option C ..........
Page 19: Preface - What's New In Loggernet 4
Software development kits and standalone clients were released to provide additional functionality. One of the main efforts in the development of LoggerNet 3.1 was to incorporate support for the CR1000 datalogger. This included datalogger management (connect, collect data, set clock, send program, etc.) in...
Page 20 See below for more details on what is new in LoggerNet 4.0 and each individual application. One of the main efforts in the development of LoggerNet 4.1 was the ability to use LNDB databases with View Pro. The ability to lock the timestamp column on the left of the data file has also been added to View Pro.
Page 21 Poll for Statistics check box on the datalogger’s Schedule tab in the Setup Screen that must be enabled to poll for these statistics.) The Task Master has been integrated into the LoggerNet server. This allows for remote administration of the Task Master. (See Section 9.1.3 Remote Administration of the Task Master for conditions that must be met for remote administration of the Task Master.)
Page 22 LoggerNet into a file. LoggerNet Admin and LoggerNet Remote enhance the capabilities of LoggerNet by providing management tools for more complex networks. The difference in the two is that LoggerNet Admin offers a complete LoggerNet package, while LoggerNet Remote, which was designed to be run remotely, does not include the LoggerNet server.
Page 23 The Setup Screen now has the option of being used in an EZ View or a Standard View. The Standard View is similar to the Setup Screen in older versions of LoggerNet. In the EZ View, the EZ Setup Wizard is used to add dataloggers and edit their settings.
Page 24: Task Master
Section 4, Setting up Datalogger Networks, for information on how the Maximum Time On-Line setting will affect a connection made using LoggerNet Admin or LoggerNet Remote 4.0 to connect to a remote server running an older version of LoggerNet.) The Pause Data Displays option has been moved to the Edit menu. (In previous versions it was available as a check box on the Connect Screen.)
Page 25 Preface — What’s New in LoggerNet 4? New sensor files have been added for the CMP3 Pyranometer, the IRR-P Precision Infrared Temperature Sensor, the JC Ultrasonic Depth Sensor, the CNR2 Net Radiometer, the CS106 Barometric Pressure Sensor, the OBS-3+ Turbidity Sensor, the 03002 Wind Speed and Direction Sensor, the 105E...
Page 26 Preface — What’s New in LoggerNet 4? over a slow or unreliable communication link where the attempt to receive table definitions back from the datalogger fails. Clear Undo/Redo List on File Save – Clears the change tracking in the program when the file is saved. Otherwise change tracking is kept until the file is closed.
Page 27: View Pro
View Pro View Pro is included for the first time in LoggerNet 4.0. It maintains the ease of use of our former data file viewer with greatly enhanced capabilities. Large files can be loaded more quickly. Scrolling is more responsive for large files.
Page 28: Network Planner
Network Planner The Network Planner, a graphical application that assists the user in designing PakBus datalogger networks, is introduced for the first time in LoggerNet 4.0. The Network Planner allows the development of a model of the PakBus network, proposes and verifies valid connections between devices, and allows integration of the model directly into LoggerNet 4.0.
Page 29 Convert, TroubleShooter, Network Planner, PakBus Graph, LogTool, the Device Configuration Utility, Data Export, and the RWIS Administrator. NOTE Available alternate language packages are provided by Campbell Scientific’s international representatives or on the CSI website. They are not included in a standard LoggerNet installation.
Page 30 Preface — What’s New in LoggerNet 4? xxvi...
Page 31: System Requirements
Section 1. System Requirements 1.1 Hardware and Software LoggerNet is a collection of 32-bit programs designed to run on Intel-based computers running Microsoft Windows operating systems. The recommended minimum computer configuration for running LoggerNet is Windows XP, Windows Vista, or Windows 7 because they offer the most stable operating environment.
Page 32 Section 1. System Requirements...
Page 33: Cd-Rom Installation
If you choose to purchase LoggerNet, you will need to run the install program on the LoggerNet CD and input the CD Key from the back of your CD case. This can be done either before or after the 30-day trial period has expired.
Page 34: Upgrade Notes
LoggerNet. 2.2 Upgrade Notes If you have any version of LoggerNet 3 installed on your computer, when you run the installation the existing version will be updated with the new files. If you have any version of LoggerNet 2 installed, you can choose to upgrade that installation, or install LoggerNet 4.x separately while leaving the previous...
Page 35: Loggernet Directory Structure And File Descriptions
C:\Program Files\Campbellsci\LoggerNet directory. This includes the executables, DLLs, and most of the application help files. This directory does not need to be included in back up efforts. LoggerNet and its applications rely on registry entries to run correctly; therefore, any restoration of the program should be done by reinstalling the software from the original CD.
Page 36 Lib directory – The Lib directory is a library directory for several of the LoggerNet applications. The Compilers folder holds all of the compilers for the CRBasic Editor, except for the CR200 compilers, which are stored in the...
Page 37: Backing Up The Network Map And Data Files
Device Configuration Utility. LoggerNet directory – The ASCII data files that are saved to disk as a result of data collection from the dataloggers are stored to the LoggerNet directory with a *.dat extension.
Page 38: Performing Scheduled Backups
LoggerNet cache, the name of the backup file, and the number of backup files that will be kept before the oldest is overwritten 2.3.2.3 Performing Backups from the Task Master...
Page 39: Restoring The Network From A Backup File
The data cache files contain all of the data that has been collected from the dataloggers by the LoggerNet server. These files are kept open (or active) as long as data is being stored to the file.
Page 40: Program Crashes
Some users may desire to run LoggerNet as a service, so that in the event of a loss of computer system power LoggerNet will resume data collection and scheduled task activities when power is restored to the computer and it “boots up”.
Page 41: Issues With Running Loggernet As A Service
You will be asked to enter and confirm a password for the LoggerNet user account. The password you enter can later be used to log in to the computer as the LoggerNet user. The password can be changed by pressing the Options button and then pressing Change Password.
Page 42: Network Drives
Section 2. Installation, Operation and Backup Procedures Giving the LoggerNet user write access This is the process for giving the LoggerNet user write access to a designated directory in Windows XP. The process in other operating systems is similar. •...
Page 43 This is usually quite safe since: 1) no other application should be trying to use this port, and 2) the server will only respond to LoggerNet- specific messages on this port (it will not run viruses or other unauthorized bits of code).
Page 44 Section 2. Installation, Operation and Backup Procedures 2-12...
Page 45: Introduction
Introduction 3.1 What is LoggerNet? LoggerNet is a software application that enables users to set up, configure, and retrieve data from a network of Campbell Scientific dataloggers and share this data over an Ethernet communications network. This software application is designed to run under Windows XP, Windows Vista, and Windows 7.
Page 46: Overview Of Major Loggernet Functions And Associated Software Applications
LoggerNet, or on remote computers running LoggerNetData, LoggerNet Admin, or LoggerNet Remote. Note that the LoggerNet Toolbar must be up and running (or LoggerNet must be running as a service) and Remote Connections must be enabled for remote computers to access a LoggerNet server.
Page 47: Favorites Category
Favorites tab. The Available Applications column shows all applications that are available in LoggerNet. (Press the + sign next to a category to show the applications in that category.) An application can be added to the Favorites category by selecting it in the Available Applications column and pressing the right arrow key.
Page 48: Toolbar Menus
Check for Updates – Opens Campbell Scientific’s website to check for updates to LoggerNet. Give Feedback on LoggerNet – Opens a form on our website which allows you to provide feedback on LoggerNet to Campbell Scientific. About LoggerNet – Displays version and copyright information for LoggerNet.
Page 49: Alternate Language Support
(e.g., LocalHost:6700 or 192.168.7.123:6700). NOTE If LoggerNet is being run as a service (available in LoggerNet Admin), you use LoggerNet Service Manager to specify an alternate working directory or IP port.
Page 50: Loggernet Admin/Loggernet Remote
One of these additions is the ability to access a LoggerNet server from a remote computer. To do this, you need to “log in” to the remote server. All of the standard LoggerNet clients that are capable of accessing remote servers (such as Setup, Connect, or Status) include a Select Server dialog box under the application’s File menu.
Page 51: Real Time Tools
Back up the Network Map and Data Files). 3.2.4 Real Time Tools LoggerNet’s real-time tools are used to connect to a datalogger, set the clock and send a program to the datalogger, and view the data being collected from the datalogger by the LoggerNet server. These tools include the Connect Screen and RTMC.
Page 52: Network Management Tools
LoggerNet Admin includes some tools which are useful when managing large networks, or when you need to manage networks with several users. The LoggerNet Service Manager is a utility that allows you to install and run LoggerNet as a service. Refer to Section 2.4, Installing/Running LoggerNet as a Service, for additional information.
Page 53: Working With Data Files
The editor checks for program validity and offers many user-configurable options to make editing long programs easier. Edlog is the tool to create and edit datalogger programs for all Campbell Scientific dataloggers except the CR200 Series, CR1000, CR3000, CR5000, CR800 Series, and CR9000.
Page 54: Automating Tasks With Task Master
TOA5, Array Compatible CSV, or CSIXML format (TOB2/TOB3 files can also be converted to TOB1 format). TOB files are binary files that are either created by LoggerNet during collection or are collected directly from a compact flash or PCMCIA card installed in a CRX000 datalogger. A command line file converter, toA_to_tob1, is also included in LoggerNet.
Page 55: Data Display Clients
Data Filer does not collect data from a datalogger directly, but from the data cache. Therefore, data collection must occur in LoggerNet (either by a scheduled or manual data collection), for the data to be available to the Data Filer.
Page 56 Section 3. Introduction often explain the purpose of a control or a suggested action. For text boxes where some of the text is hidden, the full text will appear in the hint. 3-12...
Page 57: Setup Screen – Ez View (Ezsetup Wizard)
Section 4. Setting up Datalogger Networks The EZ and Standard Views of the Setup Screen provide ways to create and maintain the communications link and data collection schedules for a network of dataloggers. The EZ View uses the EZSetup Wizard which walks you through the setup step-by-step. In the Standard View, you add devices and configure their settings on your own.
Page 58: Setting Up Datalogger Networks
Setup Screen or Connect Screen. The Data Files step is where you define what data tables, or final storage areas, should be collected by LoggerNet and saved to disk. If you used the EZSetup...
Page 59: Setup Screen - Standard View
Definition button to retrieve the table names. The Data Files step also has a Table Collected During Data Collection (or Enabled for Scheduled Collection) field. When enabled, LoggerNet will collect that table or final storage area from the datalogger on a manual or scheduled data collection attempt.
Page 60: Adding Devices To The Network
Section 4. Setting up Datalogger Networks The number of tabs will vary, based upon the type of device that is selected. Some devices may have only hardware and notes tabs, while other devices, such as dataloggers, have several tabs. 4.2.1 Adding Devices to the Network Devices are added to the device map in the order that they appear in your communications link.
Page 61 Section 4. Setting up Datalogger Networks The contents of the Add Device window will change as each device is added to the network map. Only those devices that are valid components to add to the last device added will be shown. Continue to add devices in this manner until your network map is complete.
Page 62: Applying Changes, Undo And Redo
A keyboard shortcut Ctrl+D will also delete the selected device. 4.2.2 Applying Changes, Undo and Redo The device map is not saved or entered in LoggerNet until you click the Apply button at the bottom of the screen. You can build a complete network and set up the configurations for all of the devices without applying.
Page 63: Renaming Network Devices
Advanced Call-Back Enabled – Enabling call-back tells LoggerNet to watch for a call- back from the datalogger on this port. If there is a phone modem attached it will be set to accept incoming calls.
Page 64: Ipport (Internet Protocol Serial Port)
2 seconds. Delay Hangup – The amount of time, in seconds and milliseconds, that LoggerNet should delay before hanging up the link to the device. If a new command to the device is issued before the delay has expired, communication will not be terminated.
Page 65: Tapiport (Telephony Api)
This option is useful for a datalogger doing TCP call-back from behind a firewall. In this case, it is not possible to create a TCP connection from LoggerNet to the datalogger and any time spent attempting to do so will be wasted and may result in missing incoming connection attempts.
Page 66 Delay Hangup – The amount of time, in seconds and milliseconds, that LoggerNet should delay before hanging up the link to the device. If a new command to the device is issued before the delay has expired, communication will not be terminated.
Page 67: Datalogger
When this box is selected, the datalogger is enabled for communication. Call-back Enabled – Enabling call-back tells LoggerNet to watch for a call- back from this datalogger. The parent PakBus port will be set up to receive incoming calls.
Page 68 Delay Hangup – The amount of time, in seconds and milliseconds, that LoggerNet should delay before hanging up the link to the device. If a new command to the device is issued before the delay has expired, communication will not be terminated.
Page 69: Schedule Tab
When adding a new device to the network, this field will not show up until after the Apply button has been pressed. The ID will be assigned automatically by LoggerNet, but can be changed by the user. This allows the user to designate unique addresses for all BMP1 devices across multiple LoggerNet networks.
Page 70 Entering a zero for any of the intervals below will cause CAUTION LoggerNet to try and collect as fast as possible. Collection Interval – This is the interval at which the datalogger will be checked for new data. If this interval is set at 1 hour, new data will be collected from the datalogger every hour.
Page 71 LoggerNet will immediately try to perform a collection. In some cases, this may not be the desired behavior. Selecting the Stay On Collect Schedule check box will cause LoggerNet to always wait until the next even Collection Interval to perform a collection.
Page 72 LoggerNet. Since the transmission of these records is unacknowledged, there is a possibility that the data will be lost. If LoggerNet doesn’t receive a record for any reason, a hole is created. If the Data Advise or One Way Data hole collection check box is selected, LoggerNet will attempt to contact the datalogger and request the missing records.
Page 73: Final Storage Area 1 And 2 Tab (Edlog Dataloggers With Mixed-Array Operating System)
If the data is only going to be used within LoggerNet for display on the Connect Screen graph or numeric display, or for RTMC, you can choose no output file and a limited amount of data will be kept in LoggerNet’s internal data cache.
Page 74: Data Files Tab (Crbasic Dataloggers, And Edlog Dataloggers With Table Data And Pakbus Operating Systems)
If this is the first call to a datalogger there might be a lot of historical data stored. When Collect All on First Collection is checked, LoggerNet will collect all data in the datalogger the first time data is collected. If Collect All on First Collection is not checked, the first call to the datalogger will collect the number of arrays specified in the Arrays to Collect on First Collection field.
Page 75 If the data is only going to be used within LoggerNet for display on the Connect Screen graph or Numeric Display, or for RTMC, you can choose no output file and the data will only be kept in LoggerNet’s internal data cache...
Page 76 Therefore, fewer records than the number specified may be collected. Get Table Definitions – When this button is pressed, LoggerNet will query the datalogger for its table definitions. This should only be needed the first time connecting to a station or when the datalogger program has changed.
Page 77: Clock Tab
Enabled – Select this box to automatically compare the datalogger’s clock to the LoggerNet server PC’s clock based on the schedule defined by the other parameters on this tab. If the datalogger’s time differs from the server’s time by more than a specified amount, the datalogger’s clock will be set to the...
Page 78: Program Tab
LoggerNet server. Table-based dataloggers store program information in the table definitions. If the table definitions have been retrieved from the datalogger, LoggerNet should know the name of the running program. However, mixed-array dataloggers do not store the program name internally.
Page 79: Phonebase
PhoneBase has only Hardware and Notes tabs. This device must be properly installed and configured in the operating system to use one of the computer’s ComPorts before it can be used by LoggerNet. Standard Communications Enabled – Before communications can take place, all devices in the chain must have the Communications Enabled box checked.
Page 80: Phoneremote
Delay Hangup – The amount of time, in seconds and milliseconds, that LoggerNet should delay before hanging up the link to the device. If a new command to the device is issued before the delay has expired, communication will not be terminated.
Page 81: Rfbase
However, for manual connections from the Connect Screen, it is always best to manually disconnect rather than relying on LoggerNet to disconnect for you. When the device is contacted on a schedule, communication with the device will be terminated once this time limit is exceeded.
Page 82: Rfremote
Delay Hangup – The amount of time, in seconds and milliseconds, that LoggerNet should delay before hanging up the link to the device. If a new command to the device is issued before the delay has expired, communication will not be terminated.
Page 83: Rfbase-Td
RF Polling Interval plus the Computer Offset when collecting the data from the base modem. If it is desired to have LoggerNet poll the RFBase-TD for data more frequently than the interval established by the RF Polling Interval and Computer Offset settings, the Computer Poll Interval should be set to a non-zero value.
Page 84 RF Poll Offset = X Computer Offset = 4 minutes 47 seconds Computer Poll Interval = 0 LoggerNet will query the RF Base 12 times per hour at: XX:04:47, XX:09:47, XX:14:47, XX:19:47, XX:24:47, XX:29:47, XX:34:47, XX:39:47, XX:44:47, XX:49:47, XX:54:47, XX:59:47...
Page 85 RFBase-TD for data. When this setting is at its default value of 0, LoggerNet will contact the RFBase-TD at the RF Polling Interval plus the Computer Offset. If this setting is changed to a non-zero value, LoggerNet will 4-29...
Page 86 Computer Offset. Delay Hangup – The amount of time, in seconds and milliseconds, that LoggerNet should delay before hanging up the link to the device. If a new command to the device is issued before the delay has expired, communication will not be terminated.
Page 87: Rf Remotetd
Section 4. Setting up Datalogger Networks Adjusted Server Date/Time – Displays the date and time for the computer on which the LoggerNet server is running. This value will be displayed/updated only when the Check Clocks button is pressed. Station Date/Time – Displays the date and time for the RFBase. This value will be displayed/updated only when the Check Clocks button is pressed.
Page 88: Md9 Base
A verify interval of zero causes LoggerNet to use a default verify interval of 2.5 times the beacon interval. If the beacon interval is also zero, the default verify interval is 5 minutes.
Page 89 Delay Hangup – The amount of time, in seconds and milliseconds, that LoggerNet should delay before hanging up the link to the device. If a new command to the device is issued before the delay has expired, communication will not be terminated.
Page 90: Md9 Remote
However, for manual connections from the Connect Screen, it is always best to manually disconnect rather than relying on LoggerNet to disconnect for you. When the device is contacted on a schedule, communication with the device will be terminated once this time limit is exceeded.
Page 91: Rf400
Section 4. Setting up Datalogger Networks If you are using LoggerNet Admin or LoggerNet Remote 4.0 and NOTE using the Connect Screen to connect to a remote server that is running an older version of LoggerNet, the behavior will be different than described above.
Page 92: Rf400 Remote
Attention Character. However, if the RF400 is being used in a communications link that includes a phone modem, you will most likely need to change this character in the RF400 radio setup and on LoggerNet’s Setup Screen. Most phone modems use + as the reset character, and sending this character unexpectedly will reset the modem and terminate the communications link.
Page 93 The format for this field is 00 h(ours) 00 m(inutes) 00 s(econds). NOTE If you are using LoggerNet Admin or LoggerNet Remote 4.0 and using the Connect Screen to connect to a remote server that is running an older version of LoggerNet, the behavior will be different than described above.
Page 94: Generic Modem
Max Time On-Line is reached. The format for this field is 00 h(ours) 00 m(inutes) 00 s(econds). If you are using LoggerNet Admin or LoggerNet Remote 4.0 and NOTE using the Connect Screen to connect to a remote server that is running an older version of LoggerNet, the behavior will be different than described above.
Page 95: Pakbusport
Delay Hangup – The amount of time, in seconds and milliseconds, that LoggerNet should delay before hanging up the link to the device. If a new command to the device is issued before the delay has expired, communication will not be terminated.
Page 96 When this box is selected, the PakBus port is enabled for communication. PakBus Port Always Open – The computer running the LoggerNet server is included as a PakBus device in the network. Because of the nature of broadcast messages within the Pakbus network, the computer can keep the PakBus port open, and therefore, can “listen”...
Page 97 A verify interval of zero causes LoggerNet to use a default verify interval of 2.5 times the beacon interval. If the beacon interval is also zero, the default verify interval is 5 minutes.
Page 98: Pakbus Router
Select a PakBus port in the device map and press Start Search to have LoggerNet query the network for devices. When a device is found, its PakBus address will be added to the Node PakBus ID column. When Get Device Type is pressed, the type of device (e.g., CR1000, CR10X-PB) will be displayed in...
Page 99: Pakbusport Hd
Max Time On-Line is reached. The format for this field is 00 h(ours) 00 m(inutes) 00 s(econds). If you are using LoggerNet Admin or LoggerNet Remote 4.0 and NOTE using the Connect Screen to connect to a remote server that is running an older version of LoggerNet, the behavior will be different than described above.
Page 100: Pakbustcpserver
A verify interval of zero causes LoggerNet to use a default verify interval of 2.5 times the beacon interval. If the beacon interval is also zero, the default verify interval is 5 minutes.
Page 101 A verify interval of zero causes LoggerNet to use a default verify interval of 2.5 times the beacon interval. If the beacon interval is also zero, the default verify interval is 5 minutes.
Page 102: Serialportpool
045, and 6 instead of 006). Maintained Nodes This box is used to cause LoggerNet to maintain a connection with a range of dataloggers attached to the PakBus TcpServer. LoggerNet waits for an incoming connection from a datalogger in the range. Once an incoming connection has been established with a datalogger in the range, the connection is maintained.
Page 103 For more information on modem pooling, refer to LoggerNet’s online help. When using pooled modems, the modems should all be such that NOTE any of the modems/phone lines could be used in conjunction with any device that has it as part of its modem pool.
Page 104 Time is cumulative for all devices in the network. Delay Hangup – The amount of time, in seconds and milliseconds, that LoggerNet should delay before hanging up the link to the device. If a new command to the device is issued before the delay has expired, communication will not be terminated.
Page 105: Terminalportpool
With pooled devices, multiple terminal server/phone modem combinations can be specified for each datalogger. That way, LoggerNet is not restricted to the use of a single base modem when calling a particular station. When calling a station, LoggerNet will decide which modem from a group (pool) of modems to use.
Page 106 For more information on modem pooling, refer to LoggerNet’s online help. NOTE When using pooled modems, the modems should all be such that any of the modems/phone lines could be used in conjunction with any device that has it as part of its modem pool.
Page 107 Time is cumulative for all devices in the network. Delay Hangup – The amount of time, in seconds and milliseconds, which LoggerNet should delay before hanging up the link to the device. If a new command to the device is issued before the delay has expired, communication will not be terminated.
Page 108: Setting Up Scheduled Data Collection
One of the goals in datalogging applications is to retrieve the data from the datalogger’s memory to a computer so that it can be analyzed further. LoggerNet can be used to retrieve the data from the datalogger manually, on demand, or you can set up an automatic data collection schedule. When the schedule is enabled and LoggerNet is up and running, the LoggerNet server will initiate calls to the datalogger on the defined schedule and collect its data.
Page 109: Intervals
4.2.5.2.2 Data Collection Setting Intervals The collection interval at which the LoggerNet server requests new data from the datalogger is set up on the Schedule tab for that datalogger in the Setup Screen.
Page 110: Communications Path Considerations
Data File or Final Storage tab. The Schedule tab is used to define the interval on which the LoggerNet server will check the datalogger for new data. If new data exists, it will be stored in the data files and the LoggerNet data cache.
Page 111 Section 4. Setting up Datalogger Networks You should check the directory path and the data file options to make sure the files are where you want them and in the right format. Note that for table- based dataloggers, each table must be configured separately (i.e., selected for collection, file name provided, file format specified, etc.).
Page 112: Setting The Clock
A datalogger’s Clock tab can be used to define a schedule at which an automatic clock check will be performed. The datalogger’s clock will be set if it varies from the LoggerNet server’s clock more than the amount of time specified in the Allowed Clock Deviation field.
Page 113: Sending A Program To The Datalogger From Setup
Current Program fields. To send a new program, press the Send button. For mixed-array dataloggers, if the datalogger currently has a program running in it but LoggerNet is not aware of that program, you can Associate a program with the datalogger. When a program is associated with a datalogger, input location labels and final storage values will be available for viewing on LoggerNet’s Numeric and Graphical Displays.
Page 114: Pakbus Settings
4.2.8.1.2 PakBus Settings The LoggerNet PakBus Settings are used to set up the PakBus ID for one or more PakBus ports in LoggerNet. LoggerNet can be configured so that each PakBus port in the network map will be an independent PakBus network (where communication between PakBus devices exists only in that network), or so that all PakBus ports in the network map are part of one PakBus network.
Page 115: Troubleshooting Tips
IPPort’s Hardware tab of the Setup Screen (AirLink Modem Name). 4.2.8.1.4.1 Troubleshooting Tips If the computer on which the LoggerNet server is running is set up behind a firewall, the administrator of that firewall must open a hole in the firewall to allow the incoming notifications to reach the server.
Page 116: Troubleshooter
Network Map and Data Files, for more information. 4.2.10 Selecting a Remote Server If you are using LoggerNet Admin or LoggerNet remote, you can connect to a LoggerNet server running on a different computer over a TCP/IP connection.
Page 117 Section 4. Setting up Datalogger Networks Press the New Subnet button to add a new subnet. You will be asked to enter a name for the subnet. All of the dataloggers that are not assigned to a subnet will be shown in the Unassigned Dataloggers column. Select a datalogger and press the right arrow key to add it to the current subnet.
Page 118: Network Planner
A station is created by adding a root device to the Drawing Canvas. Examples of root devices include PakBus dataloggers, the LoggerNet server, as well as radio and phone modems. Once the root device is added to the model, any peripherals that connect to the root device are added.
Page 119: Adding A Background Image
Section 4. Setting up Datalogger Networks 4.3.2.1 Adding a Background Image A background image can be associated with the model by using the Options | Change the Background Image menu item. When you select this menu item, a file selection dialog will be shown and you will be allowed to select a bitmap image file for the background.
Page 120 Section 4. Setting up Datalogger Networks Using the Scroll Buttons Navigation buttons that can be used to scroll the model canvas are highlighted in the image below. The following buttons and features are associated with this control: Arrow Buttons–Pressing any arrow button will scroll the drawing canvas in the direction of the arrow.
Page 121: Changing The Canvas Scale
Section 4. Setting up Datalogger Networks Using the Mouse While the Hand Tool is selected by pressing the hand icon on the toolbar, you can scroll the drawing canvas by holding down the left mouse button while the mouse pointer is over a blank area of the canvas and dragging the mouse in the desired direction.
Page 122: Adding Stations Links
Section 4. Setting up Datalogger Networks icon. If you then click the left mouse button, the dialog box shown below will appear. You must select the communication interface for the new peripheral from the dialog list box. These interfaces are prioritized by the Network Planner, such that the links considered the best are listed at the top.
Page 123 Section 4. Setting up Datalogger Networks When the canvas is operating in this mode, the mouse cursor changes from a hand to a jagged line. While in this mode, you can click on a station icon to indicate the first device in the link. If that device can support a new link, a small green “+”...
Page 124: Adding Activities
• Scheduled polling from LoggerNet to a datalogger • Initiation of call-back data polling from a datalogger to LoggerNet (this is a specialization of the set variable transaction) • Transmission of one-way data messages from a datalogger to either LoggerNet or to another datalogger •...
Page 125 Section 4. Setting up Datalogger Networks Aside from providing a means of documentation, activities in the Network Planner model serve an important role in specifying the intervals at which data will be expected to be transmitted over network links. The Network Planner will use these intervals to determine appropriate values for neighbor verification interval settings Activities can be added to the model by using the Activity Tool icon...
Page 126 Section 4. Setting up Datalogger Networks Source Device – Specifies the device that will initiate the activity. This choice box will be populated with the list of all devices in the model that are capable of originating activities. These devices will be identified by their station names and device names (generally the device type) separated by a colon character.
Page 127: The Station Summary
Section 4. Setting up Datalogger Networks 4.3.7 The Station Summary The station summary is a view that displays details about the station that is currently selected on the drawing canvas. By default, it is shown in the lower right-corner of the Network Planner window. This view provides the following features: •...
Page 128: Configuring Devices
4.3.8 Configuring Devices The Configure Devices panel lists tasks that need to be completed before the network can be deployed. These tasks include configuring any LoggerNet servers and writing settings to devices. The Configure Devices panel is divided into two sections. The list box at the top lists all of the Configure Devices items...
Page 129: Configuring Using The Device Configuration Protocol
Section 4. Setting up Datalogger Networks and provides check-boxes that allow these items to be checked off to indicate when an item has been completed. The bottom portion of the panel displays a more detailed description of the selected item. If the item has been completed, the description will include the date and time when it was completed.
Page 130: Avoiding Conflicts With The Loggernet Server
Utility or from within PakBus Graph. 4.3.8.1.1 Avoiding Conflicts with the LoggerNet Server If the Network Planner was started by the LoggerNet tool bar and a local LoggerNet server is reported to be running, the dialog box shown below will appear.
Page 131: Settings Generated
This dialog will not be shown if the Network Planner is launched outside of the LoggerNet tool bar or if there is no local server reported to be running. 4.3.8.1.2 Settings Generated The settings for the device will be generated from information contained in the Network Planner model including device links and activities between devices.
Page 132 Model Prefix – This field allows you to enter a string that will be placed at the beginning of the name for every device in LoggerNet’s network map that the Network Planner generates. If specified, this value will appear in the names followed by an underscore character.
Page 133 If you click on the Connect button in the Configure LoggerNet dialog, the Network Planner will attempt to connect to the specified server address and will log in using the specified user name and password.
Page 134: Saving Your Work
Section 4. Setting up Datalogger Networks The colors of items in this dialog indicate the impact they may have on the operation of devices that are already in the LoggerNet network map. These are coded as follows: Green – The change is merely additive (adding new devices, for instance) and is unlikely to have any noticeable impact on the workings of existing devices.
Page 135: Arranging Screen Components
4.4 Device Configuration Utility The Device Configuration is used to set up PakBus information in PakBus- capable dataloggers and to configure peripheral communication devices. Refer to Section 10, Utilities Installed with LoggerNet, for information on the Device Configuration Utility. 4-79...
Page 136 Section 4. Setting up Datalogger Networks 4-80...
Page 137: Real-Time Tools
Section 5. Real-Time Tools LoggerNet’s real-time tools are used to manage your stations in the datalogger network. Tools are provided for sending new programs, setting the clock, toggling ports and flags, collecting data, and displaying data numerically and graphically. 5.1 The Connect Screen The Connect Screen provides a real-time connection to a datalogger in the datalogger network.
Page 138 When you select the Connect button the animated graphic will indicate an active connection state. It will show that LoggerNet is trying to establish the connection; the two connectors join together when the connection is made. You can also connect to the datalogger by double clicking the datalogger name...
Page 139: Data Collection
If LoggerNet fails to make a connection to the datalogger, it will time out and display an error message that it could not connect. It will immediately attempt the connection again and will continue trying until the user clicks Cancel.
Page 140: Custom Collection
Collection, scheduled data collection will be suspended. The directory where the files are stored for custom collection is separate from the files for scheduled collection data and by default is a Data directory under the LoggerNet directory (e.g., C:\CampbellSci\LoggerNet\Data). File Format This option is used to select the file format in which to store the collected data.
Page 141: Table-Based Dataloggers
− Collect All Since Last Collection – When this option is selected, LoggerNet will attempt to collect all the data since the last Custom Collection from the datalogger. Note that separate data collection pointers are kept for the Custom Collection option; therefore, collecting from this window will not affect data files created by scheduled data collection or a manually initiated collection from the main Connect Screen.
Page 142 Collection, scheduled data collection will be suspended. The default data file names for custom collection are separate from the files for scheduled collection data and by default are placed in a Data directory under the LoggerNet directory. Collect Mode −...
Page 143 − Data Since Last Collection will retrieve the data stored since the last time a custom collection was performed. LoggerNet keeps track of the records collected from each table every time a custom collection is executed. This option will work even if the last custom collection used a different option.
Page 144: Ports And Flags
Click the button next to the flag or port to turn it on or off. You do not have to be actively connected to the datalogger to toggle a port or flag. If you are not connected, when the port or flag is toggled, LoggerNet will connect to the datalogger, make the change, and disconnect.
Page 145 The first time a program is sent to a datalogger, LoggerNet will look for a Public array with the name of Flag in the program. If a Flag array is found, the declared flags will be added to the Ports and Flags dialog box.
Page 146: Datalogger Clock
Pause Clock Update. In some situations it is desirable to pause the clock update to minimize data traffic over the communications link. You can set the clock by clicking the Set button. LoggerNet attempts to set the datalogger clock as closely as possible to the computer clock. A slight difference in the clocks might exist after the clock is set because of the communications time delay.
Page 147: Program Management
*.dld file that is downloaded to the datalogger. The CR200 Series datalogger also requires a precompiled file (*.bin), which can be done in the editor or when the program is sent using LoggerNet. CRX000 dataloggers compile their program on-board. 5.1.5.1 Sending a Datalogger Program To transfer a program, press the Send button.
Page 148: Cr200 Series Programs
CRBasic Editor, or when the file is downloaded to the datalogger by LoggerNet. If a *.bin file is downloaded to a CR200, and the version of that binary file does not match the datalogger’s OS, the download will fail and an error will be returned.
Page 149: Data Displays
Updates to the displays can be suspended by selecting Pause Data Displays from the Connect Screen’s Edit menu. This will stop the updates to all displays even though new data may be coming in to LoggerNet. 5-13...
Page 150: Data Display Limitations
The settings and selected data values for a display are saved when the display, Connect Screen, or LoggerNet is closed. The display settings for each datalogger are also saved independently, so a different datalogger will have different settings.
Page 151: Adding And Removing Values
Section 5. Real-Time Tools 5.1.7.2.1 Adding and Removing Values The Numeric Display is initially blank when opened; the fields to be displayed must be selected. Press the Add button to bring up the Add Selection dialog box that lists the data fields for the available datalogger tables or final storage arrays.
Page 152 Section 5. Real-Time Tools Selecting a table name or final storage array ID will bring up a list of data fields in the right hand window. Select the fields to add by clicking the data field names. Multiple data fields can be selected by holding down the Shift or Ctrl key while clicking additional names.
Page 153: Display Options
Section 5. Real-Time Tools To delete data fields from the Numeric Display, select the data fields on the display and press the Delete button. You can delete all data fields from the display using the Delete All button. Adding new data fields on top of existing fields in the display will overwrite the existing fields.
Page 154: Right Click Menu Options
The settings and selected data values for a graph are saved when the graph, Connect Screen, or LoggerNet is closed. The graph settings for each datalogger are also saved independently, so a different datalogger will have different settings.
Page 155: Displaying Values On A Graph
Section 5. Real-Time Tools NOTE A mixed-array datalogger’s final storage data must be collected by LoggerNet before it can be displayed. When a value declared as a Long is being graphed, –2147483648 NOTE (the most negative long value) is used to indicate NAN (Not A Number).
Page 156: Graph Options
Section 5. Real-Time Tools NOTES Table-based dataloggers – If the Add Selection dialog box is empty, return to the Setup Screen’s Data Files table and select Get Table Definitions. Mixed-array dataloggers – If no array IDs are listed and the input locations are listed as InputLocation_# instead of with labels, return to the Setup Screen’s Program tab and associate a DLD file with the datalogger.
Page 157 Section 5. Real-Time Tools Scaling Tab The Scaling options has tabs to set up the scale for the left and right axes. The axes can be scaled automatically, fixed to a specific range, or set to Powers of 0 to 10 or Powers of –10 to 10. The left and right axes are set independently.
Page 158 Section 5. Real-Time Tools value is less than –10, all of the points in the series are divided by 10 until the maximum value is less than or equal to 10 and the minimum value is greater than or equal to –10. If all of the points in the series are greater than or equal to –1 and less than or equal to 1, all of the points in the series are multiplied by 10 until the at least one value is outside that range.
Page 159 Section 5. Real-Time Tools Visual Display Tab The Visual Display options allow the user set the appearance of the graph. The colors for the grids and background as well as how the trace should appear can be set here. Titles can also be added to the graph. 5-23...
Page 160 Section 5. Real-Time Tools Display Options – These options are used to set the look of the graph itself. The Background Color selects the color of the graph background. This is white by default. Be careful to select a background color that does not make any of the data traces disappear.
Page 161: Trace Options
Section 5. Real-Time Tools Plot NAN as value – With this option is selected, each NAN value in the data will be represented by the specified value. Configuration Tab The Configuration tab of the Graph Display Options dialog box is used to Save or Load graph configurations.
Page 162: Right Click Menu Options
Section 5. Real-Time Tools Display Tab Color – Sets the color of the trace and the data points. The user can choose from the Windows color palette for the color. The color for this trace is shown in the color window. Select Axis –...
Page 163 Section 5. Real-Time Tools Save As – Allows you to save a picture of the current graph in a BMP or WMF format. Copy – Save a copy of the current graph image to the Window’s clipboard. This copy can then be pasted into another application. Options –...
Page 164: Table Monitor
Section 5. Real-Time Tools Trace Options – Displays a dialog box that lets you set the color and appearance of the trace. Help – Brings up help for the Graph. 5.1.7.3.5 Additional Capabilities Vertical Line Marker – Double-clicking a point on the graph will bring up a vertical line marker on the screen that moves with the cursor.
Page 165: File Control For Cr5000, Cr1000, Cr800 Series, Cr3000, And Cr9000 Dataloggers
Section 5. Real-Time Tools 5.1.9 File Control for CR5000, CR1000, CR800 Series, CR3000, and CR9000 Dataloggers CR5000, CR1000, CR3000, CR800 Series, and CR9000 dataloggers have a built in file system much like a computer hard disk. Multiple files can be stored in the datalogger’s memory or on a PC card, including data files and datalogger programs.
Page 166 Section 5. Real-Time Tools modified and the file attributes which indicate whether the file is Read Only (R) or Read/Write (RW). Note that the Size, Modified date, and Attributes may not be available for all dataloggers. At the bottom of the right-hand side of the window is a summary box that indicates the Running Program, the Run On Power Up Program, the current Program State (running, stopped, or no program), and the last compile results.
Page 167 Section 5. Real-Time Tools CR1000/CR3000/CR800 Series Datalogger Run Now Options When Run Now is checked, the program is compiled and run in the datalogger. You may choose to preserve existing data tables on the datalogger’s CPU if there has been no change to the data tables (Preserve data if no table changed) or to delete data tables on the CPU that have the same name as tables declared in the new program (Delete associated data tables).
Page 168 Section 5. Real-Time Tools To summarize, any change in data table structure will delete all tables on the datalogger’s CPU, regardless of whether or not the Preserve Data option was chosen. If the Preserve Data option was chosen but the datalogger was unable to retain the existing data, the following message will appear in the Compile Results: Warning: Internal Data Storage Memory was re-initialized.
Page 169: Terminal Emulator
Section 5. Real-Time Tools CR1000, CR3000, and CR800 Series Dataloggers — A program NOTE marked as “Run on power up” can be disabled when power is first applied to the datalogger by pressing and holding the DEL key. Delete – Highlight a file and press the delete button to remove the file from the datalogger’s memory.
Page 170: Station Status
Section 5. Real-Time Tools To activate the remote keyboard select Datalogger | Terminal Emulator from the menu. The remote terminal mode should be used with care. It is CAUTION possible to affect the settings of the datalogger, such as changing the datalogger program and tables. Changes of this type will cause data collection to be suspended and possibly result in lost data.
Page 171: Calibration Wizard
From this menu, you can select fields or view/modify a value (if it is a writable value). Press Refresh to prompt LoggerNet to query the datalogger and update the values again, the Print button to print the information in the current tab, or the Save button to save the information in the tab being displayed to a file.
Page 172: Real-Time Monitoring And Control
Calibration and Zeroing. Also, refer to the datalogger’s CRBasic help file for additional information on the FieldCal and FieldCalStrain instructions, and to the LoggerNet help file if help is needed while using the Calibration wizard. 5.2 Real-Time Monitoring and Control...
Page 173: The Rtmc Workspace
Section 5. Real-Time Tools RTMC was designed to be easy and straightforward to use. Experiment with different combinations and options to get the display results you are looking for. As seen in the example screen above, different types of graphical components can be combined to create an attractive real-time display.
Page 174: Display Components
LoggerNet on a schedule. If scheduled data collection is not set up in LoggerNet or the selected data value is excluded from scheduled collection, the values will not update and an exclamation point will appear in the upper right corner of the component.
Page 175: Functions Available From The Rtmc Menus
Section 5. Real-Time Tools Label displays a text string that can be used to label other components. Switch indicates the state of a port, flag, input location, or Boolean value. A 0 is considered Off (false); any non-zero number is considered On (True).
Page 176 Section 5. Real-Time Tools File Menu New Project starts a new RTMC project. The currently opened project will be closed. If there are changes that have not been saved the user will be prompted to save changes. Open brings up the File Open dialog to open a previously saved project. Save will save the changes in the current project to the RTMC project file.
Page 177 PC. The server name is the network name or IP address of the computer where LoggerNet is running. If you are connecting to a version of LoggerNet that supports server security, and security is enabled, you...
Page 178 Section 5. Real-Time Tools will need to enter the username and password. By default, LoggerNet’s port number is 6789. Note that the remote LoggerNet server must have Remote Connections enabled (Tools | Options | Allow Remote Connections) for RTMC to be able to display remote data. See below for additional information.
Page 179 Section 5. Real-Time Tools Cut deletes the selected component and places a copy on the Windows clipboard. Copy places a copy of the selected component on the Windows clipboard. Align provides some options for lining up a group of components with the last component selected.
Page 180: Expressions
Section 5. Real-Time Tools When components are grouped, the properties for each of the components will show up as an item in the Component right-click menu. These menu items can be used to modify the properties for each component. If there are multiple screens in the project, the Window Menu will allow you to change between the screens.
Page 181 Section 5. Real-Time Tools StartRelativeToNewest(nsecPerDay,ordercollected); MaxRunOverTime(“Server:CR1000.QtrHour.Temp”,Timestamp(“Server: CR1000.QtrHour.Temp”),nsecPerDay) would begin displaying a 24 hour maximum immediately, provided that the data is available in the communications server’s data cache. Aliases If a data value is used multiple times in an expression, the expression can be simplified by declaring an alias for the data value at the first of the expression, in the form: Alias(alias_name, data_value)
Page 182: Operators
Section 5. Real-Time Tools NOTES Timestamps are truncated to seconds prior to synchronization. Therefore, synchronizing sub-second data is not recommended as the results will be unpredictable. If the timestamps of the stations are not the same (for example, if one datalogger is a few minutes behind the other), the component will display the exclamation point indicating no data, until the data sources have common timestamps and, therefore, can be synchronized.
Page 183: Order Of Precedence
Section 5. Real-Time Tools 5.2.1.4.2 Order of Precedence When processing mathematical expressions, the order of precedence is: • Anything inside parentheses ( ) • Exponentiation ^ • Negation (unary) – • Multiplication *, division / • Modulo (remainder) MOD • Addition +, subtraction –...
Page 184: Functions
Section 5. Real-Time Tools Constant Description nsecPerDay Number of nanoseconds in a day nsecPerWeek Number of nanoseconds in a week 5.2.1.4.5 Functions The following functions show the use and placement of the numbers the function operates on. The parentheses are not required unless there are two or more parameter values.
Page 185: Logical Functions
Section 5. Real-Time Tools Function Description LN(x) Returns the natural log of a number. (Note that LN or LOG may be used to perform the same function.) LOG(x) Returns the natural log of a number. (Note that LN or LOG may be used to perform the same function.) LOG10(x) Returns the logarithm base 10 of a number.
Page 186: String Functions
Section 5. Real-Time Tools 5.2.1.4.7 String Functions Function Description Returns a hexadecimal string representation of an expression. HexToDec Converts a hexadecimal string to a float or integer. InStr Finds the location of a string within a string. InStrRev Finds the location of a string within a string. (Differs from InStr in that it searches from the end of the string rather than from the start of the string.) Left...
Page 187: Time Functions
Section 5. Real-Time Tools 5.2.1.4.9 Time Functions Function Description FormatTime Produces a string that formats a timestamp in the manner specified. SetTimeStamp Returns the value specified and sets it timestamp to the timestamp specified. SystemTime Returns the current computer time. SystemTimeGMT Returns the current GMT (Greenwich Mean Time) system time.
Page 188: Statistical Functions
Section 5. Real-Time Tools 5.2.1.4.11 Statistical Functions Function Description AvgRun Returns a running average of up to the last specified number of values. AvgRunOverTime Returns the running average of the specified value over time. AvgRunOverTimeWithReset Returns the running average of the specified value since the function was reset.
Page 189: Remote Connection
Address is a number that will have four digits between 0 and 255 separated by decimal points. An example would be 192.168.4.32. Do not put leading zeros with the numbers. The default port number for LoggerNet is 6789. If this default port number is used, it does not need to be specified in RTMC.
Page 190 When the run-time display screen is started, the display components will have a red exclamation point in the upper right corner until data is received from LoggerNet. If data is not displayed, check to see that the data is being collected on a schedule by LoggerNet.
Page 191: Network Status And Resolving Communication Problems
The Troubleshooter highlights potential problems in a communication network and provides access to a Communications Test and other troubleshooting tools. The LoggerNet Server Monitor is used to monitor the communication log for a remote instance of LoggerNet or when LoggerNet is being run as a service.
Page 192: Visual Status Indicators
The color and letter for the image are a way to quickly verify the LoggerNet communication server’s connection with the device. A device has one of four states: Normal (green N), Marginal (blue M), Critical (red C), or Unknown (gray U).
Page 193: Status Monitor Functions
6.1.2 Status Monitor Functions The Status Monitor includes a number of functions that provide control over the LoggerNet data collection process, configure the display appearance, or bring up other applications such as Log Tool. The Status Monitor functions can also be accessed through the menus at the top of the screen.
Page 194 The statistics will be retrieved during scheduled or manual data collection. These statistics are shown in the table below. The table also shows how the LoggerNet server maps these server statistics to the Status Table of each datalogger.
Page 195 Invalid Table Definitions – A change in the table definitions for this device has been detected. This has caused scheduled collection to be suspended until LoggerNet has updated table definitions to match the datalogger. Network Paused – Scheduled data collection has been suspended for the whole network.
Page 196 • Last Clock Set (Last Clk Set) – The computer date and time that the datalogger’s clock was last set to match the LoggerNet computer’s clock. • Last Collect Attempt (Last Col Attempt) – The computer date and time when data collection was last attempted for this device.
Page 197 LoggerNet will attempt to verify the table definitions for the datalogger. Getting Table Defs – LoggerNet is in the process of retrieving the table definitions from the datalogger. Invalid Table Defs – The table definitions from the datalogger do not match what LoggerNet has stored as the table definitions for the datalogger.
Page 198: Display/Subnet
Only. Selecting All Devices will show your entire network including root devices, communication devices, etc. In LoggerNet Admin, you can also use the Subnet button to view a subnet of your network map. Subnets are configured from the Setup Screen’s View | Configure Subnets menu item.
Page 199: Pool Statistics
Section 6. Network Status and Resolving Communication Problems Collection will stop the collection. This might be needed if the datalogger has a lot of uncollected data and it would take too long to get it all. These functions are available by clicking the buttons or from the right-click menu. 6.1.2.6 Pool Statistics The Tools | Pool Statistics menu item opens a new window displaying statistics for all of the pooled devices in the network.
Page 200: Pool Devices
6.1.2.8 State of Operations The Tools | State of Operations menu item opens a window that provides for monitoring of operations queued by the LoggerNet server for BMP1 and BMP5 devices in the network map (i.e., CR10X-TD, CR23X-TD, CR510-TD, CR10X-PB, CR510-PB, CR23X-PB, CR200X series, CR800 series, CR3000, CR1000, RFBase-TD, and RFRemote-TD/PB).
Page 201 Section 6. Network Status and Resolving Communication Problems Column Descriptions Device Name – Indicates the name of the device associated with the operation. Description – Describes the type of operation. State – Indicates the current state of an active operation, or the most recent state of a completed operation.
Page 202: Logtool
Deleted, 1/2/2013 8:45:00 AM, CR1000, delay hangup, , 2, , , , , , 1 Deleted, 1/2/2013 8:45:00 AM, CR3000, delay hangup, , 2, , , , , , 3 6.2 LogTool There are four logs kept by LoggerNet that track the operation of the server, communications with the dataloggers and data collection. These logs can be used for troubleshooting communication problems. The LogTool utility allows you to view the communication packets transferred between the computer running the datalogger support software and other devices in the network.
Page 203: Log Types
(i.e., serial port). 6.2.2 Using LogTool LogTool can be opened from the Status Monitor, the LoggerNet Toolbar’s Tools category, or the Troubleshooter. When the LogTool is first opened, two logs are displayed: the transaction log and the communication log. The Object State log and the Low Level I/O log can be displayed by toggling their associated button on the toolbar.
Page 204: Saving Logs To File
Section 6. Network Status and Resolving Communication Problems I/O Log – Opens the Low Level I/O log for a specific COM port in a new window. TimeStamp Options – Allows you to select the format for the time stamp in the logs.
Page 205: Comm Test
Delete All Log Files from the LogTool menu. All of the log files can be zipped by selecting File | Zip All Log Files. (When working with a Campbell Scientific applications engineer to resolve a problem, you may be asked to use...
Page 206: Pakbus Graph
To initiate the test, click on one or more of the datalogger stations to select them (the circles will appear blue), and press the Test button. The LoggerNet server will attempt to contact the selected device(s) and perform a simple clock check. While a test is in progress, the circle for a device will appear yellow.
Page 207: Selecting The Pakbus Network To View
Section 6. Network Status and Resolving Communication Problems 6.4.1 Selecting the PakBus Network to View When PakBus Graph is opened, it is set to view the first PakBus network on the computer on which the datalogger support software is running. If more than one PakBus network is set up on the computer, the different networks can be viewed individually by selecting a port name from the PakBus Network drop-down list.
Page 208: Right-Click Functionality
Reset Node – This option will reset the routing table in a PakBus device. Change PakBus Address (server only) – By default, the PakBus address of the software server is 4093 (PC400) or 4094 (LoggerNet). This option lets you change this default.
Page 209: Status Information
Section 6. Network Status and Resolving Communication Problems right side of the window will display status information for it and for other devices in its communications link. If Datalogger Network is highlighted, the status of all devices will be displayed. Note that you can suppress all status information but potential problems by selecting the Show Potential Problems Only check box.
Page 210: Buttons
Table Definitions – Table-based dataloggers return information on all the data tables in the datalogger to the LoggerNet server. The state can be Valid or Out of Date. If table definitions are out of date, they must be updated before data can be collected from the datalogger (LoggerNet attempts to do this automatically.
Page 211 The left-hand pane of the TD-RF Quality Test window displays the network map as configured in LoggerNet, and provides a means of selecting a device or an RF path to be tested. The branches of the network map can be expanded or collapsed by clicking the small triangle to the left of the parent device.
Page 212 – When this checkbox is checked, all entries in the right-hand pane are also written to a text file in LoggerNet’s working directory (C:\Campbellsci\LoggerNet\Logs\RFTestResults.log). Entries in the file are limited to maximum of ten thousand records. After reaching the limit, the oldest two thousand records are deleted.
Page 213 Section 6. Network Status and Resolving Communication Problems "1/3/2013 9:20:14 AM" "RFRemote-PB_3" "RFRemote-PB_2" 239 54 136 65 161 56.46 "1/3/2013 9:20:14 AM" "RFRemote-PB_2" "RFRemote-PB_3(6C67)" 137 50 138 63 164 30.75 Clear – Clicking this button clears the contents of the right-hand pane. ...
Page 214 RF Quality Report from each of the modems involved in the test. The RFBase- TD sends the collected reports to LoggerNet in the RF Test response packet. The TD-RF Quality Reports are displayed in the right-hand pane of the TD-RF Quality Test window in the order (top-down) they were collected;...
Page 215 Section 6. Network Status and Resolving Communication Problems Demodulated Data Stream Bit Rate = 3 KHz Composite of all T2 Transitions Composite of all T1 Transitions TD-RF QUALITY REPORT The total number of Data bytes in the test packet. Dynamically adjusted downward in response to lost or corrupted packets.
Page 216: Archiving Troubleshooter Results
CAUTION severely degrade the performance of the TD-RF Network. It is recommended that these features be activated only at the direction of a Campbell Scientific Applications Engineer. It should be noted that the activation of the Advanced Features is not persistent;...
Page 217: Other Tools In Troubleshooter
The LoggerNet Server Monitor is a utility that is used to monitor the status of LoggerNet when it is being run as a service or being run on a remote computer. Once started it can be minimized, where it resides in the Window’s system tray.
Page 218 Section 6. Network Status and Resolving Communication Problems (white background/blue text) The LoggerNet server is running, but Warnings or Faults have occurred. There have likely been communication problems with a device in the datalogger network. (white background/red text) The LoggerNet server is no longer running.
Page 219: Review Of Csi Datalogger Models
SCWIN. In addition to the above programming tools, the Transformer utility is offered in LoggerNet for those users of CR10X or CR23X dataloggers who need to develop programs for the CR800 Series, CR1000 or CR3000 dataloggers.
Page 220: Short Cut
Cut created the program. 7.2 Short Cut 7.2.1 Overview The Short Cut program generator creates programs for Campbell Scientific dataloggers in five easy-to-follow steps. Using a wizard-like interface, you create a new or open an existing program, select the datalogger and specify...
Page 221: Creating A Program Using Short Cut
Help button from the sensor form. After generating the program, you can send it to the datalogger from the Results tab of Short Cut’s Finish screen or from LoggerNet’s Connect Screen or from PC400, PC200W, or RTDAQ’s Clock/Program tab.
Page 222: Step 2 - Select Datalogger And Specify Scan Interval
Section 7. Creating and Editing Datalogger Programs 7.2.2.2 Step 2 – Select Datalogger and Specify Scan Interval Click the arrow next to Datalogger Model to display a list of Campbell Scientific dataloggers. Select the datalogger type. Set the Scan Interval, or period for each measurement cycle.
Page 223 CR9000X program.) This is used to select which group of sensor files will be displayed when creating a program: Campbell Scientific, Inc. (CSI, USA) or Campbell Scientific, Ltd. (CSL, UK). The standard set of Short Cut sensor files was created by CSI; however, CSL has created some additional files that are customized for their client base.
Page 224 Section 7. Creating and Editing Datalogger Programs This setting is similar to the Integration setting in that the dialog box will be displayed only the first time you create a program for a specific datalogger type, and the setting will apply to all programs created or edited for that datalogger, unless it is changed via the Program menu.
Page 225: Step 3 - Choose Sensors To Monitor
Refer to the documentation for your sensors for the name of the sensors you have. If your sensor is not shown, you may be able to measure it with a generic measurement. Contact your Campbell Scientific application engineer for more assistance, if needed.
Page 226 Section 7. Creating and Editing Datalogger Programs Measurement name Measurement units Notes specific to this sensor Note that this sensor not only offers a custom name field and units, but also allows you to correct for sea level, a common practice in measuring atmospheric pressure.
Page 227 Section 7. Creating and Editing Datalogger Programs...
Page 228 Section 7. Creating and Editing Datalogger Programs Click on the Wiring tab of a sensor’s parameter form to show the wiring for the sensor (or the first sensor in a sensor group). Each wire’s caption/color is shown on the left side of the wire. The location where the wire will be connected to the device is shown on the right side (under the device).
Page 229 Section 7. Creating and Editing Datalogger Programs In addition to actual sensors, Short Cut provides functionality to perform various calculations and effect some simple control: Some of these calculations may require additional sensors, or sensor measurements stored in particular units. See the help for each calculation to determine the necessary inputs.
Page 230 Section 7. Creating and Editing Datalogger Programs Short Cut provides you with a wiring diagram by clicking on Wiring Diagram on the left side of the Sensors window. In the example below, Short Cut was told to measure a CS105 Barometric Pressure sensor, an HMP45C Air Temperature and Relative Humidity sensor and a 05103 Wind Speed and Direction sensor.
Page 231 Section 7. Creating and Editing Datalogger Programs Short Cut can also create programs for dataloggers using a variety of interface devices, including multiplexers and special interfaces for sensors. Add these devices by selecting them from the Devices folder in the Available Sensors and Devices tree.
Page 232: Step 4 - Setup Output Tables
Section 7. Creating and Editing Datalogger Programs 7.2.2.4 Step 4 – Setup Output Tables After selecting the sensors to be measured, you can choose what data to store from the outputs step: On the left, Short Cut will show the sensors you’ve added to be measured, with the measurement labels you’ve used.
Page 233 Section 7. Creating and Editing Datalogger Programs Note that outputs for a sensor don’t have to be added in the same sequence as the measurement. You can even drag and drop the outputs to rearrange their order. Note also that multiple outputs can be added for any one sensor. For example, you may want to store the maximum and minimum air temperature as well as the average.
Page 234 Section 7. Creating and Editing Datalogger Programs The Advanced Output allows you to store data based on time, the state of a flag, the value of a measurement or a data event. Be cautious in using more than one check box, for the logic for the check boxes in the advanced mode are inclusive—that is, they must all be true in order for any output to be stored.
Page 235: Step 5 - Generate The Program In The Format Required By The Datalogger
Section 7. Creating and Editing Datalogger Programs 7.2.2.5 Step 5 – Generate the Program in the Format Required by the Datalogger The Finish button completes the process. If you haven’t yet saved the program, Short Cut asks for a program name and offers the default directory within its program working directory (default is C:\Campbellsci\SCWin).
Page 236: Short Cut Settings
If you send a program with security set, you will then need to add that security setting to LoggerNet's Setup Screen or RTDAQ or PC400’s EZSetup Wizard for that datalogger. If you don’t, you may find that you can no longer communicate with the datalogger.
Page 237: Select Cr200 Compiler
This compilation is done by Short Cut to check for errors in the program before sending it. It’s done again by LoggerNet, RTDAQ, PC400, or PC200W when sending the program to the datalogger. Compilation is performed using a special executable that mimics the functions and capability in the datalogger’s...
Page 238: Integration
7.2.4 Editing Programs Created by Short Cut Short Cut is very flexible and has many features. It does not, however, support all of the functionality in Campbell Scientific dataloggers. Some users will need to develop programs with capabilities beyond that offered by Short Cut, but will want to take advantage of the library of instructions and settings known to a program generator in order to get a head start.
Page 239: New Sensor Files
Campbell Scientific website: www.campbellsci.com/downloads It is also possible to have custom sensor files created for sensors your organization uses that are not included with Short Cut. Contact your Campbell Scientific applications engineer for details. 7.2.6 Custom Sensor Files The creation of custom sensor files can be enabled from Short Cut’s Tools | Options menu item.
Page 240: Inserting Instructions
Section 7. Creating and Editing Datalogger Programs 7.3.2 Inserting Instructions An instruction can be easily inserted into the program by highlighting it in the Instruction Panel list and pressing the Insert button or by double-clicking the instruction name. If an instruction has one or more parameters, an instruction dialog box will be displayed to facilitate editing the parameters.
Page 241 Section 7. Creating and Editing Datalogger Programs Below is an example of the Parameter dialog box for the differential voltage instruction (VoltDiff). The Prev (Previous) and Next buttons can be used to move to the next (or previous) instruction with the parameter entry box opened. Short Cuts for Editing the Parameters Right-clicking or pressing F2 on a parameter that uses a variable as an input type will display a list of variables that have been defined in the program.
Page 242: Right-Click Functionality
Section 7. Creating and Editing Datalogger Programs Pressing F9 at any time will also bring up a list of variables. However, when a variable is chosen from the list brought up by F9, it will simply be inserted at the cursor without overwriting anything. Right-clicking or pressing F2 on a parameter that has a finite number of valid entries will bring up a list of those available options.
Page 243: Toolbar
LoggerNet, PC400, or RTDAQ. LoggerNet, PC400, or RTDAQ must be running for this function to work properly. Print – Prints the currently opened program.
Page 244 Section 7. Creating and Editing Datalogger Programs Print Preview – Opens a Print Preview screen that will show what the program will look like when printed. You can check and set the margins and printer options. Undo – Each time the Undo button is clicked it will step back through the last changes made to the program.
Page 245: Compile
This function is not available for the CR9000 datalogger. 7.3.3.2 Compile, Save, and Send The CRBasic Editor allows you to send a program to a datalogger that has already been defined on the network map in LoggerNet, PC400, or RTDAQ. 7-27...
Page 246 Section 7. Creating and Editing Datalogger Programs This only works if LoggerNet, PC400, or RTDAQ is running at the time you attempt to send the program. This function first checks the program for errors using the pre-compiler, then saves the program (using the current name, or by prompting the user for a name if the program is new).
Page 247 Section 7. Creating and Editing Datalogger Programs PC400, or RTDAQ network map. When you send a *.CR1 program, this screen will show only the three CR1000 dataloggers. Any other dataloggers will be excluded from the list in this case, even when they are defined in the network map, because those dataloggers are not associated with *.CR1 programs.
Page 248 Section 7. Creating and Editing Datalogger Programs CR9000(X)/CR5000 Datalogger Run Now Options The Run Now options and behavior for the CR9000(X) and CR5000 dataloggers are different from the CR1000, CR3000, and CR800 dataloggers. Below is a dialog box for a CR9000X datalogger. When Run Now is checked, the file will be sent with the Run Now attribute set.
Page 249: Conditional Compile And Save
Sending the Program To send the file and perform the associated functions you have selected in the screen, press the Send button. If LoggerNet, PC400, or RTDAQ is not running, an error message will appear indicating that there is no communications server currently running.
Page 250: Program Navigation Using Bookmarks And Goto
Section 7. Creating and Editing Datalogger Programs Save as Default Template - Saves the comments and instructions in the active file as a template that will be used each time File | New is selected for that type of datalogger. Delete - When selected, a list of all dataloggers is displayed.
Page 251: Crbasic Editor Edit Menu
Section 7. Creating and Editing Datalogger Programs 7.3.3.7 CRBasic Editor Edit Menu This menu item allows you to edit and manipulate the text currently being displayed in the Editor. Standard text editing functions such as Cut, Copy, Paste, Delete, Select All, Undo and Redo are found in this menu. 7.3.3.7.1 Other Options –...
Page 252 Section 7. Creating and Editing Datalogger Programs The Vertical Spacing tab is used to set up the rules for the CRBasic Editor's Rebuild Indentation function (Edit | Rebuild Indentation). You can control whether blank lines are inserted before or after certain instructions, and how the CRBasic Editor will process multiple blank lines in the program.
Page 253: Instruction Panel Preferences
Section 7. Creating and Editing Datalogger Programs The Syntax Highlighting tab sets up the appearance of different text elements in the program using different font styles and colors. You can customize the appearance of the text by giving normal text, keywords, comments, operators, numbers, strings, and parentheses each a different font style and color to make the program easier to read and edit.
Page 254: Crbasic Editor Tools Menu
Section 7. Creating and Editing Datalogger Programs Background Color - Displays a color selection dialog to set the color of the CRBasic program window. Wrap Text When Printing - When this option is selected, long lines that extend past the right margin will be wrapped to the next line. This option affects printing, as well as the Print Preview mode.
Page 255: Constant Customization
Section 7. Creating and Editing Datalogger Programs 7.3.3.9.2 Constant Customization The Constant Customization feature allows you to define values for one or more constants in a program prior to performing a conditional compile (Compile | Conditional Compile and Save menu item). The constants can be set up with an edit box, a spin box field for selecting/entering a value, or with a list box.
Page 256 Section 7. Creating and Editing Datalogger Programs The Constant Customization syntax may be best understood by looking at an example. Consider the following program code: 'Start of Constants Customization Section Const SInterval=10 'Min=5 'Max=60 'Inc=5 Const SUnits = sec 'value=sec 'value=min Const Reps=1 Const Number=0...
Page 257: Other Options
Section 7. Creating and Editing Datalogger Programs The constant SInterval is defined with a default value of 10, a maximum of 60 and a minimum of 5, with a step of 5 each time the up or down control is selected.
Page 258: Available Help Information
Section 7. Creating and Editing Datalogger Programs 7.3.3.10 Available Help Information Pressing the Help button of the Parameter dialog box will bring up a detailed help topic for the instruction being edited. Pressing F1 when your cursor is within a parameter field will bring up help only on that parameter. Some fields also have text in the Comments column, which provides a short description of the option that has been selected for the parameter.
Page 259: Program Declarations
Section 7. Creating and Editing Datalogger Programs Define Subroutines If there is a process or series of calculations that needs to be repeated several times in the program, it can be packaged in a subroutine and called when needed rather than repeating all the code each time.
Page 260: Mathematical Expressions
FFT, etc. The instructions for making measurements and outputting data are not found in a standard basic language. The instructions Campbell Scientific has created for these operations are in the form of procedures. The procedure has a keyword name and a series of parameters that contain the information needed to complete the procedure.
Page 261: Line Continuation
Section 7. Creating and Editing Datalogger Programs 7.3.4.5 Line Continuation Line continuation allows an instruction or logical line to span one or more physical lines. This allows you to break up long lines of code into more readable “chunks”. Line continuation is indicated by one white space character that immediately precedes a single underscore character as the last character of a line of text.
Page 262: Example Program
Section 7. Creating and Editing Datalogger Programs 7.3.4.7 Example Program The following program will serve as a programming example in this section to illustrate the concepts and program structure. This is a program for a CR5000 datalogger. Note that other dataloggers may have slightly different parameters for some instructions.
Page 263 Section 7. Creating and Editing Datalogger Programs The data table header may also have a row that lists units for the output values. The units must be declared for the datalogger to fill this row out (e.g., Units RefTemp = degC). The units are strictly for the user's documentation; the datalogger makes no checks on their accuracy.
Page 264: The Scan - Measurement Timing And Processing
TABLE 7-1. Formats for Output Data Code Data Format Size Range Resolution Campbell Scientific floating point 2 bytes ±7999 13 bits (about 4 digits) IEEE4 IEEE four byte floating point 4 bytes 1.8 E -38 to 1.7 E 38...
Page 265: Numerical Entries
Section 7. Creating and Editing Datalogger Programs The Scan instruction determines how frequently the measurements within the scan are made: Scan(Interval, Units, BufferOption, Count) Scan(1,MSEC,3,0) The Scan instruction has four parameters (the CR200 datalogger’s Scan instruction has only two). The Interval is the time between scans. Units are the time units for the interval.
Page 266: Expression Evaluation
Section 7. Creating and Editing Datalogger Programs TABLE 7-3. Synonyms for True and False Predefined Constant True (-1) False (0) Synonym High Synonym Synonym Synonym Trigger Do Not Trigger ≠0 Number Digital port 5 Volts 0 Volts 7.3.4.11.2 Expression Evaluation Conditional tests require the datalogger to evaluate an expression and take one path if the expression is true and another if the expression is false.
Page 267: Flags
If the value of the variable is non-zero the flag is high. If the value of the variable is 0 the flag is low. LoggerNet, PC400, or RTDAQ looks for the variable array with the name Flag when the option to display flag status is selected from the Connect Screen.
Page 268: Arrays Of Multipliers And Offsets For Sensor Calibration
Section 7. Creating and Editing Datalogger Programs DataTable(Name, TrigVar, Size) DataTable(Temp, TC(1)>100, 5000) Entering the trigger as the expression, TC(1)>100, will cause the trigger to be true and data to be stored whenever the temperature TC(1) is greater than 100. 7.3.4.13.2 Arrays of Multipliers and Offsets for Sensor Calibration If variable arrays are used for the multiplier and offset parameters in measurements that use repetitions, the instruction will automatically step...
Page 269: Edlog
(1,1) are only updated when the tables are called. 7.4 Edlog 7.4.1 Overview Edlog is a tool for creating, editing, and documenting programs for Campbell Scientific’s mixed-array dataloggers: CR7, CR500, CR510, CR10, CR10X, 21X, CR23X. Edlog also supports these same dataloggers configured with table-based operating systems, including the table-data or “TD”...
Page 270: Context-Sensitive Help
Section 7. Creating and Editing Datalogger Programs make it more compact. During the precompile step, a Program Trace Information file (*.PTI), that provides an estimate of program execution time, is also created. For mixed-array dataloggers the precompiler also creates a Final Storage Label file (*.FSL) to supply labels for final storage values to be used by other software applications.
Page 271: Creating A New Edlog Program
Section 7. Creating and Editing Datalogger Programs For example, the following expression could be used to create a new input location for temperature in degrees Fahrenheit from an existing input location for temperatures in degrees Celsius. TempF=TempC*1.8+32 7.4.2 Creating a New Edlog Program To create a new datalogger program, choose File | New from the Edlog menu and select the datalogger type from the dialog box.
Page 272: Program Structure
Section 7. Creating and Editing Datalogger Programs The first line of text identifies the type of datalogger program to be written. This is followed by a comment line and the Program Table Headers and Execution Interval fields. The Program Table Headers and Execution Interval fields are protected text that cannot be deleted or commented out.
Page 273: Edlog File Types
Section 7. Creating and Editing Datalogger Programs − Control – Do any control of external hardware or devices. − Output Data – Check to see if it is time, or a condition exists, to trigger output data to be saved in final storage. Descriptive Labels –...
Page 274: Inserting Instructions Into The Program
Section 7. Creating and Editing Datalogger Programs • *.TXT – Printer output files created by Edlog are saved with a TXT extension. These files can be sent to a printer or viewed with a text editor. A TXT file is created by selecting File | Print to File. 7.4.2.3 Inserting Instructions into the Program Instructions are entered into the program table in the order that they should be executed in the program.
Page 275: Entering Parameters For The Instructions
Section 7. Creating and Editing Datalogger Programs 7.4.2.4 Entering Parameters for the Instructions When an instruction is inserted, the cursor moves to the first parameter. Type the parameter’s value and press <Enter> to move to the next parameter. There are two ways to get help on a parameter: •...
Page 276: Expressions
Section 7. Creating and Editing Datalogger Programs 7.4.2.6 Expressions Algebraic expressions can be used in a program to easily perform processing on input locations. When a datalogger program that contains an expression is compiled, the appropriate instructions are automatically incorporated into the DLD file.
Page 277: Operators And Functions
Section 7. Creating and Editing Datalogger Programs TABLE 7-5. Operators and Functions Operators multiply divide – subtract raise to the power of; enclose negative values in parentheses modulo divide scientific notation; 6e–1=0.6 Functions cosine; angle in degrees sine; angle in degrees tangent;...
Page 278 Section 7. Creating and Editing Datalogger Programs Execution Interval = 10 sec ;this instruction reads the temperature probe ;the output is in degrees C 1: Temperature (107) (P11) 1: 1 REPS 2: 2 Channel 3: 1 Excitation Channel 4: 2 Loc [TempC] 5: 1 Mult...
Page 279 Section 7. Creating and Editing Datalogger Programs Errors That Can Occur With Expressions Some of the error messages that occur when using expressions need no further explanation: Missing left parenthesis Missing right parenthesis Variable name expected Number expected Floating point numbers limited to 5 digits Function expected New line expected Equal sign expected...
Page 280 Section 7. Creating and Editing Datalogger Programs Floating Point Numbers Limited to 5 Digits All fixed numbers are limited to five digits not including negative signs and decimal points. Function Expected Letters that are immediately followed by parentheses are assumed to be a function.
Page 281: Editing An Existing Program
Section 7. Creating and Editing Datalogger Programs For Example: This error message is displayed when a program contains any of these expressions: result=(ex^2)data gamma=(10–omega)SIN(psi) dee=(17)number These are correct ways of entering the above expressions: result=(ex^2)*data gamma=(10–omega)*SIN(psi) dee=(17)*number Equal Sign Expected An equal sign MUST immediately follow the label of the Input Location that stores the results (e.g., label = expression).
Page 282: Editor Keystrokes
Section 7. Creating and Editing Datalogger Programs TABLE 7-6. Editor Keystrokes PgUp Page Up PgDn Page Down Up Arrow Move Up One Line Down Arrow Move Down One Line Right Arrow Move One Character Right Left Arrow Move One Character Left <Ctrl>...
Page 283: Editing Comments, Instructions, And Expressions
Section 7. Creating and Editing Datalogger Programs 7.4.2.8 Editing Comments, Instructions, and Expressions To edit Comments, Expressions, and Instruction parameters, move the cursor to the appropriate text and retype it. To delete an instruction when the cursor is somewhere within the instruction, select Edit | Delete Instruction or press <Shift>...
Page 284: Display Options
Section 7. Creating and Editing Datalogger Programs Programs created with the DOS versions of Edlog earlier than 6.0 were stored with the instruction description and comments in a *.DOC file instead of a *.CSI file. The DLD version of these programs can be imported into current versions of Edlog by using this Document DLD feature, though any comments will be lost.
Page 285: Renumbering The Instructions
Section 7. Creating and Editing Datalogger Programs Open the on-line help system. 7.4.5.2 Renumbering the Instructions When Automatic Renumbering is enabled, the instructions are automatically renumbered whenever instructions are inserted or deleted. By default, Automatic Renumbering is enabled. Automatic renumbering can be turned off by selecting Options | Editor if you have a very large program and auto renumbering is slowing down editing.
Page 286: Entering Input Locations
Section 7. Creating and Editing Datalogger Programs 7.4.7 Entering Input Locations When a parameter requires an Input Location, the cursor automatically advances to where the label is keyed in. When a new label is entered, the next available Input Location number is automatically assigned to that label. To select an existing label from a list, press the right mouse button or <F6>.
Page 287: Input Location Editor
Section 7. Creating and Editing Datalogger Programs 12: If time is (P92) minutes into interval 2: 60 minute interval 3: 10 Set high Flag 0(output) 13: Sample (P70) 1: 2 Reps 2: 1 Loc [TempC] When the program is executed, the datalogger will perform the Sample (P70) instruction twice.
Page 288: Input Location Anomalies
Section 7. Creating and Editing Datalogger Programs Editing functions are available from the Input Location Editor’s Edit menu and a hot key: Insert (<F2>) – Inserts blank Input Locations. This is used to provide space for new input labels between existing labels. This automatically changes the Input Location numbers for all of the labels that are after the inserted location.
Page 289: Final Storage Labels
DLD files. For table-based dataloggers the final storage labels are included as part of the datalogger program in the *.DLD file; no FSL file is created. LoggerNet gets the final storage labels as part of the table definitions from the datalogger. Split, the Graphical and Numeric Displays, View, and the LoggerNetData applications use the final storage labels.
Page 290 Section 7. Creating and Editing Datalogger Programs The user can create a custom label to reflect the meaning of the value that is being stored. Click the FSL Edit button on the toolbar or press F9 to bring up the Final Storage Label Editor as shown below. In this example from a mixed-array datalogger, the final storage output data for Array ID 112 is shown.
Page 291: Datalogger Settings Stored In The Dld File
Setting security in the datalogger allows you to restrict access to certain functions, which helps ensure the program or data are not altered. Security is unlocked in the datalogger when, upon attempting to connect, LoggerNet sends the code entered in the Setup Screen.
Page 292: Final Storage Area 2
7.4.15.1 Mixed-array Dataloggers Mixed-array dataloggers can store the labels for input locations and final storage output in the DLD file. LoggerNet uses this information on the Monitor Values displays. If you do not include these labels in the DLD file, you will see generic names for input locations, and will not be able to display final storage locations at all.
Page 293: Power Up Settings/Compile Settings
Section 7. Creating and Editing Datalogger Programs If you are trying to minimize the size of your DLD file but still want to be able to monitor input locations in the software, you can put all of the labels that you want to view at the beginning of your list of input locations, and put the labels for scratch and less important values at the end.
Page 294: Pakbus Settings
Section 7. Creating and Editing Datalogger Programs 7.4.18 PakBus Settings PakBus dataloggers have various settings that allow them to function properly in a PakBus network. In Edlog dataloggers with PB operating systems, these options can be set in the datalogger’s *D mode with a keyboard/display, but they can also be set in the DLD program file For any of the options, if the check box Do Not Change Current Settings is enabled, then those settings will not be changed when the program is...
Page 295: Neighbor Filter
7.5.1 Transforming a File The Transformer utility can be opened from the Program category of the LoggerNet toolbar. When the Transformer is first opened, a dialog box is displayed in which to enter the Source File and the Program File.
Page 296 Section 7. Creating and Editing Datalogger Programs The Source File is the CSI or DLD file to be converted. The Program File is the new CR* file that will be created. By default, the resulting file name for the CR1000, CR800, or CR3000 program that will be created is the name of the original program with a CR* extension.
Page 297: Controls
Section 7. Creating and Editing Datalogger Programs Comments about the conversion are shown in the Action Log (bottom portion of the window). The Action Log should be reviewed carefully; it provides useful comments and alerts you to any problems that may exist in the converted file.
Page 298 Section 7. Creating and Editing Datalogger Programs 7-80...
Page 299: View Pro
(*.DAT) saved in a variety of formats including files from mixed-array and table- based dataloggers. It can also be used to view data from a LoggerNet database table created with LNDB. View can also open other CSI file types (*.DLD, *.CSI, *.PTI, *.FSL, *.LOG, *.CR2, *.CR5, *.CR1, *.CR3, *.CR8, *.CR9).
Page 300: The Toolbar
Section 8. Working with Data Files on the PC View Pro is closed by selecting File | Exit from the menu or pressing the red X in the upper right-hand corner. When View Pro is closed, all open graphs and data files will also be closed.
Page 301 Section 8. Working with Data Files on the PC New Histogram. Brings up a Histogram window from which you can view Histogram data values. New XY Plot. Brings up an XY Plot window from which you can plot data values on the y-axis against another specified da value on the x-axis.
Page 302: Opening A File
This may be useful when viewing binary files. 8.1.4 Viewing a LoggerNet Database Table A LoggerNet database table created using LNDB can be viewed in View Pro by selecting View LoggerNet Database Table from View Pro’s File menu. You will need to select a database and then a table from that database.
Page 303 Section 8. Working with Data Files on the PC database, you will need to press the Change Database button on the Select Table dialog box.) View Pro supports SQL Server Compact, SQL Server, and MySQL databases. The information to enter changes depending on the database type as described below: SQL Server Compact SQL Server Compact is an embedded database that just requires the selection...
Page 304 Section 8. Working with Data Files on the PC SQL Server To configure a connection to SQL Server you must select a SQL Server instance. The list of published SQL Server instances is shown in the Data Source combo box. You can also type into the Data Source combo box, because the desired server might not be published.
Page 305 Section 8. Working with Data Files on the PC MySQL The MySQL connection is an ODBC connection. You must use the Windows ODBC Data Source Administrator to configure the database connection. Currently only system data sources are supported and show in the Data Source combo box.
Page 306: Selecting A Table
Section 8. Working with Data Files on the PC 8.1.4.2 Selecting a Table The Select Table dialog box comes up once a database has been selected. Select the database table that you wish to view and then press the OK button. To select a table from a different database, press the Change Database button.
Page 307 Section 8. Working with Data Files on the PC File The name of the file to be imported. Press the File button to bring up a browser to select the desired file. Header Line Count CSV files may have multiple header lines or no header line. Use the Header Line Count field to designate how many header lines your file contains before the data begins.
Page 308 Section 8. Working with Data Files on the PC Date and Time Format Codes yy = Year last 2 digits yyyy = Year as 4 digits m = Month number no-leading 0 mm = Month number as 2 digits mmm = Month using short form (Jan) mmmm = Month using long form (January) d = Day number no-leading 0 dd = Day number as 2 digits...
Page 309: Data View
Section 8. Working with Data Files on the PC 8.1.6 Data View The initial display for data files in View Pro is as normal text in a grid format. The following figure shows the View Pro main screen with two data files open. The data file windows have been tiled horizontally.
Page 310: Column Size
Section 8. Working with Data Files on the PC Array-based data files do not contain timestamps. If an FSL file is associated with the data file, View Pro will try to extract timestamps from the appropriate columns. You can select Array Definitions from View Pro’s View menu to specify how the timestamps are created.
Page 311: Window Arrangement
Section 8. Working with Data Files on the PC 8.1.6.7 Window Arrangement When multiple data files are opened, they are arranged so that the title bar of each window is visible and they cascade down and to the right starting from the upper left corner.
Page 312 Section 8. Working with Data Files on the PC Zoom Feature You can zoom in on a particular area of a graph by holding the left mouse button and dragging the mouse cursor from top-left to bottom-right over the area to be zoomed. Dragging the mouse cursor from bottom-right to top-left will undo the zoom.
Page 313: Line Graph
Section 8. Working with Data Files on the PC 8.1.7.1 Line Graph From the Line Graph screen, you can graph data values on the y-axis against their timestamps on the x-axis. 8.1.7.1.1 Selecting Data to be Graphed Data value(s) are added to a graph by clicking the column heading(s) in the data panel with a single mouse click.
Page 314: Graph Width
Section 8. Working with Data Files on the PC Creating Multiple Line Graphs To open an additional Line Graph, select “None” from the Selected Graph drop-down menu on the main View Pro toolbar. The highlighting in the data file will be cleared. Select the data that you would like graphed as described above and then press the Line Graph button.
Page 315: Line Graph Toolbar
Section 8. Working with Data Files on the PC and drag the cursor across the graph. Data values at the current cursor position will be shown in the table to the right of the graph. 8.1.7.1.5 Line Graph Toolbar The Line Graph toolbar includes the following icons: Statistics.
Page 316 Section 8. Working with Data Files on the PC Export. Allows the graph to be exported in a choice of text or graphical formats. Lock Scrolling. Locks and unlocks the scroll bar at the bottom of the graph. When unlocked, moving the scroll bar on either the graph or the data file will scroll both the graph and the data file.
Page 317: Histogram
Section 8. Working with Data Files on the PC Synchronize Axes button may be pressed to synchronize the timestamps of the remaining graph(s) and data file(s) so that they are all displaying data from the same time period. When the data panels and graphs are currently synchronized, the button icon will have a check mark in the bottom right corner.
Page 318: Selecting Data To Be Viewed
Section 8. Working with Data Files on the PC 8.1.7.2.1 Selecting Data to be Viewed From a Histogram Screen When a Histogram screen is first opened with no histogram records selected in the data file, the Histogram Setup dialog box will open which allows you to set up the Histogram.
Page 319: Options
Section 8. Working with Data Files on the PC NOTE All histogram records from the same histogram will have the same default name in the list. They can be distinguished by the colored boxes next to their names. Each box is the same color with which that histogram record is highlighted in the data file.
Page 320: Xy Plot
Section 8. Working with Data Files on the PC Show Table. Brings the main View Pro window in front of other windows, making the data file(s) visible. Show/Hide Gradient. A toggle button that turns on and off the gradient background of the Histogram. It may be useful to hide the gradient, when printing the Histogram.
Page 321: Selecting Data To Be Plotted
Section 8. Working with Data Files on the PC 8.1.7.3.1 Selecting Data to be Plotted To select the data value(s) to be plotted, highlight the column headings in the data file with a single mouse click. Each column that is selected in the data file, will be added to the XY Plot in both the X and Y drop-down lists.
Page 322: Rainflow Histogram
Section 8. Working with Data Files on the PC 8.1.7.4 Rainflow Histogram From the Rainflow Histogram screen, you can view rainflow histogram data. The Rainflow Histogram button on the toolbar will be enabled if there is at least one valid rainflow histogram in the currently selected data file. A Rainflow Histogram is a 3D representation based on the rainflow counting algorithm of Endo and Matsuishi which was first published in 1968.
Page 323: Selecting Data To Be View
Section 8. Working with Data Files on the PC 8.1.7.4.1 Selecting Data to be View From a Rainflow Histogram Screen When a Rainflow Histogram screen is first opened with no rainflow histogram records selected in the data file, the Rainflow Histogram Setup dialog box will open which allows you to set up the Rainflow Histogram.
Page 324: Options
Section 8. Working with Data Files on the PC screen is opened, all selected rainflow histogram records will be listed on the left side of the Rainflow Histogram screen. A rainflow histogram record can then be displayed by clicking on it in the list. Once the Rainflow Histogram screen is opened, additional rainflow histogram records can be added to the Rainflow Histogram screen by selecting them in the data file as described above.
Page 325: Fft
Section 8. Working with Data Files on the PC Show/Hide Gradient. A toggle button that turns on and off the gradient background of the Rainflow Histogram. It may be useful hide the gradient, when printing the Rainflow Histogram. Modify Selection. Brings up the Rainflow Histogram Setup dialog box from which you can change the options for the selection.
Page 326: Selecting Data To Be Graphed
Section 8. Working with Data Files on the PC 8.1.7.5.1 Selecting Data to be Graphed From an FFT Screen When an FFT screen is opened, a Fast Fourier Transform Setup dialog box will open which allows you to set up the FFT. The first option is a drop-down list that shows the available FFTs in the currently selected data file.
Page 327: Options
Section 8. Working with Data Files on the PC NOTE All FFT records from the same FFT will have the same default name in the list. They can be distinguished by the colored boxes next to their names. Each box is the same color with which that FFT record is highlighted in the data file.
Page 328: Right-Click-Menus
Section 8. Working with Data Files on the PC Show Table. Brings the main View Pro window in front of other windows, making the data file(s) visible. Show/Hide Gradient. A toggle button that turns on and off the gradient background of the FFT. It may be useful to hide the gradient, when printing the FFT.
Page 329 Section 8. Working with Data Files on the PC The records included can be defined by initial and ending time, time span, initial and ending record, or record span. If any of the date/time or record number options are changed, the other options will automatically adjust to reflect the change.
Page 330: Graphs
Section 8. Working with Data Files on the PC Goto Bookmark If the data panel contains one or more bookmarks, hovering over the Goto Bookmark menu item will bring up a list of the current bookmarks. Selecting a bookmark from the list will automatically move the data panel to that record. The shortcut Ctrl-n, where n is the number of the bookmark, can also be used to move the data file to the desired bookmark.
Page 331: Printing Text
Options | File Types from the Windows Explorer menu. 8.2 Split 8.2.1 Functional Overview Split is a tool to analyze data collected from Campbell Scientific dataloggers. Its name comes from its function of splitting out specific data from a larger 8-33...
Page 332: Getting Started
Section 8. Working with Data Files on the PC data file. Originally, Split could only process mixed-array files, and it was used to “split” the different arrays – typically different time intervals – of a file into separate files (e.g., for hourly versus daily data). In addition to splitting out mixed-array data, Split can filter output data based on time or conditions, calculate statistics and new values, reformat files, or check data quality (limit testing).
Page 333 Section 8. Working with Data Files on the PC When Edlog compiled Birch.dld, it also created the Final Storage Label file, Birch.fsl that lists the final storage locations for each data element. 8-35...
Page 334 Section 8. Working with Data Files on the PC When you start Split a blank template similar to the one above is shown. This template is used to enter the parameters that will define what data from the input file to include in the output file. The parameters entered on this template can be saved as a parameter file (*.PAR) and reused for other data.
Page 335 Section 8. Working with Data Files on the PC In this example we want the hourly data (note the Output Interval at the bottom of the Data File Label window), so click array 60. To paste the desired values from this array into the Select box, select the field names while holding down the <ctrl>...
Page 336 Section 8. Working with Data Files on the PC Note that the cursor in the INPUT FILE(S) screen must be in valid paste area (Copy or Select). If the cursor is in the File name box or in Start/Stop condition, you will get the error message “Cannot Paste There”. The Paste operation copied the numbers of each of the fields into the Select box.
Page 337 Section 8. Working with Data Files on the PC Maximum column heading width is one less than the number entered in the Default Column Width field. However, entering a number in the Width row for the column will set the column width for an individual column. Any FSL labels that are too long for Split column headings will be shown in red.
Page 338: Split Parameter File Entries
Browse button to find the input file. In LoggerNet, mixed array datalogger files are stored in a simple comma separated ASCII format; tabled-based datalogger files are stored in TOA5 (a comma separated format with headers).
Page 339: Comma Separated, Field Formatted, Printable Ascii, And Table Oriented Ascii Input File Format Types
Section 8. Working with Data Files on the PC Split’s default output file, a field-separated ASCII format with a *.PRN file extension, can be processed a second time if desired. TABLE 8–1 provides an example of Comma Separated, Field Formatted, Printable ASCII, and Table Oriented ASCII input file types.
Page 340: File Info
Section 8. Working with Data Files on the PC A maximum of eight input files may be processed by Split at one time. Additional input files are added using the EDIT | ADD DATA FILE menu option. Split looks for a file extension of .DAT if no extension is specified. If the Input File does not exist, an error message is displayed when RUN | GO is selected from the menu options.
Page 341 Section 8. Working with Data Files on the PC Last Count Each time Split runs a parameter file, it keeps track of the number of bytes it read from the input file and saves this information in the parameter file. Split can then start where it last left off.
Page 342 Section 8. Working with Data Files on the PC In the following figure, Split will skip the first 256 bytes of data before it begins processing the data in Input File. Align Array When using a specific start offset, the number of bytes specified may cause Split to seek to the middle of a row.
Page 343 Section 8. Working with Data Files on the PC Stop Offset This number specifies the number of bytes from the beginning of the file that Split should stop processing the data file. In the following figure, Split will skip the first 256 bytes of data before beginning and stop execution on byte 1024.
Page 344: Start Condition
Section 8. Working with Data Files on the PC For example, with an input timestamp of “2008-10-09 10:25” and an offset of 3600, the timestamp output by Date(“yyyy-mm-dd hh:nn”;1;1;1;1) would be “2008-10-09 11:25”. This may be useful when adjusting for different time zones. NOTE The offset will not be applied to Date and Edate functions with only two parameters.
Page 345 (1:1[–1]:1[1200]:1:)and the time is 1200 (1:1[– 1]:1[1200]:1:). As an expanded example, assume that LoggerNet is used to append data to an archive file. SplitR is executed using a desktop shortcut. In this case the frequency of data collection and data reduction is the same.
Page 346 Section 8. Working with Data Files on the PC data file (day, hrmn, sec.) are different each time the data are collected, but by telling Split where to Start reading relative to the PC clock, the Start Conditions do not need to be changed. To accommodate variations in the data collection and reduction frequencies, an interval in minutes or seconds may be specified as shown in the examples below.
Page 347: Stop Condition
Section 8. Working with Data Files on the PC 8.2.3.1.4 Stop Condition The Stop Condition specifies when to stop processing data. This feature allows segments of data to be removed from large data files. For instance, if a data file contains one month of data and just one day is desired, the start and stop values allow the user to get just that day’s data.
Page 348: Example Of Event Driven Test Data Set
Section 8. Working with Data Files on the PC Additional Input Files are added by choosing Edit | Add Data File from the Split menu. The same data file will be used as the Input File for each array. • Type in the array ID in the Copy field of the Input File tab for each array.
Page 349: Processed Data File Using Option C
Section 8. Working with Data Files on the PC To process these files using the C option, the parameter file would be set up as follows (assuming the name of our data file is Data_1.DAT): First Input File = Data_1.DAT:1 Stop condition = C,1[200] Copy = 1[100] Select = 1,2,3,4...
Page 350: Copy
Section 8. Working with Data Files on the PC processed but it is desired that the function affect one or more⎯but not all⎯of the files, the F option is used in the Stop Condition field of the files that you want processed using the function.
Page 351: Select
Section 8. Working with Data Files on the PC NOTE The Copy Condition is used almost exclusively for mixed-array dataloggers, except when time-syncing two or more data files. See Section 8.2.3.1.15, Time Synchronization, for additional information. Time Ranges When specifying a Copy condition, a range of time values can be specified instead of a single time.
Page 352: Ranges
Section 8. Working with Data Files on the PC 8.2.3.1.7 Ranges Element numbers may be entered individually (e.g., 2,3,4,5,6,7), or, in groups (e.g., 2..7) if sequential. Range limits (lower to upper boundary conditions) may be placed on elements or groups of elements specified in the Select or Copy lines.
Page 353: Variables
Section 8. Working with Data Files on the PC NOTE In this instance, out of range data refers to data outside of the specified output range. It is not to be confused with out of range data generated by the logger. 8.2.3.1.8 Variables Variables can be assigned names in the Select line.
Page 354: Mathematical Functions, Details, And Examples
Section 8. Working with Data Files on the PC 8.2.3.1.10 Mathematical Functions, Details, and Examples TABLE 8-6. Split Operators and Math Functions OPERATOR PRECEDENCE ORDER OPERATORS (3 = high, 1 = low) = raise to the power x Mod y = Modulo divide of x by y ∗...
Page 355 Section 8. Working with Data Files on the PC The following array of ASCII data will be used for all Mathematical function examples. 0105 0176 1200 –07.89 55.10 12.45 270.5 Abs(x) returns the absolute, or positive value of element x. Examples: Abs(4) = 7.89 Abs(4∗5) = 434.74...
Page 356: Time Series Functions, Details, And Examples
Section 8. Working with Data Files on the PC SpaMax(x..y) returns the maximum value of elements x through y. Examples: SpaMax(1..7) = 1200 SpaMax(1,2,5) = 176 SpaMin(x..y) returns the minimum value of elements x through y. Examples: SpaMin(1..7) = –7.89 SpaMin(1,2,5) = 55.1 SpaSd(x..y) returns the standard deviation of elements x through y.
Page 357 Section 8. Working with Data Files on the PC Time Series functions are used to perform vertical processing on selected elements, such as calculating the average of an element over a specified range of data. Time Series results are output in three instances: 1.
Page 358 Section 8. Working with Data Files on the PC Semicolons are used in Time Series functions to separate the elements or expressions from the count which determines the interval. SmplMax and SmplMin require two elements separated by a semicolon. The first is checked for a maximum or minimum, while the second is sampled on the maximum or minimum.
Page 359 Section 8. Working with Data Files on the PC Count(x;n) returns the number of data points (non blanks) in element x over a full data set or every n value. Example: Count(1) = 24 (24 data points in data set). NOTE Blanks and Count are functions designed for checking the integrity of the data file.
Page 360 Section 8. Working with Data Files on the PC 1.1182 (Sd temp for 8 hours) 4.965 (Sd temp for 8 hours) Smpl(x;n) returns a sample of element x every n value. Examples: Smpl(4;8) = 23.98 (RH every 8 hours) 24.31 (RH every 8 hours) 37.13 (RH every 8 hours) SmplMax(x;y;n) looks for a maximum value in element x and samples...
Page 361: Special Functions, Details, And Examples
Section 8. Working with Data Files on the PC 8.2.3.1.12 Special Functions, Details, and Examples TABLE 8-8. Split SPECIAL FUNCTIONS Crlf = Insert carriage return line feed in Output File. Date(“format”S;H;D;Y) = Convert day of year and time to a timestamp with calendar date and time, where format uses Windows conventions to specify output format.
Page 362 Section 8. Working with Data Files on the PC The Crlf is placed after the maximum temperature 67.33 so that the maximum RH is on the next line. A carriage return/line feed is recognized by Split as an element, NOTE and may throw the column headers off in the output file.
Page 363 Section 8. Working with Data Files on the PC 38.8 17.12 37.13 11.86 Smpl (Line;8), Smpl (4;8), Smpl (5;8) 23.98 6.588 24.31 8.88 37.13 11.86 smpl(.PA,n) Outputs the data to the printer or .RPT file with n lines per page. Examples: 2, 3, Smpl (.PA;12) = 58.56...
Page 364 Section 8. Working with Data Files on the PC When using the Date function for a table-based datalogger (e.g., a time stamp in the format “2002-02-03 21:16:00”), if the time stamp is the first element in the array, a 1 is used for all of the time stamp elements (S;...
Page 365 Section 8. Working with Data Files on the PC edate(“mm/dd/yy, hh:nn”;1;1;1;1) 02/25/02, 04:10 edate(“yyyy”, “dayofyear”, “hhnn”;1;1;1;1) 2002, 56, 0410 Notice that this last example essentially creates an array-type of timestamp. NOTE When processing a data file from a mixed array datalogger, if the time stamp uses midnight as 2400 with “today’s”...
Page 366: Split Functions Example
Section 8. Working with Data Files on the PC 8.2.3.1.13 Split Functions Example The following is a parameter file that operates on the Mt. Logan data with several of the Split features being utilized. This first screen shows the input file and the select criteria that were programmed.
Page 367 The National Weather Service includes wind chill in reports only when temperatures drop below 35°F (1.7° The formula is for example purposes and is not endorsed by Campbell Scientific as a standard. When this .PAR file is executed, the following output is displayed on the screen.
Page 368: Summary Of Select Line Syntax Rules
Section 8. Working with Data Files on the PC Wind Chill Report from Mt. Logan Temp Wind Speed Wind Chill Wind Chill deg C deg C deg F 14.756 2.6172 438.06 13.148 55.666 14.156 3.6967 489.58 10.813 51.463 13.806 3.4643 491.34 10.733 51.319...
Page 369: Time Synchronization
Section 8. Working with Data Files on the PC VALID EXPRESSION INVALID EXPRESSION Arctan (2/3) Arctan ((2/3)) Arctan (2/3, 3/4, 4/5) Arctan ((2/3, 3/4), 4/5) Arctan (COS(2)) Arctan (COS(2), COS(3)) • A single expression can operate on a set of elements. For example, the expression (3..6,8)/2.0 is the same as 3/2.0, 4/2.0, 5/2.0, 6/2.0, 8/2.0;...
Page 370 Section 8. Working with Data Files on the PC Typically, the starting time specified must actually be found in the input file before the Start Condition is satisfied (e.g., if the input file starts at 1100 hrs and 1000 hrs is entered for the starting time, with no day specified, Split will skip over arrays until it reaches 1000 hrs the next day).
Page 371 Section 8. Working with Data Files on the PC 8.2.3.1.15.1 Time Synchronization and the Copy Condition To use the time synchronize function, time element(s) must be specified in the Start Condition. The user must also specify a time interval in the Copy condition.
Page 372: Output Files
Section 8. Working with Data Files on the PC 8.2.3.2 Output Files To create an Output File, click the OUTPUT FILE tab. The file is created on the default drive or directory unless the file name is preceded with an alternative drive or directory.
Page 373: Description Of Output Option Commands
Section 8. Working with Data Files on the PC 8.2.3.2.1 Description of Output Option Commands File Format There are five File Format options to choose from: No File, Field, Comma, Printable, and Custom. If No File is chosen, then only the .PRN file is saved to disk.
Page 374 Section 8. Working with Data Files on the PC Screen Display The Screen Display field controls writing the processed data to the screen. To write to the screen, check the box. For faster execution, clear the box to omit writing to screen. The data will then be written to the file only. Report A report, with page and column headings, can be sent to a file or printer.
Page 375: Definition Of Blank Or Bad Data For Each Data File Format
Section 8. Working with Data Files on the PC It allows the following settings to be modified: Replace bad data with – The text in the field, to the right of this option, is entered into the .PRN output file data set if data are blank, bad, or out of range.
Page 376 Section 8. Working with Data Files on the PC The Copy Condition determines the interval of your data. Therefore, to output data that occurs every 24 hours, you would use: Copy Condition = 1:1[1]:1:1 Because you have specified a time in the Start Condition, but not the day, Split assumes the first day of the year.
Page 377 Section 8. Working with Data Files on the PC summary of the left over values and the Time Series Heading from the report. No Date Advance – When processing a data file from a mixed array datalogger, if the time stamp uses midnight as 2400 with “today’s” date, the date function will convert that time stamp to 0000 hours with “tomorrow’s”...
Page 378: Report Headings
Section 8. Working with Data Files on the PC Heading and Column Headings from being printed at the bottom of the report. The “left over” summary data will still be printed. No Record Numbers from TOB Files – Split automatically converts TOB (binary) files to ASCII prior to being processed.
Page 379: Editing Commands
Section 8. Working with Data Files on the PC 8.2.5 Editing Commands Split supports the Windows Cut, Copy, and Paste commands. Text from any field in Split or other Windows applications can be Cut, Copied, or Pasted. 8.2.6 Running Split From a Command Line Existing parameter files can be executed using Splitr.exe which is a “run-time”...
Page 380: Running Multiple Copies Of Splitr (/M Switch)
Section 8. Working with Data Files on the PC 8.2.6.1.3 Running Multiple Copies of Splitr (/M Switch) Multiple copies of Splitr can be run at one time by using the /M switch. This switch must appear immediately after Splitr. For instance, a batch file containing the lines: SPLITR /M Logan/R SPLITR /M Sinks/R...
Page 381: Input/Output File Command Line Switches For Processing Alternate Files
Section 8. Working with Data Files on the PC If a parameter is to be left as it is in the parameter file, then space comma space ( , ) may be entered in the command line. For instance, if the parameter file LOGAN.PAR contained TEST1.DAT as an input file name, the following command line would leave the input file TEST1.DAT and change the output file to TEST.PRN.
Page 382 Section 8. Working with Data Files on the PC /[text] Sets the text that will be used in the place of bad data. This is the same as the text string used in the Replace Bad Data field that is found under the Other button of the Output File tab.
Page 383 Section 8. Working with Data Files on the PC Removes the dashed lines from the heading of the RPT file. This is the same as choosing the No Dashes check box that is found under the Other button of the Output File tab. Removes the record number from TOB files that are processed with Split.
Page 384: Processing Multiple Parameter Files With One Command Line
Changes the value for midnight to 2400 instead of 0000. This is the same as selecting Midnight is 2400 Hours check box found under the Offsets/Options button of the Input File tab. Batch File Example “c:\Program Files\campbellsci\LoggerNet\splitr.exe” c:\Campbellsci\SplitW\switch-test.par input1a.dat Output.prn/E/H/W 4[1200]: , , 1..6 where PAR file: switch-test.par...
Page 385: Input/Output File Settings
Section 8. Working with Data Files on the PC 8.3.1 Input/Output File Settings The file settings are used to specify the directory where the binary data is stored, and the directory in which the converted file(s) should be saved. Press the Select Card Drive button to bring up dialog box that helps you browse for the drive assigned to the card reader.
Page 386: File Format
Hours/Minutes only, or a timestamp that includes Seconds only. CSIXML – Data is stored in XML format with Campbell Scientific defined elements and attributes. For more information, refer to Appendix B, Campbell Scientific File Formats.
Page 387: File Naming
Section 8. Working with Data Files on the PC given a numeric suffix prior to the *.dat extension. The first file is stored with a _1 at the end of the root file name (e.g., TOA5_Mytable_1.dat). The number is incremented by one with each new file saved. If a file with the same name is found, the number will be incremented to the next available number.
Page 388: Toa5/Tob1 Format
Section 8. Working with Data Files on the PC The Create New Filenames option is disabled when the Use Filemarks, Use Removemarks, or Use Time option is enabled. Append to Last File – When this option is selected, converted data will be appended to the end of the destination file.
Page 389: Viewing A Converted File
Section 8. Working with Data Files on the PC In some instances, data on a card can become corrupted. Corruption can occur if the card is subjected to electrostatic discharge or if it is removed when data is being written to the card (e.g., the card is removed from the CFM100 without pressing the Card Control button to stop data storage to the card).
Page 390 Section 8. Working with Data Files on the PC C:\Campbellsci\CardConvert directory. You should rename this file as it will be overwritten the next time that CardConvert is closed. When running CardConvert from a command line, you can designate the CCF file using the command line option runfile.
Page 391: Task Master
FTP client to send data to the Internet or a phone dialer to call a pager or phone upon an alarm condition. Also note that when running LoggerNet as a service, tasks being run by the Task Master cannot interact with the desktop. Therefore, any tasks set up in the Task Master should not require any user interaction.
Page 392: Automating Tasks With Task Master
Section 9. Automating Tasks with Task Master 9.1.1 Setup Tab 9.1.1.1 Adding Tasks To add a task that will run based on a data collection event for a datalogger, select the datalogger by clicking it. Then click the Add After button or select Add After from the Edit menu.
Page 393: Logger Event Tasks
Section 9. Automating Tasks with Task Master Tasks can be renamed by selecting the task and then clicking again on the task name. The name will turn into a text edit box and you can create your own task name. There is also a right click menu that will allow the same Add Scheduled, Add After, Rename, and Delete functions as described above.
Page 394 • After Any Call – The task is run any time LoggerNet attempts to contact the datalogger. This will run even if the datalogger does not respond or no data is collected.
Page 395: Scheduled Event Tasks
Section 9. Automating Tasks with Task Master 9.1.1.3 Scheduled Event Tasks An alternative to event driven tasks, scheduled tasks are repeated at a specified interval or based on the calendar. 9.1.1.3.1 Interval Tasks The Base Date and Time are used to set the initial date and time for the task execution.
Page 396: Calendar
Section 9. Automating Tasks with Task Master 9.1.1.3.2 Calendar Set the Hours of the Day, Minutes of the Hour, Days of Month, Days of Week, and Months on which the task should be executed. The task will run when ALL of the specified settings are met. If a setting is left blank, it will always apply.
Page 397 Section 9. Automating Tasks with Task Master Month to 1, 2, 3, 4, 5, 6, 7, the Days of the Week to 2-Monday, and leave the other settings blank. To execute a task on the fifth day of every quarter at midnight, set the Hours of the Day to 00, the Minutes of the Hour to 00, the Days of the Month to 5, the Months to 1-January, 4-April, 7-July, 10-October, and leave the other settings blank.
Page 398: Define What The Task Does
Section 9. Automating Tasks with Task Master 9.1.1.4 Define What the Task Does The “What Task Does” tab describes the action that will be taken when the task is triggered. From this tab, select a sub-tab to set up the action(s) that should be performed by the task.
Page 399 Task Master. (If you are running Windows as a restricted user or if you are running LoggerNet as a service, you must explicitly set all file paths in the batch file.) The Task Master may not be able to process certain characters on a command line, such as the redirect (<) character.
Page 400 Section 9. Automating Tasks with Task Master Any data file associated with the designated station will be transferred, whenever that file is closed. (Therefore, a tables File Output Option on the Setup Screens Data Files tab must be set to anything but “No Output File” in order for the tables collected data to be transferred.) If more than one file is closed (i.e., multiple tables are collected and written), all of the files are transferred.
Page 401 If LoggerNet security is enabled, the command line options must also include the username and password as shown below: –user=“username” –password=“password” If you have used a command line argument to change LoggerNet’s default port number, the command line options must also include the server address and port number as shown below: –server=server_address:port (e.g., LocalHost:6700 or 192.168.7.123:6700)
Page 402 Section 9. Automating Tasks with Task Master 9-12...
Page 403: Status Tab
After task, the device which the task is dependent upon will be listed. Last Time Run – The last time that the task was run by LoggerNet. Next Time to Run – The next time that the task is scheduled to be run. If the task is not a scheduled task (interval or calendar), this field is not applicable and will be left blank.
Page 404 Section 9. Automating Tasks with Task Master Pending Actions – Species the number of actions that are currently pending for this task. This value will be zero if there are no actions currently pending. An increasing number may indicate that you are attempting to run the task faster than is possible.
Page 405: Remote Administration Of The Task Master
9.1.3 Remote Administration of the Task Master In LoggerNet Admin and LoggerNet Remote, the File | Select Server option allows you to select the LoggerNet server to which the Task master should connect. You also specify the username and password to be used.
Page 406 Section 9. Automating Tasks with Task Master 9-16...
Page 407: Utilities Installed With Loggernet
LoggerNet Along with LoggerNet’s server, clients and program editors, we also install several utilities. These are launched either from the Utilities category of the LoggerNet toolbar or from a command line calling the executable itself. These utilities include Device Configuration Utility, an application that uses a serial or an IP port to configure...
Page 408: Main Devconfig Screen
Section 10. Utilities Installed with LoggerNet 10.1.2 Main DevConfig Screen The DevConfig window is divided into two main sections: the device selection panel on the left side and tabs on the right side. After choosing a device on the left, you will then have a list of the serial ports (COM1, COM2, etc.) installed on your PC.
Page 409: Downloading An Operating System
10.1.3 Downloading an Operating System DevConfig can send operating systems from the Send OS tab to all Campbell Scientific devices with flash replaceable operating systems. An example for the CR1000 is shown below: The text at right describes any interface devices or cabling required to connect the PC to the device.
Page 410 Section 10. Utilities Installed with LoggerNet When the operating system has been sent to the device, a message dialog will appear similar to the one shown below: The information in the dialog helps to corroborate the signature of the operating system sent. For devices such as the CR10X (especially those with extended memory) that can take a long time to reset following an OS download, text warns you against interrupting the memory test.
Page 411: Terminal Tab
Section 10. Utilities Installed with LoggerNet 10.1.4 Terminal Tab The Terminal tab will be available when the application is connected to any device type that can be communicated with in a remote terminal mode. The Terminal tab offers a terminal emulator that can be useful in accessing settings or status information that are not exposed in other windows.
Page 412: Off-Line Mode
Section 10. Utilities Installed with LoggerNet Clicking Connect puts DevConfig into Terminal emulation mode on the Serial Port and at the Baud Rate selected. When you click on Identify Datalogger Type, DevConfig will attempt to identify the type of device that is connected on the specified serial port. It will attempt to communicate using each of the datalogger protocols (mixed-array, table-data, and PakBus) in turn.
Page 413: Corascript
LoggerNet server operations. Because the commands available in CoraScript operate directly NOTE on the LoggerNet server and not through a user interface, there are no confirmation prompts for critical operations. Care should be exercised in using the commands to avoid interrupting normal server operations.
Page 414: Connecting To The Loggernet Server
10.2.2.1 Connecting to the LoggerNet Server Before you can execute any commands a connection to the LoggerNet server must be established. The connect command sets up the server context in which subsequent commands will operate until the end of the script is reached or another connect command is processed.
Page 415: Hole Management
By default, the data cache will not be saved, so it may be a good idea to include at least this option if your intent is to fully restore LoggerNet to the exact state it was in when the backup was created. In this instance, the command would be: +create-backup-file include-tables=“true”;...
Page 416: Scripting Corascript Commands
To automate network processes, scripts can be created with other scripting language tools that would call the CoraScript interpreter, and send commands to the LoggerNet server. This provides an alternate means of controlling data collection, hole collection and maintenance functions such as clock check and set.
Page 417: Adding A New Rwis Station
You must enter a valid Station Name for the new station. (Note that you will not be able to enter a name that is already used in LoggerNet’s network map.) You will also need to choose the Station Type from the drop-down list. The type must either be NTCIP-ESS Version 1 or NTCIP-ESS Version 2.
Page 418: Editing Station Settings
Controls on this panel include the following: Host IP Address – Enter the IP address for the station. This setting must match that used by the physical device in order for LoggerNet to be able to successfully communicate with the RWIS station.
Page 419: Schedule Settings
RWIS station. These parameters will be used when snapshots are retrieved. FTP Port – Enter the TCP port number that the LoggerNet server will use when downloading snapshots from the RWIS station. In most cases, the default value of 21 should be adequate.
Page 420 Section 10. Utilities Installed with LoggerNet Stay On Schedule – By default, when LoggerNet has missed a scheduled poll because of some condition (i.e. LoggerNet was closed, scheduled polling was disabled, the schedule was paused from the Status Monitor, etc.), once the...
Page 421: Snapshots Settings
File Path – Specifies the directory and name of the file written for the selected table. For remote LoggerNet connections, this path must be specified in terms of the remote server’s file system. The following sequences may be used when defining the path: %a –...
Page 422: Clock Settings
The source paths can be optionally specified in the Source Path box. If a path is specified, LoggerNet will use this setting to specify the snapshot path. If the path source is not specified here, LoggerNet will interpret the value of the device’s essSnapShotCameraStoragePath variable as providing both the path...
Page 423 PC, and you want the station to reflect the local time when the clock is set. LoggerNet Data/Time – Displays the date and time for the computer on which the LoggerNet server is running. This value will be displayed/updated only when the Check button is pressed.
Page 424: Data Tab
XML file that, at present, is statically linked as a part of the LoggerNet server DLL. Future versions may have the ability to dynamically specify tables and variable assignments within those tables.
Page 425: File Format Convert
The size of these arrays will depend upon the value read from the variable that is defined as the “dimensioning” variable. If the value of this variable ever changes, the LoggerNet server will evaluate whether the current table definitions should be changed. If the current table definition already defines enough values to match the current value, no change will take place.
Page 426: Options
Section 10. Utilities Installed with LoggerNet • TOA5 • TOACI1 • TOB1 • CSIXML • File Format Convert cannot produce TOB2 or TOB3 files, and it NOTES cannot read CSV files. Some file headers have less information than other formats. If you convert from a file with more information in the header to one with less, information will be lost.
Page 427 Section 10. Utilities Installed with LoggerNet Files can be baled if missing records are found. See the Bale based on information below. When checking timestamps, “null” records can be written to “fill” missing records. See Missing Records information below. File Check Write File to cause an output file to be created.
Page 428: Toa_To_Tob1
Section 10. Utilities Installed with LoggerNet Remove Marks – A new file is created when a remove mark is found in the data file (TOB3 only). File Marks – A new file is created when a file mark is found in the data files (TOB3 and TOB2 only).
Page 429: Utilities Installed With Loggernet Admin And Loggernet Remote
Filer, Data Export, LN Server Monitor, LoggerNet Service Manager, and Security Manager. The LoggerNet Service Manager, which allows LoggerNet to be run as a service, is discussed in the installation notes (Section 2, Installation, Operation and Backup Procedures). The LN...
Page 430: Managing User Accounts
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote Enter the IP address or alias for the LoggerNet server (e.g., LocalHost), leave the User Name and Password fields blank, and press OK. A wizard is launched to help you set up an Administrator Account, which will be used for managing the security for the LoggerNet network.
Page 431: Security Manager Access Table
Full Administrator – The user has full access rights in all LoggerNet clients, including the Security Manager. If an option in the LoggerNet user interface is not applicable for the security level of the user logged in to LoggerNet, that option will be disabled. The following table provides an overview of the functions available to each level of security.
Page 432 Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote TABLE 11-1. Security Manager Access Table Read Station Network Full Only Operator Manager Admin Admin View/configure ports/flags Toggle ports/flags View Status Table Change Status Table Reset data tables via Station Status/Table Fill...
Page 433: Resetting Security
The LoggerNet Admin Hole Monitor Utility is used to monitor the hole collection activity for the dataloggers in a LoggerNet network. A hole is any discontinuity of data in the LoggerNet server’s data cache for a datalogger. Holes can occur if the server is unable to collect data from a...
Page 434: Hole Collection Activity
11.2.1 Hole Collection Activity The main window for the Hole Monitor is shown below. The list of stations in the LoggerNet datalogger network is displayed on the left side of the Hole Monitor Utility’s main window. You can monitor hole...
Page 435: Message Log
– This state, printed with blue text, indicates that LoggerNet has made attempts to collect the hole since it was detected by the hole monitor application. collected – This state, printed with green text, indicates that the server has succeeded in collecting the hole.
Page 436: Data Filer
Data Filer is a LoggerNet application that is used to retrieve data from the LoggerNet data cache, and save the data to a file. It provides a means for a user to manually retrieve and store ASCII data on a remote PC, which can then be used for further analysis.
Page 437: Setting Up The Data Filer
11.3.2.2 Collection Options Collect Mode This option is used to specify what data will be retrieved from the LoggerNet data cache and stored on the remote computer by the Data Filer: All the Data – Retrieves all records from the selected tables.
Page 438 Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote File Format This option is used to determine the format in which the data file will be saved: TOACI1 – Data is stored in a comma separated format. Header information for each of the columns is included.
Page 439: The Collected Data
Table Name – The name of the data storage table in the datalogger. # of Records – The number of records in LoggerNet’s data cache for the table. By default, the size of the data cache for each datalogger table is set to two times the size of the table in the datalogger.
Page 440: Record Number Anomalies
As an example, if the datalogger’s internal table size were 100 records, LoggerNet’s cache would be sized at 200 records. If both had rung around and LoggerNet’s cache now held record numbers 201–400 and someone re-sent the same program to the datalogger, LoggerNet would not clear its data cache, but would continue to store the new records.
Page 441 If Collected Order is selected, Data Export will export records as they are collected by the LoggerNet server. With this option, it is possible that data records are exported out of order.
Page 442: Theory Of Operation
Database Server The LoggerNet server has the responsibility to see that every collectable record is collected from the network of dataloggers. The collected data is stored in the data cache of the server. When the Data Export client is first initialized it sets up the socket and then waits for a data retrieval client to connect.
Page 443: Custom Data Retrieval Client
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote the unsent records remain in the LoggerNet server’s data cache. The Data Export maintains transfer progress information on disk so that if the server goes down or there is another problem with the transfer, it can recover and continue to transfer all collectable records.
Page 444 If the Data Export application loses its connection with the LoggerNet communication server, it will need to be re-connected before any records can be obtained and sent out.
Page 445 Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote Reg Failed/ Start Stop Report Running Connect Failed/ Server Registration Report entry: Register Server ( ) Server Registered exit: Deregister Server ( ) Reg OK/Report Wait For Client Connection entry: Open Session ( )
Page 446 Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote report a broken socket and so the watchdog is necessary for reliability. Rec Intv 2 This is an amount of time greater than 2 times the expected interval between data records. It is just...
Page 447 Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote well being of that record. The server moves on to the next record. Stop Note that in the Session Open and Server Registered states there are “exit” actions that need to be executed on the Stop event.
Page 448: Rtms Format Description
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote 11.4.5 RTMS Format Description The EBNF description of RTMS syntax is as follows: Record = ( DataRecord | AckRecord ) CRLF. DataRecord = StationName “,” TableName “ (“ FieldSpecs “) VALUES (“ FieldValues “)”.
Page 449: Standard Format Description
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote 11.4.6 Standard Format Description The following is an EBNF syntax of a new record format that we have developed that we believe is more digestible than the pseudo-SQL syntax that...
Page 450 Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote 11-22...
Page 451: Optional Client Applications Available For Loggernet
Applications Available for LoggerNet Several client applications are available that are compatible with LoggerNet. Many of these allow remote access to the data in the LoggerNet data cache, or provide a way to post process that data. Client applications include LoggerNetData, RTMC-RT, RTMC Pro, LNDB, Baler, OPC Server, and the LoggerNet SDKs.
Page 452: Rtmc Run-Time
Baler is a LoggerNet client application that allows you to set up a schedule on which data will be retrieved from the LoggerNet server and saved to a file on a remote computer. Tables are selected for baling from the dataloggers in the LoggerNet network.
Page 453: Csiopc Server (Pc-Opc)
12.7 CSIOPC Server (PC-OPC) The CSIOPC Server is a LoggerNet client that makes OPC data available to third-party OPC clients. OPC is an acronym for “OLE (Object Linking and Embedding) for Process Control”. It is a set of industry standards, based on Microsoft’s OLE technology, designed to provide a common interface between...
Page 454 Section 12. Optional Client Applications Available for LoggerNet 12-4...
Page 455: Implementing Advanced Communications Links
RF base. LoggerNet will make a call each time that it does data collection for a station. It will stay on-line until a response is received — either the data, or an error indicating that the data collection failed.
Page 456: Operational Considerations
RF systems this value should be long enough to allow data collection for the anticipated amount of data. If the Max Time Online is reached, LoggerNet will force the connection to close, even if it is in the middle of collecting data.
Page 457: Hardware Setup
The datalogger and the RF base must both be connected to the remote phone modem on the same 9 pin ribbon cable. 13.1.3.2 Network Setup in LoggerNet Setting up a datalogger at the RF base in a Phone to RF system requires that the datalogger be connected as a child of the remote phone modem, and the RF Base be connected as a child of the datalogger.
Page 458: Operational Considerations
13.2.2.2 MD9 Addresses The address for an MD9 base device is set in the LoggerNet communications software at 255. The hardware configuration in the MD9 base modem must match for successful communications (refer to your MD9 users manual for information on setting the hardware switches within the device).
Page 459: 1Grounding
Section 13. Implementing Advanced Communications Links collection for the anticipated amount of data. If the Max Time Online is reached, LoggerNet will force the connection to close, even if it is in the middle of collecting data. 13.2.2.5 1Grounding Depending on the configuration and distance of the MD9 network, be sure to follow the grounding guidelines provided in the MD9 hardware manual.
Page 460: Special Considerations
IP address – This is the Internet Protocol address that is used by LoggerNet to communicate with the serial server. This address must be unique on the network where it is running and is typically assigned by a network administrator.
Page 461 Section 13. Implementing Advanced Communications Links Subnet Mask – This setting is used to limit the search applicability area for IP addresses. If both the server and the serial server are in the same low level subnet this would be set to 255.255.255.0. Consult with the network administrator for the proper setting.
Page 462 Section 13. Implementing Advanced Communications Links 13-8...
Page 463: Troubleshooting Guide
This section is provided as an aid to solving some of the common problems that might be encountered using the LoggerNet software. This list is not comprehensive but should provide some insight and ability to correct simple errors without a call to Campbell Scientific technical support.
Page 464: Socket Errors
Toolbar and start over. 14.2.2 Socket Errors The LoggerNet Server uses TCP/IP sockets for communications. Various problems can occur with these socket connections. Some of the most common errors and remedies are listed below.
Page 465: Socket Error Messages
10047 Address family not This message shows up when the supported by protocol LoggerNet Toolbar comes up but the family. The socket being server did not come up because addressed does not TCP/IP is not installed on the support the type of computer.
Page 466: Data Collection Issues
Collect Now button. This will force collection from the datalogger and will return the datalogger to the normal collection state. Invalid Table Defs indicates that LoggerNet does not have a current copy of the datalogger table definitions. You will need to update the table definitions from the Setup Screen or the Connect Screen.
Page 467: Terminal Emulator To Test Communications
COM port, the baud rate will typically be 115,200 baud and LoggerNet simply opens the port. For a phone modem, the baud rate will be set to the value in the Setup Screen for that phone modem, the COM port will be opened and the DTR line will be asserted to enable the phone modem.
Page 468 You can work with the modem by selecting it in Terminal Emulator and clicking Open Terminal. LoggerNet will open the COM port and raise DTR to enable the modem. You can then type characters to be sent to the modem. For example,...
Page 469 Section 14. Troubleshooting Guide assume you have a Hayes-compatible modem and an array-based datalogger on a phone link with the phone number “752-7779”. You could test the link with the following sequence: Type ATH <Enter> To hang up the modem. You should see an “OK” on the screen sent by the modem.
Page 470: Rf Communication Link Issues
ATH <Enter> To hang up your base modem. If the modem you select in LoggerNet’s Setup Screen doesn’t work, check to make sure you’ve selected the correct modem, that it’s powered up and that the phone line is working. You may have to adjust the baud rate. If you still have trouble, you may need to consult your modem manual for the appropriate initialization strings.
Page 471: Checking Rf Components And Connections
RF modems require specific cables to make the right connections. For questions in this area, contact the network installer or Campbell Scientific. 5. Check that the antenna is the right type (directional or omnidirectional) and is designed for the frequency being used. Most antennas will have labels identifying the frequency range.
Page 472 Section 14. Troubleshooting Guide If you are using a data radio that does not have a transmit button NOTE built in, you can easily build a push to transmit button from the documentation of the radio/RF modem interface connector. There will be one pin that when pulled high or pulled low will initiate radio communication.
Page 473: Troubleshooting With Attenuation Pads
The sub-links should be checked in both directions of communication. Before proceeding, it is a good idea to calculate the theoretical signal power for each of the RF links. Appendix C of Campbell Scientific’s RF Telemetry manual outlines the calculations.
Page 474 Section 14. Troubleshooting Guide and subsequently the radio will not detect the signal, the signal power is between –95 and –115 dBm which is below the power limit for good data transmission. Similarly, if a 10 dBm attenuation pad is inserted in the link and the radio subsequently will not detect the signal, the actual signal power is between –105 and –115 dBm.
Page 475: Using Data Table Monitor
Data Table Monitor is a utility that was created to retrieve data from the LoggerNet server data cache and display it on the screen. It also has the option to export it to a file. Once the utility has been started, as new records are collected by the server, the new records will be displayed and sent to the file.
Page 476 Files\CampbellSci\LoggerNet directory. Double click the Tablemon2.exe file. The utility will start with a screen similar to the one shown below. Click the Connect button to connect to the LoggerNet server. The dialog box shown below will be displayed. If you are working on the same computer where LoggerNet is running leave the default Server Host Address as localhost.
Page 477 Section 14. Troubleshooting Guide Setup Screen, no data will be coming into the data cache. Data Table Monitor can only display and output data from the data cache. Data Table Monitor displays and outputs all the data points from an array or table. Click the Start button to bring up the Start Advise Options dialog.
Page 478 • XML – Data is stored in XML format with Campbell Scientific defined elements and attributes. For additional information, refer to Appendix B, Campbell Scientific File Formats.
Page 479: Troubleshooting Pakbus Communications
Remedy 4: If you have two in-range routers using neighbor filters, in order for them to discover one another you must list each of them as a potential neighbor in the other’s neighbor filter. Problem: LoggerNet can’t communicate via datalogger-router to a certain remote datalogger. (PC-RF400~~~RF400-CR10XPB~~~RF400-CR510~~~CR205) Possible reason 1: A datalogger router has insufficient *D15 max nodes, max neighbors, or max routers configured.
Page 480 Problem: Can’t LoggerNet communicate with datalogger-router in network? (PC-RF400~~~RF400-CR10XPB~~~CR205) Possible reason: The datalogger-router has more than one M.E.
Page 481 Section 14. Troubleshooting Guide Possible reason: Two network devices have the same PakBus Address. Remedy: Change one of the duplicate PakBus Addresses. Make all addresses unique throughout the network. Problem: In P193 network, certain CR200 Series devices don’t transfer data. Possible reason: The Master datalogger’s *D15 setting configures too few max nodes, max neighbors, and max routers.
Page 482 Section 14. Troubleshooting Guide 14-20...
Page 483: Glossary Of Terms
Appendix A. Glossary of Terms Advise – See Data Advise ASCII File – A computer file containing letters, numbers, and other characters using the ASCII character encoding. Asynchronous – The transmission of data between a transmitting and a receiving device occurs as a series of zeros and ones. For the data to be “read” correctly, the receiving device must begin reading at the proper point in the series.
Page 484 SDI-12 sensors. CoraScript – A command line interpreter client to the LoggerNet server that allows the user access to many of the capabilities of the LoggerNet server using direct commands or programmed script files. CR10X-TD Family of Dataloggers – Any of the Edlog dataloggers with table-data operating systems become “TD”...
Page 485 DevConfig – Short for “Device Configuration Utility”, a software application that provides a graphical user interface to configure settings in dataloggers and communications peripherals. Available in PC400, LoggerNet, and as a stand- alone application from the Campbell Scientific website. (Supplants CSOS.EXE, PakCom, and stand-alone terminal emulators.)
Page 486 Appendix A. Glossary of Terms Edlog – Campbell Scientific’s software application used to create new or edit existing datalogger programs. Edlog supports all of the programming capabilities in the dataloggers it supports. (Program generators such as Short Cut are necessarily more limited in the features they can support.) Edlog Datalogger –...
Page 487 Appendix A. Glossary of Terms Ground Connection – Most sensors require one or more ground connections in addition to excitation or signal inputs. Ground connections may serve any of several purposes: • a reference for a single-ended (SE) analog voltage (use analog ground if available) •...
Page 488 They contain information about communications between the communications server and other devices in the datalogger network. Log files are typically used for troubleshooting purposes. LoggerNet has four types of log files: Transaction, Communications Status, Object State, and Low Level I/O.
Page 489 Net Description – Description of dataloggers and communications devices that form the datalogger network. Created using the EZWizard in PC400 or Setup Screen in LoggerNet to communicate with the various dataloggers. Node – Part of the description of a datalogger network. Each node represents a device that the communications server will dial through or communicate with individually.
Page 490 Appendix A. Glossary of Terms Packet – a unit of information sent between two BMP or PakBus devices that are communicating. Each packet can contain data, messages, programming, etc. Usually contains addressing and routing information. PakBus – A packet-based and packet-switched networking protocol used by newer dataloggers.
Page 491 RTMC – Real Time Monitoring and Control software. A client application to the communications server that displays data from the server’s data cache (only) and updates as new data is collected. RTMC is relatively easy to set up, and ships with LoggerNet.
Page 492 Campbell Scientific for fast real-time data acquisition. RTMS included both communications and graphical display features and was designed for IBM’s OS/2 PC operating system and replaced by LoggerNet, RTMC and RTDM. Scan Interval – See Execution Interval. SDI-12 – SDI-12 stands for Serial Digital Interface at 1200 baud. It is an electrical interface standard and communications protocol that was originally developed by Campbell Scientific and other manufacturers for the U.S.
Page 493 Appendix A. Glossary of Terms Station Number – The LoggerNet server assigns and uses station numbers for routing packets to the dataloggers. These numbers can be modified using CoraScript. Not to be confused with datalogger serial numbers, PakBus addresses, or addresses set in communications peripherals such as RF or MD9 modems.
Page 494 Appendix A. Glossary of Terms Variable Name – Edlog uses variable names in expressions. Variables are another name for input location labels. For instance, in the equation TempF = (TempC*1.8) + 32, TempC is an input location label and TempF is a new location calculated from TempC.
Page 495: Campbell Scientific File Formats
PC files. The data formats written to PC files by LoggerNet are written by default as .DAT files. The following sections will focus on the format of these PC files, discuss the data formats that exist in the datalogger and on PC cards, and describe methods for converting binary data formats.
Page 496: Ascii Printable
Appendix B. Campbell Scientific File Formats B.1.2 ASCII Printable Files in ASCII Printable format have the following features: • Data are printed in fixed field widths. • The length of each line of text in the file will not exceed 79 characters.
Page 497: B-1. Output Instruction Suffixes
Appendix B. Campbell Scientific File Formats B.1.3.1 Field Name Suffixes Each field name will have a suffix corresponding to the output instruction used as described in the table below: TABLE B-1. Output Instruction Suffixes Instruction Description Suffix Totalize Totalize Average...
Page 498: Toa5
"2004-11-11 15:04:15",2,13.7,24.98 B.1.5 TOB1 TOB1 files can be generated by LoggerNet when outputting data files to the PC. This binary file format is typically only used when it is essential to minimize the file size or when other software requires this format. It has the...
Page 499 Appendix B. Campbell Scientific File Formats An example of a TOB1 ASCII header: "TOB1","STATION","CR9000","1000","1.00","CPU:BIG.DLD","25871","VALUES" "SECONDS","NANOSECONDS","RECORD","Array(1)","Array(2)","Fast","my_string" "","","RN","mVolts","mVolts","mVolts" "","","","Smp","Smp","Smp" "ULONG","ULONG","ULONG","IEEE4","IEEE4","FP2","ASCII(25)" Header line one describes the file environment with the following eight fields: • Data file type (TOB1). • Station name (STATION). •...
Page 500: Array Compatible Csv
Appendix B. Campbell Scientific File Formats The timestamp and record number for each record are an optional output in a TOB1 file. If these elements are present, a “SECONDS”, “NANOSECONDS”, and “RECORD” column will be generated as names in the field list of header line two.
Page 501: B-2. Pre-Defined Xml Entities
Appendix B. Campbell Scientific File Formats XML documents possess a tree structure that consists of elements and element attributes. The document is expected to have a single root element which can contain any number of sub-elements which in turn can contain any number of sub-elements and/or other content.
Page 502: File Syntax
Appendix B. Campbell Scientific File Formats In addition to these pre-defined entities, arbitrary unicode characters can be represented by using the sequence &xxx; where xxx is the decimal unicode code value for the desired character. For more details regarding XML documents and their contents, you can visit the W3C consortium web page at http://www.w3.org/XML.
Page 503 Appendix B. Campbell Scientific File Formats <xsd:element name="model" type="xsd:string" minOccurs="0" maxOccurs="1"/> <xsd:element name="serial-no" type="xsd:unsignedInt" minOccurs="0" maxOccurs="1"/> <xsd:element name="os-version" type="xsd:string" minOccurs="0" maxOccurs="1"/> <xsd:element name="dld-name" type="xsd:string" minOccurs="0"/> <xsd:element name="dld-sig" type="xsd:unsignedShort" minOccurs="0" maxOccurs="1"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="fieldsType"> <xsd:element name="field" type="fieldType" minOccurs="1" maxOccurs="unbounded"/> </xsd:complexType>...
Page 504: The Csixml Element
Appendix B. Campbell Scientific File Formats <xsd:attribute name="units" use="optional" type="xsd:string"/> <xsd:attribute name="process" use="optional" type="xsd:string"/> </xsd:complexType> <xsd:complexType name="dataType"> <xsd:element name="r" type="recordType" minOccurs="0" maxOccurs="unbounded"/> </xsd:complexType> <xsd:complexType name="recordType"> <xsd:attribute name="no" type="xsd:unsignedInt" use="optional"/> <xsd:attribute name="time" type="xsd:dateTime" use="optional"/> <xsd:element minOccurs="1" maxOccurs="unbounded" type="valueType"> <xsd:annotation> <xsd:documentation xml:lang="en">...
Page 505: The Head Element
Appendix B. Campbell Scientific File Formats B.1.7.3.1 The head Element This element contains the meta-data or descriptive data for the table. It does not have any attributes and has exactly two sub-elements, environment and fields. B.1.7.3.1.1 The environment Element This element contains sub-elements that provide information about the station that generated the data and the program running on it.
Page 506: B-3. Field Data Types
Appendix B. Campbell Scientific File Formats TABLE B-3. Field Data Types xsd:string Specifies string content xsd:long 64 bit signed integer xsd:unsignedLong 64 bit unsigned integer xsd:int 32 bit signed integer xsd:unsignedInt 32 bit unsigned integer xsd:short 16 bit signed integer...
Page 507: File Example
Appendix B. Campbell Scientific File Formats B.1.7.3.2.1.1 The v (value) Element This element conveys one scalar value (or string) for a field. There will be one of these elements for each field element defined in the fields element of the header.
Page 508: Csijson
Appendix B. Campbell Scientific File Formats <v20>2006-08-15T00:28:05</v20> <v21>127.8</v21> <v22>0</v22> <v23>2006-08-15T01:39:45</v23> <v24>0</v24> <v25>1108</v25> <v26>2006-08-15T10:13:37</v26> <v27>24.76</v27> <v28>766.1</v28> <v29>2006-08-15T07:15:00</v29> <v30>761.7</v30> <v31>2006-08-15T18:30:00</v31> <v32>0.254</v32> </r> <r no="341" time="2006-08-17T00:00:00"> <v1>12.97</v1> <v2>2006-08-16T16:09:52</v2> <v3>31.16</v3> <v4>2006-08-16T15:49:27</v4> <v5>10.43</v5> <v6>2006-08-16T06:13:46</v6> <v7>52.5</v7> <v8>2006-08-16T22:20:10</v8> <v9>32.15</v9> <v10>2006-08-16T10:19:42</v10> <v11>30.34</v11> <v12>2006-08-16T15:37:33</v12> <v13>10.06</v13> <v14>2006-08-16T05:25:24</v14> <v15>84.6</v15> <v16>2006-08-16T04:26:52</v16> <v17>13.21</v17>...
Page 509: A Short Introduction To Json
Appendix B. Campbell Scientific File Formats B.1.8.1 A Short Introduction to JSON Much like XML, JSON is a recursive structure with a root object (represented by an opening and closing curly brace (‘{‘ and ‘}’). This root object can contain named strings, numbers, objects, and arrays. A simple object specification follows: "head": {...
Page 510 Specifies the name of the station. This can either be the station_name name of the “Station Name” setting or can be the name of the station device in LoggerNet’s network map. table_name Specifies the datalogger table name. Specifies the model of the datalogger that produced this model data.
Page 511 Appendix B. Campbell Scientific File Formats B.1.8.2.1.4 head.fields Array The fields object is an array of field descriptions for the data contained in this file. The order and number of field descriptions in this array must match exactly that of the actual data.
Page 512: The Data Array
Appendix B. Campbell Scientific File Formats B.1.8.2.2 The data Array The data array is an array of record objects. Each record object will contain the following subordinate objects: An integer that specifies the record number as assigned by the datalogger.
Page 513: Datalogger Data Formats
Appendix B. Campbell Scientific File Formats 69.62625, "2010-01-19T07:53:40", 73.69058, 78.82542, "2010-01-19T17:41:05" "no": 44, "time": "2010-01021T00:00:00", "vals": [ 70.85629, "2010-01-20T08:14:40", 74.24667, 77.28296, "2010-01-20T17:41:51" "no": 45, "time": "2010-01-22T00:00:00", "vals": [ 70.90952, "2010-01-21T07:17:08", 74.41795, 78.02577, "2010-01-21T17:39:01" B.2 Datalogger Data Formats B.2.1 TOB2 or TOB3 TOB2 and TOB3 files are created when data are retrieved from external PC cards on dataloggers such as the CR9000, CR5000, and CR1000.
Page 514 Appendix B. Campbell Scientific File Formats The TOB2 or TOB3 binary file format has the following structure with each header line terminated with a carriage return and line feed (CRLF): ASCII Header Line 1 ASCII Header Line 2 ASCII Header Line 3...
Page 515: Binary Data Value Types
B.3.1 FP2 (2 Byte Low Resolution Format) A two-byte floating-point number format created by Campbell Scientific, Inc. and used to store low-resolution values. Appendix C of the CR10X datalogger manual describes this format in greater detail. Basically, this format consists of a single sign bit, a two-bit negative decimal exponent, and a 13-bit mantissa.
Page 516: Converting Binary File Formats
PC. Binary files may be output as data files to the PC by LoggerNet to save hard disk space or to accommodate a user that is only interested in using binary files in an application.
Page 517: Tob32.Exe
Appendix B. Campbell Scientific File Formats B.4.5 TOB32.EXE The TOB32.EXE command line utility is installed by default in the LoggerNet program directory at C:\Program Files\Campbellsci\Loggernet\tob32.exe. The output is similar to CardConvert. Command line switches are used to determine the new file format that will be created. Some of the basic switches...
Page 518 Appendix B. Campbell Scientific File Formats Only without the tabs and carriage return in the middle. One with strings might look like this. PC1,StatMsg (TMSTAMP TIMESTAMP,RECNBR DECIMAL(10,0),SrcStn VARCHAR(256),AbtStn VARCHAR(256),Hop DECIMAL(3,0),Message VARCHAR(256)) VALUES ('1993-12-08 15:02:02.25',13355,'PC1','StatMsg',0,'DBSelect End Pipe Queue Dump') The acknowledgment records to be sent back to the server for the two records...
Page 519: Memory Allocation For Final Storage
Appendix C. Table-Based Dataloggers This section describes some of the characteristics and features of the CR10X-TD family and CRx000 family of table-based dataloggers. The dataloggers included in these families are CR510-TD, CR10T, CR10X-TD, CR23X-TD, CR3000, CR800, CR1000, CR5000, CR200, and CR9000. C.1 Memory Allocation for Final Storage The datalogger memory includes four important areas: the datalogger program storage, input storage, intermediate storage, and final storage.
Page 520: Cr5000/Cr1000/Cr3000/Cr800/Cr9000 Memory For Programs And Data Storage
Appendix C. Table-Based Dataloggers Event driven tables should have a fixed size rather than allowing NOTE them to be allocated automatically. Event driven tables in CR10X-TD type dataloggers that are automatically allocated are assumed to have one record stored per execution interval in calculating the length.
Page 521: Converting An Array-Based Program To A Cr10X-Td Table-Based Program Using Edlog
The CR200 Series dataloggers do not have an on-board compiler. Programs must be precompiled by LoggerNet, or when using the CRBasic Editor, before they are sent to the datalogger. Refer to Section 5.1.5.2, CR200 Series Programs, for additional information about sending programs to CR200 dataloggers.
Page 522: Program Instruction Changes
Appendix C. Table-Based Dataloggers 5. Open the newly created file in Edlog. It will be opened using the CR10X- TD datalogger template instead of the CR10X. Make any changes necessary to replace the commented or deleted instructions. 6. Check the Options | DLD File Labels setting to ensure the “Include first ___ Input location labels”...
Page 523: C.3 Table Data Overview
Appendix C. Table-Based Dataloggers Also, check any Instruction 92s for Command Codes that may affect the output flag (see discussion above on output flag instructions). • Instruction 96, Serial Output – Instruction 96 is used to send data in the active Final Storage area to a storage module, computer, printer, or alternate final storage area.
Page 524: Default Tables
Appendix C. Table-Based Dataloggers Example: A CR10X-TD is to be used to monitor three thermocouples. Each hour a temperature for each of the three thermocouples is to be stored. The table has five fields: DATE_TIME, RECORD #, TEMP1, TEMP2, TEMP3. The program is written so that each hour an Instruction 84, Table Data, generates a new “record”...
Page 525: C-1. Example Of Status Table Entries (Cr10T)
Appendix C. Table-Based Dataloggers status, port status, and the reading from each sensor scanned or user created input locations. • Status Table – The Status table contains information on the datalogger. Data is written to the table with each datalogger program execution. Note that the actual fields contained in the table are datalogger-specific.
Page 526 Appendix C. Table-Based Dataloggers TABLE C-1. Example of Status Table Entries (CR10T) Time that the program began running. StartTime Battery Current value of the battery voltage. This measurement is made in the background calibration. Current Panel temperature measurement. PanelTemp LithiumBattery A Boolean variable signaling “True”...
Page 527 Appendix C. Table-Based Dataloggers TABLE C-1. Example of Status Table Entries (CR10T) SkippedSlowScan The number of scans that have been skipped in this slow sequence. If the user has slow scans then this variable becomes an array with a value for the system slow scan and each of the user’s scans.
Page 528 Appendix C. Table-Based Dataloggers TABLE C-1. Example of Status Table Entries (CR10T) CardStatus Contains a string with the most recent card status information. CompileResults Contains any error messages that were generated by compilation or during run time. C-10...
Page 529: Software Organization
D.2 LoggerNet Server Data Cache The LoggerNet server data cache is a set of files kept on the hard disk of the computer where the server is running. These data files are in binary format and can only be used or interpreted by the LoggerNet server.
Page 530: Retrieving Data From The Cache
Appendix D. Software Organization When it is time for a scheduled data collection the server sends a data poll request to the datalogger to get all of the data stored in the selected tables since the last poll. The tables to be collected are specified by the user in the Setup Screen.
Page 531: Directory Organization
Appendix D. Software Organization tables set up based on the new table definitions for that datalogger. LoggerNet will save the existing output data file with a modified name and create a new output data file. D.3 Directory Organization The default installation of the LoggerNet software creates folders and installs software in two directories: the C:\CampbellSci working directory and C:\Program Files\CampbellSci\LoggerNet program directory.
Page 532: C:\Program Files\Campbellsci\Loggernet Directory
Campbell Scientific software product is installed on the system, common applications will be shared among these software applications. For instance, you may have PC400 and LoggerNet installed on the same computer. Both of these applications include the CRBasic Editor. By sharing directories among CSI applications, you have only one “instance”...
Page 533: E.1 Event Logging
Appendix E. Log Files E.1 Event Logging As LoggerNet performs its work, it will create records of various kinds of events. The logs can be very useful for troubleshooting problems and monitoring the operation of the datalogger network. You can monitor these logs using LogTool launched from the Tools category of the LoggerNet toolbar.
Page 534: Enabling Log Files
“SS” is the seconds into the minute, and “mmm” is the milliseconds into the second. Device Name – The name of the device associated with the message. If the message is associated with the LoggerNet server, this will be an empty string.
Page 535: Transaction Log Format
Network branch Device Name A branch of the moved network map was moved from one parent device to another (not supported in LoggerNet 1.1) Network logon Logon Name A client application succeeded successfully attached to the server Network logon Logon Name...
Page 536 (c:\campbellsci wmodem.ini. \loggernet\sys\bin). May indicate a permissions or configuration problem on the computer. Modem custom When the server If the user has not set...
Page 537 Appendix E. Log Files TABLE E-1. Transaction Log Messages User Response to Code Message Text Message Parameters Message Meaning Message Starting BMP A start data advise data advise operation has been transaction initiated. Data advise is not in place until the datalogger responds.
Page 538 Appendix E. Log Files TABLE E-1. Transaction Log Messages User Response to Code Message Text Message Parameters Message Meaning Message Hole collect The datalogger has response returned the response received to the hole collect request. This will contain either the data or state that the hole is lost.
Page 539 RF the datalogger operators base on behalf of the manual or contacting an datalogger). applications engineer at Campbell Scientific. Records Table name; Beginning Datalogger records received record number; Ending have been received record number and stored in the data cache.
Page 540 Appendix E. Log Files TABLE E-1. Transaction Log Messages User Response to Code Message Text Message Parameters Message Meaning Message Terminal Terminal emulation emulation response message has transaction been received from complete the datalogger. Terminal The expected emulation terminal emulation transaction response from the failed...
Page 541 Appendix E. Log Files TABLE E-1. Transaction Log Messages User Response to Code Message Text Message Parameters Message Meaning Message Program file The server is receive start requesting the datalogger program. The actual program segments will appears as BMP1 message type 5. Program file A program segment receive status...
Page 542 If ever seen contact an device or malformed indicating that a application engineer at packet BMP1 message Campbell Scientific. 2. Routing failure didn’t make it to the Code 2 indicates that {unrecognized station data logger. the RF base has lost the...
Page 543 Appendix E. Log Files TABLE E-1. Transaction Log Messages User Response to Code Message Text Message Parameters Message Meaning Message Frequent occurrences indicate that the radio, antenna, connectors and RF link be reviewed. Unexpected As part of data A change in table change in collection the server definitions indicates...
Page 544 Appendix E. Log Files TABLE E-1. Transaction Log Messages User Response to Code Message Text Message Parameters Message Meaning Message Logger locked This message indicates the start of a transaction such as terminal emulation that will tie up the datalogger preventing other operations.
Page 545 Appendix E. Log Files TABLE E-1. Transaction Log Messages User Response to Code Message Text Message Parameters Message Meaning Message Data restore On server startup the This is a computer failed data broker data problem. The files are storage area could not either not present or are be created.
Page 546 Verify that the stored table the LoggerNet system configuration file or configuration files exist new table definitions. and the directory has This could be the not been corrupted.
Page 547 Appendix E. Log Files TABLE E-1. Transaction Log Messages User Response to Code Message Text Message Parameters Message Meaning Message Collect area Collect area name The specified collect During system startup skipped area was skipped this is a normal warning because the message.
Page 548 Appendix E. Log Files TABLE E-1. Transaction Log Messages User Response to Code Message Text Message Parameters Message Meaning Message BMP1 packet The packet message type The specified BMP1 received code: packet was received 0 Packet Delivery Fault over the serial Notification communications link.
Page 549 Appendix E. Log Files TABLE E-1. Transaction Log Messages User Response to Code Message Text Message Parameters Message Meaning Message Table reset The name of the table that The name of a table was reset; The account was changed at the name of the logged in request of a client.
Page 550: Communications Status Log Format
"2009-04-15 16:41:06.367","CR1000","86","Manual poll started","admin" "2009-04-15 16:41:06.367","CR1000","92","Collect area poll started","TestFast" "2009-04-15 16:41:06.382","CR1000","41","Records received","TestFast","21007","21007","polling" "2009-04-15 16:41:06.382","CR1000","20","Hole detected","TestFast","20769","21006" "2009-04-15 16:41:06.429","CR1000","11","Clock check started" "2009-04-15 16:41:06.492","CR1000","41","Records received","TestFast","20769","20799","polling" "2009-04-15 16:41:06.507","CR1000","144","data file opened","TestFast","C:\Campbellsci\LoggerNet\CR1000_TestFast.dat" "2009-04-15 16:41:06.507","CR1000","21","Hole collected","TestFast","20769","20799" "2009-04-15 16:41:06.507","CR1000","41","Records received","TestFast","20800","20864","polling" "2009-04-15 16:41:06.507","CR1000","21","Hole collected","TestFast","20800","20864" "2009-04-15 16:41:06.523","CR1000","13","Clock checked","2009-04-15 16:41:34.55","2009-04-15 16:41:06.516","-28" "2009-04-15 16:41:06.601","CR1000","41","Records received","TestFast","20865","20899","polling"...
Page 551: E-2. Communication Status Log Messages
Appendix E. Log Files Communications Status Log Example "2009-04-15 16:41:05.367","IPPort","S","Device dialed" "2009-04-15 16:41:05.382","PakBusPort_ip","S","sending message","src: 4094","dest: 2","proto: PakCtrl","type: 0x09","tran: 214" "2009-04-15 16:41:05.398","PakBusPort_ip","S","received message","src: 2","dest: 4094","proto: PakCtrl","type: 0x89","tran: 214" "2009-04-15 16:41:05.398","CR1000","S","PakCtrl message received","89" "2009-04-15 16:41:05.413","PakBusPort_ip","S","sending message","src: 4094","dest: 2","proto: BMP5","type: 0x17","tran: 213" "2009-04-15 16:41:05.429","PakBusPort_ip","S","received message","src: 2","dest: 4094","proto: BMP5","type: 0x97","tran: 213" "2009-04-15 16:41:05.429","CR1000","S","BMP5 message received","type: 0x97","check/set clock"...
Page 552 TABLE E-2. Communication Status Log Messages Message Text Message Meaning User Response to Message PakBus framing error LoggerNet received data Some possible causes: the from the link that cannot datalogger program or its settings be verified to be part of a are configured to write data on the PakBus packet.
Page 553: Object State Log Format
Appendix E. Log Files E.1.3.4 Object State Log Format The object state log includes two fields in addition to the timestamp and device name: Object Name – The name of the object from which the message is being generated. Typically this will be the name of an object method. Description –...
Page 554: Cqr Log (Rf Link
RFBase is dialed. (Note that information on an RFBase-TD link is not contained in the CQR log). The CQR log is written to the <working directory>\Logs directory. By default, this is C:\Campbellsci\LoggerNet\Logs. Each time an RF link is shutdown, an entry will be written to the CQR Log.
Page 555: F.1 Calibration Essentials
F.1.2 Basic Calibration Process When calibrating with a Campbell Scientific datalogger, known and measured values are given as inputs. The outputs of the calibration then become the new values for the multiplier and offset variables in the CRBasic program. If...
Page 556: Writing Calibration Programs With The Crbasic Editor
If you wish to make measurements that will be calibrated as discussed above, you should use the FieldCal instruction within the CRBasic program. When the program is running in the datalogger, you can use the LoggerNet Calibration Wizard to perform the actual calibrations (in real-time) on the sensors that were previously designated for calibration.
Page 557: Calibration File Details
The calibration file contains information about the latest calibrations performed during program execution and information that the LoggerNet Calibration Wizard needs to step users through the calibration process. F.3 Four Kinds of Calibration...
Page 558: Offset Calibration
Appendix F. Calibration and Zeroing F.3.2 Offset Calibration Offset Calibration is the act of placing a sensor into a state where the output condition is known to be a certain value and then changing the measurement’s offset variable so that the sensor output reads as exactly that value. It is similar to a zeroing calibration, except that the known value is a non-zero value.
Page 559: Two-Point Multiplier Only Calibration
F.4.1 How to Use the Mode Variable for Calibration Status and Control To perform a manual calibration (without use of the LoggerNet Calibration Wizard) on a FieldCal enabled program running in a datalogger, it is necessary to understand the function of the mode variable that is used as an argument of the FieldCal instruction.
Page 560: Using The Mode Variable For Manual Single-Point Calibration
Appendix F. Calibration and Zeroing The following values of the mode variable give the status of the calibration: No calibration has been performed since program start Calibration in progress OR first stage of two-point calibration in progress Waiting for second stage of two-point calibration to begin Second stage of two-point calibration in progress Calibration complete –1...
Page 561: Using The Mode Variable For Manual Two-Point Calibration
Appendix F. Calibration and Zeroing 5. Note that the datalogger automatically sets the mode variable to 2 during the calibration process. 6. Note that the mode variable is set to 6 automatically by the datalogger when the calibration process completes. F.4.3 Using the Mode Variable for Manual Two-Point Calibration These steps demonstrate how to perform manual two-point calibrations (Multiplier/Offset or Multiplier Only):...
Page 562: Using The Calibration Wizard With Running Programs
F.5 Using the Calibration Wizard with Running Programs The LoggerNet Calibration Wizard provides an easy to use interface which steps the user through the calibration process described above. By using simple screens to gather information, the proper changes to the mode variable and known measurements are performed automatically by the Wizard.
Page 563 Appendix F. Calibration and Zeroing Now select the kind of calibration you wish to perform, which in this case is Multiplier and Offset, and press Next. Now select which sensor it is that you wish to calibrate and press Next. You can select an entire array, or any single element of that array, as well as scalar (single-valued) variables.
Page 564 Appendix F. Calibration and Zeroing The currently measured value for the sensor will be displayed in the next screen. Now place the sensor into the first known condition, and enter that known value into the First calibrated value box. Press Set First Value. Wait for the calibration process to measure the first value.
Page 565 Appendix F. Calibration and Zeroing After the multiplier and offset have been calculated and set, the ending screen of the Wizard appears. You can conclude the calibration, or return to the starting point to perform more calibrations of the same or different sensors. The steps for performing a two-point slope only (multiplier only) NOTE calibration in the Wizard are nearly identical to those shown...
Page 566: Using The Wizard To Perform Zeroing Calibrations
Appendix F. Calibration and Zeroing F.5.3 Using the Wizard to Perform Zeroing Calibrations In the Wizard, select Zero for the type of calibration. Select the sensor you wish to calibrate, press Next. If the variable is configured as an array of sensors, you may select an individual item to calibrate only that element, or you can select the entire array.
Page 567: Using The Wizard To Perform Offset Calibrations
Appendix F. Calibration and Zeroing The Current Value box will be yellow during the calibration process. When it finishes, you will see the new value of the sensor after the application of the zeroing offset. Press Finish to end the calibration. F.5.4 Using the Wizard to Perform Offset Calibrations In the Wizard, select Offset for the type of calibration.
Page 568 Appendix F. Calibration and Zeroing Select the sensor you wish to calibrate, press Next. Now you can view the current reading on the sensor to be calibrated. Set the sensor to the known value (“calibrate to” value). Enter that value into the Enter Calibrated Value box.
Page 569: Strain And Shunt Calibration
Appendix F. Calibration and Zeroing F.6 Strain and Shunt Calibration In addition to the FieldCal instruction that performs calibrations on measurements, there is a specialized instruction for performing calibrations on strain bridge measurements (strain or shunt calibration). This instruction is called FieldCalStrain.
Page 570 Appendix F. Calibration and Zeroing F-16...
Page 571: Importing Files Into Excel
Appendix G. Importing Files into Excel Data files saved by LoggerNet can be imported into a spreadsheet program for analysis or manipulation. Instructions are given below for importing a comma separated file into Microsoft Excel. From the Excel menu, select File | Open. Browse for the *.dat file that you want to import.
Page 572 Appendix G. Importing Files into Excel Step 2 of 3 From the Delimiters group box, select Comma and Space. The Comma option directs Excel to place each data value, which is separated by a comma, into a separate column. The Space option will separate the Date and the Time into two columns.
Page 573 Appendix G. Importing Files into Excel Step 3 of 3 A quick look at the columns of data is provided in the Data Preview group box. To complete the import, select the Finish button. Converting to Excel Format Date and Time Once the data file has been imported into Excel, the time fields are still displayed as comma separated numbers such as Year, Day of Year, and Hours/Minutes in HHMM format.
Page 574: Table-Based Data File Import
Appendix G. Importing Files into Excel ([Year]–1900)*365+1+Int(([Year] –1901)/4)+[Day]+Int([HHMM]/100)/ 24+([HHMM]/100-Int([HHMM]/100))*100/60/24+[Sec]/60/60/24 Section of formula: Results: [Year]–1900)*365+1+Int(([Year]- Delivers the number of days since the beginning of 1901/4 the 20 century through the end of last year taking into account leap years +[Day] Adds the Julian date to the above +Int([HHMM]/100/24 Converts the hour portion of the HHMM time field to a fraction of a day...
Page 575 Appendix G. Importing Files into Excel Step 2 of 3 From the Delimiters group box, select Comma and Space. The Comma option directs Excel to place each data value, which is separated by a comma, into a separate column. The Space option will separate the Date and the Time into two columns.
Page 576 Appendix G. Importing Files into Excel Step 3 of 3 A quick look at the columns of data is provided in the Data Preview group box. Highlight the column with the year/month/day and from the Column Data Format group box, select the Date option. From the drop down list box to the right of this option select the YMD format.
Page 577 Appendix G. Importing Files into Excel The quotation marks can be removed by using Excel’s Search and Replace feature. From the Excel menu, select Edit | Replace. In the Find What field, type in a quotation mark (“). Leave the Replace With field blank, and select the Replace All button.
Page 578 Appendix G. Importing Files into Excel...
Page 580 Campbell Scientific Companies Campbell Scientific, Inc. (CSI) 815 West 1800 North Logan, Utah 84321 UNITED STATES www.campbellsci.com • info@campbellsci.com Campbell Scientific Africa Pty. Ltd. (CSAf) PO Box 2450 Somerset West 7129 SOUTH AFRICA www.csafrica.co.za • cleroux@csafrica.co.za Campbell Scientific Australia Pty. Ltd. (CSA)

This manual is also suitable for:

Loggernet 4.2

Campbell LoggerNet Instruction Manual

Preface - What's New in Loggernet 4

1 System Requirements

2 Installation, Operation and Backup Procedures

3 Introduction

4 Setting up Datalogger Networks

5 Real-Time Tools

6 Network Status and Resolving Communication Problems

7 Creating and Editing Datalogger Programs

Quick Links

Troubleshooting

Need help?

Questions and answers

Related Manuals for Campbell LoggerNet

Summary of Contents for Campbell LoggerNet