Appendix 3 Reserved Transactions; List Of Reserved Transactions And Format - Mitsubishi Electric MELSEC iQ-R Series User Manual

Appendix 3
This section shows transactions and message formats used internally by the SECS/GEM communication software.

List of reserved transactions and format

This section shows reserved transactions and message formats.
The names and formats of reserved transactions are reserved and defined by the SECS/GEM communication software and
cannot be used for user definitions.
No. Name
*1
1 DTR
(Date and time request)
*1
2 RSD
(Spooled data request)
*1
3 CA_ARS
(Alarm report transmission)
4 H_SCABT
(Host scenario interruption
request)
5 E_SCABT
(Equipment scenario
interruption notification)
*1 Reserved transaction of non-GEM version.
1. DTR (Date and time request)
<S2F17>(H→E)
(Header only)
<S2F18>(H←E)
A<TIME>YYYYMMDDhhmmsscc
2. RSD (Spooled data request)
<S6F23>(H→E)
U1<RSDC>...(1)
<S6F24>(H←E)
B<RSDA>...(2)
3. CA_ARS (Alarm report transmission)
<S5F1>(H←E)
<L, 3>
B<ALCD>...(1)
U2<ALID>...(2)
A<ALTX>...(3)
<S5F2>(H→E)
B<ACKC5>
4. H_SCABT (Host scenario interruption request)
<S99F1>(H→E)
(Header only)
5. E_SCABT (Equipment scenario interruption notification)
<S99F3>(H←E)
(Header only)
APPX
288

Appendix 3 Reserved Transactions

Reserved Transactions
Transaction
Primary message: S2F17(H→E)
Secondary message: S2F18(H←E)
Primary message: S6F23(H→E)
Secondary message: S6F24(H←E)
Primary message: S5F1(H←E)
Secondary message: S5F2(H→E)
Primary message: S99F1(H→E)
Secondary message: Unused
Primary message: S99F3(H←E)
Secondary message: Unused
Acquires the time configured to the CPU of the SECS/GEM communication software
pre-installed model module, and then returns it as 16-byte ASCII data.
This transaction does not involve notification to the Programmable Controller CPU or
acquisition of the equipment time data.
(1) The following code will apply.
0: Transfer the spooled message(s)
1: Discard the spooled messages(s)
(2) One of the following values is returned.
0: OK (initiate the spool output)
1: Error
2: No spooled data exists.
• If communication has been established, this transaction can be executed even
before CA-SECS becomes online (i.e., before the transaction S1F1 is executed).
• The reception of this message will not be notified to the Programmable Controller
CPU.
(1) The settings in the Alarm Data Setting window are edited as follows and then
transmitted.
When an alarm occurs: The first bit is "1".
When an alarm is reset: The first bit is "0".
(2) The set value is transmitted as it is.
(3) The set text is transmitted as it is.
Up to 120 characters can be transmitted.
• Response monitoring is enabled in accordance with the standard for SECS-.
However, the reception notification of a secondary message will not be reported to
the programmable controller CPU.
• To send an alarm report as a normal transaction triggered by the sending request,
set the user definition by another transaction name.
This transaction is transmitted from the host to interrupt the ongoing scenario.
When the ongoing scenario was interrupted by any other than the host scenario
interruption request, this transaction is transmitted to the host.
Description
Sends clock data of the SECS/GEM communication software pre-
installed model module. The programmable controller CPU is not
notified.
Requests the spooled data transfer from the host.
Used by the CA-SECS alarm function.
Interrupts the ongoing scenario from the host.
Notifies that the ongoing scenario was interrupted by equipment
request or processing error.