PC400 User’s Manual Version 4.2 Revision: 9/13 C o p y r i g h t © 1 9 9 9 - 2 0 1 3 C a m p b e l l S c i e n t i f i c , I n c .
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. 1. Introduction ..............................................................1-1 1.1 PC400 Overview .............................................................................. 1-1 1.1.1 Main Screen .............................................................................. 1-1 1.1.2 Clock/Program and the EZSetup Wizard ....................
Table of Contents 4.5.2.4 File Control for CR5000, CR800, CR1000, CR3000, and CR9000 Dataloggers ........................... 4-12 4.5.2.5 Terminal Emulator........................................................ 4-17 4.5.3 Network Menu......................................................................... 4-18 4.5.3.1 Add/Delete/Edit/Rename Datalogger ........................... 4-18 4.5.3.2 Backup/Restore Network.............................................. 4-19 4.5.3.
Table of Contents 5.6 Running Split from a Command Line ............................................ 5-47 5.6.1 Splitr Command Line Switches .............................................. 5-47 5.6.1.1 Closing the Splitr.exe Program After Execution (/R or /Q Switch) ...................................................... 5-47 5.6.1.2 Running Splitr in a Hidden or Minimized State (/H Switch) ............................................................... 5-47 5.6.1.
Table of Contents 7.2 7.3 7.4 7.5 7.6 Creating a Program Using Short Cut................................................ 7-2 7.2.1 Step 1 – Create a New File or Open Existing File..................... 7-2 7.2.2 Step 2 – Select Datalogger and Specify Scan Interval .............. 7-3 7.2.3 Step 3 – Choose Sensors to Monitor ......................................... 7-6 7.2.4 Step 4 – Setup Output Tables .................................................. 7-13 7.2.
Table of Contents 8.4.5 Datalogger Serial Port Settings ............................................... 8-24 8.4.6 PakBus Settings ...................................................................... 8-24 8.4.6.1 Network........................................................................ 8-24 8.4.6.2 Beacon Intervals........................................................... 8-25 8.4.6.3 Neighbor Filter ............................................................. 8-25 8.4.6.
Table of Contents 10. Utilities ................................................................... 10-1 10.1 CardConvert ................................................................................... 10-1 10.1.1 Input/Output File Settings ....................................................... 10-1 10.1.2 Destination File Options.......................................................... 10-2 10.1.2.1 File Format ................................................................... 10-2 10.1.2.
Table of Contents C.1.2.3 C.1.2.4 Communications Status Log Format ............................C-15 Object State Log Format ..............................................C-17 Tables 5-1. 5-2. 5-3. 5-4. 5-5. 5-6. 5-7. 5-8. 5-9. 8-1. 8-2. 9-1. 9-2. 9-3. 9-4. B-1. C-1. C-2. Comma Separated, Field Formatted, Printable ASCII, and Table Oriented ASCII Input File Format Types ..................................... 5-8 Example of Event Driven Test Data Set ........................................
Table of Contents viii
Section 1. Introduction PC400 is a software application used to set up, configure, and retrieve data from Campbell Scientific dataloggers. This software application runs on Windows XP, Windows Vista, and Windows 7 platforms. PC400 software supports programming, communication, and data collection for the “CRBasic dataloggers”, including the CR200/205, CR800, CR1000, CR3000, CR5000, and CR9000.
Section 1. Introduction enter settings for dataloggers. Once a datalogger is added to the list, you can choose the Edit button to change those settings, again with the EZSetup Wizard. Progress through the wizard is shown on the left side of the screen, with steps for choosing a datalogger, defining the communications path between the computer and the datalogger, fine tuning settings for the datalogger (e.g.
Section 1. Introduction 1.1.7 CardConvert CardConvert is a utility to retrieve binary data from Compact Flash cards containing CR1000 or CR3000 data, and convert the data to an ASCII file. 1.1.8 Short Cut Short Cut is a datalogger program “generator.” You only need to select the datalogger type, sensors, and desired outputs, and then Short Cut creates the program file to send to the datalogger. Users don’t need to learn about the individual programming instructions.
Section 1. Introduction You can also now continue an instruction onto multiple lines by placing the line continuation indicator (a single space followed by an underscore “_”) at the end of the each line that is to be continued. Also, bookmarks in a CRBasic program are now persistent from session to session. The Device Configuration Utility has a new off-line mode which allows you to look at the settings for a certain device type without actually being connected to a device.
Section 1. Introduction 1.3 Getting Help for PC400 Applications Detailed descriptions of each application and tool are included in later sections of this manual. Each application also has its own built-in help system. Context sensitive help for an application can usually be accessed by moving the focus to (clicking on) a particular item and pressing the F1 key or by selecting Help from the application’s menu.
Section 1. Introduction among items on a screen and pressing the Enter key to execute the button function. Right Click Menus – Some areas have pop-up menus that bring up frequently used tasks or provide shortcuts. Just right click on an area and if a menu appears, left click the menu item you want. Hot Keys or Keyboard Shortcuts – Many of the menus and buttons can be accessed using Hot Keys. An underlined letter identifies the hot key for a button or function.
Section 2. System Requirements 2.1 Hardware and Software PC400 is an integrated application of 32-bit programs designed to run on Intelbased computers running Microsoft Windows operating systems. Recommended platforms for running PC400 include Windows XP, Windows Vista, or Windows 7 because they offer the most stable operating environments. PC400 also requires that TCP/IP service be installed on the PC.
Section 2.
Section 3. Installation, Operation and Backup Procedures 3.1 CD-ROM Installation The following instructions assume that drive D: is a CD-ROM drive on the computer from which the software is being installed. If the drive letter is different, substitute the appropriate drive letter. 1. Put the installation CD in the CD-ROM drive. The install application should come up automatically. Skip to step 3. 2. If the install does not start, then from the Windows system menu, select Start | Run. Type “d:\setup.
Section 3. Installation, Operation and Backup Procedures 3.2.1.2 Working Directories In this version of PC400, each major application keeps its own working directory. The working directory holds the user files created by the application, as well as configuration and initialization (*.INI) files. This scheme was implemented because we use the underlying tools and many of the applications (the server itself, library files, datalogger program editors, etc.) in a number of different products.
Section 3. Installation, Operation and Backup Procedures the computer suffers some other hardware failure that prevents access to the stored data on the disk. The maximum interval for backing up data files depends primarily on the amount of data maintained in the datalogger memory. The datalogger’s final storage is configured as ring memory that will overwrite itself once the storage area or table is full.
Section 3. Installation, Operation and Backup Procedures 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. If a file does get corrupted, all of the server’s working files need to be restored from backup to maintain the synchronization in the server state. 3.2.
Section 4. The PC400 Main Screen This section provides an overview of PC400, a detailed description of the communications tabs and pull-down menus of the PC400 Main Screen, and an overview of PC400’s troubleshooting tools. 4.1 Overview To start PC400 go to the start menu of the computer and select the PC400 icon under Start | Programs | Campbell Scientific | PC400. You can alternatively use the shortcut on the desktop if you elected to create one during the installation process.
Section 4. The PC400 Main Screen PC400 supports the CRBasic series of dataloggers, including the CR200/205, CR800, CR1000, CR3000, CR5000, and CR9000. PC400 also supports the Edlog dataloggers (CR500, CR510, CR10, CR10X, 21X, CR23X, and CR7 dataloggers) using any of their mixed-array, table-data, or PakBus operating systems. PC400 supports one medium of communications for any given datalogger.
Section 4. The PC400 Main Screen The EZSetup Wizard starts as shown below. Previous and Next buttons are provided to move through the wizard. Progress is shown by the blue arrow next to each step displayed at the left. Help is available from the Help button as well as the text displayed on the right side of the screen itself. In Communication Setup you select the datalogger type and give it a name that will also become the default file name for data files collected from that datalogger.
Section 4. The PC400 Main Screen The Send Program step allows you to send a program to the datalogger. This may be a program you created with Short Cut, Edlog or the CRBasic Editor or a program supplied by someone else. If it is a mixed-array datalogger, and the datalogger is already running a program when you first connect to it, you should associate the .DLD file so that PC400 will use the labels for input locations and final storage.
Section 4. The PC400 Main Screen PC400 can also display final storage values. For mixed-array operating systems in the CR10X family of dataloggers, these values will be displayed only if the final storage data was collected from the datalogger, and only the most recent values actually collected will be displayed. An example from a CR10X-based weather station is below.
Section 4. The PC400 Main Screen In the case of table-based dataloggers, PC400 will display the last record from a final storage table and will automatically update these records as they are stored in the datalogger’s memory. Note that PC400 does not automatically collect this data to the data file. If you want a permanent record of the data, you must collect it manually from the Collect Data tab.
Section 4. The PC400 Main Screen Program variables that are declared as Boolean can also be placed on this display, for dataloggers that support data types. For these dataloggers, an Add button is available that, when pressed, lists all of the tables in the datalogger. When a table is highlighted on the left side of the window, any variables that are declared as Boolean in the program will be displayed on the right side of the window.
Section 4. The PC400 Main Screen NOTE Note that 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 4. The PC400 Main Screen Example of a Collect Data tab for a table-based CR1000: In either case, once a final storage area or table is selected you may either collect the new data since the last time you collected it with PC400, in which case PC400 appends the new data to the file if it exists, or you may collect all of the data from that final storage area or table, in which case any file with the same name is replaced.
Section 4. The PC400 Main Screen NOTE Available language packages are provided by Campbell Scientific’s international representatives or on the CSI website. They are not included in a standard PC400 installation. 4.5.2 Datalogger Menu 4.5.2.1 Connect/Disconnect This option provides the same function as the Connect/Disconnect button on the main toolbar. 4.5.2.
Section 4. The PC400 Main Screen The Station Status window is shown below: The window has three tabs. The Summary tab provides an overview of important status information in the datalogger, including the information about the datalogger model and its firmware, program details, program errors, battery voltage levels, and card memory (if one is present). NOTE Only the Summary tab is available for array-based dataloggers.
Section 4. The PC400 Main Screen NOTES No Table Fill Time Statistics will be shown for a CR200-series datalogger, because they cannot be calculated for this datalogger. For the CR10XTD, CR10XPB, CR510TD, CR510PB, CR23XTD, and CR23XPB, the Time of Fill will not be shown and you will not have the option to Reset Tables. Resetting a table will erase the data in the datalogger and in the data cache. The Status Table tab lists all of the status table fields in the datalogger along with their values.
Section 4. The PC400 Main Screen The File Control window displays a list of files stored on the datalogger’s CPU, PC card, SC115 USB drive, or USR drive. The window on the left lists all of the data storage devices available for the selected datalogger (CPU, CRD, USB, or USR). Selecting a device shows a list of the files stored there. NOTE The USR drive is a user-created drive in the CR800, CR1000, and CR3000 dataloggers.
Section 4. The PC400 Main Screen chosen to send to the highlighted device. If the Set Run Options on Send check box is selected, you will be asked to specify the Run Options for the file being sent as described below under Run Options. Datalogger programs, data files, and other ASCII files can be sent to the datalogger. Format is used to format the selected device. Just like the formatting a disk on a computer, all of the files on the device are deleted and the device is initialized.
Section 4. The PC400 Main Screen 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). CAUTION Neither of these options affects existing data files on a card if one is being used.
Section 4. The PC400 Main Screen When Run Now is checked, the program is compiled and run in the datalogger. All data tables on the CPU are erased. You have the option of whether or not to erase data files stored on a card. Run On Power-up The file will be sent with the Run On Power-up attribute set. The program will be run if the datalogger loses power and then powers back up. Run Always Run Now and Run On Power-up can both be selected.
Section 4. The PC400 Main Screen Select the option to stop the program and retain the data files, or to stop the program and delete data files. The option to retain or delete data files includes those in internal datalogger memory and those on a card written by the CardOut instruction. In most cases, data written to a card using the TableFile instruction will not be erased.
Section 4. The PC400 Main Screen Selecting a device and baud rate, and then clicking Open Terminal causes PC400 to attempt to connect with that device. If the device is a datalogger, PC400 will call the datalogger over whatever communications link has been established and will attempt to get a prompt from that datalogger. If the device is a root device, such as a serial or COM port, PC400 simply opens that port at the specified baud rate. Terminal Emulator has several uses.
Section 4. The PC400 Main Screen 4.5.3.2 Backup/Restore Network This function can be used to save a copy of the network map to a file, and then to restore the network if necessary. The settings for all the devices in the network will be saved. A default is given for the directory and file name to be used for the backup or restore.
Section 4. The PC400 Main Screen 4.5.4.2 Options The following two options can be set: 1) Automatically Check Datalogger Status – This option allows you to determine when the datalogger status is automatically checked. The options include After Connection, After Program Send, and/or On Interval.
Section 4. The PC400 Main Screen On the left side of the LogTool window, is a display of all devices known to PC400. You can choose to show all messages or filter them to show only certain devices or dataloggers. PC400 will also store these messages to log files on the PC’s hard drive and will eventually overwrite these files to keep them from growing forever. You can control the number and size of each log file type with the Options | Log File Settings menu and dialog.
Section 4. The PC400 Main Screen 4.5.4.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. If the PakBus ports set up in the software have been bridged, the resulting single port will be named “__global__”.
Section 4. The PC400 Main Screen 4.5.4.4.2 Dynamic and Static Links There are two types of links to PakBus dataloggers that the server recognizes: static links and dynamic links. Static links (depicted using red lines) are the communication links to dataloggers that have been set up in the software, but which have not been confirmed by communicating with the datalogger(s). You will see these dataloggers listed in the software’s network map.
Section 4. The PC400 Main Screen devices can be unlocked by selecting View | Unlock All Positions from the menu. 4.5.4.4.5 Discovering Probable Routes between Devices You can view the probable route that communication will take between two PakBus devices by sequentially clicking on the two devices in PakBus Graph. The probable communication route will be highlighted in cyan.
Section 5. Split Split is a tool that works with output data files (*.dat) collected from Campbell Scientific dataloggers. It is used to post-process data from either mixed-array or table-based dataloggers. Split can create reports based on collected data by filtering data based on time or conditions. It can generate statistics, perform calculations, reformat files, check for data quality (limit testing), and generate tables with report and column headings.
Section 5. Split 5.2 Getting Started The most common use of Split is to separate array data collected on a particular interval from a data file containing data output at several different intervals. In the following example, hourly data are split from a data set that contains 15 minute, hourly and daily data. The data was collected from BirchCreek, a CR10X datalogger. The CR10X was loaded with a program created by Edlog named Birch.dld.
Section 5.
Section 5. Split 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 5. Split 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 5. Split 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 5. Split For table based data files the timestamp is normally the first column and is a quoted text string ("2002-02-26 10:30:00"). To display these timestamps in the output you will need to change the column width for the first column to at least 24. If the column width is too small to accommodate the value output, the string will be highlighted in red and preceded by an asterisk, with the words “Bad Data” in the lower right corner when the file is processed. To run Split, select RUN | GO.
Section 5. Split 5.3 Split Parameter File Entries 5.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). If the input file is not in the default directory, use the Browse button to find the input file.
Section 5. Split PRINTABLE ASCII 01+0115 01+0115 01+0115 01+0115 02+0189 02+0189 02+0189 02+0189 Element 1 Element 2 Element 3 Element 4 Element 5 Element 6 Element 7 = = = = = = = 03+1200 03+1300 03+1400 03+1500 04+089.6 04+091.3 04+092.7 04+094.1 05+055.3 05+061.5 05+067.7 05+069.0 06+25.36 06+27.25 06+15.15 06+20.35 07+270.0 07+255.4 07+220.1 07+260.6 Output Array ID# (115) Julian day (189) hour, minute average temperature in deg. F average soil temperature in deg.
Section 5. Split • Reading Data in Final Storage (Binary) Format If the data is in binary format and Start and Stop Offsets are used, Final Storage (Binary) Format must be selected in the File Info field. This tells Split that the file must be decoded as Final Storage before counting the bytes. If Offsets are not used, Auto Detect may be chosen and the file will be processed correctly. 5.3.1.2 File Offset/Options Start Offset None Select his check box to start reading the input file from the beginning.
Section 5. Split CAUTION When using the Last Count option, if the Start and Stop Conditions are specified, they must exist in the newly appended data or Split will never begin execution. Because Last Count keeps track of the number of bytes in the file, if you delete data from the beginning of a file, Last Count will not work properly. Specific By selecting the Specific option and entering a number, Split will “seek” that position in the file.
Section 5. Split 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 5. Split Time Offset This field specifies a time offset, in seconds, that should be applied to each item on the Select line that uses the Date or Edate function to output a date. The offset can be positive or negative. Each input file can have its own offset (or no offset) for its Select line. 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”.
Section 5. Split NOTE Table data files contain the time and date as a single quoted string at the beginning of each data record. Split handles the dates as long as you include a colon separator as a placeholder for each of the fields in the timestamp.
Section 5. Split 5.3.1.3.1 Starting Relative to PC Time Split has the ability to start relative to the current PC TIME (computer time). This feature allows a .PAR file to be run on new data files without changing the Start Conditions, provided the Input Data File is collected at a fixed interval and Split is run at a fixed interval. For example, the same PAR file could be run every day to display the last 48 hours of data without changing the start conditions.
Section 5. Split CAUTION Split will not start reading if the exact specified starting time cannot be found, unless you enable the “Start-Stop On/After Time” feature. The interval (5 minutes, 60 minutes, and 5 seconds in the examples above) must be evenly divisible into 60 minutes. NOTE • If the start time is a certain number of days prior to the PC time, the file will be processed beginning at midnight of the day specified.
Section 5. Split As an example, let’s look at a vehicle test application. The start of the test is when the vehicle is turned on, and the end of the test is when the vehicle is turned off.
Section 5. Split Consider TABLE 5-2 below: TABLE 5-2. Example of Event Driven Test Data Set 100,12.1,10.,32.6 101,92.7,67.7 102,56.1,48.7,98.,220.1 200 100,12.5,9.89,30.1 102,56.2,50.,100.5,210.6 200 100,13.1,10.1,33.1 101,94.1,69 200 Data from arrays output during the first test. Second test. Third test. This table contains four different output arrays: 100, 101, 102, and 200.
Section 5. Split TABLE 5-3. Processed Data File Using Option C 100 100 100 12.1 12.5 13.1 10 9.89 10.1 32.6 30.1 33.1 101 92.7 67.7 101 94.1 69 102 102 56.1 56.2 48.7 50 98 100.5 220.1 210.6 When Split is run, the resulting data file will look similar to TABLE 5-3. Each line of data represents one test. Notice that blanks were inserted if the data set (conditional array) did not exist. 5.3.1.4.
Section 5. Split TABLE 5-4. Input File Entries to Process the First Data Point for each Test First Input File = DATA_1.DAT:1 Stop Condition = F,1[200] Select = AVG(2) 5.3.1.5 Copy The Copy Condition tells Split which arrays should be used for the output data. After the Start Condition is satisfied, and before the Stop Condition is met, the Copy condition must be satisfied before any data will be processed according to Select line instructions.
Section 5. Split Array-based With an entry of 1[30] and 2:3:4[600..1200]: in the Copy condition, Split will only process the data file when the time is between 6:00 a.m. and 12:00 p.m. (This assumes 2 is the year element, 3 is the day element, and 4 is the hour/minute element.) NOTE Time ranges cannot be used with the time-sync function. 5.3.1.6 Select The Select line specifies which elements of an Output Array are selected for processing and/or output to the specified Output File.
Section 5. Split TABLE 5-5.
Section 5. Split variable X). A comma must follow each variable statement, as with all parameters in the Select line. Once the variables have been declared they can be used later in the Select line (i.e., x=4-5∗(6∗3.0), y=6/3,2,3,6,7,7∗x,6+y). NOTE Variables can be defined in the first four Input File’s Select lines only, but may be used in subsequent Input File’s Select lines. Illegal operations (e.g., logarithm of a negative number) will cause Split to store blanks for the Output.
Section 5. Split 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 5. Split SpaAvg(x..y) returns the spatial average of elements x through y. Examples: SpaAvg(1..7) = 258.74 SpaAvg(1,4,7) = 122.54 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.
Section 5. Split 3. when an interval count is met When the Trigger on Stop Condition (or F option) is used, any time series data defined in the Select line is output each time the Stop Condition is met. Refer to Section 5.3.1.4.2, Trigger on Stop Condition (F Option) Output of Time Series, for more information on the Trigger on Stop Condition. Results which are output at the end of a file or a range of data are referred to as Final Summaries.
Section 5. Split Mt. Logan Weather Data Day 178 178 178 178 178 178 178 178 178 178 178 178 178 178 178 178 178 178 178 178 178 178 178 179 Time 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500 1600 1700 1800 1900 2000 2100 2200 2300 0 Airtemp deg F 58.56 57.48 56.85 56.55 56.57 55.33 55.95 58.12 59.79 61.09 61.34 60.61 61.01 60.93 62.3 63.75 66.15 67.33 66.59 64.52 59.84 56.19 55.48 55.22 RH 17.42 17.65 17.76 18.89 19.6 23.32 24.79 23.98 23.46 24.12 25.03 27.46 25.44 25.48 23.79 24.
Section 5. Split NOTE 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. Max(x;n) returns the maximum value of element x over a full data set or every nth value. Examples: Max(5) = 17.12 (max WS for day) Max(5;12) = 10.41 (max WS for 12 hours) 17.
Section 5. Split Smpl(x;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) SmplMax(x;y;n) 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. Examples: SmplMax(5;(3)) = 55.
Section 5. Split 5.3.1.12 Special Functions, Details, and Examples TABLE 5-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 5. Split 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. The label includes anything within the quote marks, the quote marks are not output but must be in the parameter file. The label cannot exceed the width of the output column (default is eight characters).
Section 5. Split 1 2 3 23.98 24.31 37.13 6.588 8.88 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). n is an element containing wind direction. For example, if n = 182, S would be returned in the output file.
Section 5. Split 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”. Both of these are used when processing data from table-based dataloggers so that the timestamps are similar to that of mixed array dataloggers. Hourarray changes a 0000 hourly timestamp to 2400, and dayofyear produces a Julian Day.
Section 5. Split 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. The “No Date Advance” function can be used to stop the date from rolling forward (Other button, No Date Advance check box).
Section 5. Split The following screen shows the output file setup including the column headings and the units.
Section 5. Split 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.45-V)(33-T) where h = Kcal m-2 hr-1 wind chill index v = wind speed in meters/second T = temperature in degrees C Note that at wind speeds between 0 to 4 mph (0 to 1.
Section 5. Split 5.3.1.14 Summary of Select Line Syntax Rules • A fixed numeric value must include a decimal point “.” or be in scientific notation. There are some exceptions to this as noted below. • Scientific notation has the format “mantissa E power of ten” (e.g., 3E5 = 3 x 105). • Element numbers are entered without a decimal point. • Commas separate Select line parameters (e.g., 2,3,(3+4)/3.2,6).
Section 5. Split This function synchronizes according to day, hrmn (hour-minute), and/or seconds. The syntax used to identify the time elements for array data is: ei[day]:ei[hrmn]:ei[seconds] Referring to TABLE 5-1, to identify the day of year for a mixed-array data file, type: 2[189]:: for hrmn type: :3[1200]: and seconds are expressed as: ::4[5] A single colon is assumed to be between day and hrmn (e.g., 2[189]: means day, :3[1200] means hours, and 2[189]:3[1200] means day and hour-minute).
Section 5. Split hour/minute for day 92 starts at 9:30 a.m. The time between the start of the day (0000) and 9:30 a.m. will be considered missing data. Blanks (or the “Replace bad data with” text) and a carriage return line feed will be inserted at the beginning of the PRN file for each “missed” output interval.
Section 5. Split Start Condition 2[-1]:3[50]: Copy Condition 1[106]and3[60,10] Where: element 1 is the array ID element 2 is the Julian day element 3 is the hour/minute The Start Condition directs Split to begin processing data when the time is one day prior to the current PC time and when the hour/minute value is equal to 50. The 1[106] in the Copy Condition specifies the array from which the data should be copied.
Section 5. Split Several output options may be specified to alter the default output to the file. Some are located on the main OUTPUT FILE screen and some are made available by pressing the Other button. 5.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.
Section 5. Split settings and sets the width of individual columns. If this field is left blank, the Default Column Widths field is used. 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.
Section 5. Split 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 5-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 5. Split 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 5. Split 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 5. Split 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 5. Split 5.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. 5.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 5. Split 5.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 5. Split 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” 5.6.3.
Section 5. Split /[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. The two input file names are separated with a comma but no spaces.
Section 5. Split /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 5. Split /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\SplitW\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 6. View After data has been collected from the datalogger, you need a way to analyze that data. View 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. View can also open other CSI file types (*.DLD, *.CSI, *.PTI, *.FSL, *.LOG, *.CR2, *.CR5, *.CR1, *.CR3, *.CR8, *.CR9).
Section 6. View Tile Vertically. This menu option is used for array-based data files where the entire data file and each individual array are opened in separate windows. It rearranges all open, non-minimized data file windows as non-overlapping vertical tiles. This makes them all visible at the same time. Tile Horizontally. This menu option is used for array-based data files where the entire data file and each individual array are opened in separate windows.
Section 6. View 6.3.1 Opening a Data File To open a data file, click the File Open icon or select File | Open from the menu. (TOACI1, TOA5, TOB1, TOB2, and TOB3 data files can be opened with View.) When a file is first opened, it is displayed in the data panel in a tabular format. 6.3.2 Opening Other Types of Files To open a file that is not a data file (*.DLD, *.CSI, *.PTI, *.FSL, *.LOG, *.CRX) select File | Open As Text from the menu. Files opened in this mode cannot be graphed.
Section 6. View 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 6. View appropriate codes in the Derived Date/Time Format field to designate the format of the timestamp. If the first column of data does not contain a timestamp, leave the Has Date/Time Column check box unchecked. You will still be able to import the file into View and view the data. However, you will not be able to graph the data.
Section 6. View 6.5 Data View The initial display for data files in View is as normal text in a grid format. The following figure shows the View main screen with a data file open. 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 *.FSL file is created when a datalogger program is compiled in Edlog or ShortCut.
Section 6. View 6.5.1 Column Size When a data file is opened, the columns are autosized to fit the data. Column sizes can be changed by dragging a column divider bar to the desired location. If column sizes have been changed, they can be returned to the default sizes by selecting View | Autosize Columns from the menu. 6.5.2 Header Information By default, only column names are shown for each column in the data file.
Section 6. View arrangement at any time. Windows can be tiled horizontally as nonoverlapping horizontal tiles by pressing the Tile Horizontally button or choosing Window | Tile Horizontally from the menu. They can be tiled vertically as non-overlapping vertical tiles by pressing the Tile Vertically button or choosing Window | Tile Vertically from the menu. A data window can be moved manually by clicking on the title bar and dragging it to the desired location.
Section 6. View Multiple columns can be added by holding the Ctrl key and dragging the mouse pointer over the column headings. A partial column can be added by dragging the mouse pointer over the desired values. (Note that once a partial column is selected, it can be extended by holding the Shift key and clicking at a point below the current selection. The selection will be extended to that point.
Section 6. View 6.6.5 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. 6.6.6 Graph Cursor Pressing the Graph Cursor icon on the toolbar will show the graph cursor.
Section 6. View 6.6.8 Line Graph Toolbar The Line Graph toolbar includes the following icons: Copy to Clipboard. Places the graphic on the Windows clipboard. It can then be pasted into other applications. Print. Prints the graph. Print options can be set before printing begins. Export. Allows the graph to be exported in a choice of text or graphical formats. Lock Scrolling. Locks and unlocks the scroll bar at the bottom of the graph.
Section 6. View (Independent) When using independent y-axes, the scale shown will apply only to the last-selected trace assigned to that axis. (A trace is selected by clicking on its name in the list above the Edit and Delete buttons.) Undo Zoom. Returns the graph to its original state after zooming. 6.7 Right-click-Menus Right-clicking in View will bring up a short cut menu. The options on this menu will vary depending on whether you right-click on a data panel, graph, or trace as described below. 6.7.
Section 6. View Copy Selection Copies selected text to the Windows clipboard. Add Selections to Graph Adds the data that is currently selected to the graph. Clear All Selections Clears all selections in the data panel. Clear Selection In the data panel, clears the selection with focus. (This is the selection that has the dashed box around it. Left or right-click on a selection to give it focus.) Format Columns This option allows you to format a column in a binary (TOB) or CSIXML file.
Section 6. View Delete Bookmark If the data panel contains one or more bookmarks, hovering over the Delete Bookmark menu item will bring up a list of the current bookmarks. Selecting a bookmark from the list will delete the bookmark. Delete All Bookmarks Deletes all bookmarks from the data panel. View Record Brings up the current record in a Record View window showing each column heading and the data value. (The Record View window can be brought up directly by clicking to the left of the record.) 6.7.
Section 6. View To preview your data before printing, press the Print Preview button or select File | Print Preview from the menu. From Print Preview you can browse among the pages that will be printed and change the paper orientation if desired. You can zoom in on a particular area of the previewed page by leftclicking the page. You can zoom out by left-clicking with the Shift button pressed. You can pan across a page by right-clicking and dragging the page.
Section 6.
Section 7. Generator Short Cut Program Short Cut (also referred to as SCWIN) is an application for generating programs for 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. Short Cut not only generates a program for the datalogger, but also a wiring diagram that can be left with the datalogger for field servicing. 7.
Section 7. Short Cut Program Generator 7.2 Creating a Program Using Short Cut On opening, Short Cut presents a wizard that walks you through the steps of creating a datalogger program. 7.2.1 Step 1 – Create a New File or Open Existing File To begin creating a new program, press the New Program button. To open an existing program, press the Open Program button and select a file from the resulting browser window.
Section 7. Short Cut Program Generator 7.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. Short Cut Program Generator 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. Short Cut Program Generator 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. Short Cut Program Generator 7.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. Short Cut Program Generator 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. Short Cut Program Generator 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. Short Cut Program Generator 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. Short Cut Program Generator 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. Short Cut Program Generator 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. Short Cut Program Generator 7.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. Short Cut Program Generator 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. Short Cut Program Generator 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. Short Cut Program Generator 7.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. Short Cut Program Generator 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. Short Cut Program Generator 7.3.3 Power-up Settings Some dataloggers offer the option to retain interim measurements or calculations or the states of flags or ports when they power-up from a low battery or loss of power condition. This may be useful when calculations are used to control devices. You may, for example, want to ensure that pumps or controls are off when a datalogger powers up so as to make the control decision based on a fresh measurement.
Section 7. Short Cut Program Generator in effect for all programs for that datalogger type (whether they are new programs or edited programs) until it is changed again. 7.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.
Section 7. Short Cut Program Generator For CRBasic dataloggers, you can use the CRBasic Editor to open the .CR# files directly. Again, Short Cut will not be able to open the files you’ve edited with the CRBasic Editor, since they are not an SCW file. 7.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.
Section 8. Datalogger Program Creation with Edlog This section provides information on memory allocation and programming for Campbell Scientific’s Edlog dataloggers, including the CR7, CR10, 21X, CR500, CR510, CR10X, and CR23X. Edlog also supports these same dataloggers configured with table-based operating systems, including the table-data or “TD” and PakBus or “PB” versions.
Section 8. Datalogger Program Creation with Edlog NOTE Be careful when copying instructions from a program written for one datalogger to a program for a different type of datalogger. Instructions may differ between dataloggers. Input Location Labels – Though the datalogger uses a number to address input locations, Edlog allows you to assign labels to these locations for ease of use when programming and later when reviewing the data on-line.
Section 8. Datalogger Program Creation with Edlog Select the datalogger you are using from the list and click OK. A blank program template will come up as shown below for a CR10X. 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.
Section 8. Datalogger Program Creation with Edlog the other tables. Most users find they can write the entire program in Program Table 1, avoiding complications associated with synchronizing two tables. Program Table 2 is normally used only when portions of the program require a different execution interval (placed in Program Table 2). NOTE Program tables in this section refer strictly to sections of the datalogger program.
Section 8. Datalogger Program Creation with Edlog 8.1.1.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. When an Edlog program is saved, Edlog automatically adds a CSI extension to the program’s name. Existing CSI files can be edited by selecting File | Open. Although CSI files are ASCII files they require a particular format, so editing the *.
Section 8. Datalogger Program Creation with Edlog 8.1.1.3 Inserting Instructions into the Program Instructions are entered into the program table in the order that they should be executed in the program. There are four ways to insert an instruction: • Select Edit | Insert Instruction from the Edlog menu. • Press + on the keyboard. • Right click a blank line and select Insert Instruction from the pop-up menu. • Type the instruction number onto a blank line and press enter.
Section 8. Datalogger Program Creation with Edlog • With your cursor anywhere within the instruction, press . This opens the help system to a detailed description of the instruction and parameters. Edlog provides hints for each parameter at the very bottom of the Edlog screen. These hints often display the valid entries for a field. NOTE Many instructions are datalogger specific; refer to the specific datalogger manual for details on a particular instruction.
Section 8. Datalogger Program Creation with Edlog Following are rules for creating expressions: • Expressions must be set equal to the label of the Input Location that will store the result. The result label must be to the left of the expression. • Expressions can have both fixed numbers and Input Location labels. Input Locations can only be referenced by their label; each number in an expression is assumed to be a constant.
Section 8. Datalogger Program Creation with Edlog Below are examples of valid expressions: Zee es Root avg length TempF = = = = = = Vee+Ex tee^(-2) SQRT(ABS(data)) (data1+data2+data3+data4+data5)/5 SQRT((adj^2)+(opp^2)) (TempC*1.
Section 8. Datalogger Program Creation with Edlog 5: Z=F (P30) 1: 32 2: 0 3: 3 6: Z=X+Y (P33) 1: 3 2: 5 3: 6 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.
Section 8. Datalogger Program Creation with Edlog (3) An expression with an @ operator does not have a number after the @; only a fixed number is allowed immediately after the @ operator. (4) An expression with an @ operator does not have either a number or label before the @. (5) There is nothing between a pair of parentheses (e.g., the expression contains this “()”). (6) A number is immediately followed by a label or function without an operator (e.g.
Section 8. Datalogger Program Creation with Edlog These are correct ways of entering the above expressions: tee=5*(2) mu=(nu)*103 bee=10.52*(ef/2) sigma=-17*(RCP(alpha)) (4) A label or function is immediately after a set of parentheses without an operator.
Section 8. Datalogger Program Creation with Edlog TABLE 8-2.
Section 8. Datalogger Program Creation with Edlog 8.1.3 Library Files Library files can be created to store portions of programs, which can then be inserted into a different program. Library files are useful if you want to write different programs for the same sensor set, or it you have several stations that have similar, but not identical, sensor sets. To create a library file, select the text to be stored and then select Edit | Save To Library File. When the window appears, type in the library file name.
Section 8. Datalogger Program Creation with Edlog Toolbar Open a new file. Save the current file to disk and optionally precompile the program. Index the parameter that is selected (for information on indexing, refer to your datalogger operator’s manual). Invoke the input location editor (for a discussion on input locations and the Editor, see Section 8.2, Input Locations). Display the input location list; allows the user to select and insert an input location automatically into a parameter.
Section 8. Datalogger Program Creation with Edlog Instructions cannot be edited in the compress view mode. Use Display | Uncompressed to switch back to the full view or use the function key to toggle between the compressed and full views. 8.1.5.4 Indention Indention is typically used with If Then/Else sequences and loops to provide a visual key to program flow. Indention is a visual aid; it has no meaning to the datalogger.
Section 8. Datalogger Program Creation with Edlog 8.2.2 Repetitions Many input/output and output processing instructions have a repetitions parameter. Repetitions (REPS) allow one programming instruction to measure several identical sensors or to process data from several Input Locations. When REPS are greater than 1, the Input Locations are assigned consecutive numbers (e.g., with REPS of 2 and LOC of 5, the Input Locations are 5 and 6).
Section 8. Datalogger Program Creation with Edlog 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 8. Datalogger Program Creation with Edlog Optimize () – Deletes Input Locations that aren’t read, written to, or marked as Manual. Optimize tries to reduce the total number of locations used by moving existing Input Location labels to fill in unused locations. This might change several Input Location numbers. Any changes in location number made by the Optimize command are reflected in the Edlog program.
Section 8. Datalogger Program Creation with Edlog • Instruction 188, SDI-IO16 • Instruction 189, SDM-LI7500 • Instructions P190-199 PakBus control • Indexed input locations in a loop See Edlog Help for each instruction to get a detailed description of input location usage. You can also refer to the datalogger user’s manual for more information on these instructions.
Section 8. Datalogger Program Creation with Edlog 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. NOTE − Array ID or Table Name identifies the set of output data instructions the data is associated with. For mixed-array dataloggers the array ID is at the beginning of each output record.
Section 8. Datalogger Program Creation with Edlog 8.4.1 Program Security Setting security in the datalogger allows you to restrict access to certain functions, which helps ensure the program or data are not altered. Security is unlocked in the datalogger when, upon attempting to connect, PC400 sends the code entered in the Setup window. 8.4.1.1 Setting Passwords in the DLD In the Program Security Dialog Box, there is a field for three levels of security.
Section 8. Datalogger Program Creation with Edlog generic names for input locations, and will not be able to display final storage locations at all. Options for mixed-array dataloggers are: Minimize DLD Size – No input location labels or final storage labels are saved in the DLD file. Default – Up to 255 input location labels and all final storage labels are saved in the DLD file. All – All input location labels and all final storage labels are saved in the DLD file. 8.4.3.
Section 8. Datalogger Program Creation with Edlog NOTE Not all dataloggers have a Compile Settings option. This option refers only to the CR510, CR10X, and CR23X. 8.4.5 Datalogger Serial Port Settings The serial port settings are used to set the baud rate to which the datalogger’s port(s) should be set when the datalogger is powered-up or when a program is compiled.
Section 8. Datalogger Program Creation with Edlog While it is possible to calculate the exact number of nodes, neighbors, and routers in a PakBus network, it is often advisable to build in some “room to grow”. For example, you might want to add 3-4 nodes, neighbors and routers. Be aware that each device you add means the datalogger must allocate memory for its routing table, so if you add too many, the datalogger won’t have enough memory left to run its program. 8.4.6.
Section 8.
Section 9. Datalogger Program Creation with CRBasic Editor This section provides information on the CRBasic Editor used to program the Campbell Scientific CR800, CR1000, CR3000, CR5000, CR9000, and CR200 Series dataloggers. CRBasic is a full-featured programming language providing the power and flexibility to set up complex datalogger programs to support demanding measurement tasks. Datalogger programs can also be created using the Short Cut program generator, see Section 7, Short Cut Program Generator.
Section 9. Datalogger Program Creation with CRBasic Editor 9.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 9. Datalogger Program Creation with CRBasic Editor 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.
Section 9. Datalogger Program Creation with CRBasic Editor 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 9. Datalogger Program Creation with CRBasic Editor • Save as .CRB File: Saves highlighted text to a file with a *.CRB extension. This file is referred to as a “library file”. The file can then be reused by inserting it into another CRBasic program. • Insert File: Inserts a library file into the current program overwriting the highlighted text. 9.3 Toolbar The toolbar of the CRBasic Editor provides easy access to frequently used operations.
Section 9. Datalogger Program Creation with CRBasic Editor Print Preview – Opens a Print Preview screen that will show what the program will look like when printed. You can check and set the margins and printer options. Undo – Each time the Undo button is clicked it will step back through the last changes made to the program. 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.
Section 9. Datalogger Program Creation with CRBasic Editor Browse Bookmarks – Displays a list of all bookmarks in the program. When a bookmark is selected, the cursor moves to that line in the program. 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.
Section 9. Datalogger Program Creation with CRBasic Editor 9.3.2 Compile, Save, and Send The CRBasic Editor allows you to send a program to a datalogger that has already been defined on the network map in LoggerNet, PC400, or RTDAQ. This only works if LoggerNet, PC400, or RTDAQ is running at the time you attempt to send the program.
Section 9. Datalogger Program Creation with CRBasic Editor The Select the destination list shows all dataloggers configured within LoggerNet, PC400, or RTDAQ that may receive a program matching the extension of the current CRBasic program to be sent. Assume, for example, that you have three CR1000s and some other dataloggers in your LoggerNet, PC400, or RTDAQ network map. When you send a *.CR1 program, this screen will show only the three CR1000 dataloggers.
Section 9. Datalogger Program Creation with CRBasic Editor 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 9. Datalogger Program Creation with CRBasic Editor 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.
Section 9. Datalogger Program Creation with CRBasic Editor 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 9. Datalogger Program Creation with CRBasic Editor 9.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. 9.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 9. Datalogger Program Creation with CRBasic Editor 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 9. Datalogger Program Creation with CRBasic Editor 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 9. Datalogger Program Creation with CRBasic Editor 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 9. Datalogger Program Creation with CRBasic Editor 9.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 9. Datalogger Program Creation with CRBasic Editor The Constant Customization syntax may be best understood by looking at an example.
Section 9. Datalogger Program Creation with CRBasic Editor 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 9. Datalogger Program Creation with CRBasic Editor 9.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. 9.
Section 9. Datalogger Program Creation with CRBasic Editor Define Subroutines Program Set scan interval If there is a process or series of calculations that needs to be repeated several times in the program, it can be packaged in a subroutine and called when needed rather than repeating all the code each time. The program section defines the action of datalogging. The scan sets the interval for a series of measurements. Measurements Enter the measurements to make.
Section 9. Datalogger Program Creation with CRBasic Editor 9.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 9. Datalogger Program Creation with CRBasic Editor 9.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 9. Datalogger Program Creation with CRBasic Editor 9.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 9. Datalogger Program Creation with CRBasic Editor 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 9. Datalogger Program Creation with CRBasic Editor 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 9. Datalogger Program Creation with CRBasic Editor 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 9. Datalogger Program Creation with CRBasic Editor TABLE 9-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 9.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 9. Datalogger Program Creation with CRBasic Editor 9.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 9. Datalogger Program Creation with CRBasic Editor 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. 9.4.13.
Section 9. Datalogger Program Creation with CRBasic Editor 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 9.
Section 10. Utilities CardConvert is a utility that is used to quickly read and convert binary datalogger data that is retrieved from a compact flash or a PCMCIA card. The binary data can also be a file already saved to the user’s PC. The binary data is converted to a TOA5 format and saved on the user’s PC. Transformer is an application that converts a datalogger program created in Edlog to a CRBasic program.
Section 10. Utilities extension. For instance, the default name for a table called MyData stored in TOA5 format would be TOA5_MyData.dat. The destination directory or filename for a converted file can be changed on an individual file basis. Click on the row for the file that you wish to change. It will be highlighted. Select Options | Change Output File from the CardConvert menu, and browse for or type in a new path and/or filename.
Section 10. Utilities Select the appropriate timestamp options for the type of timestamp to write to the file. Each time element will be output as a separate data value in the array and the data values will be separated by a comma. Selecting Year will output the year represented by four digits, YYYY (e.g., 2006). The Day will be represented as a Julian Day. The Hour/Minutes will be represented by four digits (hhmm).
Section 10. Utilities When Use Filemarks, Use Removemarks, or Use Time is selected, the Create New Filenames option is disabled. New file names will always be created. Convert Only New Data – When this option is selected, only data that has been collected since CardConvert’s last conversion of the specified file(s) will be converted. The first time CardConvert is used on a file, all data will be converted. On subsequent conversions, only new data will be converted.
Section 10. Utilities processed, the estimated number of records and a percentage of the conversion completed will be displayed at the bottom edge of the window. Note that the values reflect an estimate of the amount of data in a table. If the table is set to a fixed size, CardConvert returns a fairly close estimate.
Section 10. Utilities processing the file allows you to recover all good data on a card with more than one corrupted frame. Note that CardConvert can repair only TOB2 or TOB3 files. TOB1 files cannot be repaired. NOTE The Repair File option should be used only if a standard conversion cannot be done. 10.1.4 Viewing a Converted File Converted data files can be reviewed using the View file viewing application. View can be launched by pressing the View Files button.
Section 10. Utilities 10.2.1 Transforming a File When the Transformer is first opened, a dialog box is displayed in which to enter the Source File and the Program File. 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 CR800, CR1000, or CR3000 program that will be created is the name of the original program with a CR* extension.
Section 10. Utilities 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. If a comment in the Action Log is double-clicked, the associated instructions in both the Edlog program and the CRBasic program will be highlighted.
Section 10. Utilities The transformed file cannot be edited in the Transformer. Once transformed, it can be opened in the CRBasic Editor or saved under a new file name. To open at the program in the CRBasic Editor, press the CRBasic program icon the top left of the window. To save the file under a different name, choose File | Program File | Save As.
Section 10. Utilities 10-10 • To keep the process as simple as possible, DevConfig supports only serial and IP connections between the PC and devices. • DevConfig cannot only send operating systems to supported device types, but can also set datalogger clocks and send program files to dataloggers.
Section 10. Utilities 10.3.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 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.3.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 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 10.3.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 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 10.4 File Format Convert File Format Convert is not available from the PC400 toolbar. It can be opened from the Window’s Start menu under Programs | Campbell Scientific | PC400 | Utilities 10.4.1 Overview File Format Convert is used to convert data files from one format to another. It can also perform the following functions: • Break large files into smaller files (also known as baling). • Check for missing records by checking the record number and or timestamp.
Section 10. Utilities NOTES 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. TOB1) store string in fixed length fields and have headers that specify how big that field is.
Section 10. Utilities File Naming Date Time Filename – When this option is selected, the date and time of the first record of data in the file will be appended to the end of the base file name. The suffix includes a four digit year, a two digit month, a two digit day of month, and a four digit hour/minute. When this option is selected, Use Day of Year becomes available. If this option is selected, the Julian day (day of year) will be used in the suffix instead of the month and day of the month.
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 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. N Net Description – Description of dataloggers and communications devices that form the datalogger network. Created using the EZWizard in PC400 or Setup screen in LoggerNet to communicate with the various dataloggers. Node – Part of the description of a datalogger network.
Appendix A. Glossary of Terms PakBus – A packet-based and packet-switched networking protocol used by newer dataloggers. PakBus allows for robust transmission of commands and data, dynamic routing between PakBus devices, and peer-to-peer communications (such as when one datalogger needs to control another datalogger without involving the PC). Parameter – Number or code which helps to specify exactly what a given datalogger instruction is to do.
Appendix A. Glossary of Terms Q Quiescent Mode – Often referred to as “sleep mode” – a low power state between program execution intervals. R Real-Time Clock – All dataloggers have an internal clock. The date and time information from this clock are used in the time stamp for stored data. The datalogger’s execution interval and timer are synchronized with the clock.
Appendix A. Glossary of Terms SDI-12 – SDI-12 stands for Serial Digital Interface at 1200 baud. It is an electrical interface standard and communications protocol that was originally developed by Campbell Scientific and other manufacturers for the U.S. Geological Survey for hydrologic and environmental sensors. SDI-12 was designed to be a simple interface (ground, 12 volts, and signal) that improves compatibility between dataloggers and “smart” microprocessor-based sensors.
Appendix A. Glossary of Terms this coordination is accomplished by synchronizing the transmitting and receiving devices to a common clock signal (see Asynchronous). T Tab Windows – Some screens depict a series of related windows in a multitabbed notebook format. When you click the file folder tab, the information on the tab you chose will be displayed. Tables – An entry in the status table that shows the number of user-created data tables. (See also Data Table.
Appendix A. Glossary of Terms W Wiring Panel – The set of terminals and underlying circuits that enable connections of sensors, control and power supply wiring to the datalogger itself. Some dataloggers such as the CR23X have built-in wiring panels. Others, such as the CR10X, have removable wiring panels. Watchdog – An entry in the status table that shows the number of watchdog errors that have occurred. The watchdog checks the processor state and resets it if necessary.
Appendix B. Table-Based Dataloggers This section describes some of the characteristics and features of the Edlog TD and PB dataloggers and CRBasic dataloggers. These include the CR510-TD, CR510-PB, CR10T, CR10X-TD, CR10X-PB, CR23X-TD, CR23X-PB, CR200, CR800, CR1000, CR3000, CR5000, and CR9000. See the operator’s manual for the specific datalogger for detailed information about its operation. B.
Appendix B. Table-Based Dataloggers NOTE Event driven tables should have a fixed size rather than allowing them to be allocated automatically. Event driven tables in Edlog TD dataloggers that are automatically allocated are assumed to have one record stored per execution interval in calculating the length.
Appendix B. Table-Based Dataloggers If the amount of memory requested for the data tables exceeds the available memory, the program will not run. NOTE Event driven tables should have a fixed size rather than allowing them to be allocated automatically. Event driven tables in CR800, CR1000, CR3000, CR5000, and CR9000 dataloggers that are automatically allocated are assumed to have one record stored per execution interval in calculating the length.
Appendix B. Table-Based Dataloggers B.2.1 Steps for Program Conversion If you are converting a program from mixed-array to table-data format for the same datalogger (e.g., converting a CR10X program to a CR10X-TD program) you can edit the existing program in Edlog. If you are converting a program from one datalogger series to another (e.g.
Appendix B. Table-Based Dataloggers based on time (interval data) or when a user flag is set (event data). Time based output intervals are specified in seconds. • Instruction 18, Time – Instruction 18 is used to store the current time into an input location. Parameter 1 designates what format will be used when storing the time. There are differences in this instruction’s Parameter 1 for the two datalogger types.
Appendix B. Table-Based Dataloggers B.3 Table Data Overview In the datalogger all data is organized into tables with fixed data records. Each of these tables has a definite number of records that is either fixed by the datalogger program or allocated when the program is compiled by the datalogger. Once the maximum number of records for a table has been stored, the next record stored will overwrite the oldest record in the table.
Appendix B. Table-Based Dataloggers Data tables can also be event driven rather than interval driven. That is, a new record is stored when a specified event occurs rather than based on time. Each table is completely independent of any other tables and all records in a given table have the same number of fields. B.4 Default Tables Each table-based datalogger has a set of default tables plus the tables created by the datalogger program.
Appendix B. Table-Based Dataloggers TABLE B-1. Example of Status Table Entries B-8 TMStamp Date and time the status information was recorded. RecNBR The record number in the table. Battery Datalogger battery voltage. Watchdog The watchdog checks the processor state, software timers, and program related counters. If an error occurs, the watchdog counter is incremented.
Appendix B. Table-Based Dataloggers TABLE B-1. Example of Status Table Entries CPUSignature The Operating System signature. The value should match the value obtained by running the CSI sig program on the name.obj operating system file. DLDSignature Signature of the current running program file. ProgSignature Signature of the compiled binary data structure for the current program. This value is independent of comments added or non functional changes to the program file.
Appendix B. Table-Based Dataloggers TABLE B-1. Example of Status Table Entries B-10 WatchdogErrors The number of Watchdog errors that have occurred while running this program. This value can be reset from the keyboard by going to status and scrolling down to the variable and pressing the DEL key. It is also reset upon compiling a new program. Low12VCount Keeps a running count of the number of occurrences of the 12VLow signal being asserted.
Appendix C. Log Files and the LogTool Application C.1 Event Logging As PC400 performs its work, it will create records of various kinds of events and store them in ASCII log files. These logs can be very useful for troubleshooting problems and monitoring the operation of the datalogger network. You can monitor these logs using a built-in tool, called LogTool, accessible from the Tools | LogTool menu item, or open these log files in a simple text editor.
Appendix C. Log Files and the LogTool Application have been created, the oldest log file is deleted as a new one begun. PC400 stores the most recent log records in a file that has a $ character in the place of the version number or “X” in the above file names. When this file grows to the point that it will exceed the threshold set by the File Size setting for that log (default 1.4MB in PC400), the server renames the log file by replacing the dollar sign with a new version number.
Appendix C. Log Files and the LogTool Application TABLE C-1. Transaction Log Messages Code Message Text Message Parameters Message Meaning 1 Network device added Device Name 2 Network branch deleted Device Name 3 Network branch moved Device Name 5 Network logon succeeded Logon Name 6 Network logon failed Logon Name A new device was added to the network map.
Appendix C. Log Files and the LogTool Application TABLE C-1. Transaction Log Messages Code Message Text Message Parameters Message Meaning 14 Clock check failed Reason code: 3. Communication failure 4. Invalid datalogger security clearance 5. Invalid transaction number specified (already in use) 6. Communications are disabled for this device 7. The transaction was aborted by client request 8.
Appendix C. Log Files and the LogTool Application TABLE C-1. Transaction Log Messages Code Message Text 36 Logger table definitions have changed 40 Datalogger message Severity (S for Status, W for Warning, F for Fault); Message text. This is a message that has been generated by the datalogger (or in some cases the RF base on behalf of the datalogger).
Appendix C. Log Files and the LogTool Application TABLE C-1.
Appendix C. Log Files and the LogTool Application TABLE C-1. Transaction Log Messages Code Message Text Message Parameters 65 Device restore from file failed On server startup a device in the network map could not be restored. 66 Device save to file succeeded 67 Device save to file failed The update to the device configuration file was successful. The update to the device configuration file failed. 68 Packet delivery failed Fault code: 1. Incompatible BMP1 device or malformed packet 2.
Appendix C. Log Files and the LogTool Application TABLE C-1.
Appendix C. Log Files and the LogTool Application TABLE C-1. Transaction Log Messages Code Message Text 76 Logger unlocked 77 Null program sent 78 Server started 79 Server shut down 80 Collect area initialized Collect area removed 82 83 LgrNet restore failed 85 Data restore failed 86 Manual poll transaction started 87 Manual poll transaction complete Message Parameters The server version Collect area name Message Meaning The transaction blocking datalogger access has completed.
Appendix C. Log Files and the LogTool Application TABLE C-1.
Appendix C. Log Files and the LogTool Application TABLE C-1. Transaction Log Messages Code Message Text Message Parameters Message Meaning 100 Table mount failed Table name; Operating system information regarding the failure 101 Add record failed Table name; Beginning record number; End record number; A reason for the failure The server was not able to create a data collection area from the stored table configuration file or new table definitions.
Appendix C. Log Files and the LogTool Application TABLE C-1.
Appendix C. Log Files and the LogTool Application TABLE C-1.
Appendix C. Log Files and the LogTool Application TABLE C-1. Transaction Log Messages C-14 Code Message Text Message Parameters Message Meaning 110 Collect area setting changed 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 C. Log Files and the LogTool Application 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.
Appendix C. Log Files and the LogTool Application TABLE C-2. Communications Status Log Messages Message Text Serial packet X exchanged Classic;;Cmd BMP1 packet received RPC packet exchanged Datalogger did not respond to end command PakBus framing error Invalid low level signature C-16 Message Meaning The low level serial BMP1 communication framing packet was sent and the response received from the device. (CR10X-TD table based type devices) The listed command was sent to an array based datalogger.
Appendix C. Log Files and the LogTool Application TABLE C-2. Communications Status Log Messages Message Text Provider opened Device dialed Provider closed Unable to Locate Serial synch byte Message Meaning The serial communications port has been initialized. The communications link has been initialized to transfer data packets. The serial communications port has been closed. The low level communications synchronization byte was not received after the computer sent out a serial packet.
Appendix C. Log Files and the LogTool Application Object State Log Example "2009-04-15 16:41:05.351","CR1000","starting BMP5 operation","manage comm resource" "2009-04-15 16:41:05.367","CR1000","starting BMP5 operation","check/set clock" "2009-04-15 16:41:05.367","PakBusPort_ip","Request Transaction Focus","check/set clock","213" "2009-04-15 16:41:05.367","PakBusPort_ip","Transaction focus start","PakCtrl::Hello","2","214" "2009-04-15 16:41:05.
Campbell Scientific Companies Campbell Scientific, Inc. (CSI) 815 West 1800 North Logan, Utah 84321 UNITED STATES www.campbellsci.com • info@campbellsci.com Campbell Scientific Africa Pty. Ltd. (CSAf) PO Box 2450 Somerset West 7129 SOUTH AFRICA www.csafrica.co.za • cleroux@csafrica.co.za Campbell Scientific Australia Pty. Ltd. (CSA) PO Box 8108 Garbutt Post Shop QLD 4814 AUSTRALIA www.campbellsci.com.au • info@campbellsci.com.au Campbell Scientific do Brasil Ltda. (CSB) Rua Apinagés, nbr.
