F1F2ANNEX I BREQUIREMENTS FOR CONSTRUCTION, TESTING, INSTALLATION AND INSPECTION
2.DATA TYPE DEFINITIONS
2.54.EventFaultType
Code qualifying an event or a fault.
EventFaultType ::= OCTET STRING (SIZE(1)).
Value assignment:
- ′0x′H
General events,
- ′00′H
No further details,
- ′01′H
Insertion of a non-valid card,
- ′02′H
Card conflict,
- ′03′H
Time overlap,
- ′04′H
Driving without an appropriate card,
- ′05′H
Card insertion while driving,
- ′06′H
Last card session not correctly closed,
- ′07′H
Over speeding,
- ′08′H
Power supply interruption,
- ′09′H
Motion data error,
- F3′0A′H
Vehicle Motion Conflict,
- ′0B′H to ′0F′H
RFU,
- ′1x′H
Vehicle unit related security breach attempt events,
- ′10′H
No further details,
- ′11′H
Motion sensor authentication failure,
- ′12′H
Tachograph card authentication failure,
- ′13′H
Unauthorised change of motion sensor,
- ′14′H
Card data input integrity error
- ′15′H
Stored user data integrity error,
- ′16′H
Internal data transfer error,
- ′17′H
Unauthorised case opening,
- ′18′H
Hardware sabotage,
- ′19′H to ′1F′H
RFU,
- ′2x′H
Sensor related security breach attempt events,
- ′20′H
No further details,
- ′21′H
Authentication failure,
- ′22′H
Stored data integrity error,
- ′23′H
Internal data transfer error,
- ′24′H
Unauthorised case opening,
- ′25′H
Hardware sabotage,
- ′26′H to ′2F′H
RFU,
- ′3x′H
Recording equipment faults,
- ′30′H
No further details,
- ′31′H
VU internal fault,
- ′32′H
Printer fault,
- ′33′H
Display fault,
- ′34′H
Downloading fault,
- ′35′H
Sensor fault,
- ′36′H to ′3F′H
RFU
- ′4x′H
Card faults,
- ′40′H
No further details,
- ′41′H to ′4F′H
RFU
- ′50′H to ′7F′H
RFU,
- ′80′H to ′FF′H
Manufacturer specific.
Inserted by Council Regulation (EC) No 2135/98 of 24 September 1998 amending Regulation (EEC) No 3821/85 on recording equipment in road transport and Directive 88/599/EEC concerning the application of Regulations (EEC) No 3820/85 and (EEC) No 3821/85.