LoggerNet Admin Software de soporte para datalogger - grandes redes

Expandir todoDesplegar todo

1. How do you pull data from LoggerNet into a database, another application, or a website?

   There are several approaches you can try:

   1. The LNDB Interface can pull data from LoggerNet and insert it into a database instance. Supported database platforms are as follows: Microsoft SQL; MySQL; unofficially, MariaDB as it is open source MySQL, PostGRESQL, and Oracle. The database table structure and metadata will match the structure of the station’s program and the station name used in LoggerNet exactly. You cannot customize the structure. Refer to the setup documentation.
   2. Read or parse data from LoggerNet .dat files. The files are CSV formatted and can be parsed in using most any programming language. Files by default are stored on the LoggerNet computer in the following path: C:\Campbellsci\LoggerNet.
   3. LDMP Server, a LoggerNet Admin component, offers a listening socket for data to be pulled directly from the LoggerNet cache over the LoggerNet Service listening port 6789. Complete documentation in LoggerNet Admin is stored in the following path: C:\Program Files (x86)\Campbellsci\LoggerNet\ldmp_server2.pdf.
   4. Read in data using the CSI web server’s built in Web API. The webAPI accepts queries in the same format as the data logger’s built-in webAPI. Refer to the data logger webAPI documentation. 
2. What’s new in LoggerNet 4.2?

   • LoggerNet now supports IPv6 addresses. IPv6 addresses are written as eight two-byte address blocks separated by colons and surrounded by brackets (e.g., [2620:24:8080:8600:85a1:fcf2:2172:11bf]). Prior to LoggerNet 4.2, only IPv4 addresses were supported. IPv4 addresses are written in dotted decimal notation (e.g., 192.168.11.197). Leading zeroes are stripped for both IPv4 and IPv6 addresses.
     • Note: Although LoggerNet now supports IPv6 addresses that can be used to specify servers, CR1000, CR3000, and CR800-series dataloggers will not support IPv6 until a future OS release. Check the OS Revision History to determine when IPv6 support is added to the OS.
   • LoggerNet now supports display and input of Unicode characters and strings in many areas of the product. Unicode is a universal system for encoding characters. It allows LoggerNet to display characters in the same way across multiple languages and countries. To support Unicode, an Insert Symbol dialog box has been added to the CRBasic Editor. This allows the insertion of Unicode symbols into a CRBasic program for use in Strings and Units declarations.
   • The ability to set up subnets of the network map has been added to LoggerNet Admin. The Setup Screen’s View | Configure Subnets menu item is used to configure the subnets. Within each subnet, groups of data loggers can be specified. The data logger groups create folders that can be collapsed or expanded when viewing the subnet. After subnets have been configured, the choice can be made to view a subnet rather than the entire network in the Setup Screen, Connect Screen, and Status Monitor.
   • Defaults can be set up for the Setup Screen’s Schedule, Data Files, Clock, and File Retrieval tabs that will be used when new stations are added to the network. There is also the ability to copy these defaults to existing stations.
   • The ability to use 24:00 (rather than the default of 00:00) for the timestamp at midnight has been added. (This is accessed from the   button next to the Output Format field on the data logger’s Data Files tab in the Setup Screen. It is also available in the Connect Screen’s Custom Collection options.)
   • PakBus Encryption is now supported for communication between LoggerNet and CR1000, CR3000, and CR800-series dataloggers. A PakBus encryption key must be entered in both the data logger’s device settings and LoggerNet’s Setup Screen. AES-128 encryption is used.
     • Note: The data logger must be running OS 26 or later for PakBus Encryption to be used.
   • Two new root devices (SerialPortPool and TerminalServerPool) have been added to allow for modem pooling. Pooled devices may be useful in cases where LoggerNet is used to call, by phone, multiple remote data loggers, and more than one modem and phone line is available to make the connections.
   • A data logger’s Settings Editor can now be accessed from the Connect Screen either by right-clicking the data logger or from the Datalogger menu. The data logger’s clock can be manually set from the Connect Screen either by double-clicking in the Station Date/Time field or from the Datalogger menu. Boolean values displayed in the Connect Screen’s Numeric Display now have an LED icon next to them to allow for easy toggling.
   • Additional statistics can now be viewed in the Status Monitor for table-based data loggers, including watchdog errors, skipped scans, and battery errors.
     • Note: The Poll for Statistics checkbox on the data logger’s Schedule tab in the Setup Screen must be selected to poll for these statistics.
   • The Task Master has been integrated into the LoggerNet server. This allows for remote administration of the Task Master. (See Select Server in the Task Master Help for conditions that must be met for remote administration of the Task Master.)
     • Note:  Integrating the Task Master into the server involved extensive changes. When upgrading to LoggerNet 4.2 from a previous version, an attempt will be made to import all previously configured tasks. However, imports have only been tested back to LoggerNet 3.4.1. After upgrading from any previous version of LoggerNet, verify that all of the tasks have imported correctly.
   • Calendar-based scheduling has been added to the Task Master. This allows for non-interval task execution (including data collection). See Example #3 in the Task Master Help for an example of calendar-based data collection.
   • A Constant Customization feature has been added to the CRBasic Editor. This allows the definition of values for one or more constants in a program prior to performing a conditional compile. The constants can be set up with an edit box, a spin box field for selecting or entering a value, or a list box. A step increase or decrease can be defined for the spin box, as well as maximum and minimum values.
   • The CRBasic Editor now offers a Save and Open Display Settings feature. Display settings affect the look and feel of the CRBasic Editor. This includes font and background, as well as syntax highlighting.
   • View Pro has a new View Record option in the right-click menu that can be used to view an entire record in a new window.
3. Why don’t mixed-array datalogger tables show up in the Data Filer table selection window?

   LoggerNet doesn’t know which tables are available in mixed-array dataloggers unless the program is identified by associating it. If no tables show up in the Data Filer table selection window, check that there is a program associated with the datalogger in LoggerNet. This can be done on the Program tab of the LoggerNet Setup screen. Also, verify these two things:

   1. Scheduled collection is enabled (on the Schedule tab of the LoggerNet Setup screen).
   2. FS Area 1 is enabled (and FS Area2 if memory is being specifically allocated to it) for collection. This information is found on the respective tabs in the LoggerNet Setup Screen.
4. Will a patch for LoggerNet 4.0 apply to LoggerNet Admin 4.0 as well?

   Yes. The patch should update the install to version 4.1 Admin, as long as the previous installation was installed as Admin with the correct license key.

5. How can LoggerNet Admin be stopped from running as a service?

   Deselect Run as Service from Start Menu | Programs | Campbell Scientific | LoggerNet | LoggerNet Service Manager.

6. If LoggerNet Admin is installed on a server that is configured to have multiple users logged in at the same time, how can more than one user have LoggerNet open at a time?

   The server/client architecture of LoggerNet allows for multiple clients to access the LoggerNet server.

7. Can LoggerNet be configured to run as a service without purchasing LoggerNet Admin?

   No. Only LoggerNet Admin has the capability of running LoggerNet as a service.

8. How can LoggerNet be upgraded to LoggerNet Admin in the most seamless way possible?

   To upgrade from LoggerNet to LoggerNet Admin, the correct upgrade path is to order the LoggerNet Admin Upgrade (LOGGERNETADM/U), which allows one copy of LoggerNet or LoggerNet Admin to be upgraded to the current version of LoggerNet Admin.

9. Does upgrading a LoggerNet installation to a LoggerNet Admin installation remove scheduled data collection rules, the stations, or any other settings?

   All data and settings should remain following the upgrade from LoggerNet to LoggerNet Admin. The file formats and locations are exactly the same between the two products. No information in the configuration should be lost or reset.

10. Does LoggerNet Admin have a user name? If so, is there a way to change it to something that will be recognized by a corporate network?

    When LoggerNet Admin is set up, the user is asked to enter a user name. The user can enter something that is recognizable by a corporate network.