User Manual
Chapter 4
GFK-2849A
Oct 2019
System Operation
88
Functional
Constraints
Identifier
Operation Variable Examples
S4_SR350_DevSR350.XCBR1_Pos.ctlMo
del_CF.WRITERslt
S4_SR350_DevSR350.XCBR1_Pos.ctlMo
del_CF.ReadVal
Description
†[DC]
Direct Map
IEC 61850 - Configurator
SR350.DevSR350.MMXU1/A.net/d[DC]
PLC Protocol Variable(s)
S4_SR350_DevSR350.MMXU1_A_net.d_
DC[32]
Parameters
†[SG]
Direct Map
IEC 61850 - Configurator
Dev.IEDDevice.PTOV1/TmMult/setMag.f[
SG]
PLC Protocol Variable(s)
S8_Dev_IEDDevice.PTOV1_TmMult.setM
ag_f_SG
(+)
–
This refers to the PPV which have †.ReadVal extensions
(x)
–
This refers to the PPV which are represented as array. E.g. string data types
4.4.3
Read Operations
The PPVs created as described in the section above can be monitored and used in the
application logic as normal symbolic variables.
4.4.4
Write Operations
WRITE Operation
You can perform the write operations to IED from the RX3i controller in two steps:
1.
Write the command value to the specified value
variable (†.WRITEVal)
2.
Force a rising edge to activate the operation in a specified command variable
(†.WRITECmd).
3.
Check the result of operation is in specified result
variable (†.WRITERslt).
The above steps can be performed in RX3i controller application using ladder logic.
For each att
ribute with FC=SP/SV/SE/CF, as seen in the “
”
dialogue, Machine Edition automatically creates a set of PPVs in the PACSystems Machine
Edition project with the extensions shown below:
a.
†.
WRITEVal
(Value to be written: Type
–
Write)
b.
†.WRITECmd
(Command to transfer value in †.WRITEVal to device: Type –
Write)
c.
†.WRITERslt
(Result of operation
–
BUSY, ERROR,DONE : Type
–
Read)
d.
†.ReadVal
(Value of parameter read from device: Type
–
Read)
WRITE Operation Example
The example below is for attributes with FC=SP, used for write operation: