User's Manual

RS232-Transponder Reader
(SECS1-Protocol), Release 0.3 Draft Page 89 of 91
2000-09-29
ID: ID000093
Reader to Host: S9F1
08:17:16 Incoming: ENQ ( 05 )
08:17:16 Outgoing: EOT ( 04 )
08:17:16 Incoming: Length Byte ( 16 )
08:17:16 Incoming: Header ( 81 FF 09 01 80 01 00 00 00 04 )
08:17:16 Incoming: Data ( 21 0A 01 D2 81 )
08:17:16 Incoming: Data ( 01 80 01 00 00 00 03 )
08:17:16 Incoming: Checksum ( 04 12 )
08:17:16 Outgoing: ACK ( 06 )
The device-ID in the message block header did not correspond to the device-ID in
the reader detecting the error.
12. The reader detects a wrong stream number and sends the S9F3 message
Host to Reader: S4F1
20:03:20 Outgoing: ENQ ( 05 )
20:03:20 Incoming: EOT ( 04 )
20:03:20 Outgoing: Length Byte ( 0A )
20:03:20 Outgoing: Header ( 01 FF 84 01 80 01 00 00 00 08 )
20:03:20 Outgoing: Checksum ( 0E 02 )
20:03:20 Incoming: ACK ( 06 )
Reader to Host: S9F3
20:03:20 Incoming: ENQ ( 05 )
20:03:20 Outgoing: EOT ( 04 )
20:03:20 Incoming: Length Byte ( 16 )
20:03:20 Incoming: Header ( 81 FF 09 03 80 01 00 00 00 09 )
20:03:20 Incoming: Data ( 21 0A 01 FF 84 ) =>the wrong message header
20:03:20 Incoming: Data ( 01 80 01 00 00 00 08 )
20:03:20 Incoming: Checksum ( 04 4F )
20:03:20 Outgoing: ACK ( 06 )
The stream „4“ isn’t part of the SECS-2 message-set, so a S9F3 error message will
appear.