Mparadis at 14:24, 9 May 2018

2018-05-09T14:24:22Z

← Older revision		Revision as of 14:24, 9 May 2018
Line 1:		Line 1:
			__NOINDEX__
	[[Category:UserGuide]]		[[Category:UserGuide]]
	{{UserguideTOC\|1024.jpg\|1024}}		{{UserguideTOC\|1024.jpg\|1024}}

Mparadis: /* Product History */

2016-04-19T21:18:29Z

Product History

← Older revision		Revision as of 21:18, 19 April 2016
Line 226:		Line 226:
	{{UGhist}}		{{UGhist}}
	{{UGrow\|February 2013\|0\|100\|Product Release}}		{{UGrow\|February 2013\|0\|100\|Product Release}}
			{{UGrow\|October 2015 \|0\|101\|OS X El Capitan USB bug fix}}

Mparadis: /* API */

2015-01-22T21:57:19Z

API

← Older revision		Revision as of 21:57, 22 January 2015
Line 153:		Line 153:

	{{UGapi\|bool AntennaOn() [get,set]		{{UGapi\|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.		\|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 explicitly activated before tags can be read.
	}}		}}

Mparadis: /* Product History */

2014-04-02T15:58:00Z

Product History

← Older revision		Revision as of 15:58, 2 April 2014
Line 221:		Line 221:

	==Product History==		==Product History==

			The 1024 - PhidgetRFID Read/Write replaced our previous RFID Reader, the [{{SERVER}}/products.php?product_id=1023 1023 - PhidgetRFID].

	{{UGhist}}		{{UGhist}}
	{{UGrow\| \|0\|100\|Product Release}}		{{UGrow\|February 2013\|0\|100\|Product Release}}

Mparadis: /* EM4100 */

2013-06-21T19:13:28Z

EM4100

← Older revision		Revision as of 19:13, 21 June 2013
Line 75:		Line 75:

	====EM4100====		====EM4100====
	EM4100 (also known as EM4102) is the protocol that all previous PhidgetRFID readers have supported. This protocol encodes 40 bits of arbitrary data. Read-only tags that are factory programmed with this protocol are supposed to be unique.		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.		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.

Mparadis: Created page with "Category:UserGuide {{UserguideTOC|1024.jpg|1024}} ==Getting Started== ===Checking the Contents=== {{UGbox| '''You should have received:''' * A PhidgetRFID * A USB Cable |..."

2013-06-05T18:52:41Z

Created page with "Category:UserGuide {{UserguideTOC|1024.jpg|1024}} ==Getting Started== ===Checking the Contents=== {{UGbox| '''You should have received:''' * A PhidgetRFID * A USB Cable |..."

New page

[[Category:UserGuide]]
{{UserguideTOC|1024.jpg|1024}}
==Getting Started==

===Checking the Contents===
{{UGbox|
'''You should have received:'''
* A PhidgetRFID
* A USB Cable
|
'''In order to test your new Phidget you will also need:'''
* A compatible RFID tag
||}}

===Connecting the Pieces===
{{UGbox|
Connect the PhidgetRFID board to the computer using the USB
cable.
|[[File:1024_0_Connecting_The_Hardware.jpg|400px|link=]]
||}}

===Testing Using Windows 2000 / XP / Vista / 7===

{{UGwin}}

===Running Phidgets Sample Program===

{{UGwin2|'''PhidgetRFID-Full'''}}

{{UGbox|
Double Click on the [[File:Ph.jpg|link=]] icon to activate the Phidget Control Panel and make sure that '''Phidget RFID''' is properly attached to your PC.
|[[File:1024_0_Control_Panel_Screen.jpg|400px|link=]]
|
# Double Click on '''Phidget RFID Read-Write''' in the Phidget Control Panel to bring up RFID-full and check that the box labelled Attached contains the word True.
# Click on the Antenna Enabled box to enable the antenna.
# Click on the LED Enabled box to turn the on-board LED on or off.
# The Output 0 box controls the +5V digital output and the Output 1 box controls the external LED digital output.
# When the Keyboard Output is Enabled, the identification string will be written at the cursor point in an application running in active window on the PC (such as a word document, for example).
# Bring an RFID tag close to the PhidgetRFID board and check that the identification string is displayed. Make sure that the Antenna is enabled for this step.
# When a tag is read, its protocol is displayed here.
# Type the tag string here when writing to a writeable tag. You must use the proper string length and characters according to your chosen protocol.
# When writing, choose your protocol from this drop-down list. For more information on supported protocols, see the [[#Tag_Types|Tag Types]] section.
# When checked, this box will permanently write to a tag. '''Once a tag is written with the lock on, it can not be re-written.'''
# Once you've selected the protocol and string, press this button to write to the tag currently within range.
|[[File:1024_0_RFID_Screen.jpg|400px|link=]]
}}

===Testing Using Mac OS X===

{{UGmac|Phidget RFID|RFID-full}}

===Using Linux===

{{UGlinux}}

===Using Windows Mobile / CE 5.0 / CE 6.0===

{{UGce}}

==Technical Details==

===Tag Types===

We support read-only tags that have been programmed with a supported protocol, as well as T5577 type tags for writing.

====T5577====

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.

===Protocols===

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====
EM4100 (also known as EM4102) is the protocol that all previous PhidgetRFID readers have supported. 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 FDX-B====
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 [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. 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.

====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. 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).

===Controlled Outputs===
[[image:Rfid_relay.png|thumb|310px|link=|Make sure to attach a diode across the terminals of the relay if you are using output 0 on the RFID board to drive it.]]
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.

{| style="border:1px solid darkgray;" cellpadding="7px;"
|+'''1024 Outputs'''
|-style="background: #d1d1d1" align=center
!Output || Function || Connection
|-
|style="background: #f0f0f0" align=center| 0
|style="background: #f0f0f0" align=center| +5VDC Source
|style="background: #f0f0f0" align=center| Terminal Block
|-
|style="background: #f0f0f0" align=center| 1
|style="background: #f0f0f0" align=center| External LED Drive
|style="background: #f0f0f0" align=center| Terminal Block
|-
|style="background: #f0f0f0" align=center| LED
|style="background: #f0f0f0" align=center| Internal LED Drive
|style="background: #f0f0f0" align=center| Internal Only
|-
|style="background: #f0f0f0" align=center| RF Enable
|style="background: #f0f0f0" align=center| RF Antenna Enable
|style="background: #f0f0f0" align=center| Internal Only
|}

 

===Interfering Signals===

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.

===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.

===Further Reading===

For more information on RFID readers and tags, visit the [[RFID Primer]].

==API==
{{UGapih}}

===Functions===

{{UGapi|int OutputCount () [get] : Constant
|Returns the number of digital outputs available on this PhidgetRFID. These are the outputs provided by the terminal block.
}}

{{UGapi|bool OutputState (int OutputIndex) [get,set]
|Sets/Returns the state of an output. True indicates activated, False deactivated. False is the default state.
}}

{{UGapi|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.
}}

{{UGapi|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.
}}

{{UGapi|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.
}}

{{UGapi|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.
}}

{{UGapi|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.
}}

{{UGapi|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.
}}

===Events===
{{UGapi|OnOutputChange(int OutputIndex, bool State) [event]
|An event issued when an output has changed.
}}

{{UGapi|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.
}}

{{UGapi|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
}}

==Compliance==
{|
|rowspan="3"|[[File:Fcc-logo.png|caption|95px]]
|'''Phidgets Inc'''
|-
|'''1024_0'''
|-
|'''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.

==Product History==
{{UGhist}}
{{UGrow| |0|100|Product Release}}

1024 User Guide - Revision history

Mparadis at 14:24, 9 May 2018

Mparadis: /* Product History */

Mparadis: /* API */

Mparadis: /* Product History */

Mparadis: /* EM4100 */

Mparadis: Created page with "Category:UserGuide {{UserguideTOC|1024.jpg|1024}} ==Getting Started== ===Checking the Contents=== {{UGbox| '''You should have received:''' * A PhidgetRFID * A USB Cable |..."