Power Up Initialization; Configuration - Siemens 353 User Manual

UM353-1B
General Purpose Function Blocks are also designated as LOOP function
blocks and include blocks that do not fall into the arithmetic or logic categories.
These can be used as many times as needed and each use will automatically be
assigned a unique name (e.g. HLD01, HLD02) within each loop so that the
unique block name becomes <loop>.<block> (e.g. TC2053.HLD01).
Ethernet Function Blocks are used as needed within a LOOP for
communication over Ethernet. They will automatically be assigned a unique
name (e.g. AIE01, DIE01) within each loop when it is configured so that the
unique block name becomes <loop>.<block> (e.g. TC2053.AIE01).

1.2.2 Power Up Initialization

The Siemens 353 will retain, in the station NVRAM, calculated block values (e.g. outputs, elapsed time, last
input/output logic states), including the time since power was lost. Three power-up modes are used in the 353: hot,
warm, and cold. These affect the initialization of function blocks and are configured by two power up timers (warm
and cold), included in STATION parameters. The station will initialize a hot start when power up occurs prior to
the expiration of the warm timer. A cold start will occur when power up occurs after the expiration of the cold
timer and a warm start will take place when the station powers up after the expiration of the warm timer but prior to
the expiration of the cold timer.
Hot Start - All function block execution continues from the last state prior to a power fail.
Warm Start - Function blocks that have a power up in a last state feature, either by design or by configuration
selection, will power up as defined in the individual block descriptions. All other function blocks will initialize at
cold start conditions.
Cold Start - All function block outputs will initialize at 0 unless otherwise stated in individual block descriptions.

1.2.3 Configuration

The Siemens 353 can be configured either locally or remotely. Local configuration is accomplished through the
controller faceplate. The local faceplate includes buttons located behind a flip-down door for complete
configuration including the addition/deletion of loops and function blocks and the editing of function block
parameters. The local faceplate is required to enter an address in the controller so network communication can take
place. Section 2 Configuration Overview includes a road map for stepping through configuration. Certain block
parameters (e.g. gains, constants) can be edited while on-line but design changes (e.g. block interconnections, block
additions) will put the station in "configuration hold" which will hold outputs at the current value until the Exit
button is pressed. This will enable bumpless changes to be made while on-line. Note that new blocks will be
initialized at default values which may affect final outputs.
Remote configuration can be accomplished through several methods. A configuration
can be created on a PC running i|config and downloaded to a controller by way of: (1)
the port on the underside of the local faceplate, (2) a network connection at the
controller rear terminals, either Modbus or Modbus/TCP Ethernet, or (3) a
MultiMediaCard (MMC). During a download, the controller will hold all outputs and
it will retain all intermediate calculations by all blocks it was running prior to the
download. After the download, all function block parameters with the same tag name
as those held will be used to initialize the downloaded function block parameters, thus
providing a bumpless download under these conditions. If a loop tag name is changed,
the tag names of all function blocks within that loop will change and will, therefore,
require re-initialization of all of these blocks. However, the loop tag can be changed from the local faceplate
without causing re-initialization, providing a bumpless tag change.
April 2012
Introduction
HLD_ ESN = 000
HOLD O1
Output 1
AIE_
OR Output OR
ANALOG INPUT
Output O1
O1
ETHERNET
Output QS
QS
Optional PC-Based
Graphical Configuration Utility
1-5