Remote updates
ESP32, ESP8266 and Raspberry Pi Pico devices install new code sent from the MCode IDE, with nothing in the sketch beyond calling run(). Every update is signed by MaxwellTrack.
Which boards
- ESP32 over WiFi or a cellular modem. On a weak cellular signal a stalled download continues from where it stopped.
- ESP8266 over WiFi.
- Raspberry Pi Pico and Pico 2 over their modem, Pico W and Pico 2 W over WiFi. The board needs a file system area for the update: the MCode IDE sets it for you; in the Arduino IDE choose a Tools > Flash Size with an FS, in PlatformIO set
board_build.filesystem_size. - Every other board is updated with a firmware file over USB. The MCode IDE builds that file for you.
How an update arrives
Deploy in the MCode IDE builds the code and sends the update to the device. The device downloads it over a secure connection, checks it, and restarts into the new code. The IDE's build history shows each update from sent to installed, with the download progress. An update sent while the device was offline is sent again when it reconnects.
Signed updates
Every update is signed by MaxwellTrack. Before switching to new code the board checks the signature against the keys built into the library, and installs nothing else, so nobody can put code on your devices, even with access to their network. An update that fails the check shows bad signature in the build history, and the board keeps running its current code. Boards on library 1.3 or earlier keep receiving updates as before.
The version in the console
Builds from the MCode IDE set the version for you. For code built elsewhere, define it before the include and the console shows it beside the device:
#define MAXWELLTRACK_FW_VERSION "1.4.0"
#include <maxwelltrack.h>Keep the connection code
Every update must keep begin() with the device's ID and access token, and run() in loop(). Code without them starts offline, cannot receive the next update, and needs a USB cable to recover.
Something unclear or out of date on this page? Tell support.
