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.
Our technical support experts are ready to answer your questions. Our support numbers are:
+61 (0)7 4401 7700
+61 (0)7 4755 0355 (fax)
Sales and Technical support:
CRBasic Features - 11:09
Common CRBasic Errors and How to Fix Them - 12:07
CRBasic Help System - 3:33
LoggerNet Patch v.4.2.1 (196 MB) Add to List
LoggerNet Trial v.4.2.1 (207 MB) Add to List
What's new in LoggerNet 4 Tutorial (exe format) v.- (12.9 MB) Download Now
What's new in LoggerNet 4 Tutorial (pdf format) v.- (8.46 MB) Download Now
LoggerNet Patch (Large) v.3.4.1 (74.2 MB) Add to List
LoggerNet Patch (Small) v.3.4.1 (68.7 MB) Add to List
LoggerNet 4.0 German v. (980 KB) Add to List
LoggerNet Spanish v.4.1 (902 KB) Add to List
Spanish language files for LoggerNet 4.1.
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.
What’s new in LoggerNet 4.2?
What's new in LoggerNet 4.1?
Note: Beginning with this version of LoggerNet, Windows 2000 is no longer supported.
What is new for LoggerNet Version 4?
LoggerNet 4.0 includes many additional changes. See the preface to the LoggerNet Instruction Manual for more details on what is new in LoggerNet 4.0 and each individual application.
What changed in LoggerNet from 3.1 to 3.1.1?
Note: The following fixes only apply to customers who are upgrading to LoggerNet 3.1.1 from LoggerNet 2.x:
What changed from LoggerNet 2.x to LoggerNet 3.1?
How are PC400, LoggerNet, and LoggerNet Admin similar and different?
See the “Software Overview” brochure for comparative descriptions.
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.
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:
What might cause the "Unable to start program because the Campbell Scientific communications server is already running" message when trying to start LoggerNet?
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 (e.g., RTMC Run-Time, LoggerNet Status screen, LoggerNet Connect Screen) on TCP/IP port 6789 by default.
What is the default TCP/IP port that LoggerNet uses to communicate with a CR3000?
The default TCP/IP port is 6785.
If multiple CR3000, CR1000, or CR800-series dataloggers are connected together, can LoggerNet be used to send separate programs to them?
How can data that has been transmitted from a datalogger to LoggerNet then be transmitted to a webhost that displays the data graphically as LoggerNet does?
RTMC Pro and RTMC Web Server are LoggerNet clients that can be used for this.
Is it possible to save the CR1000’s binary data as a file and download it to LoggerNet before it is stored in a .csv file?
LoggerNet (version 4) 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).
Alternately, the CardOut() and TableFile() instructions can be used to write binary files.
Can the LoggerNet software used for a CR10X be used with a CR850 or CR800?
LoggerNet version 3.3 and newer supports the CR10X, the CR800, and the CR850.
If a laptop doesn’t have any serial ports, how can LoggerNet talk to the datalogger?
Use a USB to RS-232 cable to connect a PC without a native serial port to a datalogger. This can be purchased from Campbell Scientific (p/n 17394) or from a local electronics store.
Note: Not all USB-to-serial cables are the same. 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. Cables that are not purchased from Campbell Scientific have not been tested and may result in errors when connecting to a datalogger. Furthermore, USB-to-serial cables with the FTDI chipset are easier to use and seem to perform better than cables with the Prolific chipset.
Which software package is recommended for doing post-processing on data from the IRGASON or EC150?
EdiRe (University of Edinburgh) and MATLAB (MathWorks) are two of the products eddy-covariance customers have used to post-process their data. Others are also available. (Review the EdiRe technical paper titled “EdiRe Software for Micrometeorological Applications” for more information.)
Campbell Scientific’s default data output format is TOB1 binary, which is compatible with most post-processing software packages. If another data format is needed, Campbell Scientific’s LoggerNet software may be used to convert TOB1 to another format.
Does the datalogger software support a Linux platform?
A special Campbell Scientific product named LoggerNet Linux (LNLinux) allows the LoggerNet server to be run in a Linux environment. The server collects and stores the data, while setup and management of the network are handled from Windows workstations running LoggerNet Remote.
Is there a tutorial available for RTMC?
There isn't a stand-alone tutorial for RTMC, as the software was purposely designed to be easy to use. However, the Help screen within the program offers a good overview of how to use RTMC.
Does Campbell Scientific's 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.
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.
If data is downloaded to a PC, the resultant “CR1000_Table1.dat” file is, for example, 150 kB in size. Is 150 kB necessarily its size on the CR1000? Is there any type of data compression being used?
The CR1000 stores data in a binary format (1s and 0s), which is very compact. Campbell Scientific software, such as LoggerNet, collects the data in this binary format and converts it to a readable format such as ASCII. The CR1000's Status Table contains information regarding how memory is allocated for data storage. This information can be accessed through the Station Status button on LoggerNet's Connect Screen. The Table Fill Times tab lists the tables in the datalogger, along with the number of records in the table.
Is LoggerNet software needed to download the data from the datalogger remotely?
Campbell Scientific has several software applications that can be used to collect data from a datalogger:
Does CRBasic have to be used to program a datalogger? Does a menu-driven program generator exist for the datalogger?
Where can processor usage information be found?
The Status Table, accessed from the CR1000KD or LoggerNet’s (version 4) Connect Screen, Station Status button, has some statistics that may be useful. In Appendix B of the CR1000 Operator’s Manual, refer to “ProcessTime,” “MaxProcTime,” “MeasureTime,” and “MeasureOps.”
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.
Can a network camera be connected directly to a CR1000?
A network camera can be connected directly to a CR1000 via an NL115 or NL120 and a crossover cable. The datalogger can retrieve and store images from the network camera. Then the images can be viewed or retrieved from the datalogger in a variety of ways. These include using LoggerNet, the CR1000 web server, the CR1000 FTP client/server, or the CR1000 email client.
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. Most sensor manuals also include example programming specific to that sensor.
Is there a way to convert CR23X program files to CR3000 program files?
Yes. We have created a software application, Transformer, to help migrate CR23X program files to CR3000 program files. Transformer is available within LoggerNet 3.2 and higher.
Transformer uses a .csi or .dld file created in Edlog to generate CRBasic code for a CR3000. 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.
Is there a way to convert CR10X program files to CR1000 program files?
Yes. We have created a software application, Transformer, to help migrate CR10X program files to CR1000 program files.
Transformer is available within LoggerNet 3.0: from the Windows Start Menu, navigate to LoggerNet3.0 | Utilities | Transformer.
In LoggerNet 4.x, from the main LoggerNet window, navigate to Program | Transformer.
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 communication error with the datalogger. It does not mean that there is a clock problem in general.
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
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.
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.
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.
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.
What might cause a datalogger to not store data at a particular time, such as midnight?
This might happen because the datalogger clock is being adjusted by a remote time source. If this occurs close to the same time that the datalogger is due to store data, it can result in either a skipped record or an additional record of data.
If LoggerNet 4 is used to collect data on a schedule, check the setup for that datalogger. Look at the settings on the Clock tab in the LoggerNet Setup Screen. If that is enabled, the clock is checked and set at midnight every day and may interfere with data collection at that same time.
Skipped scans and power outages could also result in records missing from a data table. Check the datalogger’s station status or Status Table and look for skipped scans, watchdogs, and low 12 V counts.
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 (e.g., 1 s), as the PC will try to change the clock either due to 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 for just before it is supposed to store data.
While 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 LoggerNet's 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 LoggerNet's 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.)
If a datalogger’s OS hasn't been upgraded in a long time, can the most current OS be downloaded, or do the upgrades need to be done incrementally?
It is possible to upgrade the OS without downloading each OS version between the existing one on the datalogger and the most current one available. For example, a CR1000 can be upgraded directly from OS 14 to OS 25. However, when a large jump in OS versions is made, the upgrade will likely restructure the Status Table and the Setting Table, and they will need to be manually reloaded.
How can the datalogger build a text string and send it out the RS-232 port?
Sending a serial string out one of the datalogger COM ports requires at least two instructions. Generally, the SerialOpen() instruction is used to set up the communication port, such as 115.2k, N, 8, 1. The instructions SerialOut() or SerialOutBlock() can be used to transmit a specified string. See the CRBasic Editor Help for examples of programs using each of these instructions.
How can multiple networked dataloggers be time synchronized?
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.
What does the “Warning: Internal data storage memory was reinitialized” message mean?
This message indicates that the datalogger had to reconfigure and delete final storage data. The data tables are recreated, thus causing the historical data to be deleted. This message is only seen if programs are sent or restarted either by the File Control options to start/stop a program, or if the program is sent from the CRBasic Editor. If a program is sent from the Connect Screen, this message is not displayed, but final storage data on the datalogger is deleted. Remember to collect data before sending or starting a program.
What is the best way to download data simultaneously from a remote CR1000 and CR3000 via a cellular modem?
If both dataloggers are using the same cellular modem, simultaneous connection and download is not possible. To resolve this, first create a local network, such as by direct connection, RF4xx radios, an MD485, or Ethernet. Then use the cellular modem to access the network.
Resources and Links