Pilz PITreader - Page 22

Function description
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08
| 22
} Data type
You can use the data types listed in the table. Each parameter value has the data length
stated in the table. When a parameter is created, the type-ID is stated and not the name
of the data type.
Type-ID Name Data length Value range Initial value
1 STRING 2 … 255 Byte Empty STRING
10 INT8U 1 Byte 0 ... 255 0
11 INT8S 1 Byte -128 ... 127 0
12 INT16U 2 Byte 0 ... 65535 0
13 INT16S 2 Byte -32768 ... 32767 0
14 INT32U 4 Byte 0 ... 4294967295 0
15 INT32S 4 Byte -2147483648 ... 2147483647 0
20 DATETIME 4 Byte Empty time/date
30 PERMISSION 4 Byte 0 ... 64 (Hamming-coded) 0
In order for the user data to be employed it must be configured on the PITreader. The indi-
vidual parameters are created in the configuration. A maximum of 64 parameters can be
created on the PITreader.
If parameters are created on a PITreader, the range of device groups extends from 0 ... 31
to 0 ... 9999. In order to use the groups 32 ... 9999, the system parameter with ID 1 must be
created (see System parameters [ 23]).
This section describes how to configure the user data: Configure user data [ 42]
The values of the parameters are stored on the transponder key. Values for a maximum of
64 parameters and a maximum of 48 device groups can be stored on the transponder key.
The data length of the values determines how many values can actually be stored. The
more parameters are used, the fewer device groups are possible. The memory usage on
the transponder key is displayed in the web application.
For each parameter, a separate value can be stored for each device group that’s required
(group number 0 ... 9999). To save memory it is possible to configure one default value per
parameter. This default value will be used for all device groups 0 ... 9999, for which no sep-
arate value is configured.
This section describes how to write values for the parameters on a transponder key: Edit
user data values [ 40].
The user data can be read from the transponder key via Modbus/TCP, via REST API or via
the OPC Server UA (see operating manual PITreader REST API or PITreader OPC Server
UA). The PITreader always returns just one value for a parameter, which is the value for
the device group to which the PITreader belongs.
Should the parameter not exist on the transponder key, the data type's initial value is re-
turned.
If the parameter exists on the transponder key but the device group does not, the default
value is returned. If no default value is stored, the data type's initial value is returned.