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

Overview

Current Version: 1.1

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

Technical Description

LNDB has two main components: LNDB Manager and LNDB Engine. LNDB Manager is used to set up a database and select the datalogger 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

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

Dataloggers

Product Compatible Note
21X (retired)
CR10 (retired)
CR1000
CR1000X
CR10X (retired)
CR200X (retired)
CR211X (retired)
CR216X (retired)
CR23X (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.

Related Documents

Downloads

Getting Started with LNDB Tutorial (pdf format) v.- (4.39 MB) 18-10-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 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.

Related FAQs

Number of FAQs related to LNDB: 24

Expand AllCollapse All

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

  2. No. The purchased version is separate from the trial version. Uninstall the trial version, and install the purchased version.

  3. Yes, as part of the SDK—the CSIDataSource control.

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

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

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

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

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

  9. LNDB was designed to be a simple tool to facilitate getting data from the LoggerNet data cache to an SQL-based database. For users who need more advanced options, SDKs, such as LoggerNet-SDK and LoggerNetS-SDK, are available.