MCode IDE
Write device code in the browser, build it in the cloud, and update the device remotely. No toolchain to install, no cable after the first time.
Open it
Open MCode IDE in the sidebar and pick a device, or open a device and choose its MCode tab. Choose the board, and the editor starts with code that connects that device. Projects save as you type and can hold several files.
First-time flash
A device needs code that can receive updates before the first remote update. Choose First-Time Flash, pick how the device connects (WiFi, cellular LTE on an ESP32, or a cellular modem on any board), download the starter, add your access token and network details, and upload it once with the Arduino IDE. From then on the device takes updates remotely.
Build and update
| Action | What it does |
|---|---|
| Verify | Builds your code and reports problems. Nothing is sent to the device. |
| Deploy | Builds, then sends the update to the device, which restarts into the new code. |
| Stop | Cancels a running Verify or Deploy. |
| Rollback | Sends an earlier successful build again, without rebuilding. |
| Build firmware file | For boards updated over USB: builds a file to download and flash. |
The build history shows each update's delivery to the device, from sent to installed, or why it failed on the device. A device that was offline when you deployed receives the newest update when it reconnects.
Boards and updates
ESP32, ESP8266 and Raspberry Pi Pico boards update remotely, and every update is signed by MaxwellTrack: a board on library 1.4 installs nothing else. STM32, Arduino UNO R4, Zero, MKR, Mega and Uno boards get a firmware file you flash over USB. See Supported boards.
Problems and MCoder
Every problem, from a missing setting to a compiler error, appears in the Problems panel with one action, usually Fix with AI. MCoder, the assistant inside the editor, proposes a change that you review and apply; it never edits your code on its own. You can also ask it to explain, extend or tidy your code.
MCoder answers questions about the code. Ask it about the account, a reading, an alert or billing and it shows an Ask MaxwellTrack AI button that hands the question to the assistant.
Libraries
Search the library manager and add a sensor driver with one click. Common libraries also resolve from an #include alone. The MaxwellTrack library is always included.
Keep the connection code
Every sketch you deploy must keep the begin() and run() calls with the device's ID and access token. Without them the device starts offline and can only be recovered over USB.
Something unclear or out of date on this page? Tell support.
