LoggerNet Datalogger Support Software

Expand AllCollapse All

1. How can data from LoggerNet be added into the SCADA software OSIsoft PI?

   OSIsoft sells a PI interface for LoggerNet. The OSIsoft part number is PI-IN-CS-LN-NTI. Please direct all inquiries for sales and support of the interface to OSIsoft.

2. Why does LoggerNet create a backup data file every time data collection is triggered?

   Before it appends to a TOA5, TOB1, or TOACI1 data file, LoggerNet first scans the header of that file and compares the information that it contains with the information reported in the data logger table definitions. For TOA5, the following conditions can result in errors that will cause LoggerNet to refuse to append to the file:

   • The table names do not match.
   • The number of columns does not match.
   • One or more column names do not match.
   • The number of units strings does not match the number of column names.
   • The number of process strings does not match the number of column names.

   There have been cases where, using the FieldNames() instruction, the data logger program specified a double quote character (") in the units string, and this character unbalanced the quote marks in the TOA5 format, which in turn threw off the TOA5 parser.

3. When does LoggerNet do a clock check?

   LoggerNet does not do a clock check unless there is another reason to contact the data logger, such as for scheduled collection.

4. Does LoggerNet anywhere indicate the battery level of the connected data logger?

   For PakBus data loggers, the battery voltage is found on the Station Status screen. (The Station Status screen is accessed from the LoggerNet Connect screen.) For mixed-array data loggers, Station Status will display the lithium battery and the number of times the 12 V supply has dropped below an acceptable level. If the battery voltage is being read by the program, it may be available from the public table.

5. Would there be any major problems with moving a data logger to another communications path while someone is using the LoggerNet software?

   As long as the same device is being moved from one communications route to another, all data collection pointers, filenames, etc., will be maintained with that data logger as it is moved.

6. How does LoggerNet handle data collection when the data logger stores data to a CompactFlash card?

   LoggerNet collects data from the data logger first. If there is additional data on a CompactFlash card, LoggerNet collects that also. Nothing special needs to be set up in LoggerNet to have this occur.

7. Does the LoggerNet server have a specific limit on the length of a generic modem script?

   The LoggerNet server imposes no specific limits on the lengths of the generic modem scripts.

8. Is there any way to set a variable in the data logger using LoggerNet to gain manual control over when data is collected by the data logger?

   A program snippet, such as the one below, would work for this purpose. The Boolean variable can be toggled from the Ports & Flags screen in LoggerNet (accessed via the Connect screen), through the Numeric Display (also accessed via the Connect screen), or under program control.

   public StoreDataFlag as boolean

   DataTable (ConditionalTable,StoreDataFlag,100)

             Sample (1,counter,Long)

   EndTable

   When storing data conditionally, be sure to allocate a specific number of records in the size parameter of the DataTable() instruction. For more information, see the Data Table Memory Allocation Tutorial.

9. How can LoggerNet be used to edit the user drive size in the data logger settings?

   Follow these steps:

   1. Connect to the data logger using the LoggerNet Connect screen.
   2. Find the data logger in the Stations list, and right-click it.
   3. From the menu that is displayed, choose the Settings Editor.
10. Can two different communications paths to one data logger be set up in LoggerNet?

    LoggerNet can be configured to have two paths to a data logger, simply by entering the data logger twice in the network map with different comms links. LoggerNet, however, treats them as separate entities, so it will try to collect all the data twice via the two separate paths if both are enabled. Some users have set this up where they use one route most often, and manually enable collection to the backup route if the main link is lost.

    An alternative to this scheme is to set up the backup route but not add the data logger. Then, if the main link to the data logger goes down, simply drag-and-drop the data logger to the backup route. After the main link is working again, the data logger can be moved again. This keeps data collection pointers for that data logger intact.