Skip to main content
These examples show how to use the editor, exports, and ESP32 generator in different tests.

Automotive diagnostics and test bench

  • Draw a sensor signal —or import it from an oscilloscope image, photo or screenshot— and repeat it as many times as needed.
  • Send it to an ESP32 and use the Speed (RPM) control so that one full pass of the signal is one engine revolution: you sweep the range without redrawing anything.
  • Feed an ECU or a control unit on the bench with that, and see how it responds without an engine.
See Digital editing and Connect the device.

Multi-device testing

With the Pro plan and the WiFi connection, you can select different generators on the same network:
  • Test the same signal on different boards and compare how each one responds: when you connect, the signal on screen is sent automatically.
  • Test on one board, move to another, adjust the signal and return to the first to confirm the result.

Teaching and learning serial protocols

The editor reads a channel’s cells as bits and shows the interpreted frame under the drawing, field by field and with errors marked.
  • Draw a CAN frame by hand and see where the SOF, the ID, the DLC, the CRC and the ACK fall; remove a stuff bit and watch the error appear.
  • Write a UART character with the wrong parity and see the parity error flagged on the exact bit.
  • Build an I2C transfer with its START, address, R/W, ACK and STOP, and see what happens when the final NACK is missing.
  • Read a Modbus RTU, ASCII or TCP frame with the function code and the exception translated.
See Protocols.

Stimulus for firmware and hardware testing

  • Generate the exact pattern a driver, a decoder or a state machine expects, and repeat it endlessly from the ESP32.
  • Reproduce edge cases, such as an extra pulse or a transition within a substep, by editing the digital signal.
  • Keep several channels at a fixed phase relationship: clock, data and enable on the same timeline.
See Digital editing and Channels.

Documenting a signal

  • Label stretches with a name and a color (CLK, DATA, SYNC) and leave them visible.
  • Number the steps —all of them, only the high ones or only the low ones— and count them one by one or per continuous run.
  • Mark count dividers and repetition dividers so it reads where each cycle starts.
  • Export a TXT file with headers in the selected interface language.
See Numbers and labels.

Custom analog waveforms

  • Build a curve with connection points and chords: ramps, rounded peaks, vertical edges, plateaus.
  • Control how much every break is rounded with a radius of its own per corner.
  • Check that the signal closes the loop: the app warns you before exporting if the last point does not sit at the same height as the first, because every cycle would then start with an abrupt jump.
  • Export it as segments, not samples: a file of dozens of lines instead of tens of thousands.
See Analog editing and Analog format.

Reusing patterns across projects

Templates store whole channels or a stretch of pulses and are inserted folded into a single pulse, so you can keep building the signal around them without the pattern taking over the screen. Double-click unfolds them when you need to edit. See Templates.

What it does not do

  • It does not measure or capture signals: it is not an oscilloscope or a logic analyzer. Everything you see is what you drew.
  • It does not simulate circuits or components.
  • It does not read signal files from other tools such as .vcd or .sr: it does import images, photos or screenshots and TXT / CSV files.
  • It does not generate microcontroller code: the ESP32 firmware is fixed and reads what the app exports.
Your phone and your computer work together with the same account: on the phone you create signals with the generators, browse your projects, play, import and export; to draw by hand on the timeline, you continue on your computer and the signal is waiting where you left it.