Pilz PITreader User manual

PITreader
PITreader Firmware V1.5.x
Operating Manual-1004806-EN-08
}Control and signal devices

Preface
This document is the original document.
All rights to this documentation are reserved by Pilz GmbH & Co. KG. Copies may be made
for the user's internal purposes. Suggestions and comments for improving this documenta-
tion will be gratefully received.
Pilz®, PIT®, PMI®, PNOZ®, Primo®, PSEN®, PSS®, PVIS®, SafetyBUS p®,
SafetyEYE®, SafetyNET p®, the spirit of safety® are registered and protected trademarks
of Pilz GmbH & Co. KG in some countries.
SD means Secure Digital

Contents
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 3
1 Introduction ............................................................................................................................ 6
1.1 Validity of documentation.......................................................................................................... 6
1.2 Using the documentation .......................................................................................................... 6
1.3 Definition of symbols................................................................................................................. 6
1.4 Third-party manufacturer licence information ........................................................................... 7
2 Overview ................................................................................................................................. 8
2.1 Device features......................................................................................................................... 8
2.2 PITreader device view with base unit ....................................................................................... 9
3 Safety ...................................................................................................................................... 10
3.1 Intended use ............................................................................................................................. 10
3.2 Safety regulations ..................................................................................................................... 10
3.2.1 Additional documents that apply............................................................................................... 10
3.2.2 Use of qualified personnel ........................................................................................................ 10
3.2.3 Warranty and liability ................................................................................................................ 11
3.2.4 Disposal .................................................................................................................................... 11
4 Security ................................................................................................................................... 12
4.1 Implemented security measures............................................................................................... 12
4.2 Required security measures ..................................................................................................... 12
5 Function description ............................................................................................................. 14
5.1 Authentication procedure.......................................................................................................... 14
5.2 Authentication modes ............................................................................................................... 14
5.2.1 Transponder data ..................................................................................................................... 15
5.2.1.1 Device groups........................................................................................................................... 15
5.2.2 External..................................................................................................................................... 16
5.3 Authentication types ................................................................................................................. 18
5.3.1 "Basic" authentication type ....................................................................................................... 18
5.3.2 "Single authentication" authentication type............................................................................... 18
5.3.3 "2-person rule" authentication type........................................................................................... 18
5.4 Transponder key....................................................................................................................... 20
5.4.1 Serial number of the transponder key....................................................................................... 21
5.4.2 Transponder key's security ID (SID) ......................................................................................... 21
5.5 User data .................................................................................................................................. 21
5.5.1 System parameters................................................................................................................... 23
5.6 Coding ...................................................................................................................................... 24
5.6.1 Basic coding ............................................................................................................................. 25
5.6.2 OEM coding .............................................................................................................................. 25
5.7 Block list.................................................................................................................................... 26
5.8 Real-time clock and operating hours counter ........................................................................... 26
5.9 Modbus/TCP............................................................................................................................. 26
5.9.1 LED control ............................................................................................................................... 26
5.9.2 Function codes (Client connections)......................................................................................... 27
5.9.3 Modbus/TCP data areas........................................................................................................... 27
5.9.3.1 Data transfer limits.................................................................................................................... 30
5.10 HTTP(S) connection ................................................................................................................. 30

Contents
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 4
5.11 24V I/O port ............................................................................................................................. 31
5.12 Connect the base unit to a safe evaluation unit........................................................................ 31
6 Install the base unit ............................................................................................................... 32
6.1 General installation guidelines.................................................................................................. 32
6.2 Dimensions in mm .................................................................................................................... 33
7 Wiring ...................................................................................................................................... 34
7.1 Standalone................................................................................................................................ 34
7.2 Base unit with safe evaluation unit ........................................................................................... 34
8 Configuration ......................................................................................................................... 35
8.1 Web application ........................................................................................................................ 35
8.2 Connect to PITreader ............................................................................................................... 35
8.3 Manage certificates................................................................................................................... 36
8.3.1 Managing certificates................................................................................................................ 36
8.3.2 Incorporate certificate into a public key infrastructure (PKI) ..................................................... 37
8.4 Configure authentication mode................................................................................................. 37
8.5 Configure authentication type ................................................................................................... 37
8.6 Location description.................................................................................................................. 37
8.7 Data logging with personal data ............................................................................................... 37
8.8 Set device group....................................................................................................................... 37
8.9 Write/program transponder key ................................................................................................ 38
8.9.1 Program permissions................................................................................................................ 38
8.9.2 Configure the validity of the transponder key ........................................................................... 38
8.9.3 Teach in transponder key to basic coding ................................................................................ 38
8.9.4 Teach in transponder key to OEM coding ................................................................................ 39
8.9.5 Limit transponder key to identically coded PITreader............................................................... 40
8.9.6 Edit user data values ................................................................................................................ 40
8.10 Set basic coding ....................................................................................................................... 41
8.11 Set OEM coding........................................................................................................................ 41
8.12 Use block list............................................................................................................................. 41
8.13 Configure user data .................................................................................................................. 42
8.14 API Clients ................................................................................................................................ 43
8.15 Save and restore configuration................................................................................................. 43
8.16 Reset to default settings ........................................................................................................... 44
9 Firmware update .................................................................................................................... 45
10 Operation ................................................................................................................................ 46
10.1 LED indicator ............................................................................................................................ 46
10.2 Safely decommission PITreader............................................................................................... 47
10.3 Diagnostics ............................................................................................................................... 48
10.3.1 Statistics ................................................................................................................................... 48

Contents
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 5
11 Technical details .................................................................................................................... 51
12 Supplementary data .............................................................................................................. 53
12.1 Radio approval.......................................................................................................................... 53
12.2 Network data............................................................................................................................. 53
12.3 Overview of permissions........................................................................................................... 54
13 Order reference ...................................................................................................................... 56
13.1 Authentication system............................................................................................................... 56
13.2 Transponder key....................................................................................................................... 56
13.3 Accessories .............................................................................................................................. 56
14 EC declaration of conformity ................................................................................................ 57

Introduction
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 6
1 Introduction
1.1 Validity of documentation
This documentation is valid for the product PITreader. It is valid until new documentation is
published.
This operating manual explains the function and operation, describes the installation and
provides guidelines on how to connect the product.
1.2 Using the documentation
This document is intended for instruction. Only install and commission the product if you
have read and understood this document. The document should be retained for future ref-
erence.
1.3 Definition of symbols
Information that is particularly important is identified as follows:
DANGER!
This warning must be heeded! It warns of a hazardous situation that poses
an immediate threat of serious injury and death and indicates preventive
measures that can be taken.
WARNING!
This warning must be heeded! It warns of a hazardous situation that could
lead to serious injury and death and indicates preventive measures that can
be taken.
CAUTION!
This refers to a hazard that can lead to a less serious or minor injury plus
material damage, and also provides information on preventive measures
that can be taken.
NOTICE
This describes a situation in which the product or devices could be dam-
aged and also provides information on preventive measures that can be
taken. It also highlights areas within the text that are of particular import-
ance.

Introduction
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 7
INFORMATION
This gives advice on applications and provides information on special fea-
tures.
1.4 Third-party manufacturer licence information
This product includes Open Source software with various licences.
More detailed information is available in the web application of the PITreader by calling up
the menu Support -> Show legal information.
The relevant source codes can be requested via [email protected].
Your request should include the following: (a) the firmware name, (b) the firmware version,
(c) your name, (d) your company name (if applicable), (e) your reply address and (f) your E-
mail address (if possible).
Pilz can charge a fee for the data medium and for sending.
The request for the source code must be received 3 years at the latest after the receipt of
the relevant MPL. Irrespective of this period we will send you a complete, machine-read-
able copy of the source code as long as Pilz offers spares or technical support for this
device.

Overview
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 8
2 Overview
The product can be used with the following external components/systems:
}Transponder key (PITreader key) for authentication
}Web application on a PC for configuration
}Operator terminal (HMI) for authentication
}Safety controller (FS-PLC) for safe operating mode selection or authentication
}Safe evaluation unit (e.g. PIT m4SEU, order no. 402 250) for safe operating mode selec-
tion (only on PITreader base unit)
2.1 Device features
}System for authentication and authorisation on control systems
}Authentication is via transponder key
}Configurable via a web application
}Ethernet interface for Modbus/TCP
}LED to display device status
Only on PITreader base unit:
}Interface for connecting a safe evaluation unit (SEU) for operating mode selection
}For mounting cutouts D22 (diameter 22.3mm +0.4mm/-0.0mm) in accordance with
EN60947-5-1 with anti-rotation device
Only PITreader S base unit type devices and versions of the PITgb with PITreader (e.g.
PIT gb RLLE y up ETH, PIT gb RLLE y down ETH):
}Integrated OPC Server UA

Overview
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 9
2.2 PITreader device view with base unit
[1]
[2] [3]
[4]
[5]
[6]
Legend
X1 Voltage supply, 24 V input/output and connection of a safe evaluation unit (PIT
m4SEU)
X2 Ethernet interface
[1] Device description
[2] Order number
[3] Serial number
[4] PITreader base unit, including spring-loaded terminal (order no. 402 255)
[5] PITreader key adapter h (order no. 402 308)
[6] PITreader key (see also Transponder key [ 20])

Safety
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 10
3 Safety
3.1 Intended use
The PITreader is a system for authentication and authorisation on control systems. Authen-
tication is via transponder key.
The following is deemed improper use in particular
}Any component, technical or electrical modification to the product,
}Use of the product outside the areas described in this operating manual,
}Use of the product outside the technical details (see Technical details [ 51]).
NOTICE
EMC-compliant electrical installation
The product is designed for use in an industrial environment. The product
may cause interference if installed in other environments. If installed in other
environments, measures should be taken to comply with the applicable
standards and directives for the respective installation site with regard to in-
terference.
3.2 Safety regulations
3.2.1 Additional documents that apply
You should also read and take note of the following documents:
}Operating manual of the PITreader you are using
(e.g. PITgbRLLEyupETH, PITgbRLLEydownETH)
}Operating manual PITreader REST API
}Operating manual PITreader OPC Server UA
3.2.2 Use of qualified personnel
The products may only be assembled, installed, programmed, commissioned, operated,
maintained and decommissioned by persons who are competent to do so.
A competent person is a qualified and knowledgeable person who, because of their train-
ing, experience and current professional activity, has the specialist knowledge required. To
be able to inspect, assess and operate devices, systems and machines, the person has to
be informed of the state of the art and the applicable national, European and international
laws, directives and standards.
It is the company’s responsibility only to employ personnel who
}Are familiar with the basic regulations concerning health and safety / accident prevention,
}Have read and understood the information provided in the section entitled Safety
}Have a good knowledge of the generic and specialist standards applicable to the specific
application.

Safety
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 11
3.2.3 Warranty and liability
All claims to warranty and liability will be rendered invalid if
}The product was used contrary to the purpose for which it is intended,
}Damage can be attributed to not having followed the guidelines in the manual,
}Operating personnel are not suitably qualified,
}Any type of modification has been made (e.g. exchanging components on the PCB
boards, soldering work etc.).
3.2.4 Disposal
}When decommissioning, please comply with local regulations regarding the disposal of
electronic devices (e.g. Electrical and Electronic Equipment Act).

Security
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 12
4 Security
To secure plants, systems, machines and networks against cyberthreats it is necessary to
implement (and continuously maintain) an overall industrial security concept that is state of
the art.
Perform a risk assessment in accordance with VDI/VDE 2182 or IEC 62443-3-2 and plan
the security measures with care. If necessary, seek advice from Pilz Customer Support.
4.1 Implemented security measures
}The web application is protected against unauthorised access by a password prompt.
}The password is saved in an encrypted format.
}If a password is changed, you will be prompted to enter the old password for authentica-
tion.
}Defend against CSRF attacks (Cross-Site Request Forgery) by assigning a unique token
to a session.
}A user will automatically be logged out of the web application after 15 minutes of inactiv-
ity.
4.2 Required security measures
}The product is not protected against physical manipulation. We therefore recommend that
you install the product in a lockable control cabinet or operator panel.
A safe evaluation unit PIT m4SEU may only be connected via the terminals TxD/RxD in
the inside of a control cabinet or operator panel.
}The configuration computer that accesses the product has to be protected from attacks
by a firewall or other suitable measures. We recommend that a virus scanner is used on
this configuration computer and updated regularly.
}If necessary, protect the configuration computer and the product from unauthorised use
by assigning passwords and taking further measures if required. We also recommend
that the user logged on to this configuration computer does not have administrator rights.
}Ensure that the product is separated by a router (layer 3 switch or firewall) from the com-
pany network.
}Assign only safe passwords. When assigning passwords, please note:
– The password should have at least 8 characters.
– The password should contain upper and lower case characters, as well as special
characters and numbers.
– If possible, the password should not be available in dictionaries.
– The password should not be made up of standard variants and repetitions or key-
board patterns (so not: 1234abcd).
– Use a password manager for optimum management of complex passwords.
– Language-independent characters are not available in every keyboard language.
– Make sure you regularly change the passwords of the user accounts on the system
and/or ask the users to change their passwords themselves.
– Make the users aware of the responsible use of their access data.

Security
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 13
}Limit Modbus/TCP connections to the internal machine network. Secure the connection
against external networks.
}As soon as possible, install firmware updates that Pilz provides for the product.
}Keep the transponder key in a safe place and protect it from unauthorised access. Advise
users of the security risks of sharing transponder keys.
}Log data may contain personal data. Only store exported logs on a storage medium that
is adequately protected.
}Before disposal, the product must be safely decommissioned. To do this, all the data
must be deleted from the device.
– Set the configuration back to its default settings or delete the configuration.
– Switch off the product.
Company firewall Machine firewall
Company network Machine network
Internet
Configuration computer
Product
Fig.: Example network topology
}Note the network data [ 53] for risk analysis and the security measures.

Function description
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 14
5 Function description
5.1 Authentication procedure
Transponder
key is inserted
Coding
matches?
Read permission from
the transponder key
corresponding to the
device group
Yes
No
Not authenticated
(LED: flashing red)
Transponder
in block list?
Not authenticated
(LED: red)
Yes
No
Apply permission from
REST API / OPC UA
"Transponder
data" mode
"External"
mode
Wait for authentication
(LED: yellow)
Permission
> 0 Yes
No
Not authenticated
(LED: red)
Authenticated
(LED: green)
Authentication block
activated by other
transponder keys
Not authenticated
(LED: red)
Evaluation: single
authentication
Not authenticated
(LED: red)
Yes
No
Block
activated via
24 V I/O
port?
Evaluation: 2-
person rule
2-person rule
Single
authentication
Not authenticated
(LED: flashing green)
First transponder key
Fig.: Authentication procedure
5.2 Authentication modes
The PITreader supports two authentication modes:
}Transponder data [ 15]
Pre-defined, group-based authentication in the transponder key
}External [ 16]
Authentication takes place externallye.g. via PLC, HMI
When delivered, the transponder data authentication mode is set. The authentication mode
can be changed in the web application.

Function description
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 15
5.2.1 Transponder data
In transponder data authentication mode, a user can authenticate himself on a safe evalu-
ation unit (e.g. PIT m4SEU) and the connected control system by inserting a transponder
key into the read area of the PITreader. Authentication is carried out using the permissions
stored on the transponder key.
Safe operating mode selection can be implemented via a safe evaluation unit (e.g.
PITm4SEU) (only with PITreader base unit).
A controller (PLC, HMI) can use Modbus/TCP to read the transponder key that is currently
authenticated.
INFORMATION
Please note that in transponder data authentication mode, authentication
depends solely on possession of the transponder key. Loss of a transpon-
der key can therefore lead to a security risk.
We recommend that you enter the security IDs of all the published
transponder keys in a list, so that they can be transferred into the Block
list [ 26] if they are lost.
5.2.1.1 Device groups
There are 32 selectable device groups, G0 to G31.
PITreader devices are combined within a device group. One user (one transponder key)
has the same permission on all PITreader devices within a group. Another user can have a
different permission. Device groups can be used for a machine type, for example (in this
case a user has the same permission on all turning machines, for example), see also Set
device group [ 37].
One permission can be stored on a transponder key per device group.
Each device group can have up to 65 different permissions.
}0: No permission
}1 to 64: Permission 1 to 64
For example a permission may relate to the enabling of functions, which can be assigned
based on the level of training.
Permissions are code words for failsafe communication with a guaranteed minimum ham-
ming distance. An overview of the code words for the permissions can be found under
Overview of permissions [ 54].
Only one permission at a time is valid in the PITreader. Additional permissions stored on
the transponder key can be called up via the Modbus/TCP interface of the PITreader and if
necessary can be used for customer-specific purposes.

Function description
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 16
INFORMATION
By employing user data, the number of device groups can be extended to
more than 32. A PITreader can be assigned to device group 0 ... 9999. Per-
missions for device groups 0 ... 31 can be stored on a transponder key as
well as permissions for a maximum of 48 other device groups in the range
32 ... 9999. See User data [ 21].
5.2.2 External
In external authentication mode, a user can authenticate himself on the connected control
system or on the HMI by inserting a transponder key into the read area of the PITreader.
The following connection options are available:
External authentication (Modbus/TCP)
Security ID
Modbus/TCP
PLC
PITreader
Fig.: External authentication (Modbus/TCP)
The PITreader provides the transponder key data via the Modbus/TCP connection.
The permission for the user can be identified using a permission database (on the PLC)
and the data from the transponder key (e.g. the security ID). The authentication is external
(on the PLC).
No authentication takes place within the PITreader and the device LED lights up yellow
when the transponder key is inserted.
To display the externally identified authentication status via the device LED, the colour and
flash mode can be overwritten via the Modbus/TCP interface (see also Modbus/
TCP [ 26]).
INFORMATION
A safe evaluation unit (e.g. PITm4SEU) cannot be used in external authen-
tication mode via Modbus/TCP.

Function description
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 17
External authentication (REST API)
REST (HTTPS)
Permission
Modbus/TCP
PITreader REST API Client
(e.g. HMI)
PLC
Security ID and
permission
PIT m4SEU
Permission
Security ID
Fig.: External authentication (REST API)
The permission for the user can be identified using a permission database on the REST
API Client (e.g. HMI) and the data from the transponder key (e.g. security ID).
Authentication occurs on the RESTAPI Client. The information about the authentication
status is adopted by the PITreader and forwarded to the controller and the safe evaluation
unit (e.g. PITm4SEU). The externally calculated authentication status is displayed via the
device LED on the PITreader.
External authentication (OPC UA)
OPC UA DA
Permission
Modbus/TCP
PITreader Display unit
with OPC UA
Client
(e.g. display unit from
Pilz with PASvisu
Client and PASvisu
project)
PLC
Security ID and
permission
PIT m4SEU
Permission
Security ID
Fig.: External authentication (OPC UA)
The permission for the user can be identified using a permission database on the OPC UA
Client (e.g. display unit) and the data from the transponder key (e.g. security ID).
Authentication occurs on the OPCUA Client. The information about the authentication
status is adopted by the PITreader and forwarded to the controller and the safe evaluation
unit (e.g. PITm4SEU). The externally calculated authentication status is displayed via the
device LED on the PITreader.

Function description
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 18
5.3 Authentication types
The PITreader supports the following authentication types:
}Basic
}Single authentication
}2-person rule
5.3.1 "Basic" authentication type
The "Basic" authentication type includes the "Transponder data" and "External" authentica-
tion modes with all their functions and possibilities (see Authentication modes [ 14]).
5.3.2 "Single authentication" authentication type
The authentication type "single authentication” includes all the functions and possibilities of
the "Basic" authentication type. Users also obtain special rights when "single authentica-
tion" is configured. Users can log in to a device using their transponder key in order to ac-
tivate an authentication block for all other transponder keys. The authentication block re-
mains activated until the same transponder key is used to log out. When the authentication
block is active, the device LED lights up red.
}Activate authentication block:
Log in for single authentication by inserting the transponder key on the PITreader. By log-
ging in, an authentication block is activated for all other transponder keys. If the transpon-
der key is removed, the authentication block remains activated.
}Deactivate authentication block:
The authentication block is not deactivated until the same transponder key is used to log
out. To log out, the same transponder key must be re-inserted and then removed again.
Note: The authentication block can also be reset via the web application. This requires
administrator access rights to the web application. A reset via the web application will be
logged.
5.3.3 "2-person rule" authentication type
The "2-person rule" authentication type includes all the functions and possibilities of the
"Basic" authentication type.
With the "two-person rule" authentication type, two different transponder keys are needed
for authentication. The authentication process is started with the first transponder key. Ac-
tual authentication then occurs using the second transponder key.
}Start authentication process
The authentication process is started by inserting the first transponder key into the
PITreader. The device LED flashes green.
The transponder key runs through all the authentication steps up to the permission check
(see Authentication procedure [ 14]). If there is sufficient permission and the "2-person
rule" is configured, the permission is assessed internally as "permission 0"; i.e. authentic-
ation is not possible with the first transponder key.

Function description
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 19
Once the first transponder key is removed, a 30-second time window is activated. Au-
thentication with the second transponder key can occur within this time window. The
device LED will flash green until the 30-second time window has elapsed or the second
transponder key is inserted.
}Cancel authentication process
An authentication process that has been started will be cancelled if a second valid
transponder key is not inserted within the 30-second time window or the same transpon-
der key is re-inserted.
An authentication process that has been started is not cancelled as a result of an invalid
transponder key.
}Restart authentication process after it has been cancelled
The authentication process can be restarted by re-inserting and removing the first
transponder key.
}Authentication
When the authentication process is started, a user can authenticate himself with a
second transponder key within the 30-second time window.
Once the second transponder key has been inserted, it runs through all the authentication
steps (see Authentication procedure [ 14]). If it is a valid transponder key, then au-
thentication occurs.
Notes:
}Both transponder keys may be any transponder key; i.e. there is no need for special or
preconfigured transponder keys. However, the transponder keys must be valid for the
specific application.
}The permission enabled via authentication through the second transponder key is estab-
lished internally. The permissions on the two transponder keys are evaluated and authen-
tication occurs with the lower of the permissions on the two transponder keys
Examples:
– Permission on the first transponder key: 10
Permission on the second transponder key: 5
-> Authentication occurs with permission 5
– Permission on the first transponder key: 1
Permission on the second transponder key: 5
-> Authentication occurs with permission 1

Function description
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08 | 20
5.4 Transponder key
The following types of transponder key are available (see also Order reference [ 56]):
Designation Permission Serial number
PITreader key ye 1 Permission 1 01nnnnnnn
PITreader key ye 2 Permission 2 02nnnnnnn
PITreader key ye 3 Permission 3 03nnnnnnn
PITreader key ye 4 Permission 4 04nnnnnnn
PITreader key ye 5 Permission 5 05nnnnnnn
PITreader key ye 5 service Permission 5 (Service) 13nnnnnnn
PITreader key ye g Without pre-programmed
permission
00nnnnnnn
With the exception of "PITreader key ye g", all transponder keys are pre-programmed in the
factory and the permission cannot be modified. The permission applies to all PITreader
groups.
In the case of "PITreader key ye g", the permission for the PITreader groups can be modi-
fied and also locked as an option.
Device groupsFree user data
PITreader
key ye 2
Start/End Date
User Data User Data
Start/End Date
PITreader
key ye g
G0 G1 G2 G3
2 2 2 2
G28 G29 G30 G31
2 2 2 2
G0 G1 G2 G3
0-64 0-64 0-64 0-64
G28 G29 G30 G31
0-64 0-64 0-64 0-64
. . . . . .
Factory-locked
Data cannot be locked
Validity
Fig.: Example of "PITreader key ye 2" and "PITreader key ye g"