Your hardware. Before the hardware.
Simulate devices, explore faults and test your telemetry flow in one workspace.
Optional cloud connection
Standalone. Your simulations stay in this browser.
Virtual OTA test. Uses the real deployment APIs for your selected development target. It verifies downloaded bytes and simulates reboot/health reporting; it never flashes hardware or executes a firmware binary.
No deployment checked.
Simulate real-world field connectivity conditions to verify that your firmware's edge ring buffer protects against telemetry data loss.
When network connectivity drops, telemetry packets are automatically spooled into the simulated LittleFS non-volatile ring buffer. As soon as connectivity is restored, Telematric replays the buffered queue chronologically with zero data loss.
| Index | Timestamp | Payload Preview | Reason For Enqueue |
|---|---|---|---|
| Ring buffer empty. Zero dropped packets stored. | |||
Embed your cloud-hosted Wokwi simulation directly inside this cockpit tab. Simply paste your Wokwi Project ID or full URL below to run the full simulation frame inside your browser.
Interactive in-browser code editor. Type your custom logic or constants directly, then click Run Code to update the live digital twin simulation immediately.
Loading firmware template...
Wokwi virtual wiring layout for ESP32-DevKitC V4 with fault toggle switch (GPIO 15) and status indicator LEDs.
Loading diagram.json...
Workspace telemetry & optional virtual OTA
Start standalone without credentials. To send synthetic telemetry to Telematric, enter a development API key with devices:read and telemetry:write, your workspace UUID and a registered development device UUID. Live requests consume your workspace allowance.
OTA is a separate opt-in: add firmware:read and an existing supported ESP32 target’s OTA token. Check deployments, verify downloaded bytes and simulate reboot, healthy completion, interruption or rollback. No firmware binary executes and no physical device is flashed.
Project metadata and bounded telemetry queues are saved in this browser; secrets are not. Reload and scenario imports never connect automatically. Your own backend or OTA tooling can be used independently.
Read connection & OTA guide ↗The Telematric Pre-Silicon Simulator is an embedded digital twin studio that emulates the behavior of physical IoT silicon in real time before PCB fabrication:
/v1/telemetry/reading) to trigger real alert rules.
- Zero-Hardware Verification: Test entire IoT dashboards, alert webhooks, and billing meters before spending thousands of dollars manufacturing custom hardware.
- Dynamic 2-Board Virtual Workbench: Dynamically swaps the virtual hardware workbench between the ESP32-DevKitC V4 and the authentic MXChip AZ3166 IoT DevKit (featuring a live 128x64 VGM128064 OLED screen, ST sensor cluster, user buttons, and 14 gold edge fingers) based on the active profile.
- Interactive Pin Testing & Digital Multimeter: Select a virtual pin to inspect illustrative voltage values, toggle simulated logic levels and view pulse animations with simulated serial logs. No electrical or interrupt verification is performed.
- Pre-Silicon Memory Profiler: Mathematically validates Flash partition layout (Dual A/B OTA rollback slots) and RAM heap headroom (mbedTLS handshake buffers) against actual MCU silicon specs (e.g., STM32F412RG 1MB/256KB or ESP32 4MB/320KB).
- Interactive Fault Injection Matrix: Dynamically inject I2C bus lockup (
0x43 timeout), mechanical drop/shock events, pressure surges, and Wi-Fi disconnects to test firmware panic recovery. - Live In-Browser Code Editor & Hot-Reload: Edit custom C++ firmware code directly in the browser and click Run Code to update the live simulation outcome immediately.
- Production Firmware Export: 1-click download of ready-to-compile C++ source code (
az3166_threadx_main.cppormain.cpp).
While the digital twin provides illustrative device behavior and selected telemetry contracts, physical hardware introduces real-world electrical and environmental factors that engineers must account for:
| Domain | Simulator Digital Twin | Physical Hardware Reality | Engineering Action Needed |
|---|---|---|---|
| Wi-Fi & RF Network | Auto-connected virtual network | Physical walls, 2.4GHz interference, router distance | Configure real SSID/Password in cloud_config.h; ensure 2.4GHz band is enabled. |
| Sensor Accuracy | Physics-derived mathematical curves | MEMS manufacturing tolerance (±0.5°C, ±1.5% RH) | Apply zero-point calibration offsets if laboratory precision is required. |
| Thermal Soak | Calculated ambient dissipation | MCU core & Wi-Fi chip warm the PCB enclosure | Duty-cycle sensor reads; subtract self-heating factor (~1.5°C when Wi-Fi is active). |
| Power Delivery | Continuous simulated power | Wi-Fi transmit current spikes (~250mA peak) | Ensure USB cable or power supply provides ≥500mA without dipping below 2.7V. |
A. Flashing the MXChip AZ3166 (Eclipse ThreadX):
- Connect the AZ3166 board to your Mac or PC using a micro-USB cable.
- The board automatically mounts as a virtual USB drive named
/Volumes/AZ3166(macOS) orD:\(Windows). - In your terminal, navigate to the samplex repository and compile:
./scripts/build.sh telemetry
- Deploy by copying the compiled binary to the board:
./scripts/deploy.sh /Volumes/AZ3166
- The board will reboot and immediately begin executing Eclipse ThreadX and streaming telemetry.
B. Flashing ESP32 Microcontrollers:
- Click Download .cpp in the Firmware Editor tab to download
main.cpp. - Open with Arduino IDE or PlatformIO. Install
ArduinoJsonlibrary. - Compile and upload via USB serial port (
/dev/ttyUSB0).
You can customize the firmware logic without any local compilers installed:
- Navigate to Tab 4: Wokwi & C++ Bridge.
- Click inside the Target Firmware Editor box to type or paste custom code.
- Edit device constants such as
TELEMETRY_INTERVAL_SECor adjust sensor alarm thresholds. - Click Run Code in Simulator: The studio reads supported parameters from your code text and triggers an updated simulation cycle on the waveform canvas and serial monitor!
Explore illustrative pin states in the virtual workbench. No physical pins are measured or driven:
- Attach Multimeter Probe: In Tab 4: Wokwi & C++ Bridge, click any physical pin on the ESP32 (e.g.,
GPIO 15,GPIO 2,EN) or gold edge finger on the AZ3166 (e.g.,PA4,ADC1_IN0). The Multimeter HUD connects instantly. - Measure Live Voltages (Read Volts): Click Read Volts to capture an illustrative voltage value with synthetic jitter (±8mV), logged to the simulated serial monitor. These values are not electrical measurements.
- Drive Logic Levels (Pull LOW / Pull HIGH): Click Pull LOW (GND) to drive the pin to 0.00V GND. If probing
GPIO 15, this closes the safety trip switch and triggers an immediate digital twin alarm. If probingEN, it reboots the microcontroller. Click Pull HIGH (3.3V) to inject 3.3V and restore nominal state. - Signal Generator Pulse Injection: Click Inject Pulse to strobe a 100ms logic clock pulse on the selected virtual pin. This does not execute MCU instructions or verify hardware interrupts.
The Telematric Simulator bridges the pre-silicon development lifecycle across seven primary embedded and IoT verticals:
ac_power_kw, dc_voltage_v, and inverter_temp_c. Triggers automated power curtailment webhooks and dispatch alerts during grid loss.voltage_v, current_a, battery_soc_percent, and cell_temp_c. Verifies high-voltage isolation alerts, charge-cycle billing counters, and automatic contactor lockout.depth_m, hull_status, and thruster_current_a. Triggers automated surface-and-recover failsafe commands upon water ingress detection.