Measurement and Control Products for WEATHER Measurement and Control Products for WATER Measurement and Control Products for ENERGY Measurement and Control Products for MACHINES Measurement and Control Products for STRUCTURES Measurement and Control Products for EARTH
Robust, Versatile
Contains advanced programming and communication capabilities
 
 
 
 
 
Image Gallery

General Support

User Forum

Visit the Campbell Scientific Forum to submit your question to users around the world.

Ask an Expert

Ask an Expert using our simple form and we'll pass it along to one of our experts.

Call Us

Our technical support experts are ready to answer your questions. Our support numbers are:

Orders 435.227.9090
435.227.9091 (fax)
Technical Support 435.227.9100
US Sales 435.227.9120
International Sales 435.227.9140
Accounts Receivable 435.227.9092
Repairs 435.227.9105
Main 435.227.9000
435.227.9001 (fax)

Videos & Tutorials

CRBasic Features - 11:09
CRBasic Help System - 3:33
Common CRBasic Errors and How to Fix Them - 12:07
Troubleshooting Cellular Modems - 15:29
Getting Started with RTMC - 10:32
RTMC Pro - Real Time Monitoring and Control - 10:55
Tip - Changing Variables in Table Monitor and Numeric Display - 2:33
Using Variable Arrays, Repetitions, and Aliases - 6:50

Downloads

LoggerNet Patch v.4.2.1 (196 MB) Add to List

This patch will upgrade LoggerNet, LoggerNet Remote or LoggerNet Admin version 4.0 and newer to 4.2.1. A version of LoggerNet 4.x must be installed on the computer. 

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


View Revision History
LoggerNet Trial v.4.2.1 (207 MB) Add to List

This is a fully functional 30 day trial of the standard version of LoggerNet.

Current LoggerNet users: It is recommended that you install the trial on a computer other than the one running your existing LoggerNet. If that is not practical, we strongly recommend you back up the LoggerNet working directory to prevent backward compatibility issues if you revert to a previous version. To revert you must re-install LoggerNet using the original disk and software key.

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


View Revision History
What's new in LoggerNet 4 Tutorial (exe format) v.- (12.9 MB) Download Now

LoggerNet 4.0 was released in August of 2009. This tutorial demonstrates some of the new features and enhancements. Two new applications, ViewPro and the Network Planner, are introduced.

What's new in LoggerNet 4 Tutorial (pdf format) v.- (8.46 MB) Download Now

LoggerNet 4.0 was released in August of 2009. This tutorial demonstrates some of the new features and enhancements. Two new applications, ViewPro and the Network Planner, are introduced.

NOTE: Adobe Reader 9 or later is needed to view this tutorial.

LoggerNet Patch 3.4.1 (Large) v.3.4.1 (74.2 MB) Add to List
This patch upgrades LoggerNet version 3.0 and newer to 3.4.1. A version of LoggerNet 3.x must be installed on the computer. If you are using a version of LoggerNet 2.x, you must purchase an upgrade.

NOTE: Starting with LoggerNet 3.2, the included RTMC data display client has moved from Version 1.x to 2.x. This will require you to also upgrade from RTMC Web Server 1.x or RTMC Run-time 1.x if you also use those products.
View Revision History
LoggerNet Patch 3.4.1 (Small) v.3.4.1 (68.7 MB) Add to List
If you already have LoggerNet 3.2, 3.2.1, 3.2.2, 3.3, 3.3.1 or 3.4 installed you can download this smaller version of the patch. (Patches from 3.2, 3.2.1, 3.2.2, 3.3, 3.3.1 or 3.4 to 3.4.1 only.)
LoggerNet 4.0 German v. (980 KB) Add to List

German language files for LoggerNet 4.0.

LoggerNet Spanish v.4.1 (902 KB) Add to List
Spanish language files for LoggerNet 4.1.

FAQs

What is the difference between LoggerNet and LoggerNet Admin?

LoggerNet Admin was designed specifically for working with large networks. It has features that are not available in the regular LoggerNet software. For example, the ability to run LoggerNet as a service is a feature of LoggerNet Admin. In addition, the ability to create custom views is available in LoggerNet Admin only. The standard LoggerNet software has only the Network view or the Stations view.

What are the options for purchasing LoggerNet 4?

A customer who owns any version of LoggerNet or PC400 can upgrade to LoggerNet version 4 by ordering LoggerNet/U.

A customer who does not own any version of LoggerNet or PC400 must purchase the full version of LoggerNet.

Where is there information about the revisions to the LoggerNet software?

The LoggerNet revision history information can be found through the “Software and OS Revision Histories” web page. Revision history information is available for LoggerNet patches and upgrades, as well as for the trial versions of the software.

Are LoggerNet upgrades free?

Within a version, such as an upgrade from a version 1.0 to a version 1.1, upgrade patches are available for download, free of charge, from our website. A link to the patch can be found in the Downloads section of the Support tab on the LoggerNet product page.

To upgrade from one major version to the latest version (for example, version 1.3 to 2.0), the purchase of LOGGERNET/U (Upgrade to Current Version of LoggerNet) is required.

How are PC400, LoggerNet, and LoggerNet Admin similar and different?
  • PC400 is simple software for the user who has only a few stations to manage, and who does not require complex communications links or scheduled data collection.
  • LoggerNet provides support for more complicated networks and allows for data collection to occur on schedule.
  • LoggerNet Admin contains additional tools which are useful for those managing large networks of dataloggers, or for those who need to run LoggerNet as a service.

For comparative descriptions, see the “Software Overview” brochure.

Is it possible to upgrade from PC200W to the current version of LoggerNet?

There is no upgrade path from PC200W to LoggerNet. Only licensed copies of LoggerNet qualify for upgrade pricing to the current version.

Is there a version of LoggerNet that will run on a Linux computer?

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.

Does Campbell Scientific software contain spyware?

No. The libexpat.dll module used by some of our applications is sometimes identified as spyware by anti-spyware programs. It is an open-source XML parser, not spyware.

Is LoggerNet software needed to download the data from a datalogger remotely?

Campbell Scientific has several software applications that can be used to collect data from a datalogger, including PC200W, PC400, and LoggerNet.

Can a single copy of LoggerNet be purchased and installed on a laptop PC and a desktop office PC, or are two copies of LoggerNet needed?

For the current licensing information, refer to the LoggerNet Instruction Manual. Two copies of LoggerNet would need to be purchased for use on the two computers.

Campbell Scientific offers free PC200W software (available for download) that enables the following:

  • Connecting to a datalogger through a serial port (including direct connect, short haul modems, or radios)
  • Monitoring data
  • Collecting data
  • Sending or retrieving a program

There is no restriction as to how many machines the PC200W software can be installed on.

Does LoggerNet include LNDB and RTMC?

A basic version of RTMC, called RTMC Development, is included with LoggerNet. The full version of RTMC is called RTMC Pro and has many additional features, including more screen components, the ability to use more data sources (including LNDB databases and data files), the ability to generate reports, and the CSI Web Server.

LoggerNet does not include LNDB, which is purchased separately.

How much memory does LoggerNet have?

The datalogger has its own memory, but LoggerNet holds a cache of the data it has collected from the datalogger, which is normally about twice the size of the datalogger’s data capacity.

Can backups from older versions of LoggerNet work on newer versions?

Typically, a backup from an older version of LoggerNet will work on a newer version, but there will be issues trying to go from a newer version back to an older version.

Is there a Macintosh version of LoggerNet?

There are no plans for a Mac version of LoggerNet at this time. There are customers running LoggerNet in a Windows environment on a Mac, such as in Parallels.

Is Baler needed to use LNDB with LoggerNet?

No. LNDB works independently of Baler.

How long does it take to install LoggerNet?

The LoggerNet application is distributed on CD media and can be installed in minutes.

Are multiple instances of LoggerNet needed to configure LoggerNet to use LNDB for connection to multiple stations?

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.

Does LoggerNet stay connected to the datalogger after the scheduled collection is finished?

If only scheduled collection is running, LoggerNet will connect to the datalogger, collect the data, and then disconnect automatically.

Is there a trial version of LoggerNet for Linux?

No, but contact Campbell Scientific to discuss the options.

How can the settings be migrated from LoggerNet on a Windows computer to LoggerNet for Linux on a Linux computer?

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 the LoggerNet Remote software that was included with LoggerNet for Linux 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.
Does a user need to be permanently logged in to LoggerNet for the software to run and data to continue to be received?

LoggerNet does not run as a service. Therefore, it needs to be running to do its data collection. LoggerNet Admin does have the capacity to run as a service, and it can collect data when no one is logged in to the computer.

After installing an upgrade to the current version of LoggerNet, why does the Toolbar no longer show all the buttons?

There is a difference between the Toolbar initialization files used in earlier 3.x versions of the software and more recent versions.

To resolve this, close LoggerNet. Go to C:\Campbellsci\LoggerNet\sys\inifiles and delete the Toolbar.ini file. When LoggerNet is reopened, the Toolbar should display the default buttons.

When trying to start LoggerNet, what might cause the "Unable to start program because the Campbell Scientific communications server is already running" message?

A program on the computer is already using TCP/IP port 6789, or the security software (virus protection or firewall software) is blocking the use of that port. The Campbell Scientific communications server listens for, and communicates with, server clients (for example, RTMC Run-Time, the LoggerNet Status screen, the LoggerNet Connect screen) on TCP/IP port 6789 by default.

Use Microsoft’s netstat or some other TCP/IP utility to determine if another application is using port 6789.

  • If the TCP/IP utility shows no application using port 6789, the security software is probably blocking the port. Define an exception for LoggerNetService.exe in the security software to resolve the issue.
  • If the TCP/IP utility does show another application using port 6789, close the application or configure it to use a different port. If the application cannot be closed or reconfigured to use a different port, use the LoggerNet Toolbar command line switch toolbar.exe /ipport=xxxxx (where "xxxxx" is the new port number) to configure LoggerNet to use a different port.
How can data that has been transmitted from a datalogger to LoggerNet then be transmitted to a webhost that displays the data graphically?

The CSI Web Server enables the viewing of RTMC projects using a web browser. CSI Web Server allows configuring the web server, checking the status of the web server, and easily browsing to sites running on the web server. An RTMC project can be published to either a PC website or to an HTTP-enabled datalogger. The CSI Web Server is included with RTMC Pro. It also can be purchased separately for use with the standard RTMC Development application that is bundled with LoggerNet, LoggerNet Admin, LoggerNetData, and RTDAQ.

Is it possible to save the datalogger binary data as a file and download it to LoggerNet before it is stored in a CSV file?

The CardOut() and TableFile() instructions in the datalogger can be used to write binary files to the datalogger CPU, CRD, or USR drive.

Alternately, LoggerNet can be configured in the Setup screen to save data in binary format. On the Data Files tab, set the Output Format to Binary Table Data (TOB1).

Can LoggerNet be upgraded to LoggerNet Remote?

No. However, LoggerNet can be upgraded to LoggerNet Admin, which has the same features as LoggerNet Remote.

If a laptop does not have any serial ports, how can LoggerNet talk to the datalogger?

Use a USB to RS-232 cable (sometimes called a USB-to-serial-adapter cable) to connect either an SC32B or an SC-USB to the computer. Although any USB to RS-232 cable should work with the appropriate drivers, there is a better chance of success using the USB to RS-232 cables sold by Campbell Scientific.

How can LoggerNet be upgraded to LoggerNet Admin?

LOGGERNETADM/U (LoggerNet Admin Upgrade) can be purchased to upgrade one copy of LoggerNet or LoggerNet Admin to the current version of LoggerNet Admin. Although installing a copy of LoggerNet Remote on the same machine as LoggerNet will result in a LoggerNet Admin installation with all of its features, Campbell Scientific does not recommend this process because installing different versions of LoggerNet and LoggerNet Remote can result in inconsistent behavior of the software.

LOGGERNETADM/U is a little more expensive, but it is more convenient, especially if the need arises to move the installation to a different computer.

Is there a tutorial available for RTMC?

Yes. The “Getting Started with RTMC Tutorial” is available for download.

Can LoggerNet and LoggerNet Remote be installed on the same computer?

Yes. This combination will result in a LoggerNet Admin installation with all of its features. However, Campbell Scientific does not recommend this process because installing different versions of LoggerNet and LoggerNet Remote can result in inconsistent software behavior.

Where is the Transformer tool?

Transformer is available within LoggerNet 3.2 and higher.

  • From the Windows Start Menu, navigate to LoggerNet3.0 | Utilities | Transformer.
  • In LoggerNet 4.x, from the main LoggerNet window, navigate to Program | Transformer.
To run LoggerNet as a server and control two datalogger networks from remote PCs, is LoggerNet Admin needed, as well as LoggerNet Remote for each remote PC?

Yes. To install LoggerNet on a centralized server and run it as a service, LoggerNet Admin needs to be installed on the server. Assuming there are open communications paths, LoggerNet Admin can be set up to control/access two or more datalogger networks. However, if users would like to control two networks on separate PCs, a copy of LoggerNet Remote is needed for each PC accessing LoggerNet Admin on the servers.

Does CRBasic have to be used to program a datalogger? Does a menu-driven program generator exist for the datalogger?

A free program generator for all Campbell Scientific dataloggers is Short Cut for Windows (SCWin). Short Cut can be used to create programs in many situations where Campbell Scientific equipment is used. The Campbell Scientific YouTube channel has a two-part series on using Short Cut.

In situations where program requirements are too complex or specialized for Short Cut, programs can be written in any text editor that can edit and save plain ASCII text. However, creating an error-free program would be very difficult. The CRBasic Editor that comes with PC400 and LoggerNet provides a programming environment with procedure templates, integrated help, programming examples, the ability to test compile the program before sending it, and many other features that can be very helpful when developing a program.

Is it possible to use LoggerNet RTMC while a datalogger is collecting data from a serial sensor?

Yes, provided the serial sensor is connected to a port that is separate from the one used to connect to LoggerNet.

Is LoggerNet Admin needed to automatically start up LoggerNet on a virtual server?

Yes, unless a Windows task is set up to launch LoggerNet. This task method, however, is not supported by Campbell Scientific.

Where can example programs be found?

The CRBasic Editor Help contains example program code for all instructions in the datalogger. Look for the Example link at the top of each instruction topic. The CRBasic Help Tutorial demonstrates how to access this and other online CRBasic Editor Help files.

Also, many programming examples can be found in the datalogger and sensor manuals that are available on the Campbell Scientific website.

Is there a way to convert an Edlog program file to a CRBasic program file?

Yes. We have created a software application, Transformer, to help migrate Edlog program files to CRBasic program files. Transformer is available within LoggerNet 3.2 and higher.

  • From the Windows Start Menu, navigate to LoggerNet3.0 | Utilities | Transformer.
  • In LoggerNet 4.x, from the main LoggerNet window, navigate to Program | Transformer.

Transformer uses a CSI or DLD file created in Edlog to generate CRBasic code. A side-by-side comparison of the two programs is provided along with an action log that highlights parts of the program that may need attention or additional editing in CRBasic.

If the message “Clock check started” is followed by the message “Clock check failed,” what does this mean?

This is a general indication of a communications error with the datalogger. One of the first things that the communications software tries to do is read the station clock, and that is why the clock check command shows up as failing. It does not mean that there is a clock problem in general.

What might cause clock issues?

If the automatic clock synchronization option (LoggerNet [version 4] Setup, Datalogger, Clock tab) is used, do not set the Allowed Clock Deviation too tight (for example, 1 s), as the PC will try to change the clock either because of drift in its own clock or because of delays in the communication from the PC to the datalogger. If the clock is updated too often, there is the risk of the datalogger skipping records if the time is pushed forward just before it is supposed to store data.

Although most PCs are usually synchronized with Internet time, the default update time is several days, and a PC can typically drift tens of seconds in that period.

Clock issues also appear when changing to or from daylight saving time, as the datalogger does not automatically adjust for DST. Data continuity can be maintained by keeping datalogger clocks on standard time.

In addition, if the datalogger’s internal 3 V battery is bad and the datalogger’s main 12 V power supply is cycled, the datalogger’s clock will reset to a default time.

How can data from a specific date range be collected from a datalogger?

There is a Custom button on the LoggerNet Connect screen that allows a variety of different data collection tasks, including collecting a range of data between dates.

Note that, by default, data collected in this manner is stored to the C:\Campbellsci\LoggerNet\Data directory. This is a different directory and different file than where the data is stored from the LoggerNet scheduled data collection and from the Collect Now button on the Connect screen. (Scheduled collection and Collect Now data go into the same file and use the same data collection pointers.)

Can multiple networked dataloggers be time synchronized programmatically?

If the dataloggers are connected over some form of serial/PakBus link, they can be synchronized with each other using the ClockReport() and PakBusClock() instructions in the dataloggers. Use the ClockReport() instruction in the master (time) datalogger and the PakBusClock() instruction in the slave dataloggers. The option to broadcast to all can be used (providing no routing is needed), which means that just one packet of information is sent.

The ClockReport() instruction can be used as frequently as desired, although, for practical purposes, once or twice a day should be adequate for most applications. The clock should be set at a time that does not interfere with the timing of dataloggers storing their data.

If the dataloggers are connected over an IP network, use the NetworkTimeProtocol() instruction so that one datalogger acts as the time server.

Using LoggerNet, what kind of file format checking occurs?

With newer dataloggers, such as the CR1000, the default output file format is TOA5. This format requires that a header be present that accurately describes the data that will follow. LoggerNet cannot append to this file format without first checking the header of the existing file. If that header disagrees with what LoggerNet knows about the table, it will back up the existing file and start a new one with the proper header.

If it is not desired to have this checking take place, the format of the file can be modified in LoggerNet by specifying the Output Format field for the table as ASCII Table Data, No Header or Array Compatible CSV.

What would cause a message from LoggerNet that the settings are locked by a user?

A client lock is automatically created by the Setup screen when a user begins to make changes. This lock will remain until the changes have been committed or cancelled, or until the connection between the Setup screen and the LoggerNet server is severed.

What is the Network Planner?

Network Planner is new to LoggerNet 4.0. It was specifically designed to help set up dataloggers in PakBus networks so that they can communicate with each other and the LoggerNet server.

The Network Planner allows the graphical layout of devices and the specification of the links between the devices. It can then use that information to generate settings for all the devices and provide the means to program those settings into the devices and also to configure LoggerNet.

Is it possible to have a datalogger initiate the data transfer, rather than LoggerNet?

A datalogger can be programmed to initiate data transfer by using the SendVariables() or ModemCallback() instruction in CRBasic.

How can the clock used by LoggerNet be set independently of the PC system clock?

LoggerNet can be set to use GMT, regardless of the PC system clock, by using the LoggerNet Setup screen: Tools | LoggerNet Server Settings | LoggerNet Settings.

An offset to the PC clock can be set for the datalogger. Follow these steps:

  1. In the Setup screen, highlight the datalogger.
  2. Select the Clock tab.
  3. Set a value in the Time Zone Offset field.
Why does LoggerNet create a backup data file every time data collection is triggered?

Before it appends to a TOA5, TOB1, or TOACI1 data file, LoggerNet first scans the header of that file and compares the information that it contains with the information reported in the datalogger table definitions. For TOA5, the following conditions can result in errors that will cause LoggerNet to refuse to append to the file:

  • The table names do not match.
  • The number of columns does not match.
  • One or more column names do not match.
  • The number of units strings does not match the number of column names.
  • The number of process strings does not match the number of column names.

There have been cases where, using the FieldNames() instruction, the datalogger program specified a double quote character (") in the units string, and this character unbalanced the quote marks in the TOA5 format, which in turn threw off the TOA5 parser.

Can the standard LoggerNet software be used to access LoggerNet Admin running on a server, or is LoggerNet Remote needed?

To connect to a remote computer, either LoggerNet Remote or another copy of LoggerNet Admin is needed. The standard LoggerNet software does not have the ability to log in to a server other than localhost.

Can the CRBasic Editor be purchased without LoggerNet, or do they have to be purchased together?

The CRBasic Editor is included with LoggerNet, PC400, and RTDAQ, which are software options available for purchase. The CRBasic Editor cannot be purchased separately.

The CRBasic Editor has a number of features, such as syntax highlighting, context-sensitive help, a program precompiler, etc. However, the CRBasic Editor is not required to edit a datalogger program. All datalogger programs are simply text files that can be edited with any editor capable of handling plain text, such as Notepad, WordPad, vi, or Emacs. Caution should be used, however, editing a program in a text editor. Coding mistakes can make the datalogger program run incorrectly or not at all.

How can the LoggerNet cache for a specific datalogger be cleared and then filled with data from a file saved on disk?

The cache for a particular datalogger can be cleared by updating its table definitions in LoggerNet, but data cannot be imported into the cache from a data file, and the cache cannot be edited. To clear the cache, choose Reset instead of Merge when updating table definitions for the datalogger.

If long-term storage in a database is required, consider purchasing LNDB (LoggerNet Database Software).

How can a program be removed from a datalogger using LoggerNet?

The Retrieve button, used to retrieve a program from a datalogger, is found on the LoggerNet Connect screen. Note that some dataloggers, such as the CR200X-series, do not store the program in a retrievable format, and the Retrieve button will be disabled.

There is also a File Retrieval tab in LoggerNet on the Setup screen that can be used to retrieve files stored on the datalogger.

What is the station name?

There are two station names associated with a datalogger. One name is the Station Name used in the LoggerNet network map. The other name is the Station Name field in the datalogger Status table. Almost all data file formats work in LoggerNet include a station name in the header of the data file. By default, the network map station name is used. However, a checkbox in the LoggerNet Setup window, Data Files tab, allows choosing the datalogger Status table station name instead.

What is Split?

LoggerNet and PC400 have a program named Split that enables selection of records and mathematical calculations on data values in a data file. The program is especially useful in isolating data records of interest from data files from array-based dataloggers where several different types of records may be stored in the same file.

Note that the version of Split in PC200W is a different application. Its only function is to separate each array in a mixed-array file into separate files.

How can the LoggerNet PakBus address be changed?

The PakBus address that LoggerNet uses for communication with the PakBus network is, by default, 4094. This address can be changed for one or all ports from the LoggerNet Setup screen: Tools | LoggerNet Server Settings | PakBus Settings.

How can the Record Number (RECNBR) be turned off in LoggerNet so that it is not saved with all the other values?

In the LoggerNet Setup screen, on the Data Files tab, select the browse button beside the Output Format field. This will open a dialog box that enables turning off Record Number. The option to not produce the record number was introduced in LoggerNet 4.0.

In typical use, the datalogger itself does not store the record number or timestamp with each individual record in its own memory. Those values are generated by calculation when the data is retrieved.

Would there be any major problems with moving a datalogger to another communications path while someone is using the LoggerNet software?

As long as the same device is being moved from one communications route to another, all data collection pointers, filenames, etc., will be maintained with that datalogger as it is moved.

Where is scheduled data collection enabled?

In the LoggerNet Setup screen, use the Schedule tab.

If the LoggerNet disk is lost, what can be done?

Campbell Scientific does not replace lost or damaged disks. Customers are urged to create a backup copy of the CD and record the product key for safe keeping.

What is the CRBasic Editor that comes with LoggerNet?

The CRBasic Editor is a programming tool for the CR200X-series, CR5000, CR1000, CR3000, CR800, CR850, and CR9000X-series dataloggers. It is intended for use by the experienced datalogger programmer who needs more flexibility than what is found in Short Cut for Windows (SCWin).

The CRBasic Editor is a programming environment that provides instruction templates, extensive help screens, and examples.  An overview of the CRBasic Editor is provided in the LoggerNet Instruction Manual.

What might cause LoggerNet to display a “PakBus Framing Error” message such as "PakBusPort","F","PakBus framing error","Invalid low level signature"?

The invalid low-level signature means that LoggerNet has received some data into its serial port that it is trying to interpret as a PakBus data packet, but the data appears to be corrupt, as proven by a signature check on the packet. (The signature of the datalogger response fails to correspond with the message contents.)

There are several reasons why this may occur:

  • The datalogger program or its settings are configured to write data on the port on which an attempt to connect is being made.
  • Corruption of the data occurs between the datalogger and LoggerNet. This is more likely to occur over a non-PakBus-aware radio link, but it can happen with suspect serial interfaces.
  • There is a mismatch in baud rates between the computer serial port and the datalogger. This can cause the computer UART to clock in what appears to be garbage bytes (usually FF or 00 hex). Typically when this occurs, there are accompanying fault messages in the comms log for the serial port that report a serial framing error or, perhaps, a buffer overflow.
  • The link, for various reasons, can drop sequences of characters from transmissions. This can happen if the CPU on the computer is so loaded that it has a hard time processing serial interrupts in a timely fashion. It can also happen in the case of poorly written USB drivers for the device.
  • An attempt is made to communicate via the wrong COM port, and a device other than the datalogger responds.
How can a file stored on a datalogger drive be retrieved automatically from a datalogger?

Starting with LoggerNet 4.0, there is a tab in the Setup screen to retrieve a file stored on one of the datalogger drives from the datalogger on a schedule.

  • In LoggerNet 4.0, the tab is named Image Retrieval.
  • In LoggerNet 4.1, the tab is named File Retrieval.
When does LoggerNet do a clock check?

LoggerNet does not do a clock check unless there is another reason to contact the datalogger, such as for scheduled collection.

How can a backup of an existing network map and setups be created and transferred from one computer running LoggerNet to another computer running LoggerNet Admin?

Select the Backup menu item from the LoggerNet Setup screen. The choice can be made to set up automatic network backups or to perform a manual backup. This procedure creates a BKP file that can be copied to the new computer and imported using Restore Network.

It may be helpful to include the data cache (the binary database of collected data, which is twice the size of the table in the datalogger), as well as the initialization files. Files such as data files, program files, etc., can also be added.

How can TOA5 files be converted to TOB1?

A simple Windows program called File Format Convert can be started from the Windows Start menu: Campbell Scientific | LoggerNet | Utilities | File Format Convert.

There is also a console program, toa_to_tob1.exe, that is included in the LoggerNet installation directory: C:\Program Files\Campbellsci\LoggerNet\toa_to_tob1.exe

This program must be started from a console window (command prompt), and it expects two arguments: an input file name (the first one) and an output file name (the second one).

How can it be calculated when a datalogger data table will fill up?

One of the simpler ways to approximate how long it will take for a data table to fill up is to open the LoggerNet Connect screen, click the Station Status button, and view the Table Fill Times tab.

How does LoggerNet handle data collection when the datalogger stores data to a CompactFlash card?

LoggerNet collects data from the datalogger first. If there is additional data on a CompactFlash card, LoggerNet collects that also. Nothing special needs to be set up in LoggerNet to have this occur.

Can LoggerNet perform scheduled data collection on two dataloggers at the same time?

Yes, but only if the communications links to the dataloggers allow simultaneous communication. For example, two mixed-array dataloggers can be contacted simultaneously using two different COM ports; however, if they are accessed via the same COM port, LoggerNet can connect to only one at a time.

Can two instances of LoggerNet communicate at the same time with one datalogger?

It is certainly possible for two instances of LoggerNet to communicate with the datalogger. Depending on the link type and capability of the datalogger, they may be able to do so simultaneously. However, it is important to ensure that each of the PakBusPort devices in each LoggerNet instance has a unique PakBus address.

Does the LoggerNet server have a specific limit on the length of a generic modem script?

The LoggerNet server imposes no specific limits on the lengths of the generic modem scripts.

What might cause an “Access is denied” message in LoggerNet during serial communications with a datalogger?

Typically with serial ports, the reason for the "Access is denied" message is because another process or ComPort device in LoggerNet is fighting for access to the same serial port resource. For example, if each generic modem is set up to communicate on a separate ComPort device in the LoggerNet network map, but those ComPort devices are all using the same serial port, this may explain the error message. Alternatively, there may be some other application that is using the serial port.

Where is the datalogger security code set up in LoggerNet?

The security code is set up in the datalogger Hardware tab of the LoggerNet Setup screen. Unlike the Device Configuration Utility, LoggerNet will not prompt for the security code on connection, so the setting has to be in the setup information.

Where are skipped records for the datalogger reported?

Using the LoggerNet Connect screen, check the datalogger Status table.

Is there a possibility to auto-update the graphs in View Pro or other functions inside LoggerNet 4 without pushing the Refresh button in View Pro?

View Pro is meant to be a file viewer, so there is no automatic update capability.

To view graphs in real time, there are graphs that can be launched from the numeric monitor. For fully customizable displays, RTMC can be used. RTMC uses the LoggerNet server for its data source, but RTMC Pro (purchased separately from LoggerNet 4) can also use a DAT file.

How can it be determined when a clock set is occurring?

Check the trans*.log in the C:\Campbellsci\LoggerNet\Logs directory. When a clock set occurs, it will show up in the logs (for example, the words "Clock Set" with a date and time of the occurrence).

What might cause multiple PCs, all running LoggerNet, to not communicate with a PakBus datalogger?

All devices in a PakBus network, including computers, must have unique PakBus addresses. (The datalogger becomes confused when several devices connect to it with the same PakBus address.) Make sure all the copies of LoggerNet on different PCs have different PakBus addresses for the PakBus ports used to connect to the same datalogger. Configure the address to something other than the default of 4094 from the Setup window: Tools | LoggerNet Server Settings | PakBus Settings. If this is not done, the connections will be intermittent, as each new connection will cause any existing connection to be lost.

Is there any way to set a variable in the datalogger using LoggerNet to gain manual control over when data is collected by the datalogger?

A program snippet, such as the one below, would work for this purpose. The Boolean variable can be toggled from the Ports & Flags screen in LoggerNet (accessed via the Connect screen), through the Numeric Display (also accessed via the Connect screen), or under program control.

public StoreDataFlag as boolean

DataTable (ConditionalTable,StoreDataFlag,100)

          Sample (1,counter,Long)

EndTable

When storing data conditionally, be sure to allocate a specific number of records in the size parameter of the DataTable() instruction. For more information, see the Data Table Memory Allocation Tutorial.

What might cause trouble downloading data from a datalogger using LoggerNet with a USB-to-serial cable?

First, make sure the most recent version of LoggerNet is being used. (Improvements were made between versions 4.0 and 4.1 that resolved some issues with LoggerNet and some USB-to-serial cable drivers.) Next, ensure that the most recent drivers from the cable manufacturer are being used. Often, newer drivers are developed for devices after they are released, and the software shipped with those devices is not updated. The drivers can be downloaded from the manufacturer's website.

How can LoggerNet be used to edit the user drive size in the datalogger settings?

Follow these steps:

  1. Connect to the datalogger using the LoggerNet Connect screen.
  2. Find the datalogger in the Stations list, and right-click it.
  3. From the menu that is displayed, choose the Settings Editor.
How can data during a certain duration be erased without erasing the configuration and the program?

There is no mechanism to selectively erase data from the datalogger for a given date range. However, the data tables in the datalogger can be reset, which effectively erases the data.

Note: Following these steps will cause the loss of all data:

  1. In the LoggerNet Connect screen, click the Station Status button.
  2. When the dialog box opens, select the Table Fill Times tab, which shows the data tables in the datalogger and their sizes.
  3. Either select individual tables, or select the Select All checkbox.
  4. Click the Reset Tables button. This will erase all data in the tables.
What is PakBus Graph?

PakBus Graph is a tool available with LoggerNet that can be used to verify a network’s topology. It presents a graphical view of the network as it is learned by LoggerNet.

Does the LoggerNet Admin licensed version include LoggerNet Remote, or is it a separate purchase?

LoggerNet Admin contains all of the capabilities of LoggerNet Remote. Additional copies of LoggerNet Remote are purchased separately. Because using different versions of LoggerNet and LoggerNet Remote can result in issues, Campbell Scientific recommends purchasing the LoggerNet Admin Upgrade.

Can two different communications paths to one datalogger be set up in LoggerNet?

LoggerNet can be configured to have two paths to a datalogger, simply by entering the datalogger twice in the network map with different comms links. LoggerNet, however, treats them as separate entities, so it will try to collect all the data twice via the two separate paths if both are enabled. Some users have set this up where they use one route most often, and manually enable collection to the backup route if the main link is lost.

An alternative to this scheme is to set up the backup route but not add the datalogger. Then, if the main link to the datalogger goes down, simply drag-and-drop the datalogger to the backup route. After the main link is working again, the datalogger can be moved again. This keeps data collection pointers for that datalogger intact.

What software can be used for scheduled data collection?

LoggerNet and VisualWeather are the only datalogger support software packages, offered by Campbell Scientific, that perform scheduled data collection.

Can LoggerNet store data in binary file format?

Yes. LoggerNet can be configured to store data in a binary file format.

Follow these steps:

  1. In the LoggerNet Setup screen, select the datalogger.
  2. Choose the Data Files tab.
  3. In the Output Format field, select Binary data.
Can LoggerNet be configured so that each data collection is saved in a new file rather than being appended to an existing file?

Yes. Follow these steps:

  1. In the LoggerNet Setup screen, click the icon for the datalogger.
  2. Choose the Data Files tab.
  3. Deselect the Use Default File Name checkbox.
  4. In the menu for the File Output Option field, choose Create Unique File Name.
How can the LoggerNet network map be transferred to a new computer without losing information?

Within LoggerNet, there is the capability of creating a backup file containing the LoggerNet system files, settings, and data. This can be used to move settings from an old computer to a new one. The process involves performing a Network Backup on the old computer and a Network Restore on the new one.

From the LoggerNet Setup Screen, choose Backup | Manual Backup…. In the screens that follow, several choices need to be made:

  1. Keep the checkboxes selected for the cache and initialization files, and click Next to proceed.
  2. If data files that have been manually downloaded should be included in the backup, select those files. Click Next to proceed.
  3. Either note where the file is being saved, or enter a path to a location where the file can be easily found.  Click Next to proceed.
  4. Click the Back Up Now button on the last screen.

From the LoggerNet Setup Screen choose Backup | Restore Network…. Follow these steps:

  1. Select the file that was backed up to in the previous process.
  2. Click the Restore button. 
    Note: This process will destroy any settings or files that exist for LoggerNet in the folder for the restoration. 

Even with the Backup/Restore utility, there still may be some work to do.  For example, if a new computer has different serial port numbers or different modem settings than the old computer, after the restore process is completed, the network map in the Setup screen will have to be reviewed, and the settings that have changed will need to be fixed.

How can LoggerNet be upgraded to LoggerNet Admin in the most seamless way possible?

To upgrade from LoggerNet to LoggerNet Admin, the correct upgrade path is to order the LoggerNet Admin Upgrade (LOGGERNETADM/U), which allows one copy of LoggerNet or LoggerNet Admin to be upgraded to the current version of LoggerNet Admin.

Can LoggerNet create a wind rose?

The RTMC Development application that comes with LoggerNet does not contain the wind rose control, although it does have a compass that can be used to display current wind direction. A wind rose control is included in RTMC Pro, which must be purchased separately.

Can LoggerNet be configured to run as a service without purchasing LoggerNet Admin?

No. Only LoggerNet Admin has the capability of running LoggerNet as a service.

Does the LoggerNet license allow the migration of an installation from one computer to another? If so, what is the process?

Although the licensing agreement could be interpreted very strictly, Campbell Scientific realizes that data and procedures are very valuable to our customers and that migrating a system can be risky with no backup. Therefore, customers may temporarily violate the single machine installation rule during the migration process. The migration procedure is as follows:

  1. Install LoggerNet on the new computer.
  2. Migrate the settings across to the new computer using backup and restore.
    1. From the LoggerNet Setup screen, choose Backup | Manual Backup…. In the screens that follow, several choices need to be made:
      1. Keep the checkboxes selected for the cache and initialization files, and click Next to proceed.
      2. If data files that have been manually downloaded should be included in the backup, select those files. Click Next to proceed.
      3. Either note where the file is being saved, or enter a path to a location where the file can be easily found.  Click Next to proceed.
      4. Click the Back Up Now button on the last screen.
    2. From the LoggerNet Setup screen choose Backup | Restore Network…. Follow these steps:
      1. Select the file that was backed up to in the previous process.
      2. Click the Restore button. 
        Note: This process will destroy any settings or files that exist for LoggerNet in the folder for the restoration.
  3. Ensure LoggerNet is working properly on the new computer.
  4. Uninstall the LoggerNet software from the old computer.
Is there a Windows 8 compatible version of LoggerNet?

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

To test whether LoggerNet will work in a particular Windows environment, download the 30 day trial version in the Downloads section of the Support tab on the LoggerNet product page.

Note that the purchased version of LoggerNet is separate from the trial version and requires a full installation. There is no way to unlock the trial version, and it must be uninstalled before installing the licensed version of LoggerNet. However, any files created using the trial version are stored and will be available for use when the purchased version is installed.

Will a patch for LoggerNet 4.0 apply to LoggerNet Admin 4.0 as well?

Yes. The patch should update the install to version 4.1 Admin, as long as the previous installation was installed as Admin with the correct license key.

Is there a way to install LoggerNet without the CD in the server, as long as a valid CD license and a copy of the CD are in the possession of the user?

Yes. The files can be copied from the CD and used to install the software. Note that the CD media is proof of purchase and will not be replaced if it is lost.

Is there a list of the ports used by LoggerNet?

To see which ports are being used, use an application such as Windows netstat or TCPView. Unless an alteration has been made with a command line argument, LoggerNet will be listening on port 6789.

Do all NLxx Internet and IP network products require LoggerNet to be installed locally?

If the NLxx device uses a routable IP address, LoggerNet should be able to access the device from anywhere there is Internet access—as long as firewall restrictions do not interfere.

Can LoggerNet be programmed so that each month of data is automatically stored in a new file?

LoggerNet cannot do this directly via scheduled data collection, but there are a few ways to accomplish this:

  1. Use the LoggerNet Split application to parse the LoggerNet DAT file into a monthly summary file. Split can be triggered manually or set up as a calendar-based scheduled task in the Task Master that runs on the Last day of every month.
  2. Set up the datalogger as a different datalogger in the LoggerNet network map, and then set up a calendar-based scheduled task in the Task Master to collect data on the Last day of every month.
  3. To store data in a database, and manually query the data on a monthly basis, use LNDB (LoggerNet Database Software).
Can PC200W software be used to view LoggerNet data?

The View application in PC200W can be used to open files created by LoggerNet. TOACI1, TOA5, TOB1, TOB2, TOB3, printable ASCII, comma-separated ASCII, and array-based datalogger binary data files can be opened with View.

Can LoggerNet run on a 64-bit version of Windows?

LoggerNet and its components are 32-bit applications. They have not been specifically developed for 64-bit Windows systems. However, we run some of our tests on 64-bit operating systems, and there have been no reports of customers experiencing problems specific to a 64-bit version of Windows.

To test whether LoggerNet will work in a particular Windows environment, download the 30 day trial version from the Downloads section of the Support tab on the LoggerNet product page.

Note that the purchased version of LoggerNet is separate from the trial version and requires a full installation. There is no way to unlock the trial version, and it must be uninstalled before installing the licensed version of LoggerNet. However, any files created using the trial version are stored and will be available for use when the purchased version is installed.

Does a purchase of LoggerNet come with remote licenses, or are those only available for an additional charge?

LoggerNet Remote (LOGGERNETREM) is a separate product available for purchase.

Does upgrading a LoggerNet installation to a LoggerNet Admin installation remove scheduled data collection rules, the stations, or any other settings?

All data and settings should remain following the upgrade from LoggerNet to LoggerNet Admin. The file formats and locations are exactly the same between the two products. No information in the configuration should be lost or reset.

How can the station time be changed in LoggerNet?

The station’s datalogger clock can be set from the Connect screen. It can also be set from the Clock tab in the Setup screen.

What is the default port that LoggerNet uses to communicate with an IP modem?

The port is set during the setup process in the modem and then in the Setup screen of LoggerNet. The port of 3001 is the default in the Raven templates supplied by Campbell Scientific.

What does the error "Classic::CmdClockSet" mean?

One of the first tasks that LoggerNet attempts to accomplish when it connects to a datalogger is to read the datalogger clock. The fact that an error is being returned for this command only indicates that LoggerNet was unable to create a connection and check the clock. The error provides no information about the cause of the communication issue.

If two licenses of LoggerNet are owned, why would having one Windows user in LoggerNet prevent another user from accessing the application?

The LoggerNet Toolbar uses the TCP/IP protocol to communicate with the LoggerNet server. If two instances of LoggerNet are being run on the same computer, there would be a TCP/IP port conflict because they are both trying to use the same port.

How can LoggerNet be programmed to download data only from the last download and not data that were previously downloaded?

In the LoggerNet Setup screen, on the Data Files tab, there are these Collect Mode options:

  • Data Logged Since Last Collection
  • Most Recently Logged Records
  • Collect At Most
What would cause the message “table definitions out of date” to appear?

The “table definitions out of date” message simply implies that the datalogger is running a program that the PC software does not recognize or in which the data tables in the datalogger have been modified. In many cases LoggerNet will update the table definitions automatically. Alternatively, in LoggerNet, navigate to Connect | Datalogger | Update Table Definitions.

If the LoggerNet product key is lost, is there a way to retrieve this information?

There is not a way for the customer to retrieve this information. In some cases, if the version of the software and the serial number are known to Campbell Scientific, the CD key can be determined. However, remember that Campbell Scientific views the holder of the CD media as the owner of the software, so the application CD must be available to do the installation.

To run LoggerNet on a Windows Server operating system, are there any performance requirements or compatibility issues to be mindful of?

Because server installations are uniquely configured, it is nearly impossible for our application engineers to replicate a customer’s implementation environment at our facility. Consequently, the support provided is limited.

To test whether LoggerNet will work in a particular server environment, download the 30 day trial version in the Downloads section of the Support tab on the LoggerNet product page.

If the original installation disk is missing, how can a copy of LoggerNet be transferred from one computer to another computer?

Campbell Scientific views the holder of the CD media as the owner of the software, so the application CD is required to do the installation.

Is it possible for LoggerNet to collect data from a datalogger and then SFTP it to a server?

Yes, using the LoggerNet Task Master. The FTP settings are available for tasks that execute After File Close or After File Retrieved. SFTP (SSH FTP) is one of the options for FTP protocol on the FTP Settings tab.

Why might the numeric and graph displays (accessed from the LoggerNet Connect screen) no longer update?

If communication is interrupted or intermittent, LoggerNet may stop updating the Table Monitor, Numeric Display, and Graphs. When this occurs, a button on the display that is normally titled Stop (to stop the update) changes to Start, and the button must be pressed to resume the update. Also, check the update interval on the display, as it may be set to a higher value than expected.

Is there a document that fully explains the various commands used in datalogger programs, such as parameters, parameter ranges, and default values?

No, but the Help in the Edlog and CRBasic editors is complete with all of this information. The CRBasic Editor Help also includes extensive examples.

What might cause Windows to display a "Blue Screen of Death" when LoggerNet is running?

Typically, blue screens are the result of bad device drivers. The Internet can be very helpful in tracking down the cause of blue screens. Copy down the codes displayed. Search the Internet for “blue screen” and the code to see what device is causing the crash. Often, an updated device driver will resolve the issue.

What TCP ports need to be opened up on a firewall to allow LoggerNet to communicate with a datalogger?

In some configurations, the server opens a socket on a specific port to listen for requests for data from its clients.  By default, the port is 6789, but it can be changed with the IPPort command line parameter. 

Is there a way to set LoggerNet to download only the last x number of hours of data?

On table-based dataloggers, in the LoggerNet Setup screen, on the Data Files tab, there is the Collect at Most option that can be used to indicate how many records to collect. Based on how often data is stored, a calculation can be made to determine how many records represent x hours of data.

Can LoggerNet connect to a modem with a dynamic IP address?

A Raven cellular modem with a dynamic IP address can be addressed through the DDNS (Dynamic Domain Name System) offered as a free service by Sierra Wireless (AirLink). The service translates a dynamic IP address into a fully qualified domain name so that the modem can be contacted directly via the Internet as if it had a static IP.  Campbell Scientific recommends that customers set up their Raven modems with a modem name that is the cellular phone number and that they use a domain of eairlink.com.

Does LoggerNet anywhere indicate the battery level of the connected datalogger?

For PakBus dataloggers, the battery voltage is found on the Station Status screen. (The Station Status screen is accessed from the LoggerNet Connect screen.) For mixed-array dataloggers, Station Status will display the lithium battery and the number of times the 12 V supply has dropped below an acceptable level. If the battery voltage is being read by the program, it may be available from the public table.

How can a datalogger be switched out (for example, from a CR800 to a CR1000) in LoggerNet?

Follow these steps:

  1. In the Setup screen, record the pertinent data from the Schedule and Data Files tabs. 
  2. Delete the listed datalogger.
  3. Add the new datalogger. 
  4. Adjust the settings on the Schedule and Data Files tabs to match what was being done previously.
    • If the settings are complicated, review the Help menu from the Setup screen to learn more about the option in LoggerNet 4.2 to Copy Device Settings in the Tools menu.
Is there a way for LoggerNet to send an email alert if a complete datalogger failure occurs?

An RTMC Pro screen can be developed to monitor a value being returned from the datalogger and send an email alert if it exceeds certain parameters. Alternatively, a task could be set up in the Task Master to email an alert that is executed after a failed call or failed retries.

Can a datalogger be configured to place a call to a PC running LoggerNet?

Yes. If the datalogger has a phone modem connected, there are Edlog and CRBasic commands that can be used to initiate calls. For example, in CRBasic a call can be made with SerialOpen(), SendVariables(), and SerialClose() instructions.

Does LoggerNet require local administrator rights to function?

Because the directory in which the executable files are installed is C:\Program Files\CampbellSci\LoggerNet, many operating system configurations require the user account under which the software is installed to have administrative privileges on the computer. However, after the software is installed, administrative privileges are not required by the user to run the software.

If LoggerNet is running on a server behind a firewall, which firewall port needs to be opened to connect to dataloggers that each have a GPRS modem and a fixed IP address?

If LoggerNet will be initiating all connections (all outbound), there should not be a need to open firewall ports.  If there will be call-backs from the modems, by default, the port that LoggerNet listens on is 6789. This, however, can be changed with the IPPort command line parameter.

What might cause a connection issue between a datalogger and an NL240 in LoggerNet?

If the NL240 is on a different network from the server running LoggerNet, either the station or LoggerNet needs to be able to initiate a connection to the other:

  • The NL240/datalogger needs an IP address that is accessible to the LoggerNet computer

OR

  • LoggerNet needs an IP address that is accessible to the NL240/datalogger.
If LoggerNet does not list the NL120, is that OK?

Yes. The NL120 operates as transparent.

Resources and Links

Shipping Weights & Dims

Single Box Shipping Weight:
     1.0 lbs
     454 g

Single Box Shipping Dimensions:
     12" x 12" x 4"
     30.5 x 30.5 x 10.2 cm