Balluff RFID · how a read happens likely band 0 of 5 nothing you enter leaves this browser

An interactive guide

How a read happens

An RFID tag puts your part's identity on the part itself. No battery, no line of sight, no label to keep clean. This page teaches you how that works by letting you operate every piece of it, and it builds your project spec as you go.

Drag the tag toward the read head.
Scroll, and the camera moves with you. The pieces you are about to spec, in the metal: read/write heads, a BIS V processor, data carriers. A real product render, set in motion. All figures on this page are educational envelopes for the technology class; measured pairing data lives in the selector.

Step 1 of 5 · distance

Where the field ends

A short-range reader does not broadcast. It builds a magnetic field that ends, on purpose, a few hundred millimeters out. A tag inside it couples like the secondary of a transformer: the field is both the power and the wire. Drag the tag and find the edge. Past it, a different physics has to take over.

Near field: energy couples through a shared magnetic circuit. Far field: a radio wave travels out and a fainter echo comes back. Envelopes are class-level, not product promises.
Read distance your process needs 80 mm

Drag the tag on the diagram or use the slider.

Likely band, derived
HF · 13.56 MHz

Reach figures are educational envelopes for the technology class, not a promise for a specific product. Measured pairing data lives in the selector.

Step 2 of 5 · mounting

Metal, honestly

Metal near a tag detunes its antenna, which reshapes the tag's coupling field. That is not a wall, it is a design input. A standard tag's field collapses on metal. On-metal and flush tags are engineered so the metal works with their field, and the price is reach. Pick a tag, toggle the surface, watch the field change shape.

The reader's field never changes. What changes is the tag's own coupling field, reshaped by the metal it sits on. Reach figures are measured field data for the technology class.
Your tag
The surface it mounts on
Coupled, reads

Class reach, measured across the technology family: metal-free tags to about 370 mm, on-metal tags to about 100 mm, flush-in-metal tags to about 55 mm. Your product pairing will have its own measured figure in the selector.

Step 3 of 5 · motion

Reading on the move

A read is not instant. The tag has to sit in the field long enough to power up and move its data. On a moving line that budget is pure geometry: time in field equals field window divided by line speed. Spend it on a bigger read than it can hold and the pass misses. Try to break it.

Each pass gets one window. The transfer either finishes inside it or the pass misses. Transfer rates are class-level here; measured rates per pairing live in the selector.
When do you read?
Line speed 18 m/min
What the tag carries
Reads clean

The geometry is exact; the transfer rate shown is a class-level teaching figure. If the budget is tight three moves fix it: read at a standstill, carry less data, or slow the pass through the window.

Step 4 of 5 · population

One tag or many

With one tag in the field the conversation is private and fast. Put several tags in the field and they all answer at once, so the reader has to run anti-collision: sort the voices out and take them in turns. It works, and every turn spends time. Add tags and watch the cycle stretch.

Anti-collision is reliable, not free: the cycle grows with every tag, and collisions cost retries. Times shown are relative, to teach the shape of the cost.
Tags in the field at once
1
One tag: a single handshake

Short-range HF anti-collision handles a handful of tags well when the station can give it time. Reading dozens at once, at range, through a gate is the full UHF problem: real, solved daily, and an engineering project rather than a catalog pick.

Step 5 of 5 · the system

From tag to PLC

Three parts make the system. The tag carries the data. The head is the antenna that talks to it. The processor turns reads into messages your controller already speaks. How the processors connect is a real choice: one processor per read point, straight onto Ethernet, or several heads sharing one BIS V processor or IO-Link master. Build both and watch what your head count does to each.

Either way the PLC never learns RFID, it just gets data on the network it already speaks. What changes is how many devices and network drops stand between the heads and it.
Read points on your line
2

Heads share one processor, up to four per unit.

How they connect
The network your PLC speaks

Every network listed is a real, shipping processor interface, and both architectures are real, shipping Balluff systems. The RFID side is identical under all of them; what changes is how many devices sit between your heads and your controller. Comparisons here are about complexity, not prices; you bring your own numbers.

Balluff BIS M EtherNet/IP processor, front view: status LEDs, power port, and two Ethernet ports labeled Port 1 and Port 2.
The direct option. A BIS M processor puts one read point straight onto Ethernet, with two ports to daisy-chain the line. Simple, popular, one per point.
Balluff BIS V processor, front view: four M12 head ports labeled H1 to H4, power port, and two EtherNet/IP network ports.
The shared option. A BIS V runs four heads (H1 to H4) over a single network drop; this one happens to speak EtherNet/IP.
Balluff IO-Link family on a dark studio background: an IO-Link master block with eight M12 ports, a BIS M unit, an RFID read head, and sensors.
The IO-Link route. Read heads share an IO-Link master's ports alongside your other sensors; the master uplinks to the controller once.
Balluff data carriers: key fob tag, disc tags, a glass capsule tag, and a screw-in bolt tag.
The tags. Discs, fobs, glass capsules, screw-in bolts. The form factor mounts to your part; the physics you just learned stays the same.

Your takeaway

Your spec

Five answers, one starting point. These are class-level envelopes to scope with, not part numbers; the selector holds the measured pairings and will take it from here.

Answer step 1 and the likely band derives itself. No frequency dropdowns here; the band is an outcome, not a preference.
Open the selector with this spec Your answers live in this page's URL. Bookmark or share it to keep them.