PRV Mit Webseite ACM 200 Eng Us

Configuration Process using Web Site
Clearguard ACM 200

Axle Counting System
A6Z00034626189/- Configuration Process using Web Site

2013-06-20 Clearguard ACM 200 Axle Counting System
© Siemens AG, 2013 All rights reserved Page 1 of 28
Document history
Version Release Sections Reason
date changed
- 2013-06-20 All First issue
The contents of this translation correspond to the document with the number A6Z00032502878/-.
Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of its
contents and communication thereof to others without express authorization are prohibited.
Offenders will be held liable for payment of damages. All rights created by patent grant or
registration of a utility model or design patent are reserved.
Siemens AG
Postfach 33 27
38023 Braunschweig
Germany
www.siemens.com
rail-automation.mobility@siemens.com

12.06.2013 Clearguard ACM 200 Axle Counting System
Contents
1 Information for the user.................................................................................................... 4
About this document ........................................................................................................... 4
2 Terms.................................................................................................................................. 6
Terms .................................................................................................................................. 6
3 Description of configuration process ............................................................................. 9

Description of configuration process................................................................................... 9
3.1 Definition of configuration data..................................................................................... 10
Definition of configuration data ......................................................................................... 10
3.2 Restriction of operational usage ................................................................................... 11
Restriction of operational usage ....................................................................................... 11
3.3 Loading of configuration data into ACM ...................................................................... 12
Loading of configuration data into ACM............................................................................ 12
3.4 Plan verification .............................................................................................................. 16
Prerequisites ..................................................................................................................... 16
Basis for checking ............................................................................................................. 17
Checking of configuration data ......................................................................................... 19
Response to detected deviations...................................................................................... 20
3.5 Correspondence checking and start of operation....................................................... 21
Correspondence checking and start of operation ............................................................. 21
4 Adjustment of configuration process ........................................................................... 23

Adjustment of configuration process................................................................................. 23
Requirements from axle counting system's application conditions................................... 23
Plan verification only after successful loading .................................................................. 24
5 Safety-related application conditions ........................................................................... 25

Safety-related application conditions ................................................................................ 25
6 Indices .............................................................................................................................. 28
List of abbreviations .......................................................................................................... 28
List of figures ..................................................................................................................... 28
List of tables ...................................................................................................................... 28

12.06.2013 Clearguard ACM 200 Axle Counting System
Information for the user
1 Information for the user
About this document
Scope
This document applies to the Clearguard ACM 200 axle counting system in equipment
revision level 1. The Clearguard ACM 200 axle counting system is referred to below sim-
ply as axle counting system.
Purpose
This document supports technical sales staff, configuring engineers and project staff in
performing their tasks. It defines a fail-safe process for loading configuration data onto
the ID plug of an ACM.
This documentation is part of the equipment described.

This documentation is part of the equipment described. It must be kept in a safe place
throughout the lifetime of the equipment described. Make this documentation available to
the personnel responsible for the activities described. If you receive any additions from
Siemens at a later date, insert them in the documentation.
Supplementary documents
The following documents are also important as supplementary documents:
Reference ID Title Document number

[SAV-B] Safety-related Application Conditions for Operators A6Z00034626218
Clearguard ACM 200 Axle Counting System
[OI] Operating Instructions for Diagnostic Web Site A6Z00034626292
[MI] Maintenance Instructions A6Z00034296081
[CI] Configuration Instructions A6Z00034626179
[SD] System Description A6Z00034296029
Table 1 Supplementary documents

Information for the user
Standards and guidelines

When using the configuration process described in this document, the regulations of the
railway operator and the relevant approval body must also be observed insofar as they
are relevant to the configuration of ACMs.
In addition, the following European standards or comparable national or international
standards must be observed when concretizing the configuration process (see
“Description of configuration process” on page 9) described in this document:
Standard Title
EN 50128:2001 Railway applications – Communications, signaling and processing
systems – Software for railway control and protection systems
EN 50129:2003 Railway applications – Communication, signaling and processing
systems – Safety-related electronic systems for signaling
Table 2 Standards and guidelines
Suggestions
If you have any suggestions to improve this document, please contact us. In this way, you
can benefit all users of this document. Any ideas and requests will be gratefully received.

Terms
2 Terms
Terms
Order basis
In this document, “order basis” designates all application-specific tasks, properties and
general conditions which have to be taken into account when implementing a specific
axle counting system. The order basis for a configuration to be created is mainly defined
by:
• line topology
• signal sources and signal sinks between which binary information (SRI) is to be
transmitted
Binary information (SRI, safety-related information)

Between two ACMs, up to two freely available items of binary information (SRI) can be
transmitted in a fail-safe manner. For each item of binary information, the local position of
signal source and signal sink must be known.
Element assignment
The element assignment establishes a unique allocation between the inputs, outputs and
logical elements of the used ACMs and the following physical elements:
• wheel detection equipment and track vacancy detection sections of the line topology
transmitted
The elements of the used ACMs include wheel detectors/wheel detection equipment,
track vacancy detection sections as well as signal sinks and signal sources for binary in-
formation (SRI).
To each ACM, two wheel detectors can be connected directly and eight wheel detectors
can be connected via adjacent ACMs.
In addition, each ACM can manage one of the following element combinations:
• up to two track vacancy detection sections
• one track vacancy detection section as well as one signal source and/or one signal
sink for binary information (SRI)
• up to two signal sources and signal sinks for binary information (SRI)
The result of element assignment is an assignment list.
ID plug
The ID plug is a non-fail-safe, replaceable storage medium for configuration data.

Terms
P_Daten.BCK
P_Daten.BCK designates the configuration data read out of an ACM in a readable, un-
commented representation. P_Daten.BCK can be available as a file, a printout or screen
display. P_Daten.BCK provides the verifier with the actual values for plan verification.
Plan verification
During plan verification, it is checked by means of configuration data (P_Daten.BCK)
read out of the ACM whether the configured values are permissible in accordance with
the configuration specifications and order basis.
It is clearly defined which data has to be checked as part of plan verification (see
“Checking of configuration data” on page 19).
Plan verification is only applied to configuration data in which safety-related errors in con-
junction with the cabling and spatial arrangement can be ruled out. In addition, verification
by means of correspondence checking must not be possible or must be very laborious.
Plan verification is thus applied to configuration data such as oscillation tolerance or con-
nection failure detection time.
Configuration acceptance mode

This mode is a defensive measure where no safety-related outputs are made (relays are
not controlled and SLC telegrams are not sent). Diagnostics are possible in this mode, for
example the reading of P_Daten.BCK.
Configuration process
The configuration process is to ensure that a system comprising several ACMs and wheel
detectors is only commissioned with approved and uncorrupted loaded configuration data
in accordance with the order basis. Failure to meet this target constitutes a hazard. The
configuration process must comply with the following safety objectives:
(S1) In the event of systematic faults, always at least two independent faults are neces-
sary to result in a hazardous situation.
(S2) In the event of random faults, the probability of a hazardous situation is practically
negligible per process sequence.
Configuration specifications
Configuration specifications implement, supplement or define requirements to be ob-
served when configuring systems.
This document contains all requirements which must be complied with when applying the
configuration process described in this document. Some of these requirements must be
implemented customer- or project-specifically. The other ones can be refined customer-
or project-specifically. They must appropriately implement or forward the safety-related
requirements included in this document.
Line topology
The line topology describes the spatial arrangement of tracks, points, wheel detec-
tors/wheel detection equipment and track vacancy detection sections.

Terms
Correspondence checking
Correspondence checking is performed to see whether a configured ACM implements the
behavior defined via the assignment list. However, the order basis has to be used for
checking since the configuration process does not support the usage of a verified as-
signment list.
Correspondence checking is a major part of the configuration process.
Web site
Each ACM has a web site which can be executed in an internet browser on a PC (see
also [OI]). The web site permits the following:
• read-out of configuration data from an ACM
• input or modification of configuration data
• saving of configuration data in a text or XML file
• loading of configuration data into an ACM
Assignment list
The assignment list is the result of element assignment. The assignment list defines the
relationship between the elements of the used ACMs and the following physical elements:
• wheel detection equipment and track vacancy detection sections of the line topology
transmitted

Description of configuration process
3 Description of configuration process
The figure below shows the main elements of the configuration process.
Figure 1 Overview of the configuration process using the web site

3.1 Definition of configuration data
The configuration process is subdivided into configuration steps P1 to P23. All configura-
tion steps relevant to the users of the configuration process are described below. Many
configuration steps required for safety-related reasons are realized in the ACM and are
thus not relevant to the users of the configuration process. These steps are not described
below.
3.1 Definition of configuration data
Definition of configuration data
Qualified staff: configuring engineer

The configuration data may only be defined by a configuring engineer.
The following knowledge is required for defining the configuration data:
• configuration specifications of the operator and the relevant approval body
• project-specific specifications relating to configuration
• meaning of the configuration data (see “Configuration Instructions” [CI])
• contents of the relevant railway operating rules
• basic mode of operation of the axle counting system (see “System Description” [SD])
• the specifications and execution notes of this section unless they have been re-
placed by operator- or project-specific specifications
Step P1: definition of configuration data

Step P1 is used to define the configuration data for one or more ACMs based on the or-
der basis in accordance with the configuration specifications.
Tools
To define the configuration data, the ACM provides a web site which supports data entry.
The configuration data entered via the web site can either be loaded directly into the ACM
or be buffered from the web site into a text or XML file.
The “Operating Instructions for Diagnostic Web Site” [OI] describe the functions of the
web site for editing configuration data and saving it on the ID plug of an ACM or in a text
file or an XML file.
As an option, the configuration data can also be created using a text editor or a different
tool. If these files comply with the specifications of the “Operating Instructions for Diag-
nostic Web Site” [OI], the configuration data can be read in from the web site and then
loaded into the ACM.

3.2 Restriction of operational usage
Execution notes for Step P1

The order basis for configuration data to be created is determined by the line topology as
well as the signal sources and signal sinks between which binary information is to be
transmitted.
Step Action
1 Using the order basis, establish a unique allocation between the inputs, out-
puts and logical elements of the used ACMs and the following physical ele-
ments:
• wheel detection equipment and track vacancy detection sections of the
line topology
• signal sources and signal sinks between which binary information (SRI)
is to be transmitted
The result of element assignment is an assignment list.
2 Based on the line topology, the binary information to be transmitted and the
assignment list, define the configuration data of the individual ACMs.
Definition can be on paper or in a file. Default configuration data or existing
configuration data can be used as a basis for definition.
3.2 Restriction of operational usage
Restriction of operational usage
Step P2: restriction of operational usage

Step Action
1 Before loading the configuration data into the ACM, it must be ensured that
the elements affected by the configuration modification are not operationally
used. The specifications defined by the operator for this purpose must be ap-
plied.

3.3 Loading of configuration data into ACM
Loading of configuration data into ACM
Note
The steps described in this section must be performed separately for each ACM con-
cerned.
Qualified staff
The configuration data may only be loaded into the ACM by qualified staff. The following
knowledge is required for loading the configuration data into the ACM:
• regulations of the operator and the relevant approval body relating to:
− modification of safety-related electronic railway systems or
− work on safety-related electronic railway systems
Step P3: switchover to configuration mode

Step P3 is used to switch one ACM to be configured to the configuration mode. For this
purpose, the following operator actions are required on the front panel of the ACM:
Step Action
1
WARNING
Dangerous operating conditions!
Accidents may occur if an ACM not taken out of operation by means of
Step P2 is reconfigured.
If a wrong ACM has been inadvertently set to the configuration mode, SAV-
B <PV4> and <PV5> must be taken into account.
Check whether you have selected the correct ACM. Only then change over
to the configuration mode.
Press the RST reset button for min. 2 s.

2 Hold the two RST-RR1 and RST-RR2 buttons down until the OK LED shows
a flashing yellow light.

Step P5: set-up of communication connection

Step P5 is used to set up a connection between the configuration PC and the ACM to be
configured.
Step Action
1 Connect the configuration PC to an Ethernet network via which a connection
to the ACM to be configured can be set up.
2 Start an internet browser.
Note: The web site has been tested with the Microsoft Internet Explorer (Ver-
sions 7, 8 and 9) and Mozilla Firefox (Versions 3 and 4) internet browsers.
3 Enter the current IP address of the new ACM or the ACM to be reconfigured
into the address bar of the internet browser.
Note: The IP address of the ACM is stored in a non-volatile manner on the ID
plug. When manufacturing the ID plug, the IP address is set to 192.168.2.250.
If connection set-up has been successful, the internet browser displays the
ACM web site with its log-in window after confirming the confirmation
prompts.
4 Log in as the “Configuring engineer” user to change the configuration data.
More detailed information about connection set-up, confirmation prompts and logging-in
can be found in the “Operating Instructions for Diagnostic Web Site” [OI].
Step P6: entry or read-in of configuration data into web site

Step Action
1 Enter the configuration data defined in Step P1 into the web site or read in the
data from a previously created file.
Note: The “Operating Instructions for Diagnostic Web Site” [OI] describe the
functions of the web site for editing configuration data and loading it from a
file.

Step P8: loading of configuration data onto ID plug of ACM

For starting loading of configuration data onto the ID plug of the ACM, proceed as follows:
Step Action
1 In the ATTRIBUTE CONFIGURATION DATA menu, click the SAVING AND LOADING
option.
2 In the SAVE TO section, click the ACM button.
The configuration data is then loaded onto the ID plug of the ACM.

Step P14: checking whether configuration data has been successfully loaded
Step Action
1 Check whether the configuration data has been successfully loaded onto the
ID plug of the ACM.
After successful loading, the following is the case:
• The OK LED on the ACM’s front panel shows a flashing yellow light.
• The TVDS1 to RR2 LEDs on the ACM’s front panel show a steady green
light.
• The web site confirms successful loading in an information window.
2 If the ACM indications and web site information differ from those described
above, repeat the loading process as from Step P3 or abort the process in
Step P16.
Step P15: transfer of ACM to configuration acceptance mode or normal operating mode
Step Action
1 Press the RST reset button on the ACM’s front panel for min. 2 s.
Note: This measure is to rule out any possibility that the configuration data is
overwritten inadvertently or due to a failure. Without this defensive measure,
any deviation would not be detected until the subsequent checks are per-
formed.
Step P16: response to incorrect loading

Step Action
1 If a deviation is detected even after repeated loading attempts in Step P14,
the process must be aborted.
If Rule PW3 (see “Plan verification only after successful loading” on page 24)
is to be implemented as a result of abortion, it must be ensured that the proc-
ess cannot be continued or the ACM to be configured cannot be restarted
until the configuration data has been successfully loaded onto the ID plug of
the ACM.

3.4 Plan verification
Prerequisites
NOTICE
Verification not possible during a failure!
If the OK LED on the ACM’s front panel shows a flashing or steady red light, the ACM
has failed.
Successful execution of the checks described below is only possible after having
remedied the failure in accordance with the “Maintenance Instructions” [MI].
Qualified staff: verifier

Plan verification must be performed by a verifier. The verifier must be a person different
from the configuring engineer. The following knowledge is required for plan verification:
• meaning of the configuration data (see “Configuration Instructions” [CI])
• regulations of the operator and the relevant approval body relating to work on safety-
related electronic railway systems
• regarding the safety-related electronic systems connected to the axle counting sys-
tem, their
− basic mode of operation,
− interfaces and
− safety-related application conditions
must be known, as long as this knowledge is not covered by configuration specifica-
tions of the operator or the project
Step P17: preparation of plan verification

Between the loading of configuration data into one or more ACMs and its read-back for
plan verification, memories used for buffering configuration data should be erased as a
defensive measure:
Step Action
1 Switch off all components of the transmission channel, the ACMs and the
configuration PC.
2 Switch on all components again after a few seconds.

Step P18a: ACM must be in configuration acceptance mode or normal operating mode
During plan verification, the ACM must be in the configuration acceptance mode or nor-
mal operating mode. This is the case if the OK LED on the ACM’s front panel does not
show a flashing yellow light.
Since the fail-safe processor of the ACM permits its configuration data to be modified in
the configuration mode only, you ensure by this measure that the configuration data can-
not be corrupted inadvertently or due to a failure after it has been read back.
Step Action
1 If the OK LED shows a steady yellow light (ACM in the direction changeover
mode), press the RST reset button on the ACM’s front panel for min. 2 s.
The ACM is restarted and is then in the configuration acceptance mode or
normal operating mode.
Basis for checking
Step P18b: read-back of configuration data from ACM

Step Action
1 Set up a connection between the configuration PC and the ACM to be config-
ured (see Step P5).
2 In the TOOLS menu, click the DOWNLOAD OF CHECKFILE OF ATTRIBUTE CONFIGU-
RATION DATA option.
The web site then requests you to enter a file name and select a folder. The
web site saves the read-back configuration data in the selected folder in a file
with the entered file name.
3 Select the folder for saving the read-back configuration data.
Note: If the configuration data of several ACMs is read back in succession,
the web site always suggests the folder used last. This simplification is possi-
bly not available after a restart of the configuration PC.

Step Action
4 Check and if required correct the file name for the read-back configuration
data.
Note: As a file name, the web site suggests a name consisting of the configu-
ration data items Basis_AdIP (IP address of the ACM) and Self_VP (version
of the configuration data). As long as these configuration data items are cor-
rectly set and maintained in accordance with the “Configuration Instructions”
[CI], the suggested file name permits a unique assignment of the read-back
configuration data within an operating area. For this reason, the suggested
file name should be accepted and, if required, supplemented by additional
information.
The web site then saves the read-back configuration data in a file and dis-
plays it in a separate window.
Step P20c: checking based on read-back data

Step Action
1 Make sure that the steps described below are performed based on the con-
figuration data read back in Step P18b by only performing them if the first line
of the configuration data printed out or displayed on screen includes the text
“Checkfile of attribute configuration data”.

Step P20b: unique assignment between data and ACM

Step Action
1 Make sure that for plan verification there is a unique and correct assignment
between the read-back configuration data and the ACM to be configured. For
this purpose, check the following data:
• Basis_AdIP (IP address)
• Self_VP (version of the configuration data)
• file name of the read-back configuration data (see the second line of the
read-back configuration data)
Checking of configuration data
Step P20c: checking of configuration data

Step Action
1 Perform plan verification based on the read-back configuration data.
The paragraphs below define which configuration data is to be checked as part of plan
verification. In addition, a general checking specification has been defined there for each
item of configuration data. If a project or operator defines its own checking specifications,
these must be observed.
Basis_AdIP plan verification

Step Action
1 Check whether Basis_AdIP is unique in the terms of SAV-B <PV2>.
Self_DS_SIM plan verification

Step Action
1 Check whether Self_DS_SIM is 0.
Com#_ReTi plan verification

Step Action
1 Check whether the values of this item of configuration data are permissible in
accordance with the configuration specifications and line topology.
Com#_Save plan verification

Step Action
1 If Com#_Save is 0, check whether this value is permissible in accordance
with the configuration specifications, line topology and interlocking type. Val-
ues greater than 0 are generally permissible.

TVDS#_RP and TVDS#_RR plan verification

Step Action
accordance with the configuration specifications.
TVDS#_RPS and TVDS#_RRS plan verification

Step Action
TVDS#_SelfDS#P and TVDS#_Com#DS#P plan verification

Step Action
1 If the oscillation tolerance is 1, check whether this value is permissible in ac-
cordance with the configuration specifications. The hazard resulting from the
oscillation tolerance must be tolerable, taking the line topology and general
operating conditions into account.
TVDS#_SelfDS#R and TVDS#_Com#DS#R plan verification

Step Action
RP_RED plan verification

Step Action
1 Check whether this value has been set correctly.
Response to detected deviations
Step P21: response to detected deviations

Step Action
1 Make sure that, for a deviation detected during plan verification, operational
usage of the affected elements is ruled out until the deviation has been cor-
rected.

3.5 Correspondence checking and start of operation
Correspondence checking and start of operation
Qualified staff: verifier

Correspondence checking must be performed by a verifier. The verifier must be a person
different from the configuring engineer. The following knowledge is required for corre-
spondence checking:
• regulations of the operator and the relevant approval body relating to:
− work on safety-related electronic railway systems
− work on the track
Step P22: correspondence checking

After plan verification of all ACMs to be configured, all elements affected by the configura-
tion modification must undergo correspondence checking.
The following rules must be observed:
Step Action
1 Make sure that you perform correspondence checking for all elements that
have been taken out of operation in accordance with SAV-B <PV3> as part of
a configuration modification.
2 Only start correspondence checking when the following conditions are met:
1. Plan verification for all ACMs to be configured has been performed suc-
cessfully.
2. The axle counting system is no longer in the configuration acceptance
mode (the OK LED must not show a flashing green light). Leave the con-
figuration acceptance mode, if required, by simultaneously pressing the
RST-RR1 and RST-RR2 buttons of the ACM concerned for min. 3 s until
the OK LED does not show a flashing green light any longer.
3 Perform correspondence checking in accordance with SAV-B <CHK2>.
4 Demonstrate that freely available binary information is transmitted correctly.
Make sure that this demonstration covers all connections that can be affected
by the configuration modification.
5 Confirm correct operation for elements that have passed correspondence
checking.

Step P23: start of operation

The operational usage of elements that have been taken out of operation in accordance
with SAV-B <PV3> as part of a configuration modification is only permissible after the
following conditions are met:
Step Action
1 A verifier has confirmed correct operation of the elements after correspon-
dence checking has been passed.
2 Approval has been granted for the modified system by the responsible ap-
proval body.

Adjustment of configuration process
4 Adjustment of configuration process
The configuration process described in this document can be refined or concretized by

operator- or project-specific specifications.
The configuration process must be concretized by operator- or project-specific specifica-
tions with reference to the safety-related application conditions stated or defined in the
sections below.
When concretizing the configuration process, the requirements from EN 50128 and
EN 50129 or comparable national or international standards must be observed. Espe-
cially EN 50128, Section 17.4.2, “Processes and Tools for Data Generation”, is relevant
to the development and adjustment of configuration processes.
The concretized configuration process may only be applied if approval has been granted
for it by the responsible approval body.
Requirements from axle counting system's application conditions
The configuration process described in this document must be concretized by operator-

or project-specific specifications with reference to Rules <PV2>, <PV3>, <PV4> and
<PV5> from the “Safety-related Application Conditions for Operators” [SAV-B].

Plan verification only after successful loading
The configuration process described in this document must be concretized by operator-

or project-specific specifications with reference to Rule PW3.
Rule PW3
By using a suitable method, it shall be ruled out that, due to the random failure of a com-
ponent on the transmission channel, plan verification is based on correct configuration
data although this data has not been loaded into the ACM.
Notes for implementation of Rule PW3

The transmission channel includes all involved Ethernet components, the configuration
PC and the Ethernet components of the ACM. Most of these components buffer the con-
figuration data to be transmitted. If one of these components fails, this buffered configura-
tion data could be read back. As a result, plan verification could be performed success-
fully although this configuration data has not been stored in the ACM.
A hazard resulting from this scenario can be ruled out by using the LEDs on the ACM and
the output information on the web site, when transmitting configuration data to the ACM,
to check whether the configuration data has been successfully loaded onto the ID plug of
the ACM and by ensuring, upon detection of a deviation, that plan verification is not per-
formed until the configuration data has been successfully transmitted to the ID plug of the
ACM.
A direct connection between the ACM and the configuration PC by means of a crossover
or patch cable is the simplest way to minimize the number of components involved in the
transmission channel during configuration and plan verification. This connection method
also rules out any feedback reaction effects from the configuration PC on the components
connected to the network.
As an option, between the loading of configuration data into one or more ACMs and its
read-back for plan verification, all components of the transmission channel, the ACM and
the configuration PC could be switched off and on again after a short period of time. In
this context, the effectiveness of restarting a configuration PC sometimes depends on the
operating system used, the internet browser used, and their configuration. Hence, this
approach is well suitable as a defensive measure but not for the implementation of Rule
PW3.

Safety-related application conditions
5 Safety-related application conditions
For the configuration process described in this document, the safety-related rules listed
below must be observed.
Note:
• The rules “SAV-B <…>” are stated in shortened form in this document. The detailed
versions can be found in [SAV-B].
• The rules “PW…” only apply to the configuration process using the web site and are
stated in full in this document.
Rule Description To be implemented
SAV-B <PV2> It shall be ensured that all fail-safe By a process defined by the
components which communicate operator or project in accor-
with each other have a unique IP dance with SAV-B <PV2>
address.
SAV-B <PV3> The elements affected by a change By a process defined by the
to the configuration data shall be operator or project in accor-
checked for correct configuration dance with SAV-B <PV3>
before they are used in normal op-
eration.
SAV-B <PV4> In the case that an axle counting By a process defined by the
system is inadvertently set to the operator or project in accor-
configuration mode, it shall be en- dance with SAV-B <PV4>
sured by a suitable method that the
hazard resulting from the operator
error is tolerable.
SAV-B <PV5> It shall be ensured by a suitable By a process defined by the
method that no inadmissible hazard operator or project in accor-
results from inadvertent configura- dance with SAV-B <PV5>
tion of an axle counting system in
operation.


PW1 Plan verification with check.html
Before operationally using an ACM By the configuration proc-
whose configuration has been modi- ess (see “Prerequisites” on
fied, a verifier shall perform a plan page 16)
verification for this ACM.
Plan verification shall be performed by By sub-section “Qualified
a verifier who is independent of the staff: verifier” (see
configuring engineer. “Prerequisites” on page 16)
For plan verification, the verifier shall perform the following steps in
the stated order:
• The verifier shall make sure that By Step P18a (see
the ACM to be checked is in the “Prerequisites” on page 16)
normal operating mode or con-
figuration acceptance mode.
• The verifier shall read the con- By Step P18b (see “Basis
figuration data as P_Daten.BCK for checking” on page 17)
out of the ACM using the
check.html web site.
• The verifier shall make sure that By Step P20a (see “Basis
verification is performed on the for checking” on page 17)
basis of P_Daten.BCK. This is
the case if the first line of
P_Daten.BCK contains the text
“Checkfile of attribute configura-
tion data”.
• The verifier shall establish a By Step P20b (see “Basis
unique assignment between the for checking” on page 17)
configuration data P_Daten.BCK
and the ACM to be configured.
This is done by checking the
unique IP address, the version of
the configuration data Self_VP,
and the file name indicated in the
second line of P_Daten.BCK.
• The verifier shall check by means By Step P20c (see
P_Daten.BCK whether the con- “Checking of configuration
figuration data relevant to plan data” on page 19)
verification is permissible in ac-
cordance with the configuration
specifications and order basis.
• The verifier shall make sure that, By Step P21 (see
for a deviation detected during “Response to detected de-
plan verification, operational us- viations” on page 20)
age of the affected elements is
ruled out until the deviation has
been corrected.


PW2 Correspondence checking
Before operationally using elements By Step P23 (see
that have been taken out of operation “Correspondence checking
in accordance with SAV-B <PV3> as and start of operation” on
part of a configuration modification, page 21)
these elements shall undergo corre-
spondence checking.
• Correspondence checking shall By sub-section “Qualified
be performed by a verifier who is staff: verifier” (see
independent of the configuring “Correspondence checking
engineer. and start of operation” on
page 21)
• Correspondence checking shall By Step P22, Item 3 (see
be performed in accordance with “Correspondence checking
SAV-B <CHK2>. and start of operation” on
page 21)
• As part of correspondence check- By Step P22, Item 4 (see
ing, the verifier shall demonstrate “Correspondence checking
that freely available binary infor- and start of operation” on
mation is transmitted correctly. page 21)
This demonstration shall cover all
connections that can be affected
by the configuration modification.
PW3 Plan verification only after successful loading
By using a suitable method, it shall be By a process defined by
ruled out that, due to the random fail- the operator or project
ure of a component on the transmis- based on the “Plan verifica-
sion channel, plan verification is based tion only after successful
on correct configuration data although loading” section (see “Plan
this data has not been loaded into the verification only after suc-
ACM. cessful loading” on page
24)
Table 3 Safety-related application conditions

Indices
6 Indices
List of abbreviations
Abbreviation Meaning
ACM axle counter module
SAV-B safety-related application rules for operators
SLC safety layer cyclic
SRI safety-relevant information
List of figures
Figure 1 Overview of the configuration process using the web site.................................................. 9
List of tables
Table 1 Supplementary documents ................................................................................................. 4

Table 2 Standards and guidelines ................................................................................................... 5
Table 3 Safety-related application conditions ................................................................................ 27


PRV Mit Webseite ACM 200 Eng Us

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PRV Mit Webseite ACM 200 Eng Us

Uploaded by

Copyright:

Available Formats

Configuration Process using Web Site

Clearguard ACM 200

A6Z00034626189/- Configuration Process using Web Site

A6Z00034626189/- Configuration Process using Web Site

3 Description of configuration process ............................................................................. 9

4 Adjustment of configuration process ........................................................................... 23

5 Safety-related application conditions ........................................................................... 25

A6Z00034626189/- Configuration Process using Web Site

1 Information for the user

About this document

This documentation is part of the equipment described.

Reference ID Title Document number

Table 1 Supplementary documents

A6Z00034626189/- Configuration Process using Web Site

Standards and guidelines

Table 2 Standards and guidelines

A6Z00034626189/- Configuration Process using Web Site

Binary information (SRI, safety-related information)

A6Z00034626189/- Configuration Process using Web Site

Configuration acceptance mode

A6Z00034626189/- Configuration Process using Web Site

A6Z00034626189/- Configuration Process using Web Site

3 Description of configuration process

Description of configuration process

Figure 1 Overview of the configuration process using the web site

A6Z00034626189/- Configuration Process using Web Site

3.1 Definition of configuration data

Definition of configuration data

Qualified staff: configuring engineer

Step P1: definition of configuration data

A6Z00034626189/- Configuration Process using Web Site

Execution notes for Step P1

3.2 Restriction of operational usage

Restriction of operational usage

Step P2: restriction of operational usage

A6Z00034626189/- Configuration Process using Web Site

3.3 Loading of configuration data into ACM

Loading of configuration data into ACM

Step P3: switchover to configuration mode

Press the RST reset button for min. 2 s.

A6Z00034626189/- Configuration Process using Web Site

Step P5: set-up of communication connection

Step P6: entry or read-in of configuration data into web site

A6Z00034626189/- Configuration Process using Web Site

Step P8: loading of configuration data onto ID plug of ACM

2 In the SAVE TO section, click the ACM button.

A6Z00034626189/- Configuration Process using Web Site

Step P16: response to incorrect loading

A6Z00034626189/- Configuration Process using Web Site

3.4 Plan verification

Qualified staff: verifier

Step P17: preparation of plan verification

A6Z00034626189/- Configuration Process using Web Site

Basis for checking

Step P18b: read-back of configuration data from ACM

A6Z00034626189/- Configuration Process using Web Site

Step P20c: checking based on read-back data

A6Z00034626189/- Configuration Process using Web Site

Step P20b: unique assignment between data and ACM

Checking of configuration data

Step P20c: checking of configuration data

Basis_AdIP plan verification

Self_DS_SIM plan verification