0% found this document useful (0 votes)
102 views7 pages

General 2. Specifications

yokogawa measure

Uploaded by

Holics
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
102 views7 pages

General 2. Specifications

yokogawa measure

Uploaded by

Holics
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

<<Contents>> <<Index>>

General GC1000 and Analyzer Server


Communication Function
Specifications MODBUS Communication
GS 11B3G1-02E

1. General 2. Specifications
The MODBUS protocol can be used for DCS communica-
tion for the GC1000 and analyzer server. 2.1 Communication Transmission Modes
This communication protocol was first established for the There are two modes for signal transmission between the
Programmable Logic Controller (PLC) made by Gould, Inc., master and slave; RTU (Remote Terminal Unit) mode and
and is now used as the universal communication protocol ASCII mode. The analyzer server supports the RTU mode
between different systems. only, however, the analyzer supports both modes.
Here the specification of Modbus communication which is
Item ASCII mode RTU mode
applied for GC1000 and Analyzer server is introduced.
Regarding the general specification of Modbus, refer to Number of data
7 bits (ASCII) 8 bits (binary)
bits
Modbus Protocol Reference Guide.
Message starting
Colon “:” None
1.1 MODBUS Configuration character
MODBUS was started as a method to allow a master device Message ending Carriage return/line feed
None
character “<cr><lf>”
to control multiple slave devices. Each device with a device
number is connected to a master. Message length 2N+1 N
Time interval of
1 second or shorter 24 bit-time or shorter
data
Master
(DCS) LRC (logical CRC-16 (cyclic
Error detection
redundancy check) redundancy check)
T01.EPS

MODBUS
2.2 Message Configuration
Slave 1 Slave 2 Slave 3 Slave 4 A message consists of four fields: device number, function,
F1_1.EPS data, and error check. It is always sent in this sequence.
Figure 1.1 MODBUS configuration In ASCII mode, a colon “:” is the starting character and
carriage return/line feed “<cr><lf>” is the message ending
The master device (master) can send a query (i.e. poll) or string. The portion between the starting character and ending
command to a slave device (slave) on a regular basis or when string is the message body. The communication message is
required. In either case, the master starts signal transmission entirely ASCII codes. The message excluding the starting
then the slave responds. character and ending string consists of “0” to “9” and “A” to
“F” representing hexadecimal numbers.
Master Slave
In RTU mode, the message consists of binary codes and can
Device number Device number be transmitted faster than in ASCII mode. If the signal
Command message
Function Function interval is more than 24 bit-time in the transmission line, the
Response message start of a new message is identified. In this system, time-out
Data Data
is 10 ms regardless of the transmission speed.
Error check Error check

F1_2.EPS Device number


Function
Figure 1.2 Master-slave command and response cycle
Data
A message transmitted between devices contains the device Error check
number, function, data, and error check code. The function F2_3.EPS
is encoded depending on the message characteristics and data
Figure 2.3 Message configuration
type.
The error check code checks the validity of the entire (1) Device number
message. The device number is set in advance for each slave and
ranges from 1 to 254. This number is same as Analyzer ID.
The ranges from 1 to 240 is assigned as GC1000, 241 to 254
as Analyzer server. The master performs signal transmission
to each slave simultaneously. Each slave checks the device
number in the message to determine whether the received

Yokogawa Electric Corporation GS 11B3G1-02E


2-9-32, Nakacho, Musashino-shi, Tokyo, 180 Japan ©Copyright Jan. 1998(YG)
Tel.: 81-422-52-5694 Fax.: 81-422-52-0622 1st Edition Jan. 1998(YG)
<<Contents>> <<Index>> 2
message is directed to the slave itself and returns a response write, and loop function, the same message as the command
message. message is sent back. For the read function, the device
For some functions, “0” can be specified as the device number plus function added with the read data are sent back
number. In this case, all slaves execute the receiving process as the response message. If an address to which data is not
of the same command message at the same time. However, allocated is read, an error is not generated but zero (0) is
the response message is not sent back. Device number 0 is responded as the read data.
supported by the analyzer server only. For the analyzer, (2) Error response
device number 0 results in a device number error. If the command message is faulty, the slave does not execute
(2) Functions the command but sends back an error response. The master
The master specifies the function to be executed by the slave. can check whether the command is accepted successfully by
The analyzer or analyzer server supports the following checking the function in the response message. If an error is
functions in the MODBUS protocol. identified, the details can be checked from the error code.

Device number
Function No. Function Description
Error function (command function + 128)
Reads the ON/OFF status of a
01 Coil status read Error code
series of coils.
Error check
Reads the ON/OFF status of a
02 Input relay status read F2_4.EPS
series of input relays.
Holding register Reads the current value of a Figure 2.4 Response to a faulty command message
03
content read series of holding registers.
Input register content Reads the current value of a
04 Error code Description
read series of input registers.
Single coil status Forcibly changes the status of a 01 Function code error (non-existent function)
05
change coil.
02 Coil, input relay, or register number error (more than 8000)
Single holding register Writes a value to a holding
06 Number of coils, input relays, or registers error (registers:
write register. 03
more than 125, coils/input relays:more than 2000)
Sends back the same message as
08 Loopback test An unrecoverable error occurred on the slave while the
the command message. 04
command message was being executed.
T02.EPS
11 Set data error (out of range)

(3) Data T04.EPS

There are two types of data “coil/relay” in bits and “register”


as 16-bit data. The coil uses two values (ON/OFF or 0/1), (3) No response
while the register ranges from 0 to 65535. Up to 8000 coils/ In the following cases, the slave ignores the command
relays or registers can be accessed and 1 to 8000 addresses message and does not send back a response (no response). If
are assigned. the device number is 0 (broadcasting), all slaves execute the
command but do not send back a response.
MODBUS name Address Application 1. When a transmission error (overrun, framing error, parity
Device Device number Analyzer number error, or CRC error) is detected in the command message
R/W Coil 0XXXX Command 2. When the device number in the command message does
Contact not match the slave number assigned to the slave
R Input relay 1XXXX Status

R/W Holding resistor 4XXXX Set value


Data
R Input register 3XXXX Measured value
3. Communication Specifications
For MODBUS communication, the DCS communication port
XXXX : 0001 to 8000 T03.EPS
of the GC1000 or analyzer server is used. The analyzer has a
DCS communication port, while the analyzer server has up
(4) Error check to three DCS communication ports.
A message is followed by an error check code to detect a Communication standard:
message error (i.e. bit changes) caused by signal transmis- RS-422 (GC1000 output)/RS-232C (output)
sion. In ASCII mode, an error check code according to LRC Start-stop synchronization:
(logical redundancy check) is used. In RTU mode, an error Start bit 1, data bit 7/8, parity bit 1, stop bit 1
check code according to CRC-16 (cyclic redundancy check) Communication speed:
is used. 1200, 2400, 4800, 9600 bps (selectable)
2.3 Slave Response Error detection:
When the slave receives a command from the master, it Odd number parity, even number parity, none
performs an error check then sends back a normal response if (selectable)
the command is normal, or an error response if the command Transmission mode: ASCII mode (GC1000)/RTU mode
is abnormal.
(1) Normal response
For the single coil status change, single holding register

All Rights Reserved. Copyright © 1998, Yokogawa Electric Corporation GS 11B3G1-02E 1st Edition Jan.05, 1998-00
<<Contents>> <<Index>> 3
4. System Configuration 5. Communication Data
(1) GC1000
5.1 Coil (command contact)
For the communication port, an RS-422 standard serial port
is used. This standard is converted into the RS-232C (1) Run command
standard via a communication converter (K9404LD) then Commands the start of continuous analysis to the
connected to the DCS. This communication converter has a GC1000.
protection feature that automatically disconnects communi- (2) Stop command
cation if the explosion-proof feature of the GC1000 cannot
Commands the stop of continuous analysis to the
be maintained.
GC1000.
Field Panel/office (3) Time setting request
Requests the GC1000 to set the system clock.
(4) Change to main pattern request
Communication converter Requests of changing the appointed operational pattern
K9404LD
RS422 Note RS232C as the main pattern.
GC1000 DCS
analyzer (5) Interrupt pattern execution request
Power off signal Requests of changing the appointed operational pattern
as an interrupt pattern.
Note : Dedicated communication line (RS-422) Note 1: Coil reset the status from 1 to 0 automatically when
0.75 mm2 twisted pair x 3, cable outside diameter 10 to 15.9 the message is accepted by GC1000.
mm, up to 1 km (*) Note 2: The command regarding the operation executes after
Flameproof packing cable must be constructed on the analyzer the analysis finished.
side. Note 3: It is needed to use the input relay if the command is
Refer to "GC1000 Installation Manual (TI 11B3A103E)."
accepted or not.
* Parts, cables, and construction materials must be prepared by
the customer.
F4_1.EPS 5.2 Input Relay (status contact)
Figure 4.1 GC1000 (1) Analyzer normal
(2) Analyzer Server The GC1000 is normal. If there is no alarm of alarm
level 1 (critical failure) or level 2 (minor failure), 1 is
RS232C Note displayed.
DCS
Analyzer
server
(2) Analyzer failure
Control room
HUB The GC1000 is faulty. If there is at least one alarm of
alarm level 1 (critical failure), 1 is displayed.
(3) Analyzer server failure
HUB HUB Field The analyzer server is faulty. If there is at least one alarm
of alarm level 1 (critical failure), 1 is displayed.
GC1000 GC1000 GC1000 GC1000 (4) Alarm status change
The alarm status to the GC1000 is changed. After a new
Note : Analyze Server is connected to DCS with the cable of RS232C alarm occurs, when the alarm status change is read, 1 is
D-sub 25 pin straight.
F4_2.EPS read. Then, when at least one alarm status is read, the
Figure 4.2 Analyzer server status is reset to 0.
(5) Measuring (run mode)
The GC1000 is measuring. In RUN mode, 1 is dis-
played. Otherwise, 0 is displayed.
(6) Stop (ready mode)
The GC1000 stops. In READY mode, 1 is displayed.
Otherwise, 0 is displayed.
(7) Maintenance (other modes)
If the GC1000 is in MANUAL, LAB, or PAUSE mode,
1 is displayed. Otherwise, 0 is displayed.
(8) Executing the operational pattern
The corresponding pattern is being executed.
(9) Data update
New data can be acquired for each task. After new data
arises, when data update is read, 1 is read. Then, at least
one analysis value is read, and the status is reset to 0.

All Rights Reserved. Copyright © 1998, Yokogawa Electric Corporation GS 11B3G1-02E 1st Edition Jan.05, 1998-00
<<Contents>> <<Index>> 4
(10) Data valid (2) Starting peak number
Data is valid for each analysis value. The requirements The starting peak number assigned to each task is
for validity are that the analysis value is between the displayed. The number of analysis values is 255 or
upper and lower limits, the retention time is at or below fewer (including the peaks of all tasks). The number is 0
the upper limit, and for operation data, the data to be if no peak is assigned.
used for operation is valid. (3) Peak number
(11) Alarm status Peak number assigned to each task is displayed. See the
The alarm status of the GC1000 and analyzer server is figure below.
displayed for each alarm number. If an alarm occurs, 1 Example: The peak number of Task 2, Peak 3 is 7
is displayed. Otherwise, 0 is displayed. The alarm
number is 1 to 99 for level 1 alarms of the analyzer, 101 Starting peak number = 1
to 199 for level 2 alarms, and 201 to 249 of analyzer Task 1 Number of peaks = 4
Starting peak number = 5
server alarms. The analyzer bus regular cycle communi- Task 2 Number of peaks = 10
cation off alarm is assigned to 249.
Starting peak number = 15
(12) Calibration factor update Task 3 Number of peaks = 10
Whether a new calibration factor is updated is displayed Starting peak number = 25
for each task. After the calibration factor is updated,
when calibration factor update is read, 1 is read. Then,
if at least one calibration factor is read, the status is reset
to 0. 255
F5_2.EPS

5.3 Holding Register (set data) Figure 5.2 Example of peak allocation
(1) Time setting value (4) Sampling time
This is a set of four registers used by the DCS to set the This register contains the sampling time for each task.
analyzer clock. When the time setting request is made, Hour and minute are stored.
this setting value is set in the analyzer system clock.
These registers are also used for the coil time setting Example: 15: 23
request. When Analyzer Server is set the time and date
all GC1000 connected to Analyzer Server is set the same Hour Minute 0F17 (Hexadecimal)
F5_3.EPS
time and date.
(5) Analysis value
Example: September 25, 1996, 15:23:10
This register contains each analysis value. The value is
Year 07CC (Hexadecimal)
represented by a fraction to the full scale or by a real
number (floating point format). The full scale is set in
Month Day 0919 (Hexadecimal)
advance for each analysis value. As the scaling factor,
either 9999 or 65535 can be selected. The real number
*1 000F (Hexadecimal)
format conforms to the IEEE standard and requires two
Hour
registers per data.
Minute Second 170A (Hexadecimal) Fraction format:
F5_1.EPS
(Analysis value * Scaling factor)/Full scale value
For example, the analysis result is 5 ppm (0-20 ppm
Figure 5.1 Time register configuration range), in this case, reading value to use scaling factor
(2) Task change 9999 is
5
20 × 9999 = 2499 (09C3)
The DCS sets the starting task number of a operational
pattern on the GC1000. If the objected operational F5_4.EPS

pattern set a single task, continuous measurement can be For the real number format, units (such as %, ppm, etc.)
performed by specifying the flow path. are considered. For example, the floating point value
(3) Analysis value converted from 1.5 can be read for 1.5 %.
Same data as the analysis value in the input register can (6) Retention time
be read but cannot be written. This register contains the retention time for each analysis
value. The unit is in seconds.
5.4 Input Register (measured data) (7) Calibration factor
(1) Task number
This register contains the calibration factor for each
The currently selected task number is displayed. In stop analysis value. 0.000 to 9.999 are multiplied by 1000 and
or MANUAL mode, the task number is 0. In LAB mode, displayed (i.e. 0000 to 9999).
the task number is 32.

All Rights Reserved. Copyright © 1998, Yokogawa Electric Corporation GS 11B3G1-02E 1st Edition Jan.05, 1998-00
<<Contents>> <<Index>> 5
6. Addressing 6.3 Mapping Feature
The analyzer server has 512 mapping registers that can be set
6.1 General Rules by the user for each of the Coil, Input relay, Holding register,
In this system, the process control system is positioned as the and Input register. The device number and address of the
master device, and the GC1000 or analyzer server as the GC1000 connected can be set in the mapping register. The
slave device. The GC1000 ID number corresponds to the mapping register address ranges from X7001 to X7512.
device number. However, since the analyzer server controls With the device mapping feature, data required by the DCS
multiple GC1000s, an analyzer server has multiple device can be selected from the data prepared by the GC1000 at a
numbers corresponding to these GC1000s. time and can be transferred to the DCS continuously.
The operation command is assigned to the coil, the status Analyzer
flag to the input relay. The set value corresponds to the
holding register, and the measured value such as the analysis Mapping register
result to the input register. Up to 8000 coils/relays or X7001
X7002
registers are available. Addresses 1 to 8000 are assigned for
X7003
access from the master.
The GC1000 data is for each analyzer, each operational Analyzer
DCS
pattern, each task, or for each peak. The relationship
between the data and address is defined as shown below.

Address Application
X7512
Each F6_1.EPS
000X X: Item number (1 to 9)
analyzer
Each Figure 6.1 Mapping feature
operational 00XP X: Item number (1 to 9), P: Pattern number (1 to 4)
pattern
Each t as k 0XTT X: Item number (1 to 9), TT: Task number (1 to 32)
X: Item number (1 to 6), CCC: peak number
Each peak XCCC
(1 to 255)
T05.EPS

6.2 Exceptions
Analyzer server normal/error of the Input relay shows the
analyzer server status. Therefore, the same information is
displayed for all GC1000 device numbers connected to an
analyzer server. The alarm status of the Input relay is
displayed as 1 or 0 by checking the GC1000 alarm status
against the address and alarm number. In this case, the alarm
status is not for each peak but addresses 12001 to 12249 are
used. (The number from the place of 100 is the alarm
number.)
For the analysis value of the Input register, either the fraction
format or real number format can be selected. In the real
number format, two registers are required per data, so the
address is twice as large as the peak number. For example,
addresses of data #1, #2, and #3 in the real number format
are 31001-2, 31003-4, and 31005-6.

All Rights Reserved. Copyright © 1998, Yokogawa Electric Corporation GS 11B3G1-02E 1st Edition Jan.05, 1998-00
<<Contents>> <<Index>> 6
7. Address Table
7.1 Address Table (general)

Compo-
Name Unit Pattern Task Address Description
nent
Run command YES 00001 When the message is received, the slave is reset.
Stop command YES 00002 Same as above.
Time setting request YES 00003 Same as above.
Coil Change to main pattern
YES 0001P Same as above.
request
Interrupt pattern execution
YES 0002P Same as above.
command
Analyzer normal YES 10001
Analyzer error YES 10002
Reset when the alarm status is read after alarm status
Analyzer status change YES 10003
change is read.
Measuring YES 10004
Stop YES 10005
Maintenance YES 10006
Analyzer server normal YES 10008
Input relay
Analyzer server error YES 10009
Executing pattern YES 1001P
Reset when the analysis value is read after data update is
Data update YES 101TT
read.
Reset when the calibration factor is read after calibration
Calibration factor update YES 102TT
factor update is read.
Data valid YES 11CCC
Alarm status YES 12AAA AAA: Alarm number (1 to 245)
40001- Year (40001), month/day (40002), hour (40003),
Time setting request YES
Holding 40004 minute/second (40004)
register Task change YES 4001P
Analysis value 41DDD Read only. Write disabled.
Task number YES 30001
Starting peak number YES 301TT Peak starting position for each task
Number of peaks YES 302TT Number of peaks for each task
Input Sampling time YES 303TT Hour/minute
register 31CCC/- Analysis value (CCC: Peak number), DDD=CCC*2-1 for
Analysis value YES
31DDD the real number
Retention time YES 32CCC Second
Calibration factor YES 33CCC Analysis value (CCC: Peak number)
T06.EPS

All Rights Reserved. Copyright © 1998, Yokogawa Electric Corporation GS 11B3G1-02E 1st Edition Jan.05, 1998-00
<<Contents>> <<Index>> 7
7.2 Address Table (MODBUS mapping)

Name Unit Pattern Task Peak Address Description


Time setting request YES 00001 When the message is received, the slave is reset.

Coil
MODBUS mapping 07XXX Same as above. XXX: 001 to 512

Analyzer server normal YES 10001


Analyzer server error YES 10002
Reset when the alarm status is read after alarm status
Alarm status change YES 10003
change is read.

Input Relay
Alarm status YES 101AA AA: Alarm number (1 to 49)

MODBUS mapping YES 17XXX XXX: 001 to 512

40001- Year (40001), month/day (40002), hour (40003),


Time setting request YES
40004 minute/second (40004)

Holding
Register
MODBUS mapping 47XXX XXX: 001 to 512

Input
MODBUS mapping 37XXX XXX: 001 to 512
Register

T07.EPS

All Rights Reserved. Copyright © 1998, Yokogawa Electric Corporation GS 11B3G1-02E 1st Edition Jan.05, 1998-00

You might also like