LNDB LoggerNet Database Software
Designed for Data Network Administrators
Push data from LoggerNet data cache to relational databases
weather applications supported water applications supported energy applications supported gas flux and turbulence applications supported infrastructure applications supported soil applications supported

Overview

LoggerNet DB (LNDB) is ideally suited for transitioning data from LoggerNet’s data cache to a relational database of your choice. Publishing user-selected LoggerNet collected data to these relational databases enables data administrators to share their data with a large customer base across various platforms and methods. Those platforms could include custom websites (including those developed with RTMC and CSIWEBS), custom data reporting systems, data warehousing, and customer software (web and desktop) applications. This application is for data network administrators that want to push their valuable LoggerNet data into relational databases and have that data published in real time (as often as the data is collected).

The low-cost LNDB software is simple to set up and administer and gives you the flexibility you need for your organization. Most users can have the software installed and LoggerNet data uploading to their relational database in less than 20 minutes' time (assuming the database and LoggerNet are set up and proper credentials are issued to the data manager). After setup, LNDB runs as a service on Windows and continues to reliably push LoggerNet data to the relational database, allowing you to focus your time and energy on other projects.

Read More

Benefits and Features

  • Reliably moves data from user-selected LoggerNet data caches into tables in a relational database
  • Can be used to import data from user-created data files into a relational database table
  • Exports data from a database table into a data file
  • Includes QuickReports application to design simple report from an LNDB database
  • Allows users to review database data in real time
  • Monitors the LNDB data ingestion engine
  • Simple to set up and easy to use
  • Saves data managers money by not having to hire a database administrator and a custom software developer

Technical Description

LNDB can be run as a service on the workstation or server. This ensures that when the computer is restarted, LNDB is automatically started without human intervention. This allows data ingestion from LoggerNet to the relational database to continue after unforeseen power issues or automatic operating system updates.

LNDB Manager is the main client screen used to configure the LNDB engine. It is used to determine which LoggerNet system to connect to and which database is used. LNDB Manager can also be used to watch the status of various data collections and data push events. Data can be reviewed in tabular columns directly from the database without having to use database-specific tools. Status messages and Significant Events can be viewed using LNDB Manager as well.

DBExport is a database client that can be used to retrieve data directly from the relational dabase. Users can pull all the data from the database or select data using data ranges. EDExport also has the ability to check for and inform the user of missing records for the exported data. Exported file formats include TOA5, TOACI1, TOB1, CSIXML, and Custom CSV.

DBImport is a database client that can be used to import data from existing data files. The user can ingest the data into an existing table or create a new one in the database. These data files can be either those created by LoggerNet or database files from other sources or data loggers.

QuickReports is another database client that can be used to generate simple reports and graphs with data from the relational database.

Images

Specifications

Operating System Windows 11 or 10 and Windows Server versions 2012 R2, 2016, or 2019. (Users using Windows Server with security policies other than the default policies will need to work with their IT administrations to resolve any security issues.)
Required Framework This software requires the Microsoft .NET 4.6.2 (or better) Framework to run properly. To use the reporting functions of LNDB 2.0, Microsoft .NET Framework 3.5 also needs to be installed. If the required version of the .NET framework is not already installed on your computer, it can be obtained from the Microsoft Download Center.

Compatibility

Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.

Dataloggers

Product Compatible Note
CR1000 (retired)
CR1000X
CR200X (retired)
CR216X (retired)
CR300 (retired)
CR3000
CR310
CR350
CR5000 (retired)
CR6
CR800 (retired)
CR850 (retired)
CR9000X (retired)

Software

Product Compatible Note
CSIWEBS
CSIWEBS/U
LoggerNet
LoggerNet Admin
LoggerNet Admin Upgrade
LoggerNet/U
RTMCPRO
RTMCPRO/U

Additional Compatibility Information

Supported Databases

LNDB has been tested and shown to work with the following databases:

  • Microsoft® SQL Server® (Express, Standard, and Enterprise) 2005–2019
  • Microsoft® SQL Server® Compact 3.5 SP2 (installed with LNDB)
  • MySQL 5.0–8.0 (with an appropriate 32-bit ODBC database driver; for example, MySQL 5.0 or 5.1 with MySQL 3.51.27 or 5.1.6 ODBC database driver, note that earlier versions of 5.x ODBC database drivers have known issues; MySQL 5.6 with MySQL 5.3 ODBC database driver)
  • Oracle Database 12c Release 1 (12.1.01) and 18c (18.1.0)
  • PostgreSQL 9.4 through 12

Note: LNDB may work with other versions of SQL Server Express, SQL Server Compact, MySQL, Oracle Database, or PostgresSQL.

Computer Requirements

LNDB runs on Windows 11 or 10 and Windows Server 2012 R2*, 2016*, or 2019*.

*Users using Windows Server with security policies other than the default policies will need to work with their IT administrations to resolve any security issues.

Resources and Links

Downloads

LNDB Trial v.2.0 (45.7 MB) 01-04-2019

A fully functional 30 day trial version of LNDB (LoggerNet DataBase) software.

Note: This application requires the Microsoft .Net 3.5 and .Net 4.6.2 Frameworks.  If they are not already installed on your computer,  they can be obtained from the Microsoft Download Center.

FAQs for

Number of FAQs related to LNDB: 26

Expand AllCollapse All

  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. Is there a stored copy of LNDB “Significant Events”?

    Check C:\Campbellsci\LNDB\logs.

  3. Does LNDB work on any server-class OS, or is it limited to a desktop OS?

    LNDB has been tested to run on Windows 10 and 11. 

    Because Windows Server installations are all uniquely configured, it is nearly impossible for our application engineers to replicate a customer’s implementation environment at our facility.

    To test whether LNDB will work in a particular Windows Server environment, download the 30 day trial versions of LoggerNet and LNDB. Each is available in the Downloads section of the product page: LoggerNet and LNDB.

  4. What might be the cause of a “Failed to connect to localhost” message when running LNDB Manager?

    Most likely, the LoggerNet server is not running. If LoggerNet Admin is used, the LoggerNet server can run as a service. If LoggerNet is used, the program needs to be running for the server to be running.

    If a user is logging in to a remote LoggerNet server, not only does the LoggerNet server need to be running on the remote machine, but the user must be able to reach the machine through the network and log in to the machine if access is restricted.

  5. Which port needs to be open to enable LNDB to communicate with the LoggerNet server?

    The LoggerNet default port number is 6789. If a command line argument has been used to change the LoggerNet default port number, this alternate port number must be open.

    Note: The alternate port number must be specified in the Login to LoggerNet Server dialog box when entering the Server Address (for example, 192.168.7.123:6700).

  6. How can the Windows Authentication that LNDB uses be changed from a host name (computer name) to a user name?

    The LNDB service runs under a local system account by default, which may be why it uses the computer name. Go to Control Panel | Administrative Tools | Services and set it to run under a user name.

  7. How does LNDB handle duplicate records?

    LNDB uses two fields as primary keys: the record number and time stamp. If the record number and time stamp are both duplicated, the record is discarded. If only the record number or only the time stamp is duplicated, LNDB should import the record. 

  8. Can LNDB automatically connect to a remote LoggerNet server?

    With LoggerNet and LoggerNet Admin, remote connections are not enabled by default. They have to be enabled in the LoggerNet Toolbar. Right-click anywhere on the toolbar, and, in the resulting dialog box, verify that Allow Remote Connections is selected.

  9. Is there a way to establish connections between LNDB and two different database hosts at the same time?

    Not at the same time. Currently, a user would have to manually switch back and forth between the database hosts periodically using the File menu Select Database... option to keep them both updated.

  10. Can LNDB be used to upload data gathered from LoggerNet to a remote Linux MySQL server?

    Yes, but LNDB can only run on a Windows platform. Run LNDB on the same Windows host on LoggerNet, and post the data to MySQL running under Linux. Configure LNDB (running on Windows) to point to the MySQL server running on Linux.

Visit the FAQ Library

Case Studies

delaware river: bridge health
Delaware River: Bridge Health
Intelligent Infrastructure Systems, a Pennoni company, was contracted to design and install an efficient structural-health......read more
Explore All Case Studies

Privacy Policy Update

We've updated our privacy policy.  Learn More

Cookie Consent

Update your cookie preferences.  Update Cookie Preferences