Multilogger Usersguide 55
Multilogger Usersguide 55
Software
USER’S GUIDE
Version 5.5
Disclaimer: The following document is provided to assist users with the installation, operation
and training in the use of our products. This document and our products are intended to be used
by technically qualified personnel. Contained herein is information that is proprietary to Canary
Systems and may not be reproduced or copied in any form, nor disclosed to outside parties by
any means whether directly or indirectly, without the written consent of Canary Systems. This
document is subject to change without notice and Canary Systems assumes no responsibility for
errors, omissions or misinterpretation. Furthermore Canary Systems makes no warranty as to the
suitability of this information and/or products for any given application or use.
Appendix A – Tables
A.1 Julian Day .......................................................................................................................................................... 111
A.2 ASCII Characters ............................................................................................................................................... 112
Section 1 – Introduction
MultiLogger is a Windows client application for MLGateway. It provides for configuring the programming
and data collection automation of MLGateway. It has been designed to make the job of configuring and
acquiring data from numerous types of data acquisition equipment faster, easier, and simpler. It is
compatible with Windows 95/98/ME/NT/2000/XP/2003/Vista/7/8 and supports a number of data collection
devices such as the Campbell Scientific CR500, CR510, CR10, CR10X, CR21X, CR23X, CR7, CR2xx,
CR800/850 and CR1000, Geokon LC-1 and 8500/8510, and Kinemetrics K2. For more information on the
control modules see the Operator‘s Manual for the respective unit.
MultiLogger is highly integrated with the other MultiLogger Suite applications and serves as a client
application of MLGateway and MLServer. Communication between the various software components of
MultiLogger Suite is depicted in the illustration below. Communications between MultiLogger, MLGateway
and MLServer are implemented using a highly reliable custom designed TCP based transport system.
MLGateway and MLServer installation and configuration information is found in Appendix B.1 and B.2
Note: MultiLogger is a client application for MLGateway and hence does not need to be running to
provide for data collection automation and monitoring.
See the MultiLogger Suite Installation Guide for direction with installing MultiLogger.
Networking Features
Client/server operation using MLGateway software.
Multi-user network support using MLGateway.
Automated data collection can operate as Application or Service model.
Multiple users can easily share network and datalogger configurations.
Program Options
Datalogger ID to help identify data files.
Three basic measurement intervals including single interval, read times and logarithmic.
Up to 8 different logarithmic intervals are supported as well as 8 read times.
Single interval with a range of 1 to 604,800 (once per week) seconds.
User defined Start and Stop times.
Configurable alarm action including control port activation and voice calls.
Up to (16) direct connect instruments can be specified.
Up to (10) 8, 16, 32, or 48 channel multiplexers can be used.
Each multiplexer channel can be configured by instrument type, conversion factors and units,
temperature measurement and correction and alarm limits.
Numerous program options including Gage Types, Units Conversion, Upper Channel devices,
Check Alarms types, Output Data, Alarm Action and Output Device are user configurable.
Communication System
Native support for TAPI devices (phone modems) and TCP/IP Socket devices.
Complete automation of data collection functions, including database update.
Security code can be used to prevent unauthorized program modifications and data collection.
Maximum connect time can be used to prevent extended long distance connection.
Many communication peripherals are supported.
Data collection can be specified as since last collection, all data or number of arrays.
Data file formats including comma, space or tab delineated ASCII.
Up to 1000 Input Storage locations can be monitored via the text based monitor.
Up to 128 Input Storage locations can be monitored via 4 charts on the graphical monitor.
Graphical monitor charts may be saved, loaded, printed and extensively configured.
Data Reduction
Roobrik, a powerful data processing tool is supplied with MultiLogger.
Data selector that allows you to select data based on start/stop/copy criteria.
Additional elements may be calculated using a powerful formula editor.
Data may be used to create a report, chart or OLE/DDE copied directly into Microsoft Excel.
Operation of Roobrik can be completely automated using its command line feature.
Help System
Context sensitive help available for most software options.
Complete re-architecting to support true client/server deployment with MLGateway acting as the
server and MultiLogger acting as a client.
Improved support for multiple MLGateway clients.
Improved logging and monitoring functions.
Data collection settings can now be customized for each node.
Improved communications reliability and improved message logging.
Monitoring and configuration of data import automation.
New VirtualDL for measurement automation using devices connected directly to the computer.
Improved functionality for creation and management of Gateway Folders.
Data collection from all Campbell CR800 and CR1000 tables now supported.
Configuration of multiple nodes for After Call-Back Do.
Ability to make multiple changes to Network Configuration and Save/Cancel in single step.
Please review our FAQ #28 found in our support directory at http://www.canarysystems.com/nsupport/ for
a more detailed list of enhancements.
Canary Systems may be contacted directly via phone, fax or e-mail. Unlimited support via phone and
email is provided for 30 days after installation. Ongoing support via phone, email and Webex is available
for a nominal annual fee.
NOTE: The latest versions of the software components are available without charge from the
support area of www.canarysystems.com. Older versions may be subject to upgrade fees. Contact
your software vendor or Canary Systems directly for more information.
Our website also provides numerous Application Notes and all the latest User‘s Guides. Press the
Support button at www.canarysystems.com to access these resources.
Note: To get started MLGateway must be activated on the workstation or server that the
MultiLogger client software will be connecting to. See Appendix B.1 for complete information on
MLGateway activation. DO NOT PROCEED UNTIL ACTIVATION IS COMPLETED.
Once the installation is complete and activation has been completed, the software can be started by
clicking Start | MultiLogger or Start | Programs | MultiLogger then double-click the MultiLogger icon.
A view typical of an empty Network Configuration shown after installation is depicted below. This is the
Network Manager view.
Menu Toolbar
The menu and toolbar at the top of the form provide access to commonly used functions.
The Help menu provides access to the Help Contents section of the MultiLogger
help file. Select About to display the MultiLogger About form with version running
and support information.
These functions are also duplicated in the Function menu at the top of the form.
Hint: This section will provide an example exercise getting started with MultiLogger to create a basic
network configuration to access a Campbell CR800 through a direct serial connection.
The MultiLogger
Network Manager view
will update with the
default Gateway List. It
will be blank because
no configuration has
been defined yet.
The Network
Configuration will
update with a default
Gateway.
Before additional
nodes can be added
to the Gateway the
Configuration Mode
must be activated.
Select the
default
Gateway1 and
click the Add
button, the Add
new Gateway
or Device form
will display.
Five items will display in the Add new Gateway or Device form. Gateway is a top-level node, the
remaining items are added to the currently selected Gateway.
Hint: See Section 3 for complete information on the Network Configuration node types.
The Network Configuration will update with the COM port added to the Gateway.
Note the Com Port drop-down on the configuration panel to the right.
Configure the appropriate Com Port to match the port or adaptor used for accessing the data acquisition
equipment.
Next, add the data acquisition device, in this case the Campbell CR800. Press the Add button to display
the Add new Gateway or Device form. Note that devices are organized by type, to add the CR800 use
the button to expand the Campbell Current Loggers group and select CR800.
Hint: When creating data acquisition nodes a default folder will be created in the [Shared
Docs]\MLGateway\Default (since this is the default Gateway) to be used for
Note: When using the Assign a new Configuration File option you’ll have opportunity to rename
the default folder name.
For example, the option Assign a new Configuration File was selected. The Network Configuration
updated to show the new node, however the default CR800 nodename was changed to MyCR800.
Note the default Project Path was also updated once the nodename was changed.
The Configuration File hasn‘t been created yet, the Logger form needs to be used to create the
Configuration File, as the message at the bottom of the configuration panel indicates.
Hint: MultiLogger version 5 differs from previous versions in that multiple changes to the Network
Configuration can be made requiring only a single press of the Save button.
To create the configuration file for the new CR800 node, double-click it or use the Logger button at the
top of the form.
The Logger form is used for configuring and monitoring the data acquisition gear, in this case a Campbell
CR800. It consists of several controls and interfaces for the various functions.
Additional information on the Logger form components will follow, more detailed information follows in
sections 4 and 5.
The pull-down menus provide access to basic file operations, additional program configuration forms, the
functions depicted on the toolbar and the on-line help system. The pull-down menus are accessed using
the mouse or <Alt> key combinations, where key is the letter underlined in each menu option. For
example, pressing <Alt> F displays the File menu.
Open configuration file – Opens a file dialog so you can load a different
configuration file. The file selected using the file dialog becomes
associated with the selected datalogger.
Hint: Configuration files must always reside in the Project Path, if a file
outside the current Project Path is selected it will be copied automatically
to the Project Path after selection.
Save configuration file – Saves the current configuration using the name already specified.
Save configuration file as… – Saves the current configuration using a name you will select using the
save file dialog.
Print configuration file – Sends a report to the default printer detailing the program and connection
configuration.
Print setup – Opens the print setup dialog so you can modify the default printer settings.
Exit – Closes the Logger Configuration form. If a monitoring session is active it will be terminated. If
changes were made to the configuration without saving you will be prompted to save these changes.
Input Locations – Invokes the Configure Input Locations form for configuring the pre-defined locations
for data values, or for defining new locations.
Total Station – To configure an attached Robotic Total Station. See the Canary Systems Total Station
User‘s Guide for information on this option.
Hint: The choices on the Program menu will depend on the datalogger selected. Review section 6 for
information on the dataloggers supported by MultiLogger.
The Configure menu, depicted at right, provides access to additional monitoring configuration options.
Text Monitor – Invokes the Select Locations form which is used to select
locations for the text monitor. See section 6.3 for more information.
Capture Intervals – Configures the data capture facility that operates while the
monitor mode is active. See section 6.6 for more information.
Terminal Font – Displays a font dialog which configures the font for the terminal emulation window. See
section 6.8 for more information.
MS Excel Link – Configures the OLE linking to Excel for data that is captured during monitoring. See
section 6.9 for more information.
Notification System – Configures the notification system which allows you to send e-mail using data
collected through data collection or monitor mode capture. See section 6.10 for more information.
Preferences – Configures various display and function parameters. See section 6.11 for more
information.
The Logger toolbar can be hidden to maximize the display for monitoring. The functions
are then accessed through this menu.
In addition, right clicking anywhere in the configuration form (except on the charts) will
display a pop-up menu which also duplicates the functions of the configuration form
toolbar.
The Help menu, depicted at right, accesses the on-line help system, and About box.
Help Contents – Displays the contents of the MultiLogger on-line help system.
The toolbar at the top of the configuration form speeds access to the most common datalogger functions.
These functions are duplicated in the Function menu displayed at the top of the form and by right-clicking
anywhere on the form.
The Zero, Start, Collect, Monitor, Stop, Clear and Test functions all
require a connection to the selected datalogger. When these functions
are initiated MultiLogger will first attempt to connect (unless the
connection has already been established) using the devices you have
specified on your Network Configuration. This may include dialing
modems, making socket connection connections, sending transceiver
ID‘s or addresses, etc.
The Zero, Start, Stop, Clear and Test functions also require a program to be downloaded into the
datalogger.
Hint: You should never Abort any of the program download functions!
After successful download the program will be compiled and loaded into
memory for execution by the datalogger. The dialog will update as
shown.
After successful compile the progress dialog will update to show the
download succeeded.
Zero - Downloads the Zero mode program into the datalogger which reads all channels without any
conversions as listed on the Channel Configuration form so the baseline readings can be obtained.
All interval and start/stop time configurations are also ignored.
Hint: The readings taken in the Zero mode are not stored for collection.
Once the Zero mode starts and readings are obtained, the Configure Zero Readings form will
display automatically when selecting Start, or any other program download function.
Hint: Only channels that were configured in the Text Monitor will display in the Zero Readings form.
The purpose of the Configure Zero Readings form is to allow selection of zero readings from
specific channels. For example, perhaps only a few of the channels required a new zero reading. Use
the checkbox list on the left side of the form to select the Zero Readings to be updated. The form also
lists the Location, Label, Description, Current Zero and New Zero for reference.
Use the Select All or Clear All buttons to select all zero readings, or clear the selections,
respectively.
Press Accept when finished reviewing, press Cancel to cancel selection of any new Zero Readings.
Start - Downloads the Start mode program which is generated from all the various program
configuration options.
After successful Start mode download the Monitor Mode will start automatically.
Hint: After the Start function is first run, the caption on the button will change to Update, as below.
Collect - Data are collected from the datalogger using the settings
defined on the Data Collection tab of the Network Manager. During
the data collection a status gauge will indicate the progress of the data
collection. A message will display at completion if the operation
succeeds. If successful, the Last Data Collection edit box will update
with the current date and time. Monitoring will be paused during the
data collection procedure.
A status form will display at the end indicating how many arrays of data
were collected or if the collection failed.
Monitor - The Monitor mode is a real-time display of datalogger memory locations using text and
graphical monitoring.
Clear - The storage memory of the datalogger is cleared by pressing this button.
Hint: If there is a program currently operating in the datalogger it will be cleared by the Clear
operation! You must restart the datalogger by pressing Start/Update after running the Clear function!
Test - Downloads the Test mode program which allows you to selectively monitor individual
multiplexer channels. This is useful when troubleshooting instruments on large systems. Simply click
on the instrument channel to monitor, this channel will be selected as shown by its display shown with
a yellow background on the text monitor. The selected channel will be continually read until a different
mode (either Zero or Start/Update) or channel is activated. The units of the Test mode are the same
as the Zero mode, i.e. no math conversions are applied. All interval and start/stop time configurations
are also ignored.
Click on
the Value
cell for the
channel to
read in Test
mode
Hint: The readings taken in the Test mode are not stored for collection.
Roobrik - Invokes the data reduction program Roobrik. Roobrik is a software tool included with
MultiLogger that can process data files, calculate values and generate reports, charts and
spreadsheets. See the Roobrik User‘s Guide for complete information on Roobrik.
The tabs of the page control on the Logger form have the following functions. Each is explained in greater
detail in other sections of this manual.
The first tab, the Project tab, describes the Project configuration.
The next tab, the Program tab, describes how the datalogger is programmed.
The Text Monitor tab contains the controls and displays of the text based monitoring.
Graphical Monitor contains the charts used for the graphical monitor.
Terminal provides you access to the terminal emulation window.
Hint: To display the properties for any element of the Network Manager click on the element, the panel on
the right will update with respective property fields.
Following are explanations for the various parameters associated with each type of node.
3.1.1 Gateways
Essentially a Gateway is a computer, whether local or remote, that provides a way to access the
dataloggers that are attached. If the datalogger(s) are connected directly to the PC on which MultiLogger
is running then the Gateway is considered Local, if the datalogger(s) are connected to a PC that is
accessible via TCP/IP then the Gateway is considered Remote.
Hint: Whether a Gateway is Local or Remote the MLGateway application included with the installation
provides for access to the Gateway. See Appendix B.1 for more information on installing and activating
MLGateway.
Hint: MultiLogger supports multiple Local and Remote Gateways. Gateway Lists can also be retrieved by
connecting to MLServer and retrieving the list of Gateways that have been configured. Information on this
functionality will be detailed in the following sections.
The following information must be entered into the Gateway panel which displays to the right of the
Network Configuration Tree when a Gateway is selected in the tree.
Gateway Name – The Gateway Name is shown in the Network Manager frame, to change the name
use the Windows slow left double click on the Gateway name. The cursor will switch to edit mode and
the name can be changed. The Gateway Name is limited to 32 characters. Press Save on the toolbar
after changing the name. When adding new Gateways the default name is "Gateway" plus a
sequence number which is the number of Gateways, plus one, currently defined. A Folder needs to
be defined for each Gateway.
Gateway Enabled – Check whether the Gateway is enabled, this primarily affects the start-up
operation of MultiLogger, no connections are attempted to Gateways that are disabled. If the
Gateway has data collection configured it will still be automated by MLGateway.
Gateway Type – Select whether the Gateway is Local or Remote. Local would be selected when
MultiLogger is connecting to MLGateway on the local computer. Remote refers to a remote computer
running MLGateway.
IP Address - Enter the address of the computer which is running MLGateway. For Local Gateways
the IP Address edit will be disabled, the local IP of 127.0.0.1 is automatically used. For Remote
Gateways the machine name or IP of the computer running MLGateway must be entered.
Port – Configure the Port used for communication to the Gateway. The default of 9001 is used for
Local and Remote Gateways. Multiple copies of MLGateway can be running on a single computer
with different Port assignments.
Folder – Configure the folder where the Network Configuration is stored. The default folder path is
[Shared Docs]\MLGateway\Default.
Hint: When editing folders on Remote Gateways you must have read/write access to the [Shared
Docs]\CanarySys\MLGateway path.
Click on the to configure Gateway Folders. This displays the Configure Gateway Folders form.
The Default folder will be shown, use the button to
configure the Folders.
Press to Delete the currently selected Folder. You will be asked to confirm deleting the
Folder as this deletes the entire folder path. Note: You cannot delete the Default folder.
Press to Select the currently selected Folder as the Folder for the selected Gateway.
Press to Cancel changes made. Note: This will not cancel changes made to the
Folders. Note: This does not cancel most changes made to the folder configuration.
For example, to add a new Gateway Folder first press the Add
button. Enter the new Gateway Folder name in the edit.
Press OK to save the new Gateway Folder name and return to the
Configure Gateway Folders form.
Notice the Network Manager will now update with the new Gateway Folder. Notice the Network
Configuration is blank because the new Gateway Folder does not have any nodes defined yet.
Hint: To copy the settings of one Gateway to another use the Copy button on the Configure Gateway
Folders form.
Notice also that a new path was created in the [Shared Docs]\MLGateway folder.
Use My Computer to browse to the Public Documents folder, Vista/W7 path is shown.
Alternately browse from the root of the drive to find the Public Documents folder. Note the actual path
is \Users\Public\Public Documents\CanarySys\MLGateway.
When running on Windows XP or Windows 2003/2008 the Public Documents path is found in the
\Documents and Settings\All Users\Documents folder.
Note the new folder, MyGatewayFolder, named using the Configure Gateway Folders form.
Hint: To allow other users on the network access to the Gateway Folders on this computer you will need
to configure the Sharing for the CanarySys folder.
Pakbus Address – Enter the Pakbus address of the computer, the default is 4094.
Database Alias - This drop-down will only be
enabled if the Gateway List Configuration is
configured for Get Gateway List from MLServer.
The Gateway List stores the list of available
Gateways as well as the list of databases that have
been configured on the Gateway computers. The
Database Alias will then update with the list of
databases that have been configured. If no database
is shown or the database to be used for the Gateway
is not shown then check the configuration of
MLServer on the Gateway computer. See the
MLDBConsole User‘s Guide for complete information
on MLServer including the configuration and
management of databases.
Gateway Log File Settings – Configure the messaging detail for the Gateway log file, or the log file
generated by MLGateway. Check all options for maximum detail. See Appendix B.6 for complete
information on the Gateway log file and message types.
There are 3 types of Ports that can be connected to the Gateway for
building connections to the DAU‘s (as shown in the Add new Gateway or
Device form shown at right), COM or serial ports, TCP/IP Sockets and
TAPI based Phone Modems.
TCP/IP Socket – This selects the installed TCP/IP networking of the Gateway to connect to a
terminal server or similar device which has a datalogger or network of dataloggers connected to it.
Common terminal server devices include Campbells NL100, NL105, or NL120 or the Lantronix UDS-
10 or UDS-1100 Device Servers.
Allow Call-back – Check to open the socket and port to accept incoming connections from the
remote TCP/IP devices that have dataloggers attached which are generating call-back events. See
Appendix B.5 for more information on call-back.
Port – Specify the port that should be opened for accepting connections from TCP/IP devices that
have dataloggers attached which are generating call-back events. This should be a different port than
what is configured for the outgoing connection to the remote TCP/IP device.
Extra Response Time (msec) – Specify any additional time in milliseconds that should be allowed
for receiving responses through the socket. This is particularly helpful where network latencies may
be delaying the communications, a value of 500 (0.5 second) or higher may be required to allow for
these latencies. Note: It is important to specify a value that approximates the actual latencies of the
network, because setting an unnecessarily high value can slow down communications and recovery
mechanisms in certain cases. Use the Windows utility PING or other network testing tools to check
the network latency for a particular connection.
Phone Modem – This selects a phone modem that has been installed on the Gateway.
Modem – A list of available phone modems will be shown in the drop-down list, select from one of the
available modems. If the Modem list is empty or the wrong modems are shown, then use the Control
Panel | Phone and Modem to check the installed modems.
Note: Modem configuration is determined through the Control Panel of Windows, MLGateway
uses the Windows Telephony Application Interface, or TAPI, to control modems. If connection
difficulties are experienced when using the Phone Modem then changes to the modem settings,
using the Control Panel, will probably be required. Common problems involve the communication
rate and error correcting protocol, older modems in use with some data acquisition hardware may
not support the higher speeds and complex error correcting protocols common in newer
modems. It may be necessary to fix the baud rate, usually at 9600, and disable any error
correcting protocols. Contact Canary Systems for additional application assistance.
Allow Call-back – Check to enable the Phone Modem for Auto-Answer, to accept incoming calls to
accept incoming call-back events from phone modem equipped dataloggers. See Appendix B.5 for
more information on call-back.
A datalogger may be connected to the Gateway using one or more Communication Devices. These
include the RF Modem, MD9 Modem or Generic Modem. Select a port and press Add to include any of
these devices in the Network Configuration.
MD9 Modem – This refers to the Campbell Scientific multi-drop networking devices, either the MD9
or MD485.
The following settings can be configured for each MD9 Modem Device:
MD9 Modem Name - Specify a name of up to 32 characters that will be used to identify the MD9
Modem in the Network Configuration. Change the name by left slow-clicking on the name shown in
the Network Configuration tree.
Baud Rate – Configure the speed at which MD9 Modem will be communicated with, this setting must
match the speed of the connected modems. Note: This option will only display if the MD9 Modem
is attached to a COM port.
IP Address, Port – Configure the IP Address and Port to be used to connect to the MD9 Modem.
Note: This option will only display if the MD9 Modem is attached to a TCP/IP Socket.
Dialed Using Phone Number – Configure the Phone Number to be used for connected to the MD9
Modem. Note: This option will only display if the MD9 Modem is attached to a Phone Modem.
Extra Response Time (msec) – Specify any additional time in milliseconds that should be allowed
for receiving responses through the radio network. This is particularly helpful where network latencies
may be delaying the communications, a value of 500 (0.5 second) or higher may be required to allow
for these latencies.
Generic Modem – Generic Modems are specialized communication devices, defined by the user‘s
needs. It includes a simple scripting system to provide for sending commands and receiving
responses to establish connections. See Appendix B.3 for complete information on this device.
The following settings can be configured for each Generic Modem Device:
Generic Modem Name - Specify a name of up to 32 characters that will be used to identify the
Generic Modem in the Network Configuration. Change the name by left slow-clicking on the name
shown in the Network Configuration tree.
Baud Rate – Configure the speed at which Generic Modem will be communicated with, this setting
must match the speed of the connected modems. Note: This option will only display if the
Generic Modem is attached to a COM port.
IP Address, Port – Configure the IP Address and Port to be used to connect to the Generic Modem.
Note: This option will only display if the Generic Modem is attached to a TCP/IP Socket.
Dialed Using Phone Number – Configure the Phone Number to be used for connecting to the
Generic Modem. Note: This option will only display if the Generic Modem is attached to a
Phone Modem.
Extra Response Time (msec) – Specify any additional time in milliseconds that should be allowed
for receiving responses through the modem network. This is particularly helpful where network
latencies may be delaying the communications, a value of 500 (0.5 second) or higher may be
required to allow for these latencies.
Half Duplex – Check this box when the modem is incapable of simultaneously receiving and
transmitting characters.
3.1.4 Dataloggers
Dataloggers read instruments and store the data for later collection by MLGateway. Numerous models
are supported as detailed in Section 6. See the respective Operators Manual for more information on
specific models. An example Campbell CR800 is selected in the Network Configuration below.
Security Code – If the datalogger has a security code other than 0, the security code will need to be
entered or certain operations such as program Update will fail. See the datalogger Operators Manual
for a description of security settings.
Extra Response Time (msec) – Enter the Extra Response Time in milliseconds.
Set Clock Offset (sec) – During scheduled data collection datalogger clock can be compared to the
Gateway clock and automatically adjusted if the difference exceeds the amount specified. Set to 0 to
disable the clock check. Even if collecting data more than once per day, only one clock adjustment
will be made per day. Allow enough offset to account for poor communication link quality. For
example, when using a direct connection a setting of 1 second will work reliably, however for a radio
connection the setting should be on the order of 10 seconds or more.
Time Zone Offset (hrs) – Use this edit to allow for adjusting clocks in time zones different from the
Gateway time zone. Enter a value positive or negative to reflect the difference between the
datalogger clock and the PC clock. For example if the PC clock is 4:29:57PM but the datalogger clock
is 2:29:57PM then enter an Offset of –2.
Maximum Time On-Line (sec) - Specify the maximum number of seconds allowed for scheduled
data collection during an individual call. This value also sets the length of time for manual collection
when the data is collected via the Logger form. Data collection will be terminated if the number of
seconds is exceeded.
Maximum Packet Size - The data are transmitted and received in groups called packets. When
referring to array loggers (CR510, CR10X) a packet is actually 2 bytes, when referring to table
loggers (CR2xx, CR800, CR1000) a packet is a single byte. Valid values are 32 to 2048. Optimum
packet size is a function of the communication link quality and the type of logger connected. The
defaults assigned for each datalogger type should generally be used.
Project Settings
Configuration File – This file stores the
configuration information for the selected
datalogger. Note: When first adding a
datalogger to the Network Configuration you
will need to select a configuration file using
the button located to the right of the edit.
Alternately Multilogger can create a file for
you, press Save to invoke the Select Logger
Configuration Form, shown below:
Select Browse to an existing
Configuration File to select a previously
created configuration file, select Assign a new Configuration File to start the Logger configuration
form with a default configuration. This configuration can then be saved to a different file if desired.
Project Path – See section 4.1 for more information.
Description – Verbose description of the datalogger, up to 255 characters may be entered.
Datalogger ID – See section 4.1.7 for more information.
Last Updated – See section 4.1.6 for more information.
Last Data Collection – See section 5.1.1 for more information.
Last Battery Voltage – This edit indicates the battery voltage from the last collected array of data,
whether collected using the Agent or the Logger configuration form. If the data have not been
collected yet, or the battery was otherwise unavailable, then the edit will be blank. It is a READ-ONLY
field and can only be modified by the system.
3.1.5 Tasks
Tasks are programs or batch files that are designed to be run after collecting data due to a call-back
event or after collecting data from all the dataloggers on a particular Gateway.
The follow settings can be configured to customize the Data Collection for each datalogger:
Schedule
Enable Schedule – Check this option to enable scheduled collection of data from this datalogger. If
unchecked data can still be collected but it must be done manually using the Logger form.
Automatic Database Import – Check to enable automatic import of the collected data into the
database. This option will only be enabled if the Gateway List is retrieved from MLServer, since
MLServer imports the data collected by MLGateway.
Schedule – There are 3 basic options for the collection schedule:
ASAP – Collect the data continuously as soon as possible. The actual interval will depend on
how many other stations have scheduled data collection enabled.
Interval – Select between 1 minute and 12 hours as an interval for data collection. Use the
Offset Hour and Minute spin-edits to offset the interval from the even time increments, e.g. if
Interval is 1 hour and Offset Minute is 5 then data collection will be scheduled at 5 minutes after
the top of each hour.
Daily at Time - Specify the time of day to be used for data collection. Check which days of the
week to collect data using the Sunday – Saturday checkboxes to the right.
Call-back Schedule
Enable Schedule – Check this option to enable scheduled collection of data from this datalogger
AFTER a call-back event. If unchecked call-back data collection will still be initiated but only when a
call-back event is received from the sending dataloggers. This functionality provides for automatically
increasing the frequency of data collection after a call-back event.
Interval – Select between 1 minute and 12 hours as an interval for the call-back data collection. Use
the Offset Hour and Minute spin-edits to offset the interval from the even time increments, e.g. if
Interval is 1 hour and Offset Minute is 5 then call-back data collection will be scheduled at 5 minutes
after the top of each hour.
Duration – Select between 1 minute and 48 hours as the duration of the Call-back Schedule.
Failure Settings
Retries - Specify how many attempts should be made to collect from this datalogger. Generally the
default should be used, however if the connection is known to be unreliable this may be increased.
Delayed Retries – Specify whether and how many retries will be made at the delayed interval if the
Retries setting is exceeded during a data collection attempt. Specify 0 to disable. The maximum
setting is 99.
Delayed Retries Interval – Select the interval for the delayed retries, between 1 minutes and 60
minutes. Data collection for this datalogger will be paused if Delayed Retries and the Delayed
Retries Interval are exceeded. For example, if Delayed Retries is configured for 24 and the Delayed
Retries Interval is 60 minutes then data collection for this node will be paused after 24 hours of
unsuccessful data collection attempts. A successful collection resets the Delayed Retries counter.
Resume Schedule After Delayed Retries – Check this option to resume the scheduled collection in
the event of collection failure and the failure of the Delayed Retries at the Delayed Retries Interval.
For example, if scheduled collection is once per day at noon and Delayed Retries is configured for 10
and the Delayed Retries Interval is 60 Minutes, then collection attempts will continue for 10 hours
after the failed collection at noon, with the option checked collection will continue the next day at
noon.
After Collection Do
The control shown in the group lists all other datalogger nodes and any Tasks that have been configured.
Use the check box located to the left of each datalogger or Task to select that option for execution after
data collection for the current node. If selecting a datalogger then data will be collected automatically. If
selecting a Task then the Task will be run. The data collection can be a scheduled data collection or as a
result of a Call-Back event.
Data Recorded Since Last Collection - When selected the pointer recorded at the last data
collection will determine how many arrays are to be collected in subsequent attempts.
Hint: First data collections from new dataloggers will ALWAYS collect ALL DATA.
All Data - All data in the dataloggers memory will be collected at each collection.
Number of Arrays - Only the specified number of arrays will be collected at each collection.
Specify the format of the data files that will be stored after a successful data collection.
Note: The stored data format will always follow English locale regardless of the Locale setting of
the computer being used to collect data.
Comma Delineated ASCII - This is a standard format for importing into spreadsheets and other data
processing programs. Values in the array are separated by commas.
Example array; 1997.0,275.00,1253.0,30.000,0.75164,0.0000,0.0000,0.0000,11.849,23.130
Space Delineated ASCII - Values in the array are separated by the space character (ASCII #32).
Example array: 1997.0 275.00 1253.0 30.000 0.75164 0.0000 0.0000 0.0000 11.849 23.130
Tab Delineated ASCII - Values in the array are separated by the tab character (ASCII #9).
Example array: 1997.0 275.00 1253.0 30.000 0.75164 0.0000 0.0000 0.0000 11.849 23.130
Check Convert Decimal Day to Y1900 Format to replace the decimal day value with Y1900 value,
calculated from the date and time values stored in the array of data. The Y1900 format is a very useful
format for representing the date/time stamp of the data, this format is supported by many data reduction
and graphing software packages such as Microsoft Excel.
The Y1900 Format is an integer representing the number of days that have elapsed since January 1st,
1900, then a fractional part to represent the portion of the day that has passed, for example the number
37623.375 represents January 2, 2003 at 9:00AM
Data are collected from datalogger nodes and stored in files that have a root name using the
configuration file name. For example, using the example Network Configuration and node
name/configuration file name created previously, the primary data file to be collected will be
MyCR800.dat. This file will be stored in the Project Path for the node, in this case:
[Shared Docs]\MLGateway\MyGatewayFolder\MyCR800.
Hint: Remember the actual [Shared Docs] path differs between Windows versions.
On Windows XP/2003/2008: \Documents and Settings\All Users\Documents\CanarySys
On Windows Vista/7: \Users\Public\Public Documents\CanarySys\
When data collection is initiated and successful the collected arrays are copied to the file name in one of
the following ways;
Append to Data File - The collected arrays of data will be appended to the node data file.
Overwrite Data File - The collected arrays of data will overwrite the data file named in node data file.
Create New Data File - A new file name will be generated using the node data file name and a 4
digit sequence number and then collected arrays of data will be stored to this file. If the file exists
prior to collection the 4 digit sequence number will be increased until the file name is unique.
Note: If the data collection is aborted or otherwise does not complete the data file will not be modified.
During data collection the file tempfile.dat is used to store the collected arrays in binary format. Once
data collection successfully completed the data are processed and copied into the data file.
See Section 6 for specific information on data collection from each type of datalogger supported.
Click on the Data Collection Status tab to show the current status of data collection. The following
information and controls are provided.
In addition to the Data Collection Status panel, the Network Configuration tree will highlight the
datalogger nodes in various colors to describe the collection status. When first creating the Network
Configuration for the project, or when adding dataloggers to an existing network, no color will be
assigned. If scheduled data collection has been enabled, the background color of the node will indicate
the status of the collection.
The last data collection attempt failed and the Agent is in Delayed Retries.
Due to the Retries sequence being complete, scheduled data collection is now disabled.
The node is disabled. Communications and scheduled data collection are disabled.
In addition, an hourglass icon will display to the left of the node name during active data collection
tasks to indicate that the Agent is busy.
Note the button located throughout the forms, these provide for modifying the datalogger
programming. Included with MultiLogger is an application, MLEditor, which provides for editing the
programming files. See Section 7 for more information on MLEditor.
The general organization of the form and its functions are similar between different types of dataloggers.
See Section 6 for additional details on the differences in the form depending on the type of datalogger
being configured.
This section will provide information on the Project and Program tabs, the components of the Logger form
that involve configuration and programming of the dataloggers. The following section will provide
information on the monitoring features of the Logger form.
The Project tab displays basic settings related to the configuration of the system. A typical screen is
depicted below.
Hint: See the following section regarding path limitations for loading/saving of the Configuration Files.
The Project Path informs you of the default folder where the configuration file was saved to or loaded
from. In addition this path will be used for all files that are related to a configuration and monitoring
session. To change this path you must open a new configuration file or save your current configuration to
a new folder. The default path is assigned when the datalogger node is added to the Network
Configuration by creating a folder with the same name as the node in the [Shared
Docs]\MLGateway\Folder path.
Hint: You can load configuration files from outside the Gateway Folder path, however if they are outside
the path of the current Gateway Folder path they will be copied to the current path. You cannot save a
configuration file outside the Gateway Folder path.
See Section 3.1.1 for additional information on the Gateway Folder paths.
The following files will be created and stored in the Project Path:
File Type Extension Description
Configuration File .cfg Contains all your program and monitoring settings
Download File .??? Extension matches datalogger type
Instruction Files .??? Extension matches datalogger type
Location File .loc Contains input storage/final storage definitions
Data File .dat Contains data that you collect
Temp Data File .tmp A temporary data file used during data collection
Chart Template .tee The templates used for your Graphical Monitor
4.1.3 Description
Provide a more verbose description of the datalogger using this edit. Up to 255 characters may be
entered.
By default the download file loaded into the datalogger when pressing Start/Update on the MultiLogger
toolbar is the one named by using the Configuration File root name, with the extension to match the
datalogger type. This file is automatically created by MultiLogger when the Zero, Start/Update or Test or
Info functions are run.
However, if an alternate file should be used by the Start/Update function, specify that name in the
Download File edit. Select the file by pressing the button.
Hint: When specifying a Download File that differs from the default file all of the Program file options are
disabled. In addition, the Zero and Test modes are also disabled. The reason for this is that, with a non-
default file name, MultiLogger assumes that the download file does not need to be generated.
The Download File may be loaded into the MultiLogger Editor by pressing the button.
This displays the type of datalogger being configured with the Logger form. This cannot be changed in the
Logger form, it is selected when the Network Configuration is built.
Records the date and time when the Start function was last run. You cannot edit this field, it is auto-
generated by MultiLogger and saved in the configuration file as a reference.
4.1.7 Datalogger ID
The Datalogger ID is a number that is stored as the first element in every array of Final Storage data. This
is useful for identifying data when collecting data from multiple dataloggers using multiple configuration
files. The ID should be unique for each datalogger ensuring that the collected data files are not confused.
Once assigned, the Datalogger ID should not be changed for a given datalogger.
When adding dataloggers and assigning new Configuration Files, Datalogger ID‘s will be automatically
assigned beginning with ID 100. However the default ID may be changed by modifying the ID shown in
the Datalogger ID edit.
Hint: For older Campbell Control Modules such as the CR510 and CR10X, the ID is limited to a value of
1-511, for newer dataloggers such as CR2xx, CR800 and CR1000, the ID is limited to a value of 1-9999.
Further, the Datalogger ID is used as the root file name for the Location File used to define how to import
data from each datalogger configured in the Network Manager. For example, if the Datalogger ID is 100,
the Location File created by MultiLogger will be 100.loc. This file is found in the Project Path and is
automatically updated whenever the program for the datalogger is modified. See the MLDBConsole
User‘s Guide for more information on the format of Location Files.
Press OK to ignore the error and continue with enabling the scheduled data collection. Press Cancel to
uncheck the Enable Schedule option for the datalogger node currently selected in the Network Manager.
The Program tab displays and provides access to all the programming options of the datalogger.
Hint: The options shown on the page will differ slightly depending on the type of datalogger selected. See
Section 6 for complete information on Program options for all supported dataloggers.
The Data Output refers to an instruction file that contains the programming that determines when data
are actually stored. For example, you may select an interval of 60 seconds using the Single Interval
option but select Every 1 Hour as the data storage interval. When you are monitoring readings you will
see them update every minute but when you collect data it will have an hourly interval.
Another use of this feature is in the case of alarm monitoring, you may read instruments at some defined
interval, say every 300 seconds ( 5 minutes), but with 'During Alarm' selected as the Data Output option
data are only stored when one of the instruments exceeds it's high or low alarm settings.
Hint: To output data every time readings are taken select Always as the Data Output option.
WARNING: Certain combinations of Interval Types and Data Output options may not necessarily
work as intended. In general you should follow these guidelines when using the Data Output
feature, only use Single Interval with a scan rate that is faster than the Data Output option. For
example, selecting a Single Interval of 3600 seconds (every hour) but selecting 'Every 15 Minutes'
as the Data Output option will only output data when readings are taken, at the hourly interval! To
be sure your selections of Interval Type and Data Output are working correctly you should
conduct a test to verify proper data storage.
The selected Data Output instruction file may be loaded into the MultiLogger Editor by pressing the
button. Additional Data Output options may be defined by editing the MultiLogger setup files.
The selected Alarm Action instruction file may be loaded into the MultiLogger Editor by pressing the
button. Additional Alarm Action options may be defined by editing the MultiLogger setup files.
Hint: Do not specify a device, such as an external data storage module, that is not connected to the
datalogger!
The selected Storage Device instruction file may be loaded into the MultiLogger Editor by pressing the
button. Additional Storage Device options may be defined by editing the MultiLogger setup files.
Specify whether the Single Interval, the Logarithmic Intervals Table or the Special Read Times are
used to schedule readings.
When using the Single Interval option, select from the drop-down the desired interval. The interval
selection will synchronize with the datalogger clock, for example selecting ‗1 Hour‘ will synchronize
readings on the hour and every hour. The maximum interval length is once per week, ‗7 Day‘, the
minimum will depend on the datalogger being configured.
When using the Logarithmic Intervals the Logarithmic Intervals Table will be used to schedule
readings. Enter up to 8 different interval lengths and iterations.
When using the Special Read Times the Read Times Table will be used to schedule measurements.
Enter up to 8 times each day that the datalogger will take measurements. To disable a particular time
clear the Enable Read Time n, where n is 1 through 6, check box. Time is entered in 24 hour format, a
warning will display if the format is incorrect.
Hint: Avoid enabling multiple Read Times with the same time configuration.
Check or clear the corresponding checkbox to enable or disable the Start Time and Stop Time. If
enabled, the time as selected for the respective month, day, hour and minute will be used. The Start
Time and Stop Time can be used with any of the Interval Types.
If the Logarithmic Intervals are enabled the Length and Iterations table will be used to schedule
readings. See the following guidelines for the Length and Iterations entries.
Length - The units are seconds. The maximum interval length is 86,400 seconds or one set of
readings per day. The minimum interval length is 1 second. An entry of 0 is not allowed. The intervals
do not synchronize with real time.
Iterations - The repetitions of each interval length. The maximum is 99,999. Entering 0 will repeat the
interval length indefinitely.
Default Intervals and Iterations:
Interval Length Iterations Elapsed Time
1 30 20 10 minutes
2 60 40 50 minutes
3 120 25 100 minutes
4 300 80 500 minutes
5 600 50 1000 minutes
6 3600 24 2440 minutes
7 7200 48 5320 minutes
8 86400 0 Indefinite
Hint: When Logarithmic Intervals are selected for the Interval Type then the Elapsed Hours, Elapsed
Minutes and Elapsed Seconds storage locations will be utilized to display the elapsed time from the first
logarithmic interval.
Each Direct Connect channel can be customized using the options on this form. It is displayed by
pressing the Direct Connect button on the Program tab, or by selecting the corresponding Program
menu item.
Press to paste the channel configuration currently stored in the clipboard to the current
channel. Note: The Labels and Descriptions are NOT copied.
Press to display the Channel Configuration topic from the on-line help system.
Press to cancel the changes you have made to the channel configuration.
See the following topics for more information on the channel configuration form.
4.3.1 Channel
Use your mouse to select the channel to edit. The maximum number of channels available will be a
function of the Direct Connect Channels setting for the specified datalogger (usually 16) on when being
used to edit multiplexer channels the setting on the Configure Multiplexers form. The channel number
you have selected will display in the upper left of the Channel Configuration form on the channel
caption.
4.3.2 Identification
Configure the Label, or Name, for the channel, as well as the Description which provides additional
reference information for the channel.
The channel number caption will display which channel is selected using the Channel list.
Label - The channel Label is used to identify a particular channel. This label is used to identify Input
Storage usage (as displayed in the Monitor mode) and Final Storage usage when reducing data using
Roobrik or for import into the database. You may enter up to 24 alpha-numeric characters for each
Label.
Please note the following acceptable characters for use in your labels:
Lower case alphabet, a through z.
Upper case alphabet, A through Z.
Numeric, 0 through 9.
The underscore character, _.
The dollar sign, $.
Note: You will not be allowed to use any other characters, such as comma or spaces in your labels!
Description - The description field is used to provide additional information regarding the instrument
channel (or Input Channel). Up to 255 ASCII characters are allowed, all characters except the comma
are allowed.
4.3.3 Measurement
Configure the Gage Type | Make | Model to be used to make the measurement for the selected channel.
Gage Type - The Gage Type identifies the basic category of instrument that is connected to the
selected channel. The Gage Type | Make | Model selections are derived from the list of gage types
stored in the MultiLogger setup files. See section 8 for more information.
Hint: When using the Channel Configuration form to configure multiplexer channels there may be some
limitations on the selection of Gage Types. If the multiplexer Gage Type is set to MultiSensor or VWDSP
then you will be able to select all the gage types available. However, if the multiplexer Gage Type is
specified as a particular gage type, such as Vibrating Wire, then the only gage types that will be available
are None and the specified gage type, in this example, Vibrating Wire.
Make - Select the Make of the instrument connected to the channel. The Make list is derived from the
list of gage types stored in the MultiLogger setup files. See section 8 for more information.
Model - Select the model of the instrument connected to the channel. The Model is sub-category of
the Make. The Model list is derived from the list of gage types stored in the MultiLogger setup files.
Press to edit the instruction file for the specified instrument. See section 8 for more information.
Press to display additional information on the selected instrument.
Select Linear to use the Linear Coefficients for converting the instrument reading to engineering units.
When Linear is selected the Polynomial Coefficients box will be disabled.
Select Polynomial to use the Polynomial Coefficients for converting the instrument reading to
engineering units. When Polynomial is selected the Linear Coefficients box will be disabled.
When Linear is selected as the Conversion Method the Zero Reading, Gage Factor and Offset
entered will be used to convert the raw instrument reading to engineering units.
Where R represents the current instrument reading and CF represents the units conversion factor.
The Zero Reading and Gage Factor are normally included on a calibration certificate from the instrument
manufacturer. They can also be generated with a spreadsheet program by performing a linear regression
on the output units versus reading.
If the Input Units and Output Units feature is being used then the Gage Factor will be multiplied by the
appropriate factor to complete the conversion.
You may use scientific notation to enter values. For example, '1.234E-2' will represent '.01234'.
When Polynomial is selected as the Conversion Method the three coefficients entered as Coefficient
A, Coefficient B and Coefficient C will be used to convert the raw instrument reading to engineering
units.
Output A CF R 2 B CF R C CF
Where R represents the current instrument reading and CF represents the units conversion factor.
The coefficients are normally included on a calibration certificate from the instrument manufacturer. They
can also be generated with a spreadsheet program by performing a linear regression on the output units
versus reading and reading squared.
You may use scientific notation to enter values. For example, '8.91E-6' will represent '.00000891'.
The Units Type defines the category of engineering units conversions currently in use. For example,
Pressure, Load and Distance are the standard categories. Select None to disable (actually still applies
a factor of 1.0) the conversion of the gage reading as defined by the Input Units and Output Units.
After selecting the Units Type select an appropriate Input Units and Output Units setting. The Input
Units refers to the engineering units of the calibration factors that are being used, either the Linear
Coefficients or Polynomial Coefficients. The Output Units refers to the units that are desired. For
example, assume a pressure transducer was calibrated in psi but, being used to measure water level, it is
desired to output feet of water. As shown in the example above, select Pressure as the Units Type, psi
as the Input Units and Feet H20 as the Output Units.
Note: Additional engineering Units Types, Input Units and Output Units can be added by editing the
MultiLogger setup file. See section 8 for more information.
Apply - Check Apply to enable the temperature correction for the particular channel.
Note: The Temperature Correction options will be disabled unless Upper Channel is configured.
Initial Temp – Enter the initial temperature to be used for the correction, units must match the output
of the Upper Channel temperature measurement.
Temp Factor – Enter the linear correction factor to be used for the correction. The units must match
the output of the selected Conversion Method.
Hint: If using the Units Conversion the output of the temperature correction will be adjusted accordingly.
The Processing File drop-down allows for inclusion of additional processing or programming for the
selected channel. Select None to disable the inclusion of additional programming for the channel. The list
of available Processing Files is derived from the multilogger.ini setup file.
Press to load the selected Processing File into the MultiLogger editor.
Values may be selected from the Available Properties grid on the right by left double-clicking the row
with the value to be used, or entered manually by clicking in the Value cell in the File Properties grid.
Note: Please consult MultiLogger Application Note #16, available in the Support area of our
website at www.canarysystems.com for more information on this topic including the creating of
new Processing File options and the format of the files.
Type - The drop down list is used to select an alarm checking procedure for the selected channel. To
disable alarm checking select None as the type. Common alarm types and their function include:
Low and High - This alarm type is designed to indicate alarm if the measurement falls outside
the range specified by Alarm Low and Alarm High.
Rate of Change - This alarm type is designed to indicate alarm if the change in measurement
falls outside the range specified by the Alarm Low and Alarm High.
Rate of Change/High Level - This alarm type is designed to indicate alarm if the absolute
change in measurement falls outside the value specified by Alarm Low and the value exceeds
Alarm High.
Two Level Alarm - This alarm type is designed to indicate alarm if the measurement value
exceeds either Alarm Low or Alarm High. If the measurement exceeds the Alarm Low value
then a low level alarm is activated, if it exceeds Alarm High then a high level alarm is activated.
Note: Alarm Low and Alarm High values are also used to configure the display of the alarm status
when using the Text Monitor. The cells that show measurements that exceed the Alarm Low value
(function depends on the alarm type configured) will display in yellow, cells that show
measurements that exceed the Alarm High value (function depends on the alarm type configured)
will display in red.
Contact Canary Systems regarding information on other types listed. Numerous support documents are
available at www.canarysystems.com regarding other options.
Alarm Low – Enter the low value to be used for the configured alarm type. The function of Alarm Low
will depend on the alarm type configured.
Alarm High – Enter the low value to be used for the configured alarm type. The function of Alarm
Low will depend on the alarm type configured.
Hint: Alarm Low and Alarm High will be disabled if None is selected as the alarm type.
Press to edit the instruction file for the selected alarm type.
4.3.11 Channel B
Certain controllers such as the Campbell CR800 and Campbell CR1000 support a secondary
measurement, or Channel B, for each channel, whether a Direct Connect channel or Multiplexer channel.
Click Channel B to display the Channel B configuration.
Hint: The Channel B tab will not display for controllers that don’t support it and it will not display if the
Configure Multiplexer | Wires setting is less than 4.
Select the Upper Channel tab on the Channel Configuration form to display the Upper Channel
configuration options.
Hint: The Upper Channel will be disabled unless Channel A Measurement is configured. It may also be
disabled for certain multiplexer types, for example 2-wire multiplexers.
Typically the Upper Channel selection is used for temperature devices that are connected or associated
with the measurement configured on the Channel A or Channel B tabs.
Hint: Configuration of an Upper Channel device is required to use the Channel A or Channel B
Temperature Correction functions.
Configure the Label, or Name, for the channel, as well as the Description which provides additional
reference information for the channel.
The channel number caption will display which channel is selected using the Channel list.
Label - The channel Label is used to identify a particular channel. This label is used to identify Input
Storage usage (as displayed in the Monitor mode) and Final Storage usage when reducing data using
Roobrik or for import into the database. You may enter up to 24 alpha-numeric characters for each
Label.
Please note the following acceptable characters for use in your labels:
Lower case alphabet, a through z.
Upper case alphabet, A through Z.
Numeric, 0 through 9.
The underscore character, _.
The dollar sign, $.
Hint: You will not be allowed to use any other characters, such as comma or spaces in your labels!
Description - The description field is used to provide additional information regarding the instrument
channel (or Input Channel). Up to 255 ASCII characters are allowed, all characters except the comma
are allowed.
Device – Select the measurement device from the drop-down list. Devices can be added to this list
by editing the MultiLogger setup file.
Press to edit the instruction file for the specified Upper Channel device..
Units – Select the appropriate units from the drop-down list. The units available are derived from the
units.ini file which can be edited using MLSetup.
Hint: The Units configuration does not apply a mathematical conversion to the measurement, it is for
display purposes only.
Press to display the Configure Multiplexers topic from the on-line help system.
Press to cancel the changes you have made to the multiplexer configuration.
Hint: You will not be able to access other MultiLogger forms and/or functions until you close this form.
See the following topics for more information on the form selections.
Hint: When using the VWDSP Interface the Multiplexer Gage Type must be set to VWDSP.
Press to edit the individual channels of the multiplexer. You must select a multiplexer
Model and Gage Type to be allowed access to the Channel Configuration form. See
section 5.3 for more information on the Channel Configuration form.
Hint: The maximum number of multiplexer channels allowed for array based loggers is 256, for table
based loggers it is 320. You will not be able to program your system if the number of channels exceeds
these values.
Hint: When using a Wires selection of 2 the Channel Configuration Upper Channel Device selections will
be disabled. You must use a Wires selection of 4 or higher for the Upper Channel Devices to be enabled.
Select the digital I/O port of the datalogger that will be used to enable the
multiplexer. Note that certain ports may be selected that are not actually available
depending on the model of datalogger. In this case the selection will revert to a working port.
Hint: Multiplexers from certain manufacturers support “daisy-chaining” where a single control port is used
to activate a series of multiplexers that share this control port. To activate this feature in MultiLogger be
sure to specify the same Enable port for each multiplexer that will be sharing this port.
Select the digital I/O port of the datalogger that will be used to clock, or advance the
channels, of the respective multiplexer. Note that certain ports may be selected that
are not actually available depending on the model of datalogger. In this case the selection will revert to a
working port.
Hint: If the Multiplexer Gage Type is set to VWDSP this setting is ignored.
Label - You may enter up to 24 alpha-numeric characters to identify each location. See section 4.3.2
for guidelines regarding proper label format. See the on-line help for more information on adding and
deleting locations using the Label field.
Alias - You may enter up to 24 alpha-numeric characters as an alias, or alternate name, for the
corresponding location.
Description - You may enter up to 255 alpha-numeric characters to identify each location. See
section 5.3.3 for more information on the format of this field.
Units - You may select from the drop-down list a Units identifier to describe the Units of the
measurement. Note: This does not apply any conversion to the data values, it is simply a field
reference. The list of available units can be modified – see section 7.2 for more information on the
Multilogger setup files.
Reserved – Some Input Storage locations have keywords assigned to them that instruction files or
MultiLogger itself may use to identify the location. These keywords are assigned in the MultiLogger
setup file. You cannot change these keywords using this form, you must edit the MultiLogger setup
file directly. Note: For CRBasic programmed dataloggers such as the Campbell CR2xx,
CR800/850 and CR1000 you cannot change the Label for Reserved keywords. In these cases
you can modify the Alias to display and use an alternate Label for the location.
Check Alarms - Alarm checking can be enabled for a particular Input Storage location by selecting
the Type. Enter the Low Limit and High Limit values which may be used for the alarm checking. If
the Database System is installed this information will be used to control the alarm functionality of the
database client tools.
This form displays information about the program that has been generated for the datalogger including
the number of instructions, size of program in bytes, Final Storage locations used, data overwrite in
hours, Input Storage assignments and Final Storage assignments.
Press to display the Datalogger Program Information topic from the on-line help system.
The Program Instructions caption indicates the total number of instructions that
are used in the datalogger program. It is not a very useful piece of information. See
Program Bytes for a more useful number.
The Program Bytes caption indicates how many bytes the current datalogger program
requires of program storage memory. This is particularly an issue with older control
modules that only have 1986 bytes of program memory.
MultiLogger will attempt to approximate how long the datalogger can store data
before overwriting of the oldest data occurs. You must have run the Status
operation while in the Monitor mode for this calculation to work. The Status
operation interrogates the control module and returns the amount of available data
memory. Press the button on the Text Monitor tab to run the Status operation.
Hint: The value shown may be inaccurate depending on specific Program settings. For example, if Single
Interval is configured for 1 Hour, but Output Data is configured for Once Per Day, the calculation result
will be based on the 1 Hour interval, NOT the daily data storage.
If the Status operation has not been run for this control module the Overwrite in Hours will display 0.
There may also be other circumstances which produce 0, for example using Special Read Times as the
Interval Type but then not enabling any of the times.
Hint: If the result > 24 hours the caption will change to Overwrite in Days and the result will be re-
calculated to show overwrite in days.
Select Configure | Text Monitor from the pull-down menu to select locations for the Text Monitor. You
may also left double-click a location label in the Text Monitor to display the select locations form.
The Available Locations list details the Input Storage locations that are available for monitoring. The
Selected Locations list details the locations that are currently selected.
Press to move locations from the Available Locations list to the Selected Locations list.
Press to display the help topic for the locations form from the on-line help system.
Press to accept the changes made to the Selected Locations list and close the form.
Press to cancel changes made to the Selected Locations list and close the form.
Hint: While the Text Monitor is running you may press the D key to change the number of digits shown to
the right of the decimal point. This setting will be saved in the configuration file for later retrieval.
Datalogger flags are software flags accessible to the program running in the
datalogger. They are usually used for range checking or other Boolean type
operations. Two of the flags, flags 7 and 8 are generally used for the alarm routines,
the rest are available for your program. Flag 7 disables the alarm function, high
indicates alarms are disabled, low indicates alarms are enabled. Flag 8 indicates the
current state of the alarms, high indicates an active alarm, low indicates not active.
In the low state the flag button is colored green, in the high state, red.
To toggle the state of a flag simply left click the respective button while the monitor
mode is active. Only click once, it usually takes a second or two to actually toggle the
flag.
Datalogger ports are the digital I/O ports of the datalogger. They are usually used for
enabling and clocking multiplexers but are also used for power control, SDM devices,
the MultiSensor Interface or SDI sensors.
In the low state the port button is colored green, in the high state, red.
To toggle the state of a port left click the respective button while the monitor mode is
active. Only click once, it usually takes a second or two to actually toggle the port.
Hint: Depending on the port configuration there may be times when the ports do not toggle.
The two clock displays indicate the computer time (updated once per second) and datalogger time
(updated when the last set of monitor locations were processed). The clocks, assuming the datalogger
clock has been updated, should agree within 2 or 3 seconds.
Press to match the datalogger clock to the computer clock. It usually takes 2-3 seconds for the
operation to complete. This button will be disabled unless the Monitor Mode is Active.
Press to reset the various error counters that the control module records. The reset process usually
takes 2 to 3 seconds after which the monitor mode will resume. This button will be disabled unless
the Monitor Mode is Active.
Press to cancel the monitor mode that is currently active and close the port that is open. If the
connection was made using a phone modem the modem will be hung up. This button will be
disabled unless the Monitor Mode is Active.
Press to interrogate various system settings and status indicators of the datalogger. If the status
check completes successfully then the Datalogger Status form will display. This button will be
disabled unless the Monitor Mode is Active.
Note: Some of the indicators do not display for the older control modules such as the CR10. Also for
newer dataloggers such as the CR2xx, CR800/850 or CR1000 the Status table will be retrieved. See the
respective Operators Manual for details regarding the Status table listing for these units.
Press to enable the Excel DDE link. When data are captured they will be sent via DDE to Excel.
Indicates that the Excel DDE link is enabled. Press to disable the DDE link.
The text of the button indicates the status of the monitor data capturing. Monitor data capturing is useful
as a backup means of data collection. See section 5.7 for more information on the data capture facility.
Indicates that monitor data capturing is on (default). Click to toggle capture OFF.
Indicates that monitor data capturing is off. Click to toggle capture ON.
Select this option to automatically select locations for the Text Monitor based on locations that are
actually stored by the program. This is a very useful option to help manage the display of the Text
Monitor as changes are made to the channel configuration.
The display at right illustrates the monitor labels and corresponding values.
All monitor labels are prefixed by the Input Storage number. The Input
Storage number and corresponding label are derived from a combination of
three sources, the MultiLogger setup file, the user defined labels associated
with the Direct Connect Instrument Configuration and the labels entered
for Multiplexer Channel Configuration.
The list of Input Storage numbers and corresponding labels can be displayed
on the Program Information form generated by pressing the Info button on
the MultiLogger toolbar.
The caption illustrates the first 10 Input Storage locations, their corresponding Input Location numbers,
labels and monitor values. To change the number of digits shown press the D key.
The list of locations can be configured by selecting Configure | Text Monitor from the pull down menu or
left clicking the location label.
If a monitor value exceeds alarm settings the value will display in red.
Monitor values being monitored in the Test mode will display in yellow.
Press Help to display the Enter Input Storage Value topic from the on-line help system.
Hint: When the Test mode is Active, left clicking the location values will select that location for monitoring.
This only applies to instruments connected to multiplexers. For other locations left clicking the value will
have no effect.
The real-time monitor charts are configured by selecting Configure | Graphical Monitor from the pull-
down menu. Up to 4 charts may be activated for the graphical monitor.
Press to display the Configure Graphical Monitor topic from the on-line help system.
Press to accept the changes you have made and close the form.
Press to cancel the changes you have made and close the form.
Select the type of chart that will display. Generally Lines is used, select None to disable the chart.
5.3.2 X Data
Select the data that will be used for the X axis. The available data includes the sequence number, or the
number of data points plotted in the current session, and all the Input Storage values of the datalogger.
5.3.3 X as Label
This option configures the format of the X data supplied to the graphical monitor for the selected chart. If
checked then the X data is considered a label, and hence spacing will be equal along the bottom axis of
the chart, if unchecked then the X data will be considered a value and plotted.
For example, if the Time(HHMM) is selected as the X Data then you will want to check X as Label.
5.3.4 Y1 Locations
Press to select locations for the Y1 axis (left-side) of the chart. The locations form will display. See section
5.1 for an explanation of how the Locations form works.
5.3.5 Y2 Locations
Press to select locations for the Y2 axis (right-side) of the chart. The locations form will display. See
section 5.1 for an explanation of how the Locations form works.
The Graphical Monitor displays the charts that have been enabled using the Configure Graphical
Monitor form. Up to 4 charts may be displayed. They are automatically sized to fit the viewable area of
the form.
The charts may be printed by clicking the printer icon at the top of the chart.
The toolbar at the top of the chart provides access to the functions of the charting tool, in addition to
allowing customization of many of the charting options.
The following section will provide brief explanations for the button functions and chart functionality.
Allows zooming
in on select portions
of the chart or
scrolling the chart. To
zoom in on a section
of the chart hold the
left mouse button and
drag down to the
lower right. You will
see a box outline
display over the chart.
When the left mouse
button is released the
boxed section will be
expanded to fill the
chart area. To revert
back to the original
size simply hold the
left mouse button and
drag to the upper left,
you will again see a
boxed section display, release the left mouse button to revert back to the original size. To scroll hold the
right mouse button and drag left-right or up-down. Dragging left-right will scroll the X-axis, dragging up-
down will scroll the Y-axis. Release the button to hold the scroll position (the MultiLogger popup menu will
display when releasing the right mouse button, simply left mouse button click on the chart to hide the
popup menu).
Click to activate
the Rotate function.
Hold the left mouse
button and drag left-
right to rotate in the
left to right plane,
drag up-down to
rotate in the up and
down plane. The
degree of rotation for
each orientation is
shown on the status
line to the right of the
toolbar, as shown.
Activates the
Move function. Hold
the left mouse button
and drag left-right or
up-down to move the
chart. Offset values will
display to indicate in
pixels how far the chart
has been moved, as
shown.
Activates Zoom,
to scale the size of the
chart. Hold the left
mouse button and drag
up-down to decrease
the size of the chart.
Drag down-up to
increase the size of the
chart. Drag left-right or
right-left to decrease
the size of the chart.
The Zoom factor will
show on the status
line.
Adjust 3-D
depth. Hold the left
mouse button and
drag left-right to
increase the depth,
drag right-left to
decrease the depth.
The 3-D depth will be
shown in the status
line, as shown.
Copy the
current chart image
as a bitmap to the
Windows clipboard.
This image may then
be pasted into other
Windows applications
using the Paste
button. Only the
image is copied,
example shown at
right.
Save the current chart image in one of 4 formats, Teechart Pro (template file, extension .tee),
Enhanced Metafile (graphic format, extension .emf), Metafile (graphic format, extension .wmf) or Bitmap
(graphic format, extension .bmp).
Hint: A viewing/editing tool called TeeOffice is available for download from our website to load the .tee
format files for customization, export or printing.
When the Monitor mode is active the values that are being
monitored may be automatically saved to a data file. This is
useful where backup of test data is desirable or when a
specific sequence of data capture is required. You still have
the option of collecting data the ―traditional‖ way (by
pressing the Collect button) and processing the test results
using this data. The Configure Capture Intervals form
configures how the data capture functions. The button on
the Text Monitor tab indicates the status of the data capture
function. By default data capture is enabled.
The name of the data file that will be used to store the monitor capture data is indicated in the edit box.
Press to select a different data file. If you want to save the data to a new file press , type the name of
the file and then press OK.
Hint: The default file name is always the nodename followed by “_capture.dat”. The default path is the
[Shared Docs]\MultiLogger path. You cannot save the capture data file to an alternate path.
The Data Capture file format is as follows (with Include Date/Time Information checked):
ID,Year,JulianDay,Time,Seconds,DecimalDay,ValueN,ValueN+1
ValueN refers to the first Input Storage location value that is being monitored. ValueN+1 refers to the
second Input Storage location value that is being monitored. The sequence of <comma>Value would
continue for all of the Text Monitor locations. In addition a label file (extension .txt) using the root name of
the capture data file name (ie for the file ―MyCR800_capture.dat‖ the label file is ―MyCR800_capture.txt‖)
is created for the current monitoring session. The capture data file can be loaded into Roobrik and the
label file will identify the array positions of the data.
The Data Capture file format is as follows (with Include Date/Time Information NOT checked):
ID,ValueN,ValueN+1
ValueN refers to the first Input Storage location value that is being monitored. ValueN+1 refers to the
second Input Storage location value that is being monitored. The sequence of <comma>Value would
continue for all of the Text Monitor locations.
You have the option of storing computer generated date and time information along with the monitor
values. Generally, if you are monitoring locations 1-8 (by default these locations are included in the
monitor set) you will have date and time information that the datalogger records when the readings are
taken. Including the computer generated date and time information is useful to verify the operation of the
capture intervals when using the Capture Data using Intervals option.
Check Capture Data on Change to ignore the Capture Intervals and only store data in the monitor data
capture file when the data changes. This is often preferable to using the Capture Intervals because
duplication of data is avoided.
Select Capture Data using Intervals to schedule the capturing using the Length and Iterations list.
The Length may be specified between 0 and 99,999 seconds. If the length is specified as 0 then the
capture of monitor data stops with this interval.
The Iterations may be specified between 0 and 99,999. This setting indicates how many times the
interval length is repeated. If the Iterations is set to 0 then the interval is repeated indefinitely.
For example, the Configure Capture Intervals screen capture will capture the monitor data every 30
seconds for as long as the monitor data capture is enabled.
The terminal emulator is enabled by left mouse button clicking in the terminal window. Press <ENTER> a
few times to get the attention of the connected datalogger. Responses will vary depending on the type of
datalogger, see the respective datalogger documentation for information on the terminal mode
commands.
See your control module Operator‘s Manual for a list of datalogger commands.
Select to change the font type and size used for the terminal emulator. Depending on the resolution and
font size settings of your display setup it may be necessary to adjust the size of the font for better viewing.
The changes you make to the font type and size are saved in the MultiLogger setup file.
Press to cancel the changes you have made and close the form.
MultiLogger can be used to send messages via e-mail to alert others of alarm situations or to relay data
that can then be imported into spreadsheets or databases.
This form allows you to configure how the Notification System will function. You must also set the
appropriate options in the Configure Mail Messaging form.
These settings determine if the Notification System is operational and how it will function. These settings
are stored in your station file.
Disable Notification System - The Notification System will be inactive. The Message Server may
still be running but MultiLogger will not generate messages for the server.
After Collecting Data - After each data collection MultiLogger will process the data and create
messages based on the Message Format and Data Arrays Format selections. The data collection
may be initiated by pressing the Collect button on the toolbar or by using the Collection Agent.
Monitor Mode Capture Data - This enables the Notification System to process Monitor mode data
and create messages based on the Message Format and Data Arrays Format selections. Note: Data
are selected for possible message creation based on the Capture Intervals configuration. In other
words, messages are only created when a data capture event occurs.
These options configure the basic data handling procedures when the Notification System is enabled.
Always Send All Data - This option will always send all the data available for the message.
Send All Data Only if Alarm - This option will only send all the data if there is an alarm in one or
more arrays of data. Note: When using the Monitor Mode Capture Data option as the Notification
Method there is only 1 array available each time a capture data event occurs.
Send Only Alarm Arrays - This option will only send the arrays of data that contain a value that
exceed an alarm limit. Other arrays will be discarded. Note: When using the Monitor Mode Capture
Data option as the Notification Method there is only 1 array available each time a capture data event
occurs.
No Data No Message - If it is found that no arrays of data meet the above criteria for creating
messages then no message is sent.
These options configure the format of the arrays that satisfy the Message Format options.
Send All Elements – All elements in the selected arrays are selected.
Send Selected Elements – Specific elements may be selected from the selected arrays by selecting
this option. Press the button to display and configure the selected locations list. If the Notification
Method is set to Wait – Then Collect Data or After Collecting Data then the list displayed will be the
Final Storage elements. If the Notification Method is set to Monitor Mode Capture Data then the list
displayed will be the Input Storage elements that are currently selected for the Text Monitor.
Include Element Labels – Check to include the labels for the elements that are selected.
The Notify Actions determine who to send messages to. Up to 10 mail messages may be sent for each
message that is successfully created.
E-Mail? - Click on the cells below to toggle between Yes and No to enable or disable respectively the
corresponding message number.
To - Specify the address of the recipient. Format is user@domain. If the the address is incorrect the
message will be deleted (and a note made in the Message Server log).
The Configure Preferences form is designed to allow customization of various display and function
parameters.
The settings configured using this form are stored in the multilogger.ini setup file for use by all nodes and
configuration files.
5.10.1 General
Hint: If an animation file is selected outside the [Shared Docs]\MultiLogger folder a prompt will display to
copy the file to the [Shared Docs]\MultiLogger folder.
Show Logger Toolbar - The Logger Toolbar may be hidden by unchecking this box. This may be
done to provide more room for the Text or Graphical Monitor, usually in cases where the display is of
limited resolution. By default the Toolbar is shown.
Show Network Toolbar - The Network Toolbar may be hidden by unchecking this box. This may be
done to provide more room for display of the Network Configuration, usually in cases where the
display is of limited resolution. By default the Network Toolbar is shown.
Stop Logger Communication on Failure - While the Text Monitor is Active retries will be attempted
should the connection fail. Check this box to disable automatic retries.
These settings configure various options associated with the Text Monitor:
Normal Background - Click on the panel to display the Windows color dialog, to allow selecting a
different color for the cells showing normal range values.
Normal Text - Click on the panel to display the Windows color dialog, to allow selecting a different
color for the text of normal range values.
Alarm Low Background - Click on the panel to display the Windows color dialog, to allow selecting a
different color for the cells showing Alarm Low values.
Low Font - Click on the panel to display the Windows color dialog, to allow selecting a different color
for the text of Alarm Low values.
Alarm High Background - Click on the panel to display the Windows color dialog, to allow selecting
a different color for the cells showing Alarm High values.
Alarm High Font - Click on the panel to display the Windows color dialog, to allow selecting a
different color for the text of Alarm High values.
These settings configure various options associated with the Graphical Monitor:
4. The Logger form Program tab includes additional buttons for accessing the forms specific to
these controllers.
The Final Storage Array Format options configure the format of the stored Final Storage data.
Optimize Memory
Check to optimize the number of Final Storage locations used by the program that MultiLogger
will generate for the datalogger.
This option only applies to locations used by the multiplexers. Normally, 32 Final Storage
locations are allocated for each multiplexer that is enabled (by specifying a Model and Gage
Type on the Configure Multiplexers form). When Optimize Memory is checked only locations
that are being used by active channels are stored. This can, depending on the configuration of
the multiplexers, result in significant memory savings. However, be aware that this may cause
difficulties when reducing data because the position of data points will change in the array if
channels are enabled or disabled using the Channel Configuration form. As such, unless the
channel configuration is fixed, it is recommended that Optimize Memory be left unchecked.
To find out how many Final Storage memory locations are being used by the current program
configuration press the Info button on the MultiLogger toolbar.
The number of locations that can be stored depends on the memory size of the control module.
Use the Datalogger Status function (the button on the Monitor tab) while monitoring to check
the exact number of locations available. The Info displays the overwrite time in hours or days.
Generally you will want to leave the default setting of storing data at high resolution. High
resolution stores data in a 5 digit format, maximum range ±99999. Low resolution (unchecked)
stores data in a 4 digit format, maximum range ±6999. High resolution uses 4 bytes of memory
for every data point, low resolution uses 2.
User Locations are defined as Input Storage locations in the range of 11 to 62. You have the
option of storing these values in these locations at the end of the multiplexer locations in your
Final Storage array instead of before.
This feature is primarily included to maintain compatibility with the Geokon MICRO-10 program
generation software which stored user locations after the multiplexer locations.
It may be desirable to check Position User Locations at End of FS Array anyway because
User Locations are more likely to be selected for storage at a later date and if they are added
after the multiplexer locations it will result in less confusion regarding Final Storage array
positions when reducing the data.
When using a tipping bucket rain or similar pulse accumulation type instrument you will need to
check the respective box which refers to where the instrument is connected.
Accumulate P1 Pulses
Accumulate P2 Pulses
The Memory Allocation group configures the memory settings for the control module.
Input storage refers to the memory of the control module used to store readings temporarily
before sending to Final Storage. These locations are displayed in the Monitor mode.
Intermediate storage refers to the memory of the control module that is used for temporary
storage of readings during various processing operations. These locations are not accessible for
monitoring or data collection.
Two Final Storage areas can be allocated in the control module. A second storage area can be
used for example to store data sampled at a different scan interval. The default allocation is 0.
The Output Labels group configures storage of the Input Storage labels to the download file.
Check Output Labels to DLD to store the labels in the Download File. The default is to store the
labels.
If the program will be edited by MLEditor then the labels should be output, otherwise the
checkbox can be left blank.
Hint: Program download takes less time when this option is disabled (the default selection).
See the respective Control Module Operator's Manual for more information on the program
tables.
The Control Module has 3 areas of memory for program instructions. Tables 1 and 2 are used to
store programs that can run concurrently while Table 3 stores subroutines that may be called
from either Table 1 or 2. By default MultiLogger uses only Table 1 to store instructions that control
the intervals by which measurements are taken. MultiLogger also uses Table 3 to store all the
subroutines that actually acquire measurements and perform other tasks such as storing data.
Check the section [Subroutine Assignments] in the multilogger setup file for a list of subroutine
assignments used by MultiLogger.
You may override the default instructions generated by MultiLogger for Tables 1 and 2 (normally
empty) by checking the respective checkbox and using the file open dialog to select an instruction
file.
You may add subroutines to Table 3 by checking the respective checkbox and using the file open
dialog to select an instruction file (that contains subroutines).
Use MLEditor to create/modify the instruction files that are specified for Tables 1, 2 or 3.
See the respective Control Module Operator's Manual for more information on the program
tables.
7. The Clocks on the Text Monitor will only show the time,
no date will be shown.
8. Control port selection for CR500/CR510 Multiplexer Enable is constrained to C1 and C2.
9. Control port selection for CR500/CR510 Multiplexer Clock is constrained to C1, C2 and E1 and
E2.
11. The folder [Shared Docs]\MLGateway\Lib\ins contains the multilogger.ini setup file and related
instruction files.
The Campbell CR2xx is limited in its programming and data storage capability.
1. Programming of the CR2xx is in the CRBasic programming language, the Download File and
instruction file extension is .cr2.
2. The maximum number of multiplexer channels is 32, this can be configured as (2) 16-channel
multiplexers or (1) 32-channel multiplexer.
8. Control port selection for Multiplexer Clock is constrained to C1, C2 and E1 and E2.
10. The folder [Shared Docs]\MLGateway\Lib\CR2xx contains the multilogger.ini setup file and
related programming files.
The Campbell CR800 and CR1000 provide extensive programming and control capabilities.
1. Programming of the CR800 and CR1000 is in the CRBasic programming language, the Download
File and instruction file extensions are .cr8 and .cr1, respectively.
2. There is no limit on the number of multiplexer channels, beyond the limit on the number and
configuration of multiplexers themselves.
3. The maximum number of memory locations shown in the Text Monitor defaults to 1000.
5. Control port selection for Multiplexer Clock when using the CR800 is constrained to C1-C4 and
E1 and E2.
6. Control port selection for Multiplexer Clock when using the CR800 is constrained to C1-C4 and
E1 and E2.
7. When using the CR800, the Text Monitor will disable the display and status updates for the
unsupported control ports C5-C8.
8. For the Campbell CR800, the folder [Shared Docs]\MLGateway\Lib\CR800 contains the
multilogger.ini setup file and related programming files.
9. For the Campbell CR1000, the folder [Shared Docs]\MLGateway\Lib\CR1000 contains the
multilogger.ini setup file and related programming files.
10. Collection from multiple data tables is supported. MLGateway automatically appends the table
name following the node configuration file name. For example, if the node configuration file is
MyCR800 and FSDATA_AVG has been defined then the collected data will be stored in the
MyCR800_FSDATA_AVG.dat file.
The Logware software that supports the Sisgeo ADR-2VWT single-channel vibrating wire datalogger is
included in MultiLogger.
See the Logware User‘s Guide for complete information on the Logware form.
6.5 Kinemetrics K2
The Network Manager will display, left slow click the node to rename it.
Press Save when finished. The Network Configuration will re-display with the K2 node updated with
default path, an example is shown on the following page.
Note that several Connection Settings options will be disabled – these settings don‘t apply to the K2
nodes. When connecting a K2 to a COM port you will see a Baud Rate drop-down (as shown), when
connecting a K2 to a Phone Modem you will see a Dialed Using Phone Number edit and when
connecting a K2 to a Socket you will see a Port edit. Enter Extra Response Time as needed to support
any anticipated communication delays for the selected communication port.
The K2 node is not configured using MultiLogger, software from Kinemetrics provides that functionality
(although the Terminal window does provide a command line interface to configuring the K2 – see the
following sections), however several configuration items are stored in the MultiLogger configuration file
(extension .cfg) associated with the K2 node.
These include:
In addition the configuration file stores the results of the last Status command – the contents of the
configuration file can be reviewed for trigger status, memory status and other device settings. Please
consult the K2 User Documentation for more information on the Status command.
After pressing Save the Network Manager will update, however the configuration file doesn‘t exist yet.
Left double-click logger node to invoke the Logger form and create the Configuration File. The Logger
form for the K2 consists of a menu and tabbed control for Project settings and a Terminal emulator.
Project Settings – Configure the various configuration file and path settings for the K2 node. See the
previous explanation regarding the various edits.
The Last Folder drop-down will actually display a date picker to be used to populate the Last Folder edit.
Event files are organized by date and time in the K2 memory, the Last Folder edit will select the starting
date for .evt collection. Generally you will only need to collect files from the current date forward but this
will depend on the importance of collecting the historical event files.
After successfully collecting event files the Last Data Collection and Last Battery Voltage fields (read
only fields) will update.
Hint: The Datalogger ID is normally a read-only field in the Network Configuration however for K2 nodes it
is editable.
Click on the Terminal tab to display the terminal window (font may be configured using the Configure |
Terminal Font menu item) to activate the window, this includes opening the port and dialing/connecting
using the Network Configuration settings if needed. After connecting you will see the * prompt indicating
connection to the K2. If the * prompt does not display then try typing \ to force entry into monitor mode.
Hint: The K2 must be configured for Tree File System to function properly with MultiLogger. Also – Be
sure to delete file folders as they are created by the K2 to keep the display within a single page otherwise
MultiLogger will not be able to read the folder list and retrieve new event files.
Consult the Altus Monitor Mode Communications (302219) document available from
www.kinemetrics.com for a complete listing of the Terminal mode commands.
The Network Manager will display, left slow click the node to rename it.
Press Save when finished. The Network Configuration will re-display the RefTek node updated with
default path, ans example is shown on the following page.
Note that several Connection Settings options will be disabled – these settings don‘t apply to the RefTek
nodes. When connecting a RefTek to a COM port you will see a Baud Rate drop-down, when connecting
a RefTek to a Phone Modem you will see a Dialed Using Phone Number edit and when connecting a
RefTek to a Socket you will see Port edit (as shown). Enter Extra Response Time as needed to support
any anticipated communication delays for the selected communication port.
The RefTek node is not configured using MultiLogger, software from RefTek provides that functionality
(although the Terminal window does provide a command line interface to configure the RefTek – see the
following sections), however several configuration items are store in the MultiLogger configuration file
(extension .cfg) associated with the RefTek node.
These include:
After pressing Save the Network Manager will update, however the configuration file doesn‘t exist yet.
Left double-click the logger node to invoke the Logger form and create the Configuration File. The
Logger form for the RefTek consists of a menu and tabbed control for Project setting and a Terminal
emulator.
Project Settings – Configure the various configuration file and path settings for the RefTek node. See
the previous explanation regarding the various edits.
The Last Folder drop-down will actually display a date picker to be used to populate the Last Folder edit.
Event files are organized by date and time in the RefTek memory, the Last Folder edit will select the
starting date for .evt collection. Generally you will only need to collect files from the current date forward
but this will depend on the importance of collecting the historical event files.
After successfully collecting event files the Last Data Collection and Last Battery Voltage fields (read
only fields) will update.
Hint: The Datalogger ID is normally a read-only field in the Network Configuration however for RefTek
nodes it is editable.
Click on the Terminal tab to display the terminal window (font may be configured using the Configure |
Terminal Font menu item) to activate the window, this includes opening the port and
initializing/connecting using the Network Configuration setting if needed. After connecting you will be able
to type commands to send to the RefTek. Initially there will not be a prompt character. All commands to
the RefTek start with the ‗{‗ character and include two letters for the command and the ID of the unit.
Note, since you are connected directly to a single RefTek unit, you may use a ID value of 0.
An example session is shown below. This session displays a list of the event files currently stored on the
recorder‘s harddrive using the file maintenance command: ‗{FM,0,ev‘
Refer to the 130 Cmd Line Reference document available from www.reftek.com for a complete listing for
the Terminal mode commands and responses.
The Network Manager will display, left slow click the node to rename it.
Press Save when finished. The Network Configuration will re-display the MR2002 node updated with
default path, an example is shown on the following page.
Note that several Connection Settings options will be disabled – these settings don‘t apply to the MR2002
nodes. When connecting a MR2002 to a COM port you will see a Baud Rate drop-down, when
connecting a MR2002 to a Phone Modem you will see a Dialed Using Phone Number edit and when
connecting a MR2002 to a Socket you will see Port edit (as shown). Enter Extra Response Time as
needed to support any anticipated communication delays for the selected communication port. Enter the
Password (Default is SWISS) to be used to authenticate the connection.
The MR2002 node is not generally configured using MultiLogger, the WINCOM software from SYSCOM
provides that functionality (although the Terminal window does provide a command line interface to
configure the MR2002 – see the following sections), however several configuration items are store in the
MultiLogger configuration file (extension .cfg) associated with the MR2002 node.
These include:
Description – Used to provide a more verbose description for the unit.
Datalogger ID – The project under which the collected .xmr files will be imported. This is usually
configured as a 3 digit numeric value.
Last Updated – The date and time when the node was added to the network.
Last Data Collection – The date and time of the last collection attempt.
Last Battery Voltage – The battery voltage returned during the last data collection attempt.
After pressing Save the Network Manager will update, however the configuration file doesn‘t exist yet.
Left double-click the logger node to invoke the Logger form and create the Configuration File. The
Logger form for the MR2002 consists of a menu and tabbed control for Project setting and a Terminal
emulator.
Project Settings – Configure the various configuration file and path settings for the MR2002 node. See
the previous explanation regarding the various edits.
The Last Folder drop-down will display a date picker to be used to populate the Last Folder edit. Event
files are organized by date and time in the MR2002 memory, the Last Folder edit will select the starting
date for .xmr collection. Generally you will only need to collect files from the current date forward but this
will depend on the importance of collecting the historical event files.
After successfully collecting event files the Last Data Collection and Last Battery Voltage fields (read
only fields) will update.
Hint: The Datalogger ID is normally a read-only field in the Network Configuration however for MR2002
nodes it is editable.
Click on the Terminal tab to display the terminal window (font may be configured using the Configure |
Terminal Font menu item) to activate the window, this includes opening the port and
initializing/connecting using the Network Configuration settings (e.g. Com, Phone Modem, Socket), and
sending the login and configured Password. After connecting and logging in you will be able to type
commands to send to the MR2002. Initially there will be a ? prompt character. All commands to the
MR2002 start with the left parenthesis ‗(‗ character, followed by the command, then ‗++‘ then a right
parenthesis ‗)‘.
Note that no <ENTER> is required to terminate commands, as soon as the right parenthesis is received
the MR2002 will execute the command. Successful execution returns the command response (default is
‗*‘) and then an echo of the command.
Command Description
(BP++) Return primary battery voltage
(BB++) Return backup battery voltage
(MfSWISS++) Erase all events in SRAM memory (change default password as needed)
(MqSWISS++) Erase all events in Memory Card (change default password as needed)
(AsSWISS++) Reset Alarm Status (change default password as needed)
(SbSWISS++) Reboot system (change default password as needed)
(LiSWISS++) Login with default password ‗SWISS‘
(LpNEWPW++) Change password to NEWPW
Refer to the MR2002 command reference document (Contact Canary Systems) for a complete list.
1. Programming of the VirtualDL is a type of CRBasic programming language, the Download File
and instruction file extension is .dls.
2. Most of the Connection Settings options in the Network Manager are disabled for the Virtual Datalogger as
they are not applicable to this node type.
3. The Logger form has several differences in the interface when using the Virtual Datalogger, including:
4. The folder [Shared Docs]\MLGateway\Lib\VirtualDL contains the multilogger.ini setup file and
related programming files.
Section 7 – Roobrik
Included with MultiLogger is a powerful data reduction program called Roobrik (program file roobrik.exe).
This program is loaded (or selected if already loaded) when the Data button is pressed on the
MultiLogger toolbar. By default Roobrik will be passed the root name of the currently loaded configuration
file, with the extension changed from .cfg to .par, if the file does not exist one will be created. The
parameter file stores all of the settings related to the data reduction to be performed with Roobrik.
Essentially it is the function of Roobrik to process the ASCII data files that have been collected, calculate
additional values (if configured) and output the results to a report, chart or directly into Microsoft Excel
using OLE/DDE linking. You must have Microsoft Excel, version 5.0 or higher, installed on your machine
for the Excel linking to work!
A view of the main form of Roobrik is shown below, please see the Roobrik User’s Guide for information
regarding the operation of the program. The User‘s Guide is available in our support directory at
http://www.canarysystems.com/nsupport/ or by contacting your software vendor or Canary Systems
directly.
8.1 MLEditor
When the gear button is pressed the contents of the specified instruction file are loaded into MLEditor, an
example is shown below.
Move the scroll bars at the bottom and right of the editor window to view the entire file.
The toolbar at the top of the editor window has the following functions:
New – Create a new file. If you have made changes to the current file you will be prompted to save
your changes.
Open – Open an existing file. If you have made changes to the current file you will be prompted to
save your changes.
Save – Save the current file using the default file name.
Save As… – Save the current file using a different name.
Print – Print the current file to the default printer.
Cut – Cut the current editor selection to the clipboard.
Copy – Copy the current editor selection to the clipboard.
Paste – Paste the clipboard contents to the current cursor position.
Delete – Delete the current editor selection.
Select All – Select the entire contents of the editor.
Help – Display the MultiLogger Editor topic from the help file.
The mode of the editor depends on the extension of the file you are loading. The table below lists the
MultiLogger extensions and respective editor mode.
This mode functions as a basic text editor, similar to the Windows program Notepad. Any file may be
edited using this mode, all changes are recorded in simple text format.
Datalogger instruction files for Legacy programmed dataloggers such as the CR510 and CR10X may be
created or modified using this mode. A typical display is shown below.
Instructions are indicated by lines beginning with ‗P‘, the instruction number follows the ‗P‘. A
description of the instruction follows to the right of the instruction number.
Instructions may be entered when the cursor is between instructions by entering the instruction
number and pressing <ENTER>.
Instruction parameters are indicated by lines beginning with a numeric value and followed by a colon
and brackets indicating where the parameter value is located.
Descriptions for each parameter are shown in blue to the right of the parameter value brackets.
Comments may be inserted before instructions and after the instruction or parameter description on
each line. Comments are preceded by a semi-colon and display in blue italic.
The <TAB> key will advance the cursor between parameter value locations (between brackets) and
comments.
Press <F1> when the cursor is located between instructions to load a list of instructions for the
particular control module being used. Press <F1> when the cursor is located at a parameter value
and you will be shown a list of possible values for a parameter.
Press <F1> when the cursor is located at an Input Storage location (parameter description ‗Loc‘
shown in example) and a list of numeric values and labels will display. You may select a numeric
value or the label to enter as the location parameter. You may also append the parameter with the
loop indexing (‗—‗) characters or the channel indexing (‗++‘) if you like. The list of numeric values and
labels is derived by loading the Input Storage Assignments list from your configuration file and the
MultiLogger setup file. In addition a list of subroutine assignments and miscellaneous variables are
also loaded from the MultiLogger setup file.
The datalogger Download File for the Legacy programmed dataloggers such as the CR510 and CR10X
may be edited using this mode. A Download File contains the type of control module, the Input Storage
labeling, the instructions that operate the datalogger and special configuration codes like memory settings
and security codes.
The Download File mode functions very much like the Instruction File mode, the key difference is the way
the labeling is handled, or in other words the values for parameters that refer to Input Storage locations.
In the Instruction file mode you can actually enter a descriptive label for your location parameter which
MultiLogger then resolves to a value when the program is generated. In the Download File mode all Input
Storage location references must be numeric.
The header of the Download File stores the Input Storage labels, up to 254 may be specified. When the
Download File is loaded by the editor a table is created of Input Storage locations and labels. When you
press <F1> at a location parameter you will be shown this table. You may select an Input Storage location
number to enter for the location parameter by clicking on the label in the list. The corresponding Input
Storage number is then entered as the location parameter value. You may also append the indexing
characters (‗—‗) after the numeric value if you like. You may edit the values or labels of the list shown by
pressing <F1>.
See the previous section describing the Instruction file mode for more information.
8.2 MLSetup
Many of the program generation options such as Gage Type | Make | Model selections are customizable,
this includes modifying the programming for a given application or adding new options to extend the
functionality of the program generation.
The drop-down list selections are stored in a multilogger.ini file in the folder related to each type of
datalogger that MultiLogger can manage, as follows:
Launch MLSetup by using the shortcut found in the MultiLogger group. Use the File | Open menu option,
or the Open button, to open a file browse dialog and browse to the appropriate multilogger.ini file.
The configurable options are shown in tree form, expanding the node will show the selections available
for each option. Nodes may be added, deleted or modifying using the toolbar.
Hint: The Units section is derived from the units.ini file located in the [Shared Docs]\CanarySys folder.
JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC
1 1 32 60 91 121 152 182 213 244 274 305 335
2 2 33 61 92 122 153 183 214 245 275 306 336
3 3 34 62 93 123 154 184 215 246 276 307 337
4 4 35 63 94 124 155 185 216 247 277 308 338
5 5 36 64 95 125 156 186 217 248 278 309 339
6 6 37 65 96 126 157 187 218 249 279 310 340
7 7 38 66 97 127 158 188 219 250 280 311 341
8 8 39 67 98 128 159 189 220 251 281 312 342
9 9 40 68 99 129 160 190 221 252 282 313 343
10 10 41 69 100 130 161 191 222 253 283 314 344
11 11 42 70 101 131 162 192 223 254 284 315 345
12 12 43 71 102 132 163 193 224 255 285 316 346
13 13 44 72 103 133 164 194 225 256 286 317 347
14 14 45 73 104 134 165 195 226 257 287 318 348
15 15 46 74 105 135 166 196 227 258 288 319 349
16 16 47 75 106 136 167 197 228 259 289 320 350
17 17 48 76 107 137 168 198 229 260 290 321 351
18 18 49 77 108 138 169 199 230 261 291 322 352
19 19 50 78 109 139 170 200 231 262 292 323 353
20 20 51 79 110 140 171 201 232 263 293 324 354
21 21 52 80 111 141 172 202 233 264 294 325 355
22 22 53 81 112 142 173 203 234 265 295 326 356
23 23 54 82 113 143 174 204 235 266 296 327 357
24 24 55 83 114 144 175 205 236 267 297 328 358
25 25 56 84 115 145 176 206 237 268 298 329 359
26 26 57 85 116 146 177 207 238 269 299 330 360
27 27 58 86 117 147 178 208 239 270 300 331 361
28 28 59 87 118 148 179 209 240 271 301 332 362
29 29 60 88 119 149 180 210 241 272 302 333 363
30 30 89 120 150 181 211 242 273 303 334 364
31 31 90 151 212 243 304 365
Cells shown in grey must have 1 added to them for leap years.
Leap years occur every 4 years, i.e. 2000, 2004, 2008, etc.
Hint: When MultiLogger connects to MLGateway to make sure it is connecting to a compatible version. If
the version of MultiLogger is not compatible with MLGateway then one or both installations may need to
be updated to the current versions.
If installed and running as an Application, follow these steps to convert to Service operation:
1. Use the right-click pop-up menu to exit the application.
2. Start a command window by typing cmd <ENTER> using the Start | Run option
of Windows (or the Start | Search edit Vista and Windows 7).
3. Change to the folder where MultiLogger is installed, if the default folder was used
then enter cd \program files\multilogger <ENTER>.
4. Start MLServer as a Service by typing mlgateway /install
<ENTER>. A message should display indicating successful loading of
the Service. Close the cmd window by typing exit <ENTER>.
5. The Service must be started. Go to Control Panel | Administrative
Tools | Services. Locate the MLGateway entry, right-click and select
Start Service. The Services view should update to show it started.
MLGateway – Interface
The MLGateway interface is shown below. It provides status information as well as buttons to access the
various forms and functions.
Function
Buttons
Settings – Configure the Port used for MultiLogger to MLGateway communications, see the following
section for more information.
License – Configure the MLGateway license, see the following section for more information.
Deactivate – Deactivate the MLGateway license, see the following section for more information.
Configure Settings
To manually configure the Firewall, or to view the current Firewall settings, use the Control Panel |
Firewall applet, an example view showing MLGateway (and MLServer) is shown below.
MLGateway Activation
MLGateway must be licensed and activated on each machine where it is running. There are two steps:
If all fields are entered correctly, the License Key is valid and
the computer has Internet connectivity, the Authorization Code
will be delivered electronically and the software will be
activated.
Authorization Failed.
There was an error in the negotiation for the Authorization Code. Try pressing Activate again and if it fails
again then contact your vendor or Canary Systems for further direction.
MLGateway Deactivation
MultiLogger Suite can now be un-installed by using the Control Panel | Add
Remove Programs applet.
Open Saved Save Current Clear Current Open Set Search Log
Log File Log File Log File Filter Form Contents
The form provides for viewing the status messages as well as saving them and filtering what records are
shown. Typically the log file is used for troubleshooting and performance evaluation. Contact Canary
Systems for information on specific messages.
Import of data collected by other systems and/or software though import folders.
Processing of data in the database and generation of alarms and other notifications.
It can be deployed as an application or as a Windows Service. If the user installing MultiLogger Suite has
Administrator rights then it will be installed as a Service, otherwise it will install as an Application. Running
as a service provides the advantage of not requiring a user to be logged in for MLServer to function.
Several notification methods are available including email, pager, COM port, e.g. sending a command
string out a serial port of the PC, digital I/O port events, e.g. using a Keithley digital I/O card to activate a
dialer or other attached notification device and running executables. See the Insite User‘s Guide for more
information on configuring and using these notification methods.
Click the x in the upper right corner of the form to close the form.
MLServer checks every 60 seconds for pending messages. Message information is generated by
MLGateway when the Notification System is enabled, this information is stored in a file called
notifylist.txt. MLServer also processes data stored in the Firebird database and generates notifications
based on the notification configuration of the database. If there are pending messages then action is
taken depending on the type of message.
Complete detail on the installation and configuration of MLServer are found in the MLDBConsole User‘s
Guide.
Enclose any information that is being sent to the modem in quotation marks (e.g., phone
numbers, carriage return code).
Enter control characters by preceding the character with a ^. For example, enter "^m" to send
control m which is a carriage return character. Alternately the # character, followed by a number
in the range 0-255, may be used to send non-printable ASCII codes. For example to send a
carriage return, include #13 in the quoted string.
Enter Delay Commands in the form of Dn where n is the specified number of milliseconds that the
transmission is delayed. A Delay Command forces the preceding portion of the command string
to be sent then delays for the specified number of milliseconds before sending more characters.
Characters received during a delay are accepted and discarded.
Enter Wait for Response Commands in the form of R"xx"n. A Wait for Response Command
forces the preceding portion of the command string to be sent then waits for up to n milliseconds
for the quoted string, xx, to be returned. When the last character of the quoted string is received,
the command is complete and the command string continues with the next command. If the
quoted string is not received, the dialing command is aborted.
Hint: Only the order and existence of the quoted string is checked. Other characters may be mixed in the
response and the string will be accepted if the specified characters are in the correct order.
Enter T"xx" commands to transmit the quoted string, xx, without waiting for any echo.
If desired, spaces can be used between commands and quote strings; the spaces are ignored.
For example, "^m" D250 "^m" D250 "ATZ^m" R"OK"250 does the following: sends a carriage
return, pauses 250 milliseconds, sends another carriage return, pauses another 250 milliseconds,
sends ATZ followed by a carriage return, then waits up to 250 milliseconds for OK to be returned
from the modem.
Enter a ^m (carriage return) after each command string to send the command string to the
modem.
Notes:
A ^m must be entered after each command string or the command string won't be sent to the modem
(e.g., if a phone number is in a command string and a ^m is not entered, the phone number will not be
dialed).
After each character has been sent, MultiLogger waits for its echo. If an echo has not been received
within the time-period specified in the Extra Response Time, MultiLogger will continue with the next
character.
For security none of the edits will display the passwords that you enter. Passwords may be from 6 to 255
characters in length.
B.5 Call-Back
Call-back is a mechanism where the dataloggers in your Network Configuration can originate a call or
message to signal to the answering or receiving computer that data collection must be performed. The
call-back event is usually the result of an alarm condition where one or more values have exceeded the
programmed limits and user intervention is required. Call-back should not be used for routine data
collection, configuring the schedule of the datalogger nodes is better suited for this purpose.
There are two aspects to configuring the call-back system, first the Gateway computer must be configured
to properly handle the call-back events, second, the datalogger must be programmed to initiate the call-
back.
The datalogger must be programmed to initiate a call-back event, this is accomplished using the
programming for the respective datalogger. These are usually configured using the Alarm Action
option of the Logger form. Consult your software vendor or check the support area of the Canary
Systems website at www.canarysystems.com for information on using this option.
The datalogger must be programmed with the correct Datalogger ID, this is usually accomplished
automatically by running the Update procedure in the Logger form with the correct Datalogger ID
setting and the appropriate Alarm Action option.
Usually the datalogger must have a flag reset after a call-back event, although this would depend on
the programming method used. Consult your software vendor or Canary Systems for guidelines
regarding resetting of flags in the vent of a call-back event. Flags are usually reset by activating the
Text Monitor for the selected datalogger and clicking on the flag that is used to reset the call-back
mechanism.
The menu item Show MultiLogger Log File will invoke the Log File Viewer, an example is shown
following. The MultiLogger Log File is the text file, multilogger.log, found in the [Shared
Docs]\MultiLogger path. The MultiLogger Log File includes messages such as the software version
numbers, launch status, status of various communication functions and any error messages returned.
The date and time of the message is noted, the Gateway name and the Priority.
Priority Type
Client Client messages between MultiLogger and MLGateway.
Internal These are internal messages, usually errors in the function of MultiLogger.
Transport Messages detailing the connections and disconnections between MultiLogger and
MLGateway.
Logger Event messages usually generated by various Logger actions such as Start.
The Log File Viewer formats and displays the multilogger.log file and includes options for saving, opening,
filtering the messages, among other options.
Open Saved Save Current Clear Current Open Set Search Log
Log File Log File Log File Filter Form Contents
Use the Log File Filter option to filter which records are
shown in the viewer. To select specific record types simply
click in the Type group.
The menu item Show Gateway Log File will invoke the Log File Viewer, an example is shown following.
The Gateway Log File is the text file, mlgateway.log, found in the [Shared Docs]\MLGateway path. The
Gateway Log File includes messages such as the software version numbers, status of various
communication functions including low-level communications and any error messages returned. The date
and time of the message is noted, the Gateway name and the Priority.
There are several different types of messages generated:
Priority Type
ComDebug Messages related to debugging of the communications.
Hardware These are typically errors in the communications between MLGateway and
connected hardware.
Internal Various internal messages of MLGateway, usually related to deleting records from
the log file or other house-keeping.
Low Level Low-level communications between MLGateway and dataloggers. (Must be
enabled using the option on the Gateway panel of the Network Manager)
Server Messages detailing specific actions of MLGateway such as Task execution or other
functions.
Status Status messages which are generally low-priority updates of various functions.
Transport Messages detailing the connections and disconnections between MultiLogger and
MLGateway.
Use the Set Filter form to control which messages are shown, the example below illustrates the view with
the option Include low-level info checked on the Gateway panel, then the filter configured to only show
low-level log events, or the communications between the Gateway and specific dataloggers.
See the previous section on other controls and functions of the Log Viewer form.
Contact Canary Systems with questions on specific messages.