View source for 1024-0 User Guide

__NOINDEX__
__NOTOC__
<metadesc>You can read and write to RFID tags up to 6cm away with the Phidget RFID read/write.  Supports EM4100 series, ASCII and ISO11785 FDX-B protocols.</metadesc>
[[Category:UserGuide]]
==Part 1: Setup==
<div class="phd-deck-sequence">
{{PT1_1024_CHOOSE}}
{{PT1_1024_WIN}}{{PT1_1024_MAC}}{{PT1_1024_LNX}}
</div>

== Part 2: Using Your Phidget ==

===Phidget Control Panel===
You can use the [[Phidget Control Panel]] to explore your device's functionality.

1. After opening the Phidget Control Panel you will find the following channels:

[[Image:1024_Panel.jpg|link=|center]]

2. Double click on a channel to open an example program.
{{UGC-Start}}

{{UGC-Entry|Digital Output | Switchable 5V output (max current 400mA)
|
In your Control Panel, double click on "Digital Output":
[[Image:1024-DigitalOutput.jpg|800px|center|link=]]}}

{{UGC-Entry|LED Driver | Switchable 5V output (max current 16mA)
|
In your Control Panel, double click on "LED Driver":
[[Image:1024-DigitalOutput.jpg|800px|center|link=]]}}

{{UGC-Entry|Onboard LED | Turn on green LED beside USB connector
|
In your Control Panel, double click on "Onboard LED":
[[Image:1024-OnboardLED.jpg|800px|center|link=]]}}

{{UGC-Entry|RFID Reader/Writer| Read or write data from an RFID tag
|
In your Control Panel, double click on "RFID Reader/Writer":
[[Image:1024-RFID.jpg|800px|center|link=]]}}

{{UGC-End}}

{{UG-Part3}}

== Part 4: Advanced Topics and Troubleshooting ==

{{UGC-Start}}
{{UGC-Addressing}}
{{UGC-Firmware}}
{{UGC-Entry|Supported RFID Protocols|
| 
A protocol is a way of encoding data on an RFID tag. 
We support three reading and writing protocols with the 1024:

====EM4100====
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 (e.g. 0087f3bc91). This is the format to use for writing new tags, and to expect from the tag events.

====ISO11785 FDX-B====
ISO11785 defines tags used for animal IDs. If you have a pet cat or dog, chances are 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 [http://en.wikipedia.org/wiki/ISO_3166-1_numeric 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. For example, ''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.

====HID Generic====

'''Note: This protocol is only supported by 1024_1 with firmware version 310 or higher'''

HID tags are commonly used for security and access control applications. There are a number of specific formats that fall under this generic umbrella, so when the PhidgetRFID reads a HID tag, it will simply read in the raw hexadecimal data. This means you can easily clone any HID tag by reading its hex data and writing it to a new tag, but you'll be unable to know which portions of the hex data belong to various headers and which are the actual tag string.

This tag consists of eleven hexadecimal digits. 

====HID H10301====

'''Note: This protocol is only supported by 1024_1 with firmware version 310 or higher'''

HID H10301 is a specific HID format commonly used for 125kHz HID tags. If a HID tag has the specific header data that marks it as a H10301, it will read as one in the PhidgetRFID.

This tag consists of eight decimal digits. When you write a H10301 tag using the PhidgetRFID, it will automatically add the appropriate headers to mark it as an H10301 tag. 

====PhidgetsTAG====
The PhidgetsTAG protocol is an internal protocol only supported by the PhidgetRFID 1024.

This protocol allows storing an ASCII string, up to 24 characters (e.g. ''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).
}}

{{UGC-Entry|Interference from multiple RFID readers|
| 
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.
}}

{{UGC-Entry|FCC Compliance|
| 

{{1024-FCC-Table|1024_0|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.
}}

{{UGC-Entry|Object Speed|
| 
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.
}}

{{UGC-Entry|Further Reading|
| 
For more information on RFID readers and tags, visit the [[RFID Guide]].
}}

{{UGC-End}}