Balluff BIS U-6127-081-1 4-06-ST36 Betriebsanleitung Seite 260

BIS U-6127-081-1_4-06-ST36
Processor unit
7
Startup and operation (continued)
Setting the data to be signed
In addition to the key, the setting of the data to be signed
must also be the same for all devices involved. Usually, the
EPC and the TID of the data carrier are included in the
signature.
For tags with 12 byte EPC and 12 byte TID (including
64 bit serial number) the common definition is:
%E[0.12]%T[0.12].
For tags with 12 byte EPC and 8 byte TID (including 32 bit
serial number) the common definition is: %E[0.12]%T[0.8].
The definition cannot be changed subsequently
without all signatures created so far being
recognized as invalid.
The setting is made on the device web page Configuration
/ RFID / UHF Advanced in the field S
.
foRmat
Fig. 7-33: Tag signature
The signature is generated with all write com-
mands that use the universal output format,
both with the 007 protocol and with OPC UA.
Other write commands, which can only write to
individual memory banks, do not create a
modified signature and can overwrite or invali-
date an existing signature.
Switching on signature generation and verification
The use of the tag data signature is finally switched off and
on by selecting the signature algorithm on the device web
page Configuration / RFID / UHF extended in the t
field. The possible values are Off or
SignatuRe
SHA256+ECDSA512.
The signature is verified for all read commands
that use the universal output format – both with
007 protocol and with OPC UA.
The check result can be included in the output
by specifying the status byte in the format string
(e.g. as %SX[0.1] or %Sd[0.1]).
A value of 0 indicates a successful check. A
value of 2 means that the signature does not
match the other tag data.
84 english
ignatuRe calculation
ag
In principle, the generated signature can also be verified
using the public key and a suitable SW application. With
the BIS U-6127, it is currently necessary to enter the
private key into the Secure Element.