Start here

Coming from Wokwi

Your Wokwi projects open in Mokxi as they are. Here is what each Wokwi idea is called here, and what changes.

Bring a project over

The import itself, file by file (the link, the zip, diagram.json, libraries.txt, custom chips, MicroPython) is on Import a Wokwi project; this page is about what each Wokwi idea is called here.

Paste the project's link (https://wokwi.com/projects/...) into the import page, or drop Wokwi's project zip, or drop the files themselves: diagram.json, the sketch and its tabs, libraries.txt, and wokwi.toml if it has one. A Wokwi for VS Code project in the PlatformIO layout (src/, include/, platformio.ini) works too. You can also type mokxi.com/ in front of the Wokwi link in the address bar. The import report lists everything that came across and everything that did not, with the reason, and the project you had open is kept: Undo on the summary line puts it back.

A diagram.json written by hand or by an AI tool imports too. Part types can be written plainly (esp32, bluepill, ssd1306, buzzer, logicanalyser), in any case, with _ or -, and parts Wokwi does not have but Mokxi does (battery, regulator, nrf24l01, multimeter) can be named by their Mokxi type. A part neither knows becomes a note, and the rest of the project still opens.

Every part type in Wokwi's catalog comes across: as the matching Mokxi part, or, for a board or screen Mokxi does not run yet, as a drawn part that keeps its wires (and a board its code). Wokwi's D flip-flops and 2-to-1 multiplexer are Mokxi's ideal flip-flops and multiplexer, and its heart beat sensor is the Pulse Sensor. Only a custom chip (chip-*) becomes a note.

Side by side

In Wokwi In Mokxi What happens on import
diagram.json The diagram: parts, wires and notes on the canvas Each part becomes the matching Mokxi part with its pins and settings. Positions and rotations are kept.
A part's attrs The part's properties, in the panel when you click it Color, value, I2C address, pixel count, temperature and the other settings that change behavior are carried over.
connections Wires Each keeps its color. Routing hints become the wire's corners. Tidy wires routes them around the parts.
$bb (plugged into a breadboard) A pin sitting in a breadboard hole The part sits in the same holes.
wokwi-junction Wires joined at a pin Every wire that met at the junction is joined.
wokwi-text A sticky note The text is kept where it stood.
sketch.ino and tabs The board's files, in the code panel All of them, as they are.
libraries.txt Built-in libraries Every library Mokxi ships is already there and free: nothing to install. One Mokxi does not have is named in the report.
wokwi.toml Nothing needed for a sketch Mokxi builds an Arduino sketch when you press Run, so no firmware path is needed. A Pico SDK project runs the .uf2 or .elf the file points at, when the upload carries it. An SD card folder is put on the microSD card.
$serialMonitor wires The serial monitor Always connected to the board. No wires needed.
serialMonitor settings The serial panel The plotter is the Plot button. Typed lines end with a line feed, as in Wokwi.
Wokwi-GUEST Wi-Fi The board's access point setting Set to Wokwi-GUEST with no password, so your WiFi.begin connects unchanged.
wokwi-wifi-ap The board's access point setting Its name and password are copied to the board.
Logic analyzer Logic analyzer Mokxi's has four channels, so D4 to D7 go to a second one beside it. Channel names become net labels.
Custom chips (chip-*) Custom chips Each chip comes over as a part with its pins and runs its own code, when its chip.json and its code (.chip.c) or its built chip.wasm are in the import.
Keyboard shortcuts on parts (key) Click the part Press buttons and turn knobs with the mouse or a finger.

What to check after the import

  • Starting positions. A potentiometer's knob, a slide switch, the HC-SR04's distance and other parts you move by hand start at rest in Mokxi. The report says when the Wokwi project started one somewhere else. Move it on the canvas while the sketch runs.
  • Boards Mokxi draws but does not run yet. Some boards (the ESP32-S2, the ESP32-P4, the ESP-Mosaico, the STM32 Nucleo boards, the Pi Pico 2) come across with their wires and code, so you can export them for real hardware, but Run does not start them yet. Wokwi's composite video TV and its 8 inch MIPI DSI panel are drawn the same way. The full list is on Boards that are not simulated yet.
  • Libraries Mokxi does not ship. The report names them. Add one as a custom library to build the sketch.
  • MicroPython. A MicroPython project on the Raspberry Pi Pico, a classic ESP32 (the DevKit V1, the DevKitC or the LOLIN32 Lite), an ESP32-S3, an ESP32-C3 or an ESP32-C6 runs, on the official MicroPython firmware, and an ESP32's network is named Wokwi-GUEST with no password, as on Wokwi. On any other board the .py files are kept as text but do not run. See MicroPython on the ESP32.
  • CircuitPython. A CircuitPython project (a code.py) for the Raspberry Pi Pico or the Arduino Nano RP2040 Connect imports with its board set to CircuitPython and runs, on the official CircuitPython firmware. Wokwi may have used another CircuitPython version; the import report says which one runs here. On another board its code.py is kept as text. See CircuitPython on the Pico.
  • Pico SDK, ESP-IDF and Rust projects. A Pico SDK project runs its prebuilt .uf2 or .elf, and an ESP-IDF or Rust project on an ESP32 or ESP32-S3 board its .bin or .elf (see Run a prebuilt firmware): include the build/ folder in the upload, or let wokwi.toml name the file. On an ESP32-C3 or C6 an ESP-IDF build comes across as code and does not run yet.