Siemens Moore 353, Руководство пользователя

Страница: 18 / 306

Introduction UM353-1
March 2003 1-4
Ethernet
|
4 2 . 4 5 3
TC2 0 5 3 . P
PB1
PB2
A
M
AC K
L
S
D
UNITS
LOOP
S P
CLOSE OPEN
0 100 | | |
20
40
60
80
100
0
2
X 03141 S2
Moore 353
s
Multiple Moore 353 and Procidia i|pac Nodes,
each with an Ethernet Network Board.
Internal Web Server
Intranet
M
G
00
38
8
a
Local Client
P1
P3
1 3 5 7 9 1 1 1 3 1 5 1 3 5 7 9 1 1 1 3 1 5 1 3 5 7 9 1 1 1 3 1 5
P4
Ethernet-Modbus
Bridge Foreign Device with
Modbus Communications
Modbus
|
4 2 . 4 5 3
T C2 0 5 3 . P
PB1
PB2
A
M
AC K
L
S
D
UNITS
LOOP
S P
CLOSE OPEN
0 100 | | |
20
40
60
80
100
0
2
X 03141 S2
Moore 353
s
FIGURE 1-2 Ethernet Architecture Example
Often in this publication, reference is made to the labels on the controller to ensure that the controller being installed
has the correct power input, I/O, communication options, and approvals. This is particularly important when non-
incendive requirements are present or a critical process is involved where a custom configuration or calibration has
been created. Label locations are shown in Figure 1-1 and typical labels are shown in Section 14 Model Designation
and Specifications.
1.2 FUNCTION BLOCKS
Controller software is built on proven function block designs from previous LIL products and from Siemens
APACS® products that support the IEC1131 standard. In many cases, the controller has been enhanced with
features only now possible with state of the art technology.
Function blocks are selected for use within a LOOP. Multiple loops can be configured, and each loop can be
associated with an operator faceplate. Certain blocks are used once within each loop (e.g. controller, setpoint,
auto/manual), others can be used as many times as needed. Some notable features include Auto Tuning within the
PID function blocks, an expandable Sequencer that allows configuration of up to 250 steps, and up to 256 discrete
inputs and outputs. In addition, the Graphical Configuration Utility can be used to design the logic in a ladder
diagram. Combining these features with continuous control loops within the same controller offers a well-
integrated solution for small batch operations.
Several function blocks are available at the station level for configuration of STATION level parameters, such as
the station address and station tag name. Function blocks include the CLOCK block (when the RTC/CB option
board has been included), and the ETHERNET block (when the Ethernet board has been installed and the controller
contains firmware V2.4 or higher) to configure parameters such as the IP address. All other function blocks are
used for configuration within an individual LOOP. Control implementations are configured in the Moore 353 by
first creating a loop, then entering a unique loop tag name and selecting function blocks for use within that loop. A
number of loops can be configured in the Moore 353 and a number of function block types are available as
described in the sections that follow.
1.2.1 LOOP Function Block Types
Local I/O Function Blocks are provided on both the MPU Controller Board
and the I/O Expander Board. These blocks can be used in any LOOP, but as
fixed resources are expendable. When used within a loop, the unique block
name becomes <loop>.<block> (e.g. TC2053.AIN1 for Analog Input 1 used in
loop TC2053).
AIN_+
AIN_c
O1
O utput 1
ANALOG INPUT
EXTRACTOR
AIN_
QS
Q uality S tatus
StockCheck.com