Image Not Available

A LoggerNet Version for Linux
weather applications supported water applications supported energy applications supported gas flux and turbulence applications supported infrastructure applications supported soil applications supported


Current Version: 4.5

LoggerNet Linux provides a solution for those who want to run the LoggerNet server in a Linux environment. The package includes a Linux version of the LoggerNet server. A Windows version of LoggerNet Remote is required. The Windows-based client applications in LoggerNet Remote are run on a separate computer, and they are used to manage the LoggerNet Linux server.

Read More

Benefits and Features

  • Lets you run a LoggerNet server in a Linux environment


Current Version 4.5
Operating System Windows 10, 8, or 7 (for LoggerNet Remote)
RPM Distribution Red Hat (32 and 64 bit)
Debian Distribution 32 and 64 bit


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

Data Loggers

Compatible Note
21X (retired)
CR10 (retired)
CR10X (retired)
CR200X (retired)
CR206X (retired)
CR23X (retired)
CR295X (retired)
CR500 (retired)
CR5000 (retired)
CR510 (retired)
CR9000 (retired)
CR9000X (retired)

Additional Compatibility Information


The disk with the LNLinux Server contains a Debian distribution and a Red Hat RPM distribution. Each distribution includes a 32-bit and a 64-bit version. 

LoggerNet Remote is required for use with LNLinux. The LoggerNet Remote clients used to manage the LNLinux server run on an Intel-based computer with a Microsoft Windows operating system. The recommended minimum computer configuration for running the LoggerNet Remote clients is Windows 7. The LoggerNet Remote clients also run on Windows 8 and 10.


The LoggerNet server provides communications with the data loggers over various mediums including serial ports, TCP/IP connections, and Linux compatible phone modems.

Articles and Press Releases

FAQs for

Number of FAQs related to LNLINUX: 6

Expand AllCollapse All

  1. LoggerNet for Linux should run on most distributions with base distributions of Red Hat or Debian.

  2. Follow these steps:

    1. On the Windows computer, open the LoggerNet Setup screen.
    2. In the Backup menu, select the Manual Backup option to create a backup of the network.
    3. On the same or different Windows computer, use LoggerNet Remote software to connect the Setup screen to the LoggerNet for Linux server (File | Select Server).
    4. Restore the network backup (Backup | Restore Network).
    5. Review the restored settings in the Setup screen. Some settings (such as COM ports, modems, data file paths, etc.) may need to be adjusted.
  3. Yes. LoggerNet for Linux (LNLinux) allows the LoggerNet server to be run on a Linux computer. The LoggerNet server collects and stores the data, while setup and management of the network are easily handled from a Windows computer running LoggerNet Remote or, rather tediously, using Cora Command on the Linux computer.

  4. When a LoggerNet client, such as the Connect screen (in LoggerNet Remote) needs to connect to a remote LoggerNet Admin or LoggerNet Linux installation, the default port used is 6789.

    The default port can be altered using the command line argument ipport. The following is the explanation from LoggerNet Help:

          Command line arguments allow you to change LoggerNet's default behavior when it is started from a shortcut.
          /IPPORT=XXXXX Causes the server to use port XXXXX for TCP/IP communications with clients. This is useful if some other software is using LoggerNet's default port of 6789. Usage:
               "C:\Program Files\CampbellSci\LoggerNet\ToolBar.exe" /ipport=12345


  5. No, but contact Campbell Scientific to discuss the options.

  6. The blog article "How to Navigate the World of Software Upgrades, Patches, and Trials" explains the difference between patches (free of charge) and upgrades (for a fee). This example quickly shows the difference between an upgrade and a patch:

    Upgrade Patch

    Major version change, such as 1.3 to 2.0

    Minor version change, such as 1.3 to 1.4

    Typically requires purchase for a fee

    Free of charge