Pcs73wlvl100sp1b en Us
Pcs73wlvl100sp1b en Us
Basic principles 2
Faceplates 3
Industrial controls
Functions for all blocks 4
SENTRON
PCS 7 Library SENTRON 3WL/3VL Diagnostics block
5
DIA_WLVL
V10.0 SP1
Driver block Drv3WLVL 6
Programming and Operating Manual
Templates 8
Sample Project 9
Maintenance Station 10
Hardware configuration 11
Technical Data A
Troubleshooting B
Abbreviations C
05/2025
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance
are required to ensure that the products operate safely and without any problems. The permissible ambient
conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens Aktiengesellschaft. The remaining trademarks in
this publication may be trademarks whose use by third parties for their own purposes could violate the rights of
the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
1 Cybersecurity information..................................................................................................................... 7
2 Basic principles ...................................................................................................................................... 9
2.1 Information on data protection ............................................................................................ 9
2.2 Product specific security information .................................................................................... 9
2.3 Supported hardware ............................................................................................................ 9
2.3.1 Supported hardware ............................................................................................................ 9
2.3.2 I/O configuration................................................................................................................ 10
2.3.3 Hardware configuration ..................................................................................................... 10
2.4 Configuration steps ............................................................................................................ 13
2.4.1 Configuring in HW Config ................................................................................................... 13
2.4.2 Configuring in CFC ............................................................................................................. 16
2.5 Components of the software package ................................................................................ 17
2.6 Modifying the System during Operation via HCiR in Redundant CPU configurations ............. 18
2.7 Driver generator ................................................................................................................ 20
2.7.1 Generate Module Drivers.................................................................................................... 20
2.7.2 Object lists and action lists ................................................................................................. 21
2.8 Example configurations...................................................................................................... 22
2.8.1 3WL/3VL PROFIBUS and PROFINET configuration ................................................................. 22
2.8.2 3WL/3VL PROFIBUS configurations...................................................................................... 22
2.8.2.1 3WL/3VL PROFIBUS configurations...................................................................................... 22
2.8.2.2 3WL/3VL configuration on Master system ........................................................................... 22
2.8.2.3 3WL/3VL configuration behind Link system......................................................................... 23
2.8.3 3WL PROFINET configuration.............................................................................................. 25
2.8.3.1 3WL PROFINET configuration.............................................................................................. 25
2.8.3.2 3WL PROFINET devices with Y-Switch ................................................................................. 40
2.9 Update an existing PCS 7 project ........................................................................................ 45
2.10 Further documentation...................................................................................................... 45
3 Faceplates ............................................................................................................................................ 47
3.1 Faceplates ......................................................................................................................... 47
3.1.1 Faceplates - Structure......................................................................................................... 47
3.1.2 Views ................................................................................................................................ 50
3.1.2.1 Batch view ......................................................................................................................... 50
3.1.2.2 Trend view ........................................................................................................................ 51
3.1.2.3 Alarm view ........................................................................................................................ 52
3.1.2.4 Memo view........................................................................................................................ 53
3.1.3 Scalable faceplates............................................................................................................. 56
3.1.4 Displaying user configured status display and Text at Block icon & Faceplate........................ 59
3.1.5 User login based Operations............................................................................................... 63
3.2 Central color management................................................................................................. 64
These I/O configurations are taken into account for the 3WL air circuit breaker:
• Outputs: 2 control bytes
• Inputs: 2 status bytes and 12-byte, 26-byte or 42-byte measured values.
With the 3WL, these configurations correspond to the basic type 1, basic type 2 or basic
type 3.
The start addresses of inputs and outputs must be located in the process image partition that
is assigned to the watchdog interrupt OB in which the Drv3WLVL driver block is called.
If you link the 3WL air circuit breaker via PROFINET IO, you have to use basic type 3.
For Additional Information, Please refer the following links on the internet.
• (https://support.industry.siemens.com/cs/document/109763831)
• (https://support.industry.siemens.com/cs/document/21478942)
Note
The 3WL / 3VL must be configured as "DPV1" slave.
Figure 2-5 Properties of the 3WL / 3VL directly connected to the DP master system
If the 3WL / 3VL is operated in an H system downstream of a DP/PA-Link, the 3WL / 3VL must
be configured as a DPV0 slave. All acyclic services and interrupts are deactivated. This means
that the device no longer outputs diagnostic interrupts and data records can no longer be
read from the device. To find how this affects the blocks' behavior, see the chapters:
• Diagnostics block DIA_WLVL (Page 97)
• Driver block Drv3WLVL (Page 101)
• Breaker block Cb3WLVL (Page 111)
The AddrIn input parameter of the template is assigned with the corresponding input of the
logical address of the device (LAddr).
hp
jZ~s}s
Procedure
Configuring with HW Config:
1. Configure the 3WL/3VL circuit breaker at HW config.
2. Open CFC-Editor.
3. Instantiate the Cb3WLVL template from the library PCS 7 3WLVL Lib V100 SP1 >
Blocks+Templates\Templates > Select Cb3WLVL template, drag and drop it to the CFC chart.
4. Refer to the input address of the 3WL/3VL circuit breaker at HW Config and assign this address
to the "Input parameter AddrIn of the Cb3WLVL template".
Compile the CFC chart using the "Generate Module Driver" function.
Refer "Using templates (Page 191)" for further information on interconnections.
Reference
Additional information is available in the "Process Control System PCS 7 Compendium Part A -
Configuration Guidelines" Operating Manual on the Internet (https://
support.industry.siemens.com/cs/document/109809015).
Note
• There might be a QCsf momentarily triggered and reset at Drv3WLVL block during
changes/new device configuration.
• On Internal PROFINET IO system:
– For CPU 41x: Plant changes cannot be made on PROFINET IO systems.
– For CPU410x: CPU410x series only support for Internal PN configurations.
• On External PROFINET IO system:
– For CPU 41x: Plant changes cannot be made on PROFINET IO systems.
• As mentioned in CP 443-1 manual CPU410-5H and CPU410E will not support operation of
the CP as PROFINET IO controller.
• IEPB LINK PNIO does not support CiR functionality.
• For Further information on MRP, S2 redundancy, PROFINET CiR/H-CiR; please refer the below
document "PROFINET in SIMATIC PCS 7 - Guidelines and Blueprints".
Modifying the System during Operation via CiR in Standard CPU configurations
Note
• For CPU 41x: Plant changes cannot be made on PROFINET IO systems.
• As mentioned in CP 443-1 manual, CPU410-5H and CPU410E will not support operation of
the CP as PROFINET IO controller.
• IE/PB Link PN IO does not support CiR functionality.
• For CiR download, CPU410x series only supports Internal PN configurations.
For further information refer Modifying the System during Operation via CiR from the
following link. (https://support.industry.siemens.com/cs/document/45531308)
Note
To have similar behavior between this library and the PCS 7 Basis Library, a PCS 7 Basis Library
version supporting this functionality needs to be installed as well.
Reference
1. You will find the GSD files for 3WL/3VL PROFIBUS and PROFINET from the following links on
the Internet.
– (https://support.industry.siemens.com/cs/document/21478942)
– (https://support.industry.siemens.com/cs/document/109763831)
2. Additionally,you can find the relevant information by visitng the SIOS link (https://
support.industry.siemens.com) and search for
– 3WL 3VL GSD
– COM35 GSDML
3. Under Downloads click the relevant entry,
e.g., "PROFINET GSDML files: GSDML-file for COM35 of the Air Circuit Breaker 3WL" or
"PROFIBUS GSD files: GSD Files for SENTRON 3WL and 3VL".
4. This displays another Internet page where you can download the GSD/GSDML files.
Description
The object lists and the action lists are used to generate the module drivers for these hardware
modules.
The object list contains a unique object identification number for each of these hardware
modules. Each object list is assigned to a particular hardware configuration.
The action list contains a list of actions. These actions must be executed for the object
identification numbers that appear in the object list. Examples of such actions include:
• Assigning the device address
• Interconnecting the input and output parameters of the driver block
The "Generate Module Driver" function generates the module drivers when the CFC is
compiled.
Note
3VL device does not support PROFINET.
The 3WL/3VL PROFIBUS and 3WL PROFINETdevices along with their associated components
are inserted and configured in HW Config.
The following graphics show example configurations of 3WL/3VL at HW Config in the Netpro
View.
On DP Master System (DP Inter‐ Behind Y-Link (DP Interrupt- mode Behind IE/PB Link PN IO
rupt mode as DPV1) using as DPV0) using and IE/PB Link HA
• GSD file • GSD file • GSD file
Note
The 3WL/3VL must be configured as "DPV1" slave.
3WL PN Configurations
PROFINET port monitoring settings are made mandatory. When multiple devices are connected
to the CPU/CP card interface, used and unused PROFINET port settings are required to distinguish
between actual Rack failure and Device Failure.
When multiple devices are connected to the PROFINET interface, then the following settings
needs to be done.
In CPU
1. In Port 1 of the PROFINET interface, the "Transmission medium" should be automatic and the
"Monitor" checkbox needs to be activated as shown in figure.
2. In Port 2 of the PROFINET card, the "Transmission medium" and the "Monitor" checkbox needs
to be disabled as shown in figure.
In Device
Similarly, the "Transmission medium" should be automatic and the "Monitor" checkbox needs
to be activated for Port1 and Port 2 of all the 3WL devices (see figure) except for the last
device in the network loop where Port 2 should be disabled as shown in figure.
These settings are applicable in both internal PROFINET interface of the CPU and external
PROFINET interface of CP Card.
When multiple devices are connected in MRP configuration, then the topology below with
the required port settings needs to be done as given below
• In Port 1 and Port 2 of the CPU PROFINET interface and the 3WL devices, the “Transmission
medium” should be automatic and the “Monitor” checkbox needs to be activated.
• At the Media redundancy tab the role of the MRP configuration should be set to manager for
CPU and should be set as client for 3WL device
Note
Watch dog time of the each device in MRP loop must be > 200 ms.
Watch dog time can be changed by varying "Number of updated cycles with missing IO data
setting".
Note
For S2 redundancy behind Y-Switch MRP configuration is necessary.
Note
Watch dog time of the each device in MRP loop must be > 200 ms.
Watch dog time can be changed by varying "Number of updated cycles with missing IO data
setting".
Note
WinCC tools can be used to make necessary modifications to the faceplates.
Structure of a faceplate
Icons
Overview window
The overview window shows the overall status of the block:
① Group display:
Indicates whether unacknowledged alarms and warnings are pending.
② LOCK status for messages, authorization level 5 and higher
③ Message suppression1
3)
The symbol appears at the overview window in Cb3WLVL when Read Data is suppressed.
4)
The symbol appears at the overview window of the Cb3WLVL when there is Read or write
failure.
5)
The symbol appears at the overview window of the Cb3WLVL when write protection is
active.
6)
User defined icons appears when one or more bits of first 8 bits of UsrStat2 bits are high.
The expanded command area can be programmed with a 2- or 3-level access concept
for the operator. The access can be changed in the WinCC Explorer using the internal
@APLCommandExecutionSteps variable.
Level 2: The operator only needs to press the command to execute.
Level 3: The operator must also press the OK button to execute the command.
Authorization levels
Some commands are subject to permission with authorization levels via WinCC. The
authorization levels are updated when a view is opened. The user can only execute the
commands that are enabled for him.
The authorization levels are created for the project by means of a user ID.
Reference
The configuration of faceplates and icons follow the standards of the Advanced Process Library.
For more information about this and authorization levels, refer to Function Manual "Process
Control System PCS7, PCS7 Advanced Process Library V10.0" on the Internet.
3.1.2 Views
Batch view
This area shows a display of the batch that is currently running (Batchview).
You can use the internal tag "@APLBatchEnable" to enable/disable the "Batch" button in the
toolbar.
Value of @APLBatchEnable Operating the "Batch" button in the Icon of the "Batch" button in the tool‐
toolbar bar
0 Disabled
1* Enabled
① Enabled This area shows you if the block is enabled for operation via SIMATIC BATCH
(BatchEn) (Status1.Bit1)
② Allocated This area shows if the block is currently in use by SIMATIC BATCH
(Occupied) (Status1.Bit0)
③ Batch name This area shows the name of the batch that is currently running
(BatchName)
④ Batch ID This area shows the identification number of the batch that is currently run‐
(BatchID) ning (BatchID).
The batch view is disabled if BatchID = 16#00000000.
⑤ Batch step This area shows the step number of the batch that is currently running.
(StepNo)
Trend view
For additional information about the trend view, refer to the WinCC Information System
Online Help.
Alarm view
For additional information about the alarm view,refer to the WinCC Information System
Online Help.
Memo view
Note
• Files that are configured for NoteView should be saved with UTF-8 encoding. This is
applicable to all the intermediate files also, before they are converted to .MHT files.
• Jump instruction within the file in NoteView window will not work in the OS Client, Web
Server and Web Client.
• No permission levels are required for combo box and open button in the APL_Memo.PDL.
① Window Title: indicates the title of Window and name of the file opened as well.
② NoteView display area: displays content of the selected file.
③ Indicates the loading status of the selected MHT document
Note
• This window cannot be resized but it is movable.
• This window is not supported by the "screen composition" functionality.
All the .MHT files (NoteView documents) should be placed in the "OS project path\GraCS
\NoteView". In case of a Multi project, server holds all these files and these files are not
available in the client.
Error Handling
• If selected file is not found in the folder path, an error message is shown as “File not found”.
• If configured file format is other than MHT, an error message is shown as "Invalid file format".
• If selected file is more than 25 MB and if tried to open same, an error is shown as “File size
exceeds 25 MB”.
• If file name length exceeds 32 characters, an error is shown as "File name length exceeded
32 characters".
The next time the faceplate is opened or there is a process picture change, you can see in the
status bar of the block icon and the faceplate that there is a new message for you.
Clearing the check box deletes the indicators in the status bars.
Note
The content of the memo view is cleared when you perform a full compilation and download of
the OS.
Note
Faceplate must be reopened after changing the scale value. Already opened faceplate cannot be
scaled up if the scale value is changed.
Example: The screenshot below shows the faceplates scaled up by providing the value of
200, scaled down by providing the value of 50 for the internal variable.
3.1.4 Displaying user configured status display and Text at Block icon & Faceplate
The following file names with respect to the specified bits must be used for the EMFs to
display with UsrStat2 active bits.
Note
If two or more bits of the UsrStat2 input are true, then the user configured status will be
displayed for the bit corresponding to the highest bit.
Note
• If no Text is entered in the “Text 1” of the UserDig1 and UserDig2, then by Default
"UserText1" and "UserText2" will be displayed in Text field.
• If both the UserDig1 and UserDig2 inputs are true, then the text configured at UserDig2
will be displayed.
Note
Audit level is not enabled for Fast operations and 2 step operation and for locking/unlocking
message in via "Lock Messages" button in faceplate overview.
1. SIMATIC Logon must be enabled.
2. The Audit Level operation is only possible with the 3- step operation.
3. Internal tag "@APL_AuditEnable" should be set to 1.
4. For further information on Audit Levels and their functionality, please refer to the APL manual
on the internet.
The Audit Level is available for the below parameters at the Cb3WLVL block/faceplate:
For more information on Operator Trend Control (AOTC), please refer Section "APL
Operator Trend Control (AOTC)" at the Advanced Process Library Function Manual. (https://
support.industry.siemens.com/cs/document/109973505)
① Selection of states : This area displays all possible states of the function blocks. All state icons are
shown in their respective status group frames. The group name is displayed in the tooltip when the
mouse pointer is hovered in the area between the state icon and the group frame. You can select/
deselect one or more states from any status group by clicking the icon. The status information of the
selected states is displayed in the status area. The following states are displayed in this area:
Operating mode
Out of service
On mode*
Manual mode
Automatic mode
Program mode*
Local mode
Setpoint
Internal setpoint*
External setpoint*
Ramp active*
Signal status
Manipulated value
Bad, device-related
Bad, process-related
Uncertain, device-related
Uncertain, process-related
Maintenance request
In progress
Forcing*
Bypass
Interlock
Interlock active
Interlock disabled
Rapid stop*
Reset request
Memo
Active memo
Messages
Locked message
Suppressed messages
Block status
Internal simulation*
Internal error
Group error
3.5.3 Overview of the "PCS 7 Measuring point browser" for Maintenance station
① Selection of states : This area displays all possible maintenance state/Job of the function blocks. All state icons are
shown in their respective status group frames. The group name is displayed in the tooltip when the mouse pointer is
hovered in the area between the state icon and the group frame. You can select/deselect one or more states from any
status group by clicking the icon. The status information of the selected states is displayed in the status area. The
following states are displayed in this area:
Maintenance status
Unchecked/unknown
Maintenance alarm
Maintenance demand
Maintenance required
Local operation
Simulation*
Out of service
Passivated
Configuration change*
Good
Locked messages
Maintenance job
MA alarm demanded
MA demand requested
MA required demanded
Maintenance status
Completed
Canceled
In maintenance
Release request
Planned maintenance
MA not started
② Selection of areas : This area displays the top folders of the plant hierarchy. You can select/deselect one or more areas.
The status information from the selected areas is displayed in the status area.
③ Opening the faceplate : Double-click a row in the status area to open the corresponding faceplate.
④ Status area : This area shows the list of blocks with their corresponding "Type", "State", and "Area" depending on the
"Selection of states" and "Selection of areas".
Reference
You can obtain further information on the organization blocks in the "Process Control System
PCS 7 System Functions" manual and in the system and standard functions reference manual for
S7-300/400 on the internet (https://support.industry.siemens.com/cs/document/44240604).
"X" = The 3WL/3VL library block calls this block, "–" = the 3WL/3VL library block does not call this block.
Block Parameter
Cb3WLVL GrpErr.Value
L1Cur.ST
LocalLi.ST
OffLocal.ST
OnLocal.ST
Icons
The icons for the Quality Code are displayed in the block icon and in the overview window of the
faceplates.
Reference
You can obtain further information on the Quality Code display, in the PCS 7 libraries APL
Styleguide programming manual in the Internet (https://support.industry.siemens.com/cs/
document/65601446).
Note
1. Any parameter change with an initial write must have a valid read call executed, which can
be checked with latest timestamp at the faceplate.
2. After full download or a warm restart, the write function would require a successful read
execution.
Dynamic reset:
To prevent loading of CPU work memory, the handling of temporary errors has been
enhanced such that the maximum count of these repetitive calls is configured by the input
parameter ReSFxTrCnt/RESFXTRCNT (Drv3WLVL/DIA_WLVL), beyond which the error is
reset by terminating the RDREC/WRREC/RDSYSST call dynamically with a return code 16#7000
at the output parameter RDSYSSTAT/RdStat/WrStat.
If the return code is not equal to 16#7000 then the termination will be repeated for the
number of user configured cycle times at the input parameter ReSFxFlCnt/RESFXFLCNT
(Drv3WlVL/DIA_WLVL).
Reset:
Reset can be triggered irrespective of temporary/permanent error, if the user wants to make
sure that the block RDREC/WRREC/RDSYSST call is not occupying the CPU work memory.
For Drv3WLVL block, reset can be performed for RDREC/WRREC by setting input parameter
• CallRst = Reset
For DIA _WLVL block, reset can be performed for RDSYSST by setting input parameter
• CALLRST = Reset
Note
This Feature bit has no function in "out of service" mode. The process tag remains in "out of
service" mode following warm restart of the CPU.
Note
The restart routine of the blocks resets the following trip point outputs in the OB100 execution:
• CLx_Ax_Act
• CLx_Wx_Act
This causes an outgoing message on initialization of the Alarm8_P in OB100, and an incoming
message following expiry of the RunUpCyc counter at the cyclic interrupt level.
Note
In the case of full download with AS stop, the blocks (for Feature.Bit0 = 1) cannot continue
to run in their previous mode following restart.
Default setting: 0
Bit = 0: The status "In progress" is displayed in the faceplate of the assigned technological block
and in the block icon (see below). A 0-1 edge change of the OosLi input parameter has
no further effect on the behavior of the technological block. The previous state is re‐
tained. No change is made to "out of service" mode.
Bit = 1: A switchover to "Out of service" mode is made provided the block is in "Manual mode".
If this requirement is not met, the mode does not change. The "In progress" status is
displayed in the faceplate of the assigned technological block and in the block icon
regardless of the change of operating mode. No message is output, whether the mode
has been changed or not.
A 1-0 edge change of the input parameter OosLi has no effect on the behavior of the
technological block. The previous state is retained.
Bit = 0: The block does not reset the control commands. If two control commands for
switching the operating mode are active, the operating mode is not changed. In
this case, the text "Invalid signal" appears in the faceplate.
Bit = 1: The block resets the control commands. This ensures, for example, that the con‐
trol command is reset automatically when exiting a step when controlled from the
SFC.
Bit = 0: The block does not reset the switching commands. If two commands for control are
active, the state of the control is retained. In this case, the text "Invalid signal" appears
in the standard view of the faceplate.
Bit = 1: The block resets the switching commands. This ensures, for example, that the control
command is reset automatically when exiting a step when controlled from the SFC.
4.9.5 Set switch or pushbutton mode (input signal as pulse signal or steady-state
signal)
Feature bit
Number of the Feature bit: 4
You use this Feature bit to select whether the mode switchover between "manual mode" and
"automatic mode" and the switching command is made with a control input (switch) or with
two 1-active control inputs (pushbuttons).
The Feature bit affects the following control inputs:
• Mode switchover (parameter AutModLi and ManModLi)
• Switching commands "Off" and "On" (parameter OffAut and OnAut)
Default setting: 0
Bit = 0: Pushbutton Every automatic command is assigned a control input. This is latching
mode: and is 1‑active.
Mode:
• AutModLi = 1 for setting "Automatic" mode
• ManModLi = 1 for setting "Manual" mode
Switching commands:
• OffAut = 1 for the switching command "Off"
• OnAut = 1 for the switching command "On"
Bit = 1: Switch Two steady-state automatic commands are assigned to one control
mode: input.
Mode:
• AutModLi = 1 for setting "Automatic" mode
• AutModLi = 0 for setting "Manual" mode
Switching commands:
• OnAut = 0 for the switching command "Off"
• OnAut = 1 for the switching command "On"
The inputs ManModiLi and OffAut have no effect.
Note
As the control bytes and the switch state are different with the 3VL and the 3WL, the switch type
must be defined using this Feature bit.
Default setting: 0
Bit = 3VL
0:
Bit = 3WL
1:
Bit = 0: Deactivated
Bit = 1: Activated
Note
The configuration data are read out via acyclic services. Since only 8 cyclic services can be run
simultaneously on each PROFIBUS line, the execution can be delayed considerably. This can be
the case, for example, if all devices are reading out their configuration data at the same time
after a return of the PROFIBUS line. If more than eight devices are using the acyclic services, we
recommend that Feature bit 8 not be set. Instead, update the configuration data in the faceplate
via the parameter view or the specific measured value view after a change.
Default setting: 0
Bit = 0: The configuration data is not read out automatically on restart of the controller
(OB100) and rack restore (OB86). After the data has been changed, it must be read
out via the parameter view in the faceplate.
Bit = 1: The configuration data is read out automatically on restart of the controller (OB100)
and rack restore (OB86).
4.9.9 Reset via input signals in the event of interlocks (protection) or errors
Feature bit
Number of the Feature bit: 9
You use this Feature bit to define how automatic control is to be enabled again following an
outgoing interlock.
Default setting: 0
Bit = Exiting "local mode" in manual mode (bumplessly, since the control signal can be
0: tracked).
Bit = Exiting "Local mode" in the last operating mode active before "local mode" (with bump).
1:
You can find further information in the description of "local mode" of the standard APL blocks.
Bit = 0: Deactivated
Bit = 1: Activated
Default setting: 0
Bit = 0: Bumpless switchover is deactivated. Switchover from "local mode" / "manual mode"
to automatic mode is possible at any time.
Bit = 1: Bumpless switchover from "local mode" / "manual mode" to "automatic mode" is
activated. Switchover from "local mode" / "manual mode" to automatic mode is only
possible if the control of "local mode" / "manual mode" and "automatic mode" agree.
If a switchover takes place at another time, this is indicated in the faceplate with the
text "Mode switch fail".
You use this Feature bit to define the behavior of the block when an interlock signal of an
interlock block is excluded or simulated.
Default setting: 0
Bit = Switch-relevant excluded and simulated interlock signals are processed with the status
0: 16#60. They are displayed as either simulated or excluded, depending on the interlock
status.
Bit = Excluded and simulated interlock signals are evaluated separately. All excluded inter‐
1: lock signals of a sequence of interlock blocks are displayed as excluded. Switch-relevant
simulated interlock signals are processed with status 16#60, and they are displayed as
simulated.
Bit = Deactivated
0:
Bit = Activated
1:
Default setting: 0
Default setting: 0
Default Setting: 0
You use the Feature2 bit to define whether or not the diagnostic warning "µP error" is
to be suppressed, i.e. whether it is to be taken into account when generating the general
HMI message "A warning is currently present".
Default setting: 0
4.9.35 Suppress of the diagnostic warning “Short time mean value current”
Feature2 bit
Number of the Feature2 bit: 9
If the diagnostic warning "Short time mean value current" is pending for the device, the
general message "A warning is currently present" is displayed on the HMI. In the "Diagnostics"
faceplate, the
pending/triggered diagnostic warnings can be read out precisely.
You use the Feature2 bit to define whether or not the diagnostic warning "Short time
mean value current" is to be suppressed, i.e. whether it is to be taken into account when
generating the general HMI message "A warning is currently present".
Default setting: 0
Bit = Deactivated
0:
Bit = Activated
1:
Bit = Last state of the Limit violation active output before switching to the "Out of service"
0: mode is retained.
Bit = The state of the Limit violation active output is reset to "Good"
1:
4.9.38 Disable limit act output when limit value message is disabled
Feature2 bit
Number of the Feature2 bit: 12
You can use the Feature2 bit to disable the limit value act output (CLX_XX_Act) when the
limit value message (CLX_XX_MsgEn) is disabled.
Default setting: 0
Bit = 0: Limit active output is not disabled when limit value message is disabled.
Bit = 1: Limit active output is disabled when limit value message is disabled.
Operating principle
The DIA_WLVL block handles the diagnostics of the 3WL / 3VL circuit breakers. The diagnostic
information of the 3WL / 3VL are forwarded to the block Drv3WLVL. The DIA_WLVL block forms
the quality code (signal status) of the 3WL / 3VL and forwards this to the Drv3WLVL block.
Configuration
When the CFC function "Generate module driver" is used, the following is carried out
automatically:
• The DIA_WLVL block is integrated into OB1, OB40, OB70, OB72, OB82, OB83, OB85, OB86
and OB100 in its runtime group after the runtime group of the OB_DIAG1 block.
• Parameters are assigned for the inputs SUBN1_ID, SUBN2_ID, SUBN_TYP, RACK_NO,
DPA_LINK and PNIODVC.
• The logical start address LADDR of the device is parameterized.
• The diagnostic address DADDR of the device is parameterized.
• The EN and RACKF inputs are interconnected to the EN_F, QRACKF and SUBN1ERR
outputs of the upstream block OB_DIAG1 / OB_DIAG1_PN.
• The input DIAG_REQ is interconnected with the output DiagReq of the Drv3WLVL block.
• The SUBN1ACT input is connected to SUBN1ACT output of the upstream block OB_DIAG1/
OB_DIAG1_PN.
• The output QUALITY is interconnected with the input ST of the Drv3WLVL block.
• The output QDIAG_INF is interconnected with the input DiagInf of the Drv3WLVL block.
Startup characteristics
The module ID of the addressed DP slave is read out. It is hereby checked whether this module
ID matches the configured module ID. If this is not the case, the output QMODF (module fault) is
set.
In the case of interfacing via PROFINET IO, a check is made as to whether the addressed PN
device exists. If this is not the case, the output QMODF (module fault) is set.
Higher-level errors
If a higher-level module fault is active at the input RACKF, the output QRACKF is set.
Module faults
If an incorrect module ID of the connected module is read out by the block, the output QMODF is
set.
Group errors
If one of the previously listed errors is active, or maintenance is requested, the output QERR is
set.
Input parameters
In/out parameters
Output parameters
Operating principle
The block reads and writes cyclically all cyclic data of a 3WL / 3VL circuit breaker from and to the
process image.
The block reads and writes acyclic data of the 3WL / 3VL circuit breaker from and to the device.
Configuration
Integrate the block in the CFC editor into a cyclic interrupt OB, for example into OB30 to OB38.
When the CFC function "Generate module driver" is used, the following is carried out
automatically:
• The member variables of the input structure Addr are parameterized with the addresses
configured in HW Config. The input Addr.BasicType contains the number of the basic type
used. The input Addr.Input receives the input address of the 3WL / 3VL, and the
input Addr.Output the output address of the 3WL / 3VL.
• The inputs DiagInf and ST are interconnected with the outputs QDIAG_INF
and QUALITY of the upstream diagnostic block DIA_WLVL.
• The input MS is interconnected with the output O_MS of the upstream MOD_SWT/MOD_SWTL
block.
• The in/out parameters Mode, DataXchg and DataXchg1 are interconnected with the
outputs OMODE_00, DXCHG_00 and DXCHG1_00 of the upstream MOD_SWT/MOD_SWTL
block.
• The output DiagReq is interconnected with the input DIAG_REQ of the upstream DIA_WLVL
diagnostics block.
A template for the process tag types is available for the Drv3WLVL driver block in the library:
• Template Cb3WLVL
Startup characteristics
The RDREC/WRREC call temporary error counters will be reset to 0 during the CPU warm restart.
The following measured values are available for the basic types 2 and 3:
The following measured values are only available with basic type 3:
When the write operation has been completed with or without errors, the block copies the
number of the data record to the output AcyclData.RdyWrite, and the return value of
the WRREC call to the output tag AcyclData.RetValWr and WrStat output parameter.
You can find the meaning of the return values in the online help of the WRREC block.
If an error occurs, the values are set to the old values and the output WrErr = 1 is set.
Higher-level errors
A higher-level error is displayed with 1 at an output parameter QCsf:
• If the signal status in the HighWord of the MODE input parameter takes a value different from
16#80
• If the input Csf is set
Input parameters
In/out parameters
Output parameters
Operating principle
The Cb3WLVL block receives measured data and diagnostic data from the driver blocks of the
3WL / 3VL circuit breakers. The Cb3WLVL block prepares this data and makes it available for
further use in the user program and for visualization.
The circuit breaker can be switched on and off via the control signals.
Different inputs are available for control. You can find further detailed descriptions about
configuring, the operating principle, visualization and operation in the following chapters.
Note
The block resets the control commands in case of control system fault at the block or when the
breaker is unavailable.
Configuration
Integrate the block in the CFC editor into a cyclic interrupt OB (OB30 to OB38). In addition, the
block is integrated automatically into the startup OB (OB100).
To connect the I/O signals, the Drv3WLVL driver block (cyclic and acyclic data of the circuit
breaker) has to be called in the same cyclic interrupt OB before the Cb3WLVL breaker
block. The output structures CyclData and AcyclData of the Drv3WLVL driver block are
interconnected with the same-name inputs of the Cb3WLVL breaker block.
A template for the process tag types is available for the Cb3WLVL block in this library:
• Template Cb3WLVL
Startup characteristics
You define the startup characteristics for this block via the Feature bit "Setting the startup
response".
After startup, the messages are suppressed for the number of cycles parameterized in the
RunUpCyc value.
"Local mode"
In "Local mode", you can transfer the following commands to the circuit breaker:
• "Off": positive edge OffLocal
• "On": positive edge OnLocal
If you put the block in "Local mode", only the "local" signals of the circuit breaker influence
the control (input parameter. OffLocal = 1, OnLocal = 1).
Note
In contrast to the general description, only the values 0, 1 and 3 can be set at the
parameter LocalSetting. Tracking in "Local mode" is not possible with the Cb3WLVL block.
"Automatic mode"
In "Automatic mode", you can transfer the following commands to the circuit breaker:
• "Off": positive edge OffAut
• "On": positive edge OnAut
"Manual mode"
In "Manual mode", you can transfer the following commands to the circuit breaker:
• "Off": OffMan
• "On": OnMan
• "Acknowledge TRIP": AckTripOp
• "TRIP" / Reset mechanical off": ResTripOp
• "Reset Maintenance Information and Counters": RMSinfoOp
"Out of service"
You can find general information on "Out of service" mode in the online help of the APL blocks.
Note
Make sure to start the "Read configuration data" once. This ensures that the displayed data are
up-to-date.
With a positive edge at the RdDataLi.Value input, the acyclic measured values and
diagnostic data are read once. You will find the acyclic measured values in the table below
from "Current unbalance" to "Temperature in circuit breaker" (data record 94). You will find
the diagnostic data below in the table from "Modules connected to the CubicleBUS" to
"Threshold warnings" (data record 92).
Note
As long as the acyclic measured values are being read via the RdDataLi input, "Read
configuration data" cannot be triggered in the faceplate or via the Feature.bit8.
The DataRdOK.Value output is set when the acyclic measured values and the diagnostic
data have been successfully read. The DataRdOK.Value output is reset when reading of the
acyclic measured values and the diagnostic data is started.
The Cb3WLVL breaker block has the following configuration data with the corresponding data
record number in the 3WL / 3VL circuit breaker:
* The measured values are only read if they are not already available via the cyclic data of the 3WL / 3VL
circuit breaker.
For more information, refer to the section "Reading cyclic values from process image" in the
chapter"Reading cyclic values from the process image" (Page 102)
• OffLocal.ST
• OnLocal.ST
Group errors
The following parameters are taken into account for forming the group error GrpErr:
• CyclData.Csf
• FaultExt
For this block, the following characteristics are available to you at the relevant bits of the
"Feature2" I/O:
Operator permissions
This block has the standard function "Operator permissions". The operator permissions are
described in the online help of the APL blocks.
The block has the following permissions for the parameter OS_Perm:
Bit Function
0 1 = Operator can switch to "Automatic mode"
1 1 = Operator can switch to "Manual mode"
2 1 = Operator can switch to "Local mode"
3 1 = Operator can switch to "Out of service" mode
4 1 = Operator can switch the breaker off
5 1 = Operator can switch the breaker on
6 1 = Operator can acknowledge TRIP
7 1 = Operator can reset TRIP / Mechanical Off
8 1 = Operator can reset all maintenance information and counters
9 1 = Operator can reset the monitoring error
Bit Function
10 1 = Operator can change current L1 alarm high limit
11 1 = Operator can change current L1 warning high limit
12 1 = Operator can change current L1 hystersis
13 1 = Operator can change current L1 warning low limit
14 1 = Operator can change current L1 alarm low limit
15 1 = Operator can change current L2 alarm high limit
16 1 = Operator can change current L2 warning high limit
17 1 = Operator can change current L2 hystersis
18 1 = Operator can change current L2 warning low limit
19 1 = Operator can change current L2 alarm low limit
20 1 = Operator can change current L3 alarm high limit
21 1 = Operator can change current L3 warning high limit
22 1 = Operator can change current L3 hystersis
23 1 = Operator can change current L3 warning low limit
24 1 = Operator can change current L3 alarm low limit
25 … 26 Reserved
27 1 = Operator can read the configuration data
28 1 = Operator can write the configuration data
29 1 = Operator can switch on the function "Release for maintenance"
30 1 = Operator can reset "Protection".\
31 Reserved
The block has the following permissions for the OS1Perm parameter:
Bit Function
0 1=Operator can activate/deactivate current L1 alarm high message
1 1=Operator can activate/deactivate current L1 warning high message
2 1=Operator can activate/deactivate current L1 warning low message
3 1=Operator can activate/deactivate current L1 alarm low message
4 1=Operator can activate/deactivate current L2 alarm high message
5 1=Operator can activate/deactivate current L2 warning high message
6 1=Operator can activate/deactivate current L2 warning low message
7 1=Operator can activate/deactivate current L2 alarm low message
8 1=Operator can activate/deactivate current L3 alarm high message
9 1=Operator can activate/deactivate current L3 warning high message
10 1=Operator can activate/deactivate current L3 warning low message
11 1=Operator can activate/deactivate current L3 alarm low message
Display and operator input area for current and limit values
The high and low limiting of the current values and limit values in the faceplate are defined by
the parameterization at the structured variable Cur_OpScale.
Sending commands
These commands can be sent regardless of the operating mode of the Cb3WLVL block:
• "Delete trip and event recording list" (positive edge DTripRcLi.Value)
• "Reset the minimum / maximum values" (positive edge RMiMaxLi.Value)
• "Reset the minimum / maximum values for temperatures" (positive edge RTempLi.Value)
All commands remain for one second in the in/out parameter CyclData.BrCtrl. If the
same command is sent again during this time, it will be lost.
State diagram
The block has the following states:
• "Off"
• "On"
• "TRIP"
• "Not ready"
A state change takes place via the commands:
• "Switch on"
• "Switch off"
If the breaker state is not defined, the circuit breaker is in "Not ready" state.
Switching is only possible if there is no interlock.
2Q
2II
75,35HVHW
① Function:
• Protection trip
• Test function
Figure 7-1 State changes
Monitoring of feedback
If the Feature.bit11 is activated, the command for switching on, switching off and reset
TRIP / Mechanical Off are time-monitored.
If the expected state is not reached within the monitoring time MonTime after an operation,
the block outputs a message and outputs the text "Monitoring" in the standard view of the
faceplate.
The circuit breaker cannot be switched on and off via the Cb3WLVL block as longs as the
block is in the error state MonErrAct = 1.
You must reset the monitoring error in the standard view of the faceplate.
Interlocks
This block has the following interlocks:
• Switch on permission
• Interlocks without reset ("Interlock")
• Interlocks with reset ("Protection")
You can find more detailed information in the online help of the APL blocks in the chapter
"Interlock".
Note
Unlike the general description, the rest position of the Cb3WLVL breaker block is the same
position as the 3WL / 3VL circuit breaker before the interlock. An interlock of the Cb3WLVL
breaker block does not lead to a switching operation.
"Disabling interlocks"
This block has the standard function "Disabling interlocks", which is described in the online help
of the APL blocks.
The bumpless switching from "Local mode" to "Automatic mode" is performed via the
parameter LocalSetting. You can find more detailed information in the online help of
the APL blocks in the chapter "Local mode".
In the standard view of the faceplate, the text "Mode switch fail" is output in the case of
undesired changeover with bump.
When the operator initiates the switching from "Local mode" to "Automatic mode" and the
above described fault occurs, the block remains in "Local mode". When interconnected inputs
initiate the switching from "Local mode" to "Automatic mode" and the above described fault
occurs, the block is switched to "Manual mode".
Auxiliary value
The MsgStat1, MsgAckn1, and MsgErr1 parameters transfer the following information:
• Message status
• Message error
• Message acknowledgment status
*W = Warning
*S = AS, OS process control fault
*A = Alarm
Auxiliary value
The MsgStat2, MsgAckn2 and MsgErr2 parameters transfer the following information:
• Message status
• Message error
• Message acknowledgment status
Auxiliary value
The MsgStat3, MsgAckn3 and MsgErr3 parameters transfer the following information:
• Message status
• Message error
• Message acknowledgment status
Auxiliary value
The MsgStat4, MsgAckn4 and MsgAckn4 parameters transfer the following information:
• Message status
• Message error
• Message acknowledgment status
Note
The command button is disabled in the below conditions:
1. When there is a control system fault at the block.
2. When the device is disconnected/unavailable.
(7) Operator input area for the interlock functions of the block
You operate the interlock functions of the block using these buttons. You can find more
detailed information in the online help of the APL blocks in the chapter "Interlocks".
• "External fault"
• "Internal error"
Note
The limit set point values are not written to the device, but still, the limit parameterization
is disabled during the following conditions
1. Device is in out of service mode
2. Device is disconnected/unavailable
Note
The read data button is disabled in below conditions
1. When read call is suppressed
2. During device is in out of service mode
3. When device is disconnected/unavailable
4. During RDREC call execution / termination.
5. During WRREC call execution / termination.
The Reset maintenance info./counters is disabled in below conditions:
1. When device is in out of service mode.
2. When device is disconnected/unavailable.
(3) Service
In this area, you activate the following functions:
• "Reset maintenance information and counters"
• "Release for maintenance"
You can find more detailed information in the online help of the APL blocks in the chapter
"Release for maintenance".
① Automatic preview
② Display of the currently active monitoring time
③ Enabled operations
④ Displaying current control signals
• "Local Off":
– 1 = Circuit breaker is switched off in "Local mode"
• "Local On":
– 1 = Circuit breaker is switched on in "Local mode"
• "Bypass protection":
– 0 = Bypass deactivated
– 1 = Bypassing of the interlock in "Local mode"
Note
These signal will be displayed irrespective of block mode.
⑤ Enabled operations
⑥ Last successful Timestamp of read data
Note
The read data button is disabled in below conditions
1. When read call suppressed
2. During device is in out of service mode
3. When device is disconnected/unavailable
4. During RDREC call execution / termination.
5. During WRREC call execution / termination.
If the 3WL / 3VL circuit breaker is connected in an H system downstream of a DP/PA-Link, this
area is not displayed.
The following long-term mean values are displayed:
• Long-term mean value current L1 (is only displayed for the 3WL)
• Long-term mean value current L2 (is only displayed for the 3WL)
• Long-term mean value current L3 (is only displayed for the 3WL)
• Long-term mean value 3-phase average current
Note
The read data button is disabled in below conditions
1. When read call is suppressed
2. During device is in out of service mode
3. When device is disconnected/unavailable
4. During RDREC call execution / termination.
5. During WRREC call execution / termination.
(3) Displaying tripping reason and tripping reason in case of extended protection
function
This area shows you the actual tripping reason and the tripping reason of the extended
protection function.
If a 3VL circuit breaker is used, this area is not displayed.
Following tripping reasons can be displayed.
• Overload tripping (L)
• Instantaneous short-circuit trip (I)
• Short-time delayed short-circuit trip (S)
• Ground-fault tripping (G)
• Tripping operation as a result of extended protection function
• Overload trip in neutral conductor (N)
Following tripping reasons can be displayed in the case of extended protection function:
• Phase unbalance current
• Phase unbalance voltage
• Imported active energy
• Exported active energy
• Overvoltage
• Undervoltage
• THD current
• THD voltage
• Change of phase rotation
Note
The read data button is disabled in below conditions
1. When read call is suppressed
2. During device is in out of service mode
3. When device is disconnected/unavailable
4. During RDREC call execution / termination.
5. During WRREC call execution / termination.
Note
The read data button is disabled in below conditions
1. When read call is suppressed
2. During device is in out of service mode
3. When device is disconnected/unavailable
4. During RDREC call execution / termination.
5. During WRREC call execution / termination.
Note
The read data button is disabled in below conditions
1. When read call is suppressed
2. During device is in out of service mode
3. When device is disconnected/unavailable
4. During RDREC call execution / termination.
5. During WRREC call execution / termination.
Note
The read data button is disabled in below conditions
1. When read call is suppressed
2. During device is in out of service mode
3. When device is disconnected/unavailable
4. During RDREC call execution / termination.
5. During WRREC call execution / termination.
(3) Displaying long-term mean value of 3-phase reactive power including signal status
This area shows you the actual long-term mean value of the 3-phase reactive power with the
relevant signal status.
You can find additional information on the block icon and the operator input options in the
following chapters of the online help of the APL blocks:
• "Configuring the block icons"
• "Structure of block icon"
• "Operator input using the block icon"
Symbol Meaning
It is not known whether the 3WL / 3VL circuit breaker is open or closed.
The 3WL air circuit breaker is in connected position and has tripped.
The 3WL air circuit breaker is in test position and has tripped.
Symbol Meaning
The 3WL air circuit breaker is absent.
Input parameters
* The block algorithm can write back values to these inputs during the processing of the block.
In/Out parameters
Output parameters
To edit the template, right-click on the template and select "Open" from the shortcut menu.
The template is opened as a CFC chart.
Manual interconnections
Note
Assigning the starting logical address is sufficient to start the driver generation, through which
the “AddrIn” values are passed to the other dependent blocks.
Automatic interconnections
If the option "Generate Block Driver“ is activated in the "Compile Program" dialog,
interconnections that are not yet available but that are necessary will be automatically executed.
Template of Cb3WLVL
A chart I/O type is used to connect a 3WL / 3VL circuit breaker with the driver blocks on PCS 7.
The Drv3WLVL driver block transfers the cyclic and acyclic values of the 3WL / 3VL circuit
breaker from and to the device.
The Drv3WLVL driver block is connected to the Cb3WLVL breaker block via the structures
AcyclicData and/or CyclicData.
The process tag type contains the necessary interconnections between the blocks named
above.
To instantiate the template, the AddrIn input of the Drv3WLVL template must be
parameterized with the start address of the inputs of the 3WL / 3VL circuit breaker.
Note
For more information on setting up a Maintenance Station refer to the Function manual of PCS
7 Maintenance Station.
Configuration
1. Open the plant view in the SIMATIC Manager.
2. Select the object in the tree view:
– If you are using a multiproject, select the object "[name of the project] MP".
– If you are using a single project, select the object "[name of the project]".
3. Select the menu command Options > Plant Hierarchy > Settings.
5. Click "OK". The "Define Maintenance Station" dialog box opens and all OS’s available in the
multiproject, project are shown.
6. Select the OS you want to define as Maintenance Station.
7. Compile the CFC charts with "Generate Module Driver" setting enabled before creating
diagnostics screens. (If not it will show a popup for module error generation).
8. Once the CFC is compiled, generate diagnostic screen by selecting Options > Plant Hierarchy
>Create/Update Diagnostic screen.
• Overview of the SENTRON Devices screen is given below : Diagnostics > Field Devices >
Profinet_IO_System which tells the entire device identification information.
• Maintenance view allows the user to set the new maintenance job and to plan the existing
jobs. The Maintenance Release option in this window will get enabled when the operator
puts the device into maintenance state, after which the maintenance operator can carry out
maintenance of the device.
Good - -
Message is locked - -
Good - -
Message is locked - -
Messages
Messages for an incoming Signaling, Warning and Tripping event can be found using:
For more information on "Correlation maintenance state and maintenance job" refer to PCS 7
Maintenance Station Function Manual.
Terminal assignment
The figure below shows the inscription on the COM35, the external terminal assignment for
connecting the closing coil, the shunt release, write protection via communication, and the free
input/output.
&XELFOH%86
:ULWH )UHH )UHH &ORVH 2SHQ
,1 (QDEOH 287
< ))
([WHUQDO
,QWHUQDO
Note
Observe the polarity.
Note
COM35 input and output are rated for use with 24 V DC maximum.
'&9 '&9
ZULWH
HQDEOH
)UHH&ORVH2SHQ
;;
;
;
;
;
;
;
;
;
;
;
;
;
&20
0
(78
) <
Note
The Write Enable input (terminals 1 & 2) must be connected together to allow remote
configuration. Without this jumper, remote commands to change parameters, open/close, etc.,
will be ignored by the COM35.
The figure below shows the wiring if contacts are installed with voltages not equal to 24 V DC.
• Interposing/coupling relays must be used.
• If F1 is not used for switching off, the connection points X5:11 / X5:12 must be connected
for F2 to F4.
/
1
'&9 '&9
ZULWH
HQDEOH . .
. .
)UHH&ORVH2SHQ
;;
;
;
;
;
;
;
;
;
;
;
;
;
&20
0
(78
) <
RJ45 connection
The figure below shows COM35 from behind. It shows the RJ45 connection for the external
CubicleBUS modules. If no external CubicleBUS module is connected, the bus must be
terminated with the terminating resistor supplied.
Table 11-1 Terminal strip connection X8 between COM35 and CubicleBUS nodes
When the input is open (delivery condition of the COM35), write protection is active and
modifications and actions are always locked.
&XELFOH%86
:ULWH )UHH )UHH &ORVH 2SHQ
,1 (QDEOH 287
< ))
([WHUQDO
,QWHUQDO
&XELFOH%86
:ULWH )UHH )UHH &ORVH 2SHQ
,1 (QDEOH 287
< ))
([WHUQDO
,QWHUQDO
Temporary protection
• Door switch
To protect service personnel during maintenance work, it is possible to prevent the circuit
breaker from being operated via communication while the switchgear door is open.
• Selector switch
It is possible to put a selector switch in the switchgear door. In this way, you can choose
whether remote operation/parameterization will be possible or whether you would like to
prevent or permit it temporarily.
• Security
The write protection is a very secure way of preventing impermissible operation and
modification of parameters. You can temporarily enable (if you require it yourself) or disable
remote operation/parameterization by a second independent path (e.g. by the CPU).
Contact 1 / 2:
Write protection is integrated in COM15 to interlock the switching operations of the circuit
breaker. This protection does not permit commands which put switching operations at risk.
Write protection on COM15 therefore has to be released via pin 2 in order to switch on or off.
The simplest version is depicted and takes the form of a wire jumper between 1 and 2
without customer-specific release (in released representation).
Contact 4 / 5:
These "User" contacts are used to control the magnets for the anti-pumping device and/or trip
detection. (The circuit breaker should be fitted with the "Remote reset magnet for the display
and reset button, including automatic resetting of the anti-pumping device")
Contact 6 / 7:
The "Close" / "Motorized operating mechanism for spring energy store" contact is used to
close the circuit breaker and controls the Y1 switch-on solenoids and the automatic charging
of the circuit breaker. (The circuit breaker should be fitted with the "Manual operating
mechanism with mechanical and electrical call, switch-on solenoid suitable for uninterrupted
duty, 100 % ED")
Contact 8 / 9:
The "Open" contact is used to switch off the circuit breaker and controls the F1 switch-off
solenoid. (The circuit breaker should be fitted with the "Shunt release suited to uninterrupted
duty, 100 % ED")
11.3.2 24 V DC voltage
Note
The contact between WE and 24 V must be closed for the remote function! Without this wire
jumper, the PROFIBUS-DP cannot be used to switch the SENTRON VL on or off.
More information on fitting the motorized operating mechanism can be found in the
installation instructions for the motorized operating mechanism.
Connection diagram for COM20 on motorized operating mechanism, SENTRON VL:
Table A-1 Memory space requirements and called blocks per block type
Block 1 No. 2 Length of Length of Length of in‐ Length of in‐ Temporary Blocks called4
block in the block in the stance data in stance data in memory, in
load work memory, the load mem‐ the work bytes3
memory, in in bytes 3 ory, in bytes 4 memory, in
bytes 3 bytes4
DIA_WLVL FB1742 5972 5202 670 202 398 SFB54,
SFC50,
SFC51,
SFC6,
SFC64
Drv3WLVL FB2595 8690 7450 1678 804 68 SFB52,
SFB53,
SFC6,
SFC64
Cb3WLVL FB2596 36138 31384 5414 1972 158 SFB35,
FC260,
FC369,
SFC20,
SFC24,
SFC6,
SFC1
1
The symbolic designator in the symbol table of the library for the respective function block (FB). It must be unique within the
project.
2
Consists of the type of block (FB) and the number.
3
Memory requirement of program code, once per block type
4
Memory requirement for an instance data block.
5
The memory required for the local data when the block is called in an execution level. This is limited according to the specific
CPU. If this amount is exceeded, you must check the setting in the CPU configuration and redistribute it among the
organization blocks based on the actual requirement.
6
The relevant driver block uses these blocks. They are now located in the user program. They are stored in the same library.
* Since PO Count is defined as "-1", AS RT PO licenses is not consumed for any blocks. After CFC compilation, during download,
the total number of PO's are booked depending on the utilization of the CPU memory.
Note
Refer FAQ for more information on "How are the licenses for the AS and OS counted in PCS 7 V7.0
onwards?" on the internet (https://support.industry.siemens.com/cs/document/38855207).
Note
After successful debugging of the SFB/SFC calls DebugInf parameter should be disabled to
reduce the consumption of work memory.
After successful reset the input parameter DebugInf value is enabled.
Parameters Function
Parameter Description
Req 1= SFB/SFC call is executed.
0 = SFB/SFC call is terminated.
Busy 1= SFB/SFC call is in busy state (i.e.. return code is equal to 16#7001 or
16#7002)
Error 1= SFB/SFC call is in error state (i.e return code = 16#80xx)
Dyn_Rst 1= Dynamic reset executed for SFB/SFC call
Brkn_Call 1= Broken call detected
Reset 1= exclusive reset is executed
RecNum Indicate the data set number for read/write operations.
Index Updates SZL_ID during the RDSYSST call execution (Req := true) or SFC termi‐
nation (Req := false)
Status The actual return status output of the RDREC/WRREC/RDSYSST call.
TrueCnt The counter value will increase by 1 during SFB/SFC call request (Req :=True).
FalseCnt The counter value will increment by 1 during SFB/SFC call termination request
(Req := False).
Note
For more information on SFB/SFC call handling, refer (Page 75)
Abbreviation Meaning
AS Automation station
APL Advanced Process Library
CFC Continuous Function Chart
CiR Changes in Run
CPU Control processing unit
DP Distributed Peripherals
ES Engineering Station
FB Function block
GSD Generic Station Description
GSDML General Station Description Markup Language
HW Config "Hardware configuration" module in SIMATIC Manager
ID Identification number
MA Maintenance
MS Maintenance Station
OB Organization block
OS Operator Station
PCS 7 Process Control System 7
SFB System function block
SFC System function call
RDREC Reading a Data Record
WRREC Writing a Data Record
RDSYSST Read system status
A W
Approved modifications Write protection
Write protection, 216 Approved modifications, 216
Locked modifications, 216
Temporary protection, 218
C
Circuit breaker
Closing/opening, 212
COM35
Components, 212
Connections, 212
CubicleBUS, 211
Disable write access, 215
RJ45 connection, 215
Terminal assignment, 211
Terminal strip connection, 215
Wiring, 212
Write protection application, 216
CubicleBUS
COM35, 211
Node, 215
D
Disable write access
COM35, 215
L
Locked modifications
Write protection, 216
N
Node
CubicleBUS, 215
T
Temporary protection
Write protection, 218
Terminal strip connection, 215