UM353-1
Function Blocks
March 2003
3-65
3.2.65 ODC - Operator Display for Controllers
ODC
blocks are one of five operator displays that are used on
a one per loop basis to configure the local operator display
functions and network parameters from a remote operator
workstation associated with the loop. See the i|ware PC
faceplate on the next page.
The following features are in firmware 1.30 and higher.
1. A new parameter, VIEW OD, when set to YES, the
default setting, enables the operator display to be viewed
and accessed locally using the LOOP button. In some
cases, it may be desired to view only display or operation
parameters with a network workstation and not allow
operation or viewing of the control loop from the local
display. Here the parameter should be set to NO.
2. Output LE is high (1) when a loop event is active. Output
SE is high when a station error is active.
3. The LOOP # (this parameter was MB INDEX in version
1.21) is used to index reads and writes to Modbus
parameters. The LIL has 25 parameters: C1S, C2S, C3S,
..... C25S. When an ODC block has been selected and
the LOOP # has been configured, the corresponding C#S
LIL parameter will contain the LIL starting Chan (n)
location. The LOOP# must be entered to enable either
LIL or Modbus communications.
Range pointers for both the process/setpoint and valve
bargraphs must be configured to define the range of the
variable inputs to P, S, and V. If these parameters are not
configured, the bargraphs will be scaled using the engineering
range of 0.00 to 100.00. The range pointer for X and Y
define the displayed decimal point position and the units code.
This information also defines the scaling of the loop
information provided to a remote workstation over the
network (i.e. Modbus or LIL).
Input variables P, S, V, X, and Y are shown in the numeric display, using the engineering UNITS and the preferred
DPP of the range pointer. The Total from the BATOT will also be displayed when configured within the BATOT
block. If a value is greater than allowed by the DPP parameter, the decimal point will be shifted to allow the display
to show the full number, until it exceeds the maximum available digits, at which time it will indicate over range.
When input U1 or U2 goes high (1), the 8-character user status (U_STATUS) will be displayed as configured by the
status priority (U_ PRIOR). A priority of 0 will disable that status function setting the bits in the status word to 0.
See Section 9 Operation for a description of display actions using priorities 1 to 5.
The horizontal bargraph can be selected as direct or reverse acting. This feature allows it to always indicate an
OPEN valve when fully lit. The labels on the basic faceplate are fixed, but paste on labels can be used to change the
indications. The V NET AC parameter allows the LxVI network parameter to be set for direct or reverse action.
This enables the valve bar on the HMI to operate similar to the valve bar on the faceplate. The left and right bar
labels should be set accordingly (e.g. Left = “OPEN & Right = CLOSE).
An operator display must be configured to map controller loop data to network data. Loop network data is mapped
into registers or coils when the standard Modbus interface is used and to channels/parameters when the optional LIL
interface has been added. Mappings for both Modbus and LIL are listed in the tables included in the ‘Network
P
rocess
OPERATOR DISPLAY for CONTROLLERS
PF
P
ulse of
F
ODC
P
S
V
U1
S
etpoint
V
alve
U
ser Status
2
P
ulse o
N
INPUT X
(H)
.........................
loop tag.block tag.output (null)
U2
INPUT V
(H)
.........................
loop tag.block tag.output (null)
INPUT S
(H)
..........................
loop tag.block tag.output (null)
INPUT P
(H)
.........................
loop tag.block tag.output (null)
INPUT Y
(H)
.........................
loop tag.block tag.output (null)
X
Variable
X
Y
LE
L
oop
E
vent
PN
P
rocess
- R
an
G
e
P
oin
T
e
R
(S)
.........
loop tag.block tag (null)
U
ser
1
STATUS
(S)
......................... 8 Char. ASCII
(U1 STAT)
U
ser
2
STATUS
(S)
......................... 8 Char. ASCII
(U2 STAT)
H
or.
BAR
AC
tion
(S)
.................................. Rev/Dir
(Dir)
INPUT U1
(H)
.......................
loop tag.block tag.output (null)
INPUT U2
(H)
.......................
loop tag.block tag.output (null)
Variable
Y
U
ser Status
1
P
G
R
U 1 S T A T U S
P T R
G
R
P T R
V
V
alve
- R
an
G
e
P
oin
T
e
R
(S)
.............
loop tag.block tag (null)
S
U
T
A
T
S
2
U
U 1
2
U
P R I O R
P R I O R
U
ser
2
PRIOR
ity
(S)
.............................. 0,1,2,3,4,5
(5)
U
ser 1
PRIOR
ity
(S)
.............................. 0,1,2,3,4,5
(5)
H
B A R
A C
I N P U T
I
I
I
I
N
N
N
N
P
P
P
P
U
U
U
U
T
T
T
T
P
S
V
Y
X
I
I
N
N
P
P
U
U
T
T
2
1
U
U
X
G
R
P T R
Y
G
R
P T R
Input
X
- R
an
G
e
P
oin
T
e
R
(S)
..........
loop tag.block tag (null)
Input
Y
- R
an
G
e
P
oin
T
e
R
(S)
..........
loop tag.block tag (null)
OPERATOR
DISPLAY
H
H
B A R
L D
B A R
R D
H
or.
BAR L
eft
D
isplay
(S)
................. 5 Char ASCII
(CLOSE)
H
or.
BAR R
ight
D
isplay
(S)
............... 5 Char ASCII
(OPEN)
for
CONTROLLERS
CM
C
o
M
puter
C
o
N
sole
CN
NL
N
ot
L
ocal
L
ocal
O
peration
LO
WD
W
atch
D
og
C
onsole/
L
ocal
CL
E
merg.
L
ocal
EL
NETWORK
INTERFACE
I N P U T
L
C
I N P U T
L
E
INPUT CL
(H)
.......................
loop tag.block tag.output (null)
INPUT EL
(H)
.......................
loop tag.block tag.output (null)
L
O P
#
I
L
L
C H A N
LOOP #
(S)
................................................ 01 to 25
(null)
LIL
starting
CHAN
nel (n)
(H)
................ 008 to 251
(null)
VR
V
alve
R
ange
P
rocess
R
ange
PR
XR
X R
ange
YR
Y R
ange
O D
W
I E
V
VIEW
O
perator
D
isplay
(H)
........................ NO/YES YES
SE
S
tation
E
rror
O
V
N E T
A C
V
alve Bar
NET
work
AC
tion
(S)
.................. Rev/Dir
(Dir)
I
nput
A
A
Global
Alarm
Management
I N P U T
A
INPUT A
(H)
......................
Global alarm acknowledge (null)
Rev. 4
StockCheck.com
Summary of Contents for Moore 353
Page 2: ...S t o c k C h e c k c o m ...
Page 14: ...Contents UM353 1 xii March 2003 S t o c k C h e c k c o m ...
Page 24: ...Introduction UM353 1 March 2003 1 10 S t o c k C h e c k c o m ...
Page 152: ...LonWorks Communications UM353 1 March 2003 5 4 S t o c k C h e c k c o m ...
Page 164: ...Network Communications UM353 1 6 12 March 2003 S t o c k C h e c k c o m ...
Page 246: ...Operation UM353 1 March 2003 9 8 S t o c k C h e c k c o m ...
Page 254: ...Controller and System Test UM353 1 March 2003 10 8 S t o c k C h e c k c o m ...
Page 282: ...Circuit Description UM353 1 March 2003 13 4 S t o c k C h e c k c o m ...
Page 298: ...Model Designation and Specifications UM353 1 March 2003 14 16 S t o c k C h e c k c o m ...
Page 302: ...Abbreviations And Acronyms UM353 1 15 2 March 2003 S t o c k C h e c k c o m ...
Page 304: ...Warranty UM353 1 W 2 March 2003 S t o c k C h e c k c o m ...