Dear Readers,
Wiegand is the wiring convention that lets a card reader tell a door controller which credential was just presented. It is not a card, not a chip and not a security protocol — it is the short, deliberately simple electrical link between the reader at the door and the panel in the cupboard. Understanding that boundary is most of what an integrator needs, so this page starts there.
What the Wiegand interface actually is
Wiegand became a de facto standard rather than a published one. It grew out of the Wiegand effect card readers that dominated access control in the 1980s, and it survived because it was easy to wire, tolerant of long runs, and universally understood by panel manufacturers. Decades later, readers using entirely modern contactless technology still speak it, because the panel on the other end expects it.
A Wiegand link uses three conductors: a common ground and two data lines, usually labelled DATA0 and DATA1, or simply D0 and D1. At rest, both data lines sit at the high level, typically around +5 VDC. To send a bit, the reader briefly pulls one line low and leaves the other alone: pulling D0 low sends a zero, pulling D1 low sends a one. The controller counts the pulses and reassembles the credential.
That one-line-per-bit-value arrangement is the whole trick. It needs no clock, no negotiation and no addressing, which is why it works reliably over cable runs that most interfaces of its era could not manage. Reader manufacturers commonly publish a maximum run of around 500 feet (150 m).
The data: 26 bits, and everything that came after
The original and still most widely referenced format carries 26 bits: a leading parity bit, an 8-bit facility code, a 16-bit card number, and a trailing parity bit. The leading parity is calculated across the first twelve bits and the trailing parity across the last twelve, giving the panel a cheap integrity check on each half of the message.
Those field widths are the format’s main constraint. Eight bits allow 256 facility codes and sixteen bits allow 65,536 card numbers — comfortable for one building, restrictive for an estate. Manufacturers responded by defining their own longer formats with different field layouts and parity schemes, which is why “Wiegand” in practice describes a family of formats rather than one. There is an upper bound: the physical card set the limit, because only about 37 Wiegand wire filaments fit inside an ISO/IEC 7810 CR80 card before reliability suffers, so most access control formats stay under 37 bits.
For an integrator this matters more than the history. A credential whose identifier is longer than the chosen format can carry has to be shortened, mapped or rejected somewhere, and which of those happens is a decision with security consequences. It is worth establishing explicitly for any reader and panel pairing rather than discovering it in commissioning.
What Wiegand does not do
Wiegand carries the credential in clear. There is no authentication of the reader to the panel, no encryption on the wire, and no replay protection. A reader can perform a fully authenticated read of a modern secure credential and then announce the result over an unprotected pair of wires — the trust boundary moves at the connector.
This is not a defect in anyone’s product; it is the age of the convention showing. It is, however, the right question to ask early in a design, because it determines whether Wiegand belongs in the architecture at all or belongs behind additional protection.
Wiegand interface or Wiegand effect?
The two are routinely confused, and searching for one reliably returns the other. The Wiegand effect is a magnetic phenomenon in a specially processed ferromagnetic wire, discovered by John R. Wiegand, which produces a sharp voltage pulse and is used in pulse generators and self-powered sensors. The Wiegand interface described on this page is the wiring convention named after those early readers. Modern Wiegand-interface readers generally contain no Wiegand wire at all.
Where Ambimat fits
Ambimat Electronics designs and manufactures RFID and NFC reader products for OEM integration through the AmbiTap and AmbiPay families. Our work is the reader side of the link described above: the contactless front end, the antenna and enclosure integration, the credential handling, and the host interface that carries the result into your system.
Wiegand interface support for the Ambimat RFID/NFC reader portfolio is under development. It is not available in our current production offering today. We are publishing that status rather than waiting, because the requirements that shape it — which bit formats matter to you, how your controller expects to be driven, what your electrical and cable constraints are — are exactly what we want to hear while the work is being defined.
Discuss your Wiegand reader requirement
If you are designing a reader and controller architecture and Wiegand is part of it, our engineering team would like the details. The more specific the better: the reader application and environment, the RFID or NFC credential types you need to read, the Wiegand format you expect to emit if you already know it, the controller or panel you must interoperate with, any voltage, cable length or isolation constraints, your project timing, and expected volumes.
We will tell you plainly what is available today and what is still under development. Talk to our engineering team.
Frequently asked questions
What is the Wiegand interface?
Wiegand is the wiring convention that lets a card reader tell a door controller which credential was just presented. It is not a card, a chip or a security protocol — it is the short electrical link between the reader at the door and the panel that makes the access decision.
How does Wiegand connect a reader to a controller?
Over three conductors: a common ground and two data lines, usually labelled DATA0 and DATA1. Both data lines idle high. The reader pulls D0 low to send a zero and D1 low to send a one, and the controller counts the pulses and reassembles the credential. There is no clock and no addressing, which is why the link tolerates long cable runs.
Is Wiegand currently supported by Ambimat readers?
No. Wiegand support is under development and is not currently offered as a production interface.
What is Ambimat developing?
Wiegand interface support for the Ambimat RFID/NFC reader portfolio is under development. Bit formats, electrical characteristics, target products and timing are not defined yet. Those requirements are being gathered now, which is why the status is published rather than held back until it is finished.
Is Wiegand secure?
Wiegand carries the credential in clear. There is no authentication of the reader to the panel, no encryption on the wire and no replay protection. A reader can perform a fully authenticated read of a modern secure credential and then announce the result over an unprotected pair of wires, so the trust boundary moves at the connector.
What does Ambimat supply today?
RFID and NFC reader products for OEM integration through the AmbiTap and AmbiPay families: the contactless front end, antenna and enclosure integration, credential handling, and the host interface that carries the result into your system.
References:-
Technical background on the Wiegand interface and its formats is drawn from the following public sources. The explanation above is Ambimat’s own.