1024 User Guide
|Go to this device's product page|
Checking the Contents
You should have received:
In order to test your new Phidget you will also need:
Connecting the Pieces
Connect the PhidgetRFID board to the computer using the USB cable.
Testing Using Windows 2000 / XP / Vista / 7
Make sure you have the current version of the Phidget library installed on your PC. If you don't, follow these steps:
- Go to the Quick Downloads section on the Windows page
- Download and run the Phidget21 Installer (32-bit, or 64-bit, depending on your system)
- You should see the icon on the right hand corner of the Task Bar.
Running Phidgets Sample Program
Double clicking on the icon loads the Phidget Control Panel; we will use this program to ensure that your new Phidget works properly.
The source code for the PhidgetRFID-Full sample program can be found in the quick downloads section on the C# Language Page. If you'd like to see examples in other languages, you can visit our Languages page.
Updating Device Firmware
If an entry in this list is red, it means the firmware for that device is out of date. Double click on the entry to be given the option of updating the firmware. If you choose not to update the firmware, you can still run the example for that device after refusing.
Double Click on the icon to activate the Phidget Control Panel and make sure that Phidget RFID is properly attached to your PC.
Testing Using Mac OS X
- Go to the Quick Downloads section on the Mac OS X page
- Download and run the Phidget OS X Installer
- Click on System Preferences >> Phidgets (under Other) to activate the Preference Pane
- Make sure that the Phidget RFID is properly attached.
- Double Click on Phidget RFID in the Phidget Preference Pane to bring up the RFID-full Sample program. This program will function in a similar way as the Windows version.
For a step-by-step guide on getting Phidgets running on Linux, check the Linux page.
Using Windows Mobile / CE 5.0 / CE 6.0
For a step-by-step guide on getting Phidgets running on Windows CE, check the Windows CE page.
We support read-only tags that have been programmed with a supported protocol, as well as T5577 type tags for writing.
T5577 tags can be written with any of the supported protocols. Fresh T5577 tags that have never been programmed may show up as an EM4100 tag, or may not show up at all, depending on how the factory programmed them. After writing, they will always show up as the written tag. We also support a lock function which prevents a tag from ever being re-written.
A protocol is a way of encoding data on an RFID tag. This is not the same as the tag type. For example, we support the T5577 tag type, which can be programmed with any of the protocols which we support. We also support read-only tags which have been programmed in any of these protocols.
We support reading and writing in 3 protocols with the 1024:
EM4100 (also known as EM4102) is the protocol that all previous PhidgetRFID readers have supported. Therefore, if you want to use the 1024 to write to writable tags to be read with previous versions of the PhidgetRFID, you need to write them in this protocol first. This protocol encodes 40 bits of arbitrary data. Read-only tags that are factory programmed with this protocol are supposed to be unique.
Phidgets represents this protocol as a 10-digit hex string (include leading 0's) ie. "0087f3bc91". This is the format to use for writing new tags, and to expect from the tag events.
ISO11785 defines tags used for animal ID. If you have a pet cat / dog, chances are fairly high that they have one of these tags implanted. FDX-B refers to the way that the ISO11785 data is encoded on the RFID tag, and is the industry-standard encoding scheme.
This tag consists of a 10-bit country code and a 38-bit unique ID.
The country code is ISO 3166. The '999' code is set aside for testing.
The unique ID is 38-bit unsigned, so that's a range of 0 - 274,877,906,943.
Phidgets represents this protocol as a 15-digit decimal number string - concatenated 3-digit country code and 12-digit id. ie. "999000000000123" would represent the testing country code and an id of 123. please note that the 12-digit id part cannot exceed the 38-bit maximum integer value of 274,877,906,943.
Note that Animal tags with a valid country code are supposed to be unique. Of course, with the 1024 you can freely copy an existing Animal Tag.
The PhidgetsTAG protocol is an internal protocol only supported by the PhidgetRFID 1024.
This protocol allows storing an ASCII string, up to 24 characters. ie. "I am a Phidgets Tag!"
The ASCII data must be 7-bit, so no extended ASCII support, but standard text is all supported (as well as control codes).
The PhidgetRFID has four outputs - two of which are available to the user, and two of which are for internal control of the Phidget board only. Output 0 is a +5V source from the USB bus through a P-Channel MOSFET with less than one ohm impedance. This can be used to switch a TTL or CMOS device, or it can be used to drive a 5VDC relay such as the Aromat JS1-5V. Output 1 is an LED drive output at 5VDC with maximum 15mA of available current (250 ohm CMOS output). Both Output 0 and 1 are available in hardware at the terminal blocks on the PhidgetRFID board. If Output 0 is used to drive a relay, a fast clamping diode must be placed across the relay drive pins as shown in the diagram on the right. Not doing so can result in permanent damage to the PhidgetRFID board.
|0||+5VDC Source||Terminal Block|
|1||External LED Drive||Terminal Block|
|LED||Internal LED Drive||Internal Only|
|RF Enable||RF Antenna Enable||Internal Only|
If you are using multiple RFID readers, placing them too close together will cause interference when reading tags. You could work around this problem by rapidly "polling" each 1024 by turning the antenna on, checking for tags, and then turning it off in sequence. Of course, this will lengthen the amount of time it takes for your system to read a tag, since you may have to wait for the nearest reader to become active.
When trying to read tags, you should allow the tag to remain within detection range for at least 50ms. Tags moving through the detection area faster than this may not register at all.
For more information on RFID readers and tags, visit the RFID Primer.
We document API Calls specific to this product in this section. Functions common to all Phidgets and functions not applicable to this device are not covered here. This section is deliberately generic. For calling conventions under a specific language, refer to the associated API manual in the Quick Downloads section for that language. For exact values, refer to the device specifications.
int OutputCount () [get] : Constant
- Returns the number of digital outputs available on this PhidgetRFID. These are the outputs provided by the terminal block.
bool OutputState (int OutputIndex) [get,set]
- Sets/Returns the state of an output. True indicates activated, False deactivated. False is the default state.
bool AntennaOn() [get,set]
- Sets/Returns the state of the antenna. True turns the antenna on, False turns it off. The antenna if by default turned off, and needs to be explicitely activated before tags can be read.
bool LEDOn() [get,set]
- Sets/Returns the state of the onboard LED. True turns the LED on, False turns it off. The LED is by default turned off.
string LastTag () [get]
- Returns the last tag read. This method will only return a valid tag after a tag has been seen. This method can be used even after a tag has been removed from range of the reader.
int LastTagProtocol () [get]
- Returns the protocol of the last tag read. This method will only return a valid protocol after a tag has been seen. This method can be used even after a tag has been removed from range of the reader.
bool TagStatus() [get]
- Returns the state of whether or not a tag is being read by the reader. True indicates that a tag is on (or near) the reader.
void Write(string tag, int protocol, boolean lock)() [get]
- Writes new data to a tag, using the specified protocol. Lock will lock the tag from further writes. See above for string formats according to protocol.
OnOutputChange(int OutputIndex, bool State) [event]
- An event issued when an output has changed.
OnTag(string tagString, int protocol) [event]
- An event issued when a new tag is seen by the reader. The event is only fired one time for a new tag, so the tag has to be removed and then replaced before another OnTag event will fire.
Note: in some languages this event is called Tag2
Note: it is very important not to block in this event, or you will receive extra attach / detach events.
OnTagLost(string tagString, int protocol) [event]
- An event issued when a tag is removed from the reader.
Note: in some languages this event is called TagLost2
|FCC ID: SUT1024-0|
- This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
- (1) This device may not cause harmful interference, and
- (2) This device must accept any interference received, including interference that may cause undesired operation.
- Note: The manufacturer is not responsible for any radio or TV interference caused by unauthorized modifications to this equipment. Such modifications could void the user’s authority to operate the equipment.
- The user is cautioned that any changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment.
- This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
- • Reorient or relocate the receiving antenna.
- • Increase the separation between the equipment and receiver.
- • Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- • Consult the dealer or an experienced radio/TV technician for help.
- This unit was tested with shielded cables on the peripheral devices. Shielded cables must be used with the unit to ensure compliance.
|Date||Board Revision||Device Version||Comment|