Frequently Asked Questions: LoggerNet
Which datalogger file should I Transform?
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.What are my options for purchasing LoggerNet 3.x?
If you own any version of LoggerNet, PC400, or PC208W you can upgrade to the 3.x series by ordering LoggerNet/U. If you do not own a copy of our Datalogger Support Software, you must purchase the full version of LoggerNet.What changed in LoggerNet from 3.1 to 3.1.1?
Changes- Enhanced performance of the CRBasic Editor when checking for matching parentheses.
- 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, 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).
- 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.
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.
Is there a tutorial available for RTMC to shorten my learning curve?
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.I'm receiving a security code error from your software, but my CR1000 doesn't have security set. What do I do?
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.
Where do I find the Transformer tool to convert my CR10X program to a CR1000 program?
The Transform Utility is not a tool that is accessible via the LoggerNet application. To find the Transform Utility go to your Windows Start menu, find LoggerNet3.0 | Utilities | Transformer. This will launch the Transformer Utility 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 Utility 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.
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.
After installing an upgrade to the current version of LoggerNet, why does my 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.Why do I receive the message “Unable to start program because the Campbell Scientific communications server is already running” when I try to start LoggerNet?
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.
