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".
Functionality
Wireless networking for CAN-bus data
Bridges operate as CANopen® device with device monitoring & configuration
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
Mode L2
In Layer-2 mode, one bridge operates in access-point mode. The other bridges operate in station mode and connect to the AP-mode bridge. The default mode is Layer-2-AUTO, this starts the bridge in station mode and tries to connect to a access-point bridge. If no such bridge is found,