LNDB LoggerNet Database Software
Valuable Tool
Use standard database tools on LoggerNet data
weather applications water applications energy applications gas flux & turbulence applications infrastructure applications soil applications

Overview

Current Version: 1.3

LNDB is an application that enables you to easily move data from a LoggerNet data cache into a database such as Microsoft SQL Server or MySQL. Then you can use industry-standard software to access and query your data for reports. LNDB also comes with QuickReports, an application that allows you to generate simple reports from an LNDB database with just a few mouse clicks.

Read More

Benefits and Features

  • Moves data from selected LoggerNet tables into a database
  • Imports data from a data file into a database table
  • Exports data from a database table into a data file
  • Includes QuickReports application to design simple reports from an LNDB database
  • Allows you to review database data
  • Monitors the LNDB Engine

Images

Detailed Description

LNDB has two main components: LNDB Manager and LNDB Engine. LNDB Manager is used to set up a database and select the data logger data tables that will be stored in the database. It also provides tools to monitor the LNDB Engine and to review the database data.

LNDB Engine runs as a service and sends the selected data from the LoggerNet data cache to the database. Additionally, LNDB includes utilities for importing and exporting data, and generating simple reports from your database data.

Specifications

Current Version 1.3
Operating System Windows 10, 8, or 7

Compatibility

Note: The following shows notable compatibility information. It is not a comprehensive list of all compatible or incompatible products.

Data Loggers

Product Compatible Note
21X (retired)
CR10 (retired)
CR1000
CR1000X
CR10X (retired)
CR200X (retired)
CR206X (retired)
CR211X (retired)
CR216X (retired)
CR23X (retired)
CR295X (retired)
CR300
CR3000
CR310
CR500 (retired)
CR5000 (retired)
CR510 (retired)
CR6
CR800
CR850
CR9000 (retired)
CR9000X

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–2016
  • Microsoft® SQL Server® Compact 3.5 SP2
  • MySQL 5.0–5.7 (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)

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

Computer Requirements

LNDB runs on Windows® 10, 8, or 7.

Downloads

Getting Started with LNDB Tutorial (pdf format) v.- (4.58 MB) 10-18-2010

This tutorial shows how to move data into a database using LNDB. The report generation capabilities of QuickReports are introduced and we show how to use a database as a data source in RTMC Pro.


LNDB Patch v.1.3 (41.8 MB) 12-22-2017

Upgrades LNDB 1.x and 1.2 to 1.3.

Note: This application requires the Microsoft .Net 4.0 Framework.  If it is not already installed on your computer,  it can be obtained from the Microsoft Download Center.

View Update History

LNDB Trial v.1.3 (41.8 MB) 12-22-2017

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

Note: This application requires the Microsoft .Net 4.0 Framework.  If it is not already installed on your computer,  it can be obtained from the Microsoft Download Center.

Frequently Asked Questions

Number of FAQs related to LNDB: 25

Expand AllCollapse All

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

  2. Table names in LNDB are automatically generated and cannot be changed.

  3. LNDB currently requires that all data logger table columns have a corresponding database table column. There are currently three options when table definitions change:

    1. Stop Storing Data (The user can manually alter/archive the database table.)
    2. Archive Database Table
    3. Modify Database Table (New columns are added, and old columns are orphaned. If the database column data type is not what is expected, an archive occurs.)
  4. No. For information about creating live connections to Microsoft SQL Server, Oracle, or MySQL data sources with FileMaker Pro’s External SQL Data Source feature, visit the FileMaker website.

  5. LNDB has been tested to run on Windows XP, Windows Vista, and Windows 7. LNDB and its components have not been formally tested and certified on Windows 8 platforms. We are aware of customers using Campbell Scientific software products with Windows 8 successfully.

    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.

  6. One method is to use Custom Collect to specify a range of data and then store the data to a different file. Alternatively, if LNDB is set up to store data in a database, a range of data can be pulled out and stored in a separate data file. These two methods, however, are manual ones.

  7. No. LNDB works independently of Baler.

  8. If the stations are all accessed by the same instance of LoggerNet, LNDB can collect table data from multiple stations. In the LNDB Manager, highlight the station in the left tree, and select the checkboxes next to the desired table names.

    Note: LNDB can only communicate with one instance of LoggerNet.

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

Case Studies

Delaware River: Bridge Health
Intelligent Infrastructure Systems, a Pennoni company, was contracted to design and install an efficient structural-health......read more

Privacy Policy Update

We've updated our privacy policy.  Learn More