Current Version: 2.0
LNDB/U is an upgrade to the latest version of our LoggerNet DB (LNDB) software. You must have an earlier version of LNDB to qualify for the upgrade.
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
LNDB/U allows users who have an earlier version of LNDB to upgrade to the latest version of LNDB.
|Operating System||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.)|
Note: The following shows notable compatibility information. It is not a comprehensive list of all compatible or incompatible products.
|LoggerNet Admin Upgrade|
LNDB has been tested and shown to work with the following databases:
Note: LNDB may work with other versions of SQL Server Express, SQL Server Compact, or MySQL.
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.
Number of FAQs related to LNDB/U: 25
Expand AllCollapse All
Table names in LNDB are automatically generated and cannot be changed.
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.
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.
There are two main components of the LNDB application:
Yes, as part of the SDK—the CSIDataSource control.
No. It can only be changed using the Login to LoggerNet Server dialog box. The Login to LoggerNet Server dialog box opens automatically after LNDB is installed. It can also be opened at any time from the File | Select LoggerNet Server menu item or by double-clicking the LN Connection Status Label on the Status Bar.
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.
No. LNDB works independently of Baler.
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.