The Fusion4 Communication Manual provides users with the
information needed to automate the control and data retrieval process
from Honeywell Enraf microprocessor-based controllers and Fusion4
Portal.
This manual describes the machine-to-machine messages needed for
electronic controller operation using a number of protocols. By providing
the protocols as defined in this manual, users can choose the protocol
that best suits their needs.
This manual applies to Fusion4 Portal and all Fusion4 controllers. The
list of controllers includes:
Fusion4 SSC-A (Single Stream Controller for Additive Injection)
Fusion4 SSC-B (Single Stream Controller for Blending)
Fusion4 MSC-A (Multi-Stream Controller for Additive Injection)
Fusion4 MSC-L (Multi-Stream Controller for Loading)
1.2 Target audience
This manual is intended for:
Administrators who are assigned to install Fusion4 controllers and/or
Fusion4 Portal
Administrators, engineers, system integrators and supervisors who
are assigned to configure and maintain Fusion4 controllers and/or
Fusion4 Portal
System integrators who are assigned to integrate the Terminal
Automation System (TAS) with Fusion4 controllers and/or Fusion4
Portal
Operators who are assigned to operate Fusion4 controllers and/or
Fusion4 Portal
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual1 - 1
General
This page is intentionally left blank.
Fusion4Part No.: 4418305_Rev07
1 - 2Communication ManualHoneywell
Safety
CHAPTER 2 SAFETY
2.1 Safety conventions
2.1.1 Warnings
Following warning mark is used within this document to urge attention in
order to prevent personal injuries or dangerous situations, further
described within this document.
SymbolDescriptionRemark
General warningWill always be explained by text.
2.1.2 Cautions
Following caution mark is used within this document to urge attention in
order to prevent damages to the equipment, further described within
this document.
SymbolDescription
General caution sign
2.2 Liability
The information in this installation & operation manual is the copyright
property of Honeywell International Inc. Honeywell International Inc.
disclaims any responsibility for personal injury or damage to equipment
caused by:
Deviation from any of the prescribed procedures
Execution of activities that are not prescribed
Neglect of the safety regulations for handling tools and use of
The contents, descriptions, and specifications in this manual are subject
to change without notice. Honeywell International Inc. accepts no
responsibility for any errors that may appear in this manual.
electricity
WARNING!Only personnel that are authorized by the customer are allowed to make
changes on the Fusion4 system. All modifications must be in accordance to
the guidelines as set forth by Honeywell International Inc.
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual2 - 1
Safety
This page is intentionally left blank.
Fusion4Part No.: 4418305_Rev07
2 - 2Communcation ManualHoneywell
Fusion4 System Overview
CHAPTER 3 FUSION4 SYSTEM OVERVIEW
Honeywell Enraf’s Fusion4 loading automation system manages and
controls the loading and unloading of petrochemicals in a safe, secure
and well-documented manner. Key elements in the Fusion4 system are:
Fusion4 Portal, see section 3.1
Fusion4 controllers for loading, see section 3.5
Fusion4 controllers for additive injection, see section 3.2 and
section 3.4
Fusion4 controllers for blending, see section 3.3
FIGURE 3-1 shows an overview of the Fusion4 system.
FIGURE 3-1Fusion4 system overview
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual3 - 1
Fusion4 System Overview
3.1 Fusion4 Portal
3.1.1 Description
Fusion4 Portal is a Windows PC software suite designed to interface
with Honeywell Enraf's portfolio of hazardous area control devices. Its
main functions are:
Retrieving data from the connected devices to print a Bill of Lading
(BoL) after product has been delivered to a truck or train, et cetera
Configuring, commissioning and diagnosing of controllers
OPC interfacing
Monitoring of field devices for the control room
Printing transactions
Fusion4 Portal can scan and print transaction data of 1 up to 250
streams spread across up to 50 devices, including:
Fusion4 Fusion4 SSC-Bs (Single Stream Controllers for Blending)
Fusion4 Fusion4 MSC-Ls (Multi-Stream Controllers for Loading)
Fusion4 Fusion4 MSC-As (Multi-Stream Controllers for Additive
Injection)
3.1.2 Principle of operation
The basic principle of operation is achieved by Fusion4 Portal
continuously communicating with the connected devices. As soon as a
device has new transaction data available Fusion4 Portal will retrieve
this data. When transaction data from a connected device like an
Fusion4 SSC-A or Fusion4 MSC-A is received and the print transaction
function of the device is enabled, a transaction summary will be printed.
When transaction data from a connected device like an Fusion4 SSC-B,
Fusion4 MSC-L or 1010CB is received and the print transaction function
of the device is enabled, the data, including the applicable engineering
units, is immediately printed resulting in a Bill of Lading (BoL). The BoL
is printed for custody transfer when a product from storage tanks has
been transferred to other parties. Fusion4 Portal is certified for printing
W&M compliant BOLs for Contrec 1010CB and Fusion4 SSC-B. For
this reason, Fusion4 Portal is certified for printing W&M compliant BoLs
for 1010CB and SSC-B. The transaction data, including the applicable
engineering units, is stored immediately after receipt on the hard disk.
Fusion4 Portal features an OPC server that communicates with loading
devices like 1010CB and Fusion4 MSC-L. This server offers OPC
connectivity with OPC clients to read, subscribe and write values to the
Fusion4Part No.: 4418305_Rev07
3 - 2Communication ManualHoneywell
Fusion4 System Overview
devices to achieve the required work flow at the terminals. An example
of an OPC client is a Terminal Automation System (TAS).
3.1.3 Communications
Communication with the devices is realized by using hard-wired, serial
EIA RS-422/485 communications ports, which are connected to the
devices via serial communication lines.
NOTE: Optionally, the Fusion4 Portal server may be connected to the devices through
a Terminal Server.
Fusion4 Portal includes several different communications protocols.
These include:
FlexConn (see CHAPTER 9)
SLIP+ (see CHAPTER 8)
3.2 Fusion4 Single Stream Controller for Additive Injection
3.2.1 General
The Fusion4 Single Stream Controller for Additive Injection
(Fusion4 SSC-A) is designed to control one single additive stream. It
can operate within any product transfer application, such as road tanker
loading, rail off-loading or pipeline transfer, where multiple products
need to be accurately combined.
3.2.2 Principle of operation
The basic principle of operation is achieved by the Fusion4 SSC-A
monitoring the flow of the wild stream, and using this flow rate to
accurately pace the flow of the additive stream to a predetermined
target ratio in parts per million (ppm).
The pacing of the additive stream is realized through accurate, rapid
injections of very small volumes of additive into the process, at
frequently and evenly spaced intervals.
The Fusion4 SSC-A is a cycle-based injector, meaning that the additive
is not dispensed continuously. An internal recipe controls the ratio of
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual3 - 3
Fusion4 System Overview
additive being injected to the process stream. In a typical application,
the process flow rate is monitored by the controller. As chemical
additive is called for, the controller opens a solenoid control valve and
injects a small quantity of additive into the process stream. When the
required quantity is reached, the controller closes the valve and waits
until the next injection is required. The injection cycle repeats in this
manner, keeping the additive ‘in pace’ with the process flow. The reason
for cyclical injection technology is uniform mixing of product and
additive.
The injection control of the Fusion4 SSC-A can be achieved in different
pacing modes:
Self-paced mode: The Fusion4 SSC-A autonomously injects on a
time and fluid volume basis (configurable).
Smart mode: An external trigger source (Pulse Input, Digital Input,
Analogue Input, or Comms) makes the Fusion4 SSC-A inject a
configurable additive volume.
server mode: In this case additive injection is fully controlled by an
external device.
3.2.3 Communications
Full control of and full access to all setup entities of the Fusion4 SSC-A
can be realized by using a hard-wired, serial EIA RS-485
communications port, which is connected to a client system via a data
communications line. This client system can be a PC service program, a
load computer, a SCADA system, DCS, or any other type of Terminal
Automation System.
The Fusion4 SSC-A includes several different communications
protocols. These include:
FlexConn (see CHAPTER 9)
FMC Smith AccuLoad (see CHAPTER 5)
Brooks PetroCount (see CHAPTER 6)
Modbus Legacy and Modbus RTU (see CHAPTER 7)
The Fusion4 SSC-A supports two serial communication ports.
The CAN-ADD-BLEND board houses a 2- or 4-wire isolated RS-485
communication port.
The CAN-OPTION-SSC board houses a 2-wire isolated RS-485
communication port.
Alarms are reported through the protocols of the RS-485
communications interface. Alarms may also be cleared using the
RS-485 communications interface.
Fusion4Part No.: 4418305_Rev07
3 - 4Communication ManualHoneywell
Fusion4 System Overview
NOTE: Refer to the Installation & Operation Manual Fusion4 SSC-A (Part No.
4418300) for more information.
3.3 Fusion4 Single Stream Controller for Blending
3.3.1 General
The Fusion4 Single Stream Controller for Blending (Fusion4 SSC-B) is
a hazardous area, intelligent blend controller, utilizing state-of-the-art
microprocessor technology for high-accuracy blending applications.
The MID-compliant Fusion4 SSC-B is designed to control one single
blend stream. It can operate within any product transfer application,
such as road tanker loading, rail off-loading or pipeline transfer, where
multiple products need to be accurately combined.
3.3.2 Principle of operation
The basic principle of operation is achieved by the Fusion4 SSC-B
monitoring the flow of the wild stream, and using this flow rate to
accurately pace the flow of the blend stream to a predetermined target
blend percentage or ratio.
The pacing of the blend stream is achieved through digitally controlled
solenoid valves that modulate the position of a variable control valve
within the blend stream.
The Fusion4 SSC-B is capable of achieving highly accurate linear
control across the complete blend range; allowing for blend ratios from
0% to 100% (practical blend rates are around 5% to 40%) on standard
load rack applications.
Temperature and pressure measurements are used to convert the
observed blend volume to reference conditions, in order to have very
accurate blend transaction data that can be used for W&M-compliant
custody transfer.
3.3.3 Communications
Full control of and full access to all setup entities of the Fusion4 SSC-B
can be realized by using a hard-wired, serial EIA RS-485
communications port, which is connected to a client system via a data
communications line. This client system can be a PC service program, a
load computer, a SCADA system, DCS, or any other type of Terminal
Automation System.
The Fusion4 SSC-B includes several different communications
protocols. These include:
FlexConn (see CHAPTER 9)
FMC Smith AccuLoad (see CHAPTER 5)
Brooks PetroCount (see CHAPTER 6)
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual3 - 5
Fusion4 System Overview
Modbus Legacy and Modbus RTU (see CHAPTER 7)
The Fusion4 SSC-B supports two serial communication ports.
The CAN-ADD-BLEND board houses a 2- or 4-wire isolated RS-485
communication port.
The CAN-OPTION-SSC board houses a 2-wire isolated RS-485
communication port.
Alarms are reported through the protocols of the RS-485
communications interface. Alarms may also be cleared using the
RS-485 communications interface.
NOTE: Refer to the Installation & Operation Manual Fusion4 SSC-B (Part No.
4418301) for more information.
3.4 Fusion4 Multi-Stream Controller for Additive Injection
3.4.1 General
The Fusion4 Multi-Stream Controller for Additive Injection
(Fusion4 MSC-A) is designed to control up to twenty four additive
streams. It can operate within any product transfer application, such as
road tanker loading, rail off-loading or pipeline transfer, where multiple
products need to be accurately combined.
3.4.2 Principle of operation
The basic principle of operation is achieved by the Fusion4 MSC-A
monitoring the flow of the wild stream, and using this flow rate to
accurately pace the flow of the additive stream to a predetermined
target ratio in parts per million (ppm).
The pacing of the additive stream is realized through accurate, rapid
injections of very small volumes of additive into the process, at
frequently and evenly spaced intervals.
The Fusion4 MSC-A is a cycle-based injector, meaning that the additive
does not dispense continuously. An internal recipe controls the ratio of
additive being injected to the process stream. In a typical application,
the process flow rate is monitored by the controller. As chemical
additive is called for, the controller opens a solenoid control valve and
injects a small quantity of additive into the process stream. When the
required quantity is reached, the controller closes the valve and waits
until the next injection is required. The injection cycle repeats in this
manner, keeping the additive ‘in pace’ with the process flow. The reason
for cyclical injection technology is uniform mixing of product and
additive.
Fusion4Part No.: 4418305_Rev07
3 - 6Communication ManualHoneywell
Fusion4 System Overview
The injection control of the Fusion4 MSC-A can be achieved in different
pacing modes:
Self-paced mode: The Fusion4 MSC-A autonomously injects on a
time and fluid volume basis (configurable).
Smart mode: An external trigger source (Pulse Input, Digital Input,
Analogue Input, or Comms) makes the Fusion4 MSC-A inject a
configurable additive volume.
server mode: In this case additive injection is fully controlled by an
external device.
3.4.3 Communications
Full control of and full access to all setup entities of the Fusion4 MSC-A
can be realized by using:
Hard-wired, serial EIA RS-485 communications port, which is
connected to a client system via a data communications line
Ethernet
This client system can be a PC service program, a load computer, a
SCADA system, DCS, or any other type of Terminal Automation
System.
The Fusion4 MSC-A includes several different communications
protocols. These include:
RS-485
SLIP+, see CHAPTER 8
FlexConn, CHAPTER 9
FMC Smith AccuLoad (see CHAPTER 5)
Modbus Legacy and Modbus RTU | TCP/IP (see CHAPTER 7)
Ethernet
FlexConn (see CHAPTER 9)
Modbus TCP/IP (see CHAPTER 12)
The Fusion4 MSC-A supports the following serial communication ports:
The CAN-ARM-MSC-1 board houses one isolated terminal
connector with two 2-wire half-duplex RS-485 communication ports.
The CAN-ARM-MSC-2 board houses one isolated terminal
connector with two 2-wire half-duplex RS-485 communication ports.
The CAN-HMI-MSC board houses one isolated terminal connector
with two 2-wire half-duplex RS-485 communication ports and one
4-wire full-duplex RS-485 terminal connector.
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual3 - 7
Fusion4 System Overview
Alarms are reported through the protocols of the RS-485
communications interface. Alarms may also be cleared using the
RS-485 communications interface.
NOTE: Refer to the Installation & Operation Manual Fusion4 MSC-A (Part No.
4418307) for more information.
3.5 Fusion4 Multi-Stream Controller for Loading
3.5.1 General
The Fusion4 Multi-Stream Controller for Loading (Fusion4 MSC-L) is a
Load Computer, Batch Controller Unit (BCU) or a Preset, and is typically
installed on a loading, at a terminal, in the petro chemical industry. The
Fusion4 MSC-L is designed to accurately transfer products from the
storage area into another containment vessel. Apart, from loading a
single product, the MSC-L also provides necessary functionality for
blending products, additive injections and for loading the final products
accurately, as required in the global oil storage and distribution industry.
The MSC-L controls the following:
Loading - Transferring the base or the stock oil, or the petroleum
derivative from a storage tank to a vehicle, for example, road trucks,
rail cars, or barges.
Additive injection - Improving and differentiating the base or stock oil,
or petroleum derivatives by changing the physical properties and
specifications of the oil product (fuel) during loading/transferring.
Blending - Combining two or more fluid products to a predetermined
specification during loading.
3.5.2 Communications
Full control of and full access to all setup entities of the Fusion4 MSC-L
can be realized by using:
Hard-wired, serial EIA RS-485 communications port, which is
connected to a client system via a data communications line
Ethernet
This client system can be a PC service program, a SCADA system,
DCS, or any other type of Terminal Automation System.
The Fusion4 MSC-L includes several different communications
protocols. These include:
RS-485
FMC Smith AccuLoad, see CHAPTER 5
Modbus RTU, see CHAPTER 7
Fusion4Part No.: 4418305_Rev07
3 - 8Communication ManualHoneywell
Fusion4 System Overview
FlexConn, see CHAPTER 9
Ethernet
FlexConn, see CHAPTER 9
Modbus TCP/IP, see CHAPTER 12
The Fusion4 MSC-L supports the following serial communication ports:
The CAN-ARM-MSC board houses one isolated terminal connector
with two 2-wire half-duplex RS-485 communication ports.
The CAN-HMI-MSC board houses one isolated terminal connector
with two 2-wire half-duplex RS-485 communication ports and one
4-wire full-duplex RS-485 terminal connector.
Alarms are reported through the protocols of the RS-485
communications interface. Alarms may also be cleared using the
RS-485 communications interface.
NOTE: Refer to the Installation & Operation Manual Fusion4 MSC-L (Part No.
4418309) for more information.
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual3 - 9
Fusion4 System Overview
This page is intentionally left blank.
Fusion4Part No.: 4418305_Rev07
3 - 10Communication ManualHoneywell
RS-485 Communications
CHAPTER 4 RS-485 COMMUNICATIONS
The Fusion4 controllers (Fusion4 SSC-A, Fusion4 SSC-B, Fusion4
MSC-A and Fusion4 MSC-L) use the EIA-485 standard for
communications. A converter is required to enable communications with
peripheral devices such as modems or personal computers that use the
EIA-232 interface standard.
Proper system wiring is critical to the reliable operation of serial
communication interfaces. Improper wiring can cause high data error
rates and reduce data throughput. Although exact wiring requirements
vary depending on the type of interface used, each of the following is
important to the overall success of a communications system:
RS-485 interfaces are typically used in multi-drop configurations. When
installing a two-wire cable for use with a Fusion4 controller, receive and
transmit share the same conductor pair (half-duplex). The wires must
be a twisted pair. Wiring for RS-485 must be designed as a daisy chain.
Cable stubs are permitted so long as they are 4.5 m (15 feet) or less in
length. Conductor pairs must be terminated with a termination resistor
at the most distant end, to ensure proper line impedance for maximum
signal reception. Without termination resistors, reflections of fast driver
edges can cause multiple data edges that can cause data corruption.
Termination resistors also reduce electrical noise sensitivity due to the
lower impedance. The value of each termination resistor should be
equal to the cable characteristic impedance (typically, 120 ohms for
twisted pairs).
Using the recommended cable (Belden Cable 9841 for two-wire), an
RS-485 interface may support maximum 32 server devices onto one
client (host) over a maximum wire length of 1000 m (3281 feet). The
host (client) initiates the communication by addressing one of the
servers in its query. Only the addressed server will respond.
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual4 - 1
RS-485 Communications
4.1 Characteristics
TABLE 4-1 displays the characteristics of an RS-485 interface used for
communications.
TABLE 4-1Characteristics of RS-485 Interface
ItemMin.TypicalMax.Unit
Terminator resistor R
Driver common mode voltage-1-+3
T
118120122
V
Driver output voltage, Open circuit1.5
Driver output voltage, Loaded1.5
Driver output short circuit current--±200mA
Receiver common mode voltage-7-+12V
Receiver sensitivity--±200mV
Receiver input resistance12--
Data transmission rate--500kbps
Number of connected devices--32-
4.2 Cable specifications
TABLE 4-2 displays the specifications of a cable used in RS-485
interfaces.
TABLE 4-2Cable specifications for RS-485 interfaces
ItemMin.TypicalMax.Unit
Cable length--1000
-1.5
-1.5
-6
-6
-3.6
-3.6
[3281]
V
V
k
m
[ft]
Cable characteristic impedance-120
Cable DC resistance--100
Cable capacitance--55.77
[17]
pF/m
[pF/ft]
Fusion4Part No.: 4418305_Rev07
4 - 2Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CHAPTER 5 FMC SMITH ACCULOAD PROTOCOL
5.1 Fusion4 SSC-A, Fusion4 SSC-B and Fusion4 MSC-A
5.1.1 Description
The FMC Smith AccuLoad protocol is closely related to the protocol
defined by Smith Meter Inc. for use with their AccuLoad Electronic
Preset Controller. In the FMC Smith AccuLoad protocol, there are two
different message formats, depending on whether the message
originated from the client or from a controller.
The message format for a command instruction from the client to a
controller is:
STXA1A2A
3
textETXLRC
TermDescriptionHex value
STXStart of Text Character02
A1A2A
textASCII string containing the command instruction
ETXEnd of Text Character03
LRCLongitudinal Redundancy Check
3-digit address of the Fusion4 controller
3
HEX
HEX
NOTE: This protocol is also used by MSC-L when it is the client and a Fusion4 SSC-A,
Fusion4 SSC-B or Fusion4 MSC-A is a server device communicating with each
other over RS485 using FMC Smith protocol for external additive injection.
The message format for a response/acknowledgment from a
controller to the client is:
NULSTXA1A2A
3
TermDescriptionHex value
NULNull Character00
STXStart of Text Character02
A1A2A
textASCII string containing the response acknowledgment
3-digit address of the Fusion4 controller
3
textETXLRCPAD
HEX
HEX
ETXEnd of Text Character03
LRCLongitudinal Redundancy Check
PADPad Character7F
HEX
HEX
The longest packet string transmitted or received by the controller can
be no longer than 255 characters in length. The command to or the
response from the controller is contained in the text field. The format for
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 1
FMC Smith AccuLoad Protocol
this field is defined in the descriptions of the allowed commands and
responses below.
5.1.1.1 Text field format
The structure of the text field is very specific for each command. The
formats for the text field apply whether the string is a request from the
client or a response from the controller. The format of the data
associated with a given parameter code is specific and cannot be
varied. Only one command may be transmitted to the controller in a
given text field.
The Parameter and Task Code formats are described in detail in the
Installation & Operation Manual of the specific Fusion4 controller. All
leading and trailing zeros on numbers must be transmitted. Even
though the alphanumeric data strings are of variable length, they cannot
be longer than the maximum length specified. The controller determines
the end of the string when either a semi-colon or an ETX is
encountered.
When a protocol string is received by the controller, it is first checked for
transmission errors by using the LRC. The LRC is a 7-bit exclusive-OR
of the characters in the protocol string following the STX character up to
and including the ETX character. If the LRC of the received string does
not match the received LRC value, an error has occurred in
transmission and the Fusion4 controller will ignore the string.
5.1.1.2 Broadcast commands
A Fusion4 controller is capable of receiving a ‘broadcast’ command
from the client unit using the FMC Smith AccuLoad protocol. A
broadcast command is a command that is directed to all the controllers
on the communications bus, simultaneously. In the controller, the
addresses 998, 999, and 000 are reserved for use as the Broadcast
Address. Any command message that is addressed to a controller‘s
Broadcast Address, is recognized by that unit and processed. However,
unlike a command to a controller’s primary address, a broadcast
command generates no response from the controller. Clearing alarms
and setting the time/date are examples of the use of broadcast
commands. Only write commands or task commands may be broadcast
since a read command by definition requires a response and responses
to broadcast commands are not allowed.
Fusion4Part No.: 4418305_Rev07
5 - 2Communication ManualHoneywell
FMC Smith AccuLoad Protocol
5.1.1.3 Command Identifier Prefixes
In TABLE 5-1 the command identifier prefixes that are available in the
FMC Smith AccuLoad protocol are listed.
TABLE 5-1FMC Smith AccuLoad protocol: Command identifier prefixes
IdentifierDescription
RVRead a value from the Fusion4 controller
WVWrite a value to the Fusion4 controller
EXExecute a task function in the Fusion4 controller
5.1.1.3.1 RV - Read Value
This command instructs the controller to read a memory location.
Request
RV_XXX
XXX= Parameter register code
_= Denotes a space
Response
RV_XXX_A0....A
XXX= Parameter register code
....A
A
0
n
_= Denotes a space
or
NOXXExecution of the command failed
XX= Two-digit error code as defined in section 5.1.1.4.
5.1.1.3.2 WV - Write Value
This command instructs the controller to program a memory location.
Request
WV_XXX_A0....A
XXX= Parameter register code to be written to
....A
A
0
n
n
Command completed successfully
= Value of the parameter register requested. It is an ASCII
character string whose format is defined in the specific
controller manual.
n
= Data to be written to the parameter register XXX. The data
string must conform exactly to the format for that code as
defined in the specific controller manual.
_= Denotes a space
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 3
FMC Smith AccuLoad Protocol
Response
OKValue was programmed successfully
or
NOXXExecution of the command failed
XX= Two-digit error code as defined in section 5.1.1.4.
5.1.1.3.3 EX - Execute Task
This command instructs the controller to execute a task function.
Request
EX_XXX
XXX= Task code as defined in the specific controller manual
_= Denotes a space
Response
OKTask was completed successfully
or
NOXXExecution of the command failed
XX= Two-digit error code as defined in section 5.1.1.4.
5.1.1.4 Error Codes
The controller is capable of returning several error messages to the
client unit if it is unable to successfully carry out a command. These
error messages are in the form of ʹNOXXʹ where ʹXXʹ is a two-digit
number representing the error that occurred.
The individual errors that the controller is capable of responding to are
listed in TABLE 5-2.
TABLE 5-2FMC Smith AccuLoad protocol: Error codes
Error No.DescriptionExplanation
00Illegal CommandCommand code is not
01Transaction in ProgressController is permitted. No
recognized.
measurement parameters can
be changed.
02Illegal ValueValue is out of range
03Syntax Error in ValueValue string is not in the correct
format.
04Illegal Text String FormatConstruction of the text field is
incorrect.
Fusion4Part No.: 4418305_Rev07
5 - 4Communication ManualHoneywell
FMC Smith AccuLoad Protocol
Error No.DescriptionExplanation
05Unit in Critical AlarmAlarm must be cleared before
the command can be
completed.
06Option Not InstalledCommand code is not
supported in this version of the
controller.
07No Transaction in ProgressTransaction must be in progress
to execute the command code.
08Transmission Error (LRC failed)Error occurred in the protocol
string during transmission.
09In Local Programming ModeController is being programmed
with the hand held controller.
10Commands out of SequenceAnother command code must
be performed before the current
one can be.
11Write Attempt to a Read Only
Value
12Access Denied to Security CodeFuture Use
13No Records FoundThis error results when trying to
5.1.1.5 Examples
Tried to store a value to a read
only parameter register.
read or clear records from the
Transaction or Security Log and
no records are present.
Example 1. The client requests the Active Alarm Status (802) of the controller
with address 123. The controller has no active alarms.
Request
STX123RV 802ETXLRC
Response
NULSTX123RV 802 0000ETXLRCPAD
Example 2. The client sets the Additive K-Factor to 6300.000 on the controller
with address 313.
Request
STX313WV 001 6300.000ETXLRC
Response
NULSTX313OKETXLRCPAD
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 5
FMC Smith AccuLoad Protocol
Example 3. The client sets the time on all the controllers on the communication
loop at the same time (broadcast command). The time is 02:34:13
PM. Number 999 is the broadcast address for the system.
Request
STX999WV 111 14:34:13ETXLRC
Response
None
5.1.2 Fusion4 SSC-A
TABLE 5-3 lists the FMC Smith AccuLoad protocol parameters for the
Fusion4 SSC-A (Single Stream Controller for Additive Injection).
TABLE 5-3FMC Smith AccuLoad protocol parameters for Fusion4 SSC-A
Parameter Name
Wild stream K-factor001floating pointRnnnnn.nnn
Additive K-factor002floating pointRnnnnn.nnn
Injection volume010floating pointR/Wnnnn.n
Volume per injection cycle020floating pointR/Wnnnn.n
Solenoid dwell time030integerRnnnnn
Minimum product volume for
transaction
Factored pulse output
resolution
Number of clean start cycles060integerR/Wnn
Flush volume061floating pointR/Wnnn
High flow threshold value063floating pointR/Wnnnnn
REMARK: The # denotes global parameters affecting all injector channels.
5.2 Fusion4 MSC-L
5.2.1 Description
The AccuLoad Emulation functionality in the Fusion4 MSC-L allows the
Fusion4 MSC-L to interact with a TAS in the same way as AccuLoad III
interacts. Due to some inherent differences between the devices, the
functionality of Standby mode and Remote mode is not implemented for
Accuload Emulation. Therefore, all supported commands currently work
irrespective of the mode of the Fusion4 MSC-L.
The Fusion4 MSC-L supports two protocols for AccuLoad Emulation
mode.
Communications for Terminal Mode of Operation, see section 5.2.1.1
Communications for Minicomputer Mode of Operation, see section
5.2.1.2
5.2.1.1 Communications for Terminal Mode of Operation
In Communications for Terminal Mode of Operation there are two
different message formats:
The message format for a command instruction to AccuLoad III is:
*A1A
2
TermDescriptionHex value
*Start of the message2A
A1A
textASCII string containing the command instruction
CRCarriage Return0D
LFLine Feed0A
2-digit Fusion4 MSC-L address (01...99)
2
REMARKS: 1. The CR-LF characters define the end of the message.
2. No error checking other than parity on each character is performed.
textCRLF
HEX
HEX
HEX
Fusion4Part No.: 4418305_Rev07
5 - 14Communication ManualHoneywell
FMC Smith AccuLoad Protocol
The message format for a response/acknowledgment from the Fusion4
MSC-L is:
*A1A
2
textCRLF
TermDescriptionHex value
*Start of the message2A
A1A
2-digit Fusion4 MSC-L address (01...99)
2
textASCII string containing the response/acknowledgment
CRCarriage Return0D
LFLine Feed0A
REMARKS: 1. The CR-LF characters define the end of the message.
2. No error checking other than parity on each character is performed.
5.2.1.2 Communications for Minicomputer Mode of Operation
In Communications for Minicomputer Mode of Operation there are two
different message formats:
The message format for a command instruction:
STXA1A
2
TermDescriptionHex value
STXStart of Text02
A1A
textASCII string containing the command instruction
2-digit Fusion4 MSC-L address (01...99)
2
textETXLRC
HEX
HEX
HEX
HEX
ETXEnd of Text03
LRCLongitudinal Redundancy Check0A
HEX
HEX
The message format for a response/acknowledgment from the Fusion4
MSC-L is:
NLSTXA1A
2
TermDescriptionHex value
NLNull character00
STXStart of Text02
A1A
2-digit Fusion4 MSC-L address (01...99)
2
textASCII string containing the response/acknowledgment
ETXEnd of Text03
LCRLongitudinal Redundancy Check
PADPad character7F
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 15
textETXLRCPAD
HEX
HEX
HEX
HEX
FMC Smith AccuLoad Protocol
5.2.2 Configuring AccuLoad Emulation functionality on the Fusion4 MSC-L
Configure the following from the HMI:
1. Install the AccuLoad Emulation Workflow from the installation
package.
2. Set the communication protocol of the selected COM port to Terminal host
or Minicomputer host. Set the baud rate, parity, etc. the same as the host
side.
3. Set the arm address for each arm from the arm identification menu. This
address needs to be the same as the one set on the host side.
4. From the device configuration menu, set the emulation type as AccuLoad.
5. From the Workflow Settings menu, set the workflow mode as ‘Remote
only’ and also set the correct timeout. When a command is not set within
this timeout, the Fusion4 MSC-L will go to Standby mode and only the
RE_SA command (see section 5.2.4.16) will get it back in Remote mode.
REMARK: In Standby mode it is currently not possible to perform transactions locally.
5.2.3 Fusion4 MSC-L Product Numbering
There are many commands in AccuLoad that fetch data by sending a
product number as a part of the command. In AccuLoad it is possible to
assign up to six products to an arm and then these can be addressed as
product 1 through 6 in a command. However, in Fusion4 MSC-L
streams are assigned to an arm. To match this with the AccuLoad
method, the products are numbered as follows.
Consider that for an arm in Fusion4 MSC-L, streams 2, 4, 6, 8 and 10
are assigned to this arm through the arm configuration. These will be
then internally numbered as product 1 through 5 for Emulation, i.e.:
Product 1 = Stream 2
Product 2 = Stream 4
Product 3 = Stream 6
Product 4 = Stream 8
Product 5 = Stream 10
Product 6 = Not used on this arm
Fusion4Part No.: 4418305_Rev07
5 - 16Communication ManualHoneywell
FMC Smith AccuLoad Protocol
5.2.4 Commands
5.2.4.1 AB - Allocate Blend Recipes
This command allocates the blend recipes that will be allowable for
selection. This allocation is a subset of those enabled in Program mode.
Command
AB_C1C2C3...C13
Where C1C2C3...C13 is the three- to thirteen-character bit map. See section
5.2.4.1.1 up to and including section 5.2.4.1.13 for more information.
Response
OKGood Response. Recipes were allocated
or
NOXXRecipes were not allocated.
XX= Two-digit error code as defined in section 5.1.1.4.
Remarks: 1. AccuLoad III has a total of 50 recipes on device level, whereas the Fusion4
MSC-L has 50 recipes per arm. Therefore, when the recipe numbers are
sent for a particular arm, these recipes need to be configured on that arm in
the Fusion4 MSC-L
2. A one allocates the corresponding recipe number for selection. Allocation is
cancelled when Transaction done status is being set.
3. Allocation is also cancelled if, when in Remote Control mode, a power-fail
restart occurs between batches.
4. This command does not require all characters. A minimum of three characters is accepted. For those characters omitted, the corresponding recipes
are not allocated.
5. This command will automatically exit from Program mode when initiated.
Constraints: Recipe allocation remains in effect for the current transaction only.
Special Case: None
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 17
FMC Smith AccuLoad Protocol
5.2.4.1.1 AB - Allocate Blend Recipes Command: Character 1
TABLE 5-6 describes character 1 of the AB command.
TABLE 5-6AB command: Character 1
CharacterRecipe Request
CharHexRecipe 4Recipe 3Recipe 2Recipe 1
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
5.2.4.1.2 AB - Allocate Blend Recipes Command: Character 2
TABLE 5-7 describes character 2 of the AB command.
TABLE 5-7AB command: Character 2
CharacterRecipe Request
CharHexRecipe 8Recipe 7Recipe 6Recipe 5
030
131X
232X
333XX
434X
535XX
636XX
737XXX
Fusion4Part No.: 4418305_Rev07
5 - 18Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharacterRecipe Request
CharHexRecipe 8Recipe 7Recipe 6Recipe 5
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
5.2.4.1.3 AB - Allocate Blend Recipes Command: Character 3
TABLE 5-8 describes character 3 of the AB command.
TABLE 5-8AB command: Character 3
CharacterRecipe Request
CharHexRecipe 12Recipe 11Recipe 10Recipe 9
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 19
FMC Smith AccuLoad Protocol
5.2.4.1.4 AB - Allocate Blend Recipes Command: Character 4
TABLE 5-9 describes character 4 of the AB command.
TABLE 5-9AB command: Character 4
CharacterRecipe Request
CharHexRecipe 16Recipe 15Recipe 14Recipe 13
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
5.2.4.1.5 AB - Allocate Blend Recipes Command: Character 5
TABLE 5-10 describes character 5 of the AB command.
TABLE 5-10AB command: Character 5
CharacterRecipe Request
CharHexRecipe 20Recipe 19Recipe 18Recipe 17
030
131X
232X
333XX
434X
535XX
636XX
737XXX
Fusion4Part No.: 4418305_Rev07
5 - 20Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharacterRecipe Request
CharHexRecipe 20Recipe 19Recipe 18Recipe 17
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
5.2.4.1.6 AB - Allocate Blend Recipes Command: Character 6
TABLE 5-11 describes character 6 of the AB command.
TABLE 5-11AB command: Character 6
CharacterRecipe Request
CharHexRecipe 24Recipe 23Recipe 22Recipe 21
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 21
FMC Smith AccuLoad Protocol
5.2.4.1.7 AB - Allocate Blend Recipes: Character 7
TABLE 5-12 describes character 7 of the AB command.
TABLE 5-12AB command: Character 7
CharacterRecipe Request
CharHexRecipe 28Recipe 27Recipe 26Recipe 25
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
5.2.4.1.8 AB - Allocate Blend Recipes: Character 8
TABLE 5-13 describes character 8 of the AB command.
TABLE 5-13AB command: Character 8
CharactersRecipe Request
CharHexRecipe 32Recipe 31Recipe 30Recipe 29
030
131X
232X
333XX
434X
535XX
636XX
737XXX
Fusion4Part No.: 4418305_Rev07
5 - 22Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharactersRecipe Request
CharHexRecipe 32Recipe 31Recipe 30Recipe 29
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
5.2.4.1.9 AB - Allocate Blend Recipes: Character 9
TABLE 5-14 describes character 9 of the AB command.
TABLE 5-14AB command: Character 9
CharactersRecipe Request
CharHexRecipe 36Recipe 35Recipe 34Recipe 33
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 23
FMC Smith AccuLoad Protocol
5.2.4.1.10 AB - Allocate Blend Recipes: Character 10
TABLE 5-15 describes character 10 of the AB command.
TABLE 5-15AB command: Character 10
CharactersRecipe Request
CharHexRecipe 40Recipe 39Recipe 38Recipe 37
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
5.2.4.1.11 AB - Allocate Blend Recipes: Character 11
TABLE 5-16 describes character 11 of the AB command.
TABLE 5-16AB command: Character 11
CharactersRecipe Request
CharHexRecipe 44Recipe 43Recipe 42Recipe 41
030
131X
232X
333XX
434X
535XX
636XX
737XXX
Fusion4Part No.: 4418305_Rev07
5 - 24Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharactersRecipe Request
CharHexRecipe 44Recipe 43Recipe 42Recipe 41
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
5.2.4.1.12 AB - Allocate Blend Recipes: Character 12
TABLE 5-17 describes character 12 of the AB command.
TABLE 5-17AB command: Character 12
CharacterRecipe Request
CharHexRecipe 48Recipe 47Recipe 46Recipe 45
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 25
FMC Smith AccuLoad Protocol
5.2.4.1.13 AB - Allocate Blend Recipes: Character 13
TABLE 5-18 describes character 13 of the AB command.
TABLE 5-18AB command: Character 13
CharacterRecipe Request
CharHexReservedReservedRecipe 50Recipe 49
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
A41XX
B42XXX
C43XX
D44XXX
E45XXX
F46XXXX
Fusion4Part No.: 4418305_Rev07
5 - 26Communication ManualHoneywell
FMC Smith AccuLoad Protocol
5.2.4.2 AR - Alarm Reset
This command resets one of the alarms currently registered at the
Fusion4 MSC-L.
Command
ARReset all alarms in all tables.
AR_XX_DDReset specific alarm for a specified directory.
AR_XX_IN_YYReset specific alarm for the specified injector.
XX= Two-character alarm code. See section 5.2.4.2.1 up to and
DD= Directory, where:
including section 5.2.4.2.5 for more information.
•SY = System
•P1 = Product 1
•P2 = Product 2
•P3 = Product 3
•P4 = Product 4
•P5 = Product 5
•P6 = Product 6
•AR = Arm
•M1 = Meter 1
•M2 = Meter 2 (Ratio, hybrid blending configuration only)
•M3 = Meter 3 (Ratio, hybrid blending configuration only)
•M4 = Meter 4 (Ratio, hybrid blending configuration only)
•M5 = Meter 5 (Ratio, hybrid blending configuration only)
•M6 = Meter 6 (Ratio, hybrid blending configuration only)
•IN = Additive injector
•RR = Recipe (01 - 50)
YY= Injector (01...24)
Response
OKGood response
or
NOXXThe alarm was not reset
XX= Two-digit error code as defined in section 5.1.1.4.
Remarks: The two-character alarm code must be one of those alarms that is allowed to
be reset through the communication channel.
Constraints: The alarm code must be able to be reset through communications. If it is
allowed, it must be pending or a ʺNOʺ will be returned.
Special Case: A special code, ʺAAʺ, may be used to reset all resettable alarms that are
pending in the directory specified.
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 27
FMC Smith AccuLoad Protocol
5.2.4.2.1 System Alarms That Can Be Reset Through Communications
TABLE 5-19 gives an overview of the System alarms that can be reset
through communications.
TABLE 5-19System Alarms
CodeCondition
CMCommunications Alarm - Communications failure on one of the
PAPower-fail Alarm - The unit either had a power failure or a hardware
U1User Alarm #1
U2User Alarm #2
U3User Alarm #3
U4User Alarm #4
U5User Alarm #5
communications channels.
reset occurred.
U6User Alarm #6
5.2.4.2.2 Injector Alarms That Can Be Reset Through Communications
TABLE 5-20 gives an overview of the Injector alarms that can be reset
through communications.
TABLE 5-20Injector Alarms
CodeCondition
KALow Additive Error - Indicates that not enough additive was injected
NANo Additive Pulses Error - Indicates that the additive flow meter's
GAGeneral Additive Error - Indicates that there is an additive injector error.
AHAdditive High Temperature Alarm - Used only for flow controlled
ALAdditive Low Temperature Alarm - Used only for flow controlled
ATAdditive Temperature Probe - Used only for flow controlled additive
during one cycle or an average of several cycles.
pulses were not detected.
additive types. Temperature probe or transducer is out of range with
high alarm setting.
additive types. Temperature probe or transducer is out of range with
low alarm setting.
types. Short or open condition in temperature probe.
PSPulse Security - Used only with the security option. Indicated that an
excessive number of out- of-sequence errors in the A-B pulse stream
have been detected on one of the flow controlled additive meters.
XAIndicates a collision in the incoming pulse stream. (The signals on A
and A-bar or B and B-bar are the same).
Fusion4Part No.: 4418305_Rev07
5 - 28Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CodeCondition
CTIndicates that the additive total received from the smart additive system
5.2.4.2.3 Arm Alarms That Can Be Reset Through Communications
TABLE 5-21 gives an overview of the Arm alarms that can be reset
through communications.
TABLE 5-21Arm Alarms
CodeCondition
CAAdditive Clean Line - The additive clean line volume delivered has
CLClean Line - The clean line volume delivered has under-run the clean
HFHigh Flow - Flow rate has exceeded limit set by Excess High Flow
may be erroneous
under-run the additive clean line volume programmed.
line volume programmed by at least the amount of clean line alarm
limit.
program parameter for more than 4 seconds.
OAOverrun - Volume delivered has exceeded the preset amount by at
5.2.4.2.4 Meter Alarms That Can Be Reset Through Communications
TABLE 5-22 gives an overview of the Meter alarms that can be reset
through communications.
TABLE 5-22Meter Alarms
CodeCondition
DRDensity Transducer - Density transducer failure or out-of-range
LALeakage Alarm - Indicates that leakage between transactions has
PRPressure Transducer - Pressure transducer failure or out-of-range
TPTemperature Probe - Short or open condition in the temperature probe
VFValve Fault - Indicates that the meter was still registering flow when the
least the number of units set in the Overrun Limit program code.
condition
exceeded the programmed ʺleakage alarm limitʺ (system 202).
condition
circuit
valve fault timer expired after the Fusion4 MSC-L commanded the
valve to close
XAIndicates a collision in the incoming pulse stream. (The signals on A
and A-bar or B and B-bar are the same)
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 29
FMC Smith AccuLoad Protocol
5.2.4.2.5 Product Alarms That Can Be Reset Through Communications
TABLE 5-23 gives an overview of the Product alarms that can be reset
through communications.
TABLE 5-23Product Alarms
CodeCondition
BHBlend High Alarm - An overflow on this product has caused a blend
BLBlend Low Alarm - An underflow on this product has caused the blend
BVBlock Valve Alarm - The valve did not close within 10 seconds after
HDHigh Density - Density transducer is out of range of the high alarm
HFHigh Flow Alarm - Flow rate has exceeded limit set by Excess High
tolerance to be exceeded.
tolerance to be exceeded.
receiving the signal to close.
setting.
Flow program code for more than 4 seconds.
HPHigh Pressure - Pressure transducer is out of range of the high alarm
setting.
HTHigh Temperature - Temperature probe or transducer is out of range of
the high alarm setting.
LDLow Density - Density transducer is out of range of the low alarm
setting.
LFLow Flow Alarm - Flow rate was at or below the minimum flow rate
established by Low Flow Limit program code for longer than 8
seconds.
LPLow Pressure - Pressure transducer is out of range of the low alarm
setting.
LTLow Temperature - Temperature probe or transducer is out of range of
the low alarm setting.
OAOverrun Alarm - Volume delivered has exceeded the preset amount by
at least the number of units set in the overrun limit program code.
UFUnauthorized Flow - The Fusion4 MSC-L has detected unauthorized
flow.
Fusion4Part No.: 4418305_Rev07
5 - 30Communication ManualHoneywell
FMC Smith AccuLoad Protocol
5.2.4.3 AV - Request Additive Volumes by Batch
This command retrieves additive batch volumes from the Fusion4
MSC-L.
Command
Current Transaction
AV_XXTotal additive of batch in progress (delivery type for flow
controlled additive)
AV_XX_ZTotal additive, by volume type, of batch in progress if that type
is available
AV_XX_YYTotal additive of a specified batch
AV_XX_YY_ZTotal additive of specified batch, specified volume type if
volume was stored
Local Storage Transaction
AV_XX_YY_NNNTotal additive of a specified batch in an historic transaction
AV_XX_YY_Z_NNNTotal additive, volume type, of specified batch in an historic
transaction for flow controlled additives
XX= Additive number (01...24)
YY= Batch number requested
Z=
NNN= Number of transactions back into local storage to retrieve the
G (GV Total)
=
N (GST Total)
=
M (Mass Total)
data
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 31
FMC Smith AccuLoad Protocol
Response
Current transaction
AV_XX_YY_VVVVV.VVVGood response. For AV_XX and AV_XX_YY
AV_XX_Z_VVVVV.VVVGood response for AV_XX_Z
AV_XX_YY_Z_VVVVV.VVVGood response for AV_XX_YY_Z
Local Storage Transaction
AV_XX_YY_VVVVV.VVV_NNNGood response for AV_XX_YY_NN
AV_XX_YY_Z_VVVVV.VVV_NNNGood response for AV_XX_YY_Z_NNN
XX= Additive number (01...24)
YY= Batch number requested
Z=
VVVVV.VVVTotal Additive Batch Volume
R for Raw or Indicated (IV) Total
G for Gross (GV) Total
=
N for Gross at Standard Temperature (GST) Total
=
M for Mass Total
=
NNNNumber of transactions back into local storage to retrieve the
data
or
NOXXAdditive batch volumes have not been retrieved.
XX= Two-digit error code as defined in section 5.1.1.4.
Remarks: If bays are configured, the AV for the current batch returns the current batch on
the arm addressed (or NO39 if no batch is in progress for the arm). For an AV
command for a completed batch, the batch argument specified in the batch is
the bay-based transaction, and hence may return a batch completed on an arm
that is not the arm being addressed.
Constraints: 1. The commands AV_XX_Z, AV_XX_YY_Z_NNN, and AV_XX_YY_Z will
work only when “Z” is “G for Gross (GV) Total”.
2. Volume units are assumed as the type programmed into the Fusion4
MSC-L. Volume types are available for flow controlled additives only.
Fusion4Part No.: 4418305_Rev07
5 - 32Communication ManualHoneywell
FMC Smith AccuLoad Protocol
Special Case: None
5.2.4.4 BA - Bay Assignment
This command retrieves the position of each arm in the bay.
Command
BA
Response
BA_A1A2A3A4A5A6Good response. The position of each arm in the bay was
An n is a character representing the position of arm n:
•A = Bay A
•B = Loading bay B
•? = In transit
or
retrieved.
NOXXThe position of each arm in the bay was not retrieved.
XX= Two-digit error code as defined in section 5.1.1.4.
Remarks: None
Constraints: None
Special Case: None
5.2.4.5 DY - Request Dynamic Display Values
This command retrieves a current dynamic display value from the
Fusion4 MSC-L.
Command
DY_ddxx
dd= Dynamic display type:
•SY = System
•P1 = Product #1
•P2 = Product #2
•P3 = Product #3
•P4 = Product #4
•P5 = Product #5
•P6 = Product #6
•Bz = batch, where ʺzʺ is 1…9 for batches 1...9, and ʺAʺ for
batch 10
•CB = current batch
xx= Variable number to access. See section 5.2.4.5.1 up to and
including section 5.2.4.5.5 for more information.
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 33
FMC Smith AccuLoad Protocol
Response
DY_V..V_D..DGood response
V..V= Value of the variable
D..D= Description of the variable (may contain spaces)
NOXXRequested display was not returned.
XX= Two-digit error code as defined in section 5.1.1.4.
Remarks: 1. No response exceeds 31 characters.
2. For bay configurations, the following information applies:
All additives on the bay can be accessed via any valid arm
address located on the bay.
Batch values are for the bay-based batch.
Not all transaction ʺDYʺ values are available when bays are
configured, i.e., average temperature, pressure, meter factor, etc.
Constraints: 1. NO06 will be returned if the requested batch has not been delivered (Bz
qualifier).
2. NO05 will be returned if there is no transaction in progress and no transaction has ever been done (TR qualifier).
3. NO30 will be returned if a product or recipe is requested which is not
currently allocated to the arm to which the command was directed.
4. NO31 will be returned if the command format does not match the current
configuration for the arm.
Special Case: None
5.2.4.5.1 DY_SYXX - System Dynamic Display Values
TABLE 5-24 gives an overview of the System dynamic display values.
TABLE 5-24System dynamic display values
Index Number (XX)DescriptionResponse
00Current Flow Rate Units/Min, Arm 1DY Flow (Arm 1)XXXXX.X Gal/Min
01Current Flow Rate Units/Min, Arm 2DY Flow (Arm 2)XXXXX.X Gal/Min
02Current Flow Rate Units/Min, Arm 3DY Flow (Arm 3)XXXXX.X Gal/Min
03Current Flow Rate Units/Min, Arm 4DY Flow (Arm 4)XXXXX.X Gal/Min
04Current Flow Rate Units/Min, Arm 5DY Flow (Arm 5)XXXXX.X Gal/Min
05Current Flow Rate Units/Min, Arm 6DY Flow (Arm 6)XXXXX.X Gal/Min
06Current Flow Rate Units/Hr, Arm 1DY Flow (Arm 1)XXXXXXX.X Gal/Hr
Fusion4Part No.: 4418305_Rev07
5 - 34Communication ManualHoneywell
FMC Smith AccuLoad Protocol
Index Number (XX)DescriptionResponse
07Current Flow Rate Units/Hr, Arm 2DY Flow (Arm 2)XXXXXXX.X Gal/Hr
08Current Flow Rate Units/Hr, Arm 3DY Flow (Arm 3)XXXXXXX.X Gal/Hr
09Current Flow Rate Units/Hr, Arm 4DY Flow (Arm 4)XXXXXXX.X Gal/Hr
10Current Flow Rate Units/Hr, Arm 5DY Flow (Arm 5)XXXXXXX.X Gal/Hr
11Current Flow Rate Units/Hr, Arm 6DY Flow (Arm 6)XXXXXXX.X Gal/Hr
12Current Recipe Name, Arm 1DY Recipe (Arm 1) XXXXXXXXX
13Current Recipe Name, Arm 2DY Recipe (Arm 2) XXXXXXXXX
14Current Recipe Name, Arm 3DY Recipe (Arm 3) XXXXXXXXX
15Current Recipe Name, Arm 4DY Recipe (Arm 4) XXXXXXXXX
16Current Recipe Name, Arm 5DY Recipe (Arm 5) XXXXXXXXX
17Current Recipe Name, Arm 6DY Recipe (Arm 6) XXXXXXXXX
18Current Preset, Arm 1DY Preset (Arm 1) XXXXXX Gal
19Current Preset, Arm 2DY Preset (Arm 2) XXXXXX Gal
20Current Preset, Arm 3DY Preset (Arm 3) XXXXXX Gal
21Current Preset, Arm 4DY Preset (Arm 4) XXXXXX Gal
22Current Preset, Arm 5DY Preset (Arm 5) XXXXXX Gal
23Current Preset, Arm 6DY Preset (Arm 6) XXXXXX Gal
24Current Delivered Volume, Arm 1DY Deliv. (Arm 1) XXXXXXX.XX Gal
25Current Delivered Volume, Arm 2DY Deliv. (Arm 2) XXXXXXX.XX Gal
26Current Delivered Volume, Arm 3DY Deliv. (Arm 3) XXXXXXX.XX Gal
27Current Delivered Volume, Arm 4DY Deliv. (Arm 4) XXXXXXX.XX Gal
28Current Delivered Volume, Arm 5DY Deliv. (Arm 5) XXXXXXX.XX Gal
29Current Delivered Volume, Arm 6DY Deliv. (Arm 6) XXXXXXX.XX Gal
30Current Remaining Volume, Arm 1DY Remain. (Arm 1) XXXXXXX.XX Gal
31Current Remaining Volume, Arm 2DY Remain. (Arm 2) XXXXXXX.XX Gal
32Current Remaining Volume, Arm 3DY Remain. (Arm 3) XXXXXXX.XX Gal
33Current Remaining Volume, Arm 4DY Remain. (Arm 4) XXXXXXX.XX Gal
34Current Remaining Volume, Arm 5DY Remain. (Arm 5) XXXXXXX.XX Gal
35Current Remaining Volume, Arm 6DY Remain. (Arm 6) XXXXXXX.XX Gal
Note: For Bz (= Batch, were z is 1 to 9 for batches 1 to 9, and A for batch 10), and CB (= Current batch) the variables
marked with
#
will respond NOXX as these are not used/accessible on the Fusion4 MSC-L.
5.2.4.6 Command Code EA - Enquire Alarms
This command requests the alarm status from the Fusion4 MSC-L
(short form).
Command
EA_DDRequest alarm status of directory.
DD= Directory specification:
•SY = System
•P1 = Product #1
•P2 = Product #2
•P3 = Product #3
•P4 = Product #4
•P5 = Product #5
•P6 = Product #6
•AR = Arm
•IN = Injector
•M1 = Meter
•M2 = Meter 2 (ratio, hybrid blending configuration only)
•M3 = Meter 3 (ratio, hybrid blending configuration only)
•M4 = Meter 4 (ratio, hybrid blending configuration only)
•M5 = Meter 5 (ratio, hybrid blending configuration only)
•M6 = Meter 6 (ratio, hybrid blending configuration only)
•RR = Recipe
Fusion4Part No.: 4418305_Rev07
5 - 40Communication ManualHoneywell
FMC Smith AccuLoad Protocol
Response
EA_SY_A1A2A3A4A5A6A8A9A10Good Response. Ten characters for System.
EA_Px_A1A2A3A4Good Response. Four characters for Products.
EA_AR_A1A2A3Good Response. Three characters for Arm.
EA_IN_A1A2A3 … A77Good Response. Seventy-seven characters for Additive
Injectors.
EA_Mx_A1A2A3Good Response. Three characters for Meter.
EA_RR_A1Good Response. One character for Recipe.
or
NOXXRequested display not returned
XX= Two-digit error code as defined in section 5.1.1.4.
Remarks: Allow for additional characters to be added to the end when alarms are added
in the future.
Constraints: 1. NO30 will be returned if the meter, product or additive specified is not
currently configured to the arm which the request was sent.
2. NO31 will be returned if the command format does not match the current
configuration for the arm.
Special Case: None
5.2.4.6.1 Response to EA_SY command: Characters A1 and A2
The system alarm requests associated with characters A1 and A2 are
not supported by the Fusion4 MSC-L due to differences in architecture
between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.2 Response to EA_SY command: Character A3
TABLE 5-29 describes character A3 in the response to an EA_SY
command.
TABLE 5-29Response to EA_SY command: Character A3
CharacterSystem Alarm Requests
CharHex
030
131N/A
Communication
(CM)
Power Failure
(PA)
Passcode
Reset (DA)
BSE Failure (DA)
232N/A
333N/AN/A
434X
535XN/A
636XN/A
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 41
FMC Smith AccuLoad Protocol
CharacterSystem Alarm Requests
CharHex
737XN/AN/A
838X
939XN/A
:3AXN/A
;3BXN/AN/A
<3CXX
=3DXXN/A
>3EXXN/A
?3FXXN/AN/A
Note: The system alarm requests highlighted in red are not supported by the Fusion4 MSC-L due to differences in
architecture between the Fusion4 MSC-L and the AccuLoad III.
Communication
(CM)
Power Failure
(PA)
Passcode
Reset (DA)
BSE Failure (DA)
5.2.4.6.3 Response to EA_SY command: Character A4
TABLE 5-30 describes character A4 in the response to an EA_SY
command.
TABLE 5-30Response to EA_SY command: Character A4
CharacterSystem Alarm Requests
CharHex
030
131N/A
232N/A
333N/AN/A
434N/A
535N/AN/A
636N/AN/A
737N/AN/AN/A
838X
939XN/A
User Alarm 1
(U1)
PTB Printer (PP)
Shared
Printer (SP)
CIVACON Comm
Failure (CV)
:3AXN/A
;3BXN/AN/A
<3CXN/A
=3DXN/AN/A
>3EXN/AN/A
Fusion4Part No.: 4418305_Rev07
5 - 42Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharacterSystem Alarm Requests
CharHex
?3FXN/AN/AN/A
Note: The system alarm requests highlighted in red are not supported by the Fusion4 MSC-L due to differences in
architecture between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.4 Response to EA_SY command: Character A5
User Alarm 1
(U1)
PTB Printer (PP)
Shared
Printer (SP)
CIVACON Comm
Failure (CV)
TABLE 5-31 describes character A5 in the response to an EA_SY
command.
TABLE 5-31Response to EA_SY: Character A5
CharacterSystem Alarm Requests
CharHex
030
User Alarm 5
(U5)
User Alarm 4
(U4)
User Alarm 3
(U3)
User Alarm 2
(U2)
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 43
FMC Smith AccuLoad Protocol
5.2.4.6.5 Response to EA_SY command: Character A6
TABLE 5-32 describes character A6 in the response to an EA_SY
command.
TABLE 5-32Response to EA_SY command: Character A6
CharacterSystem Alarm Requests
CharHex
030
131X
232N/A
333N/AX
434N/A
535N/AX
636N/AN/A
User Alarm 9
(U9)
User Alarm 8
(U8)
User Alarm 7
(U7)
User Alarm 6
(U6)
737N/AN/AX
838N/A
939N/AX
:3AN/AN/A
;3BN/AN/AX
<3CN/AN/A
=3DN/AN/AX
>3EN/AN/AN/A
?3FN/AN/AN/AX
Note: The system alarm requests highlighted in red are not supported by the Fusion4 MSC-L due to differences in
architecture between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.6 Response to EA_SY command: Characters A7 to A9
The system alarm requests associated with characters A7 to A9 are not
supported by the Fusion4 MSC-L due to differences in architecture
between the Fusion4 MSC-L and the AccuLoad III.
Fusion4Part No.: 4418305_Rev07
5 - 44Communication ManualHoneywell
FMC Smith AccuLoad Protocol
5.2.4.6.7 Response to EA_SY command: Character A10
TABLE 5-33 describes character A10 in the response to an EA_SY
command.
TABLE 5-33Response to EA_SY command: Character A10
CharacterSystem Alarm Requests
CharHexReservedReservedComFlash (CF)
030
131N/A
232N/A
333N/AN/A
434X
535XN/A
636XN/A
Data Retention
(DA)
737XN/AN/A
838X
939XN/A
:3AXN/A
;3BXN/AN/A
<3CXX
=3DXXN/A
>3EXXN/A
?3FXXN/AN/A
Note: The system alarm requests highlighted in red are not supported by the Fusion4 MSC-L due to differences in
architecture between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.8 Response to EA_Px command: Character A1
TABLE 5-34 describes character A1 in the response to an EA_Px
command.
TABLE 5-34Response to EA_Px command: Character A1
CharacterProduct Alarm Requests
CharHexHigh Flow (HF)
030
131N/A
232N/A
High Density
(HD)
Back
Pressure (BP)
Product Program
Error (DA)
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 45
FMC Smith AccuLoad Protocol
CharacterProduct Alarm Requests
CharHexHigh Flow (HF)
333N/AN/A
434X
535XN/A
636XN/A
737XN/AN/A
838X
939XN/A
:3AXN/A
;3BXN/AN/A
<3CXX
=3DXXN/A
>3EXXN/A
High Density
(HD)
Back
Pressure (BP)
Product Program
Error (DA)
?3FXXN/AN/A
Note: The product alarm requests highlighted in red are not supported by the Fusion4 MSC-L due to differences in
architecture between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.9 Response to EA_Px command: Character A2
TABLE 5-35 describes character A2 in the response to an EA_Px
command.
TABLE 5-35Response to EA_Px command: Character A2
CharacterProduct Alarm Requests
CharHexLow Flow (LF)Low Density (LD)
030
131X
232X
333XX
434X
535XX
High Temp
Alarm (HT)
High Pressure
(HP)
636XX
737XXX
838X
939XX
:3AXX
Fusion4Part No.: 4418305_Rev07
5 - 46Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharacterProduct Alarm Requests
CharHexLow Flow (LF)Low Density (LD)
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.10 Response to EA_Px command: Character A3
High Temp
Alarm (HT)
TABLE 5-36 describes character A3 in the response to an EA_Px
command.
TABLE 5-36Response to EA_Px command: Character A3
CharacterProduct Alarm Requests
CharHexOverrun (OA)Zero Flow (ZF)
030
Temperature (LT)
Low
High Pressure
(HP)
Low Pressure
(LP)
131X
232X
333XX
434N/A
535N/AX
636N/AX
737N/AXX
838X
939XX
:3AXX
;3BXXX
<3CXN/A
=3DXN/AX
>3EXN/AX
?3FXN/AXX
Note: The product alarm requests highlighted in red are not supported by the Fusion4 MSC-L due to differences in
architecture between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.11 Response to EA_Px command: Character A4
TABLE 5-37 describes character A4 in the response to an EA_Px
command.
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 47
FMC Smith AccuLoad Protocol
TABLE 5-37Response to EA_Px command: Character A4
CharacterProduct Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838N/A
939N/AX
Product Stop
(PA)
Blend Low (BL)Blend High (BH)Block Valve (BV)
:3AN/AX
;3BN/AXX
<3CN/AX
=3DN/AXX
>3EN/AXX
?3FN/AXXX
Note: The product alarm requests highlighted in red are not supported by the Fusion4 MSC-L due to differences in
architecture between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.12 Response to EA_AR command: Character A1
TABLE 5-38 describes character A1 in the response to an EA_AR
command.
TABLE 5-38Response to EA_AR command: Character A1
CharacterArm Alarm Requests
CharHexTicket (TK)Overrun (OA)Zero Flow (ZF)
030
Arm Program
Error (DA)
131N/A
232N/A
333N/AN/A
434X
535XN/A
Fusion4Part No.: 4418305_Rev07
5 - 48Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharacterArm Alarm Requests
CharHexTicket (TK)Overrun (OA)Zero Flow (ZF)
636XN/A
737XN/AN/A
838N/A
939N/AN/A
:3AN/AN/A
;3BN/AN/AN/A
<3CN/AX
=3DN/AXN/A
>3EN/AXN/A
?3FN/AXN/AN/A
Note: The arm alarm requests highlighted in red are not supported by the Fusion4 MSC-L due to differences in
architecture between the Fusion4 MSC-L and the AccuLoad III.
Arm Program
Error (DA)
5.2.4.6.13 Response to EA_AR command: Character A2
TABLE 5-39 describes character A2 in the response to an EA_AR
command.
TABLE 5-39Response to EA_AR command: Character A2
CharacterArm Alarm Requests
Arm Recipe
CharHexStorage Full (SF)
Program Error
(DA)
030
131X
232X
333XX
434N/A
535N/AX
636N/AX
737N/AXX
838N/A
Additive Clean
Line (CA)
Clean Line (CL)
939N/AX
:3AN/AX
;3BN/AXX
<3CN/AN/A
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 49
FMC Smith AccuLoad Protocol
CharacterArm Alarm Requests
Arm Recipe
CharHexStorage Full (SF)
Program Error
(DA)
=3DN/AN/AX
>3EN/AN/AX
?3FN/AN/AXX
Note: The arm alarm requests highlighted in red are not supported by the Fusion4 MSC-L due to differences in
architecture between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.14 Response to EA_AR command: Character A3
Additive Clean
Line (CA)
Clean Line (CL)
TABLE 5-40 describes character A3 in the response to an EA_AR
command.
TABLE 5-40Response to EA_AR command: Character A3
CharacterArm Alarm Requests
CharHexReservedReserved
030
131N/A
232N/A
333N/AN/A
434X
535XN/A
636XN/A
737XN/AN/A
838X
939XN/A
:3AXN/A
;3BXN/AN/A
<3CXX
=3DXXN/A
>3EXXN/A
Card
Removed (CD)
DE Head
Alarm (DE)
?3FXXN/AN/A
Note: The arm alarm requests highlighted in red are not supported by the Fusion4 MSC-L due to differences in
architecture between the Fusion4 MSC-L and the AccuLoad III.
Fusion4Part No.: 4418305_Rev07
5 - 50Communication ManualHoneywell
FMC Smith AccuLoad Protocol
5.2.4.6.15 Response to EA_IN command: Characters A1 to A12
The injector alarm requests associated with characters A1 to A12 are
not supported by the Fusion4 MSC-L due to differences in architecture
between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.16 Response to EA_IN command: Character A13
TABLE 5-41 describes character A13 in the response to an EA_IN
command.
TABLE 5-41Response to EA_IN command: Character A13
CharacterInjector Alarm Requests
CharHex
030
131X
232X
Injector 4 Low
Add Error (KA)
Injector 3 Low
Add Error (KA)
Injector 2 Low
Add Error (KA)
Injector 1 Low
Add Error (KA)
333XX
434X
535XX
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 51
FMC Smith AccuLoad Protocol
5.2.4.6.17 Response to EA_IN command: Character A14
TABLE 5-42 describes character A14 in the response to an EA_IN
command.
TABLE 5-42Response to EA_IN command: Character A14
CharacterInjector Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
Injector 8 Low
Add Error (KA)
Injector 7 Low
Add Error (KA)
Injector 6 Low
Add Error (KA)
Injector 5 Low
Add Error (KA)
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.18 Response to EA_IN command: Character A15
TABLE 5-43 describes character A15 in the response to an EA_IN
command.
TABLE 5-43Response to EA_IN command: Character A15
CharacterInjector Alarm Requests
CharHex
030
Injector 12 Low
Add Error (KA)
Injector 11 Low
Add Error (KA)
Injector 10 Low
Add Error (KA)
Injector 9 Low
Add Error (KA)
131X
232X
333XX
434X
535XX
Fusion4Part No.: 4418305_Rev07
5 - 52Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharacterInjector Alarm Requests
CharHex
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.19 Response to EA_IN command: Character A16
Injector 12 Low
Add Error (KA)
Injector 11 Low
Add Error (KA)
Injector 10 Low
Add Error (KA)
Injector 9 Low
Add Error (KA)
TABLE 5-44 describes character A16 in the response to an EA_IN
command.
TABLE 5-44Response to EA_IN command: Character A16
CharacterInjector Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
:3AXX
Injector 4 Low
Add Error (KA)
Injector 3 Low
Add Error (KA)
Injector 2 Low
Add Error (KA)
Injector 1 Low
Add Error (KA)
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 53
FMC Smith AccuLoad Protocol
5.2.4.6.20 Response to EA_IN command: Character A17
TABLE 5-45 describes character A17 in the response to an EA_IN
command.
TABLE 5-45Response to EA_IN command: Character A17
CharacterInjector Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
Injector 20 Low
Add Error (KA)
Injector 19 Low
Add Error (KA)
Injector 18 Low
Add Error (KA)
Injector 17 Low
Add Error (KA)
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.21 Response to EA_IN command: Character A18
TABLE 5-46 describes character A18 in the response to an EA_IN
command.
TABLE 5-46EA_IN command: Character A18
CharacterInjector Alarm Requests
CharHex
030
Injector 24 Low
Add Error (KA)
Injector 23 Low
Add Error (KA)
Injector 22 Low
Add Error (KA)
Injector 21 Low
Add Error (KA)
131X
232X
333XX
434X
535XX
Fusion4Part No.: 4418305_Rev07
5 - 54Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharacterInjector Alarm Requests
CharHex
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.22 Response to EA_IN command: Characters A19 to A24
Injector 24 Low
Add Error (KA)
Injector 23 Low
Add Error (KA)
Injector 22 Low
Add Error (KA)
Injector 21 Low
Add Error (KA)
The injector alarm requests associated with characters A19 to A24 are
not supported by the Fusion4 MSC-L due to differences in architecture
between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.23 Response to EA_IN command: Character A25
TABLE 5-47 describes character A25 in the response to an EA_IN
command.
TABLE 5-47Response to EA_IN command: Character A25
CharacterInjector Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
Injector 4 No
Pulses (NA)
Injector 3 No
Pulses (NA)
Injector 2 No
Pulses (NA)
Injector 1 No
Pulses (NA)
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 55
FMC Smith AccuLoad Protocol
CharacterInjector Alarm Requests
CharHex
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.24 Response to EA_IN command: Character A26
Injector 4 No
Pulses (NA)
Injector 3 No
Pulses (NA)
Injector 2 No
Pulses (NA)
TABLE 5-48 describes character A26 in the response to an EA_IN
command.
TABLE 5-48Response to EA_IN command: Character A26
CharacterInjector Alarm Requests
CharHex
030
Injector 8 No
Pulses (NA)
Injector 7 No
Pulses (NA)
Injector 6 No
Pulses (NA)
Injector 1 No
Pulses (NA)
Injector 5 No
Pulses (NA)
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
Fusion4Part No.: 4418305_Rev07
5 - 56Communication ManualHoneywell
FMC Smith AccuLoad Protocol
5.2.4.6.25 Response to EA_IN command: Character A27
TABLE 5-49 describes character A27 in the response to an EA_IN
command.
TABLE 5-49Response to EA_IN command: Character A27
CharacterInjector Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
Injector 12 No
Pulses (NA)
Injector 11 No
Pulses (NA)
Injector 10 No
Pulses (NA)
Injector 9 No
Pulses (NA)
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.26 Response to EA_IN command: Character A28
TABLE 5-50 describes character A28 in the response to an EA_IN
command.
TABLE 5-50Response to EA_IN command: Character A28
CharacterInjector Alarm Requests
CharHex
030
Injector 16 No
Pulses (NA)
Injector 15 No
Pulses (NA)
Injector 14 No
Pulses (NA)
Injector 13 No
Pulses (NA)
131X
232X
333XX
434X
535XX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 57
FMC Smith AccuLoad Protocol
CharacterInjector Alarm Requests
CharHex
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.27 Response to EA_IN command: Character A29
Injector 16 No
Pulses (NA)
Injector 15 No
Pulses (NA)
Injector 14 No
Pulses (NA)
Injector 13 No
Pulses (NA)
TABLE 5-51 describes character A29 in the response to an EA_IN
command.
TABLE 5-51Response to EA_IN command: Character A29
CharacterInjector Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
:3AXX
Injector 20 No
Pulses (NA)
Injector 19 No
Pulses (NA)
Injector 18 No
Pulses (NA)
Injector 17 No
Pulses (NA)
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
Fusion4Part No.: 4418305_Rev07
5 - 58Communication ManualHoneywell
FMC Smith AccuLoad Protocol
5.2.4.6.28 Response to EA_IN command: Character A30
TABLE 5-52 describes character A30 in the response to an EA_IN
command.
TABLE 5-52Response to EA_IN command: Character A30
CharacterInjector Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
Injector 24 No
Pulses (NA)
Injector 23 No
Pulses (NA)
Injector 22 No
Pulses (NA)
Injector 21 No
Pulses (NA)
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.29 Response to EA_IN command: Characters A31 to A42
The injector alarm requests associated with characters A31 to A42 are
not supported by the Fusion4 MSC-L due to differences in architecture
between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.30 Response to EA_IN command: Character A43
TABLE 5-53 describes character A43 in the response to an EA_IN
command.
TABLE 5-53Response to EA_IN command: Character A43
CharacterInjector Alarm Requests
CharHex
030
Injector 4
General Additive
Error (GA)
Injector 3
General Additive
Error (GA)
Injector 2
General Additive
Error (GA)
Injector 1
General Additive
Error (GA)
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 59
FMC Smith AccuLoad Protocol
CharacterInjector Alarm Requests
Injector 4
CharHex
General Additive
Error (GA)
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
Injector 3
General Additive
Error (GA)
Injector 2
General Additive
Error (GA)
General Additive
Error (GA)
Injector 1
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.31 Response to EA_IN command: Character A44
TABLE 5-54 describes character A44 in the response to an EA_IN
command.
TABLE 5-54Response to EA_IN command: Character A44
CharacterInjector Alarm Requests
Injector 8
CharHex
General Additive
Error (GA)
030
131X
232X
333XX
434X
Injector 7
General Additive
Error (GA)
Injector 6
General Additive
Error (GA)
Injector 5
General Additive
Error (GA)
535XX
636XX
737XXX
838X
939XX
Fusion4Part No.: 4418305_Rev07
5 - 60Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharacterInjector Alarm Requests
Injector 8
CharHex
General Additive
Error (GA)
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.32 Response to EA_IN command: Character A45
Injector 7
General Additive
Error (GA)
Injector 6
General Additive
Error (GA)
TABLE 5-55 describes character A45 in the response to an EA_IN
command.
TABLE 5-55Response to EA_IN command: Character A45
Injector 5
General Additive
Error (GA)
CharacterInjector Alarm Requests
Injector 12
CharHex
General Additive
Error (GA)
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
Injector 11
General Additive
Error (GA)
Injector 10
General Additive
Error (GA)
General Additive
Error (GA)
Injector 9
>3EXXX
?3FXXXX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 61
FMC Smith AccuLoad Protocol
5.2.4.6.33 Response to EA_IN command: Character A46
TABLE 5-56 describes character A46 in the response to an EA_IN
command.
TABLE 5-56EA_IN command: Character A46
CharacterInjector Alarm Requests
Injector 16
CharHex
General Additive
Error (GA)
030
131X
232X
333XX
434X
535XX
Injector 15
General Additive
Error (GA)
Injector 14
General Additive
Error (GA)
Injector 13
General Additive
Error (GA)
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.34 Response to EA_IN command: Character A47
TABLE 5-57 describes character A47 in the response to an EA_IN
command.
TABLE 5-57Response to EA_IN command: Character A47
CharacterInjector Alarm Requests
CharHex
030
Injector 20
General Additive
Error (GA)
Injector 19
General Additive
Error (GA)
Injector 18
General Additive
Error (GA)
Injector 19
General Additive
Error (GA)
131X
232X
333XX
Fusion4Part No.: 4418305_Rev07
5 - 62Communication ManualHoneywell
FMC Smith AccuLoad Protocol
CharacterInjector Alarm Requests
Injector 20
CharHex
General Additive
Error (GA)
434X
535XX
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
Injector 19
General Additive
Error (GA)
Injector 18
General Additive
Error (GA)
Injector 19
General Additive
Error (GA)
?3FXXXX
5.2.4.6.35 Response to EA_IN command: Character A48
TABLE 5-58 describes character A48 in the response to an EA_IN
command.
TABLE 5-58Response to EA_IN command: Character A48
CharacterInjector Alarm Requests
Injector 24
CharHex
General Additive
Error (GA)
030
131X
232X
333XX
434X
535XX
636XX
737XXX
Injector 23
General Additive
Error (GA)
Injector 22
General Additive
Error (GA)
Injector 21
General Additive
Error (GA)
838X
939XX
:3AXX
;3BXXX
<3CXX
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 63
FMC Smith AccuLoad Protocol
CharacterInjector Alarm Requests
Injector 24
CharHex
General Additive
Error (GA)
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.36 Response to EA_IN command: Characters A49 to A66
Injector 23
General Additive
Error (GA)
Injector 22
General Additive
Error (GA)
Injector 21
General Additive
Error (GA)
The injector alarm requests associated with characters A49 to A66 are
not supported by the Fusion4 MSC-L due to differences in architecture
between the Fusion4 MSC-L and the AccuLoad III.
5.2.4.6.37 Response to EA_IN command: Character A67
TABLE 5-59 describes character A67 in the response to an EA_IN
command.
TABLE 5-59Response to EA_IN command: Character A67
CharacterInjector Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
Injector 4 High
Temp (AH)
Injector 3 High
Temp (AH)
Injector 2 High
Temp (AH)
Injector 1 High
Temp (AH)
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.38 Response to EA_IN command: Character A68
TABLE 5-60 describes character A68 in the response to an EA_IN
command.
Fusion4Part No.: 4418305_Rev07
5 - 64Communication ManualHoneywell
FMC Smith AccuLoad Protocol
TABLE 5-60Response to EA_IN command: Character A68
CharacterInjector Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
Injector 4 Low
Temp (AL)
Injector 3 Low
Temp (AL)
Injector 2 Low
Temp (AL)
Injector 1 Low
Temp (AL)
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.39 Response to EA_IN command: Character A69
TABLE 5-61 describes character A69 in the response to an EA_IN
command.
TABLE 5-61Response to EA_IN command: Character A69
CharacterInjector Alarm Requests
CharHex
030
131X
232X
Injector 4 Temp.
Probe (AT)
Injector 3 Temp.
Probe (AT)
Injector 2 Temp.
Probe (AT)
Injector 1 Temp.
Probe (AT)
333XX
434X
535XX
636XX
737XXX
838X
Part No.: 4418305_Rev07Fusion4
HoneywellCommunication Manual5 - 65
FMC Smith AccuLoad Protocol
CharacterInjector Alarm Requests
CharHex
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
?3FXXXX
5.2.4.6.40 Response to EA_IN command: Character A70
Injector 4 Temp.
Probe (AT)
Injector 3 Temp.
Probe (AT)
Injector 2 Temp.
Probe (AT)
TABLE 5-62 describes character A70 in the response to an EA_IN
command.
TABLE 5-62Response EA_IN command: Character A70
Injector 1 Temp.
Probe (AT)
CharacterInjector Alarm Requests
CharHex
030
131X
232X
333XX
434X
535XX
636XX
737XXX
838X
939XX
:3AXX
;3BXXX
<3CXX
=3DXXX
>3EXXX
Injector 4 Pulse
Security (PS)
Injector 3 Pulse
Security (PS)
Injector 2 Pulse
Security (PS)
Injector 1 Pulse
Security (PS)
?3FXXXX
5.2.4.6.41 Response to EA_IN command: Character A71 to A77
The injector alarm requests associated with characters A71 to A77 are
not supported by the Fusion4 MSC-L due to differences in architecture
between the Fusion4 MSC-L and the AccuLoad III.
Fusion4Part No.: 4418305_Rev07
5 - 66Communication ManualHoneywell
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.