LoggerNet DB/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 MoreLNDB/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.
Product | Compatible | Note |
---|---|---|
21X (retired) | ||
CR10 (retired) | ||
CR1000 (retired) | ||
CR1000X | ||
CR10X (retired) | ||
CR200X (retired) | ||
CR206X (retired) | ||
CR211X (retired) | ||
CR216X (retired) | ||
CR23X (retired) | ||
CR295X (retired) | ||
CR300 | ||
CR3000 (retired) | ||
CR310 | ||
CR350 | ||
CR500 (retired) | ||
CR5000 (retired) | ||
CR510 (retired) | ||
CR6 | ||
CR800 (retired) | ||
CR850 (retired) | ||
CR9000 (retired) | ||
CR9000X (retired) |
Product | Compatible | Note |
---|---|---|
CSIWEBS | ||
CSIWEBSL | ||
CSIWEBSL/U | ||
CSIWEBS Upgrade | ||
LoggerNet | ||
LoggerNet Admin | ||
LoggerNet Admin Upgrade | ||
LoggerNet Upgrade | ||
RTMCPRO | ||
RTMC Pro 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 LoggerNet DB Upgrade: 25
Expand AllCollapse All
Check C:\Campbellsci\LNDB\logs.
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.
The easiest way to get the data into LNDB is to store the information in the LoggerNet data cache (or, for the information to be in a format that looks like a data logger data file to LNDB so that it can be imported).
LNDB currently requires that all data logger table columns have a corresponding database table column. There are currently three options when table definitions change:
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.
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.
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.
Table names in LNDB are automatically generated and cannot be changed.
No. LNDB works independently of Baler.
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).
We've updated our privacy policy. Learn More
Update your cookie preferences. Update Cookie Preferences