Using the ThingDAQ analyzer
Everything on the capture screen, in the order you meet it: getting a board talking, the toolbar, the gestures the plot answers to, the rail down each side, and what the numbers along the bottom are counting. The same text is behind the analyzer’s ? button.
Getting connected
Three ways to get something on screen, and the question a board is asked first.
- Plug in a ThingDAQ
- Start Capturing opens the browser’s own port picker, and the capture begins the moment the port opens. Closing the picker without choosing anything is not a failure — the screen says so and waits.
- No board yet
- “Open the simulator” goes to /simulator/, where the worker’s own framed, checksummed generator stands in for a device. Below the framer the two are the same code, so everything on this page is true of it except the DEVICE panel, which has no hardware to describe. /app/ never simulates: with no board it waits on the Connect screen.
- A board with no firmware on it
- “Program a board” opens the flasher and writes the published image over WebHID; it is the same panel the /docs/ page carries. Where the browser has no WebHID the button becomes a link to /docs/, which names three desktop loaders that can do it instead.
- Eight inputs or sixteen
- A board that reports it can read the auxiliary bank is asked once, on a card over the Connect screen, before the first run starts. “Don’t ask again” keeps your answer, and the DEVICE panel changes it later.
The toolbar
The bar across the top: what the run is, and the four things you can do to it.
- Capture / Stop
- The one primary button starts and stops the run, and its label is its state rather than a light beside it. Reviewing a file, there is no run to start, so a REVIEWING badge carrying the file’s own header takes its place.
- Capture mode
- Continuous, Single shot or Repeat on trigger — what a trigger does to the run once it fires. In continuous mode nothing is watching, which is why the trigger chip beside it dims.
- Sample rate
- On the synthetic source this is the generator’s own clock, and picking one restarts it. On a device the clock is fixed and this is the recorded rate — what survives the decimator — so it is live while stopped and locked while a run is going.
- The trigger chip
- The text is the condition, as in FALL D9, and the dot is where the scan stands. Continuous mode dims the whole chip rather than pulsing at a trigger that will never stop the run.
- − + and Fit
- The two icon buttons zoom about the middle of the plot and keep the live edge pinned. Fit shows the whole capture and goes on fitting it as the head advances, until a zoom or a pan backwards releases that.
- Export
- Opens the export modal: four formats, a range, a file name and the channels, with the size it will come to. It is disabled rather than missing until there is a capture to export.
- Save session…
- Writes this run’s working file out as a .tdq you keep, which is the only thing that reopens later as this session. When nothing was logged it explains why instead, and offers to log the next run; on a review the file on screen is already saved.
- Open session…
- Opens a saved .tdq and reviews it. Offered on a live capture too, because a running capture is no reason to be unable to look at an old one.
Moving around the plot
The pointer and the keyboard both drive the window; the keys work while the plot has focus.
- Wheel
- Zooms about the pointer, exponentially, so a fast scroll and a slow one over the same distance land on the same zoom. It releases follow-live, because zooming about a place on screen means letting the live edge scroll away from it.
- Drag to pan
- Right-drag, alt-drag, or hold space and drag. The pan keeps going if the pointer leaves the plot, because the drag takes pointer capture.
- Drag to measure
- A left-drag puts cursor A where it started and cursor B under the pointer. A click that travels less than three pixels places A alone, which is how one instant is marked.
- Double-click
- Fits the whole capture, the same as the toolbar’s Fit button.
- Pan a step
- The arrow keys move the window forty pixels, or five times that with shift held. They move the window, so left goes back in time.←→
- Zoom from the keyboard
- Zooms about the middle of the plot rather than about the pointer, and keeps the live edge pinned. That is the one difference between these and the wheel.+-
- Fit
- Shows the whole capture, and goes on fitting it while the capture grows.f
- Start and stop
- Releasing space starts or stops the capture — unless it was held to pan, in which case it was a modifier and nothing is toggled.Space
- Lift the cursors
- Clears both cursors and the band between them. A measurement with no way to undo it is the reason this key exists.Escape
- t · Δ · 1/Δ
- In the status bar: where cursor A sits, how far B is from it, and one over that distance as a frequency. The renderer measures all three on the canvas, so they are what was drawn rather than what the chrome believes.
The channel rail
The left column: one row per signal on the plot, and what each is doing at the cursor.
- Reorder
- Drag a row by its grip to move it up or down the stack, or focus the grip and use the up and down arrows. The order the rail is in is the order the plot draws.
- @CURSOR
- The right-hand column is each channel’s value where cursor A sits, read out of the ring inside a frame. It updates about ten times a second whatever the capture rate is.
- Rename
- The name is editable in the inspector’s CHANNELS panel, not in the rail. Renaming D9 there renames it in the rail, in the plot’s gutter and in the trigger chip at once, because all three read one record.
- Colour
- The swatch beside each name in CHANNELS opens the palette. The rail’s chip, the trace and the export all take that colour from the same place.
- Show and hide
- The switch in CHANNELS decides whether a channel is drawn and counted at all, and a hidden one leaves this rail with it. It is not the same as STORAGE’s KEEP, which decides what is recorded and cannot be undone afterwards.
Inspector panels
The right column, six panels deep. Each folds away, and the folds are remembered.
- TRIGGER
- Source, edge, level and position, plus Force and Re-arm. The level slider is for an analog source only — a lane is high or it is low — so it dims with the reason on it when the source is digital.
- CHANNELS
- The editing half of the rail: a name, a colour and a switch per channel, in the rail’s own drag order. The METHOD select under the list is about the whole digital stream — how a window of samples becomes one recorded instant.
- ANALOG
- V/div, offset and coupling for the two traces — the only inspector controls that change what the plot looks like rather than what the chrome says about it. The V/div choices come from the converter the device described, not from an assumed 3.3 V.
- DEVICE
- What answered on the port, in its own words: firmware, build, board, MCU, serial, the converter’s geometry and both rates. Nothing here is filled in with a plausible constant, and INPUTS — eight lanes or sixteen — is the one row you can change.
- STORAGE
- How much memory the ring is given, what is kept in it, whether the run is also written to a file, where that file stops, and the interleave. “Remember this choice” decides whether logging is still on next time you load the page.
- EXPORT
- Three one-click formats and the way into the full dialog; they open the same door, and differ only in whether the format was chosen before it opened. Every control here is disabled with the reason on it while there is nothing to export.
Saving and reopening a session
What a logged run writes, how to keep it, and what you get back when you open it.
- The working file
- With “Log to file” on, every recorded item is written to a browser-managed file as well as into the ring. No file manager can see it, and the browser may clear it under storage pressure unless it agreed to keep it.
- .tdq
- “Save session…” copies that working file out to somewhere you chose, and a .tdq is the only thing that reopens later as this session. An export — CSV, VCD, BIN, PNG — is a different thing, and none of them reopens here.
- Scrolling back
- Once a logged run stops, the plot reads the file as well as the ring, so Fit reaches back past what the buffer still holds. SCROLLBACK in the status bar is what says that is happening.
- Reviewing a file
- /app/?source=file is the analyzer with no capture behind it: the same layout, gestures and export, reading a session file. Every control that would change what is being recorded goes inert, because the recording already happened.
Sixteen inputs
Eight digital lanes on D6–D13, or sixteen with the auxiliary bank.
- Which pins
- Every board reads D6–D13. A board running protocol v2 with the auxiliary bank switched to inputs reads D16–D23 as well, in the high byte of a two-byte level. The pin table on the /docs/ page lists both banks.
- When you are asked
- Once, on a card over the Connect screen, and only when a board has just reported that it could be wired either way. The first run waits for the answer, because the width decides the ring’s geometry as well as what is drawn.
- Changing it later
- The DEVICE panel’s INPUTS select, while the capture is stopped. “Ask on connect” beside it brings the card back for the next board.
Reading the status bar
Along the bottom: what the capture is collecting, and what anything is losing.
- RATE
- Bytes a second arriving from the source, averaged over the last snapshot. It is the wire’s throughput, not the sample rate the toolbar shows.
- SAMPLES
- How many instants this run has recorded, which is what the decimator produced rather than what the device sampled. BUF beside it is how full the ring is on the way to wrapping.
- DROPPED
- Items the plot will never be able to show, with the number of gaps they fall into. It stays a dim zero until something is lost and then turns amber, because a capture that quietly drops samples looks exactly like one that did not.
- FW · LINK · RING
- The legend beside DROPPED splits the count three ways: the device dropped them before it framed them, they went missing on the wire or failed a checksum, or this tab fell behind and the buffer lapped the renderer. The plot’s bands carry the same glyphs.
- DRAW
- The 95th-percentile frame time over the frames just drawn, and a count of the ones that missed the budget. It is about the display rather than the capture, so a screen that cannot keep up never gets mistaken for a device that cannot.
- FILE
- How far the log has got towards its cap, in percent and in bytes, and only while a run is writing one. It turns amber past nine tenths, because reaching the cap ends the run.
Where to go next
Everything above assumes a board that already runs the ThingDAQ firmware. Putting it there, and knowing which pin is which once it is running, is the other page.