Table of Contents
Advertisement
Appendix
A.10 Transparency software
For billing using Giro-e, the Contract-ID also includes the pUID (SEPA-ID). The "Contract ID
explanation" graphic shows the marked area ③.
The length of the contract ID is determined by these factors:
• Version number of the charging controller firmware
• Card number
• Login method, e.g., RFID, Giro-e
Explanation of the version number
This number consists of several bytes. A byte is always written in hexadecimal notation with 2
characters. Bytes 0 - 2 encode the version number of the charging controller firmware as an
integer.
Table A- 3
Position
Byte 0
Byte 1
Byte 2
In this example, the version number is: 2.1.2
Conversion example card number
The card number is given in ASCII code in the following bytes. After the conversion example
of the following table, the card number is derived from this, as is also shown in the backend.
Table A- 4
Position
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 8
Byte 9
Byte 10
148
Explanation of the version number
Conversion example card number
Characters in the Transparen-
cy software (hex)
43
42
44
36
37
36
45
36
Meaning
Major revision
Minor revision
Patch revision
Decoded card number (ASCII)
C
B
D
6
7
6
E
6
SICHARGE Operating instructions, ERK
Operating Instructions, 06/2021, A5E48571690-AC
Advertisement
Table of Contents
