Honeywell Mercury Driver
Not counted towards your tag license limit.
This driver can communicate with the following versions of Honeywell Mercury flow computer devices:
- ECAT
- Mini-AT (firmware versions newer than 6.81)
- Mini-Max (firmware versions newer than 2.60)
- ERX
- EC350
- ERX350
The following Honeywell Mercury protocol features are supported:
- Reading item data.
- Reading of live data items.
- Write data to an item.
- Retrieving logged data records (including extracting events from audit trigger/alarm field).
- Reading of event log records (when supported by device).
- Reading of alarm log records (when supported by device).
- Support for incoming calls initiated by a site.
Unlike a standard driver, all reads and writes are done together after establishing a session with the RTU. Standard read triggers in IO tags are disabled. If a write is called, the value to be written is saved within the driver and then written out during the next calling session. A triggering mechanism is required to perform the calls. We recommend using a Polling Driver Tag for that purpose.
What is read by the driver during each call is determined by the addresses configured in I/O tags using this driver.
Related application properties
The following property settings hold additional configuration parameters for your Honeywell Mercury driver:
MercuryDriverAlarmXXXPriority, where XXX is the item number (only a certain subset of item numbers are alarms).
MercuryDriverEventXPriority, where X is the event code, ranging between 0 and 22.
MercuryDriverTAPriority_XXXX, where XXXX is a particular Trigger Type.
Troubleshooting
-
The driver appears to be configured correctly but has not triggered a single read since the application started.
Has a Polling Driver tag been configured? The driver must initiate sessions to receive data. We recommend that you configure a Polling Driver tag to manage the polling interval and trigger sessions.
-
Why can't I use a Trigger tag to trigger sessions?
If you only have one Honeywell Mercury driver, you could use a Trigger tag tied to its Trigger parameter. However a Polling Driver tag is suitable for single and multiple configurations.
Server List
Select (or create) a named server list.
Honeywell Mercury Driver, Configuration properties tab
Device Type
Commands work differently based on the device. Select from any of:
- Mini-AT
- Mini-Max
- ECAT
- EC 350
- ERX
- ERX 350
Date Format
Three options are allowed:
- MMDDYY
- DDMMYY
- YYMMDD
Site ID #1, Site ID #2
Used by the discriminator to determine the driver to which inbound calls are sent.
Access Code
Defaults to 33333
Enable VTScada Alarm Logging
Select if alarms read from the device should be recorded in the VTScada alarm history.
Honeywell Mercury Driver, Communications properties tab
Port
Must be a serial port, to which a modem or cellular modem is attached.
Call Trigger
A tag or expression. A call is placed when this value changes from zero to any non-zero value.
Timeout
Specify the time in seconds, after which a call is aborted if there is no response. Defaults to 2 seconds.
Device Clock Time Zone
VTScada stores all values using UTC time zone. To store time-stamped data correctly, you must specify the timezone of the RTU.
Retries
The number of times to retry a message before declaring an error.
Use only if the driver is connected to a device that uses a serial port or a UDP/IP port that is configured to be polled. When connected directly to a device using TCP/IP, this value should normally be set to 0 since TCP/IP is a guaranteed message delivery protocol.
For unreliable communications, such as radio, set to 3 or 4.
Hold
Select this to have I/O tags attached to the driver hold their last value in the event of a communication failure. If not selected, tags will have their value set to invalid on a communication failure.
