User's Manual
Table Of Contents
- Page 1
- Page 2
- Page 3
- Page 4
- Page 5
- Page 6
- Page 7
- Page 8
- Page 9
- Page 10
- Page 11
- Page 12
- Page 13
- Page 14
- Page 15
- Page 16
- Page 17
- Page 18
- Page 19
- Page 20
- Page 21
- Page 22
- Page 23
- Page 24
- Page 25
- Page 26
- Page 27
- Page 28
- Page 29
- Page 30
- Page 31
- Page 32
- Page 33
- Page 34
- Page 35
- Page 36
- Page 37
- Page 38
- Page 39
- Page 40
- Page 41
- Page 42
- Page 43
- Page 44
- Page 45
- Page 46
- Page 47
- Page 48
- Page 49
- Page 50
- Page 51
- Page 52
Hi-G-Tek Ltd. Microelectronics & Asset Tracking Technology
117
6
RS 485/232 Communication Protocol
There are 2 types of commands: SHORT COMMANDS and LONG
COMMANDS.
Short Commands: These are commands that are relevant to
internal tasks at the reader level.
Long Commands: These commands involve sessions with seals.
The READER will respond to commands generated by the LSC
within T seconds.
RLSC
For short commands, response time should be: T = 50 msec.
RLSC
For long commands, the LSC should return to retrieve the results
after T with the appropriate GET RESULTS command.
session
T is a derivative of the type of command executed to the seals.
session
Acknowledge can be positive or negative.
If the LSC detects a problem, Acknowledge will be negative.
The READERS are designed to work in cycles. Following an
internal or external trigger, a READER SESSION is generated.
This is a full communication cycle going back and forth between
a READER and the tags located in the READER's receiving zone.
The LSC operates differently The READERs are scanned on a
different time line, using the same frequency as that of the
READER's cycles or greater.
This protocol supports RS-485 and RS-232 communication
fashions. When working with the LSC using RS-232 communication
opposite only one device, address fields should be set to 0xFFFF.
When using RS-485 communication in broadcast situations, the
address field should be set to 0x0000.