User Tools

Site Tools


French VersionDeutsche VersionEnglish Version

WIOpico 16 I/O CAN


The WIO-PicoW-CAN version uses CAN for communication instead of WiFi, and offers an USB interface for communicating with the host computer.
Also a WLAN service is possible but in a wired environment all communications should be wired.
It is also possible to use the CANService as global CAN interface for more flexibility.
So with the coming of this board WIO stands for both Wireless and Wired I/O.

The CAN communication uses the RCAN protocol to be able to efficiently use every byte in the extended CAN packet.



RCAN uses a CAN bus speed of 125k and can be integrated in a CBUS environment.
The CAN Interface must be able to process extended CAN packets, and the RCAN protocol must also be enabled.


MBUS uses a CAN bus speed of 250k and can be integrated in a Märklin compatible environment.
With this protocol active the WIO-Pico-CAN can only be used as interface between CAN and Rocrail.



Option Required Remark Default
I/O YES Process I/O over CAN.
USB-Bridge Optional 250kb USB interface.
RCAN YES WIO-Pico-CAN only evaluate the RCAN protocol.
Pico CAN YES Needed for the pin to PCB mapping.
NeoPixel on servo4 Optional NeoPixel on GP20; Servo 4 will be disabled. J1-3 (GP8)

The CAN options can also be set on the Maintenance Tab:


Protocol: RCAN or RCAN+CBUS if the CAN bus is mixed.


The WIO firmware cannot be updated over CAN.
Temporary WiFi credentials can be set on the Update Tab. The WIO-Pico-CAN will make a WiFi connection and will be visible on the Query Tab.(Refresh)
Select the WIO-Pico-CAN and upload the WIO binary on the Update Tab as usual.
After the update the WIO-Pico-CAN will reboot without the temporary WiFi credentials.


LEDScript, IOScript and AMP files can be transferred over CAN on the File Tab.
The WiFi credentials on the Update Tab can also be used for accessing files by browser.


wio/wiopico-io16can-en.txt · Last modified: 2024/07/18 21:56 by rjversluis