LoggerNet Software de soporte para datalogger

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. 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.

3. What changed in LoggerNet from 3.1 to 3.1.1?

   Changes

   • Enhanced performance of the CRBasic Editor when checking for matching parentheses.

   Bug Fixes

   Note: The following fixes only apply to customers who are upgrading to LoggerNet 3.1.1 from LoggerNet 2.x:

   • Data file paths for table-based dataloggers appeared to be distorted in the Setup Screen.
   • Numeric Monitor displayed inlocs from some table-based dataloggers incorrectly.
4. Is there a way to convert CR23X program files to CR3000 program files?

   Yes. We have created a software application, Transformer, to help migrate CR23X program files to CR3000 program files. Transformer is available within LoggerNet 3.2 and higher.

   • From the Windows Start Menu, navigate to LoggerNet3.0 | Utilities | Transformer.
   • In LoggerNet 4.x, from the main LoggerNet window, navigate to Program | Transformer.

   Transformer uses a .csi or .dld file created in Edlog to generate CRBasic code for a CR3000. A side-by-side comparison of the two programs is provided along with an action log that highlights parts of the program that may need attention or additional editing in CRBasic.

5. What is new for LoggerNet Version 4?

   • LoggerNet 4.0 introduces a new look and feel to the LoggerNet Toolbar. Applications are divided into categories to make navigating the Toolbar easier. You can also organize a Favorites category for the applications that you use most often.
   • A new file viewing application, View Pro, is introduced in which LoggerNet 4.0. View Pro allows you to graph data in a variety of formats including Line Graph, X- Y Plot, Histogram, Rainflow Histogram, and FFT(2D or 3D).
   • Another new application, the Network Planner, is included. The Network Planner is a graphical application that assists the user in designing PakBus datalogger networks.

   LoggerNet 4.0 includes many additional changes. See the preface to the LoggerNet manual for more details on what is new in LoggerNet 4.0 and each individual application.

6. What changed from LoggerNet 2.x to LoggerNet 3.1?

   New features

   • Support for the CR1000 throughout the software, including the Short Cut program generator
   • EZSetup client
   • Added a TroubleShooter client to help identify communications problems. This includes a new Communication Test tool.
   • Users can check and set data logger clocks, and send programs from the Setup Screen.
   • Status Monitor Screen added a communications history display; sorting by statistic can be done by clicking the column header.
   • A new LogTool client provides access to the log displays. Users can limit messages to specific devices.
   • RTMC added “auto-tabbing” and new time stamp formatting.
   • Added a new utility called Device Configurator (DevConfig) to set the various settings in data loggers and communications peripherals. Settings can be saved to a file and loaded to other devices.
   • Short Cut included various refinements such as drag-and-drop for output selection, and a 50 or 60 Hz noise rejection option.
   • A new Transformer tool is provided to convert CR10X (mixed-array OS only) Edlog program (.dld or .csi) to a CR1000 CRBasic program (.CR1).

   Changes

   • Reorganized Setup Screen to distinguish between settings most users would need to edit and settings where the default usually works and which users typically won’t need to change.
   • Integrated dynamic IP addressing in AirLink Ravens into Server settings.
   • Server now locks the network when any client is trying to edit it to prevent “dueling clients.”
   • Made PakBus ports independent, allowing the user to bridge or not bridge them to create sub-networks.
   • Connect Screen functions work without having to "connect" to the data logger first.
   • Numeric and Graph Screens update automatically for some types of data without being “connected” if the data is being collected via schedule.
   • PakBus Graph is now more graphical in nature and allows easier access to device settings.
   • LoggerNet Server offers a variety of refinements, including reintroduced support for RF95T base and remote devices for BMP1 networks, standalone PakBus routers assigned to each PakBus port, a new "hangUpDelay" setting, the ability to “lock” a device when its settings are being edited to prevent other clients from “dueling” for those settings, accepting one-way data notifications from PakBus data loggers, and accepting UDP packets from an AirLink modem (Raven or PinPoint) containing a new dynamic IP address.
7. Why might the numeric and graph displays (accessed from the LoggerNet Connect screen) no longer update?

   If communication is interrupted or intermittent, LoggerNet may stop updating the Table Monitor, Numeric Display, and Graphs. When this occurs, a button on the display that is normally titled Stop (to stop the update) changes to Start, and the button must be pressed to resume the update. Also, check the update interval on the display, as it may be set to a higher value than expected.

8. How can a data logger be switched out (for example, from a CR800 to a CR1000) in LoggerNet?

   Follow these steps:

   1. In the Setup screen, record the pertinent data from the Schedule and Data Files tabs. 
   2. Delete the listed data logger.
   3. Add the new data logger. 
   4. Adjust the settings on the Schedule and Data Files tabs to match what was being done previously.
      • If the settings are complicated, review the Help menu from the Setup screen to learn more about the option in LoggerNet 4.2 to Copy Device Settings in the Tools menu.
9. What's new in LoggerNet 4.1?

   • One of the main efforts in the development of LoggerNet 4.1 has been the ability to use LNDB databases with View Pro. The ability to lock the timestamp column on the left of the data file has also been added to View Pro. This keeps the timestamp visible while scrolling through columns of data. 
   • The Device Configuration Utility has a new off-line mode which allows viewing settings for a certain device type without actually being connected to a device.
   • The CRBasic Editor now has the capability to open a read-only copy of any file. This provides the ability to open multiple copies of a program and examine multiple areas of a very large program at the same time. In addition, an instruction can be continued onto multiple lines by placing the line continuation indicator (a single space followed by an underscore “_”) at the end of each line that is to be continued. Also, bookmarks in a CRBasic program are now persistent from session to session.
   • In the Troubleshooter and the Setup Screen (Standard View), it is now possible to click on a potential problem to bring up a menu that enables the user to go to the Setup Screen or Status Monitor to fix the potential problem, bring up Help describing the problem, or in some cases, fix the problem directly.
   • Campbell Scientific’s new wireless sensors have been added to the Network Planner.
   • Statistics (average, minimum, maximum, and number of data points) can now be viewed for each data value being displayed in a Connect Screen graph. All of the Connect Screen’s displays (table monitor, numeric displays, and graphs) now show the units that have been assigned to the data values.
   • Split has a new “Time Sync to First Record” option that can be used with the time-sync function to avoid blank lines at the start of the output file. Also, a range of time values rather than a single time can now be entered in a Split Copy Condition.
   • CardConvert can now be run from a command line without user interaction.
   • An option to provide feedback on LoggerNet has been added to the LoggerNet Toolbar’s Help menu.
   • Miscellaneous other changes and bug fixes have also been implemented in this version.

   Note:  Beginning with this version of LoggerNet, Windows 2000 is no longer supported.

10. Can LoggerNet perform scheduled data collection on two data loggers at the same time?

    Yes, but only if the communications links to the data loggers allow simultaneous communication. For example, two mixed-array data loggers can be contacted simultaneously using two different COM ports; however, if they are accessed via the same COM port, LoggerNet can connect to only one at a time.