This software is protected by United States copyright law and international
copyright treaty provisions. The installation and use of this software constitutes
an agreement to abide by the provisions of this license agreement.
Campbell Scientific grants you a non-exclusive license to use this software in
accordance with the following:
(1) The purchase of this software allows you to install and use the software on
one computer only.
(2) This software cannot be loaded on a network server for the purposes of
distribution or for access to the software by multiple operators. If the
software can be used from any computer other than the computer on which
it is installed, you must license a copy of the software for each additional
computer from which the software may be accessed.
(3) If this copy of the software is an upgrade from a previous version, you
must possess a valid license for the earlier version of software. You may
continue to use the earlier copy of software only if the upgrade copy and
earlier version are installed and used on the same computer. The earlier
version of software may not be installed and used on a separate computer
or transferred to another party.
(4) This software package is licensed as a single product. Its component parts
may not be separated for use on more than one computer.
(5) You may make one (1) backup copy of this software onto media similar to
the original distribution, to protect your investment in the software in case
of damage or loss. This backup copy can be used only to replace an
unusable copy of the original installation media.
This software may not be sold, included or redistributed in any other software,
or altered in any way without prior written permission from Campbell
Scientific. All copyright notices and labeling must be left intact.
Limited Warranty
The following warranties are in effect for ninety (90) days from the date of
shipment of the original purchase. These warranties are not extended by the
installation of upgrades or patches offered free of charge.
Campbell Scientific warrants that the installation media on which the software
is recorded and the documentation provided with it are free from physical
defects in materials and workmanship under normal use. The warranty does not
cover any installation media that has been damaged, lost, or abused. You are
urged to make a backup copy (as set forth above) and record the CD key to
protect your investment. Damaged or lost media is the sole responsibility of the
licensee and will not be replaced by Campbell Scientific.
Campbell Scientific warrants that the software itself will perform substantially
in accordance with the specifications set forth in the instruction manual when
properly installed and used in a manner consistent with the published
recommendations, including recommended system requirements. Campbell
Scientific does not warrant that the software will meet licensee’s requirements
for use, or that the software or documentation are error free, or that the
operation of the software will be uninterrupted.
Campbell Scientific will either replace or correct any software that does not
perform substantially according to the specifications set forth in the instruction
manual with a corrected copy of the software or corrective code. In the case of
significant error in the installation media or documentation, Campbell
Scientific will correct errors without charge by providing new media, addenda,
or substitute pages. If Campbell Scientific is unable to replace defective media
or documentation, or if it is unable to provide corrected software or corrected
documentation within a reasonable time, it will either replace the software with
a functionally similar program or refund the purchase price paid for the
software.
All warranties of merchantability and fitness for a particular purpose are
disclaimed and excluded. Campbell Scientific shall not in any case be liable for
special, incidental, consequential, indirect, or other similar damages even if
Campbell Scientific has been advised of the possibility of such damages.
Campbell Scientific is not responsible for any costs incurred as a result of lost
profits or revenue, loss of use of the software, loss of data, cost of re-creating
lost data, the cost of any substitute program, telecommunication access costs,
claims by any party other than licensee, or for other similar costs.
This warranty does not cover any software that has been altered or changed in
any way by anyone other than Campbell Scientific. Campbell Scientific is not
responsible for problems caused by computer hardware, computer operating
systems, or the use of Campbell Scientific’s software with non-Campbell
Scientific software.
Licensee’s sole and exclusive remedy is set forth in this limited warranty.
Campbell Scientific’s aggregate liability arising from or relating to this
agreement or the software or documentation (regardless of the form of action;
e.g., contract, tort, computer malpractice, fraud and/or otherwise) is limited to
the purchase price paid by the licensee.
Table of Contents
PDF viewers: These page numbers refer to the printed version of this document. Use the
PDF reader bookmarks tab for links to specific sections.
Preface — What’s New in LoggerNet 4?...........................xv
1. System Requirements .............................................1-1
1.1 Hardware and Software.................................................................... 1-1
1.2 Configuration of TCP/IP Service ..................................................... 1-1
2. Installation, Operation and Backup Procedures...2-1
E-2. Communication Status Log Messages............................................E-19
F-1. The FieldCal Instruction “Family”................................................... F-2
xiv
Preface — What’s New in LoggerNet 4?
Product History
LoggerNet 4 continues the original design of client-server functionality that
first appeared when Version 1.0 was released for Windows to replace Real
Time Monitoring Software (RTMS) that ran on OS/2 operating systems.
Versions in the 1.x series supported only table-based dataloggers and provided
large network users with sophisticated capabilities to develop clients to the
server to move data without having to store it in interim files.
Version 2.0 added support for dataloggers with mixed-array operating systems,
the CRBasic dataloggers, and additional communications devices. It also
supported client applications’ requests for data via TCP/IP, and automatically
created files on the PC for final storage data. Subsequent revisions in the 2.x
series added support for hardware as it was released and refined the clientserver architecture to make it more robust and flexible. Software development
kits and standalone clients were released to provide additional functionality.
NOTE
One of the main efforts in the development of LoggerNet 3.1 was to
incorporate support for the CR1000 datalogger. This included datalogger
management (connect, collect data, set clock, send program, etc.) in
LoggerNet, as well as programming support in CRBasic and Short Cut. To
help with creating CR1000 programs, a Transformer utility was developed to
convert existing CR10X Edlog programs to CR1000 CRBasic programs.
LoggerNet 3.2 added support for our new CR3000 datalogger. In addition,
LoggerNet Admin and LoggerNet Remote were developed, which provide
tools to support larger networks. These tools include security and remote
management capabilities, and the ability to run LoggerNet as a service.
LoggerNet 3.3 added support for the CR800 datalogger. A new file output
option was also added for table-based dataloggers. This CSV file format
option allows the creation of data files similar to those from mixed array
dataloggers.
LoggerNet 3.4 improved LoggerNet’s performance on Windows Vista. In
addition, changes were made to the user interface of the Numeric Display and
Graphs.
Beginning with LoggerNet 3.4, Windows NT 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 which
allows multiple data files to be opened, multiple graphs to be created, and
graphing in a variety of formats (Line Graph, X-Y Plot, Histogram, Rainflow
Histogram, and FFT). Another new application, the Network Planner, is
included. This is a graphical application that assists the user in designing
xv
Preface — What’s New in LoggerNet 4?
PakBus datalogger networks. It allows the development of a model of the
PakBus network, proposes and verifies valid connections between devices, and
allows integration of the model directly into LoggerNet 4.0.
See below for more details on what is new in LoggerNet 4.0 and each
individual application.
One of the main efforts in the development of LoggerNet 4.1 was 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 adds an 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. An option to provide feedback on LoggerNet is now
available from the LoggerNet Toolbar’s Help menu.
NOTE
Beginning with LoggerNet 4.1, Windows 2000 is no longer
supported.
LoggerNet 4.2 adds support for 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., 192.168.11.197). Leading zeroes are stripped for both IPv4 and
IPv6 addresses. Note that while LoggerNet now supports IPv6 addresses and
they can be used to specify servers, CR1000/CR3000/CR800 series dataloggers
will not support IPv6 until a future OS release. Check the OS revision history
on our website to determine when IPv6 support is added to the OS.
LoggerNet now supports display and input of Unicode characters/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. See Unicode in the LoggerNet help file index
for more information on Unicode and what applications support Unicode
characters. To support Unicode, an Insert Symbol dialog box has been added to
the CRBasic Editor. This allows you to insert Unicode symbols into your
CRBasic program for use in Strings and Units declarations.
The ability to set up subnets of the network map has been added to LoggerNet
Admin. The Setup Screen’s View | Configure Subnets menu item is used to
configure the subnets. Within each subnet, you can also specify groups of
dataloggers. The datalogger groups create folders than can be collapsed or
expanded when viewing the subnet. Once subnets have been configured, you
xvi
Preface — What’s New in LoggerNet 4?
can choose to view a subnet rather that the entire network in the Setup Screen,
Connect Screen, and Status Monitor.
You can now set up defaults 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. Note that the datalogger
must be running OS 26 or later in order for PakBus Encryption to be used. A
PakBus Encryption Key must be entered in both the datalogger’s device
settings and LoggerNet’s Setup Screen. AES-128 encryption is 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
there is more than one modem and phone line available to make the
connections.)
NOTE
You can now access a datalogger’s Settings Editor from the Connect Screen
either by right-clicking on the datalogger or from the Datalogger menu. You
can also manually set the datalogger’s clock 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 toggle.
You can now view additional statistics in the Status Monitor for table-based
dataloggers including watchdog errors, skipped scans, and battery errors. (Note
that there is a Poll for Statistics check box on the datalogger’s Schedule tab in
the Setup Screen that must be enabled 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 Section 9.1.3 Remote
Administration of the Task Master for conditions that must be met for remote
administration of the Task Master.)
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 previouslyconfigured tasks. However, imports have only been tested back
to LoggerNet 3.4.1. After upgrading (from any previous version
of LoggerNet), you should verify that all of your 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
Section 9.1.1.4 Define What the Task Does for an example of calendar-based
data collection.
xvii
Preface — What’s New in LoggerNet 4?
A Constant Customization feature has been added to the CRBasic Editor. This
allows you to define 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/entering a value, or with a list box. A step
increase/decrease can be defined for the spin box, as well as maximum and
minimum values.
The CRBasic Editor now allows you to Save and Open Display Settings.
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.
LoggerNet Products
Campbell Scientific offers four LoggerNet software packages, LoggerNet,
LoggerNetData, LoggerNet Admin, and LoggerNet Remote and several
standalone client products. Each of these packages is purchased separately.
LoggerNet is the main software application and comes with all of the
applications needed to set up and configure a network of dataloggers including
tools to write programs and monitor retrieved data. LoggerNetData is a
complementary product that includes applications that can be used on a remote
computer to monitor data, or retrieve, view, and analyze data that was collected
by LoggerNet into a file. LoggerNet Admin and LoggerNet Remote enhance
the capabilities of LoggerNet by providing management tools for more
complex networks. The difference in the two is that LoggerNet Admin offers a
complete LoggerNet package, while LoggerNet Remote, which was designed
to be run remotely, does not include the LoggerNet server.
New and Improved Applications
Several new applications, as well as improvements to previously available
applications, are included with the release of LoggerNet 4.0.
Toolbar
The LoggerNet 4.0 Toolbar has a completely new look and feel. 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.
Then, if you prefer a smaller version of the toolbar, you can select Favorites
View from the View menu. This will switch to a small view of the toolbar
containing only icons for applications in the Favorites category.
Additional options are available including the ability to show a LoggerNet
system tray icon (either whenever LoggerNet is running or only when
LoggerNet is minimized), the option of hiding the LoggerNet taskbar button
when LoggerNet is minimized and the system tray icon is showing, the option
of whether or not to minimize clients when the Toolbar is minimized, and the
ability to hide or show the main menu.
xviii
Setup Screen
Preface — What’s New in LoggerNet 4?
The Setup Screen now has the option of being used in an EZ View or a
Standard View. The Standard View is similar to the Setup Screen in older
versions of LoggerNet. In the EZ View, the EZ Setup Wizard is used to add
dataloggers and edit their settings.
Standard View Changes
A new menu item has been added to enable a Stations Only view. When this is
enabled, only stations will be shown in the Network Map and they will be
listed in alphabetical order. This can be especially helpful, when working with
a large network.
A Scheduled Backup menu item has also been added. This opens a dialog box
from which you can setup automatic backups of LoggerNet on a user-defined
schedule.
A new root device, the PakBus TcpServer, has been added. This device can
accommodate multiple incoming PakBus/TCP connections to service the
stations attached to it. Therefore, it allows the same IP port to be used to listen
for incoming connections from multiple dataloggers. The device has a Routing
tab that can be used to specify IP addresses and port numbers to be used for
outgoing connections to specific dataloggers attached to the PakBus TcpServer.
The Routing tab can also be used to cause LoggerNet to maintain a connection
with a range of dataloggers, once an incoming connection has been established.
Connect Screen
An Image Files tab has been added to the Setup Screen for the CR1000,
CR3000, and CR800 Series dataloggers. This tab provides an easy way to
retrieve image files from the datalogger on a specified interval. (Note this tab
is renamed File Retrieval in LoggerNet 4.1.)
A Notes tab has been added to all devices to allow the user to keep notes about
the device for future reference. This is purely for the user’s convenience. (The
information in a datalogger’s Notes tab is displayed in the Connect Screen,
when that datalogger is selected.)
A new File Output Format option, CSIXML, has been added. When this option
is selected, data is stored in XML format with Campbell Scientific defined
elements and attributes.
Individual devices and/or device branches of the Network Map can be copied
and pasted into the network.
Various other settings have been added including BMP1 Station ID, BMP1
Low Level Delay, PakBus Verify Interval, TCP Password, Enable Automatic
Hole Collection, Stay on Collect Schedule, and Collect At Most. See Section
4.2.4, Device Settings, or LoggerNet’s online help for information about these
settings and what devices they apply to.
The Connect Screen has been reorganized with most of the buttons now
residing on a toolbar at the top of the window.
xix
Preface — What’s New in LoggerNet 4?
A Table Monitor has been added in the middle of the window that can be used
to monitor the values for one entire table.
A Notes field has been added that displays the information from the Setup
Screen’s Notes tab of the selected datalogger.
A connection made in the Connect Screen is now subject to the Maximum
Time On-Line configured in the Setup Screen. (See the Device Settings help in
Section 4, Setting up Datalogger Networks, for information on how the
Maximum Time On-Line setting will affect a connection made using
LoggerNet Admin or LoggerNet Remote 4.0 to connect to a remote server
running an older version of LoggerNet.)
The Pause Data Displays option has been moved to the Edit menu. (In previous
versions it was available as a check box on the Connect Screen.)
The Update Interval for data displays has been moved from the Options dialog
to the display’s main window.
New options added to the data displays include an Auto Format option (rather
than specifying the number of decimal places to display), the ability to format
the timestamp for numeric displays, and the ability to specify what will happen
when a NAN is encountered in a graph.
Status Monitor
Task Master
The configuration of the data displays can now be saved.
A new File Format option, CSIXML, has been added to Custom Collection.
When this option is selected, data is stored in XML format with Campbell
Scientific defined elements and attributes. For Custom Collection, you also
now have the option of whether or not to include timestamps and/or record
numbers.
Two new statistics are now available to be monitored: Link Time Remaining
(the time remaining, in milliseconds, until Maximum Time On-Line is reached
and the device is automatically disconnected) and RFTD Blacklisted (indicates
that a station has been blacklisted by an RF Base because of a failed
communication attempt).
A new event type, After File Closed, has been added to the Task Master. Using
this event type, a task will be executed anytime a data file being written to is
closed.
Along with the above event type, FTP and SFTP capabilities have been added
which allow the just closed file to be transferred to a designated FTP server.
Short Cut
Support has been added to Short Cut for the CR9000X datalogger, the ET107
Evapotranspiration Monitoring Station, and the AVW200 Two-Channel
Vibrating Wire Spectrum Analyzer.
xx
Preface — What’s New in LoggerNet 4?
New sensor files have been added for the CMP3 Pyranometer, the IRR-P
Precision Infrared Temperature Sensor, the JC Ultrasonic Depth Sensor, the
CNR2 Net Radiometer, the CS106 Barometric Pressure Sensor, the OBS-3+
Turbidity Sensor, the 03002 Wind Speed and Direction Sensor, the 105E
(chromel-constantan) Thermocouple, the WindSonic1 (RS-232) TwoDimensional Ultrasonic Wind Sensor, the WindSonic4 (SDI-12) TwoDimensional Ultrasonic Wind Sensor, the HMP155 Temperature and Relative
Humidity Sensor, the SR50A Sonic Ranging Sensor (SDI-12 Output), the
CS450/455 Pressure Transducer, a Vibrating Wire Sensor (for generic
vibrating wire sensors and the AVW200), and a saturation vapor pressure
calculation
An Advanced tab has been added to the Finish screen for CRBasic dataloggers,
which allows the user to view the CRBasic code and launch the CRBasic
Editor.
There is now an option to send the program to the datalogger from the Results
tab on the Finish screen.
The user now has the ability to create custom sensor files using existing sensor
files as templates.
CRBasic Editor
The user can now manually set advanced outputs to high or low resolution.
The Add Device button has been removed. Peripheral devices are now listed in
and selected directly from the Available Sensors and Devices tree.
The CRBasic Editor now gives you the option to Save and Encrypt a file.
Encrypted files can be compiled in the datalogger but cannot be read by a user.
Dim variables can now be declared within a subroutine or function and are
local to that subroutine or function. The same variable name can be used within
other subroutines or functions or as a global variable without conflict. The F9
and F10 pop-up pick list will include the local variables for a specific
subroutine or function if the cursor is within that subroutine or function.
F11 can now be used to bring up a pop-up pick list that contains all userdefined functions found in the program.
A new button has been added to the toolbar (blue arrow) which takes the cursor
to user-defined functions and subroutines.
A new shortcut, CTRL-Y, has been added that will delete the current line.
Several options have been added to the Editor Preferences dialog box
including:
Variable Name Matching – When enabled variable names will be
capitalized based on how they are declared in the program, regardless of
how the user may have typed them.
Create .TDF File at Compile – The user can then associate a .TDF file
with a datalogger. This can be useful if communication is taking place
xxi
Preface — What’s New in LoggerNet 4?
over a slow or unreliable communication link where the attempt to receive
table definitions back from the datalogger fails.
Clear Undo/Redo List on File Save – Clears the change tracking in the
program when the file is saved. Otherwise change tracking is kept until
the file is closed.
Syntax Highlighting for Variables and Local Variables – Variables and
Local Variables can now be given their own syntax highlighting to make
them easier to identify.
You can now drag and drop a file onto the CRBasic Editor workspace to open
the file. Also, multiple files can be selected from the File | Open dialog box.
All selected files will be opened.
Support has been added for custom voice files for the VoiceSpeak instruction.
When inserting a VoiceSpeak instruction, the user then has the option of
choosing words from the standard Voice.txt file or from a user-created custom
voice file.
The CRBasic Editor now has alternate language support, if a separate
LoggerNet language package has been installed.
RTMC
Many new functions have been added that may be used when building
expressions in RTMC. These include string functions, time functions, start
option functions, and function with state. The ability to declare aliases for data
values used in expressions has also been added. See Section 5.2.1.4,
Expressions, or the Expressions topic in RTMC’s online help for more
information.
RTMC has a new Layout Toolbar which gives quick access to the Align, Space
Evenly, Make Same Size, Center, and Order menu items from RTMC’s
Component menu.
Graphics Options have been added to the Edit | Preferences menu item that
allow you to choose the maximum number of frames per second, whether
animation is enabled, and whether high quality or high speed is more
important. From this menu item, you can also choose the visual theme for
RTMC. This determines the look and feel of the application (i.e. colors, button
appearance, etc.). These options are available in both RTMC Development and
RTMC Run-Time.
An Edit | Customize menu item has been added which allows you to customize
RTMC’s toolbars and menus. This menu item is available in both RTMC
Development and RTMC Run-Time.
Panning functionality has been added to charts in RTMC Run-Time.
In RTMC Run-Time, all alarms on a screen can be acknowledged by rightclicking on the screen and then choosing “Acknowledge All On-Screen
Alarms”.
xxii
View Pro
Preface — What’s New in LoggerNet 4?
Miscellaneous other changes have been made to the settings for specific
components.
View Pro is included for the first time in LoggerNet 4.0. It maintains the ease
of use of our former data file viewer with greatly enhanced capabilities.
Large files can be loaded more quickly. Scrolling is more responsive for large
files.
View Pro allows you to have multiple data files opened at one time. Multiple
graphs can be created from the same file or from multiple files. There is no
limit to the number of traces per graph. Data can be graphed in a variety of
formats including a Line Graph, X-Y Plot, Histogram, Rainflow Histogram, or
FFT (2D or 3D).
You have the ability to create a Line Graph containing multiple strip charts.
This allows you to simultaneously display data from multiple files (one strip
chart per file) to compare data from multiple stations. The X-axes (timestamps)
of the strip charts can be synchronized to facilitate cross file comparisons.
Split
A Line Graph can use record numbers rather than timestamps on the X-Axis.
This allows you to display data files containing gaps in the timestamps.
From the toolbar of a Line Graph, you can bring up a Statistics box which
shows the average, standard deviation, minimum, and maximum of the
displayed points. From the toolbar you can also add a graph cursor to a Line
Graph. The cursor can be scrolled across the graph and the data values and
timestamp at the current cursor position will be shown.
View Pro has zoom capability to allow you to zoom in on a certain area of a
graph. You can also scroll a graph either from the graph itself or from the
opened data file.
You can print a graph either from a preview screen or directly from the graph
toolbar. The graph can also be saved in a variety of formats (BMP, JPEG,
WMF, EMF, or PCX).
Binary files (TOB1, TOB2, TOB3) can be opened directly in View Pro.
A Time Offset option has been added. This allows the user to specify a time
offset that will be applied to each item on the Select line that uses the Date or
Edate function to output a date. This may be useful when adjusting for different
time zones.
Split now maintains a log file, splitr.log, each time Splitr is run. The main
purpose of this log file is to enable users running Splitr in command line mode
to identify what happened with each execution of Splitr. If a second instance of
Splitr is started when one is already running, another log file, splitrunning.log,
will be written. This file simply identifies the time that the second instance of
Splitr was started and that Splitr was already running.
xxiii
Preface — What’s New in LoggerNet 4?
CardConvert
A new File Format option, CSIXML, has been added to the Destination File
Options. When this option is selected, data is stored in XML format with
Campbell Scientific defined elements and attributes.
Troubleshooter
The Troubleshooter now allows the user to customize the possible problems for
which warnings will be given. In addition, you can click on any highlighted
warning to bring up additional information about the warning.
For array-based dataloggers, you now have the option to do a full hardware
reset. You can also now bring up Station Status information for array-based
dataloggers. (Previously this was only available for table-based dataloggers.)
Capability has been added to the Comm Test to report Invalid Datalogger
Security and Invalid LoggerNet Security.
Network Planner
The Network Planner, a graphical application that assists the user in designing
PakBus datalogger networks, is introduced for the first time in LoggerNet 4.0.
The Network Planner allows the development of a model of the PakBus
network, proposes and verifies valid connections between devices, and allows
integration of the model directly into LoggerNet 4.0.
Data Filer
A new File Format option, CSIXML, has been added. When this option is
selected, data is stored in XML format with Campbell Scientific defined
elements and attributes.
You now have the option of whether or not to include timestamps and/or
record numbers in the data file.
RWIS Administrator
RWIS Administrator is a new application that has been added to LoggerNet
which provides support for communication with RWIS (Road Weather
Information Systems) weather stations.
Alternate Language Support
Certain LoggerNet clients can display the user interface component text (for
buttons, dialog boxes, etc.) in a language other than English if a separate
LoggerNet language package has been installed. If a language package is
installed on your machine, you will see the language in the list for the
Languages menu (Options | Languages).
In LoggerNet 4.0, additional applications now have alternate language support.
The applications that now support alternate languages are Setup, Connect,
Status Monitor, Task Master, Short Cut, CRBasic Editor, View Pro, Card
xxiv
Preface — What’s New in LoggerNet 4?
Convert, TroubleShooter, Network Planner, PakBus Graph, LogTool, the
Device Configuration Utility, Data Export, and the RWIS Administrator.
NOTE
Available alternate language packages are provided by Campbell
Scientific’s international representatives or on the CSI website.
They are not included in a standard LoggerNet installation.
xxv
Preface — What’s New in LoggerNet 4?
xxvi
Loading...
+ 550 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.