Not all sensor network applications can deal with the wiring involved with a wireline CAN solution. Sometimes there is a just a gap that cannot easily be crossed with a wire. Other times it is just not practical, for example because the system is a temporary setup, which does not warrant clean installation of the wiring involved.

CAN-bus is really just intended a wire-based technology and must of it's features depend on the physical medium. However, if we don't bother too much about priorities and bus error features, then there is no reason not to route CAN-bus telegrams over a wireless medium. This is also acknowledged by CAN in Automation, the group behind CANopen, with their publications CiA 315 "Generic frame for wireless tunneling of CAN messages and for transfer of diagnostic data" and CiA 457 "CANopen interface profile wireless transmissions".


  • Wireless networking for CAN-bus data
  • Bridges operate as CANopen® device with device monitoring & configuration and SYNC regeneration
  • Transparent for J1939 or other 29-bit CAN applications
  • Transparent for CAN-FD, FD can be disabled for individual bridges
  • Supports up to 8 clients in the wireless domain in Layer-2 AP mode
  • Supports encrypted point-to-point link in TCP/IP mode
  • Configuration via CANopen or via PC application on micro-USB port
  • Possibility for branding or custom firmware with specific behaviour


L2 Modes allow for direct connections between bridge devices. TCP Modes rely on connection to regular WiFi access-points in order to establish an TCP/IP connection between two devices.
One or more bridge devices in STA mode connect to one bridge in AP mode. Vendor IE allows for identification of WiCAN devices regardless of actual SSID. Both bridges can connect to the same access-point, but also to different access-point accross the globe.
First try as station, become AP if initial connect fails Station mode, connect to SSID or any WiCAN AP Access-point mode Station mode, connect with regular AP


  • Globally approved 2.4GHz ISM band using 802.11b/g/n protocol (Wi-Fi)
  • CANopen® interface profile wireless transmission (CiA 457 + custom)
  • Large FIFO buffers allow for buffering of bursts on either side
  • Separate priority FIFO helps in preserving timing of messages with ID ≤ 0x100
  • Supports LSS node ID assignment and Fastscan (CiA 305)
  • Supports firmware update via wired or wireless CAN interface or locally via USB
  • Supports power management & monitoring features (CiA 302-9 + custom for monitoring of bus voltage, input current, CPU voltage and CPU temperature)
  • Supports custom heartbeat messages, using additional bytes for status


DIN-rail bridge
Wireless CAN-bus bridge for DIN-rail.
IP67 bridge
Wireless CAN-bus bridge IP67.

Wireless performance & limitations

Connecting CANopen devices over a wireless link strips some of the reliablity and ruggedness features of the CAN bus protocol. Additionally, there are bandwidth limitations that are less easiliy defined than with a wireline approach.

Use of more than 2 bridge devices in a network results in multicast transmissions, which decreases effective bandwidth proportionally to the number of bridges. When the wireline feed bitrate and message rate exceeds the available RF bandwidth, increased message latency may occur and ultimately message loss.



Item: Description: Status: Price: Action:
No products yet, please email for your inquiries...
'CANopen' is a registered trademark of CAN in Automation (CiA)