API & MCP

Everything a person can do on Ohmforge Serial Log to Capture, a program or AI agent can do with the same inputs and get the identical result.

HTTP API

Ohmforge Serial Log to Capture

Turns a saved serial monitor log into a waveform capture and measures it like an oscilloscope recording. Lines with numbers ("512", "1.5 2.0", "temp:21.5 hum:40") become channels, text lines are skipped. Time comes from the log's time stamps (Arduino IDE, Ohmforge Serial monitor, Tera Term style), from a time column the device prints (millis()) or from a fixed sample rate. You get Vpp, mean, RMS, frequency, duty cycle and rise time per channel, a chart and a CSV that opens in the Capture analyzer.

Inputs of Ohmforge Serial Log to Capture
FieldTypeDefaultDescription
filefile—Log file. A text log saved by a serial monitor; up to 10 MB and 200 000 lines. Processed in memory and not kept.
logtextarea—Or paste the log. Used when no file is uploaded.
timeBaseselect (auto, received, column, rate)"auto"Time base
sampleRatenumber—Sample rate (lines per second, for a fixed sample rate)
columnUnitselect (ms, us, s)"ms"Unit of the device time column
seriestext—Series to use (optional). Comma-separated names ("Value 1" for unlabelled numbers); empty = the first four.
unittext—Unit of the values (optional). Shown with the measurements, e.g. V, A or °C; empty = plain numbers.
hysteresisnumber10Crossing hysteresis. Noise smaller than this band does not count as a crossing.

Every result contains

inputs (normalised, defaults applied), summary, result (validated against the published schema), units, assumptions, sources, warnings, computedAt and links.

MCP (Model Context Protocol)

{
  "mcpServers": {
    "ohmforge-serial-log-to-capture": { "type": "http", "url": "https://ohmforgeseriallogtocapture.usefulweb.site/mcp" }
  }
}