Table of Contents
WIOpicoLNet 16 I/O
WIO Overview → WIOesp & WIOpico
- WIO Overview | WIO Setup | WIO Control | User Bitmaps | WIO Firmware | WIO Mobile | Cable | LEDScript | IOScript | WIOpi
Features
- 16 I/O
- 4 Servos
- NEO Pixel
- I2C
GCA PCB
WIO Firmware
- Connect the Pico with the BOOTSEL button pressed with USB.
- An external drive will show up fin the Filemanger/Finder with a name like "RPI-RP2" or "RP2350".
- Copy the correct uf2 file on this drive.
See also WIO Pico Install the firmware for more information.
WIO LNet setup
If the WIOpicoLNet should be used as WiFi bridge the WiFi credentials must be set.
All other settings are under Configuretion.

The […] button will open the options dialog:

LNet must be selected in the preload selection.
Example of a configuration CSV file:
wio-lnet.csv.zip
See also: WIO Setup Maintenance
Addressing
Fixed addressing based on module number.
Base address = module number * 16 + port.
Servos are using the same base address.
NEO Pixel using the module number as Node-ID and start with port 1.
Start of Day
Generally LNet address 1017 is used to trigger on all module a SoD. (Reporting all inputs.)
Because of this Node-ID 63 and port 9 cannot be used.
WIO Address
Maintenance
LocoIO Programming
The WIO address can be set on the LocoIO General tab.
Only the low part can be changed: 1…127.

See also: LocoIO Programming
I/O
The I/O can be configured on the LocoIO Easy Setup tab:

The port numbers are fixed and depends on the WIO address.
See also: LocoIO Programming
Servo
Servos and I/O share the same 4 port numbers of the WIO.
Example setup for servo 1:

Port number is module address * 16 + port.
In this example: 44 * 16 + 1 = 705
Servo Setup
The servo left/right position and speed can be setup on the LocoIO Servo tab:

See also: LocoIO Programming
NEOPixel
NEOPixel addressing is the same as standard WIO, and uses the tunnel packet:
![]()
If the status pixel is used, pixel 1, the LED address is internally increased by one.
Interfaces
WiFi
USB
Uses an ASCII based protocol formatted like this:
.XXXXXX,
Prefix with a dot, LNet bytes are HEXA converted and the packet ends with a comma.
No CTS flow.

Tunnel packet
To be able to use various WIO functions a tunnel packet is defined.
8 Data bytes
| OPC | Length | Destination | Operation | Data | CRC | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0xEC | 15 | Module# | RASCII command | High bits 1 | data 0 | data 1 | data 2 | data 3 | High bits 2 | data 4 | data 5 | data 6 | data 7 | Checksum |
4 Data bytes
| OPC | Length | Destination | Operation | Data | CRC | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0xEC | 10 | Module# | RASCII command | High bits 1 | data 0 | data 1 | data 2 | data 3 | Checksum |
High bits
| # | High bits 1 | High bits 2 |
|---|---|---|
| 0 | data 0 | data 4 |
| 1 | data 1 | data 5 |
| 2 | data 2 | data 6 |
| 3 | data 3 | data 7 |
| 4 | nop | nop |
| 5 | nop | nop |
| 6 | Event flag | nop |
| 7 | - | - |





