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:

+61 (0)7 4401 7700
+61 (0)7 4755 0355 (fax)
Sales and Technical support:

Videos & Tutorials

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

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


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?
  • LoggerNet now supports IPv6 addresses. IPv6 addresses are written as eight two-byte address blocks separated by colons and surrounded by brackets (e.g., [2620:24:8080:8600:85a1:fcf2:2172:11bf]). Prior to LoggerNet 4.2, only IPv4 addresses were supported. IPv4 addresses are written in dotted decimal notation (e.g., Leading zeroes are stripped for both IPv4 and IPv6 addresses.
    • Note: Although LoggerNet now supports IPv6 addresses that can be used to specify servers, CR1000, CR3000, and CR800-series dataloggers will not support IPv6 until a future OS release. Check the OS Revision History to determine when IPv6 support is added to the OS.
  • LoggerNet now supports display and input of Unicode characters and strings in many areas of the product. Unicode is a universal system for encoding characters. It allows LoggerNet to display characters in the same way across multiple languages and countries. To support Unicode, an Insert Symbol dialog box has been added to the CRBasic Editor. This allows the insertion of Unicode symbols into a CRBasic program for use in Strings and Units declarations.
  • Defaults can be set up for the Setup Screen’s Schedule, Data Files, Clock, and File Retrieval tabs that will be used when new stations are added to the network. There is also the ability to copy these defaults to existing stations.
  • The ability to use 24:00 (rather than the default of 00:00) for the timestamp at midnight has been added. (This is accessed from the   button next to the Output Format field on the datalogger’s Data Files tab in the Setup Screen. It is also available in the Connect Screen’s Custom Collection options.)
  • PakBus Encryption is now supported for communication between LoggerNet and CR1000, CR3000, and CR800-series dataloggers. A PakBus encryption key must be entered in both the datalogger’s device settings and LoggerNet’s Setup Screen. AES-128 encryption is used.
    • Note: The datalogger must be running OS 26 or later for PakBus Encryption to be used.
  • Two new root devices (SerialPortPool and TerminalServerPool) have been added to allow for modem pooling. Pooled devices may be useful in cases where LoggerNet is used to call, by phone, multiple remote dataloggers, and more than one modem and phone line is available to make the connections.
  • A datalogger’s Settings Editor can now be accessed from the Connect Screen either by right-clicking the datalogger or from the Datalogger menu. The datalogger’s clock can be manually set from the Connect Screen either by double-clicking in the Station Date/Time field or from the Datalogger menu. Boolean values displayed in the Connect Screen’s Numeric Display now have an LED icon next to them to allow for easy toggling.
  • Additional statistics can now be viewed in the Status Monitor for table-based dataloggers, including watchdog errors, skipped scans, and battery errors.
    • Note: The Poll for Statistics checkbox on the datalogger’s Schedule tab in the Setup Screen must be selected to poll for these statistics.
  • The Task Master has been integrated into the LoggerNet server. This allows for remote administration of the Task Master. (See Select Server in the Task Master Help for conditions that must be met for remote administration of the Task Master.)
    • Note:  Integrating the Task Master into the server involved extensive changes. When upgrading to LoggerNet 4.2 from a previous version, an attempt will be made to import all previously configured tasks. However, imports have only been tested back to LoggerNet 3.4.1. After upgrading from any previous version of LoggerNet, verify that all of the tasks have imported correctly.
  • Calendar-based scheduling has been added to the Task Master. This allows for non-interval task execution (including data collection). See Example #3 in the Task Master Help for an example of calendar-based data collection.
  • A Constant Customization feature has been added to the CRBasic Editor. This allows the definition of values for one or more constants in a program prior to performing a conditional compile. The constants can be set up with an edit box, a spin box field for selecting or entering a value, or a list box. A step increase or decrease can be defined for the spin box, as well as maximum and minimum values.
  • The CRBasic Editor now offers a Save and Open Display Settings feature. Display settings affect the look and feel of the CRBasic Editor. This includes font and background, as well as syntax highlighting.
  • View Pro has a new View Record option in the right-click menu that can be used to view an entire record in a new window.
What's new in LoggerNet 4.1?
  • One of the main efforts in the development of LoggerNet 4.1 has been the ability to use LNDB databases with View Pro. The ability to lock the timestamp column on the left of the data file has also been added to View Pro. This keeps the timestamp visible while scrolling through columns of data. 
  • The Device Configuration Utility has a new off-line mode which allows viewing settings for a certain device type without actually being connected to a device.
  • The CRBasic Editor now has the capability to open a read-only copy of any file. This provides the ability to open multiple copies of a program and examine multiple areas of a very large program at the same time. In addition, an instruction can be continued onto multiple lines by placing the line continuation indicator (a single space followed by an underscore “_”) at the end of each line that is to be continued. Also, bookmarks in a CRBasic program are now persistent from session to session.
  • In the Troubleshooter and the Setup Screen (Standard View), it is now possible to click on a potential problem to bring up a menu that enables the user to go to the Setup Screen or Status Monitor to fix the potential problem, bring up Help describing the problem, or in some cases, fix the problem directly.
  • Campbell Scientific’s new wireless sensors have been added to the Network Planner.
  • Statistics (average, minimum, maximum, and number of data points) can now be viewed for each data value being displayed in a Connect Screen graph. All of the Connect Screen’s displays (table monitor, numeric displays, and graphs) now show the units that have been assigned to the data values.
  • Split has a new “Time Sync to First Record” option that can be used with the time-sync function to avoid blank lines at the start of the output file. Also, a range of time values rather than a single time can now be entered in a Split Copy Condition.
  • CardConvert can now be run from a command line without user interaction.
  • An option to provide feedback on LoggerNet has been added to the LoggerNet Toolbar’s Help menu.
  • Miscellaneous other changes and bug fixes have also been implemented in this version.

Note:  Beginning with this version of LoggerNet, Windows 2000 is no longer supported.

What is new for LoggerNet Version 4?
  • LoggerNet 4.0 introduces a new look and feel to the LoggerNet Toolbar. Applications are divided into categories to make navigating the Toolbar easier. A Favorites category can be organized for the applications that are used most often.
  • A new file viewing application, View Pro, is introduced in which LoggerNet 4.0 View Pro allows you to graph data in a variety of formats including Line Graph, X-Y Plot, Histogram, Rainflow Histogram, and FFT(2D or 3D).
  • Another new application, the Network Planner, is included. The Network Planner is a graphical application that assists the user in designing PakBus datalogger networks.

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?


  • Enhanced performance of the CRBasic Editor when checking for matching parentheses.

Bug Fixes

Note: The following fixes only apply to customers who are upgrading to LoggerNet 3.1.1 from LoggerNet 2.x:

  • Data file paths for table-based dataloggers appeared to be distorted in the Setup Screen.
  • Numeric Monitor displayed inlocs from some table-based dataloggers incorrectly.
What changed from LoggerNet 2.x to LoggerNet 3.1?

New features

  • Support for the CR1000 throughout the software, including the Short Cut program generator
  • EZSetup client
  • Added a TroubleShooter client to help identify communications problems. This includes a new Communication Test tool.
  • Users can check and set datalogger clocks, and send programs from the Setup Screen.
  • Status Monitor Screen added a communications history display; sorting by statistic can be done by clicking the column header.
  • A new LogTool client provides access to the log displays. Users can limit messages to specific devices.
  • RTMC added “auto-tabbing” and new time stamp formatting.
  • Added a new utility called Device Configurator (DevConfig) to set the various settings in dataloggers and communications peripherals. Settings can be saved to a file and loaded to other devices.
  • Short Cut included various refinements such as drag-and-drop for output selection, and a 50 or 60 Hz noise rejection option.
  • A new Transformer tool is provided to convert CR10X (mixed-array OS only) Edlog program (.dld or .csi) to a CR1000 CRBasic program (.CR1).


  • Reorganized Setup Screen to distinguish between settings most users would need to edit and settings where the default usually works and which users typically won’t need to change.
  • Integrated dynamic IP addressing in AirLink Ravens into Server settings.
  • Server now locks the network when any client is trying to edit it to prevent “dueling clients.”
  • Made PakBus ports independent, allowing the user to bridge or not bridge them to create sub-networks.
  • Connect Screen functions work without having to "connect" to the datalogger first.
  • Numeric and Graph Screens update automatically for some types of data without being “connected” if the data is being collected via schedule.
  • PakBus Graph is now more graphical in nature and allows easier access to device settings.
  • LoggerNet Server offers a variety of refinements, including reintroduced support for RF95T base and remote devices for BMP1 networks, standalone PakBus routers assigned to each PakBus port, a new "hangUpDelay" setting, the ability to “lock” a device when its settings are being edited to prevent other clients from “dueling” for those settings, accepting one-way data notifications from PakBus dataloggers, and accepting UDP packets from an AirLink modem (Raven or PinPoint) containing a new dynamic IP address.
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.

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


  • LoggerNet needs an IP address that is accessible to the NL240/datalogger.
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.

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, then 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.

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.

• In LoggerNet 4.x, from the main LoggerNet window, navigate to Program | 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:

  1. PC200W
    • Provides basic tools (clock set, program download, monitor data, retrieve data, etc.)
    • Only supports direct connections between a PC and a datalogger (i.e., connecting through a serial COM port, such as a short haul RAD modem or radio); no telecommunications, such as phone modems or Internet
    • Offers simple tools to view and graph data files
    • Does not include the CRBasic Editor or Edlog software
    • Does not do automated scheduled data collection
    • Is available as a free download from our website
  2. PC400
    • Has all of the features of the PC200W
    • Supports additional telecommunication options, such as IP ports and phone modems; does not support combined communication options such as phone-to-radio
    • Offers additional features, including the CRBasic and Edlog program editors
    • Does not do automated scheduled data collection
    • Is not offered as a trial version
  3. LoggerNet
    • Is not as simple to use as the other software options, but contains the tools needed to communicate with, program, manage, and collect data from a single datalogger or a network of dataloggers
    • Includes the CRBasic and Edlog program editors
    • Can communicate with any configuration of hardware and telemetry offered by Campbell Scientific
    • Includes tools to view, graph, and manipulate data files
    • Does automated scheduled data collection
    • Has a task manager to manipulate data files following collection
    • Is available as a 30 day downloadable trial version
Does CRBasic have to be used to program a datalogger? Does a menu-driven program generator exist for the datalogger?

Short Cut for Windows (SCWin) is a free program generator for Campbell Scientific dataloggers, including the CR1000. The Campbell Scientific YouTube channel has a two-part series on using Short Cut

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.

  • 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 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

DataTable (ConditionalTable,StoreDataFlag,100)

          Sample (1,counter,Long)


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

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