Pcom - Phase Communication - Siemens Moore 353 User Manual

UM353-1

3.2.76 PCOM - Phase COMmunication

The Phase Communication PCOM function block, in
firmware 1.30 and higher, is available on a one per loop
basis to enable communication with a higher level
device, such as a PC running a batch management
software program. When the controller configuration is
structured such that logic operations are partitioned in
small phase operations, the PCOM block facilitates the
interface between the logic controlling the overall phase
operations for the batch and the logic performing the
control logic for each phase.
The logic performed by the PCOM block is detailed in
Boolean form in Figure 3-1. Network communication
can be either Modbus or LIL (Local Instrument Link).
Details are listed in the Network Communications
section. The LOOP # configured in the ODC or ODS
function block for the loop determines the location of
the status word and the status coils in the Modbus
mapping. Communication states are represented in
Figure 3-1, on the next page, using the symbols shown
below. Modbus states are mapped in coils and LIL
states mapped into two 16-bit status word as shown
below. Three global channels are used to send out the
two status words and an integer value from 1-7 that
represents the status of the PCOM block: 1=ABORTED,
2=DONE, 3=HELD, 4=RUN, 5=INTRLK, 6=READY, 7=EMER OR. The location of the first channel is
configured using the LIL CHAN parameter, represented by channel z in the LIL mapping tables.
Read/Write States
Each communication state is read as a 1 or 0. Using Modbus, a write of a 1 (W1) or a 0 (W0) will affect the
communication state as defined by the associated logic in Figure 3-1. The W1 or W0 is equivalent to a Mask ON or
a Mask OFF using LIL commands. All unconfigured inputs will be treated as low (0) except OK, RD, RN and HE
which will be treated as high (1). Three of the output states, EO ("EMERG"), IK ("INTRLK"), and FD
("FAILED") can be configured for priorities 0-5. This will affect the flashing, etc. as previously described for other
controller status conditions. These states also have unacknowledged bits as detailed in status word 2. Conditions
that require acknowledging can be acknowledged by either using the local faceplate ACK button or by writing to
the individual not acknowledged bit or the Not Ack'd PCOM bit.
BIT 15 14 13 12 11 10 9
1
R R R
0
R R R
Status Word 1
March 2003
Read States
R 0
START
W 1
W 0
8 7 6 5 4 3 2 1 0
R R W W W R/W W W R/W R/W
R R R R R R/W R R R/W R/W
Phase COMunication
PCOM
EO
Emerg. OR Phase
Communication
INT_OK OK
PF
Phase_Fail
RD
ReaDy
RN
RuN
HE
HEld
DN
DoNe
L I L C H A N
LIL CHANnel ........................ 008 to 253
P
E O R I O R
Emerg. Override PRIORity ... 0,1,2,3,4,5
I K P R I O R
InterlocKed PRIORity ........... 0,1,2,3,4,5
D F P R I O R
Device Fail PRIORity ............ 0,1,2,3,4,5
I P U E O
N T
INPUT EO ............
I N P U T O K
INPUT OK ............
U
I N P T P F
INPUT PF ............
I N P U T R D
INPUT RD ............
I N P U T R N
INPUT RN ............
P U
I N T H E
INPUT HE ............
I N P U T D N
INPUT DN ............
E S N
Exec. Seq. No. .................... 000 to 250
RUN
R 1/0
BIT 15 14 13 12 11 10 9 8
1
R R
0
R R/W
Status Word 2
Function Blocks
EO Emerg. OR
IK
InterlocKed
FD
FaileD
RS
ReSet
EN
ENabled
ST
STart
HO
HOld
(null)
(4)
(4)
(4)
loop tag.block tag.output (null)
loop tag.block tag.output (null)
loop tag.block tag.output (null)
loop tag.block tag.output (null)
loop tag.block tag.output (null)
loop tag.block tag.output (null)
loop tag.block tag.output (null)
(000)
7 6 5 4 3 2 1 0
R R R R R R
R/W R/W
R/W R R R
3-79