ABB Relion 620 Series - Writing of SPA Data; SPA Events; Event Outlook

3.5.4 Writing of SPA data
Writing SPA data refers here either to writing to a Modbus Coil (one bit data) or to a
writable Modbus Register (up to 16 bit data). SPA write operation can only be
performed to one Modbus object at a time.
There are rules for writing SPA data.
• When writing to coils, SPA channel 0 is used. Data type is O, and the data number
corresponds to the Coil address to be written. Value can be “0” or “1” (depends
on the object).
• When writing to registers, SPA channel 1 is used. Data type is O, and the data
number corresponds to the Register address to be written. Value can be
“0...65535” (depends on the object).
If the written data address does not exist in the IED there is a negative SPA response
(NAK) number 6. If the value is rejected by the Modbus object then the negative SPA
response number is 8. A successful writing is positively acknowledged.
Writing the value “1” to the Modbus coil address 2052. If the SPA channel is 0, the
channel number is omitted in the command message:
>25WO2052:1:CC
<25A:CC
Writing the value “7” to the Modbus register address 9051:
>25W1O9051:7:CC
<25A:CC
3.5.5 SPA events
The MOM + MCD bits available on the Modbus interface in the IED detect the fast
indication data transitions. It is possible to receive also SPA events from the IED
interface. The SPA events are derived from user enabled Modbus events.
Every Modbus indication data can separately be enabled to produce a time tagged
event on either both its transitions (ON-OFF) or only on the activating transition (ON).
If this is done, then the Modbus events are automatically converted to SPA events for
the SPA interface. The Modbus/SPA events need not to be enabled for the MOM +
MCD operations to work. The Modbus/SPA event generation can be optimized to
include only the required events.
3.5.5.1 Event outlook
Events include a normal SPA time stamp, in seconds and milliseconds. The event
channel is the Modbus register address on which the indication bit resides. The event
Section 3 1MRS757645 B
Vendor-specific implementation
68 620 series
Communication Protocol Manual