FAQs
Frequently Asked Questions About our Products and Solutions
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 data logger 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 data loggers 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).
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 sub-networks.
Connect Screen functions work without having to "connect" to the data 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 data loggers, and accepting UDP packets from an AirLink modem (Raven or PinPoint) containing a new dynamic IP address.