Changes between Version 28 and Version 29 of S6350serialcom
- Timestamp:
- 10/27/08 14:17:12 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
S6350serialcom
v28 v29 1 1 = TI S6350 communication overview = 2 2 3 In order to use the [wiki:S6350 TI reader] within RealBasic we had to implement some of the serial protocol ourselves. You must first generate a command encapsulated in the TI protocol and have the payload of the command be the [wiki:ISO15693] command. Only 3 of the [wiki:ISO15693] commands are necessary to track RFID's, [https://69.164.214.41/projects/fslapcounter/wiki/S6350serialcom#InventoryAllSlots Inventory All Slots], [https:// 69.164.214.41/projects/fslapcounter/wiki/S6350serialcom#Inventory1slot Inventory 1 Slot] and [https://209.20.66.101/projects/fslapcounter/wiki/S6350serialcom#SilenceTag Silence Tag].3 In order to use the [wiki:S6350 TI reader] within RealBasic we had to implement some of the serial protocol ourselves. You must first generate a command encapsulated in the TI protocol and have the payload of the command be the [wiki:ISO15693] command. Only 3 of the [wiki:ISO15693] commands are necessary to track RFID's, [https://69.164.214.41/projects/fslapcounter/wiki/S6350serialcom#InventoryAllSlots Inventory All Slots], [https://209.20.66.101/projects/fslapcounter/wiki/S6350serialcom#Inventory1slot Inventory 1 Slot] and [https://209.20.66.101/projects/fslapcounter/wiki/S6350serialcom#SilenceTag Silence Tag]. 4 4 5 5 To use [wiki:ISO15693] commands with the TI reader the command must be encapsulated in a TI command followed by a [https://69.164.214.41/projects/fslapcounter/wiki/S6350serialcom#Checksum checksum]. An example of the TI command structure follows: … … 14 14 Bytes x+1 and x+2 are the checksum 15 15 }}} 16 17 = Collisions =18 19 The [wiki:ISO15693] protocol allows for 16 time slots for communicating with an RFID reader. A collision occurs when 2 or more tags use the same time slot. By default each tag will use the 1st time slot unless a collision occurs. In the event of a collision the tags will randomly move to a different time slot.20 21 The Inventory All Slots command can handle this as it checks each of the 16 slots for a RFID. Unfortunately doing this operation is slow, it takes about .3 seconds, far too long for a lap counter to get accurate lap times.22 23 The solution is to use the Inventory 1 slot command during races. This command will just check the 1st time slot for a tag. To prevent collisions you must silence the tag immediately after it is detected. If a tag is silences it will not transmit again until it leaves and reenters the antenna loop.24 16 25 17 … … 112 104 }}} 113 105 106 = Collisions = 107 108 The [wiki:ISO15693] protocol allows for 16 time slots for communicating with an RFID reader. A collision occurs when 2 or more tags use the same time slot. By default each tag will use the 1st time slot unless a collision occurs. In the event of a collision the tags will randomly move to a different time slot. 109 110 The Inventory All Slots command can handle this as it checks each of the 16 slots for a RFID. Unfortunately doing this operation is slow, it takes about .3 seconds, far too long for a lap counter to get accurate lap times. 111 112 The solution is to use the Inventory 1 slot command during races. This command will just check the 1st time slot for a tag. To prevent collisions you must silence the tag immediately after it is detected. If a tag is silences it will not transmit again until it leaves and reenters the antenna loop. 113 114 114 = Checksum = 115 115