Getting Started
1. Install the device description
Section titled “1. Install the device description”- Download
CODESYS_Control_Pico2_W.devdesc.xml. - In CODESYS: Tools → Device Repository → Install…
- Select the downloaded
.devdesc.xmlfile and confirm.
The device then appears in CODESYS Control devices as:
| Name | nXPico W |
| Vendor | nexo S.r.l. |
| Device ID | 167e 2008 |
| Version | 3.5.20.101 |
2. Create a project and add the device
Section titled “2. Create a project and add the device”- File → New Project… → Standard project.
- As the device, pick nXPico W.
- Under the device node, the IO e WiFi module (I/O, analog inputs, LED, temperature, WiFi parameters) is added automatically — see IO Mapping and WiFi Configuration.
3. Connect and configure WiFi
Section titled “3. Connect and configure WiFi”- Connect the board over micro-USB. The CODESYS gateway runs over USB (it is COM1 inside the runtime), as on nXPico: login, download and monitoring always go through the cable. Programming over WiFi is not available.
- In the device editor’s Communication Settings, scan for the device and select it.
- Set the WiFi SSID/password and IP settings — see WiFi Configuration — then Login and download the application: the board joins the network and WiFi is available to the application.
At the first login CODESYS asks you to create the administrator user: the board has no default users or passwords. See Users and Passwords.
Runtime limits
Section titled “Runtime limits”Same limits as nXPico:
| Setting | Value |
|---|---|
| Cyclic IEC tasks | 3 — a fourth one is refused with an error at download or at startup |
| Max task priority | 31 |
| Default cycle time | 100 ms |
| Code + constants (flash) | 1 MB, executed in place (XIP) |
| Data (variables) | 20 KB |
| I/O image | 1280 bytes input, 1280 bytes output |
| Online change | Not supported — full download only |
| Max applications | 1 (Application) |
| Force / write variables | Supported |
| Breakpoints | Not available — see below |
Task priorities are honoured: a higher-priority task interrupts a lower-priority one that is running.
The code, up to 1 MB, is written to flash sector by sector during the download. If the download is interrupted (for example by unplugging the USB cable), no application starts at the next boot: never a half-written one.
Breakpoints. The board is protected by secure boot, and the chip’s protection disables debugging: the red dot appears in the IDE, but execution does not stop. Monitoring, writing and forcing variables remain available.
Next: IO Mapping, WiFi Configuration, Serial Ports and ST Examples.