Siemens Moore 353 User Manual page 17

UM353-1
When even more I/O is needed for multiple-loop applications, advanced control, or batch sequencing, a remote I/O
option board that uses the popular LonWorks protocol can be installed. This LonWorks board provides
connectivity via a high-speed digital fieldbus to a large selection of standard I/O products: analog inputs and outputs
and digital inputs and outputs using relay or solid state technology.
Although the Moore 353 can be connected to and operated entirely from a central operator workstation, such as
i|station, a controller faceplate is included. This local operator interface is for applications where loops need
individual attention during startup, troubleshooting, maintenance, or emergency conditions. The convenient
faceplate layout and sophisticated software allow process and configuration changes to be made quickly and easily.
The controller can be completely configured from the operator faceplate or, as mentioned above, configured
remotely using i|config™, the optional PC-based Graphical Configuration Utility. An optional Real Time
Clock/Configuration Board (RTC/CB) is available to quickly transfer a configuration from one controller to another
when downloading a configuration over a network is not available. The RTC/CB also provides a real time clock
function.
Network communication options are listed in the following table.
Protocol (Select One)
Modbus
Local Instrument Link
Ethernet
Modbus communication is standard. An optional Local Instrument Link (LIL) network board is available in place of
the Modbus communication to provide higher speed networking and peer-to-peer communication between
controllers. This provides connectivity with an array of network-enabled products, including those listed below.
Current Controller Models
Procidia i|pac Internet Control System
Moore 352P Single-Loop Digital Controller
An optional Ethernet board is available in place of Modbus and LIL communication. This option enables peer-to-
peer communication between Moore 353 controllers, Procidia i|pac controllers, and many other devices that feature
Ethernet (embedded Modbus RTU protocol). Ethernet communications requires an Ethernet board and controller
firmware V2.4 or higher.
The Ethernet board supports uploading and downloading of controller configurations over the Ethernet LAN. For
example, if i|config Graphical Configuration Utility software is loaded on the local client shown in Figure 1-2,
controller configurations can be developed on the client, or uploaded from the controller for editing, and then
downloaded to the controller. Data can also be acquired from remote servers for the purpose of archiving and/or
data mining. The Ethernet-Modbus Bridge in Figure 1-2 accepts an Ethernet data command from the controller and
outputs an equivalent Modbus command to a Modbus device at address 1. The returning Modbus data is embedded
by the bridge in an Ethernet packet to be sent to the requesting controller.
Regardless of the selected communication option, the RS232 port on the underside of the Display Assembly will
communicate using Modbus. Controller hardware architecture is designed to accommodate other emerging fieldbus
technologies. This includes field communications that require lower power for intrinsic safety and higher speed for
interplant networking.
For small retrofit applications, the Moore 353 with operator faceplate is a replacement for a simple stand-alone
single-loop controller. It is easily upgraded with additional I/O and communication options for advanced control
strategies and plant networking.
March 2003
Available Connection
Standard Rear Terminals, NCA and NCB
Optional Rear Terminals, NCA and NCB
Optional Rear Panel, RJ-45 (requires case option 4)
Previous Controller Models
Model 352 Single-Loop Digital Controller
Model 351 Triple-Loop Digital Controller
Moore 354/354N Universal Controllers
Model 382 Logic and Sequence Controller
Introduction
Option Board Needed
None
LIL Communication
Ethernet Communications
1-3