Supported boards
Which boards the library runs on, how each one connects, and how each one is updated.
| Board family | Arduino core | WiFi | Cellular modem | Code updates |
|---|---|---|---|---|
| ESP32, ESP32-S2, ESP32-S3, ESP32-C3 | esp32 2.x or 3.x | Yes | Yes | Remote |
| ESP32-C6 | esp32 3.x | Yes | Yes | Remote |
| ESP8266 (NodeMCU, Wemos D1 mini) | esp8266 3.x | Yes | Remote | |
| Raspberry Pi Pico (RP2040), Pico 2 (RP2350) | Raspberry Pi Pico/RP2040 by Earle Philhower | Yes | Remote | |
| Raspberry Pi Pico W, Pico 2 W | Raspberry Pi Pico/RP2040 by Earle Philhower | Yes | Yes | Remote |
| Arduino UNO R4 WiFi | Arduino UNO R4 Boards | Yes | Yes | USB |
| Arduino UNO R4 Minima, Nano R4 | Arduino UNO R4 Boards | Yes | USB | |
| Arduino MKR WiFi 1010, Nano 33 IoT | Arduino SAMD, with the WiFiNINA library | Yes | Yes | USB |
| STM32 F1, F4, G0, H7 and the same CPUs | STM32 core by STMicroelectronics | Yes | USB | |
| Arduino Zero, MKR | Arduino SAMD | Yes | USB | |
| Arduino Mega 2560, Uno, Nano | Arduino AVR | Yes | USB |
Remote means updates sent from the MCode IDE over the board's own connection, WiFi or modem; see Remote updates. On any other board the build stops with MaxwellTrack has no build for this board. The Uno and Nano compile, but with 2 KB of memory little is left for your own code; use a Mega or an UNO R4 for real projects. On the Nano the full cellular example is just too large for its 30 KB of program space; the MCode IDE's starter sketch fits.
In the MCode IDE
The MCode IDE builds for every family above except ESP32-C6, which needs Arduino core 3.x: build that board in the Arduino IDE or PlatformIO. For boards updated over USB, the IDE builds a firmware file (.bin, .uf2 or .hex) to download and flash.
Modems
Most 2G and 4G modems work. See Check your modem for what to look for, and give the modem a supply that can deliver 2 A peaks.
Memory
| Board | Offline buffer | Largest message | Per-key handlers |
|---|---|---|---|
| ESP32 | 4096 bytes | 512 bytes | 16 |
| ESP8266, STM32, RP2040, SAMD | 2048 bytes | 512 bytes | 16 |
| Mega 2560 | 512 bytes | 256 bytes | 8 |
| Uno, Nano | 128 bytes | 192 bytes | 4 |
The buffer and message memory are set aside once, at begin(), and reused, so sending never grows or fragments the heap. Change them with setQueueSize() and setMaxPayload(); see Offline buffer.
Something unclear or out of date on this page? Tell support.
