- No category
advertisement
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.2 About the PLC CPU Monitoring Function
This section explains the PLC CPU monitoring function.
2.2.1 Data registration for using the PLC CPU monitoring function
The following explains the data registration by the user to use the PLC CPU monitoring function.
(1) PLC CPU monitor registration for the Q series C24 that is required to use the PLC
CPU monitoring function is described in the following sections. The registration can be performed using one of the following methods:
1) Registration using the Q series C24 dedicated utility package (GX
Configurator-SC)
(Detailed explanation is found in Chapter 8 of the User's Manual (Basic))
2) Registration using the PLC CPU monitoring registration command (0630) for communication with the MC protocol
(Detailed explanation is found in Section 3.17 of the Reference Manual)
3) Registration using the PLC CPU "CSET" instruction
(Detailed explanation found in Chapter 17 of the User's Manual (Application))
(2) When this function is used with the modem function and data is transmitted or a notification message is notified as a PLC CPU monitoring result, register the connection data for the modem function on the "PLC CPU monitoring system setting" screen of the GX Configurator-SC.
(3) By registering the data for using the above PLC CPU monitoring function, the Q series C24 begins monitoring the PLC CPU.
2.2.2 PLC CPU monitoring information
This section explains the monitoring target information used to execute the PLC CPU monitoring function.
(1) The following information can be registered as the target of the PLC CPU monitoring function.
1) Device monitoring for the local station's PLC CPU
• Monitoring of the numeric values stored in the word device
• Monitoring of the bit device ON/OFF status
2) Monitoring of the local station's PLC CPU status
(2) In monitoring word and bit devices, a maximum total device point value of 960
(equivalent to a maximum of 15360 bits for only bit devices), or a total of 10 blocks when any continuous device range comprises one block, can be registered.
Since monitoring of the local station's PLC CPU status will also be registered as a one-block portion, up to 11 blocks can be registered.
11 ≥ (Number of word device blocks registered + number of bit device blocks registered)
+ CPU status monitoring (1 block)
960 points ≥ (Total number of all word device block points + total number of all bit device block points)
(1 point = 1 word) (1 point = 16 bits)
(3) With device monitoring of the blocks for which the word and bit devices are registered, the head device of each block becomes the monitoring target.
2 - 3 2 - 3
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
Classification
Internal system
Internal user
Register
Special relay
Special register
Input
Output
Internal relay
Latch relay
Annunciator
Edge relay
Link relay
Data register
Link register
Timer
Contact
Coil
Current value
Retentive timer
Contact
Coil
Current value
Contact
Counter
Link special relay
Link special register
Coil
Current value
Step relay
Direct input
Direct output
Index register
File register
(Example1) For a block in which 10 points of word devices from D100 to D109 are registered
Monitoring target: Numeric value stored in D100
Data transmitted: Numeric values stored in D100 to D109
(Example2) For a block in which two points of bit devices from M100 to M131 are registered
Monitoring target: ON/OFF status of M100
Data transmitted: ON/OFF status of M100 to M131
(4) The word and bit devices that can be designated as the monitoring targets and the device codes that are used to register the monitoring devices are shown in the table below.
Register the devices using the existing device ranges.
Device
Device type
Bit Word
CC
CN
SB
SW
SS
SC
SN
CS
W
TS
TC
TN
B
D
F
V
S
DX
DY
Z
R
ZR
ASCII
Device code
Binary
M
L
X
Y
SM
SD
91
H
A9
H
9C
H
9D
H
90
H
92
H
98
H
A2
H
A3
H
CC
H
AF
H
B0
H
C3
H
C5
H
A1
H
B5
H
C7
H
C6
H
C8
H
C4
H
B4
H
C1
H
C0
H
C2
H
93
H
94
H
A0
H
A8
H
Device range
(Default)
0 to 2047
0 to 1FFF
H
0 to 8191
0 to 2047
0 to 1FFF
H
0 to 12287
0 to 1FFF
H
0 to 2047
0 to 1023
0 to 7FF
H
0 to 8191
0 to 1FFF
H
0 to 15
0 to 32767
0 to FE7FF
H
POINT
(1) Designating a non-existent device code will result in an error.
(2) When the device range in the parameter setting has been changed, the new device range can be set as the PLC CPU's monitoring target.
2 - 4 2 - 4
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.2.3 Timing for PLC CPU monitoring
The following explains the timing for PLC CPU monitoring when the PLC CPU monitoring function is executed.
(1) PLC CPU monitoring using the Q series C24 is performed continuously at cycle time intervals registered by the user.
(2) Values from 1 to 65535 (unit: 100ms/s/min) can be registered as the cycle time.
Use the following expressions as a reference when registering the cycle time.
(a) When sending device data or the PLC CPU status
Cycle time designation > K + sequence scan time + processing time
+ data transmission time
(b) When notifying through combined use of the modem function
(when notifying)
Cycle time designation > K + sequence scan time + processing time
+ data transmission time
+ data transmission delay time of the modem
+ modem connection and disconnection time
(when sending data)
Cycle time designation > K + sequence scan time + processing time
+ data transmission time
+ data transmission delay time of the modem
+ modem connection and disconnection time
+ circuit disconnection wait time
When modem initialization has not been performed, the modem initialization time will be added. (We recommend that the modem initialization be performed in advance.)
The items that appear in the above expressions are explained below:
• K : 60 ms constant (internal processing time of the Q series C24)
• Processing time: Processing time for the "Multiple block batch read word unit command 0406"
For 1 point : 11.3 ms
For 480 points: 23.4 ms
For 960 points: 36.2 ms
• Data transmission time = 1 / transmission rate × bit count for one byte portion during transmission
× byte count for transmission data
• Bit count for one byte portion during transmission =
1 + data bit count + parity bit + stop bit count
(parity bit = 1, no parity bit = 0)
• Data transmission delay time by the modem: Depends on the modem specifications, line specifications and line status.
• Modem connection and disconnection time: Depends on the modem specifications, line specifications and line status.
• Modem initialization time: Depends on the modem specifications.
2 - 5 2 - 5
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(3) To monitor the PLC CPU, the Q series C24 reads monitoring information (device information, PLC CPU status information) from the PLC CPU at time intervals set by the user.
POINT
(1) Since the Q series C24 reads the monitoring information (device data, PLC
CPU status) at the time of the next PLC CPU END process after the cycle time elapses, make the cycle time as long as possible.
(2) The following should be considered if the cycle time is short.
• The scan time of the PLC CPU is longer and the number of scan cycles has increased.
• The increase in the processing time of the Q Series C24 PLC CPU monitoring function has increased causing an increase in the processing time of other data communication functions.
• The load on the external device has increased.
2.2.4 Timings of transmission and notification of monitoring results to the external device
Constant cycle transmission
The following explains the timings for the transmission and notification of the PLC CPU monitoring results.
There are two transmission methods for transmitting and notifying the monitoring results of the local station PLC CPU to the external device. These include constant cycle transmission and condition agreement transmission. One of these methods must be selected by the user during PLC CPU monitoring registration.
(1) Constant cycle transmission
The monitoring results are transmitted and notified each time monitoring information is read from the PLC CPU.
(Timing to transmit data)
Monitoring information
One-block portion
• • •
One-block portion
Cycle time
External device
Sequence program
END
END END END
2 - 6 2 - 6
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
Condition agreement transmission
Cycle time
(2) Condition agreement transmission
(a) For device monitoring, the monitoring conditions registered by the user
(conditions for sending monitoring results), the monitoring condition values and the monitoring information read from the PLC CPU are compared. The monitoring results are sent or notified when there is a block where the monitoring conditions match.
For PLC CPU status monitoring, the monitoring results are sent or notified only once when an error is detected for the first time from the status information read from the PLC CPU. (This corresponds to the edge triggered transmission noted below).
(b) Two transmission methods of the monitoring results are available for the condition agreement transmission for device monitoring. These include edge triggered transmission and level triggered transmission.
1) Edge triggered transmission
The monitoring conditions registered by the user (conditions for sending monitoring results), the monitoring condition values and the monitoring information read from the PLC CPU are compared. The monitoring results are sent or notified only once when an agreement of the monitoring conditions is detected for the first time. After that, when the monitoring information read from the PLC CPU does not match the monitoring conditions and then it matches the monitoring conditions once again, the monitoring results are sent or notified.
2) Level triggered transmission
The monitoring conditions registered by the user (conditions for sending monitoring results), the monitoring condition values and the monitoring information read from the PLC CPU are compared. While the monitoring conditions agree, the monitoring results are sent or notified at each cycle time.
(Timing to transmit data)
Monitoring information
One-block
portion
• • •
One-block portion
External device
Sequence program
(conditions matched/not matched)
Matched
END
Not matched
END
Matched
END
2 - 7 2 - 7
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(c) In the condition agreement transmission for device monitoring, the head device for each block is the monitoring target for condition monitoring of each block device.
For the condition agreement transmission, the monitoring conditions that can be designated for the device to be registered by the user and the registration values when designating the monitoring condition are shown in the table below.
Register the monitoring conditions for the head device of each block using the following table.
Monitoring condition (item to be judged)
Registration value
Valid designated device
Device value or status = device monitoring condition value or status
Device value or status
Unsigned
Signed
≠
device monitoring condition value or status
Monitoring device < monitoring condition value
Monitoring device < monitoring condition value
Monitoring device > monitoring condition value
Monitoring device > monitoring condition value
Monitoring device < monitoring condition value
Monitoring device < monitoring condition value
Monitoring device > monitoring condition value
Monitoring device > monitoring condition value
For edge triggered transmissions
0001
H
0002
H
0003
H
0004
H
0005
H
0006
H
0007
H
0008
H
0009
H
000A
H
For level triggered transmissions
0101
H
0102
H
0103
H
0104
H
0105
H
0106
H
0107
H
0108
H
0109
H
010A
H
Bit Word
(d) In device monitoring, register the monitoring condition value or status when the Q series C24 judges that the numeric value/status of the monitoring device for condition agreement transmission (head device of each block) agrees with the condition using the registration values shown below.
Type of monitoring device
Bit device
Word device
Monitoring condition value or status
OFF
ON
Numerical value
Registration value
0000
H
0001
H
0000
H to FFFF
H
(Example 1) When M0 = ON is the condition agreement
Monitoring condition registration value : 0001
H
Registration value for the monitoring condition value or status: 0001
H
(Example 2) When D0 > 100 (signed) is the condition agreement
Monitoring condition registration value : 000A
H
Registration value for the monitoring condition value or status: 100(64
H
)
REMARK
In status monitoring for the PLC CPU, the monitoring conditions and condition values for condition agreement transmission are not registered. Instead, it is registered as whether or not PLC CPU status monitoring will be performed.
Monitoring results in condition agreement transmission are sent or notified only once when an error is detected by the status information read from the PLC CPU for the first time.
2 - 8 2 - 8
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.2.5 Transmission methods of monitoring results and transmission data to the external device
The following explain the method of transmitting the PLC CPU monitoring results and data to the external device.
(1) Data transmission to the external device while performing communication using the MC protocol
(a) The same format as for the messages sent with the on-demand function is used to transmit data, except that the on-demand data section is replaced with the device information and PLC CPU status information. The data is sent as explained in (c) and (d) below.
(Detailed explanation is found in Section 3.17 of the Reference Manual)
When the interface that is to use the modem function is set in the MC protocol, connection processing and disconnection processing to the modem are performed when the PLC CPU monitoring results are transmitted.
(Example) Data transmission by MC protocol with modem function (condition agreement transmission)
Dial
Registration information for PLC CPU monitoring
Disconnection
Cycle time
External device
Sequence program
(conditions matched/ not match)
END
Matched
END
Not matched
END
Matched
(b) When the transmission of on-demand data using user frames is designated, the same format as for sending on-demand data using user frames is used to transmit data, except that the on-demand data section is replaced with the device information and PLC CPU status information. The data is sent as explained in (c) and (d) below.
See the following explanatory items for data reception by the external device side.
• Device information, PLC CPU status information arrangement: Section
3.17 of the Reference Manual
• Arrangement of data in the user frame section to be sent: Chapter 10
(c) When sending the monitoring results as data during constant cycle transmission, the entire block portion of the monitoring target device information and PLC CPU status information is transmitted in batch mode.
2 - 9 2 - 9
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(d) When sending the monitoring results as data during condition agreement transmission, head data (header) and end data (footer) for the on-demand function are added to the device information for a block with matched monitoring conditions and the PLC CPU status information upon the occurrence of an error. The header and footer are added to each clock, and then the monitoring result data is transmitted.
Transmission is performed in the following order: the PLC CPU status information, then the device information registered in the word block, and then the device information registered in the bit block.
POINT
When there is communication using the MC protocol form 1) to 4), all of the device monitoring head device number will be converted to hexadecimal ASCII data and sent. (The same conversion is performed during either constant cycle transmission or condition agreement transmission.)
(2) Data transmission to the external device while performing communication using the non procedure protocol
(a) The device information and CPU information are sent by the word/byte unit designations.
When the communication data ASCII-BIN conversion is designated, it is converted to ASCII code data and sent. (Examples are shown in (f)).
1) When the word/byte unit designation is word unit, the device information a and CPU information are each sent in one-word segments in a (H) (L) sequence.
2) When the word/byte unit designation is byte, the device information and
CPU information are each sent in one-word segments in a (L) (H) sequence.
When the interface that is to use the modem function is set in the non procedure protocol, connection processing and disconnection processing to the modem are performed when the PLC CPU monitoring results are transmitted.
(Example) Data transmission by non procedure protocol with modem function
(condition agreement transmission)
Monitoring information
Dial 1 block
•••
1 block
Disconnection
Cycle time
External device
Sequence program
(conditions matched/ not matched)
END
Matched
END
Not matched
END
Matched
(b) When sending monitoring results as data during constant cycle transmission, the device information of two or more user frame No. and PLC CPU status information that have been currently designated for the constant cycle transmission by the Q series C24.
2 - 10 2 - 10
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
Frame number
B001
H
B002
H
B003
H
B004
H
B005
H
B006
H
B007
H
B008
H
B009
H
B00A
H
B061
H
B080
H
B081
H
B082
H
(c) When sending the monitoring results as data during condition agreement transmission, the device information of two or more user frame No. and PLC
CPU status information that have been currently designated by the Q series
C24 for the condition agreement transmission of the block where the monitoring conditions match are transmitted in batch mode.
When the monitoring conditions of two or more block match, the device information and PLC CPU status information are transmitted for each block.
POINT
When there is an ASCII-BIN conversion of communication data using non procedure protocol, all of the device monitoring head device number will be converted to hexadecimal ASCII data and sent. (The same conversion is performed during either constant cycle transmission or condition agreement transmission.)
(d) The user frame numbers that can be designated for data transmission of
PLC CPU monitoring results are listed below.
• 1
H
to 3E7
H
(Default registration frame numbers)
• 3E8
H
to 4AF
H
(Frame numbers registered by the user in the flash ROM)
• 8001
H
to 801F
H
(Frame numbers registered by the user in the buffer memory)
• B001
H
to B01F
H
(Dedicated frame numbers for this function listed in (e) below)
For details on how to designate user frame numbers, see Transmission using user frames in Chapter 11.
(e) For instructing to transmit the device information and PLC CPU status information when sending monitoring results as data, use the following dedicated user frame numbers.
Information to be transmitted
Valid function
Constant cycle transmission
Condition agreement transmission
Device information for the block registered in number n
Number 1
Number 2
Number 3
Number 4
Number 5
Number 6
Number 7
Number 8
Number 9
Number 10
PLC CPU status information
(CPU abnormal monitoring data)
Number of blocks sent
Monitoring result information for all blocks
Monitoring result information for blocks satisfying the conditions
2 - 11 2 - 11
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(f) Device information and PLC CPU status information are sent using the data arrangement shown below.
The ASCII-BIN conversion designation is designated in buffer memory address 121
H
/1C1
H
. Note that when the user frame has been designated by setting to on the value for bit 14, which indicates the user frame No., there will be ASCII-BIN conversion of corresponding send data. It will be sent as binary data. (See Section 13.3 )
1) When user frame numbers B001
H
to B00A
H
are designated (example of a one-block portion)
• When word device data (W100 to W103, (4 points)) is sent
When the word/byte unit designation is word unit, the device data will be sent in a (H) (L) sequence.
The number of registered points is the number of points in word units.
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points 2.
When the word/byte unit designation is byte When the word/byte unit designation is word
L H
(W)
L H L H L H L H L H L H
(W)
L H H L H L H L H L
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
00
H
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
W100 W101 W102 W103 W100 W101 W102 W103
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points 4.
When the word/byte unit designation is byte
H
W
L H
0 0 0 1 0
L
0
L
0
0
0
H
4
L
0 0 0
H
0
L
0 1 0
H
0
L
0 2 0
H
0
L
0 3 0
H
0
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
30
H
30
H
W100 W101 W102 W103
When the word/byte unit designations word
H
W
L H
0 0 0 1 0
L
0
H
0 0 0
L
4
H
0 0 0
L
0
H
0
0 0
L
1
H
0
0 0
L
2
H
0 0 0
L
3
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
W100 W101 W102 W103
2 - 12 2 - 12
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
• When data for bit device (M16 to M175, (10 point)) is sent
When the word/device unit designation is word unit, the device data will be sent in a (H) (L) sequence.
The number of registered points is the number of points in word units.
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points 2.
When the word/byte unit designation is byte When the word/byte unit designation is word
L H
(M)
L H L H L H
L H
(M)
L H H L H L
10
H
00
H
00
H
90
H
0A
H
00
H
30
H
11
H
12
H
34
H
10
H
00
H
00
H
90
H
0A
H
00
H
11
H
30
H
34
H
12
H
3 0 1 1
0
M
2
3
0 1
M
2
2
M
2
1
1
M
2
0
0 0
M
1
9
M
1
8
0
M
1
7
0
M
1
6
0
M
3
1
M
3
0
0 0
M
2
9
1
M
2
8
0 0 0
M
2
7
M
2
6
M
2
5
1
M
2
4
1 1 3 0
0
M
3
1
0 0
M
3
0
M
2
9
1
M
2
8
0 0
M
2
7
M
2
6
0
M
2
5
1
M
2
4
0
M
2
3
M
2
2
0 1
M
2
1
1
M
2
0
0 0 0
M
1
9
M
1
8
M
1
7
0
M
1
6
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points 4.
When the word/byte unit designation is byte
H
M
L H
0 0 0 0 1
L
0
H
0 0
0
L
A
L
3 0
1
H
1
L
1 2
3
H
4
4D
H
2A
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
41
H
33
H
30
H
31
H
31
H
3 0
1
1
0
M
2
3
0
M
2
2
1
M
2
1
1
M
2
0
0 0
M
1
9
M
1
8
0
M
1
7
0
M
1
6
0
M
3
1
0
M
3
0
0
M
2
9
1
M
2
8
0 0 0
M
2
7
M
2
6
M
2
5
1
M
2
4
When the word/byte unit designation is word
31
H
32
H
33
H
34
H
H
M
L H
0 0 0 0 1
L
0
H
0 0 0
L
A
H
1 1 3
L
0
H
3 4 1
L
2
4D
H
2A
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
41
H
31
H
31
H
33
H
30
H
1 1
3
0
0
M
3
1
0
M
3
0
0
M
2
9
1
M
2
8
0 0
M
2
7
M
2
6
0
M
2
5
1
M
2
4
0
M
2
3
0
M
2
2
1
M
2
1
1
M
2
0
0 0 0
M
1
9
M
1
8
M
1
7
0
M
1
6
33
H
34
H
31
H
32
H
2 - 13 2 - 13
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2) When user frame No. B061
H
is designated
PLC CPU status information (for one block) is sent as the following data: when communicating with
ASCII code when communicating with binary code
Remark
Device code
Number of registered points
Monitoring head device
During normal operation
Device data
Module warning occurring
Module error/module system error occurring
"01"
"0001"
"000000"
"0000"
"0001"
"0002"
01
H
0001
H
000000
H
0000
H
0001
H
0002
H
All fixed value
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points 2.
When the word/byte unit designation is byte When the word/byte unit designation is word
L H L H
L H
L H L H
H L
01
H
00
H
00
H
00
H
01
H
00
H
01
H
00
H
01
H
00
H
00
H
00
H
01
H
00
H
00
H
01
H
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points 4.
When the word/byte unit designation is byte When the word/byte unit designation is word
H
0 1
L H
0 0 0 0 0
L
0
H
0 0 0
L
1
H
0 1 0
L
0
H
0
L
1
H
0 0 0 0 0
L
0
H
0 0 0
L
1
H
0 0 0
L
1
30
H
31
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
31
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
31
H
3) When user frame No. B080
H
is designated
The transmission block count will be sent as follows:
(Example)
Number of registered word blocks: 2 (D0 to D3 (4 points), W100 to W107 (8 points))
Number of registered bit blocks : 1 (M0 to M31 (2 points))
(When ASCII-BIN conversion is not performed) (When ASCII-BIN conversion is performed)
02
H
01
H
00
H
H
0
L
2
H
0
L
1
H
0
L
0
30
H
32
H
30
H
31
H
30
H
30
H
2 - 14 2 - 14
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
4) When user frame No. B081
H
is designated
Information on monitoring results for all blocks are sent as follows:
Results are sent in the following order: the device information registered in the word block, the device information registered in the bit block and then PLC
CPU status information.
(Example)
Number of registered word blocks: 1 (W100 to W103 (4 points))
Number of registered bit blocks : 1 (M0 to M15 (1 point))
Perform CPU status monitoring : 1 (1 point)
(When ASCII-BIN conversion is not performed)
The total number of bytes for the device data section is the number of device points 2.
When the word/byte unit designation is byte g head device g head device g head device
L H
(W)
L H L H L H L H L H
L H
(M)
L H L H
L H L H L H
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
00
H
00
H
00
H
00
H
90
H
01
H
00
H
30
H
11
H
00
H
00
H
00
H
01
H
01
H
00
H
00
H
00
H
W100 W101 W102 W103
3 0 1 1
0
M
0
7
0 1
M
0
6
M
0
5
1
M
0
4
0 0
M
0
3
M
0
2
0
M
0
1
0
M
0
0
0
M
1
5
M
1
4
0 0
M
1
3
1
M
1
2
0 0 0
M
1
1
M
1
0
M
0
9
1
M
0
8
When the word/byte unit designation is word
L H
(W)
L H H L H L H L H L L H
(M)
L H H L L H L H H L
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
00
H
00
H
00
H
90
H
01
H
00
H
11
H
30
H
00
H
00
H
00
H
01
H
01
H
00
H
00
H
00
H
W100 W101 W102 W103
1 1 3 0
0
M
1
5
0 0
M
1
4
M
1
3
1
M
1
2
0 0
M
1
1
M
1
0
0
M
0
9
0
M
0
8
0
M
0
7
M
0
6
0 1
M
0
5
1
M
0
4
0 0 0
M
0
3
M
0
2
M
0
1
0
M
0
0
2 - 15 2 - 15
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points 4.
When the word/byte unit designation is byte
H
W
L H
0 0 0 1 0
L
0
H
0 0 0
L
4
L
0 0 0
H
0
L
0 1 0
H
0
L
0 2 0
H
0
L
0 3 0
H
0
H
M
L H
0 0 0 0 0
L
0
H
0 0 0
L
1
L
3 0 1
H
1
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
30
H
30
H
4D
H
2A
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
33
H
30
H
31
H
31
H
W100 W101 W102 W103
3 0 1 1
0
M
0
7
0
M
0
8
1
M
0
5
1
M
0
4
0 0
M
0
3
M
0
2
0
M
0
1
0
M
0
0
0
M
1
5
0
M
1
4
0
M
1
3
1
M
1
2
0 0 0
M
1
1
M
1
0
M
0
9
1
M
0
8
H
0
L
1
H
0 0 0 0 0
L
0
H
0 0 0
L
1
L
0 0 0
H
0
30
H
31
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
When the word/byte unit designation is word
H
W
L H
0 0 0 1 0
L
0
H
0 0 0
L
4
H
0 0 0
L
0
H
0 0 0
L
1
H
0 0 0
L
2
H
0 0 0
L
3
H
M
L H
0 0 0 0 0
L
0
H
0 0 0
L
1
H
1 1 3
L
0
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
4D
H
2A
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
31
H
31
H
33
H
30
H
W100 W101 W102 W103
1 1 3 0
0
M
1
5
0
M
1
4
0
M
1
3
1
M
1
2
0 0
M
1
1
M
1
0
0
M
0
9
1
M
0
8
0
M
0
7
0
M
0
6
1
M
0
5
1
M
0
4
0 0 0
M
0
3
M
0
2
M
0
1
0
M
0
0
H
0
L
1
H
0 0 0 0 0
L
0
H
0 0 0
L
1
H
0 0 0
L
0
30
H
31
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
2 - 16 2 - 16
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
5) When user frame No. B082
H
is designated
Information on the monitoring results for the condition agreement blocks are sent for each block.
Results are sent in the following order: The PLC CPU status information, the device information registered in the word block and then the device information registered in the bit block.
(Example)
Number of registered word blocks: 2 (D0 to D3 (4 points), W100 to W103 (4 points))
Number of registered bit blocks : 1 (M0 to M15 (1 point))
When the condition satisfied monitoring device is W100 = 0 and M0
≠
ON
(When ASCII-BIN conversion is not performed)
The total number of bytes the device data section is the number of device points
2.
When the word/byte unit designation is byte
For W100 to W103 block data For M0 to M15 block data
L H
(W)
L H L H L H L H L H L H
(M)
L H L H
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
00
H
W100 W101 W102 W103
00
H
00
H
00
H
90
H
01
H
00
H
30
H
11
H
3 0 1 1
0
M
0
7
0 1
M
0
6
M
0
5
1
M
0
4
0 0
M
0
3
M
0
2
0
M
0
1
0
M
0
0
0
M
1
5
M
1
4
0 0
M
1
3
1
M
1
2
0 0 0
M
1
1
M
1
0
M
0
9
1
M
0
8
When the word/byte unit designation is word
For W100 to W103 block data For M0 to M15 block data
L H
(W)
L H H L H L H L H L L H
(M)
L H H L
00
H
01
H
00
H
B4
H
04
H
00
H
00
H
00
H
00
H
01
H
00
H
02
H
00
H
03
H
W100 W101 W102 W103
00
H
00
H
00
H
90
H
01
H
00
H
11
H
30
H
1 1 3 0
0
M
1
5
0 0
M
1
4
M
1
3
1
M
1
2
0 0
M
1
1
M
1
0
0
M
0
9
1
M
0
8
0
M
0
7
M
0
6
0 1
M
0
5
1
M
0
4
0 0 0
M
0
3
M
0
2
M
0
1
0
M
0
0
2 - 17 2 - 17
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(When ASCII-BIN conversion is performed)
The total number of bytes for the device data section is the number of device points 4.
When the word/byte unit designation is byte
For W100 to W103 block data For M0 to M15 block data
H
W
L H
0 0 0 1 0
L
0
H
0 0 0
L
4
L
0 0 0
H
0
L
0 1 0
H
0
L
0 2 0
H
0
L
0 3 0
H
0
H
M
L
0
H
0 0 0 0
L
0
H
0 0 0
L
1
L
3 0 1
H
1
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
30
H
30
H
4D
H
2A
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
33
H
30
H
31
H
31
H
W100 W101 W102 W103
3 0 1 1
When the word/byte unit designation is word
For W100 to W103 block data For M0 to M15 block data
0
M
0
7
0
M
0
6
1
M
0
5
1
M
0
4
0 0
M
0
3
M
0
2
0
M
0
1
0
M
0
0
0
M
0
1
5
M
1
4
0
M
1
3
1
M
1
2
0 0 0
M
1
1
M
1
0
M
0
9
1
M
0
8
H
W
L H
0 0 0 1 0
L
0
H
0 0 0
L
4
H
0 0 0
L
0
H
0 0 0
L
1
H
0 0 0
L
2
H
0 0 0
L
3
H
M
L
0
H
0 0 0 0
L
0
H
0 0 0
L
1
H
1 1 3
L
0
57
H
2A
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
30
H
30
H
34
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
30
H
30
H
30
H
32
H
30
H
30
H
30
H
33
H
W100 W101 W102 W103
4D
H
2A
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
30
H
31
H
33
H
30
H
31
H
31
H
1 1 3 0
1
5
0
M
1
4
0
M
1
M
1
3
1
2
1
M
1
1
0 0
M M
1
0
0
M
0
9
0
M
0
8
0
M
0
0
7
M
0
6
0
5
0
M
0
4
1
M
0 0 0
M
0
3
M
0
2
M
0
1
0
0
1
M
2 - 18 2 - 18
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
(3) Notification to the interface side using the modem function
(a) The notification message (text string data) contained in the user registered data for connecting the modem function is conveyed using the modem function.
The device information and the CPU status information read from the
PLC CPU are not sent to the external device in the notification message.
Include the device information and the CPU status information by which the PLC CPU status can be checked in the preregistered notification message.
(b) The method for message notification is functionally the same as the notification using the modem function described in Chapter 3.
The difference is that notification is performed with Y14 OFF when using the modem, whereas for notification using PLC CPU monitoring, notification is performed for whenever the PLC CPU error is detected or the designated device status is matched with the monitoring conditions (see Section 2.2.4).
(c) During constant-cycle transmission, a notification message for one connection data registered for notifying constant-cycle transmission is sent.
(d) During condition agreement transmission, a notification message for connection data registered in the block where the monitoring conditions match is sent in block units.
When there are multiple blocks where the monitoring conditions match, notification is performed at the "Wait time of notification" interval (notification interval) set by the user for use with the modem function. The PLC CPU monitoring stops until notification has been performed to all blocks where the monitoring conditions match.
POINT
(1) When performing message notification using the PLC CPU monitoring function, set the corresponding interface side as the target of the modem function.
(2) When setting data for the PLC CPU monitoring function with GX Configurator-
SC, PLC CPU monitoring begins immediately when the Q series C24 starts up.
2 - 19 2 - 19
2 USING THE PLC CPU MONITORING FUNCTION
MELSEC-Q
2.2.6 Execution sequence for using the PLC CPU monitoring function
The following explains the execution sequence for using the PLC CPU monitoring function.
(1) When transmitting the monitoring results through data transmission/notification messages using the modem function, perform the following settings in order to use the modem function.
Setting item Explanation section
Initial setting using the GX Configurator-SC Section 3.4.2
Registration of data No. for initialization and data No. for connection Sections 3.4.3 and 3.4.4
Initialization of the Q series C 24 modem/TA Section 3.4.5
(2) Register PLC CPU monitoring for the Q series C24 using one of the methods described in Section 2.2.1.
(3) By registering PLC CPU monitoring, the Q series C24 monitors the local station's
PLC CPU regardless of the RUN/STOP status and sends the monitoring information to the external device.
(4) When reregistering PLC CPU monitoring in order to change the registration data for the PLC CPU monitoring, reregister after canceling the PLC CPU monitoring.
1) When registering with communication using the MC protocol (detailed explanation found in Section 3.17 of Reference Manual)
2) When registering with the PLC CPU's "CSET" instruction (detailed explanation found in Chapter 17 of User's Manual (Application))
To cancel when using GX Configurator-SC, change the PLC CPU to the STOP status, redo the settings, and then restart the QCPU.
2 - 20 2 - 20
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 2 SAFETY PRECAUTIONS
- 6 REVISIONS
- 7 INTRODUCTION
- 7 CONTENTS
- 14 About the Manuals
- 15 The Manual's Use and Structure
- 17 About the Generic Terms and Abbreviations
- 19 Definitions and Descriptions of Terminology
- 21 1 OVERVIEW
- 21 1.1 Overview
- 26 1.2 Functions Added/Changed by Function Version B
- 27 2 USING THE PLC CPU MONITORING FUNCTION
- 27 2.1 Overview
- 29 2.2 About the PLC CPU Monitoring Function
- 29 2.2.1 Data registration for using the PLC CPU monitoring function
- 29 2.2.2 PLC CPU monitoring information
- 31 2.2.3 Timing for PLC CPU monitoring
- 32 2.2.4 Timings of transmission and notification of monitoring results to the external device
- 35 2.2.5 Transmission methods of monitoring results and transmission data to the external device
- 46 2.2.6 Execution sequence for using the PLC CPU monitoring function
- 47 2.3 Settings for Using the PLC CPU Monitoring Function
- 47 2.3.1 System setting items for the PLC CPU monitoring function
- 52 2.3.2 How to register and cancel the PLC CPU monitoring function
- 54 2.4 Precautionary Notes for Using the PLC CPU Monitoring Function
- 56 3 COMMUNICATIONS BY THE MODEM FUNCTION
- 56 3.1 Overview
- 57 3.1.1 Features
- 60 3.1.2 Function list
- 61 3.1.3 Comparisons with related devices
- 62 3.2 System Configuration
- 62 3.2.1 System configuration when performing data communication with an external device
- 63 3.2.2 System configuration when using the notification function
- 64 3.2.3 System configuration when connecting GX Developer
- 65 3.2.4 Precautions for system configurations
- 67 3.3 Specifications
- 67 3.3.1 Transmission specifications
- 68 3.3.2 Specification of connectable modems/terminal adapters
- 71 3.3.3 Compatibility with the QCPU remote password function
- 77 3.3.4 Compatibility with the callback function
- 86 3.3.5 I/O signals with the PLC CPU
- 88 3.3.6 Buffer memory
- 101 3.3.7 Precautions when using the modem function
- 107 3.4 Start-up of the Modem Function
- 107 3.4.1 Start-up procedures when communicating data with external devices
- 110 3.4.2 Initial settings of the serial communication module
- 113 3.4.3 Register/read/delete of the initialization data
- 118 3.4.4 Register/read/delete of the data for connection
- 123 3.4.5 Initialization of modem/terminal adapter
- 127 3.4.6 Line connection
- 133 3.4.7 Data communication and notification
- 139 3.4.8 Line disconnection
- 142 3.5 Sample Programs
- 143 3.5.1 Sample program for data communication-1
- 149 3.5.2 Sample program for data communication-2
- 158 3.5.3 Sample program for notification
- 161 4 RECEIVING DATA WITH AN INTERRUPT PROGRAM
- 162 4.1 Settings for Receiving Data Using an Interrupt Program
- 162 4.2 Interrupt Program Startup Timing
- 163 4.3 Reception Control Method Using an Interrupt Program
- 164 4.4 Programming
- 164 4.4.1 Program example
- 165 4.4.2 Precautions when receiving data with an interrupt program
- 167 5 CHANGING SEND AND RECEIVE DATA LENGTH UNITS TO BYTE UNITS (WORD/BYTES UNITS SETTING)
- 169 6 CHANGING THE DATA COMMUNICATIONS MONITORING TIMES
- 170 6.1 No-Reception Monitoring Time (timer 0) Setting
- 175 6.2 Response Monitoring Time (timer 1) Setting
- 178 6.3 Transmission Monitoring Time (timer 2) Setting
- 181 6.4 Message Wait Time Setting
- 182 7 DATA COMMUNICATIONS USING DC CODE TRANSMISSION CONTROL
- 183 7.1 Control Contents of DTR/DSR (ER/DR) Signal Control
- 185 7.2 Control Contents of DC Code Control
- 188 7.3 Precautions when Using the Transmission Control Functions
- 190 8 DATA COMMUNICATIONS USING HALF-DUPLEX COMMUNICATIONS
- 190 8.1 Half-duplex Communications
- 191 8.2 Data Transmission and Reception Timing
- 195 8.3 Changing the Communication System
- 196 8.4 Connector Connections for Half-duplex Communications
- 197 8.5 Half-duplex Communications Precautions
- 198 9 CONTENTS AND REGISTRATION OF THE USER FRAMES FOR DATA COMMUNICATION
- 198 9.1 User Frame Types and Contents During Communication
- 198 9.1.1 User frames to be registered and used by the user
- 204 9.1.2 Default registration frame (read only)
- 205 9.2 Transmission/Reception Processing Using User Frame Register Data
- 208 9.3 Precautions when Registering, Reading, Deleting and Using User Frames
- 210 9.4 Register/Read/Delete User Frames
- 213 9.4.1 Registering user frames
- 214 9.4.2 Reading user frames
- 215 9.4.3 Deleting user frames
- 216 10 ON-DEMAND DATA COMMUNICATIONS USING USER FRAMES
- 216 10.1 User Frame Data Communications Function
- 217 10.2 User Frame Types and Registration
- 217 10.3 User Frame On-Demand Data Transmission and Buffer Memory Used
- 219 10.4 On-Demand Function Control Procedure During User Frame Use
- 219 10.4.1 Data communication using the ASCII code
- 221 10.4.2 Data communications using the binary code
- 223 10.5 Example of an On-Demand Data Transmission Program Using User Frames
- 225 11 DATA COMMUNICATIONS USING USER FRAMES
- 226 11.1 Overview of Data Communication Procedure
- 227 11.2 Data Reception
- 227 11.2.1 About reception data
- 234 11.2.2 Timing for start/completion of data reception
- 238 11.2.3 Receive procedure
- 239 11.2.4 User frame setting for reception
- 245 11.3 Receive Program
- 245 11.3.1 Sequence program example
- 246 11.3.2 Application example for data reception using a combination that specifies the first frame
- 252 11.3.3 Application example for data reception using a combination that does not specify the first frame
- 254 11.4 Data Transmission
- 254 11.4.1 Send data
- 256 11.4.2 Transmission procedure
- 257 11.4.3 Settings for transmission user frames
- 261 11.5 Transmission program
- 264 12 TRANSPARENT CODES AND ADDITIONAL CODES
- 264 12.1 Handling the Transparent Code and Additional Code Data
- 265 12.2 Registering Transparent Codes and Additional Codes
- 266 12.3 Handling Transparent Codes and Additional Codes During Non Procedure Protocol Data Communication
- 271 12.4 Example of Data Communication Using the Non Procedure Protocol
- 272 12.4.1 Example of data reception
- 274 12.4.2 Example of data transmission
- 276 12.5 Handling Transparent Codes and Additional Codes During Bidirectional Protocol Data Communication
- 279 12.6 Example of Data Communication Using the Bidirectional Protocol
- 280 12.6.1 Example of data reception
- 282 12.6.2 Example of data transmission
- 284 13 COMMUNICATING WITH ASCII CODE (ASCII-BIN CONVERSION)
- 284 13.1 ASCII-BIN Conversion
- 284 13.2 Settings for ASCII-BIN Conversion
- 285 13.3 Performing ASCII-BIN Conversion for Data Communicated via Non Procedure Protocol
- 287 13.4 Example of Data Communication Using the Non Procedure Protocol
- 288 13.4.1 Example of data reception
- 291 13.4.2 Example of data transmission
- 293 13.5 Performing ASCII-BIN Conversion for Data Communicated Via the Bidirectional Protocol
- 295 13.6 Example of Data Communication Using the Bidirectional Protocol
- 296 13.6.1 Example of data reception
- 297 13.6.2 Example of data transmission
- 298 14 DATA COMMUNICATIONS USING EXTERNAL DEVICE AND PLC CPU M : N CONFIGURATION
- 298 14.1 Data Communications Precautions
- 300 14.2 External Devices Interlock Conditions
- 300 14.2.1 Maximum communications time per external device station
- 301 14.2.2 Message structure when communicating data between external devices
- 303 14.3 Examples of Procedure for Data Communications with the PLC CPU
- 303 14.3.1 Sequential data communications between external devices and the PLC CPU
- 306 14.3.2 Data communications between PLC CPU and external devices by designating a master station and slave stations
- 309 15 SWITCHING THE MODE AFTER STARTING
- 310 15.1 Mode Switching Operation and Contents that can be Changed
- 310 15.1.1 Settings that can be changed with mode switching
- 310 15.1.2 Operation for mode switching
- 311 15.2 Mode Switching Precautions
- 313 15.3 I/O Signals for Handshake with PLC CPU and Buffer Memory
- 315 15.4 Switching the Mode from the PLC CPU
- 315 15.4.1 Mode switching procedure
- 316 15.4.2 Mode switching sample program
- 317 15.5 Switching the Mode from an External Device
- 317 15.5.1 Mode switching procedure
- 318 15.5.2 Mode switching sample program
- 319 16 USING COMMUNICATION DATA MONITORING FUNCTION
- 319 16.1 Communication Data Monitoring Function
- 319 16.1.1 Overview
- 320 16.1.2 Communication data monitoring operation
- 322 16.2 Communication Data Monitoring Function Settings
- 326 16.3 Communication Data Monitoring Example
- 329 17 DEDICATED INSTRUCTIONS
- 329 17.1 Dedicated Instruction List
- 330 17.2 BUFRCVS Instruction
- 333 17.3 CSET Instruction (PLC CPU Monitoring Register/Cancel)
- 339 17.4 CSET Instruction (Initial Settings)
- 343 17.5 GETE Instruction
- 346 17.6 PRR Instruction
- 349 17.7 PUTE Instruction
- 354 INDEX
- 356 WARRANTY