INSTRUCTION MANUAL LoggerNet Version 4.2 Revision: 7/14 C o p y r i g h t © 1 9 9 9 - 2 0 1 4 C a m p b e l l S c i e n t i f i c , I n c .
License for Use This software is protected by United States copyright law and international copyright treaty provisions. 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.
Limited Warranty The following warranties are in effect for ninety (90) days from the date of shipment of the original purchase. These warranties are not extended by the installation of upgrades or patches offered free of charge. Campbell Scientific warrants that the installation media on which the software is recorded and the documentation provided with it are free from physical defects in materials and workmanship under normal use.
Table of Contents PDF viewers: These page numbers refer to the printed version of this document. Use the PDF reader bookmarks tab for links to specific sections. Preface — What’s New in LoggerNet 4? ....................... xv 1. System Requirements ............................................. 1-1 1.1 1.2 Hardware and Software .................................................................... 1-1 Configuration of TCP/IP Service ..................................................... 1-1 2.
Table of Contents 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 ...........................
Table of Contents 4.2.5.2.3 Communications Path Considerations ............... 4-54 4.2.5.3 Setting Up Scheduled Data Collection ......................... 4-54 4.2.6 Setting the Clock ..................................................................... 4-56 4.2.7 Sending a Program to the Datalogger from Setup................... 4-57 4.2.8 Setup’s Tools Menu ................................................................ 4-57 4.2.8.1 LoggerNet Server Settings ...........................................
Table of Contents 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 ........................... 5-19 5.1.7.3.2 Graph Options.................................................... 5-20 5.1.7.3.3 Trace Options .........
Table of Contents 6.4.1 Selecting the PakBus Network to View .................................. 6-17 6.4.2 Dynamic and Static Links ....................................................... 6-17 6.4.3 Viewing/Changing Settings in a PakBus Datalogger .............. 6-17 6.4.4 Right-Click Functionality ....................................................... 6-18 6.4.5 Discovering Probable Routes between Devices ...................... 6-18 6.5 Troubleshooter ......................................................
Table of Contents 7.3.3.8.1 Editor Preferences .............................................. 7-33 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.
Table of Contents 7.4.8 Repetitions .............................................................................. 7-68 7.4.9 Input Location Editor .............................................................. 7-69 7.4.10 Input Location Anomalies....................................................... 7-70 7.4.11 Final Storage Labels ............................................................... 7-71 7.4.12 Datalogger Settings Stored in the DLD File ........................... 7-73 7.4.
Table of Contents 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 .......
Table of Contents 8.2.6.3.1 Input/Output File Command Line Switches for Processing Alternate Files ........................ 8-83 8.2.6.4 Processing Multiple Parameter Files with One Command Line ......................................................... 8-86 8.2.7 Log Files ................................................................................. 8-86 8.3 CardConvert ................................................................................... 8-86 8.3.1 Input/Output File Settings ............
Table of Contents 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 ..
Table of Contents 13. Implementing Advanced Communications Links ..................................................................... 13-1 13.1 Phone to RF.................................................................................... 13-1 13.1.1 Setup ....................................................................................... 13-1 13.1.2 Operational Considerations ..................................................... 13-2 13.1.2.1 Scheduled Data Collection ...............................
Table of Contents B.1.5 TOB1........................................................................................ B-4 B.1.6 Array Compatible CSV ............................................................ B-6 B.1.7 CSIXML................................................................................... B-6 B.1.7.1 A Short Introduction to XML ........................................ B-6 B.1.7.2 File Syntax ..................................................................... B-8 B.1.7.
Table of Contents E. Log Files .................................................................. E-1 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.
Table of Contents 8-3. 8-4. 8-5. 8-6. 8-7. 8-8. 8-9. 11-1. 14-1. B-1. B-2. B-3. C-1. E-1. E-2. F-1. Processed Data File Using Option C .............................................. 8-51 Input File Entries to Process the First Data Point for each Test ..... 8-52 Effects of Out of Range Values for Given Output Options ............ 8-54 Split Operators and Math Functions ............................................... 8-56 Time Series Functions ................................................................
Preface — What’s New in LoggerNet 4? Product History LoggerNet 4 continues the original design of client-server functionality that first appeared when Version 1.0 was released for Windows to replace Real Time Monitoring Software (RTMS) that ran on OS/2 operating systems. Versions in the 1.x series supported only table-based dataloggers and provided large network users with sophisticated capabilities to develop clients to the server to move data without having to store it in interim files. Version 2.
Preface — What’s New in LoggerNet 4? PakBus network, proposes and verifies valid connections between devices, and allows integration of the model directly into LoggerNet 4.0. 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.
Preface — What’s New in LoggerNet 4? can choose to view a subnet rather that the entire network in the Setup Screen, Connect Screen, and Status Monitor. You can now set up defaults for the Setup Screen’s Schedule, Data Files, Clock, and File Retrieval tabs that will be used when new stations are added to the network. There is also the ability to copy these defaults to existing stations. The ability to use 24:00 (rather than the default of 00:00) for the timestamp at midnight has been added.
Preface — What’s New in LoggerNet 4? A Constant Customization feature has been added to the CRBasic Editor. This allows you to define values for one or more constants in a program prior to performing a conditional compile. The constants can be set up with an edit box, a spin box field for selecting/entering a value, or with a list box. A step increase/decrease can be defined for the spin box, as well as maximum and minimum values. The CRBasic Editor now allows you to Save and Open Display Settings.
Preface — What’s New in LoggerNet 4? Setup Screen 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. Standard View Changes A new menu item has been added to enable a Stations Only view. When this is enabled, only stations will be shown in the Network Map and they will be listed in alphabetical order.
Preface — What’s New in LoggerNet 4? Connect Screen The Connect Screen has been reorganized with most of the buttons now residing on a toolbar at the top of the window. A Table Monitor has been added in the middle of the window that can be used to monitor the values for one entire table. A Notes field has been added that displays the information from the Setup Screen’s Notes tab of the selected datalogger.
Preface — What’s New in LoggerNet 4? Short Cut Support has been added to Short Cut for the CR9000X datalogger, the ET107 Evapotranspiration Monitoring Station, and the AVW200 Two-Channel Vibrating Wire Spectrum Analyzer.
Preface — What’s New in LoggerNet 4? Variable Name Matching – When enabled variable names will be capitalized based on how they are declared in the program, regardless of how the user may have typed them. Create .TDF File at Compile – The user can then associate a .TDF file with a datalogger. This can be useful if communication is taking place over a slow or unreliable communication link where the attempt to receive table definitions back from the datalogger fails.
Preface — What’s New in LoggerNet 4? In RTMC Run-Time, all alarms on a screen can be acknowledged by rightclicking on the screen and then choosing “Acknowledge All On-Screen Alarms”. Miscellaneous other changes have been made to the settings for specific components. 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.
Preface — What’s New in LoggerNet 4? Splitr is started when one is already running, another log file, splitrunning.log, will be written. This file simply identifies the time that the second instance of Splitr was started and that Splitr was already running. CardConvert A new File Format option, CSIXML, has been added to the Destination File Options. When this option is selected, data is stored in XML format with Campbell Scientific defined elements and attributes.
Preface — What’s New in LoggerNet 4? Status Monitor, Task Master, Short Cut, CRBasic Editor, View Pro, Card 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.
Preface — What’s New in LoggerNet 4? xxvi
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. NOTE PROTECT YOUR INVESTMENT. Make a back-up copy of your LoggerNet software and record your CD key.
Section 1.
Section 2. Installation, Operation and Backup Procedures 2.1 CD-ROM Installation Place the installation disk in your computer’s CD-ROM drive. If autorun is enabled for the drive, the LoggerNet installation will start automatically. If the installation does not start automatically, select Start | Run from the Windows’ Start menu. Type D:\Setup.exe (assuming D is your CD-ROM drive letter) in the Open field. Alternately, use the Browse button to access the CD-ROM drive and select the Setup.
Section 2. Installation, Operation and Backup Procedures Note that the trial version will install some applications in the C:\Program Files\Campbellsci\Demo directory. When the purchased version of LoggerNet is installed, these applications will each be installed in their own directory under C:\Program Files\Campbellsci. The versions in the Demo directory will no longer be used.
Section 2. Installation, Operation and Backup Procedures 2.3.1 LoggerNet Directory Structure and File Descriptions 2.3.1.1 Program Directory As described in the installation procedures, all of the files for program execution are stored in the 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.
Section 2. Installation, Operation and Backup Procedures By default, the files that you create in each of the applications will be stored in their respective folders in the working directory. You can override that default and store the files in a different location. Each application “remembers” the last directory in which a file was saved and will default to that directory until a different directory is selected.
Section 2. Installation, Operation and Backup Procedures files and help files for all dataloggers supported by the CRBasic Editor. The definition files are the files which provide the unique instructions and parameters for each datalogger. The RTMCMediaLib directory contains all of the media files that can be used by RTMC to provide graphics and sound for your RTMC projects. Any custom graphics or sounds that you create and wish to use in your project should be stored in one of these directories.
Section 2. Installation, Operation and Backup Procedures The backup file is named LoggerNet.bkp and is stored in the C:\CampbellSci\LoggerNet directory (if you installed LoggerNet using the default directory structure). You can, however, provide a different file name if desired. 2.3.2.2 Performing Scheduled Backups LoggerNet also provides a simple way of backing up your network on a specified interval. From the Setup Screen’s menu, choose Network | Scheduled Backup.
Section 2. Installation, Operation and Backup Procedures Automatic Backup Configured in Task Master 2.3.2.4 Restoring the Network from a Backup File To restore a network from a backup file, choose Network | Restore Network. Select the *.bkp file that contains the network configuration you want to restore. Note that this process DOES NOT append to the existing network — the existing network will be overwritten when the restore is performed. 2.3.
Section 2. Installation, Operation and Backup Procedures If computer system power is lost while the LoggerNet server is writing data to the active files, the files can become corrupted, making the files inaccessible to the server. While loss of power won’t always cause a file problem, having files backed up as described above will allow you to recover if a problem occurs.
Section 2. Installation, Operation and Backup Procedures 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. If LoggerNet is installed as a service, the service must be running for LoggerNet to run (either automatically or manually).
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. • Right-click on the directory in Windows Explorer and choose Properties. • Go to the Security tab of the Properties dialog box and select Add. This will open the Select Users, Computers, or Groups dialog box.
Section 2. Installation, Operation and Backup Procedures (which will already be “behind” the PC’s local firewall), the server is capable of distributing the same information to similar clients connected via TCP/IP from anywhere in the world, revealing the true power of the client-server design.
Section 2.
Section 3. 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.
Section 3. Introduction 3.2 Overview of Major LoggerNet Functions and Associated Software Applications 3.2.1 The Heart of it All – LoggerNet Toolbar The LoggerNet Toolbar has several functions. The most important is starting the server that handles all communications with the dataloggers in the network. As long as the Toolbar is running, either visible or minimized, the server is working and able to communicate with the dataloggers.
Section 3. Introduction By default, the LoggerNet menus are not shown on the toolbar. Press the arrow button in the upper right corner to view the LoggerNet menus as shown below. The arrow button will change direction and can then be used to hide the menus. 3.2.1.2 Favorites Category The Favorites category can be configured to display as many or as few applications as desired by selecting the Tools | Options menu item and then using the Favorites tab.
Section 3. Introduction an application up in the Favorites column, select the application and press the up arrow until the application is in the desired location. Use the down arrow key in a similar manner to move the application down in the Favorites column. 3.2.1.3 Toolbar Menus The following options are available from LoggerNet’s menu: File Menu Exit – Closes the LoggerNet application. View Menu Full View – This option is only available when in Favorites View and brings up the full view of the Toolbar.
Section 3. Introduction Currently, there are three command line arguments: /WorkDir Sets the working directory to something other than the default. Usage: “C:\Program Files\CampbellSci\LoggerNet\ToolBar.exe” /WorkDir=C:\CampbellSci\test where “C:\Program Files\CampbellSci\LoggerNet\ToolBar.exe” is the directory and filename for the LoggerNet Toolbar (which essentially is the LoggerNet server) and C:\CampbellSci\test is the working directory to be used. /M Launches LoggerNet in a minimized state.
Section 3. Introduction 3.2.2 LoggerNet Admin/LoggerNet Remote LoggerNet Admin and LoggerNet Remote add functionality to aid in the management of networks. 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.
Section 3. Introduction automatically specifies many individual device settings such as PakBus address, neighbor lists, verify intervals, network parameters, etc. The Network Planner also provides an interface to allow the user to actually configure the dataloggers and peripheral devices in his network as well as the LoggerNet server. LoggerNet also ships with a command line scripting tool, CoraScript, which can be used to configure the datalogger network from a command prompt.
Section 3. Introduction Troubleshooter is used to identify possible problems disrupting communications or data collection. You can narrow the display to show only the dataloggers in the network, or expand it to view the entire network. Problems are highlighted in different colors to indicate levels of severity.
Section 3. Introduction For straightforward “measurement/control/data storage” datalogger programs, the Short Cut program generator is an excellent choice for datalogger program creation. Short Cut prompts you for the type of datalogger, scan interval, sensors to be measured (including those on multiplexers and other peripherals), and desired final storage output. It then creates the program for you, along with a wiring diagram showing how each of the sensors should be connected to the datalogger.
Section 3. Introduction histogram, or FFT as appropriate for the data type. You can also print graphs or save them to disk in a variety of formats. Split is used to post process and generate reports from collected data files from either mixed-array or table-based dataloggers.
Section 3. Introduction data collection must occur in LoggerNet (either by a scheduled or manual data collection), for the data to be available to the Data Filer. 3.2.11.2 Data Display Clients RTMC Run-Time is available separately from LoggerNet. It allows you to run forms created in RTMC so that data can be displayed on a remote computer. The CSI Web Server is used to display RTMC projects using a web browser.
Section 3.
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. Either method will result in a network map with all of the devices and communications links to reach the datalogger stations.
Section 4. Setting up Datalogger Networks Subsequent pages are similar. Previous and Next buttons are provided to move through each step of the wizard. Progress is shown by the blue arrow next to each step displayed at the left. Field descriptions and helpful tips are displayed on the wizard page. If additional help is needed, the on-line help can be opened by pressing F1 or the Help button on the bottom right of each page.
Section 4. Setting up Datalogger Networks Wizard to send a program to a table-based datalogger, the software will already be aware of the data tables that exist in the datalogger. If the program was already loaded, or for some reason no tables are displayed, press the Get Tables 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.
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. Let’s assume that your server computer is connected to the datalogger via a telephone modem.
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. An alternative to the Add Device window is to press the right mouse button while your cursor is on a device within the main device map window.
Section 4. Setting up Datalogger Networks To delete a device from the network map select the device and click the Delete button. This will delete the device and any devices that were connected below it. 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.
Section 4. Setting up Datalogger Networks 4.2.3 Renaming Network Devices The names of all of the devices can be changed as desired. Rename a device by selecting the device and either clicking again with the left mouse button on the selected device or clicking the Rename button. The name of the selected device will change to a text edit box and the new device name can be entered. Valid names consist of letters, numbers and the underscore (_).
Section 4. Setting up Datalogger Networks Extra Response Time – LoggerNet is preconfigured to allow time for responses based on type of device and baud rates. In this field, specify only the additional time that LoggerNet should delay before terminating the communications link if there is no response from the serial port. Additional time may be needed in instances where the communications link is noisy or network traffic is heavy. If extra response time is needed, it is typically set to 1 or 2 seconds.
Section 4. Setting up Datalogger Networks Advanced Call-back Enabled – Enabling call-back tells LoggerNet to watch for a callback from the datalogger on this port. Dataloggers depicted in the Setup Screen must be configured for call-back as well. For mixed array dataloggers, set the Call-Back ID to some value other than 0 to accomplish this. For CRBasic dataloggers, enable the Call-Back Enabled check box for those dataloggers which should be enabled for callback.
Section 4. Setting up Datalogger Networks Standard Communications Enabled – Before communication can take place, all devices in the chain must be enabled. When this box is selected, the Internet protocol serial port is enabled for communication. TAPI Line – Select the modem you want to use for communication. The modems listed are defined by Windows as part of the computer’s Modem Setup. All of the parameters for the modem, including the baud rate have to be set using the Windows Modem Setup dialog.
Section 4. Setting up Datalogger Networks 4.2.4.4 Datalogger Dataloggers have several different tabs. Similar to the serial port, a hardware tab is completed to specify communications settings. There are also tabs to define the data to be collected, how often data should be collected, whether to automatically update the datalogger’s clock, and a tab to send a program. Note that not all dataloggers will have all the settings described below. 4.2.4.4.
Section 4. Setting up Datalogger Networks 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. When connecting to a LoggerNet 3.4.1 server, you will be disconnected with no advanced warning when Max Time On-Line is reached. A message will be displayed indicating that Max Time On-Line has been reached.
Section 4. Setting up Datalogger Networks BMP1 Station ID – The address that will be used for the device in the BMP1 network. 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.
Section 4. Setting up Datalogger Networks Apply to Other Stations – This button allows the schedule setup for this datalogger to be copied to other stations in the network. Clicking the button brings up a window that lists all of the dataloggers in the network. You can select one or more dataloggers and then press OK to use the entered schedule. To select more than one datalogger, hold down the Ctrl key while clicking the dataloggers to select.
Section 4. Setting up Datalogger Networks Stay On Collect Schedule – By default, when LoggerNet has missed a scheduled collection because of some condition (i.e. LoggerNet was closed, scheduled collection was disabled, the schedule was paused from the Status Monitor, etc.), once the condition that prevented collection is no longer true, if an entire collection interval has elapsed since the last collection attempt, LoggerNet will immediately try to perform a collection.
Section 4. Setting up Datalogger Networks • Automatically Reset Changed Tables – LoggerNet will reset (delete and recreate) any tables that have changed. Unchanged tables will not be reset. Scheduled data collection will continue without action from the user. • Stop Collection Until Manually Updated – Scheduled data collection will be halted until the user manually updates the table definitions (Setup Screen, Data Files tab, Get Table Definitions button).
Section 4. Setting up Datalogger Networks 4.2.4.4.3 Final Storage Area 1 and 2 Tab (Edlog Dataloggers with Mixed-array Operating System) Mixed-array dataloggers include the 21X, CR500, CR510, CR10, CR10X, 21X, CR23X, and CR7. When the datalogger program stores data in a mixedarray datalogger, the data arrays are stored in a final storage area. Some dataloggers, such as the CR10X, have two final storage areas while others, such as the 21X, have only one.
Section 4. Setting up Datalogger Networks 01+0109. 02+2002. 03+0038. 04+1639. 05+15.00 06+13.20 07+24.79 08+073.9 09+269.0 10–1.000 01+0109. 02+2002. 03+0038. 04+1639. 05+25.00 06+13.20 07+24.79 08+073.9 09+279.0 10–.988 01+0109. 02+2002. 03+0038. 04+1639. 05+35.00 06+13.20 07+24.79 08+074.0 09+289.0 10–.946 01+0109. 02+2002. 03+0038. 04+1639. 05+45.00 06+13.20 07+24.79 08+074.0 09+299.0 10–.875 01+0109. 02+2002. 03+0038. 04+1639. 05+55.00 06+13.20 07+24.79 08+074.0 09+309.0 10–.777 01+0112. 02+2002.
Section 4. Setting up Datalogger Networks The individual tables can be highlighted by clicking the table name. The settings on the right side of the window apply to the highlighted table. The name of the highlighted table appears at the top of the settings. Double clicking a table name will toggle collection of that table on or off. Included for Scheduled Collection – If this box is checked the specified table is included in data collection.
Section 4. Setting up Datalogger Networks specify if a timestamp and record number should be included, and whether midnight is specified as 2400 or 0000. Binary table data (TOB1) – The data is stored in Table Oriented Binary format type 1. When this option is selected, the Browse button to the right of the Output Format field becomes available. It launches a dialog box from which to specify if a timestamp and record number should be included.
Section 4. Setting up Datalogger Networks Use Reported Station Name – Enabling this check box will cause the station name from the Status Table to be used in the header of the data files. If this check box is not enabled, the network map station name will be used. NOTE This check box affects only the header of the data files. It has no effect on the filenames. 4.2.4.4.
Section 4. Setting up Datalogger Networks Set Station Clock – Press this button to manually set the clock to that of the LoggerNet server. NOTE The Allowed Clock Deviation setting will prevent a manual clock set from being carried out if the difference between the datalogger’s and server’s clocks is less than the specified deviation. 4.2.4.4.6 Program Tab The program tab displays the name of the program currently running in the datalogger, if it is known by the LoggerNet server.
Section 4. Setting up Datalogger Networks Delete Files After Retrieval – When this box is selected, the files will be deleted from the datalogger after they are retrieved. Add New – When this button is pressed, a new pattern is added to the list of files to be retrieved. The user must then designate the File Pattern, Output Directory, Max Files, Force Retrieval, and Record If Skipped fields for this pattern.
Section 4. Setting up Datalogger Networks configurations. When the Edit Modem Database button is selected, the reset and initialization strings for the selected modem are displayed. You can change these settings or add a custom modem to the list. If you change the settings for one of the standard modems you will have to save it to a new name to use it. The only modems that can be deleted from the list are modems that have been added by the user.
Section 4. Setting up Datalogger Networks the delay specified. The amount of time to delay is in milliseconds so a 5second delay would be entered as 5000 milliseconds. NOTES If the answering phone is a voice modem, a code must be entered at the end of the dial string to put the modem into data mode. Use *9 for a VS1 or 9 for a COM300/310/320. The code should be sent after the modem has answered and the communication link has been negotiated.
Section 4. Setting up Datalogger Networks 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. When connecting to a LoggerNet 3.4.1 server, you will be disconnected with no advanced warning when Max Time On-Line is reached. A message will be displayed indicating that Max Time On-Line has been reached.
Section 4. Setting up Datalogger Networks Advanced Use F Command – The “F” command forces the baud rate to 9600. In the modem enabled (ME) state, the serial I/O port of the end-of-link modem will communicate with the datalogger at 9600 baud with the “F” command. In the synchronous device communication (SDC) state, the baud rate from the computer to the start-of-link modem will be 9600. Use U Command – The “U” command will force RF communication between radios to 2400 baud rather than 3000 baud.
Section 4.
Section 4. Setting up Datalogger Networks When the device is connected in the Connect Screen and the time limit approaches, a dialog box is displayed warning the user that Max Time On-Line is about to be exceeded. The dialog box has Reset Max Time and Don’t Reset buttons. If the Reset Max Time button is pressed, the Max Time On-Line counter will be reset. If the Don’t Reset button is pressed or if no button is pressed, the connection will be terminated when Max Time On-Line is reached.
Section 4. Setting up Datalogger Networks 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. BMP1 Station ID – The address that will be used for the device in the BMP1 network. When adding a new device to the network, this field will not show up until after the Apply button has been pressed.
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. The RFBase’s clock can be set to that of the PC’s by pressing the Set Station Clock button. 4.2.4.
Section 4. Setting up Datalogger Networks 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. The format for this field is 00 h(ours) 00 m(inutes) 00 s(econds). Advanced Extra Response Time – The amount of additional time, in seconds, that LoggerNet should wait for this device to respond. Note that Extra Response Time is cumulative for all devices in the network.
Section 4. Setting up Datalogger Networks When the device is contacted on a schedule, communication with the device will be terminated once this time limit is exceeded. A value of 0 in this field indicates that there is no time limit on maintaining a connection to the device. When the device is connected in the Connect Screen and the time limit approaches, a dialog box is displayed warning the user that Max Time On-Line is about to be exceeded. The dialog box has Reset Max Time and Don’t Reset buttons.
Section 4. Setting up Datalogger Networks 4.2.4.13 MD9 Remote The MD9 remote is the MD9 modem device that is connected to the datalogger at the field site. It has Hardware and Notes tabs only. NOTE A PakBus datalogger is added to an MD9 network by attaching a PakBusPortHD to an MD9 Remote. The PakBus datalogger is then attached to the PakBusPortHD. Note that this communication link may be slow. It may take several minutes for the link to be dropped, once communication is complete.
Section 4. Setting up Datalogger Networks 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. When connecting to a LoggerNet 3.4.1 server, you will be disconnected with no advanced warning when Max Time On-Line is reached. A message will be displayed indicating that Max Time On-Line has been reached.
Section 4. Setting up Datalogger Networks When the device is contacted on a schedule, communication with the device will be terminated once this time limit is exceeded. A value of 0 in this field indicates that there is no time limit on maintaining a connection to the device. When the device is connected in the Connect Screen and the time limit approaches, a dialog box is displayed warning the user that Max Time On-Line is about to be exceeded. The dialog box has Reset Max Time and Don’t Reset buttons.
Section 4. Setting up Datalogger Networks Maximum Time On-Line – This field is used to define a time limit for maintaining a connection to the device. (This may be useful in avoiding costly communication costs, in the event that a connection to a station is inadvertently maintained for a long period of time.) Maximum Time On-Line applies to both scheduled connections and manual connections.
Section 4. Setting up Datalogger Networks 4.2.4.16 Generic Modem The Generic Modem is used to set up any device in the communications network whose behavior is controlled by scripts. No default strings (such as reset and initialization strings) are sent; therefore, all commands must be entered by the user. Hardware Tab, Standard Communications Enabled – Before communications can take place, all devices in the chain must have the Communications Enabled box checked.
Section 4. Setting up Datalogger Networks Hardware Tab, Advanced Extra Response Time – In this field, specify the additional time that LoggerNet should delay before terminating the communications link if there is no response from the generic modem. Additional time may be needed in instances where the communications link is noisy or network traffic is heavy. Maximum Packet Size – Data is transferred in “chunks” called packets. For most devices the default value is 2048 byes.
Section 4. Setting up Datalogger Networks PakBus Graph can be used to visually monitor and retrieve settings from devices in a PakBus network. Refer to Campbell Scientific’s PakBus Networking Guide for more information about setting up PakBus networks. Hardware Tab, Standard Communications Enabled – Before communication can take place, all devices in the chain must be enabled. When this box is selected, the PakBus port is enabled for communication.
Section 4. Setting up Datalogger Networks 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. When connecting to a LoggerNet 3.4.1 server, you will be disconnected with no advanced warning when Max Time On-Line is reached. A message will be displayed indicating that Max Time On-Line has been reached.
Section 4. Setting up Datalogger Networks TCP Password – This is a password that is used to control IP access to a datalogger. Passwords are assigned through the Device Configuration Utility or through the datalogger’s settings which can be edited through PakBus Graph or the Device Configuration Utility.
Section 4. Setting up Datalogger Networks 4.2.4.19 PakBusPort HD This virtual device is used to facilitate communication with a PakBus datalogger in an RF95 or RF232 radio network or in an MD9 network. Standard Communications Enabled – This check box is used to turn communication on or off. This check box must be enabled for any communication to take place over the PakBus node. Maximum Time On-Line – This field is used to define a time limit for maintaining a connection to the device.
Section 4. Setting up Datalogger Networks Advanced Extra Response Time – The amount of additional time, in seconds, that LoggerNet should wait for this device to respond. Note that Extra Response Time is cumulative for all devices in the network. PakBus Address – This field is for display only. It shows the PakBus address that has been set up for the PakBus Port. This address can be changed by going to the Setup Screen’s Options | LoggerNet PakBus Settings menu item. 4.2.4.
Section 4. Setting up Datalogger Networks 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. When connecting to a LoggerNet 3.4.1 server, you will be disconnected with no advanced warning when Max Time On-Line is reached. A message will be displayed indicating that Max Time On-Line has been reached.
Section 4. Setting up Datalogger Networks Routing Tab Outbound PakBus Connections This box is used to specify IP addresses and port numbers for outbound connections to any of the dataloggers attached to the PakBus TcpServer. To add a connection, enter the PakBus Address and IP Address in the fields below the Outbound PakBus Connections box. Then press the Add Connection button.
Section 4. Setting up Datalogger Networks When configuring a SerialPortPool, use the Serial Ports tab to add all the serial ports that are connected to base modems that can be used to call this site. The dialing string entered in the phone remote must work in conjunction with any of the modems connected to the serial ports added to the pool for this datalogger. For more information on modem pooling, refer to LoggerNet’s online help.
Section 4. Setting up Datalogger Networks Maximum Time On-Line – Enter a time limit for maintaining a connection to the device. (This may be useful in avoiding costly communication costs, in the event that a connection to a station is inadvertently maintained for a long period of time.) Maximum Time On-Line applies to both scheduled connections and manual connections.
Section 4. Setting up Datalogger Networks All of the COM ports which are set up and recognized by Windows will be shown in the Available Ports list. Select a COM port from the list and press Add Port to add the port to the modem pool. To delete a COM port from the pool, select it in the Serial Port Pool box and press Remove Port.
Section 4. Setting up Datalogger Networks When configuring a TerminalServerPool, use the Terminal Servers tab to add all the terminal servers that are connected to base modems that can be used to call this site. The dialing string entered in the phone remote must work in conjunction with any of the modems connected to the terminal servers added to the pool for this datalogger. For more information on modem pooling, refer to LoggerNet’s online help.
Section 4. Setting up Datalogger Networks period of time.) Maximum Time On-Line applies to both scheduled connections and manual connections. 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.
Section 4. Setting up Datalogger Networks To add a terminal server to the pool, type in the address of the terminal server port in the Terminal Server field and press the Add button. The address consists of an IP or DNS address followed by a colon followed by the TCP port number (e.g., 192.168.7.14:10001 or [2620:24:8080:8600:85a1:fcf2:2172:11bf]:10001). After the terminal server has been added to the pool, there will be check box next to it in the Terminal Server Pool box.
Section 4. Setting up Datalogger Networks Table Data Dataloggers When connected, data from table data dataloggers is updated based on the Update Interval. (This is referred to as real time monitoring.) Note that data can be updated no faster than the data values are being generated by the datalogger. When not connected, data from table data dataloggers is updated only as often as data collection is performed. (This is referred to as passive monitoring.
Section 4. Setting up Datalogger Networks If data collection is enabled for input location data (Inlocs) on the CR10X-TD/PB family dataloggers or Public tables on CR1000, CR3000, CR800, CR5000 or CR9000 dataloggers, the current values will be collected every time a scheduled collection occurs, whether or not the values have been updated.
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 tablebased dataloggers, each table must be configured separately (i.e., selected for collection, file name provided, file format specified, etc.). NOTE For table-based dataloggers, if no table names appear on the Data Files Tab, click the Get Table Definitions button. The data collection schedule should be set up next.
Section 4. Setting up Datalogger Networks 4.2.6 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. Because it is important to maintain accurate time stamping of your data, there are a few things to take into consideration when setting up a clock check schedule.
Section 4. Setting up Datalogger Networks 4.2.7 Sending a Program to the Datalogger from Setup In most instances, you will send a new program to the datalogger from the Connect Screen. Once the program is sent from Connect, you can launch a Numeric Display from that window to view measurements and ensure the program is working correctly. However, for convenience when configuring a datalogger for communication and data collection, a program can also be sent from the Setup Screen.
Section 4. Setting up Datalogger Networks Data File Settings This box is used to set a maximum size, in bytes, for data files. When the maximum file size is reached, the current file will be archived (with an incrementing number and a .backup extension) and a new file will be created. Entering a value of 0 or less indicates that no maximum data file size should be enforced. 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.
Section 4. Setting up Datalogger Networks 17338. However, if a firewall is in use, the port value may be changed when passed through the firewall. The IP Manager Key is the 128-bit encryption key used for decoding transmissions from all AirLink modems used in the datalogger network. This setting must match the setting in the modems for the transmission to be successfully interpreted. LoggerNet’s default value in the IP Manager Key field is the default for the AirLink modems.
Section 4. Setting up Datalogger Networks This dialog box allows you to copy setting(s) from the device currently selected in the network map to other devices in the network. The list on the left side shows the settings that can be copied. The list on the right side shows the available devices in the datalogger network. Select the setting(s) you wish to copy and the device(s) you wish to copy the settings to.
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. It will be moved to the Assigned Dataloggers Column.
Section 4. Setting up Datalogger Networks 4.3 Network Planner The Network Planner is a graphical application that assists you in designing PakBus datalogger networks. You interact with a drawing canvas on which you place stations and add peripheral devices to those stations. You then create links between stations and specify the nature of those links. Finally, you specify the activities that will take place between various devices within the network.
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. Alternatively, the background image can be pasted from the clipboard using the Options | Paste the Background Image menu item.
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. Center Button–Pressing the center button will reposition the drawing canvas at the graph origin.
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. 4.3.2.3 Changing the Canvas Scale The scale of the drawing canvas can be changed using the toolbar controls highlighted in the above figure.
Section 4. Setting up Datalogger Networks 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. Note that the Network Planner simplifies the task of selecting a link by hiding, by default, all of the links except those that have the highest priority.
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 “+” icon will appear in the center of that station icon and, as you move the mouse, a green rubber-band line will follow the mouse cursor.
Section 4. Setting up Datalogger Networks In this instance, for radio based links, the icon is a small yagi antenna. If you hover the mouse cursor over the top of this connection point icon with the station selected, a tool-tip type window will appear that gives specific details about that link. 4.3.6 Adding Activities The Network Planner provides a means for you to specify that certain kinds of activities take place between station devices on a regular interval.
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.
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. Target Device – Specifies the device that will be targeted by the activity.
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: • An Edit Station Properties link that, if clicked, will present you with a dialog that contains property sheets for all of the devices and/or links in the station.
Section 4. Setting up Datalogger Networks • An optional link to perform the Configure Devices list item for the device. • A description of any activities for which this device is a source. This includes a link to delete those activities. • PakBus information for the device including its PakBus address(es), the device’s role (router or leaf node), and the routes used to reach other PakBus devices. • List of links for which the device is an end-point.
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.
Section 4. Setting up Datalogger Networks Connect – When clicked, this button will disable the dialog controls and initiate communication with the device in order to transmit the settings. In order to accomplish this, the Network Planner uses its own private LoggerNet server. Save – This button allows you to save the generated settings for the device into an XML file that can be read by the Device Configuration Utility as well as the PakBus Graph LoggerNet client.
Section 4. Setting up Datalogger Networks This dialog allows you to specify a user name and password for an administrative account on the local server and, if you click on the OK button, will perform the following actions: • The dialog will connect to the local server and scan its network map for any serial port devices that use the same serial port name as that specified in the device configuration dialog.
Section 4. Setting up Datalogger Networks This dialog has the following controls: 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. This feature allows you to use several different Network Planner models with the same LoggerNet server by keeping the generated devices separate.
Section 4. Setting up Datalogger Networks Help Window – The HTML window in the upper right corner of the dialog shows context sensitive help about the control that has the current keyboard focus. Generated Devices and Settings – The HTML window in the lower right corner of the dialog shows a summary of the devices that will be created in LoggerNet’s network map as well as the settings associated with those devices.
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. Blue – The change involves making changes to settings of existing devices.
Section 4. Setting up Datalogger Networks 4.3.10 Arranging Screen Components The Network Planner user interface has been designed so that you can exercise a great deal of control over the placement and sizes of the various user interface components. User interface components including the toolbar, the Device Palette, the Station Summary, and the Configure Devices panel can be detached from the application frame, re-anchored to the frame in a different location, resized, or hidden altogether.
Section 4.
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.
Section 5. Real-Time Tools As noted above, you can work with a datalogger station while actively connected to it or when you are in a disconnected state. Even when not actively connected, you can choose to collect data, check or set the clock, etc. When a button is pushed, LoggerNet will attempt to contact the datalogger, performed the desired action, and then terminate communication.
Section 5. Real-Time Tools Once the datalogger connection is established, an elapsed time for the connection will be shown on the bottom left of the window. This counter will continue as long as the datalogger connection is maintained. The user should be aware of the how long the Connect Screen is connected to the datalogger. A manually initiated connection to a datalogger takes priority over other communication in the network map.
Section 5. Real-Time Tools Once you have started data collection with Collect Now, you can stop it by clicking the Cancel button on the animated screen. This might be necessary if you started a data collection that is bringing in more data than you really wanted, especially over a slow communications link. 5.1.2.2 Custom Collection 5.1.2.2.1 Mixed-array Dataloggers Clicking the Custom button for a mixed-array datalogger brings up the dialog box shown below.
Section 5. Real-Time Tools − 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.
Section 5. Real-Time Tools NOTE While retrieving data from the datalogger using Custom 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 5-6 − Newest Number of Records will retrieve the number of records specified in the Starting Record Information area going back from the last record collected.
Section 5. Real-Time Tools − 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. − All the Data will get from the datalogger all the data available from all of the selected tables.
Section 5. Real-Time Tools When the Don’t Quote Strings check box is selected, strings in the data will not be surrounded by quotation marks. If the check box is not selected, strings will be surrounded by quotation marks. (Note this option is only available for the ASCII Table Data, No Header Output Format.) Enabling the Use Reported Station Name check box will cause the station name from the Status Table to be used in the header of the data files.
Section 5. Real-Time Tools Different datalogger models have a different number of ports and flags. The Ports and Flags dialog box will display only those ports and flags available for the datalogger type. Behaviors for each datalogger type are shown below. NOTE • Mixed array dataloggers have a fixed number of ports and user flags that are available. The ports and flags dialog box will display only the ports and flags supported by the datalogger; no additional values can be added.
Section 5. Real-Time Tools NOTE A control port must first be configured for output in the datalogger program before it can be toggled on or off. Consequently, if you select a port and it doesn’t appear to change, your program may not have the port configured for output (refer to your datalogger operator’s manual). The CR500 and CR510 have two control ports, but only one of the ports, control port 1, can be configured for output. Therefore, control port 2 cannot be toggled on or off.
Section 5. Real-Time Tools 5.1.5 Program Management The Program section on the Connect Screen is used to send programs to or retrieve programs from dataloggers in the network. Edlog is used to create programs for the CR7, 21X, and the CR10(X), CR510, and CR23X Series dataloggers (CRXX, CRXX-TD, and CRXX-PB). The CRBasic Editor is used to create programs for the CR5000, CR9000, CR1000, CR3000, CR800 Series, and CR200 Series dataloggers. Short Cut can be used to create programs for any datalogger type.
Section 5. Real-Time Tools 5.1.5.2 CR200 Series Programs Programs for the CR200 Series dataloggers must be precompiled before being sent to the datalogger. The compiled file is a binary image file with a *.bin extension. Unlike the other dataloggers, CR200 Series dataloggers do not have an on-board compiler. Consequently, the *.
Section 5. Real-Time Tools after associating the file, you may need to recompile the program file with a version of Edlog that stores this information in the *.dld file. NOTE If you are using Edlog Version 2.0 or greater and labels are still not available for use, check Edlog’s Options | DLD File Labels menu item and ensure that labels are being stored in the file when the program is compiled.
Section 5. Real-Time Tools NOTE If clock updates and display updates are paused while connected to a datalogger, the connection may time out and terminate the connection. There are three Numeric Display screens and three Graphical Display screens. Each screen is launched as a separate window that can be moved or resized as needed. The display screens are not minimized if the Connect Screen is minimized, but they can be minimized independently. 5.1.7.
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. 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.
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. An entire table or array can be selected by clicking the table name.
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. 5.1.7.2.2 Display Options The appearance of a Numeric Display can be customized by selecting the Options button.
Section 5. Real-Time Tools Alarms Tab Enable Alarms – Alarms can be set to turn the background of a field a different color depending on the value of a data point. Select the Enable Alarms check box to turn on the alarm feature. The alarm levels can be set for one or more selected cells by entering a value in the High Alarm Trigger Value field and the Low Alarm Trigger Value field.
Section 5. Real-Time Tools NOTE A mixed-array datalogger’s final storage data must be collected by LoggerNet before it can be displayed. NOTE When a value declared as a Long is being graphed, –2147483648 (the most negative long value) is used to indicate NAN (Not A Number). 5.1.7.3.1 Displaying Values on a Graph A graph is initially blank when opened; the fields to be plotted must be selected.
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.
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. Data values can be set to graph relative to the right or left axis by customizing the Trace Options (see below). The axes scales are only shown on the graph if there are data fields linked with them.
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. Note that scaling occurs when the Apply button is pressed on the dialog box.
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.
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. The Left / Right Grid Colors select the color of the grid lines that go with the left or right axis scale. The X-Axis color sets the color of the X-Axis.
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. Save Config – Saves the graph configuration to a file that can be loaded in the future. Load Config – Loads a previously saved graph configuration file. 5.1.7.3.
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 – Sets whether the data trace is displayed on the left or right axis. Line Width – Sets the width of the trace. Wider traces are easier to see but may obscure other traces or small variations of the data. Line Style – Selects the style for the line.
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 – Opens the Graph Display Options dialog box. Clear – Erases the existing traces on the graph. Rescale – Scales the data values so they are all displayed within the graph boundaries. This option is available only when Powers of 10 Scaling is chosen for the graph.
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. As the vertical bar is moved across the graph, the Selected Fields box will display the data value(s) corresponding to the timestamp of the vertical marker.
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.
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.
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).
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.
Section 5. Real-Time Tools NOTE CR1000, CR3000, and CR800 Series Dataloggers — A program 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. Stop Program halts execution of the currently running datalogger program. Select the option to stop the program and retain the data files, or to stop the program and delete data files.
Section 5. Real-Time Tools To activate the remote keyboard select Datalogger | Terminal Emulator from the menu. CAUTION The remote terminal mode should be used with care. It is 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. 5.1.
Section 5. Real-Time Tools NOTE Only the summary tab is available for array-based dataloggers. The Table Fill Times tab lists the tables in the datalogger, along with the maximum number of records the table can hold and the estimated amount of time that it will take the table to fill. A data table can be reset from this window by pressing the Reset Tables button. NOTE Resetting a table will erase the data in the datalogger and in the data cache.
Section 5. Real-Time Tools FieldCalStrain instruction are zeroing, 1/4 bridge strain shunt, bending 1/2 bridge strain shunt, and bending full bridge strain shunt. More information on calibration and zeroing is found in Appendix F, 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.
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. Company logos, maps, or any image stored in a standard graphic file format can be placed on the screen. Many images have been included with RTMC.
Section 5. Real-Time Tools 5.2.1.2 Display Components Display components are the objects that are used to display data. To add a component to the workspace, click an item on the Component Toolbox and then click anywhere in the workspace. The component’s Properties window is automatically displayed when the object is first placed in the work area. The Properties window is used to set colors, scale values, text, etc., and to assign the data value to be displayed by the component.
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). In run-time mode, right-click a switch to change its state. The option to change the state of a switch with a double-click can be enabled in the Properties window. Image allows you to place a static image on the display.
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. If this is the first time the project has been saved, a Save As dialog will open to select the file name and directory for the project file.
Section 5. Real-Time Tools data value changes, and specify whether high quality or high speed is more important. (Disabling animation disables the smooth transition between values on gauges, status bars, etc. When a data value changes, the component will jump to the new value. This greatly enhances performance when dealing with fast data or large, complex projects.) The Customize menu item allows you to customize RTMC’s toolbars and menus. View Menu All of the View menu items are toggles.
Section 5. Real-Time Tools 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. Configure Auto Tabbing lets you enable or disable the automatic switching between project tabs when an RTMC form is run, and set the rate at which a new tab will be displayed.
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. Select two or more components by using the cursor to click and drag a bounding box around the desired components.
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. Help Menu provides access to help for all of the features of RTMC. 5.2.1.
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.
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.
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 – When consecutive operators have the same priority, the expression evaluates from left to right. This means that an expression such as a-b-c is evaluated as (a-b)-c. 5.2.1.4.
Section 5. Real-Time Tools 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. (e.g., ATN2(y,x)) 5-48 Function Description ABS(x) Returns the absolute value of a number. ACOS(x) Returns the arc cosine of a number. ASIN(x) Returns the arc sine of a number.
Section 5. Real-Time Tools Function Description 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. (x)MOD(y) Performs a modulo divide of two numbers. PWR(x,y) Raises constant x to the power of y. RND Generates a random number. ROUND(x,y) Rounds a number to a higher or lower number. SGN(x) Used to find the sign value of a number (–1, 0, or 1). SIN(x) Returns the sine of an angle.
Section 5. Real-Time Tools 5.2.1.4.7 String Functions Function Description Hex 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.
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. Timestamp Returns the timestamp associated with the record from which a value is derived. 5.2.1.4.
Section 5. Real-Time Tools 5.2.1.4.11 Statistical Functions 5-52 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. AvgSpa Returns the average of the specified values. Last Stores the specified value and returns the previous value.
Section 5. Real-Time Tools Function Description StdDevOverTimeWithReset Returns the standard deviation of the specified value since the function was reset. Total Returns the total of all values that it has considered. TotalOverTime Returns the total of all values whose timestamps are greater than the newest timestamp minus the specified interval. TotalOverTimeWithReset Returns the total of all values since the function was reset.
Section 5. Real-Time Tools and Run Project menu or clicking the Run-Time icon on the toolbar. This will start the project window with RTMC Run-Time as shown in the window below. 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.
Section 6. Network Status and Resolving Communication Problems LoggerNet provides several tools for monitoring the status of a datalogger network and troubleshooting communication problems within that network. The Status Monitor screen provides a way to monitor communications statistics. Statistics are displayed for data collection attempts and communication failures. PakBus Graph provides a visual representation of the devices in a PakBus network and lets you edit PakBus device setting.
Section 6. Network Status and Resolving Communication Problems 6.1.1 Visual Status Indicators There are three visual status indicators in the first column of the Status Monitor. A Communication Status Image to the left of each device indicates the current communication state for that device. The color and letter for the image are a way to quickly verify the LoggerNet communication server’s connection with the device.
Section 6. Network Status and Resolving Communication Problems where failures = number of communication failures retries = number of communication retries attempts = total number of communication attempts The Communication History can be displayed in a larger view by right clicking within the history for a device and selecting Comm History from the short cut menu. Each segment of time in this larger view represents 10 minute intervals.
Section 6. Network Status and Resolving Communication Problems Entries in the Available Columns field will not be displayed on the main screen. Entries in the Selected Columns field will be displayed on the screen. The arrow buttons are used to move entries between the two columns. Alternately, an entry can be moved from one column to the other by double clicking it. A variety of status information and statistics are available.
Section 6. Network Status and Resolving Communication Problems Primary Retry – A data collection failure has led to the primary retry collection schedule. Secondary Retry – The number of primary retries set in the Setup Screen have run out and the secondary retry schedule is now active. Schedule Off – Scheduled data collection is not enabled for this device. Comm Disabled – Communications for this device or one of the devices in the communication link from the computer has been disabled.
Section 6. Network Status and Resolving Communication Problems last clock check was performed. If the datalogger clock is slower than the computer clock, this will be a positive value. • 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.
Section 6. Network Status and Resolving Communication Problems • Memory Code (Mem Code) – (Array-based dataloggers only) This number is an indication of the amount of memory available in the datalogger. The amount of memory represented depends on the datalogger. See the datalogger operator’s manual for more information. • Next Data Collection (Next Data Coll) – The date and time of the next scheduled data collection for the device.
Section 6. Network Status and Resolving Communication Problems • Total Retries – The total number of communication attempts with a device after the original attempt failed since LoggerNet was started or retries were reset. • Uncoll Holes – The number of values in holes that cannot be collected from the datalogger (most often, because the data has been overwritten by newer data).
Section 6. Network Status and Resolving Communication Problems 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.
Section 6. Network Status and Resolving Communication Problems 6.1.2.7 Pool Devices The Tools | Pool Devices menu item opens a new window that offers information about each pool (root device) and each pooled device that has been assigned to it.
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. Currently active operations are identified by a green circle displayed to the left of the Device Name. Start Time – Indicates the time the operation started.
Section 6. Network Status and Resolving Communication Problems Remove Operations When Finished When this check box is selected (default), operations that are no longer active will be deleted from the displayed list. If this box is not selected, the last state of the operation before completion will continue to be displayed in the list. The displayed list is limited to a maximum of one thousand lines. After reaching the limit, the oldest lines are deleted as new lines are added.
Section 6. Network Status and Resolving Communication Problems 6.2.1 Log Types Transaction Log (tran$.log) – This log includes information on the transactions that occur between the datalogger support software and devices in the datalogger network. Examples of these types of events are clock checks/sets, program downloads, and data collection. Communication Log (comms$.log) – This log records information on the quality of communications in the datalogger network.
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. If none of the options are enabled (an option is enabled if a check mark appears to the left of the option name), only the time is displayed (hh:mm:ss AM/PM). If Date is selected, a date (MM/DD/YY) will be added to the time stamp.
Section 6. Network Status and Resolving Communication Problems The following settings are used to save the logs to disk as well as to control the number and size of the log files. To Disk – Selecting this check box enables saving the associated logs to files on the server computer hard disk. File Count – This setting determines the number of log files to be saved to disk for this type of log. The server will store up to the number specified before overwriting the oldest log.
Section 6. Network Status and Resolving Communication Problems When you first open Comm Test, the state of the devices is unknown, so the circles for each device will appear grey. 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.
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.
Section 6. Network Status and Resolving Communication Problems 6.4.4 Right-Click Functionality There are several options available from the floating menu that is displayed when you right-click a device (not all devices will have all settings): Edit Settings – This option shows the PakBus settings of a device (see above). Ping Node – This option will send a packet to the selected device to determine if it is reachable in the PakBus network. The results of the ping will be displayed in the Log Messages.
Section 6. Network Status and Resolving Communication Problems 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. You can also limit the display to show only dataloggers by pressing the Display button and choosing Stations Only.
Section 6. Network Status and Resolving Communication Problems Scheduled Collection – This is the automatic data collection schedule. The state is either enabled, disabled, or paused. Scheduled data collection is paused from the Status window (Pause Schedule check box). 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.
Section 6. Network Status and Resolving Communication Problems 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. The devices in the network map can be individually selected, but cannot be otherwise manipulated.
Section 6. Network Status and Resolving Communication Problems Back 2T – Applicable only to an RF Link Quality test, this is the maximum transition point of all T2 transitions within the tolerance window. (See Section 6.5.3.2, TD-RF Quality Report.) Front 1T – Applicable only to an RF Link Quality test, this is the minimum transition point of all T1 transition within the tolerance window. (See Section 6.5.3.2, TD-RF Quality Report.
Section 6. Network Status and Resolving Communication Problems Clear – Clicking this button clears the contents of the right-hand pane. Start Test – The action taken when this button is activated depends on the device selected in the network map. With an RFRemote-PB or RFRemote-TD selected: An RF Link Quality test will execute on the branch of the network map comprising the selected RFRemote-TD/PB and the associated RFBase-TD.
Section 6. Network Status and Resolving Communication Problems LoggerNet responds by sending an RF Test command packet, containing a definition of the RF path to be tested, to the RFBase-TD. The RFBase-TD executes the RF Link Quality test by sending an RF Test Packet across the network to the RFRemote-TD/PB at the end of the RF path.
Section 6. Network Status and Resolving Communication Problems T1 T1 T1 T2 T1 T1 T1 T2 T2 T2 T1 T2 T1 1 1 1 0 1 1 1 0 0 0 1 0 1 +V 0 Demodulated Data Stream Bit Rate = 3 KHz 102 0 Composite of all T2 Transitions 242 42 MIN 144 2 1 204 Composite of all T1 Transitions MAX MIN 102 0 204 4 MAX 54 166 3 4 TD-RF QUALITY REPORT 1 The total number of Data bytes in the test packet. Dynamically adjusted downward in response to lost or corrupted packets.
Section 6. Network Status and Resolving Communication Problems modem acknowledge the reception of an RF Test Packet. If the sending modem does not receive an acknowledgment, it will resend the packet. This is known as a ‘retry’. After executing a number of unacknowledged retries, the sending modem will decrease the number of bytes in the packet by approximately half before attempting additional retries.
Section 6. Network Status and Resolving Communication Problems 6.5.5 Other Tools in Troubleshooter Other network status tools can be launched from the Troubleshooter utility. These are the Comm Test and LogTool. These utilities have been explained previously in this section. A Terminal Emulator can also be opened. Terminal Emulation is explained in the Troubleshooting section of this manual. 6.
Section 6. Network Status and Resolving Communication Problems (white background/red text) The LoggerNet server is no longer running. If Warnings or Faults have been encountered, you can reset the state of the icon by right-clicking it and choosing Reset, or by opening the Server Monitor and choosing Options | Reset. If you select Options | Clear – Reset, the messages will be cleared from the message window as well.
Section 7. Creating and Editing Datalogger Programs Datalogger must be programmed before they can make measurements. LoggerNet offers three options for programming dataloggers. Short Cut, Edlog, and CRBasic Editor. Short Cut (also referred to as SCWIN) is an application for generating programs for all of Campbell Scientific’s dataloggers and preconfigured weather stations except the CR7 and CR9000. Users do not have to know individual program instructions for each datalogger.
Section 7. Creating and Editing Datalogger Programs way, but store the processed data in individual tables instead of arrays. Each final storage table will contain only data for that interval – e.g., fifteen minute, hourly, and daily data records will be in different tables. The user can more closely control the size of these tables (for example to store a “buffer” of twelve hours of one minute data without taking up all of the available memory).
Section 7. Creating and Editing Datalogger Programs Short Cut was designed with extensive built-in help. Help can be accessed at any time by pressing the F1 key. There are also Help buttons on most screens. You can also open the Help by selecting Short Cut Help from Short Cut's Help menu. Help for each sensor can be accessed by searching the Help Index or pressing the Help button from the sensor form.
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. When choosing a scan interval, remember that faster scan intervals will use more power. For most applications, a 10 to 60 second scan interval is sufficient.
Section 7. Creating and Editing Datalogger Programs From this box, you indicate which CR9000X modules are inserted into which CR9000X slots. To add a module, select the module by clicking on it in the Available CR9000X Modules list, select the Slot by clicking on the slot number, then press the arrow key. To remove a module, select the slot containing it and then press the Remove Module button.
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. Note that programs containing sensor files that are filtered from the list of Available Sensors will still load and work correctly in Short Cut.
Section 7. Creating and Editing Datalogger Programs 7.2.2.3 Step 3 – Choose Sensors to Monitor In step 3, you tell Short Cut which sensors you’ll be measuring. Short Cut organizes sensors into application groups: Some major groups have subgroups. Double-clicking the Meteorological group folder shows several subgroups of meteorological sensors. Double-click a subgroup to show the available sensors. Refer to the documentation for your sensors for the name of the sensors you have.
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. In the middle of the screen, look over the notes (or refer to the Help for this sensor), for this sensor may require other sensors or have limitations.
Section 7.
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). You can change a caption/color by clicking on the caption/color label. A wiring location can also be changed by clicking on the wiring location.
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. Note that there is also a User Entered calculation available in the Calculations folder. With it you can enter your own custom calculation.
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. Each sensor was allocated the necessary terminals. Short Cut will not let you add more sensors than there are terminals on that datalogger or device.
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.
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. On the right is a multi-tabbed grid that shows the output tables.
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. NOTE Table-based dataloggers have a TableName field as opposed to an array ID.
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.
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). Short Cut also displays a Results, Summary, and Advanced window: The Results tab provides information on the files that were created.
Section 7. Creating and Editing Datalogger Programs The Summary tab displays the information in the DEF file as described above. The Advanced tab (for CRBasic dataloggers) displays the CRBasic program that was generated. It includes a CRBasic Editor button which opens the program for editing in the CRBasic Editor. Note that any changes made to the generated program in the CRBasic Editor will not be reflected in Short Cut or future programs generated by Short Cut.
Section 7. Creating and Editing Datalogger Programs controls are off when a datalogger powers up so as to make the control decision based on a fresh measurement. See the datalogger manual for a full description of this feature. 7.2.3.4 Select CR200 Compiler Use this setting to select the directory and executable name that will be used to pre-compile the CR200/205 program to check for errors. Most Campbell Scientific dataloggers are sent an ASCII program file, which they then compile into machine code.
Section 7. Creating and Editing Datalogger Programs 7.2.3.6 Integration Some dataloggers have parameters available in their measurement instructions to provide integration for rejection of noise due to AC electrical signals. These parameters will be used by Short Cut if possible, but the frequency of this noise varies. In most of North America, the AC frequency is 60 Hz. However, in many countries the frequency is 50 Hz. If you know the frequency of this AC noise, you can select one or the other frequency.
Section 7. Creating and Editing Datalogger Programs 7.2.5 New Sensor Files Short Cut was designed with future flexibility in mind. Datalogger and sensor support is provided as individual files and not part of the SCWIN executable. As new dataloggers and sensors become available, new definition files will be created to add and modify the necessary features known to Short Cut. To update these files, you can download the latest version of Short Cut from the Campbell Scientific website: www.campbellsci.
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. Complete the information in the parameter fields and press Insert to paste the instruction into the program.
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. A sample list is shown below.
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.
Section 7. Creating and Editing Datalogger Programs • Insert File: Inserts a library file into the current program overwriting the highlighted text. 7.3.3 Toolbar The toolbar of the CRBasic Editor provides easy access to frequently used operations. New – Creates a new program window to start writing a new program. If you have defined a default template, the new program will start with the defined template instructions. Open – Brings up a File Open dialog to select a program file to open.
Section 7. Creating and Editing Datalogger Programs Undo – Each time the Undo button is clicked it will step back through the last changes made to the program. Redo – Cancels the undo and steps forward restoring the changes. Cut – Removes the selected part of the program and puts it on the clipboard to be pasted elsewhere. Copy – Places a copy of the selected part of the program on the clipboard to be pasted elsewhere.
Section 7. Creating and Editing Datalogger Programs Clear Bookmarks – Erases all bookmarks from the program. GoTo – Moves the cursor to a particular section of the program. Choose the section type from the list box that appears. User-Defined Functions and Subroutines – Provides a list box containing all of the user-defined functions and subroutines. Functions are identified with a purple F. Subroutines are marked with a black S.
Section 7. Creating and Editing Datalogger Programs 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). After the compile and save, this function sends the program to a user-specified datalogger. To do this, use the Compile, Save and Send item on the File menu or Compile menu, or you can press the corresponding button on the toolbar.
Section 7. Creating and Editing Datalogger Programs programs. A program with the extension of .DLD will be associated with all CRBasic-programmed datalogger types. Select the datalogger to send the file to, and then select the Run Options. Run Now The Run Now run options are different for the different datalogger types. CR1000/CR3000/CR800 Datalogger Run Now Options When Run Now is checked, the file will be sent with the Run Now attribute set.
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. With this attribute, the program is compiled and run in the datalogger. All data tables on the CPU are erased.
Section 7. Creating and Editing Datalogger Programs 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. If LoggerNet, PC400, or RTDAQ is running and the program compiles properly on the hardware, you will receive a message indicating that the program is now running on the datalogger.
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. Select a datalogger to open a dialog box containing a list of saved templates. A template can then be highlighted and deleted from disk.
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 Create Compressed File – Creates a new file with a _str extension. All user comments and line spacing in the program are removed from the file.
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. If Do Not Insert or Remove Any Blank Lines is selected, all other fields on this tab will be disabled.
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. Text colors and styles can be disabled by clearing the Enable Syntax Highlighting check box.
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. A check mark will appear next to the option in the menu when it is selected.
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. A step increase/decrease can be defined for the spin box, as well as maximum and minimum values.
Section 7. Creating and Editing Datalogger Programs The Constant Customization syntax may be best understood by looking at an example.
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. The constant SUnits has a list box with sec and min; sec is the default. The constant Reps is defined with a default value of 1. It is an edit box, into which any value can be entered. The constant Number is defined with a default value of 0, a minimum of -100 and a maximum of 100.
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. 7.3.
Section 7. Creating and Editing Datalogger Programs Program Set scan interval The program section defines the action of datalogging. The scan sets the interval for a series of measurements. Measurements Enter the measurements to make. Processing Enter any additional processing with the measurements. Call Data Table(s) The Data Table must be called to process output data. Initiate controls Check measurements and Initiate controls if necessary.
Section 7. Creating and Editing Datalogger Programs 7.3.4.3 Mathematical Expressions Mathematical expressions can be entered algebraically into program code to perform processing on measurements, to be used for logical evaluation, or to be used in place of some parameters. As an example of Measurement Processing, to convert a thermocouple measurement from degrees Celsius to degrees Fahrenheit, you could use the following expression: TCTempF=TCTemp(1)*1.
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.
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.
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.
Section 7. Creating and Editing Datalogger Programs The output processing instructions included in a data table declaration determine the values output in the table. The table must be called by the program using the CallTable (Tablename) instruction in order for the output processing to take. That is, each time a new measurement is made, the data table is called. When the table is called, the output processing instructions within the table process the current inputs.
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. The BufferSize is the size (in the number of scans) of a buffer in RAM that holds the raw results of measurements.
Section 7. Creating and Editing Datalogger Programs TABLE 7-3. Synonyms for True and False Predefined Constant True (-1) False (0) Synonym High Low Synonym On Off Synonym Yes No Synonym Trigger Do Not Trigger Number ≠0 0 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.
Section 7. Creating and Editing Datalogger Programs 7.3.4.12 Flags Any variable can be used as a flag as far as logical tests in CRBasic are concerned. 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.
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.
Section 7. Creating and Editing Datalogger Programs Tablename.record(1,n) = the record number of the record output n records ago. Tablename.output(1,1) = 1 if data were output to the table the last time the table was called, = 0 if data were not output. Tablename.
Section 7. Creating and Editing Datalogger Programs 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. 7.4.1.2 Context-sensitive Help Pressing the right mouse button with the cursor on a parameter will provide a pick-list of options or pop-up help for that parameter. More help is available by pressing at any time or the Help button in various dialog boxes.
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. A window similar to the one shown below appears.
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. (The asterisk is used to identify the beginning of a program table in the datalogger.
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 – Use input location and final storage labels that are meaningful for the data they contain. 7.4.2.2 Edlog File Types When a program is saved and compiled, the following files are created: • *.CSI – The CSI file is what the user actually edits.
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.
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 to move to the next parameter. There are two ways to get help on a parameter: • Select the parameter with your mouse and press the right mouse button. This brings up a dialog box from which to select a value or a pop-up description of what should be entered.
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. As an example, the following expression could be used to convert temperature in degrees Celsius to temperatures in degrees Fahrenheit: TempF=TempC*1.
Section 7. Creating and Editing Datalogger Programs TABLE 7-5. Operators and Functions Operators * multiply / divide + add – subtract ^ raise to the power of; enclose negative values in parentheses @ modulo divide E scientific notation; 6e–1=0.
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 6: 0 Offset ;the following expression converts TempC to ;a temperature in degrees Fahrenheit TempF = (TempC*1.8)+32 When this program is compiled, the DLD file contains the following instructions. The last 5 instructions calculate the expression.
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 Other errors are explained below. Variable Name Expected This message occurs when the expression is not set equal to an Input Location label.
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. If the letters are not on the function list, this error message occurs. New Line Expected Indicates one of the following situations: (1) An expression contains more than one equal sign.
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).
Section 7. Creating and Editing Datalogger Programs TABLE 7-6.
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 . An instruction or block of instructions can also be selected and deleted with the delete key.
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. 7.4.5 Display Options 7.4.5.1 Graphical Toolbar A graphical toolbar provides buttons for some of the more frequently used menu items in Edlog.
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.
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 . You may prefer to enter all input locations into the Edlog program before writing the program.
Section 7. Creating and Editing Datalogger Programs 12: If time is (P92) 1: 0 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. The first time, it will sample the value stored in the TempC location. The second time, it will sample the value stored in the BatteryV location.
Section 7. Creating and Editing Datalogger Programs Editing functions are available from the Input Location Editor’s Edit menu and a hot key: Insert () – 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.
Section 7.
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. Each of the columns indicate the essential characteristics of the data value being stored.
Section 7. Creating and Editing Datalogger Programs NOTE If changes are made to measurement or output instructions after custom final storage labels have been created, you should review the custom final storage labels to make sure the correct labels are still assigned to the desired output values. Some program changes involving an increase or decrease in input locations or output values could cause a label to no longer correspond with the value being output.
Section 7. Creating and Editing Datalogger Programs 7.4.14 Final Storage Area 2 The ring memory for CR10, CR10X, CR510, and CR23X dataloggers can be divided into two final storage areas. By default, all memory is allocated to final storage area 1. However, the datalogger’s memory can be partitioned into two final storage areas using this option. To allocate memory to Final Storage Area 2, enter the number of locations into the Final Storage Area 2 Locations field.
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. Then, use the second option above to display only those values of interest. 7.4.
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.
Section 7. Creating and Editing Datalogger Programs 7.4.18.3 Neighbor Filter This option allows you to list expected neighbors that are available to the datalogger in the PakBus network. The datalogger will attempt to issue a “hello” command to all the dataloggers listed in the neighbors filter list, and will transmit an expected communication interval. The communication interval is the interval on which the datalogger expects to receive communication from the neighbors.
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. This can be changed if desired by typing in a new path and/or file name directly, or by pressing the Browse button to the right of the Program File field.
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. To view only the messages related to problems in the field, enable the Show Only Problem Messages check box.
Section 7.
Section 8. Working with Data Files on the PC After data has been collected from the datalogger, you need a way to analyze that data. LoggerNet provides two tools to do this. View Pro is a file viewer that provides a way to look at the collected data. It will open data files (*.DAT) saved in a variety of formats including files from mixed-array and tablebased 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, *.
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. 8.1.2 The Toolbar Many of View Pro’s features can be accessed from the toolbar. The main View Pro toolbar includes the following icons: Open. Brings up a dialog box from which you can choose a data file to open. Copy. Copies selected text to the clipboard.
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 data value on the x-axis. New Rainflow Histogram. Brings up a Rainflow Histogram window from which you can view Rainflow Histogram data values. New FFT. Brings up an FFT window from which you can view FFT data values. Keep Selected Graph On Top.
Section 8. Working with Data Files on the PC 8.1.3 Opening a File View Pro provides three ways to open a file. The one you use depends on the type of file being opened. Use File | Open to open a data file, File | Open as Text to open other types of files, or File | Open as Hex to view a binary or text file in hexadecimal format. A file that has been recently opened, can be quickly opened again by selecting it from the File | Recent Files list.
Section 8. Working with Data Files on the PC 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 of a filename. Press the Browse button to the right of the Data Source field to browse to the desired database.
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. Windows Authentication or SQL Server Authentication can be selected.
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. The Login ID and Password may be optional. They will be set to blank in the connection string. It has been found that when set to blank, the login id and password configured in the system data source are used.
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. 8.1.5 Importing a CSV File The File | Import CSV menu item can be used to import A CSV (Comma Separated Value) file into View Pro.
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. File Delimiter Although CSV files are by definition comma delimited, other file delimiters (tab or space) can be selected in the File Delimiter drop-down list box.
Section 8.
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. Array-based Data Files When opening a data file from an array-based datalogger, you will be given the option of loading an FSL (Final Storage Label) file. The FSL file will be used to provide column headings. (The *.
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. Note that if no timestamps are used, data cannot be graphed. 8.1.6.1 Column Size When a data file is opened, the columns are autosized to fit the data.
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. Pressing the Cascade button or choosing Window | Cascade from the View Pro menu will return the data windows to this default arrangement at any time.
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. This can also be accomplished by pressing the Undo Zoom button on the toolbar.
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. The selection will be highlighted and will automatically be added to the currently selected graph.
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. A new Line Graph will be created with your selection(s) graphed. You may then continue adding selections to the Line Graph as described above.
Section 8. Working with Data Files on the PC 8.1.7.1.5 Line Graph Toolbar The Line Graph toolbar includes the following icons: Statistics. Displays statistics for each trace including Average, Standard Deviation, Minimum and Maximum. Note that these statistics are for the data displayed in the graph. They are not statistics for the entire column(s) of data. Note that an asterisk next to a statistics value indicates that the trace contains one or more bad data values (i.e., NAN, INF, etc.).
Section 8. Working with Data Files on the PC 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. When locked, the graph will not scroll. However, moving the scroll bar on either the graph or the data file will still scroll the data file. This is a toggle button. When the lock is currently enabled, there will be a lock on top of the icon. Graph Options.
Section 8. Working with Data Files on the PC When the data panels and graphs are currently synchronized, the button icon will have a check mark in the bottom right corner. Undo Zoom. Returns the graph to its original state after zooming. 8.1.7.2 Histogram From the Histogram screen, you can view histogram data. The Histogram button on the toolbar will be enabled if there is at least one valid histogram in the currently selected data file.
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. The first option is a drop-down list that shows the available histograms in the currently selected data file. Select the histogram that you would like to view.
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. It is also the color with which that histogram record is displayed if the “Use Selection Color” option is chosen in the Selection Properties dialog box.
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 Histogram. It may be useful to hide the gradient, when printing the Histogram. Modify Selection. Brings up the Histogram Setup dialog box from which you can change the options for the selection. Undo Zoom. Returns the Histogram to its original state after zooming. 8.1.7.
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. Select from the X and Y drop-down lists the values to be used for the X axis and Y axis, respectively. 8.1.7.3.2 XY Plot Toolbar The XY Plot toolbar includes the following icons: Copy to Clipboard.
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.
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. The first option is a drop-down list that shows the available rainflow histograms in the currently selected data file. Select the rainflow histogram that you would like to view.
Section 8. Working with Data Files on the PC 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. NOTE All rainflow histogram records from the same rainflow histogram will have the same default name in the list.
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. Undo Zoom. Returns the Rainflow Histogram to its original state after zooming. 8.1.7.5 FFT From the FFT screen, you can view FFT data.
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. Select the FFT that you would like to view. The second option allows you to choose which record of the FFT you would like to view initially.
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. It is also the color with which that FFT record is displayed if the “Use Selection Color” option is chosen in the Selection Properties dialog box.
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. Modify Selection. Brings up the FFT Setup dialog box from which you can change the options for the selection. Undo Zoom. Returns the FFT to its original state after zooming. 8.1.
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. Note that changes to the records included will not be reflected in the data panel, until the Apply button is pressed. Copy Selection Copies selected text to the Windows clipboard.
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.
Section 8. Working with Data Files on the PC 8.1.9.2 Printing Text To print numerical data, press the Print button or select File | Print from the menu. A dialog box will appear allowing you to choose the printer, print range, number of copies, etc. After setting the properties, press OK to print the data. To preview your data before printing, press the Print Preview button or select File | Print Preview from the menu.
Section 8. Working with Data Files on the PC 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). Split can generate tables with report and column headings, as well as time synchronize and merge up to eight data files.
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.
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. On the INPUT FILE tab you only need to specify the input file name, copy condition, and the data to select.
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 key. All of the values could be selected by clicking the first one and holding the mouse button down, and dragging to the end. Once the values you want have been selected click Paste.
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. Notice also that it pasted the Array ID into the copy condition: 1[60] tells Split that in order to copy a line of data, the first value in that line must be 60.
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. They should be edited before running Split. To edit one of the labels, press the key or use a mouse to copy, cut, and paste.
Section 8. Working with Data Files on the PC Close the Run window. If you wish to save this parameter file for future reports, choose FILE | SAVE. The file will be saved with a .PAR extension. 8.2.3 Split Parameter File Entries 8.2.3.1 Input Files The name of the Input File is entered in the space to the right of the Browse button. The default directory is the working directory for Split (if the default installation directories were chosen, this will be c:\campbellsci\splitw).
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. The data in the various formats are identical. Each line of data represents an “Output Array”, starting with an Output Array ID (in this case 115).
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. For instance, to process two files named TEST.DAT and TEST_1.DAT the user would select TEST.DAT and TEST_1.DAT as Input Files.
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. This is done by clicking the Offsets button and selecting the Last Count option. This feature may be used to process only the new data from a file in which new data are being appended periodically to the data file.
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. Selecting the Align Array check box will cause Split to begin processing at the beginning of the next row.
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. Number of Values in Each Burst When processing a burst data file, enter the total number of values recorded for each Burst (this is the number of burst scans multiplied by the number of channels per scan).
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. (The two-parameter mode is backwards compatible with the original Date and Edate functions used in older versions of Split.) 8.2.3.1.
Section 8. Working with Data Files on the PC Logical “and” and “or” statements can be used when specifying the Start Condition. A logical “and” statement means that all conditions must be true for the statement to be true. Up to three conditions can be connected with “and” statements. If too many “and” statements are used, an error message will be displayed when you run Split. The logical “or” statement means that if any of the conditions are true, then the statement is true.
Section 8. Working with Data Files on the PC 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.
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. The Stop Condition is expressed with the same syntax as the Start Condition.
Section 8. Working with Data Files on the PC 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. The array ID is the first element of a data file, so the line should read 1[123], where 123 is the actual array ID you want to process. • In the Select field, type in the number for each element (data value) you want to be output in the report.
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 Second Input File = Data_1.DAT:2 Stop condition = C,1[200] Copy = 1[101] Select = 1,2,3 Third Input File = Data_1.DAT:3 Stop condition = C,1[200] Copy = 1[102] Select = 1,2,3,4,5 Fourth (“end of test”) Input File = Data_1.
Section 8. Working with Data Files on the PC A typical application for the Trigger on Stop Condition is to reduce days of hourly data into daily summaries. A logical element to use for the Stop Condition is time (hrmn). Assuming the third element of the hourly Output Array is hrmn, and midnight is output as 0, the Stop Condition is entered as 3[0] (or F,3[0] if the F option is used). The Time Series processing is performed over a day defined by midnight to midnight.
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. If the element being tested falls within the range, the Copy condition is satisfied and the data is processed.
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. For example, 3[3.7..5],4..7[5..10] implies that element 3 is selected only if it is between 3.7 and 5, inclusive, and elements 4,5,6, and 7 must be between 5 and 10, inclusive.
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. For example, x = 4–5∗(6∗ 3.0) means that x is equal to element 6, times the number 3, times element 5, subtracted from element 4. A numeric value is distinguished from an array element by the inclusion of a decimal point.
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 OPERATORS OPERATOR PRECEDENCE ORDER (3 = high, 1 = low) ^ = raise to the power x Mod y = Modulo divide of x by y ∗/ = multiplication, division +– = addition, subtraction 3 2 2 1 EXAMPLES OF SYNTAX FOR MATHEMATICAL OPERATORS 3∗5 multiply element 3 by element 5 3/5 divide element 3 by element 5 (3..5)/(8..
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 Arctan(x) returns the arc tangent of element x in degrees. Examples: Arctan(7) = 89.788 Arctan(7/6) = 87.365 Cos(x) returns the cosine of element x in degrees. Examples: Cos(5) = .57215 Cos(5–6) = .
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. Examples: SpaSd(1..7) = 394.57 SpaSd(5,2,1) = 49.607 Sqrt(x) returns the square root of element x. Examples: Sqrt(3) = 34.641 Sqrt(3^ 2.0) = 1200 8.2.3.1.
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. when a Trigger on Stop Condition (F option) is met 2. at the end of a data file (or within a range specified by Start and Stop Conditions) 3.
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. The following set of weather data from Mt. Logan in northern Utah gives a total of seven elements each hour.
Section 8. Working with Data Files on the PC Count(x;n) NOTE returns the number of data points (non blanks) in element x over a full data set or every nth value. Example: Count(1) = 24 (24 data points in data set). Blanks and Count are functions designed for checking the integrity of the data file. A common use for these two functions is “100.*BLANKS(x;n)/BLANKS(x;n)+COUNT(x;n)” which gives the percentage of holes (bad data) in the file.
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) SmplMax(x;y;n) returns a sample of element x every nth value. Examples: Smpl(4;8) = 23.98 (RH every 8 hours) 24.31 (RH every 8 hours) 37.13 (RH every 8 hours) looks for a maximum value in element x and samples element y when the maximum is found. If an nth value is specified then it outputs the sample on a maximum every nth value, otherwise it outputs the sample on a maximum at the end of file.
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. S=seconds, H = HoursMinutes, D = Day, Y = year. The output timestamp is quoted text. Date can be used to create monthly time series summaries.
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. NOTE A carriage return/line feed is recognized by Split as an element, and may throw the column headers off in the output file. “Label” returns a comment in the output file. This is a useful formatting function when labels are desired on the same line as the data.
Section 8. Working with Data Files on the PC 23 38.8 17.12 24 37.13 11.86 Smpl (Line;8), Smpl (4;8), Smpl (5;8) 1 23.98 6.588 2 24.31 8.88 3 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) = 100 58.56 200 57.48 . . . . . . 1100 61.34 1200 60.61 1300 61.01 1400 60.93 . . . . . . 2300 55.48 0 55.22 WDQ(n) Outputs the wind direction using an alphabetical abbreviation, based on 8 quadrants (N, S, E, W, NE, NW, SE, SW).
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; H; D; Y). If “serial” is entered for the “format” string, a serial date will be output. Other special functions are “hourarray” and “dayofyear”.
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” date, the date function will convert that time stamp to 0000 hours with “tomorrow’s” date.
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. This example does calculations based on temperature and wind speed to determine the wind chill.
Section 8. Working with Data Files on the PC The following screen shows the output file setup including the column headings and the units. This .PAR file produces a wind chill summary of the Mt. Logan Peak data set. The formula for calculating wind chill is given as follows: Te = 33–(h/22.066) where Te = Wind Chill equivalent temperature, degrees C h = ((100V)0.5 + 10.
Section 8. Working with Data Files on the PC Wind Chill Report from Mt. Logan Temp deg C 14.756 14.156 13.806 13.639 13.65 12.961 13.306 14.511 15.439 16.161 16.3 15.894 16.117 16.072 16.833 17.639 18.972 19.628 19.217 18.067 15.467 13.439 13.044 12.9 Wind Speed m/s 2.6172 3.6967 3.4643 3.3972 4.6533 4.0185 4.2554 2.9448 2.4397 2.066 2.6489 3.0463 3.7325 4.8812 3.7682 3.9694 3.5626 3.0208 3.1648 3.9157 5.2791 6.9821 7.6526 5.3014 H 438.06 489.58 491.34 493.4 529.57 530.58 528.27 456.04 414.97 383.21 402.
Section 8. Working with Data Files on the PC • 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; (3..6)/(2..5) is the same as 3/2, 4/3, 5/4, 6/5. • The element or expression that is the argument of a math or Time Series function, must be enclosed in parentheses. A range of elements can be specified, resulting in as many outputs as elements (e.g., Avg(3..5,7) will output 4 averages).
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).
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. For instance, if the original data had 15 minute outputs and you only want hourly outputs, then an interval of 60 minutes must be specified following the element number. This is entered as (assuming hrmn is element number 3) “3[60]”.
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. Use the Browse button to change directories. Split will assign this file an extension of .PRN if an extension is not specified by the user.
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. The Field, Comma, and Printable options produce files formatted as Field Formatted, Comma Separated, and Printable ASCII, respectively. An example of each of these file types is given in TABLE 8–1 in the Input Files section.
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. There are three report options: File, Printer, HTML. One or more can be selected. A report sent to a file has the extension of .RPT.
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. See TABLE 8-9 for definition of blank or bad data. Whatever text string the user enters in the field will be entered if a blank or question mark is in the data or if data are out of range.
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. Therefore, by default, you will have blank lines in your output file for each day from Jan 1st to Sept 9th. Using the Time Sync to First Record option will avoid these blank lines.
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” date. (This is because the algorithm used by the date function is based on Windows’ time format, and it does not support a 2400 time stamp.
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. When this check box is selected, the record numbers will not be included in the converted file. This will affect the element numbers used for the Start, Stop, Copy, or Select fields of the PAR (e.g.
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” version of the Split Report Generator. When Splitr.exe is run, the file is processed as if the user chose Run | Go from the Split menu. Splitr.
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 will open two copies of Splitr and process the two files simultaneously. NOTE When using the /M switch in a batch file, the behavior may depend on your Windows version.
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. “SPLITR LOGAN/R , TEST.PRN” 8.2.6.3.
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. /M Compares two input files and creates an output file with a complete data set comprised of both files. This is the same at the Match Files option that is found under the Other button of the Output File tab.
Section 8. Working with Data Files on the PC /H 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. /U Removes the record number from TOB files that are processed with Split. This is the same as choosing the No Record Numbers from TOB Files check box that is found under the Other button of the Output File tab.
Section 8. Working with Data Files on the PC /M 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 Input file: input1a.dat Output file: output.prn Other outputs: Output.
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. Note that you can also select a directory on your hard drive in which binary data files have been copied.
Section 8. Working with Data Files on the PC 8.3.2.1 File Format The File Format is used to specify the format in which the data file should be saved. Select the desired option from the list box: ASCII Table Data (TOA5) – Data is stored in an ASCII comma separated format. Header information for each of the data values is included, along with field names and units of measure if they are available. Binary Table Data (TOB1) – Data is stored in a binary format.
Section 8. Working with Data Files on the PC _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. Use Removemarks – When a compact flash card is removed from a CR1000 or CR3000 datalogger, a special mark is inserted in the last record. The Removemark is similar in nature to the Filemark.
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. If the destination file does not exist when a conversion is done, a new file will be created. On subsequent conversions, converted data will be appended to the end of that 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). This corruption can be at the beginning of the data file or anywhere within the stored data.
Section 8. Working with Data Files on the PC When running CardConvert from a command line, you can designate the CCF file using the command line option runfile. For example, “C:\Program Files\Campbellsci\CardConvert\CardConvert.exe” runfile=“C:\Campbellsci\CardConvert\myfile.ccf” The above command line will run CardConvert using the settings contained in myfile.ccf. If there are no problems or questions encountered, CardConvert will start, convert the file(s), and then exit with no user interaction.
Section 9. Automating Tasks with Task Master The Task Master is an application that is used to set up a Task that can be run on a defined schedule or based upon a data collection event from a datalogger. A Task can be data collection from another datalogger, FTP of a collected file, or anything that can be executed in a computing environment, such as a command line operation, a program executable, a batch file, or a script.
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. A new task will appear attached to the selected datalogger. You can then set up the conditions for the task with the options on the right side of the window.
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. 9.1.1.2 Logger Event Tasks There are 13 data collection events that can be selected to trigger a task linked to a datalogger.
Section 9. Automating Tasks with Task Master • After Any Scheduled Call – After a scheduled data collection attempt, regardless of whether or not the call is successful. The task is triggered only by a scheduled collection. • After Successful Call – After a successful scheduled data collection, after using a Collect Now button successfully, after a call-back, or after another task that calls the associated station successfully.
Section 9. Automating Tasks with Task Master the file name ahead of time. Therefore, the %F option can be used to insert the file name in the command line options. • After Any Data Collected – After data is collected by any means, and the call is terminated for any reason (success or failure). The task is triggered by a scheduled collection, by using a Collect Now button, a datalogger call-back, or another task that calls the associated station which causes any data to be collected.
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. The interval specifies the time between task executions. In the example shown, the task will start on October 18, 2013 and run once an hour at 15 minutes past the hour.
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. For example: To execute a task on the first day of every month at 8:00 a.m., set the Hours of the Day to 8, the Minutes of the Hour to 00, the Days of the Month to 1, and leave the other settings blank.
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.
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. If multiple check boxes (Execute File, Call Station, FTP Settings) are selected, the actions will be launched at the same time. Execute File – Select this check box to execute a file or command when a task event is triggered.
Section 9. Automating Tasks with Task Master NOTES Always enter the full path when specifying the file to execute. Otherwise, the file may not be found or may not run as expected. The Task Master can process only one command in a command line. If multiple commands are required, place the entire command sequence in a batch file and execute the batch file from the Task Master.
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.
Section 9. Automating Tasks with Task Master Example #2: The following configuration will run LNBackup.exe to perform an automated backup. The –AppendTime command line option creates a unique filename based on date and time each time the task is run. If the –AppendTime command line option is omitted, the backup file will be overwritten each time the task is run.
Section 9.
Section 9. Automating Tasks with Task Master Example #4: The following configuration will set up a task to perform a clock check on the datalogger that is named CR1000_IP in the network map. 9.1.2 Status Tab The Status tab for the Task Master provides information on the type of task, the last time a task was run, the next time it will be run (if it is a scheduled task), and the outcome the last time the task was run.
Section 9. Automating Tasks with Task Master Task Name – The name that was given to the task when it was set up. Action – Indicates whether the task will Call Station, Execute File, FTP File, or perform multiple actions. Event Type – This column indicates what type of event will trigger the task. It is only applicable to Add After tasks. The event types are listed above (Station Event Types).
Section 9. Automating Tasks with Task Master • • • • • • Communications Disabled Bad Table Definitions Task Disabled Datalogger is Locked File Write Failure Datalogger is not Valid Last FTP Started – The last time the attempt to FTP a file was started. Last FTP Finished – The last time the attempt to FTP a file was finished. Last FTP Outcome – Outcome of the Last FTP attempt. This will have a value defined under Exit Codes here: http://curl.haxx.se/docs/manpage.
Section 10. Utilities Installed with 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.
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. If the device supports IP communication, the Use IP Connection check box will be enabled.
Section 10. Utilities Installed with LoggerNet Two common operations are sending a new operating system and communicating with a device in terminal emulation mode. These two operations are covered below. Refer to DevConfig’s embedded help or the user manual for a device for more device-specific operations. 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.
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.
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.
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.
Section 10. Utilities Installed with LoggerNet 10.2 CoraScript 10.2.1 CoraScript Fundamentals CoraScript is a command line interpreter that reads its commands as text from its standard input device and writes the results of those commands as text to its standard output device. This style of input and output makes it possible to externally control the LoggerNet server operation using input and output redirection.
Section 10. Utilities Installed with LoggerNet • Command parameters are often set using a combination of the parameter name and the value in this format: --name=login. Be sure to read the help for the command you are using. • A response preceded by a plus sign (+) indicates that the command was successfully processed. • A response preceded by a minus sign (–) indicates that the command failed and will usually be accompanied by a reason for the failure. 10.2.2.
Section 10. Utilities Installed with LoggerNet NOTE You may want to consider using LoggerNet’s Scheduled Backup/Manual Backup/Restore Network options available from the Setup Screen as an alternative to using CoraScript for network backups.
Section 10. Utilities Installed with LoggerNet 10.2.2.5 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. 10.3 RWIS Administrator 10.3.
Section 10. Utilities Installed with LoggerNet The following items are available from this main screen: RWIS Stations – Lists all RWIS stations that currently exist in LoggerNet’s network map. This application will ignore all other device types. Add Station button – Used to add a new RWIS station to LoggerNet’s network map. Delete Station button – Used to delete the selected station from LoggerNet’s network map.
Section 10. Utilities Installed with LoggerNet in the Stations List once the add is complete and the settings panels will reflect the default settings for the new station. 10.3.3 Editing Station Settings The RWIS Administrator displays the LoggerNet settings for the selected station in three tabs. These settings deal with communication parameters, SNMP and FTP authentication, scheduled data collection, and collection of snapshot images. 10.3.3.
Section 10. Utilities Installed with LoggerNet SNMP Private Community – Enter the “community” string that will be sent with SNMP SET requests. Like the public community string, this value may vary between devices but the default value of private will be sufficient for most cases. FTP User Name/Password – Enter the authentication parameters for the FTP server on the RWIS station. These parameters will be used when snapshots are retrieved.
Section 10. Utilities Installed with LoggerNet elapsed since the last attempt, LoggerNet will immediately try to perform a poll. In some cases, this may not be the desired behavior. Selecting the Stay On Schedule check box will cause LoggerNet to always wait until the next even Normal Poll Interval to perform a poll. Base Date – Enter a date and a time that the first polling attempt for the device should occur.
Section 10. Utilities Installed with LoggerNet File Format – Specify the format for the selected file. Options include the following: CSV – Data is stored in a user-defined comma separated format. TOA5 – Data is stored in a comma separated format. Header information for each of the columns is included, along with field names and units of measure if they are available. TOB1 (binary) – Data is stored in a binary format.
Section 10. Utilities Installed with LoggerNet Controls on this panel include the following: Collect Snapshots on Schedule – Select this check box to enable snapshot collection schedule as part of scheduled data collection. Clearing the check box disables snapshot collection. Source Paths – This box shows the expected source paths for snapshot filenames on the NTCIP-ESS device.
Section 10. Utilities Installed with LoggerNet Controls on this panel include the following: Automated Clock Check – This check box is used to turn the clock check schedule on or off. Base Date – These fields are used to specify when the first scheduled clock check should occur. If the time reflected by these fields has already occurred, a clock check will be performed during the next data collection attempt with the station. Interval – Enter an interval for how often a clock check should be performed.
Section 10. Utilities Installed with LoggerNet 10.3.3.5 Data Tab The fifth tab can be used to view the values associated with the most recently collected record from any table. To begin, select the table you wish to monitor from the drop-down list. Press the Poll Table button to poll the specified table or the Poll All button to poll all tables. The fields of the specified table will be displayed in the grid. 10.3.
Section 10. Utilities Installed with LoggerNet station’s version number. Variables that can have multiple instances are represented as subscripted arrays. 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.
Section 10. Utilities Installed with LoggerNet To: NOTES • TOA5 • TOACI1 • TOB1 • CSIXML • CSV File Format Convert cannot produce TOB2 or TOB3 files, and it 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. If you convert from a format with less information, some fields will be left blank. Some formats (e.g.
Section 10. Utilities Installed with LoggerNet File Check Write File to cause an output file to be created. The file will be created in the same directory as the source file. The base name will be the same as the source name with the new format prepended. For example, test.dat becomes TOA5_test.dat. Use the drop-down list to select the format of the new file.
Section 10. Utilities Installed with LoggerNet Discontinuity – A new file is created when missing records are encountered (see Check section above). The How Many? can be used so that small gaps do not start a new file. The file will be baled only if the entered number of records (or more) are missing. Bale Info Use to specify the Start Time and Interval and start time for baling based on time. 10.5 Toa_to_tob1 This utility is used to convert TOA5 (ASCII Table Data) files to TOB1 (Binary Table Data) format.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote The LoggerNet Admin and LoggerNet Remote packages include several additional utilities or client applications that can be useful for the management of larger networks. The main difference between these two packages is that LoggerNet Admin includes the LoggerNet server and client applications/utilities, while LoggerNet Remote includes only the clients/utilities.
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. Follow the instructions on screen to set up the account.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote Confirm Password Enter the password for the account a second time. Security Level Use the list box to select one of five security levels for the user: Read Only – The user can view data values and status information but has no other rights. Operator – The user can view data values, check the clock, and collect data. He cannot make changes to the datalogger program, datalogger settings, or the server settings.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote TABLE 11-1.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote Deleting an Account To delete an account, highlight it and press the Delete button. When you are logged in to the Security Manager under the Administrator Account, you cannot delete that account. To delete it, log in under a different account with Full Administrator rights. Editing a Password To edit the password for an account, highlight that account, press Edit Password and enter the new information in the resulting dialog box.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote hole. If the data has been overwritten by the datalogger, then it is an uncollectable hole. 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.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote detected – This state, printed with black text, indicates that the hole has been detected but attempts have not yet been made to collect it. collecting – 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.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote 11.3 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. 11.3.1 Data Filer Requirements Data Filer is an application that is capable of accessing the data in the LoggerNet data cache and storing that data to a file.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote 11.3.2.1.1 Setting Up the Data Filer Once connection to the LoggerNet server has been established, a list of dataloggers set up in LoggerNet will be displayed in the Stations field (left side of the window). To retrieve data for a particular station, use the mouse pointer to select the datalogger then set up the Collection Options (explained below), select one or more tables to be collected, and press the Start Collection button.
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. TOA5 – Data is stored in a comma separated format. Header information for each of the columns is included, along with field names, units of measure (if they are available), and output processing types (average, sample, total, etc.).
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote Starting Date/Time and Ending Date/Time The Starting Date/Time and Ending Date/Time fields are used when the Collect Mode is “Data from Selected Date and Time”. The two fields are used to specify a range of records to collect, based on the records’ time stamps. To complete a date field, type in a date directly or click the arrow to the right of the field to display a calendar from which to choose a date.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote 11.3.5 Record Number Anomalies Under certain circumstances it may appear there is a problem with the number of records and their record numbers reflected by the Data Information table. It is possible for the oldest record to have a record number higher than the newest record. This is due to a combination of events. Tables in dataloggers are configured as ring memory.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote Once the data tables to be exported are specified, the user selects an output socket port and the export utility will begin “listening” for a request from a remote application to send data. When the connection to the application is established, data export is initiated. The options that determine the operation of Data Export are set from the dialog box opened from Data Export’s Edit | Options menu item.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote where “directory” is a keyword indicating that the next parameter “pathname” is a valid directory path on the computer file system. Each instance of Data Export started in this manner will save it’s setting in a separate *.ini file. This initialization file is saved to the directory specified by the “pathname” command line argument.
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. The record acknowledgment allows Data Export to ensure that every record it intended to send was successfully received by the client.
Section 11. Utilities Installed with LoggerNet Admin and LoggerNet Remote of the datalogger name, table name and the record number of the received record. 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.
Section 11.
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 longer than the longest period between records the client would expect to receive from the server.
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. Communications between the client and server are conducted using ASCII records where each record is terminated by a carriage return – line feed (CRLF) pair. Record length varies quite a bit.
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 “)”. AckRecord = StationName “,” TableName “,” RecordNumber. FieldSpecs = FieldName “ “ FieldType {“,” FieldName “ “ FieldType}. FieldValues = FieldValue {“,” FieldValue}. StationName = Label. TableName = Label. FieldName = Label.
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 is in the original protocol: outputRec = recordHeader { “,” fieldName “,” fieldType “,” fieldValue } “\r\n”. recordHeader = stationName “,” tableName “,” timeStamp “,” recNo. FieldName = string.
Section 11.
Section 12. Optional Client 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.
Section 12. Optional Client Applications Available for LoggerNet 12.3 RTMC Run-Time RTMC Run-Time is an application that allows you to remotely run real-time graphic display screens that have been created in the RTMC Development version. RTMC Run-Time is discussed in Section 5, Real-Time Tools, of this manual. 12.4 RTMC Pro RTMC Pro is an enhanced version of the RTMC Development application that ships with LoggerNet and is talked about in Section 5.2, Real-Time Monitoring and Control.
Section 12. Optional Client Applications Available for LoggerNet 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 automation and control hardware and software.
Section 12.
Section 13. Implementing Advanced Communications Links This section describes the configuration and operation of a variety of communications links. The communications links included here require special setup or configuration, or require special consideration in the implementation to work properly. NOTE Refer to Section 4, Setting up Datalogger Networks, if you need general information on adding devices to the device map. 13.
Section 13. Implementing Advanced Communications Links 13.1.2 Operational Considerations 13.1.2.1 Scheduled Data Collection The intervals for scheduled data collection need to be set up to allow time for the communications link to be established. Keep in mind that the phone modem requires 15–20 seconds to dial and establish communication. Also each link in the RF connection requires 3–5 seconds to link to the next device.
Section 13. Implementing Advanced Communications Links 13.1.3.1 Hardware Setup The RF modem in the RF Base has to be configured to work in Synchronous Device Communication (SDC) mode. This is done by changing the 9th DIP switch inside the RF Base modem to a 0 or closed. This will allow the datalogger to pass communication to the RF Base. NOTE SDC mode cannot be used with 21X or CR7 dataloggers or any of the table based dataloggers.
Section 13. Implementing Advanced Communications Links To begin, add a Serial Port to the device map if one does not exist. Add a Phone Modem to the Serial Port. To this Phone Modem, add a Remote Phone Modem. Next, add an MD9 base and then a remote MD9. To complete the network, add your datalogger to the remote MD9. Review all of the settings for each device, and make any changes to customize the settings for your network configuration. 13.2.2 Operational Considerations 13.2.2.
Section 13. Implementing Advanced Communications Links 13.2.2.5 Grounding Depending on the configuration and distance of the MD9 network, be sure to follow the grounding guidelines provided in the MD9 hardware manual. Grounding issues have been known to prevent reliable communications and data collection. 13.
Section 13. Implementing Advanced Communications Links 13.3.3 Special Considerations To implement TCP/IP to RF communications, a serial server has to be provided as the interface between TCP/IP and the serial connection on the RF base. There are a number of Serial Server devices available including the NL100 Network Link Interface manufactured by Campbell Scientific.
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. Default Gateway – This specifies the IP address of the router for the local computer network. Consult with the computer network administrator for the proper setting.
Section 13.
Section 14. 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. This section also includes descriptions of some of the tools such as Terminal Emulator and Data Table Monitor that can be useful in troubleshooting LoggerNet problems. 14.
Section 14. Troubleshooting Guide Problem: Message indicating Server Connection Lost. Remedy : This message indicates that the main communications software has stopped responding to the user interface screens. You need to close down all of the applications along with the 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.
Section 14. Troubleshooting Guide TABLE 14-1. Socket Error Messages Socket Error Number Message Meaning User Response to Message 10013 Permission Denied. The requested socket connection has refused the connection. This is normally a network type of issue. Check with your computer network operator. 10024 Too many open files. Too many open sockets for the applications running. This can occur when you have many applications that are using sockets running at the same time.
Section 14. Troubleshooting Guide 14.2.3 Data Collection Issues Problem: Scheduled data collection is enabled but no data is being saved in the data files, or data is not updating on numeric or graphical display. Remedy 1: Make sure that communications are enabled for the datalogger and all the devices in the communications link. Remedy 2: For table-based dataloggers, make sure tables are included for collection and the table definitions are current.
Section 14. Troubleshooting Guide 14.5 Terminal Emulator to Test Communications Terminal Emulator is a utility to test communications with the devices in the datalogger network. Terminal Emulator is accessed from the Datalogger menu of the Connect Screen. The operation of a ComPort and the connection to a phone modem can be tested. The Terminal Emulator utility is available from the Connect Screen to help troubleshoot communications problems.
Section 14. Troubleshooting Guide Dataloggers The example above shows a terminal emulation session with a datalogger. Once you have selected the datalogger click Open Terminal to start communications. Array-based dataloggers require you to type in the letters 7H (2178H for CR7 and 21X) and press Enter to establish terminal emulation mode. Table-based dataloggers are ready for terminal emulation when they are first selected. Just press Enter.
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 To hang up the modem. You should see an “OK” on the screen sent by the modem. If you do not, perhaps there is no modem attached to that COM port or perhaps the modem is not powered on. Type AT&F To put a typical Hayes-style modem back to the factory defaults.
Section 14. Troubleshooting Guide too poor to support communications. A long series of nonsense characters usually indicates electrical noise in the vicinity of the telephone cable that the modems are interpreting as high and low digital signals and reporting them as characters. Type E To hang up the datalogger, which causes it to turn off its phone modem, which in turn causes loss of the carrier signal between the modems.
Section 14. Troubleshooting Guide sections following illustrate things to look for and tests to perform to troubleshoot RF operations. 14.6.1 Checking RF Components and Connections Before testing RF signal strength, there are several things that should be done to verify that the right RF components are in place. 1. Check that the RF modem has the correct switch ID set on the DIP switches. (This is a common problem and should be checked first.) 2. Check the type and brand of the radio.
Section 14. Troubleshooting Guide NOTE If you are using a data radio that does not have a transmit button 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. See the radio documentation to identify this pin. Connect a momentary push-button to either raise or ground that pin.
Section 14. Troubleshooting Guide If the VSWR is below 1.5:1, then power transmission is good. However, be sure the antenna is oriented properly. While at the station, check the voltage on the 12 V port of the datalogger both with and without the radio transmitting. Regardless of the battery type, the datalogger requires a minimum of 9.6 Volts. 14.6.3 Troubleshooting with Attenuation Pads This test is used to measure the signal strength of the radio signal between two radios.
Section 14. Troubleshooting Guide 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. In this case, the signal power is far below the power limit.
Section 14. Troubleshooting Guide will not be picked up. If squelch is not broken, then either the signal power is less than –115 dBm, or something is wrong with the power supply, antenna orientation, or cable connections. If squelch is broken on the receiving radio, the site can be tested with the attenuation pads to determine the approximate signal power if it is between –115 and –95 dBm.
Section 14. Troubleshooting Guide To start Data Table Monitor open Windows Explorer and got to the Program 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.
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. This dialog gives you choices about which records to display and the data file in which to store them.
Section 14. Troubleshooting Guide • At Offset from Newest: This option allows you to specify how many records back from the current write index to go. A setting of 10 in the Start Offset box will display the last 10 records collected. The Start File Mark, Start Record Number, Start Offset, Begin Date, and Offset from Newest edit boxes are used only with the corresponding start options above. For each option selected, the appropriate boxes are enabled.
Section 14. Troubleshooting Guide 14.8 Troubleshooting PakBus Communications For additional information on PakBus communication, refer to our PakBus Networking Guide (under separate cover). Problem: LoggerNet can’t communicate with in-range PakBus datalogger (PC-RF400~~~RF400-CR510PB~~~ RF400-CR510PB~~~CR205) Possible reason 1: LoggerNet’s PakBus Address for datalogger doesn’t match datalogger’s PakBus Address. Remedy 1: Make them match.
Section 14. Troubleshooting Guide include the remote datalogger’s address. Whether you set up a beacon or Neighbor Filter make sure the port so configured matches the communications device port configuration. For example, if the selected neighbor filter port is “17”, make sure that the RF400 Active Interface is “CSDC 7.” Possible reason 3: An RF400 Series radio is set to a different Hopping Sequence, Network Address, Radio Address, or Standby Mode.
Section 14. Troubleshooting Guide 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. Remedy: Change Master *D15 settings for max nodes, max neighbors, and max routers to larger numbers reflecting the network size. *D15 settings allocate memory similar to *A.
Section 14.
Appendix A. Glossary of Terms A 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.
Appendix A. Glossary of Terms Cancel – Choosing Cancel from a dialog box will typically ignore any changes made and close the box. Carrier – An electrical signal used to convey data or other information. For example, radio and phone modems use carrier signals. Phone modems attempt to detect carrier when the call is placed. The red LED on the RF95T lights when the modem detects a carrier. Child Node – See Node. A node that is accessed through another device (parent node).
Appendix A. Glossary of Terms D Data Advise (Datalogger) – A mutual agreement between the communication server and the datalogger about which tables are to be collected every time the datalogger is contacted. Based on the dataloggers table definitions. Data Advise (Server) – an agreement between a client application and the communication server to provide specified data as it is collected by the server. Data Advise Notification – The packet of data sent by the datalogger based on the Data Advise agreement.
Appendix A. Glossary of Terms E 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 – Any of the dataloggers, 21X, CR7, CR10, CR500, CR10X, CR510, or CR23X. The default operating system for these dataloggers is a mixed-array configuration.
Appendix A. Glossary of Terms G Ground Connection – Most sensors require one or more ground connections in addition to excitation or signal inputs.
Appendix A. Glossary of Terms Intermediate Storage – Datalogger memory used to temporarily store values (such as a running total and number of samples for an average calculation), typically to be used for output calculations. The datalogger uses Intermediate Storage to accumulate sensor readings until output. L Link – Communications route between two devices, for example the phone link between two phone modems.
Appendix A. Glossary of Terms Modem – From “modulator-demodulator”; a device used to transmit and receive digital data over normally analog communications lines, such as an audio signal on telephone circuits. A modem attached to a computer performs a digital-to-analog conversion of data and transmits them to another modem that performs an analog-to-digital conversion which permits its attached computer to use the data.
Appendix A. Glossary of Terms P 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.
Appendix A. Glossary of Terms PROM – Programmable Read-Only Memory ─ integrated circuit chips that are used to store the Operating System (OS) in the CR10T datalogger and some other communications peripherals. The PROM can be replaced to install a new operating system (also see EEPROM). Pulse Channel – Some sensors output voltage pulse signals. Such sensors can be connected to Pulse Channels for measurement (labeled as P1, P2, etc., on the datalogger’s wiring panel).
Appendix A. Glossary of Terms RTMS – Real-Time Monitoring Software. A software application designed by 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. S Scan Interval – See Execution Interval. SDI-12 – SDI-12 stands for Serial Digital Interface at 1200 baud.
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. Storage – An entry in the status table that shows the number of final storage locations available.
Appendix A. Glossary of Terms V 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. CRBasic dataloggers use variables for all measurements, processing values, including variables to be used in Boolean form as “high” or “low”.
Appendix B. Campbell Scientific File Formats Campbell Scientific, Inc. uses different formats for data in datalogger memory, external PC cards, datalogger communication software, and 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. B.
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. • Data from multiple arrays can be included in the file. • A two-digit column number and sign precede each value in a column. An example of a printable ASCII file: 01+0112. 01+0115. 09+0.0000 01+0108. 01+0112. 01+0115. 09+0.0000 02+2002. 02+2002. 10+0.
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.
Appendix B. Campbell Scientific File Formats B.1.4 TOA5 TOA5 is a text-based file format similar to TOACI1 but with additional information in the header. This format has the following features: • Contains a text header that provides the following information: • The file format type, the station name, the datalogger type, the serial number, the OS version, the DLD name, the DLD signature, and the table name. • The field name for each of the data values. (See TABLE B- for field name suffixes.
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).
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. B.1.6 Array Compatible CSV This file format can be used to product output files from table data dataloggers that are similar to those created by mixed array dataloggers.
Appendix B. Campbell Scientific File Formats 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. Every element must have a name and can optionally have a set of attributes which are a collection of name/value pairs where the name is unique.
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. In addition, they offer an excellent tutorial at http://www.w3schools.com/xml/default.asp. B.1.7.
Appendix B.
Appendix B.
Appendix B. Campbell Scientific File Formats 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. These elements include the following: station-name ─ Specifies the name of the station that generated the data. This element must be present. table-name ─ Specifies the name of the table as given in the datalogger program. This element must be present.
Appendix B. Campbell Scientific File Formats xsd:short 16 bit signed integer xsd:unsignedShort 16 bit unsigned integer xsd:byte 8 bit signed integer xsd:unsignedByte 8 bit unsigned integer xsd:float 32 bit floating point number xsd:double 64 bit floating point number xsd:boolean Boolean value xsd:dateTime date and time stamp units This optional attribute will specify the units string provided by the datalogger program.
Appendix B.
Appendix B. Campbell Scientific File Formats 2006-08-16T06:13:46 52.5 2006-08-16T22:20:10 32.15 2006-08-16T10:19:42 30.34 2006-08-16T15:37:33 10.06 2006-08-16T05:25:24 84.6 2006-08-16T04:26:52 13.21 2006-08-16T17:28:53 11.86 2006-08-16T14:34:31 217.
Appendix B. Campbell Scientific File Formats B.1.8.2 File Syntax CSIJSON contains two subordinate objects: “head” and “data”. The head object contains the station meta-data and field descriptions while the data object is an array of record objects. B.1.8.2.1 The head Object The head object contains information about the datalogger and program that is responsible for generating the data as well as information about the fields in the data. B.1.8.2.1.1 head.
Appendix B. Campbell Scientific File Formats B.1.8.2.1.3 head.environment Object The environment object contains information about the datalogger and its program and the data table. 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. B-16 table_name Specifies the datalogger table name. model Specifies the model of the datalogger that produced this data. This object is optional.
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. Each field description object will contain the following objects: name Specifies the name of the field as assigned by the datalogger program. Specifies the expected data type for this field.
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: no An integer that specifies the record number as assigned by the datalogger. time Specifies the time stamp assigned by the datalogger. vals An array of the data values for this record. Each element in this array must correspond with the equivalent element in the head.fields array. B.1.8.
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.
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 ASCII Header Line 4 ASCII Header Line 5 ASCII Header Line 6 Frame Header Frame Body n Frame Footer Header line one describes the file environment with the following fields: • Data file type (TOB2 or TOB3). • Station name. • Model name of the datalogger.
Appendix B. Campbell Scientific File Formats Header line five describes the processing performed in the datalogger to produce the value for each field in the record; for example, sample, average, min, max, etc. If there is no known processing for a field, that field will be assigned an empty processing string. There will be one value on this line for each field name given on header line three.
Appendix B. Campbell Scientific File Formats B.4 Converting Binary File Formats Campbell Scientific dataloggers not only use the previously mentioned binary file formats but users may also choose to use and access these binary formats on the 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.
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.
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.
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.
Appendix C. Table-Based Dataloggers NOTE Event driven tables should have a fixed size rather than allowing 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.
Appendix C. Table-Based Dataloggers will calculate the amount of memory for the table based on the execution interval. The CR200 Series dataloggers have a Public table in which the current scan’s measurements are held. However, the CR200 Series does not have the ability to store multiple programs and program processing takes place in a linear fashion, similar to the TD family of dataloggers (e.g.
Appendix C. Table-Based Dataloggers 6. Check the Options | DLD File Labels setting to ensure the “Include first ___ Input location labels” field is not set to 0 if the option is selected. 7. Save and compile the program, correcting any errors that may be found by the compiler. C.2.2 Program Instruction Changes Several programming instructions have changed or are not used in table-based datalogger programs.
Appendix C. Table-Based Dataloggers • 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. This instruction is not included in the tablebased programming instructions. • Instruction 98, Send Printer Character – Instruction 98 is used to send characters to either an addressed or pin-enabled printer. This instruction is not included in the table-based programming instructions.
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” in the data table. This hourly table would then be organized as follows: DATE_TIME RECORD # TEMP1 2002-01-27 10:00:00 14 23.5 2002-01-27 11:00:00 15 24.2 TEMP2 24.
Appendix C. Table-Based Dataloggers • 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. TABLE C-1. Example of Status Table below describes typical fields that are given in the Status table. Not all fields will be present or applicable for all dataloggers. See the datalogger operator’s manual for specifics. TABLE C-1.
Appendix C. Table-Based Dataloggers TABLE C-1. Example of Status Table Entries (CR10T) C-8 Battery Current value of the battery voltage. This measurement is made in the background calibration. PanelTemp Current Panel temperature measurement. LithiumBattery A Boolean variable signaling “True” (–1) if the lithium battery is OK and “False” (0) if not. The lithium battery is loaded and a comparator checked every 4 seconds to verify that the battery is charged.
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. MeasureOps This is the number of task sequencer opcodes required to do all measurements in the system. This value includes the Calibration opcodes (compile time) and the system slow sequence opcodes.
Appendix C. Table-Based Dataloggers TABLE C-1. Example of Status Table Entries (CR10T) C-10 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.
Appendix D. Software Organization D.1 LoggerNet/Client Architecture The LoggerNet communication server provides the interface to all of the dataloggers and the support for the different communications mediums. It runs in the background and provides an attachment for the clients that provide the user interface. The server handles all communications with the dataloggers.
Appendix D. Software Organization the last poll. The tables to be collected are specified by the user in the Setup Screen. As each record is written to the data cache, the server adds a filemark number to the record as it is stored. This filemark number is used to identify discontinuities in the data. The filemark number starts out as zero when the table for the data cache is created or re-initialized. This number is incremented each time a discontinuity is seen in the data records.
Appendix D. Software Organization 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. D.3.1 C:\CampbellSci Directory (Working Directory) When LoggerNet is installed, several directories are created under the C:\CampbellSci directory.
Appendix D. Software Organization application (such as the *.SCW program file for Short Cut for Windows). The client applications are each given their own directories so that if more than one 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.
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. They can also be saved to disk and opened in a text editor.
Appendix E. Log Files E.1.2 Enabling Log Files Use LogTool (Options |Log File Settings) to enable logging of events to files. If enabled, the server will write log records to text files in the log file directory using the following file names (depending on the log type): • Transaction Log – TranX.log • Communications Log – CommsX.log • Object State Log – StateX.log • Low Level Log – IOXSerial Port_1.log where “X” is “$” for the currently active file and 0, 1, 2, etc. for archived files.
Appendix E. Log Files E.1.3.2 Transaction Log Format Each record in the transaction log includes at least two fields in addition to the timestamp and device name: Message Type Code – Identifies the type of event that has occurred. This is a number that corresponds to the description immediately following. If this log is being read by a software program, a number is very easy to use for comparison when looking for specific message types. Message Type Description – Text that describes the message type code.
Appendix E. Log Files TABLE E-1. Transaction Log Messages E-4 Code 8 Message Text Security database read failed Message Parameters 9 Modem default database read failed When the server started up it could not read the default modem file wmodem.ini. 10 Modem custom database read failed 11 Clock check started 12 Clock set 13 Clock checked 14 Clock check failed When the server started up it could not read the user customized modem settings file wmodem.cust. A clock check has been initiated.
Appendix E. Log Files TABLE E-1.
Appendix E. Log Files TABLE E-1. Transaction Log Messages Code 24 Message Text Hole collect response received 25 Hole collect failed 26 Data polling started Data polling complete Data polling failed Data collection by polling started. Data collection by polling completed Data collection by polling failed due to communication failure or a timeout. Directed data query start Directed data query continue A user initiated query has been started.
Appendix E. Log Files TABLE E-1. Transaction Log Messages Code 36 Message Text Logger table definitions have changed 37 Updating BMP1 network description 38 BMP1 network description update complete BMP1 network description update failed 39 Message Parameters 40 Datalogger message Severity (S for Status, W for Warning, F for Fault); Message text.
Appendix E. Log Files TABLE E-1. Transaction Log Messages Code 44 45 E-8 Message Text Terminal emulation transaction complete Terminal emulation transaction failed 46 Set variable started 47 Set variable complete 48 Set variable failed 49 Table resized 50 Program file send start 51 Program file send status 52 Program file send complete 53 Program file send failed Message Parameters Message Meaning Terminal emulation response message has been received from the datalogger.
Appendix E. Log Files TABLE E-1. Transaction Log Messages Code 54 Message Text Program file receive start 55 Program file receive status Program file receive complete 56 57 Program file receive failed 58 Collection schedule: normal 59 Collection schedule: primary retry 60 Collection schedule: secondary retry 61 Collection schedule suspended Message Parameters Message Meaning The server is requesting the datalogger program. The actual program segments will appears as BMP1 message type 5.
Appendix E. Log Files TABLE E-1. Transaction Log Messages E-10 Code 62 Message Text Primary retry collection attempt failed Message Parameters Message Meaning Data collection on the primary data collection interval failed. 63 Secondary retry collection attempt failed Data collection on the secondary data collection interval failed. 64 Device restore from file succeeded 65 Device restore from file failed On server startup a device previously entered in the network map has been restored.
Appendix E. Log Files TABLE E-1.
Appendix E. Log Files TABLE E-1.
Appendix E. Log Files TABLE E-1. Transaction Log Messages Code 85 Message Text Data restore failed Message Parameters Message Meaning On server startup the data broker data storage area could not be created.
Appendix E. Log Files TABLE E-1. Transaction Log Messages Code 93 Message Text Collect area poll data Message Parameters Collect area name 94 Collect area polling complete Collect area name 95 Collect area polling failed Collect area name 96 Scheduled polling begun Scheduled polling succeeded Scheduled polling failed Scheduled data collection has started. Scheduled data collection has completed. Scheduled data collection failed.
Appendix E. Log Files TABLE E-1.
Appendix E. Log Files TABLE E-1.
Appendix E. Log Files TABLE E-1. Transaction Log Messages Code 108 Message Text Table reset Message Parameters The name of the table that was reset; The account name of the logged in client 109 Collect schedule reset The account name of the logged in client 110 Collect area setting changed 111 PakBus route added The name of the collection area; The setting identifier for the setting that was changed; The new value of the setting; The account name of the logged in client.
Appendix E. Log Files Transaction Log Example "2009-04-15 16:41:05.367","CR1000","11","Clock check started" "2009-04-15 16:41:05.429","CR1000","13","Clock checked","2009-04-15 16:41:33.44","2009-04-15 16:41:05.421","-28" "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.
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.
Appendix E. Log Files TABLE E-2. Communication Status Log Messages Message Text PakBus framing error Invalid low level signature Provider opened Device dialed Provider closed Unable to Locate Serial synch byte E-20 Message Meaning LoggerNet received data from the link that cannot be verified to be part of a PakBus packet. The packet received from the device got corrupted and the packet signature doesn’t match the packet contents. The serial communications port has been initialized.
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 – Any extra information associated with the event. Object State Log Example "2009-04-15 16:41:05.351","CR1000","starting BMP5 operation","manage comm resource" "2009-04-15 16:41:05.
Appendix E. Log Files E.2 CQR Log (RF Link) The CQR log contains information about the quality of communication each time an 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 \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.
Appendix F. Calibration and Zeroing F.1 Calibration Essentials F.1.1 Definition of Calibration Calibration, in general, refers to actions taken on a measurement system to increase its accuracy. This is usually done by matching the system’s outputs to known “control” values in order to increase confidence in the measurement of future unknowns.
Appendix F. Calibration and Zeroing F.2 Writing Calibration Programs with the CRBasic Editor F.2.1 The FieldCal Instruction 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.
Appendix F. Calibration and Zeroing program start or under other conditions, use the LoadFieldCal instruction. To store calibration values to a data table (in addition to the values stored in the *.cal file), use the SampleFieldCal table output instruction with the NewFieldCal system variable as the trigger. For more information about how to use these instructions, refer to the FieldCal instruction topic of your datalogger manual, or use the online help topic for FieldCal within the CRBasic Editor. F.2.
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.
Appendix F. Calibration and Zeroing those two conditions. For future measurements (unknowns), a linear response will be used based on the line defined by those two points. To perform a two-point multiplier and offset calibration, use an argument of 2 (the number two) for the calibration type in the FieldCal instruction of your CRBasic program. The Calibration Wizard can be used to calculate and apply the two different known conditions while the program is running in the datalogger. F.3.
Appendix F.
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): 1. Ensure the status (value of the mode variable) is 0 or 6 before you start. a.
Appendix F. Calibration and Zeroing 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. The user only needs to set the sensors to the known value(s), and provide a few required inputs to the Wizard.
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. Any items that have been aliased (i.e.
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. The word Calibrating will be visible in the Current Value box until that process is complete.
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. NOTE The steps for performing a two-point slope only (multiplier only) calibration in the Wizard are nearly identical to those shown above for a two-point multiplier and offset calibration.
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. Now you can monitor the reading on the sensor to be calibrated. Set the sensor to the zero condition, and press Calibrate.
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.
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. Press Calibrate. The current value will show Calibrating until the process is complete. You will then have the opportunity to press Finish, or press Previous to return and calibrate more sensors.
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. It functions in a similar manner to the FieldCal instruction, but has additional arguments to meet the specialized needs for shunt and strain gauge calibrations.
Appendix F.
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. Excel will recognize the file as not being in an xls format, and will invoke the Text Import Wizard. The Text Import Wizard consists of three steps, each having its own window. G.
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. From the Text Qualifiers list box, select None. Select the Next button.
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.
Appendix G.
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. From the Text Qualifiers list box, select None. Select the Next button.
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. To complete the import, select the Finish button. As imported, the Date and Time fields have a quotation mark in the field.
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. If headers have been imported with the data, the column headings will be off by one since the date and time have been imported as two separate fields.
Appendix G.
Campbell Scientific Companies Campbell Scientific, Inc. (CSI) 815 West 1800 North Logan, Utah 84321 UNITED STATES www.campbellsci.com • info@campbellsci.com Campbell Scientific Centro Caribe S.A. (CSCC) 300 N Cementerio, Edificio Breller Santo Domingo, Heredia 40305 COSTA RICA www.campbellsci.cc • info@campbellsci.cc Campbell Scientific Africa Pty. Ltd. (CSAf) PO Box 2450 Somerset West 7129 SOUTH AFRICA www.csafrica.co.za • cleroux@csafrica.co.za Campbell Scientific Ltd.
