Azbil AUR355 Use and care manual

Thank you for purchasing this product.
This manual contains information for
ensuring the safe and correct use of
the product.
Those designing or maintaining
equipment that uses this product
should first read and understand
this manual. This user’s manual
contains information not only for
installation, but also for maintenance,
troubleshooting, etc. Be sure to keep it
nearby for handy reference.
(Not for use in Japan)
Flame Monitor
Model AUR355
User's Manual for
Communication Functions
No. CP-SP-1453E

NOTICE
Please make sure that this manual is available to the user of the product.
Unauthorized duplication of this user’s manual in part or in whole is
forbidden. The information and specifications in this manual are subject to
change without notice.
Considerable effort has been made to ensure that this manual is complete
and accurate, but if you should find an omission or error, please contact us.
In no event is Azbil Corporation liable to anyone for any indirect, special, or
consequential damages as a result of using this product.
© 2020-2021 Azbil Corporation. All Rights Reserved.

i
Conventions Used in This Manual
The safety precautions explained below aim to prevent injury to you and others, and to prevent property damage.
WARNING Warnings are indicated when mishandling this product may
result in death or serious injury.
CAUTION Cautions are indicated when mishandling this product may
result in minor injury or property damage only.
In describing the product, this manual uses the icons and wording listed below.
Indicates that caution is required in handling.
The indicated action is prohibited.
Be sure to follow the indicated instructions.
Handling Precautions:
Information to be aware of when handling.
Note: Indicates information that may be useful.
: Indicates an item or page to which the user may refer.
(1) (2) (3): Steps in a sequence or parts of a figure, etc.

ii
Safety Precautions
WARNING
Before mounting, removing, or wiring, be sure to turn off the power to this device and all
connected devices. Failure to do so may result in an electric shock.
Do not use communication output for control. The communication output of this device is for
monitoring the status of equipment and combustion.
CAUTION
Be sure to check that this device has been correctly wired before turning on the power.
Incorrect wiring of the device may damage it or lead to hazardous conditions.
Do not attempt to write to a write-protected address or an address that is not described in this
manual. Doing so may cause a malfunction of communication or display.

iii
Conventions Used in This Manual
Safety Precautions
Chapter 1. Overview 1
1 - 1 Overview 1
 Features 1
 Communication functions 1
Chapter 2. Wiring 3
 RS-485 communication 3
 Loader communication 5
Chapter 3. Communication Settings 6
 Device address 6
 Transmission speed 6
 Data format 6
Chapter 4. Communication 7
4 - 1 Overview of Communication 7
 Communication procedure 7
 Message structure 7
 Data link layer 7
 Application layer 10
4 - 2 Numerical Representation in the Application Layer 11
 RS, WS commands 11
 RD, WD, RU, WU commands 11
4 - 3 List of End Codes 12
 End codes for the read command 12
 End codes for the write command 12
4 - 4 Timing Specifications 13
 Timing specifications for command and response messages 13
4 - 5 Description of Commands 14
 Consecutive data read command (RS command) 14
 Continuous data write command (WS command) 16
 Fixed length consecutive data read command (RD command) 18
 Fixed length continuous data write command (WD command) 20
 Fixed length random data read command (RU command) 22
 Fixed length random data write command (WU command) 23
Contents

iv
Chapter 5. Communication Data 25
 Communication data table 25
Chapter 6. Details of Functions via Communication 35
6 - 1 Monitoring Function 35
 Alarm index/code table 35
 Operating status No. table 36
 Event code table 36
6 - 2 Event Function 37
 Event items 37
 To use events 38
 Writing 2-word event settings 38
 Writing event-related items to EEPROM 39
 Details of event items 40
 Clearing events 42
6 - 3 Data Initialization 43
6 - 4 Playback Monitor 44
 Playback triggers 44
 Playback monitor header information 44
 Playback monitor recorded information 44
 To read playback monitor data 45
6 - 5 Flame Logger 47
 Trigger 47
 Recorded information 47
 To read recorded information 47
Chapter 7. Troubleshooting 48
 What to check if communication fails 48
Chapter 8. Specifications 49
 RS-485 specifications 49

1
Chapter 1. Overview
1 - 1 Overview
This flame monitor, model AUR355 (hereinafter also “this device”), has RS-485 communication functions and can
communicate with a PC, PLC, or other host device using a user-configured program.
The communication protocol is CPL.*
For example, if the host device is a PC, it is possible to use CPL to monitor the operating status of this device or to
delete data via the RS-232C port or RS-485.
*CPL (Controller Peripheral Link) is Azbil’s host communication protocol.
 Features
The features of this device’s communication function are as follows:
• Up to 32 modules can be connected to a single master station acting as a host
device.
• The separately sold Smart Device Gateway, model NX-SVG, is required for
communication with the host device.
• Transmission speeds can be up to 19200 bps.
• Besides continuous access commands, random access commands are available.
Reading or writing to noncontiguous addresses is supported.
 Communication functions
This device has two communication ports.
One is for host communication (RS-485), and the other is for loader
communication (limited to use with the SLP-A55 loader).
Host communication is through the front connector on the front of this device, and
loader communication is through the loader jack on the front of this device.
Host communication can be used for hard-wired communication between devices
within the equipment and for monitoring the status of multiple AUR355 units.
On the other hand, loader communication is for connection to the SLP-A55 (a PC-
based software tool) and uses a special cable.
Loader communication is useful for data analysis in the field. For example, it can be
used when doing equipment maintenance.
For loader communication, refer to CP-UM-5956JE.
The purpose of the present manual is to explain host communication.
Using the RS-485 protocol, up to 32 devices (slave stations) can be connected to a
host device (master station). Also, device addresses are used to communicate with
specific slave stations.
With RS-485, using a procedure like the following, various kinds of data can be read
from a device, and error history and number of errors can be cleared.
1. The master station transmits command messages to the slave stations.
2. The master station receives response messages from the slave stations.
• The master station sends read or write commands.
• You can freely select the type of data to read or write by using data addresses.

2
Chapter 1. Overview
Examples:
z When connected to the NX-SVG
Host device
NX-SVG
AUR355
Ethernet
RS-485
AUR355 AUR355 AUR355

3
Chapter 2. Wiring
 RS-485 communication
The RS-485 cable for this device consists of three wires.
Connect the cable as shown below using the front wiring connector for this device
(sold separately).
Handling Precautions
• Attach terminating resistors (½ W or more, 150 Ω ±5 %) at each end of the
communications lines.
However, if a device that does not allow a terminating resistor is connected to
the same communications line, follow the specifications for that device.
• Be sure to connect the signal ground (SG) terminals to each other. Otherwise,
communication may be unreliable.
• Use twisted-pair cable for communication wiring.
27
28
25
26
29
30
31
35
•
•
•
•
•
DA
DB
SG
RS-485
Connector for front wiring
(sold separately)
81447514-001
Connector for front wiring
(sold separately)

4
Chapter 2. Wiring
z If the system includes 5-wire devices
SDA
SDB
RDA
RDB
SG
Shield
SG
Shield
Shield
Host device (master station)
Terminating resistor
SDA
SDB
RDA
RDB
SG
RDA
RDB
SDA
SDB
SG
FG
DA
DB
Terminating resistor
This device or
3-wire device (slave station)
5-wire device (slave station)
5-wire device (slave station)
FG
FG

5
Chapter 2. Wiring
z If the system includes 3-wire devices only
Shield
Shield
Shield
Host device (master station)
Terminating resistor
SG
DA
DB
Terminating resistor
SG
DA
DB
SG
DA
DB
SG
DA
DB
This device or 3-wire device
(slave station)
This device or 3-wire device
(slave station)
This device or 3-wire device
(slave station)
 Loader communication
To use the Smart Loader Package (SLP), connect the special cable between the
loader jack of this device and the PC running the SLP.

6
Chapter 3. Communication Settings
For communications with this device, the following settings must be configured.
1. Device address
2. Transmission speed
3. Data format
Each setting is explained below.
Each setting can be configured either in the setting mode of this device or with the Smart Loader Package.
Note
• For details about each setting, refer to Installation and Usage Guide for Smart
Loader Package Model SLP-A55 for Burner Controller Model AUR_55, Document
No. CP-UM-5956JE.
Handling Precautions
• After setting the device address, transmission speed, and data format, it is
necessary to briefly turn off the power to this device and then turn it back on
again.
When the power is turned on, the new device address, transmission speed,
and data format settings will take effect.
 Device address
The setting range is from 1 to 32.
Make sure that there are no duplicate device addresses on the same transmission
line.
The default setting is 1.
 Transmission speed
The speed can be selected from 4800, 9600, and 19200 bps.
The preset speed is 19200 bps.
 Data format
The format can be selected from:
8 bits, even parity, 1 stop bit
8 bits, even parity, 2 stop bits
8 bits, odd parity, 1 stop bit
8 bits, odd parity, 2 stop bits
The preset format is 8 bits, even parity, 1 stop bit.

7
Chapter 4. Communication
4 - 1 Overview of Communication
 Communication procedure
The simplest way to describe the communication procedure is as follows.
1. The master station sends a command message to the specified slave station.
2. The slave station processes the message, which is a command to read or write data.
3. Additionally, the slave station sends a response message whose contents
correspond to the type of processing.
4. The master station receives and processes the response.
 Message structure
The following shows the message structure.
Messages are broadly classified into two layers: the data link layer and the
application layer.
• Data link layer
This layer contains the basic information required for communication. For
example, it has the destination of the command message and the checksum
information.
• Application layer
Data is read and written in this layer. The content of the layer varies according to
the purpose of the message.
Messages include parts 1 to 9 in the figure below.
The command in a command message from the master station and the response in
a response message from the slave station are stored in the application layer.
 Data link layer
z Overview
The data link layer has a fixed length. The relative position of each item of data
and its length are prescribed. Note, however, that the position of data in the data
link layer from ETX onwards shifts according to the number of characters in the
application layer. The length of the data link layer text remains unchanged.
02H 58H30H30H 0DH03H
STX X00 ETX
0AH
CR LF
Data link layer Application layer Data link layer
1 frame
STX (start of message)
Device address
Subaddress (xed at “00”)
Device code
In command message = the command, in response message = the response
ETX (end of command or response)
Checksum
CR (delimiter)
LF (delimiter)
1 2 3 4 5 6 7 8 9
1
2
3
4
5
6
7
8
9

8
Chapter 4. Communication
z Response start conditions
The slave station sends a response message only if all the message components
(device address, subaddress, and checksum) in the data link layer are correct. If
even one of these is incorrect, no response message is sent, and the slave device
stands by to receive STX.
If the message exceeds the allowed length (160 bytes), no response message is sent,
and the slave station waits for a new message.
z List of data link layer data definitions
The following table describes the data in the data link layer.
Data name Character code Bytes Meaning
STX 02H 1 Start of message
Device address Hexadecimal 2 The device to communicate with
Subaddress Hexadecimal 2 Always 00
Device distinction code “X” (58H) or “x” (78H) 1 Type of device
ETX 03H 1 End of application layer
Checksum 2 hexadecimal digits
from 00H to FFH
2 Checksum of message
CR 0DH 1 End of message marker (part 1)
LF 0AH 1 End of message marker (part 2)
z Description of data
z STX (02H)
When STX is received, this device interprets it as the start of a transmitted message.
It follows that, no matter what has been received previously, upon receiving STX the
device begins processing a new message. The purpose of this is to enable recovery
of the device’s responsiveness when the next message (for example, a RETRY
message) comes from the master station in the event that electromagnetic noise, for
example, caused an error in the command message.
z Device address
The slave station only creates response messages to messages that contain its device
address. Device addresses in the messages are expressed as two-digit hexadecimal
characters.
The setting range for the device address is 1–32.
When the slave station responds, it adds its device address to the response message.
z Subaddress
The AUR355 does not use subaddresses. For this reason, set the subaddress to “00”
(30H 30H). When the slave station responds, it adds the subaddress to the response
message.
z Device distinction code
Either X (58H) or x (78H) can be used. This code is determined for each device
series, and other characters cannot be used. The slave station adds the same device

9
Chapter 4. Communication
distinction code as that of the received message to the response message and
returns it. It is convenient to use X (58H) in messages the first time and use x (78H)
for resent messages in order to distinguish them.
z ETX
ETX indicates the end of the application layer.
z Checksum
This value is for checking whether something abnormal (e.g., electromagnetic
noise) has caused the message content to change during transmission. The
checksum is expressed as two hexadecimal characters.
• How to create a checksum
(1) Add up the hex codes from STX to ETX in increments of 1 byte.
(2) Take the two’s complement of the addition result.
(3) Convert it to character codes.
Example:
The example below is based on a message that includes the following elements.
Device address : 10 (0AH)
Subaddress : 00 (fixed)
Device distinction code : X (58H)
1. Add the character codes byte by byte in the message from STX through ETX.
The lowest order byte of the sum is 76H.
2. Take the two’s complement of the sum.
The result is 8AH (8A (hex)).
3. Convert the characters of the result to character codes. Use this as a checksum.
The characters “8A” are converted to their character codes 38H and 41H.
z CR/LF
This indicates the end of the message. Immediately after LF is received, the device is
ready to receive and process another message.
02H 58H30H30H 0DH30H 30H 41H 30H31H2CH
52H 53H 03H
32H2CH57H
31H 41H
38H 0AH
STX X00 CR0 0 A 01,
R S ETX
2,W
1A
8LF

10
Chapter 4. Communication
 Application layer
z Configuration of application layer
The table below shows the configuration of the application layer.
Item Description
Command RS (decimal format continuous address data read command)
WS (decimal format continuous address data write command)
RD (hex format continuous address data read command)
WD (hex format continuous address data write command)
RU (hex format random address data read command)
WU (hex format random address data write command)
Data delimiter RS, WS : “,” (comma)
RD, WD, RU, WU : (none)
Word address RS, WS : “501 W,” etc.
RD, WD, RU, WU : “01F5,” etc.
Read count A number expressed as a character (e.g., “1”)
Number to write RS, WS : Expressed in characters, like“100”
RD, WD, RU, WU : A hexadecimal expression like “0064”
z Number of data words accessible by a single frame
Type Description of commands Data count
RS Read command in decimal format 16 words
WS Write command in decimal format 16 words
RD Read command in hexadecimal format 16 words
WD Write command in hexadecimal format 16 words
RU Random read command in hexadecimal format 16 words
WU Random write command in hexadecimal format 16 words

11
Chapter 4. Communication
Each numerical value must be expressed with unnecessary zeros suppressed.
The following shows the specifications, including a case where zero is not suppressed. All master station command
messages must be sent with unnecessary zeros suppressed.
 RS, WS commands
Item Specification Error Handling
Unnecessary spaces Cannot be appended. An error end code
is returned in the
response message.
Numerical value = zero Cannot be omitted.
“0” must be used.
Other unnecessary
characters
To represent a negative number,
add “−”to the beginning of the
number.
Other characters cannot be
appended.
For positive numbers, “+” must not
be added.
Range of available
numerical values
−32768 to +32767
This range must not be exceeded.
 RD, WD, RU, WU commands
Item Specification Error Handling
Unnecessary spaces Cannot be appended. An error end code
is returned in the
response message.
Numerical value = zero Cannot be omitted.
“0000” must be used.
Other unnecessary
characters
Cannot be appended.
Range of available
numerical values
0000H–FFFFH
4 - 2 Numerical Representation in the Application Layer

12
Chapter 4. Communication
The result of the application layer processing of the command message can be understood from the end code of the
response message.
Results other than “Normal” are on two levels. “Error” is returned when nothing is processed, and “Warning” is
returned when there is a possibility that some kind of processing was done.
 End codes for the read command
End code Description Operation
00 (Normal) Normal end The value that was read is returned.
99 (Error) Undefined command Only the end code is returned (no data is
appended).
40 (Error) Error in the number of
data words
Only the end code is returned (no data is
appended).
41 (Error) Data address error Only the end code is returned (no data is
appended).
 End codes for the write command
End code Description Operation
00 (Normal) Normal end All data was written.
99 (Error) Undefined command No data was written.
40 (Error) Error in the number of
data words
No data was written.
41 (Error) Data address error No data was written.
42 (Error) Data range error No data was written.
43 (Error) Could not write No data was written.
20 (Warning) Error in the number of
data words
Data was written to the accessible data
addresses.
21 (Warning) Data address error Data was written to the accessible data
addresses.
22 (Warning) Data range error Valid data was written.
23 (Warning) Could not write No data was written to read-only data
addresses. If there was data for accessible
data addresses, it was written.
• In the case of a command to write multiple data words, if multiple warnings are
generated, the last warning code is returned.
• In the case of a command to write multiple data words, if multiple warnings are
generated, and all the command messages eventually result in warnings, the error
code corresponding to the last warning code is returned instead of the warning
code.
Ex.) If multiple warnings occur and all the command messages eventually result
in warnings
If the last warning code generated was “21” (data address error), the error
code “41” (data address error) is returned as the end code.
4 - 3 List of End Codes

13
Chapter 4. Communication
 Timing specifications for command and response messages
When the master and slave stations are connected directly with RS-485, the
following points regarding the timing of command/response messages from the
master/slave stations must be observed.
z Response monitoring time
The maximum response time from the end of command message transmission by
the master station to the start of response message reception from the slave station
is 2 seconds (#1 in the figure below).
Therefore, the response monitor time should be set to 2 seconds.
If a response time-out occurs, the command message should be resent.
z Transmission start time
After the master station finishes receiving a response message (#2 in the figure
below), a wait time of 10 ms is required before it begins to transmit a command
message (to the same or a different slave station).
RS-485 driver control timing specifications
When the transmission/reception on a 3-wire RS-485 system is directly controlled
by the master station, care should be paid to the timing shown below.
Command
message
Transmission
line
RS-485 3-wire system
Command
message
Response
message
(1) End of master station transmission − Start of slave station transmission = 2000 ms max.
(2) End of slave station transmission − Start of master station transmission = 10 ms min.
Response
message
(1) (2)
(enable)
(enable)
(disable)
(disable)
Master station
driver control
Slave station
driver control
Transmission
line
(command message)
Valid
data
Valid
data
(1) End of master station transmission − Master station driver disabled time = 500 μs max.
(2) End of slave station reception − Slave station driver enabled time = 1 ms or more
(3) End of slave station transmission − Slave station driver disabled time = 10 ms or less
(4) End of master station reception − Master station driver enabled time = 10 ms or more
End of master station transmission End of slave station transmission
(response message)
(1) (4)
(2) (3)
4 - 4 Timing Specifications

14
Chapter 4. Communication
 Consecutive data read command (RS command)
This command reads data from consecutive addresses. This command can read and
return data from consecutive addresses in one message starting from the specified
read start address.
z Command message
Example of reading the present operating status
z Response message
0
Normal end (reading of single data record)
0
Normal end (reading of multiple data records)
0 0
Abnormal end
X X The end code (error) is entered in place of XX.
(2)(1) (3)
(1) End code
(2) Data delimiter
(3) Data 1
(4) Data 2 to (n−1)
(5) Data n
,
(1) (2) (3) (4) (5)
, , ,
(2) (2)
(1)
(2)(1) (3) (4)
Application layer
(1) Command
(2) Data delimiter
(3) Address
(4) Read count
R3S , 3 0 3 W , 1
(2)
4 - 5 Description of Commands