Arduino, running the sketch you wrote
arduino-cli compiles it, an AVR8 core executes it instruction by instruction, and the LCD shows what the ATmega328P actually put on the bus. Uno, Nano, Mega and ATtiny85, no board on your desk.

Hardware is all about iteration. Velxio lets you wire a circuit, program the board and run it in seconds, real firmware on a real solver, right in the browser.
DFRobot · M5Stack links on this page are affiliate links: a purchase through them earns Velxio a small commission at no extra cost to you.
Nothing on this page is a scripted animation: the firmware is compiled and executed, and the circuit around it is solved.
arduino-cli compiles it, an AVR8 core executes it instruction by instruction, and the LCD shows what the ATmega328P actually put on the bus. Uno, Nano, Mega and ATtiny85, no board on your desk.

arduino-cli or ESP-IDF compiles the sketch, then AVR8, RP2040, RISC-V, Xtensa or ARM executes it instruction by instruction. What the OLED draws and what the serial monitor prints is what the chip actually did.

ngspice compiled to WebAssembly runs a full nodal analysis about 60 times a second. GPIO pins drive real nets, ADC inputs read solved node voltages, and probes report RMS, DC and current wherever you drop them.

Adders, comparators, decoders, flip-flops and a 1-bit ALU slice: no microcontroller anywhere, just gates, switches and LEDs solved as a real net. The classroom half of electronics, without the breadboard.

The M5Stack Cardputer with its keyboard, Seeed's round display keeping time, Pimoroni's Badger 2350 driving e-paper, and DFRobot's UNIHIKER M10 in the catalogue alongside them. Their makers sent the hardware so the emulation could be checked against the real thing.




35 boards across 6 CPU architectures — AVR8, ARM Cortex-M, ARM Cortex-A, RISC-V, Xtensa, and Linux. Including partner boards from Pimoroni, M5Stack, Seeed Studio and DFRobot. All running locally, no cloud needed.
One institution contract gives every student in the class a full Pro account. No per-seat checkout, no card details in a classroom.
Private projects, BOM and schematic exports, GitHub Sync and the offline desktop app, for everyone enrolled.
Billed once to your institution, per semester or per year. Volume pricing on request for large cohorts.
Arduino, ESP32, RP2040, STM32, ATtiny and Raspberry Pi, with SPICE analog solved alongside the firmware. Not a sandboxed mock.
The simulator stays free forever. Paid plans unlock the Linux and STM32 boards, WiFi and the offline desktop app. Maker and Pro add the AI agent; No AI leaves it out.
Discover the simulator + light AI help.
The full workbench, zero AI. You write every line.
For makers shipping real circuits with AI help.
Private projects, GitHub Sync and BOM exports.
Questions, bugs and ideas: the Discord and the issue tracker are open, and so is every line of the simulator.
An interactive Esp32 Devkit C V4 circuit simulation you can run free in your browser on Velxio, by catchrajnishkapur.
/*
Mains / Generator Monitor — ESP32 (Arduino core)
--------------------------------------------------
Wiring assumption (pulled-up inputs):
- Mains sense pin: GPIO 19
- Generator sense pin: GPIO 18
- OFF = contact open -> pin reads HIGH (internal pull-up)
- ON = contact closed to GND -> pin reads LOW
NOTE: GPIO34-39 on ESP32 are input-only and have NO internal pull-up/down.
If you must use one of those pins, add an external 10k pull-up resistor.
Design:
1. Mains pin change -> hardware GPIO interrupt (IRAM_ATTR ISR).
ISR does the absolute minimum: timestamps the event and sets a flag.
2. loop() runs a retriggerable software debounce (default 300 ms).
Once the pin has been stable for the debounce window AND the state
actually differs from the last confirmed state, it's treated as a
real transition -> "Mains-ON" / "Mains-OFF" printed immediately.
3. Independently of Mains, a PERIODIC esp_timer fires every 2 minutes
(starting at boot, continuing forever) and samples the Generator
pin (digitalRead) regardless of what Mains is doing.
4. To avoid printing a combined line every 2 minutes even when nothing
changed, the periodic check only prints when the Generator's state
is DIFFERENT from what was last reported. When it does report, it
prints CURRENT Mains state + Generator state together.
5. esp_timer callbacks run in the esp_timer service task (not real ISR
context), so it's safe to do digitalRead()/Serial.println() there.
6. ALARM: if Mains-ON and Generator-ON hold true continuously for more
than 4 minutes, an alarm line is printed once. The 4-minute window
is tracked with a plain millis() timestamp and checked every loop()
pass (not tied to the 2-minute Generator sampling), and resets the
moment either Mains or Generator leaves the ON state.
*/
#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Werror=unused-value"
#include <WiFi.h>
#include <Arduino.h>
#include <Wire.h>
#include "esp_timer.h"
/*
* Start of the OTA Drive block
*/
#include <otadrive_esp.h>
// Product Key is used for RK's Generator On Alarm Module Product on OTADrive.com
#define OTA_PRODUCT_KEY "865c9958-976d-465e-801b-f4c33ddd12ea"
// OTA_FIRMWARE_VERSION - will need to be incremented for each update via OTADrive
#define OTA_FIRMWARE_VERSION "[email protected]"
#define OTA_CHECK_INTERVAL 250 // in seconds
uint32_t chipId = 0;
void otaUpdate();
void onUpdateProgress(int progress, int totalt);
String getChipId();
/*
* End of the OTA Drive block
*/
/*
* End of Error Display block
*/
/*
* Start of Application Specific Code
*/
/*
* Start of LCD Display Block
*/
#include <LiquidCrystal_I2C.h>
#include <Ticker.h>
#define LCD_I2C_ADDRESS 0x27
#define LCD_COLUMNS 20
#define LCD_ROWS 4
#define LCD_I2C_ADDRESS 0x27
#define LCD_BLINK_INTERVAL 1 // second
// Level 1: Weakest signal (Just the base/