LOGGERNET

If you own any version of LoggerNet or PC400 you can upgrade to Version 4 by ordering LoggerNet/U. If you do not own either of these software packages, you must purchase the full version of LoggerNet.

• 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 as you scroll through columns of data. 
• The Device Configuration Utility has a new off-line mode which allows you to look at the 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 gives you the ability to open multiple copies of a program and examine multiple areas of a very large program at the same time. You can also now continue an instruction onto multiple lines by placing the line continuation indicator (a single space followed by an underscore “_”) at the end of the 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), you can now click on a potential problem to bring up a menu that allows you to go 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.
• You can now view statistics (average, minimum, maximum, and number of data points) for each data value being displayed in a Connect Screen graph. All of the Connect Screen’s displays (table monitor, numeric displays, and graphs) can 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.

• LoggerNet 4.0 introduces a new look and feel to the LoggerNet Toolbar. Applications are divided into categories to make navigating the Toolbar easier. You can also organize a Favorites category for the applications that you use 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 manual for more details on what is new in LoggerNet 4.0 and each individual application.

Changes

• 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

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.

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, and you can sort by statistic 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 utlility called Device Configurator (DevConfig) to set the various settings in dataloggers and communications peripherals. Settings can be saved to a file and loaded into 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).

Changes

• 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 subnetworks.
• Connect Screen functions work without having to "connect" to the logger 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.

If you see the error message "The security code was not recognized by the station" in LoggerNet, or “Unable to send the program. Invalid security code” with PC4000, you may need to update your datalogger support software.

Using a CR1000 running Operating System Version Std.04 or later, the problem may be that LoggerNet or PC400 is interpreting the response from the datalogger incorrectly. Confirm that your new datalogger program is in your CR1000; typically you can update the table definitions and go on. Newer versions of LoggerNet and PC400 software resolve this problem. Please visit our downloads page to obtain the latest patch.

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.

A program on your computer is already using TCP/IP port 6789 or your 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 your security software is probably blocking the port. Define an exception for “LoggerNetService.exe” in your 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.

There isn't a standalone tutorial for RTMC. The help offers a good overview of how to use RTMC. We tried to keep RTMC itself simple enough that we wouldn't need to produce a separate tutorial.

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.

Beginning with LoggerNet 4, the Transformer can be accessed from the  Program category of the LoggerNet toolbar. In older versions of LoggerNet, the Transformer is not accessible via LoggerNet. To find the Transformer, go to your Windows Start menu, find LoggerNet3.0 | Utilities | Transformer. This will launch the Transformer that will allow you to select and convert a CR10X .dld or .csi file to a CR1000 program.

If you are unable to find the Transform in the Start menu, you can open Windows Explorer and go to:

C:\Program Files\CampbellSci\LoggerNet\Transformer.exe

You could then create a short cut for this and place it on your desktop.

Transformer will move all of your comments from your CR10X file so we recommend using the .csi file. If that is not available to you, you can also use the .dld file to create a CR1000 file.