ESP8266 NodeMCU simulator, with the WiFi simulated and said to be
Mokxi models the NodeMCU V1.0: an ESP-12E with its Xtensa LX106 at 80 MHz, the GPIO block, IO_MUX, the RTC pin that is D0, UART0 and the TOUT converter. The radio is not modeled (WiFi here is simulated, the Arduino API over a network of ours), and neither is a PWM peripheral, because the chip has none.
- 9peripheral areas modeled
- 5projects ready to run
- Real timeon your own machine
What is modeled
Taken from the board's own contract document and put in plain words, with what is missing listed underneath.
Not in the model
- A radio of any kind. No 802.11, no PHY, no channel, no WPA2. WiFi here is simulated (WiFi.h, HTTPClient.h and WebServer.h over a network written in software, with no real internet behind it), and on this chip, whose whole reason to exist is the radio, that is said first rather than last.
- Flash and the cache that maps it, so no PROGMEM read from flash, no SPIFFS, no LittleFS and no OTA.
- FRC1 and FRC2, the two hardware timers, and both watchdogs. Deep sleep and the RTC. SPI, I2S and the hardware UART1.
- The ADC’s registers are this model’s own. Espressif has never published the ESP8266’s SAR interface (system_adc_read() lives inside the SDK blob), so rather than invent an address and let a reader assume it is the chip’s, the contract says plainly that analogRead is the one call here that would need changing for real hardware.
Open one and press Run
Each of these opens in the editor exactly as it is drawn here.
Every built-in project on the ESP8266 NodeMCU V1.0
Each has its own page with the circuit running, the code and a parts list.
Questions
Is it free?
Yes. Every board and every part is on the free plan, with no account needed.
Does it do WiFi?
Simulated WiFi, yes, and it is worth being blunt about which half is which. Your sketch uses the real Arduino calls (WiFi.begin, WiFi.status, HTTPClient, WebServer), and the board joins a network, fetches a page and serves one. Underneath there is no radio, no 802.11 and no real internet: four made-up addresses under .mokxi exist and nothing a sketch does leaves this tab.
Why is digitalWrite(2, HIGH) the wrong pin?
Because D0 to D8 are not GPIO numbers. D4 is GPIO 2, D2 is GPIO 4 and D3 is GPIO 0. The runtime defines D0 to D8, so you can write the name on the silkscreen and mean the pin you are looking at.
Why does my LED light when I write LOW?
Because both on-board LEDs are wired from 3V3 to the pin, so LOW lights them. That is the real board, and it is the mistake this one is best at provoking.
Why is analogWrite(pin, 255) dim?
Because the range here is 0 to 1023, which is what the Arduino ESP8266 core does, so 255 is a quarter. analogWriteRange(255) makes an Uno sketch behave.
Can I compile my own sketch for it?
Yes. Edit the sketch and press Run: it compiles in the tab with clang for Xtensa, and the build panel shows every step. Nothing is uploaded.
Will my firmware run on a real NodeMCU?
Everything but analogRead, which talks to registers this model invented because the chip’s are not public. Section 6 of the contract sorts every other address into as-real-as-this-part-gets and believed.
The other boards
Every one of these runs today, and every one is free.
Looking for the shorter introduction? See the ESP8266 simulator page.
Try it on your own firmware
What you build here runs on the board on your desk, unchanged. Nothing to install and no account needed.