Skip to technology content

Wi-R TECHNOLOGY

How the
wireless wire
works

Localized electric fields connect wearable devices, extend along conductive structures, and bridge short gaps.

Woman wearing smart glasses, a wearable sensor, a watch, and a pocket compute device, surrounded by an illustrative localized orange envelope.

The connection stays close to the system

01 THE MECHANISM

Keep the connection
close to the system

Choose a physical connection context

Wi-R BAN

Connect the devices
Keep the signal local

Wi-R-enabled wearable devices communicate through a localized electric-field channel.

Sensing Compute Interaction

Each participating device needs a Wi-R interface.

Smart glasses and pocket compute communicate through an illustrative localized electric-field envelope.
Smart glassesWi-R endpoint
Pocket computeWi-R endpoint

Wi-R BAN

Connect along
the structure

Use a suitable conductive structure as part of the communication channel between participating endpoints.

Sensors Compute Control

The structure and endpoint integration must be evaluated together.

Left-facing articulated robot with highlighted joint and end-effector locations.

Wi-R NFE

Bridge the
short gap

Connect two nearby devices with a localized electric-field link. Wi-R is integrated at both endpoints.

Gap, orientation, and enclosure design are configuration-specific.

Two illustrative devices, each with Wi-R, communicating across a short gap.
Device A
Wi-R endpoint
Short gapDevice B
Wi-R endpoint

Illustrative localized channel; not a measured field map or wireless power.

02 INTEGRATION

Wi-R at each endpoint

A local link connects the devices. Each device still has its own sensing, processing, and power requirements.

Functional data connection; local power remains separate.

01 Integrate Wi-R at both ends

02 Local power remains separate

03 Compute can sit where it fits best

03 PERFORMANCE

Continuous data Less energy

Wi-R COMMUNICATION ENERGY

~0.2nJ/bit

About 0.2 nJ/bit, full-chip active TX/RX average at 5 Mbit/s.

NAMED BENCHMARK

38×

Lower communication
energy per bit

Nordic nRF54L15, Bluetooth LE 2M, +4 dBm.

What this comparison means

This is an energy-per-bit comparison at stated operating points. It is not a comparison of battery life for a complete product, delivered application throughput, or every Bluetooth implementation.

Wi-R scope
About 0.2 nJ/bit, full-chip active TX/RX average at 5 Mbit/s.
Comparator
Nordic nRF54L15, Bluetooth LE 2M, +4 dBm.
Application result
Depends on the complete endpoint and its workload.

Energy comparison: Wi-R at 5 Mbit/s, approximately 0.2 nJ/bit, full-chip active TX/RX average. Comparator: Nordic nRF54L15, Bluetooth LE 2M, +4 dBm.

Rate, power, and range must be compared for the same product and configuration.

04 SILICON

Start with the right silicon

Starting to sample

20 Mbit/s

XA-NFE3001

20 Mbit/s silicon is starting to sample. This is separate near-field silicon; the stated rate is the raw PHY rate, not application throughput.

Explore XA-NFE3001

05 SYSTEM ARCHITECTURE

Put the right function
in the right place

Sensing, compute, and interaction do not have to live in one enclosure.

Choose an illustrative system architecture
01

Smart glasses

Sensing, interaction, and local processing

02

Biosensor

A wearable sensing endpoint

03

Pocket compute

A location for additional processing

04

Watch

Sensing, feedback, and interaction

More than one place to compute

Local processing in the glasses and additional pocket compute are two illustrative placements. Wi-R provides the link; the application determines how work is distributed.

Glasses Pocket compute
Illustrative personal system with smart glasses, a wearable sensor, a watch, and pocket compute.
01

Joint sensing

Distributed sensing along the structure

02

End-effector sensing

Tactile and task-specific endpoints

03

Compute and control

Processing where the architecture needs it

Separate the data link from the control design

This is an illustrative architecture, not a certified control topology. Timing, fault response, power delivery, and integration across joints need system-specific evaluation.

Left-facing articulated robot with highlighted joint and end-effector locations.

Illustrative architectures, not deployed reference designs. Numbered leaders identify functional locations, not physical data cables.

06 CHOOSE YOUR CONNECTION

Along a system
or across a gap

07 GO DEEPER

Inspect the evidence

DEMONSTRATIONS

Browse demonstrations

Explore working Wi-R demonstrations in personal and embedded systems.

BEFORE YOU BUILD

A few practical questions

What needs to be integrated at each endpoint?

Each participating device needs a Wi-R interface and the host integration appropriate to the chosen product. Start with the relevant product documentation and evaluation hardware.

Does the data link also deliver wireless power?

Data connectivity and power delivery are separate design questions. Evaluate the power requirements of each endpoint in your configuration.

How should I compare rate, power, and range?

Compare identified products at stated operating points. Distinguish raw data rate from application throughput and IC energy from system power. Treat distance along a structure, distance away from it, and the gap between NFE devices as separate measurements.

Can an existing phone join without modification?

Participating endpoints need the corresponding Wi-R integration or an appropriate external interface. An unmodified phone or wearable does not automatically join the system.

EVALUATE Wi-R

What needs
to connect?

Tell us which endpoints need to connect, what data they carry, and what physical constraints apply. Start with your architecture, then choose the silicon.

YOUR STARTING POINT

01

The participating devices

02

The data rate and workload

03

The system layout and device spacing

Discuss your architecture Explore developer kits