LoggerNet Defaults
This screen is used to set default values for the Schedule, Data Files, Clock, and File Retrieval tabs that will be used when new stations are added to the network.
You can also use the Copy Defaults to Existing Stations button to apply these defaults to existing stations. You will be asked to select the default settings to apply and the stations to apply them to.
If you have changed settings on the LoggerNet Defaults screen, you can press the Restore Original Defaults button to restore the settings to the original LoggerNet defaults.
NOTE: Not all of the default settings apply to all station types.
Schedule Tab
Scheduled Collection Enabled - Select this check box to enable the data collection schedule that has been set up for the device. Clearing the check box suspends the schedule.
Base Date/Time - Enter a date and a time that the first data collection attempt for the device should occur. If the date and time reflected by these fields has already passed, data collection will be attempted immediately when the schedule is enabled.
Collection Interval - Enter the interval on which data should be collected from the device. The collection interval is relative to the Base Date and Time entries. For instance, if the Base Time is set at 12:15 and the interval is set for 1 hour, data collection will be attempted at 12:15, 1:15, 2:15, etc. The format for this field is 00 d(ays) 00 h(ours) 00 m(inutes) 00 s(econds) 000 m(illi)s(econds).
Primary Retry Interval - If a scheduled data collection attempt fails, data will be collected on the interval specified by this field. When a call is successful, data collection will resume on the normal schedule. The format for this field is 00 d(ays) 00 h(ours) 00 m(inutes) 00 s(econds) 000 m(illi)s(econds).
Number of Primary Retries - Enter a value for the number of data collection attempts that should be made using the Primary Retry Interval. Once the number of primary retries is exhausted, data collection will be attempted on the Secondary Retry Interval if it is enabled. Otherwise, data collection attempts will continue to be made on the original calling interval.
Secondary Retry Interval - This retry interval is optional. It can be enabled by selecting the Secondary Retry Interval Enabled check box. It is the interval that will be used for data collection attempts once the primary retries have been exhausted. The format for this field is 00 d(ays) 00 h(ours) 00 m(inutes) 00 s(econds) 000 m(illi)s(econds).
Secondary Retry Interval Enabled – Enables the Secondary Retry Interval. If this field is disabled, data collection attempts continue on the original calling interval until a successful call is made.
Collect Ports and Flags - Enable this check box to retrieve the status of the datalogger's ports and flags during scheduled data collection. When this information is retrieved it is not saved to a data file, but it is made available for real-time display by other applications such as RTMC.
Stay On Collect Schedule - By default, when LoggerNet has missed a scheduled collection because of some condition (i.e., LoggerNet was closed, scheduled collection was disabled, the schedule was paused from the Status Monitor, etc.), once the condition that prevented collection is no longer true, if an entire collection interval has elapsed since the last collection attempt, LoggerNet will immediately try to perform a collection. In some cases, this may not be the desired behavior. Selecting the Stay On Collect Schedule check box will cause LoggerNet to always wait until the next even Collection Interval to perform a collection.
Poll for statistics - The Status Monitor displays information about datalogger data collection and communication status. There are some potential useful statistics (columns) that are available for some dataloggers that are not available for other datalogger types. Sometimes there are statistics obtained automatically as part of data collection for some dataloggers but can be only obtained with additional communication commands for other dataloggers. In this latter case, these statistics are not retrieved by default as users with slow or expensive communication may not wish to incur the additional cost or time associated with the extra commands. In cases where the user does want to retrieve the additional statistics, the Poll for Statistics setting can be enabled to request that the statistics are retrieved. The statistics will be retrieved during scheduled or manual data collection.When Poll for Statistics is enabled, the Status Monitor can show the following statistics even if the Status Table is not being collected:
| Status Table Values | ||||||
Server Statistic (displayed in Status Monitor) | CR1000X CR6 Series CR300 Series CR350 Series GRANITE Data Logger Modules CR1000 CR800 Series CR3000 | CR200 | CR10XPB CR23XPB CR510PB | CR5000 | CR9000X | CRS451 Series | CRVW Series |
WatchDog Err | WatchDogErrors | WatchDogCnt | WatchDog | WatchDogErrors |
| WatchDogCnt | WatchdogErrors |
Prog Overrun | SkippedScan | SkipScan | Overruns | SkippedScan | SkippedScan | SkipScan | Skipped Scan |
Low Volt Stopped | Low12VCount |
|
|
|
|
| Low10_5V_Count |
Low 5V | Low5VCount |
|
|
|
|
|
|
Lith Batt Volt | LithiumBattery* |
| LithBat | LithiumBattery | Battery | LithiumVoltage | RTC_Battery |
NOTE: *For CR300-series dataloggers, a voltage will not be displayed. If the internal lithium battery supplied sufficient power to maintain the clock while external power was absent, the field will display “OK, ON POWER UP.” If the internal lithium battery is missing or failed to supply enough power while external power was absent, the field will display “FAIL, ON POWER UP.” The LithiumBattery field is only updated on power up, that is, when external power is first applied.
NOTE: If the above Server Statistic columns are not currently being displayed in the Status Monitor, you can add them by selecting Edit | Select Columns from the Status Monitor menu.
Reschedule On Data - When this box is selected, each time that data is received for a station, the data collection schedule will be reset using the current system time as the base time.
In bandwidth constrained networks, particularly those involving RF-TD protocols, One Way Data and Data Advise are the primary means of collecting data from network stations. When these mechanisms are used, users will typically not enable scheduled collection. This has the disadvantage of not providing the information needed by the LoggerNet Status Monitor and Troubleshooter applications to help the user recognize when data collection for a station has fallen seriously behind. By using the Reschedule on Data setting, the data collection schedule can be enabled for a station with the associated interval set to be greater than or equal to the longest expected interval at which data will be sent by the station. Since the schedule is restarted each time that new data is received, scheduled collection will not take place as long as the flow of data continues from that station. If, however, communication is interrupted from the station and no data is received, the server will start a collection attempt when the schedule fires.
Collect Via Data Advise (available only in LoggerNet Admin/LoggerNet Remote for CR510TD, CR10XTD, CR23XTD, and CR10T dataloggers in an RF TD network) - When this option is enabled, an agreement is established between the LoggerNet server and the datalogger. As part of the Data Advise agreement, LoggerNet reports the tables that are marked for collection and the datalogger stores that information in memory. When the datalogger receives a communication packet of any kind, it checks for new records in the tables marked for collection. If a new record exists, it is sent by the datalogger to the LoggerNet server.
Data Advise is used within RF telemetry networks to increase the speed of data collection. The RF polling process using the TD-RF (“Time-division polling”) PROM or OS can take advantage of the Data Advise agreement to collect data very quickly by broadcasting a communication packet to all dataloggers in the RFBase-TD network concurrently. This broadcast packet triggers all dataloggers to check for and send any new records at once. The records are simultaneously stored in the individual RF remote modems (RFRemote-TD) until retrieved through the RF polling process (initiated by the RFBase-TD).
One Way Data Hole Collection - A discontinuity in collected data is referred to as a hole. One Way Data hole collection does not apply to holes collected during manual data collection or scheduled data collection since the default behavior of those collection methods will always retrieve the records needed from the datalogger and store them in the data cache in sequential order. However, there are settings in LoggerNet and other data collection methods that can produce missing records in the data cache.
One Way Data and Data Advise are two collection methods that can produce holes. These collection methods both rely on the datalogger to send records to LoggerNet. Since the transmission of these records is unacknowledged, there is a possibility that the data will be lost. If LoggerNet doesn’t receive a record for any reason, a hole is created. If this check box is selected to enable One Way Data hole collection, LoggerNet will attempt to contact the datalogger and request the missing records. Otherwise, LoggerNet will not attempt to collect records missing from the data cache.
Please note that LoggerNet puts records from One Way Data hole collection in the .dat files as they are received. If there are holes in the data that are retrieved later, the records will not be in sequential order in the .dat file created by LoggerNet.
NOTE: One Way Data hole collection will not occur at a time when doing so would force the communication link to be dialed.
When the Server's Table Definitions are Invalid - Choose the option for the action that should be taken in the LoggerNet Server Data Cache (memory) during scheduled data collection (or upon the arrival of a One Way Data record) when LoggerNet determines that the table definitions it has stored for the datalogger and the table definitions actually in the datalogger do not match.
Automatically Reset Changed Tables - LoggerNet will reset (delete and recreate) any tables that have changed. Unchanged tables will not be reset. Scheduled data collection will continue without action from the user.
Stop Collection Until Manually Updated - Scheduled data collection will be halted until the user manually updates the table definitions (Setup Screen, Data Files tab, Get Table Definitions button). At that time, the user will be prompted to Merge or Reset the table definitions.
Background information on table definitions:
The LoggerNet server keeps track of the table definitions for a datalogger in its data cache. If the server recognizes that the table definitions for one or more tables in a datalogger are different than that for the datalogger in the server, it will use one of two methods to resolve the differences: Merge or Reset.
When LoggerNet attempts to Merge the changes in the tables into the data cache, it will delete from the data cache and then recreate any tables whose header information is different from the information stored in the table definitions. Tables which have not changed, or whose header information has not changed, will not be deleted and recreated.
When LoggerNet attempts to Reset any changed tables, all changed tables will be deleted and recreated, regardless of whether or not the change actually affected the structure of the data fields of the table.
Note that if merging a table affects the structure of the data fields, when data is stored to disk the existing file will be saved with a *.backup extension and a new file will be created. If the change does not affect the structure of the data fields (for instance, only the number of records for a table has changed), the data will continue to be stored in the existing file.
Data Files Tab
NOTE: Table Output Format, Table—Collect Mode, and Use Reported Station Name apply only to table-based dataloggers. Final Storage Output Format and Final Storage—Collect Mode apply only to array-based dataloggers.
Output File Name - Enter the default file name. The setting can contain these predefined symbols that will be expanded by the LoggerNet server at the time the file is opened or created:
%a | LoggerNet working directory. (By default, C:\Campbellsci\LoggerNet.) |
%w | LoggerNet server working directory. (By default, C:\Campbellsci\LoggerNet\sys\bin.) |
%s | Name of the station. |
%n | Name of the table or final storage area. |
%% | Substitutes a percent character in the path. |
File Output Option - Append to End of File adds new data to the end of the existing data file. Overwrite Existing File replaces the existing file with a newly created file. Create Unique File Name leaves any existing files intact and creates a new file with a unique file name based on the timestamp of the first record that will be written to the file. For example, CR1000_Table1_2008_09_03_1415.dat. No Output File results in no data file being written to disk.
NOTE: When appending to a data file, LoggerNet will check to make sure that the existing data file header matches the new data that is to be appended to the file. If the header does not match, LoggerNet may back up the existing data file and then create a new data file.
Table Output Format - The format in which the data file is saved to the computer.
ASCII, Table (no header) - Data is stored in a comma separated format. No header information is included in the file. When this option is selected the browse button to the right of the field becomes available. It launches a dialog box from which to specify if a timestamp and record number should be included, if strings should be surrounded by quotation marks, and whether midnight is specified as 2400 or 0000.
ASCII, Short Header - Data is stored in a comma separated format. Header information for each of the columns is included.
ASCII, Long Header - Data is stored in a comma separated format. Header information for each of the columns is included, along with field names and units of measure if they are available. When this option is selected, the browse button to the right of the field is available. Pressing this button opens a window from which you can specify whether timestamps and record numbers are included with each record and whether midnight is specified as 2400 or 0000.
Binary, TOB1 - Data is stored in a binary format. Though this format saves disk storage space, it must be converted before it is usable in other programs. When this option is selected, the browse button to the right of the field is available. Pressing this button opens a window from which you can specify whether timestamps and record numbers are included with each record.
Array Compatible CSV - Data is stored in a user-defined comma separated format. When this option is selected, the browse button to the right of the field is available. Pressing this button opens a window in which you customize the data string for the output file. This option can be used to produce output files from table data dataloggers that are similar to those created by mixed array dataloggers.
CSIXML - Data is stored in XML format with Campbell Scientific defined elements and attributes. For additional information, refer to the LoggerNet manual. When this option is selected, the browse button to the right of the field is available. Pressing this button opens a window from which you can specify whether timestamps and record numbers are included with each record and whether midnight is specified as 2400 or 0000.
NOTE: The station name contained in the data file header information is the name of the station in LoggerNet’s device map. It is not the station name returned by the StationName instruction in CRBasic-programmed dataloggers.
Table - Collect Mode - This option determines how data will be collected on the first and subsequent collections.
Data Logged Since Last Collection - If Collect All On First Collection is enabled with this option, all data will be collected on the first collection and any new data will be collected on subsequent collections. If Collect All On First Collection is disabled, only the number of arrays specified in the Records to Collect On First Collection will be collected and any new data will be collected on subsequent collections.
Most Recently Logged Records - During each data collection, the number of records specified in the Records to Collect field will be collected.
Collect At Most - During each data collection, LoggerNet will collect the most recently logged records up to the number of records specified in the Records to Collect field. In contrast to the Most Recently Logged Records mode, the Collect At Most mode will not duplicate records previously collected. Therefore, fewer records than the number specified may be collected.
Use Reported Station Name - Enabling this check box will cause the station name from the Status Table to be used in the header of the data files. If this check box is not enabled, the network map station name will be used.
NOTE: This check box affects only the header of the data files. It has no effect on the filenames.
Final Storage Output Format - The format in which the data file is saved to the computer. All data is retrieved in binary format and then converted by LoggerNet, if necessary, when saved to disk.
ASCII, Comma Separated stores data in a standard format with data points separated by commas. All leading and trailing zeros, unnecessary decimal points, and plus signs are stripped. Each line of data is separated with a carriage return line feed.
Data points in a ASCII, Printable format are preceded with a 2-digit ID and a + or - sign. The ID and fixed spacing of the data points make specific data easy to locate on a printed output.
The Binary option uses patterns of 0s and 1s to represent each value in the data stream. This format saves space, but must be converted using Split or some other editor before it can be read.
The default format, ASCII, Comma Separated, is most easily imported into other applications. Split can be used to convert Binary or ASCII, Printable data to a comma separated file.
Final Storage - Collect Mode - This option determines how data will be collected on the first and subsequent collections.
Data Logged Since Last Collection - If Collect All On First Collection is enabled with this option, all data will be collected on the first collection and any new data will be collected on subsequent collections. If Collect All On First Collection is disabled, only the number of arrays specified in the Arrays to Collect On First Collection will be collected and any new data will be collected on subsequent collections.
Most Recently Logged Arrays - During each data collection, the number of arrays specified in the Arrays to Collect field will be collected.
Clock Tab
Automated Clock Check - A schedule can be set up to compare the LoggerNet server's clock with the datalogger's clock, and automatically set the datalogger's clock if it varies by a certain amount.
Enabled - This check box is used to turn the clock check schedule on or off.
Initial Date/Initial Time - These fields are used to specify when the first scheduled clock check should occur. If the time reflected by these fields has already occurred, a clock check will be performed during the next data collection attempt with the datalogger.
Interval - Enter an interval for how often a clock check should be performed.
Allowed Clock Deviation - Enter the amount of time, in seconds, that the datalogger's clock can differ from the LoggerNet server's clock before the datalogger's clock is corrected. If 0 is entered, the clock will be checked but not set. The Last Clk Chk and Last Clk Diff statistics can be viewed in the Status monitor to determine the time of the last clock check and the amount of deviation when this value is set to 0.
NOTE: A datalogger will not be contacted by LoggerNet only for a clock check. If a clock check interval occurs outside of a scheduled data collection interval, the clock check will be executed the next time data collection is attempted.
WARNING: The Automated Clock Check option should be used with caution since changing the datalogger’s clock close to a time when the datalogger should be storing data can result in data with missing or duplicate timestamps. Therefore, the Allowed Clock Deviation should not be set so small that it results in frequent datalogger clock adjustments. Also the clock check interval and/or the scheduled data collection interval should not cause clock checks to occur close to a time when the datalogger should be storing data. (Note that the scheduled data collection interval is important because, as stated above, the datalogger will not be contacted specifically for a clock check. Once a clock check interval passes, the clock check will be performed during the next data collection attempt.)
Also note that when setting the Allowed Clock Deviation, you should take into account the accuracy of the datalogger clock relative to the accuracy of the computer’s clock.
WARNING: If the LoggerNet server computer automatically adjusts for daylight saving time, then your datalogger's clock will be adjusted accordingly if the Automated Clock Check is enabled.
File Retrieval Tab
NOTE: The File Retrieval Tab applies only to the CR1000X, CR6 Series, CR300 Series, CR350 Series, GRANITE Data Logger Modules, CR1000, CR3000, CR800 Series, CR10XPB, CR23XPB, and CR510PB.
Retrieval Mode - This option determines the schedule for file retrieval.
Disabled - No files are retrieved.
Follow Scheduled Data Collection - Files will be retrieved on the same schedule that has been set up for scheduled data collection on the Schedule tab. An attempt to retrieve the files will be made at the scheduled time, only if scheduled collection is enabled. However, regardless of whether or not scheduled collection is enabled, an attempt to retrieve the files will take place when a manual poll is performed using a Collect Now button, when a call-back occurs, or when a task calls the station.
New Schedule - Files will be retrieved based on the Base Date and Time and Collection Interval defined below. Only the new schedule will trigger file retrieval. Attempts to retrieve files will be made following the new schedule, whether or not scheduled collection is enabled.
Base Date/Time - Enter a date and a time that the first file retrieval attempt for the device should occur. If the date and time reflected by these fields has already passed, retrieval will be attempted immediately when the schedule is enabled.
Retrieval Interval - Enter the interval on which files should be retrieved from the device. The retrieval interval is relative to the Base Date and Time entries. For instance, if the Base Time is set at 12:15 and the interval is set for 1 hour, file retrieval will be attempted at 12:15, 1:15, 2:15, etc. The format for this field is 00 d(ays) 00 h(ours) 00 m(inutes) 00 s(econds) 000 m(illi)s(econds).
Delete Files After Retrieval - When this box is selected, the files will be deleted from the datalogger after they are retrieved.
Add New - When this button is pressed, a new pattern is added to the list of files to be retrieved. The user must then designate the File Pattern, Output Directory, Max Files, Force Retrieval, and Record If Skipped fields for this pattern.
Delete - When this button is pressed, the selected pattern is deleted from the list of files to be retrieved.
Edit File Pattern - Specifies a file pattern that will select the files that will be retrieved. Select an option from the drop-down list or type it in directly. This can be an exact filename or it can contain the wildcard characters “*” or “?”. The asterisk is able to replace zero or more characters while the question mark replaces exactly one character. The file pattern can also have a prefix indicating the drive from which to retrieve the files. Note that the file pattern is not case sensitive.
Examples
*.jpg retrieves all the jpg files from all available drives
CPU:*.jpg retrieves all of the jpg files from the CPU drive
CRD:test8.txt retrieves the file test8.txt from the CRD drive
test8.txt retrieves any file named test8.txt from all available drives
Output Directory - Enter the directory to store the retrieved files. It can be entered into the field directly, or you can press the browse button to the right of the field to select a path from the Explorer window. The setting can contain these predefined symbols that will be expanded by the LoggerNet server at the time the file is opened or created:
%a | LoggerNet working directory. (By default, C:\Campbellsci\LoggerNet.) |
%w | LoggerNet server working directory. (By default, C:\Campbellsci\LoggerNet\sys\bin.) |
%s | Name of the station. |
%% | Substitutes a percent character in the path. |
Max Files - Specifies the maximum number of files that can be retrieved on each retrieval. The newest files will be retrieved.
Force Retrieval - When this box is selected, a file that matches the file pattern will be retrieved regardless of the file’s timestamp or whether the file has already been retrieved.
Record If Skipped - When this box is selected, the names and dates of any files that are not retrieved because of the Max Files parameter will be recorded and they will not be retrieved later. If this box is not selected, the skipped files can be retrieved in a later attempt.