
Creating and transferring a configuration
5.1 Creating a configuration
SIMATIC RF1000
18 Configuration Manual, 07/2021, C79000-G8976-C647-01
Config Security Code (CSC)
The Config Security Code (CSC) is intended to ensure that a reader cannot be reconfigured,
i.e. manipulated, for example through contactless reconfiguration of the reader by a
potential attacker using a configuration card. For this reason, a CSC is assigned to each
project by means of a random generator as soon as a project setting has been created for the
first time. If an existing configuration is opened and a change is made to it, i.e. a new version
is created, the CSC remains the same as that of the previous version. This ensures that
updates of the configuration are accepted by the reader.
In the factory state, no CSC is set in the reader. This ensures that any configuration of the
reader can be loaded once at the beginning. If the loaded configuration has then set a CSC,
afterwards you can only load configurations that have the same CSC into the reader.
Logically, this is only possible if you know the CSC or you have the configuration file in
"*.balcfg" format, in which the correct CSC was stored.
If you want to configure the reader for another project, you need to perform a Factory Reset,
which restores the factory configuration and deletes the CSC.
In principle, it is possible to edit the CSC manually in the Config editor. However, you should
only do this before the first versioning of a project configuration. If the CSC changes between
two versions, this has the result that you can no longer update the reader, among other
consequences. Direct transfer of a configuration file ("*.balcfg") to a reader connected to the
computer is still possible, however, because the CSC is not checked in this case.
Note that the CSC cannot be read out of the reader, a "*.bec" file or the configuration card. It
can only be read out of the "*.balcfg" file in plain text.
5.1.2 Opening and editing existing project settings
There are various scenarios where it makes sense to open existing (finalized) configurations.
For example, in order to:
•Update an existing configuration
If you want to update an existing configuration, you can create a new version of it.
•Use an existing configuration as template
If you wish to use an existing configuration as template for another configuration, you can
create a copy and edit it as required.
•Import configuration component(s) from an existing configuration
This is useful, for example, in complex applications when you wish to add the same
configuration component (e.g. project or device settings) to multiple configuration files.
In this case, you can create the component in one configuration file and then import it
into another.
These three scenarios for opening and editing an existing configuration are described below.