Wi-R BAN
One local network for wearables and machines.
Wi-R BAN connects devices through a localized electric-field channel, on a person or along a suitable conductive structure.
Connect sensing, compute, and interaction with low active chip energy.

Smart glasses, a sensor, a watch, and local compute share a wearable system.
Endpoints follow a suitable conductive structure from base to end effector.
Illustrative endpoint layout. Data connection; each device keeps its own power.
On this page

CURRENT SILICON
YR23 Wi-R BAN
Shipping for integration
- Raw PHY data rate
- 5Mbit/s
- Active chip energy per bit
- ~0.2nJ/bit
- Energy per bit versus the named benchmark
- 38×lower energy per bit
Application throughput is lower and depends on the workload.
About 0.2 nJ/bit, full-chip active TX/RX average at 5 Mbit/s. Excludes sensors and endpoint compute.
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.
The configurations differ. This is not a complete-product battery-life comparison.
PUBLISHED DEMONSTRATION · APRIL 2024
See a real demonstration.
Explore Ixana’s published Wi-R communication video in the demo gallery. Playback is your choice.
This earlier demonstration is separate from the current YR23 silicon measurements. Board revision, cable roles, and current evaluation configuration should be confirmed with the team.
ENDPOINT INTEGRATION
Wi-R goes into both devices.
Connect each host to a Wi-R interface and coupling electrode. Each product retains its own local power supply.
WORKED SYSTEM CONCEPT
Several roles. Shared capacity.
A conceptual wearable system collects sensor and vision payloads, processes them locally, and returns a result.
The sequence below illustrates traffic planning; it is not a validated application or a timing guarantee.

Conceptual transfer sequence
- 02 → 03
Collect sensor readings
The sensor sends its sample payload to local compute when scheduled.
- 01 → 03
Transfer a vision payload
Glasses send a selected image or event to local compute in another transfer opportunity.
- 03 → 04
Return a result
Local compute sends a notification or interaction result to the watch.
These transfers share the connection. They are not independent simultaneous full-rate links. Protocol overhead, retries, host processing, and each payload’s timing requirements reduce the capacity available to applications.
ENGINEERING FIT
What your evaluation needs to establish.
Start with the complete system: endpoints, physical path, power, software, and workload.
Participating devices
Integration considerationEach endpoint needs a Wi-R transceiver, host connection, and coupling interface.
Endpoint architectureLocal power
Integration considerationBudget power for each complete endpoint, including sensors and host processing.
Measurement boundaryHost interface & software
Establish during evaluationRequest the YR23 interface documentation, SDK, and bring-up guide for your hardware revision.
Request integration documentsElectrode, materials & enclosure
Establish during evaluationReview coupling, suitable materials, mechanical geometry, movement, and operating environment together.
Discuss the physical designThroughput & timing
Published measurement / evaluate workloadUse the raw PHY rate as a starting point. Establish payload capacity, scheduling, and latency for your application.
Rate and throughput notesStarting hardware
Published kit contentsThe YR23 kit lists two boards, BER/PER testing, documentation, SDK, and example scripts. Confirm revision and availability when enquiring.
YR23 evaluation kitStart with the right information.
Silicon measurement notes
Public: active chip energy, the named comparison configuration, and what the measurement excludes.
YR23 evaluation kit
Public kit listing: paired boards and evaluation tools. Request the current revision and ordering route.
Request YR23 integration documents
Ask for the matching datasheet, host-interface details, electrode guidance, SDK, and getting-started instructions.
Before you enquire
Do I need a finished design?
No. Bring an early architecture or a general question. A proposed endpoint layout and payload needs help the team identify an evaluation route, but they are optional.
Can I request the software and integration guide?
Yes. Use the enquiry form to request the YR23 datasheet, SDK, host-interface information, and electrode guidance for the intended revision. The team can clarify access and the appropriate starting kit.
Does the chip energy figure predict my battery life?
No. The published figure covers active chip communication under its stated conditions. Your sensors, host processor, power conversion, traffic pattern, and other components need their own power budget.
EVALUATE Wi-R BAN
Let’s discuss what needs to connect.
We’ll discuss your architecture and help identify the appropriate evaluation route. An early idea or a general/company conversation is welcome.
Name and email are enough to start. Company and system details are optional.