RIG SIGNAL · OPTIONAL DEVICE / ELECTRONICS SIDECAR
That number on the screen came from somewhere.
Rig Signal is not a required step in the Water → Species → Presentation chain. Open it when a sonar, sensor, logger or product claim is the question you actually need answered. Pick the device, separate what it measured from what was inferred, check calibration and uncertainty, then return only the supported claim to the active trip.
BEFORE YOU TRUST THE NUMBER
What it walks you through.
Which device?
Maker and type off the catalog, plus how mature the product is. A first-season gadget and a hand-held thermometer aren’t making the same kind of claim.
What was measured?
Split the thing a sensor actually touched from everything calculated, classified or inferred afterward. Most of the impressive part usually lives downstream of the measurement.
Was it checked?
Calibration method, setup, reference conditions, model identity. A small difference only means something if the device was ever checked against something.
How old is it?
A reading can be dead accurate and completely useless. The water moved, the weather moved, and so did the state the device was in when it recorded.
What could fool it?
Interference, placement, motion, software assumptions, missing context, ordinary error. Those go next to the result, not in a footnote nobody opens.
Where, roughly
You pick a named public station — label only, no coordinates. If the useful part of the event survives without the spot, the spot stays out of it.
Half of this thing is the catalog and the retention check.
18 makers, 49 devices
Smart rods, sonar, bite indicators, environmental loggers — and a manual baseline, for the days when the honest tool is a thermometer and a notebook.
Retention
What the device keeps, how long it keeps it, and who else gets to see it. That’s part of whether a reading is usable, not a separate privacy chore bolted on at the end.
No evidence, no label
You attach the real source — spec sheet, manual, privacy policy, depth check — or the claim comes back unsupported and stays unsupported. Gaps don’t get filled in.
Supported still isn’t predictive.
A reading that survives all of that can inform the active trip. It can’t tell you where fish are, when they’ll eat, or that one afternoon’s event is a pattern. Sonar that’s honest about its own cone angle is still just sonar.
Return the supported claim to Field Ops
Keep the measurement small: what the device actually supported, the conditions attached to it, and the uncertainty that remains. Field Ops owns the trip; Rig Signal does not become a second trip record.
If the tackle system is the problem
A clean measurement can’t repair a rod, line, leader or terminal system that doesn’t fit the presentation job. That question belongs to Tackle Link.
Check the evidence
Source, freshness, uncertainty, corrections. Same standard a written piece has to clear.
Named station, never a pin.
Rig Signal doesn’t ask for exact fishing coordinates or private-access details. The station list is public labels, and nothing you enter leaves the browser unless you print it or export it yourself.
Most claims fail on the boring part.
Not the sensor. The paperwork behind it — no calibration, no model number, no idea how old the reading is. When a device can’t back its own claim, keep the observation small and go fish.