Home     Contact     Projects     Experiments     Circuits     Theory     BLOG     PIC Tutorials     Time for Science     RSS     Terms of services     Privacy policy  
   
 Home      Projects     Experiments     Circuits     Theory     BLOG     PIC Tutorials     Time for Science   



RFID Access ZoneAuthor
Panagiotis†Kalogeris
April 12, 2012

.

Wiegand Protocol

The Wiegand interface consists of three wires called
Data Zero (usually green),
Data One (usually white), and
Data Return (usually black).
The three wires carry Wiegand data, also called the Wiegand signal.
Since the card data is binary, the reader simply receives the radio frequency (RF) data from the card, translates it from RF to Wiegand protocol and sends the complete binary string to the controller. Zeros travel on the green wire, ones on the white wire and the controller combines the two strings of characters into the original set of binary data.


The article below was copied from wikipedia.

The communications protocol used on a Wiegand interface is known as the Wiegand protocol. The original Wiegand format had one parity bit, 8 bits of facility code, 16 bits of ID code, and a trailing parity bit for a total of 26 bits. The first parity bit is calculated from the first 12 bits of the code and the trailing parity bit from the last 12 bits. However many inconsistent implementations and extensions to the basic format exist.

Many access control system manufacturers adopted Wiegand technology but were unhappy with the limitations of only 8 bits site codes (0-255) and 16 bits for card numbers 0-65535)so they designed their own formats with varying complexity of field numbers and lengths and parity checking.

The physical size limitations of the card dictated that a maximum of 37 wiegand wire filaments could be placed in a standard credit card as dictated by CR80 or ISO/IEC 7810 standards before misreads would effect reliability hence most Wiegand formats used in physical access control are less than 37 bits in length.

An advantage of the Wiegand signaling format is that it allows very long cable runs, far longer than other interface standards of its day allowed.


Data Signals

Figure 1 below displays the timing pattern for data bits sent by the reader to the access control panel. This
timing pattern falls within the Wiegand guidelines as proscribed by the SIAís Access Control
Standard Protocol for the 26-Bit Wiegand Reader Interface (a Pulse Width time between 20 uS and
100 uS, and a Pulse Interval time between 200 uS and 20 mS).
The Data 1 and Data 0 signals are held at a logic high level (above the Voh level) until the reader is
ready to send a data stream. The reader places data as asynchronous low-going pulses (below the
Vol level) on the Data 1 or Data 0 lines to transmit the data stream to the access control panel (the
"saw-teeth" in Figure 1). The Data 1 and Data 0 pulses will not overlap or occur simultaneously.
Below the schematic is provided the minimum and maximum allowable pulse width times (the duration of a pulse)
and pulse interval times (the time between pulses) for Pyramid Series Readers.



 



Tpw : Pulse Width Time = 100 Ķs
Tpi : Pulse Interval Time = 1 ms




HID Wiegand Protocol (Taken from HID)

So as you read to the article above,manufacturers created their own protocol depending of their needs.
HID uses both the the Standard 26-Bit Format and the Corporate 1000 format consisting of 35 bits with 2 more parity birs.HID gives a variety of formats and i will post some here just for mention.

The Standard 26-Bit Format

The format in which a card is programmed is determined by the data pattern that will be compatible with the access control
panel. All HID credentials (card, fobs, tags, etc.) can be programmed with the standard 26-bit card data format.
The Standard 26-bit Format is an Open Format.
An Open Format means that anyone can buy HID cards in a specific format and that specific format description is publicly
available. The 26-bit format is a widely used industry standard and is available to all HID customers. Almost all access
control systems accept the standard 26-bit format. 26-bit originated with true Wiegand swipe card technology.
The Standard 26-bit format has 255 possible facility codes from one to 255. There can be up to 65,535 card ID numbers, from one to 65,535,
per facility code. The total number of cards that can use the entire range without duplication is 16,711,425. There are no
restrictions on the use of this format. It is not documented by HID and HID does not restrict duplication of card numbers.


 


* The maximum Facility Code is 255 because if all eight Facility Code bits are set to ones, they equal 255 decimal.
* The maximum Card Number is 65,535 because when all sixteen Card Number field bits are ones, it equals decimal 65,535.

A NOTE ON PARITY: A parity bit is used as a very simple quality check for the accuracy of the transmitted binary data. The
designer of the format program will decide if each parity bit should be even or odd. A selected group of data bits will be
united with one parity bit, and the total number of bits should result in either an even or odd number.
In the example above, the leading parity bit (even) is linked to the first 12 data bits. If the 12 data bits result in an odd
number, the parity bit is set to one to make the 13-bit total come out even. The final 13 bits are similarly set to an odd total



Other Hypothetical Formats
To further clarify how formats may be organized, we present two additional hypothetical examples.
NOTE: Since actual formats do require a varying degree of security, we will only present hypothetical examples with the
exception of standard 26-bit

In the standard 26-bit format, H10301, or the programmable field is specified as the Facility Code. The incrementing field
is called the Card Number. These data groupings can have many different names depending upon which format is under
discussion. The same name usually means something different from format to format. Therefore, another hypothetical
format could look like this:


 


The Leading Parity bit could relate to one subset of the data string and the Second Parity bit relate to an entirely different
subset. This format also has fields named Facility Code and Card Number, but if you compare it to H10301, its format is very
different, and would probably not work on a customerís system that was setup for H10301.
The person who creates the formatís unique field names has the ability to assign the names as well. Review the following
hypothetical format:


 


This format has three parity bits, a five-bit programmable field called Job Number, another four-bit programmable field called
Run Code, and an 18-bit incrementing field called Employee Number.



Corporate 1000

HID offers a unique card data format program named Corporate 1000, where the end user owns the unique format and HID
guarantees that the customerís format will not be duplicated. Furthermore, the customer must provide written authorization
to HID for an integrator or distributor, etc. to be able to purchase the specified Corporate 1000 cards from HID. This gives the
customer absolute control over the manufacture, distribution and delivery of their specific cards. Additional Corporate 1000 facts:

* The customerís access control panels must be capable of decoding the Corporate 1000 format.
* All Corporate 1000 formats are 35 bits long but the data will be arranged in different increments along that 35-bit string.

A card number, for example, may be broken into three or more parts and randomly spaced along the string.
This ensures uniqueness in every Corporate 1000 format.

* HID currently manages several hundred unique Corporate 1000 formats and many more are still readily available.
* As with all other formats, Corporate 1000 formats are identical in 125 kHz Prox and 13.56 MHz iCLASS contactless smart card technology.


Continue reading. Click here to read the worklog.
 OR click here to view the presentation.



Comments

  Name

  Email (shall not be published)

  Website

Notify me of new posts via email


Write your comments below:
BEFORE you post a comment:You are welcome to comment for corrections and suggestions on this page. But if you have questions please use the forum instead to post it. Thank you.


      

  • At 26 May 2013, 20:07:12 user atakan wrote:   [reply @ atakan]
    • @Panagiotis Kalogeris hello, thank you. To walk out of here if I'd share. Maybe those will help a step further.


  • At 22 May 2013, 12:18:38 user Panagiotis Kalogeris wrote:   [reply @ Panagiotis Kalogeris]
    • Yes of course but the only limitation is that the reader should support "Wiegand protocol" since the pic's firmware was built to support wiegand protocol.
      HID has another one type of reader where it's called clock and data interface but i haven't looked at it to tell you how it works....

      look to the link below second line....

      https://www.hidglobal.com/products/readers/hid-proximity/5365

      *Available with Wiegand or Clock-and-Data interface.


  • At 21 May 2013, 21:02:20 user Atakan wrote:   [reply @ Atakan]
    • I saw. I apologize for that. References used in the sense of our language tool. That's why I did not notice. I apologize again for that.

      I want to ask one more thing. Is it possible to use as an alternative to other rfid module?


  • At 21 May 2013, 8:13:15 user Panagiotis Kalogeris wrote:   [reply @ Panagiotis Kalogeris]
    • DID YOU VISIT THE REFERENCE SECTION ????????

      (Most readers at least two brands i know have same cable color code)


      You will need 4 wires
      = RED
      - = BLACK
      data0 = GREEN
      data1 = WHITE

      the reader has the pinout behind of it.The other cables are used to control the front indicator led, the buzzer, the hold function etc

      READ THE "WORKLOG" AND THE "REFERENCE" SECTIONS!!!!!


  • At 19 May 2013, 21:06:31 user Atakan wrote:   [reply @ Atakan]
    • Thank you for your response. reader found on ebay. Can you give information about which color to connect the cables, which end?


  • At 18 May 2013, 23:38:00 user Panagiotis Kalogeris wrote:   [reply @ Panagiotis Kalogeris]
    • Hello Atakan did you checked the reference section? (Its Below main label 3rd tab...You will find Some important info there...)
      I don't know what circuit has the reader on it....Perhaps you should contact HID for further assistance on the particular reader.....

      Regards Panagiotis


  • At 16 May 2013, 22:43:42 user Atakan wrote:   [reply @ Atakan]
    • Hello, I am a student. Required to be done in this thesis project. However, I do not know enough. I want to use your project. Can you give me information about the used RFID reader? If possible, could you give extensive information by e-mail?

      Thank you. Respect for labor.


  • At 29 December 2012, 14:22:55 user Panagiotis Kalogeris wrote:   [reply @ Panagiotis Kalogeris]
    • Hello Egzon!.Well right now the firmware that i have uploaded to the site has the ability to erase the whole eeprom (and the 5 positions).But i am working on a new firmware where you will select the card that you want to erase...and some new features including the bug that i didn't thought where hectrap told me... :-)


  • At 28 December 2012, 7:56:41 user Egzon Mulaj wrote:   [reply @ Egzon Mulaj]
    • can we erase a sector of eeprom and write to another sector of eeprom ?


  • At 8 June 2012, 20:48:14 user Panagiotis Kalogeris wrote:   [reply @ Panagiotis Kalogeris]
    • No you will have to re-erase the eeprom and then store again the cards you want.Nice observation though...i will make the correction to the new firmware :-)


  • At 8 June 2012, 20:38:19 user Giorgos Lazaridis wrote:   [reply @ Giorgos Lazaridis]
    • @herctrap you little devil :D :D :D


  • At 8 June 2012, 20:20:02 user herctrap wrote:   [reply @ herctrap]
    • If i erase the eeprom
      and then add 5 times the card "1"
      then i will be able to enter a new card?



    delicious
    digg
    reddit this Reddit this
    Faves



     HOT in heaven!


    NEW in heaven!



    New Theory: AC electric motor working principle



     Contact     Forum     Projects     Experiments     Circuits     Theory     BLOG     PIC Tutorials     Time for Science     RSS   

    Site design: Giorgos Lazaridis
    © Copyright 2008
    Please read the Terms of services and the Privacy policy