State the conditions you fish, then see whether the claim was ever tested in anything like them. Where a spec sheet does not say what it was tested in, this says so rather than filling the gap in for it. Not a buying guide, and not a step in the trip.
What the claim leaves out
Naming more conditions makes the check narrower, not more certain. Conditions never become bite scores, hotspots or catch guarantees, and nothing here tells you what to buy. Local-only by default.
The claim is written in a showroom. The transducer is asked to keep it at four in the morning, in chop, on a cold battery.
01Device & claim
What is it, and what do they say it does?
Catalog 49 devices across 18 maker groups, each with cost of ownership and technique fit. Condition envelopes densify field tests without ever becoming bite scores.
Start here · what are you trying to do?
Your job shapes priorities, checklists, and which findings rise first. Nothing is required — but a job makes the check smarter.
01bThe conditions you fish · optional
Enter what you are actually fishing under.
Conditions densify field tests and risk notes. They never become bite scores, hotspots or catch forecasts. Named public stations only; no coordinates.
Timing context only.
Timing context only.
Label only — no GPS.
Solunar claim card · optional
Paste a third-party rating. It is calendar math — not a field measurement. Rig Signal records it and will not score it.
As written by the other app — we do not score it
01cThe unit and the sentence
Name the device, then paste what they claim.
The manual baseline. Every device on the water is arguing with this notebook.
49 devices on record. Loading one seeds every field below — then you correct it.
What the maker says it does — paste it, or paraphrase it honestly.
▸Sensors, units, retention — the parts that decide whether a number means anything0 selected
Comma-separated, for anything not listed above.
02Evidence records
What source did you actually examine?
Each record stays on this device. Recording a source does not independently verify it — it only means you looked.
No evidence yet. Nothing will be treated as proven.
—Privacy & export reminders
Unclear is an answer, and the answer is no.
Ten questions that decide whether a claim can be treated as documented at all. If you cannot answer them, Rig Signal will not either.
01Account required for basic use?
02Cloud sync default on or off?
03Location / GNSS default on or off?
04Can location be disabled while core measurement still works?
05Export without account or paywall?
06Account deletion and data download documented?
07Photo / video upload for AI features?
08Third-party analytics or ads SDKs?
09Firmware telemetry disclosed?
10Map history retention known?
Export formats often claimed
CSV — Opens anywhere. The strongest export you can be offered.
GPX — Waypoints and tracks. Check whether depth or temperature survives.
JSON — Usually complete, occasionally undocumented. Ask for a schema.
Maker card format — Opens in the maker app. Not an export until something else reads it.
PDF report — A picture of your data, not your data.
Screenshot — Not an export. Treat it as a note.
Paper notes — The baseline. Nothing to revoke and no battery to run out.
Micro-guides
▸Marketing vs measurement
A measurement names a physical quantity, units, method, and limits. Marketing names benefits — catch more, never miss, perfect. Only measurement belongs in evidence supports.
▸Why privacy stays on this device unless evidence says otherwise
If account, cloud, location or retention is unclear, Rig Signal will not treat the claim as documented-usable. Convenience features never override privacy uncertainty.
▸Icons are not species ID
Fish icons and Fish ID modes simplify acoustic or model outputs. They are interpretation layers unless an independent method establishes species performance — and even then, not legal ID.
▸Completeness is not a product score
0–100 evidence completeness measures documentation coverage you entered. It is not battery life, not accuracy, and not how much you will enjoy the device.
▸Manual baseline first
Write what a human and a simple instrument would record before trusting automation. If the device cannot beat or match that baseline under stated limits, it is noise.
▸High-risk language burden
Bite detection, species ID, fight class, catch prediction, absolute guarantees and AI inference require independent evidence that specifically supports those words — or a rewrite.
▸365-day stale window
Firmware, apps and privacy policies change. Sources older than a year force a stale state until you re-open them and update the information-check date.
▸Color bands are intensity
On an ice flasher or digital ice sonar, color / TrueColor is return strength at a depth, not a species. Maker Target ID and target separation are echo-size thresholds. Cone angle, gain, interference rejection, hole diameter, and battery voltage decide what you see. Camera video is observation only. Vision live sonar and MarCum Ultra Live 360 are different instruments.
▸Integration needs export
Ready integration requires documented-usable state plus a real export you can open outside the maker app. Everything else is manual bridge or not ready.
—Teaching claims
Try these sample claims.
Use any set as a first-run walkthrough. These are teaching claims only — not validated device events, and not fishing advice.
Documented — usable with known limits
Manual water temperature
Handheld thermometer
Maker says accurate to ±0.5°F after recent calibration — under stated conditions.
Bounded manufacturer documentation, local privacy, commercial maturity. Still one time, one reading — run the field checklist under your water temp band.
·Compare against a second thermometer in the same water
·Record calibration date on the Validation Note
·Do not treat a single reading as a day-long temperature map
The claim is not backed up — privacy needs a look first
Live sonar species + catch overclaim
Live / forward-facing sonar (family)
Marketing claims live sonar lets you see every fish, ID species, and never miss — ladder rewrite required.
Species and catch language has no independent support, and the account requirement fails closed before that. Live acoustic imaging stays an interpretation layer until someone publishes a test.
·Rewrite claim to acoustic return / structure / motion only
·Run trolling-motor EMI and dual-transmit interference checks
·Document mount stability at idle vs speed
Privacy or data-leaving risk — limited use
Chart subscription lock-in
Networked chartplotter / sonar family
Charts and advanced mapping features require a recurring subscription — confirm what freezes when it lapses.
Fails closed until account and subscription defaults are mapped. Cost of ownership has to price the stack, not the glass.
·List features that freeze when the chart sub lapses
·Confirm offline use of already-downloaded charts
·Price transducer + module + sub over three years
Information is out of date
Stale documentation check
Older console family
Information check date is more than a year old.
Refresh sources and the information-check date before trusting the claim.
·Re-open every source URL
·Update information-check date
·Confirm firmware and privacy defaults still match
Documented — stays on this device
Vexilar ice flasher — bounded
FL / FLX-series flasher (family)
Depth and return intensity as color bands. Color is signal strength, not species.
Bounded manufacturer language, clear local privacy, offline core. Still one hole, one pack — run the ice-flasher checklist under cold soak. Inclusion is not validation.
·[5 min] Known hole-depth: drop a marked line or compare a second hole at the same depth. Pass: the bottom mark matches the line, or document the miss.
·[5 min] Gain step: raise and lower gain one click at a time; write what appears and disappears. Pass: a note, not a species name.
·[5 min] Nearby-flasher IR: if another unit is transmitting, step interference rejection and note new rings or lost bottom.
The claim is not backed up
Ice flasher species overclaim
FL / FLX-series flasher (family)
Marketing reads the red band as a walleye and Target ID as species — rewrite required.
Color bands are intensity. Maker Target ID is an echo-size threshold. Privacy can stay local-only and the claim still fails as species language.
·Rewrite to intensity vs depth only
·Known hole-depth against a marked line
·Do not load Vision X10 live-sonar claims onto a flasher card
Documented — stays on this device
MarCum ice sonar — bounded
LX-series digital ice sonar (family)
Depth and return intensity on a digital ice display. Color is signal strength, not species. Camera is observation.
Bounded manufacturer language, clear local privacy, offline core. Camera combos stay observation. Still one hole, one pack — run the ice-flasher checklist under cold soak. Inclusion is not validation.
·[5 min] Known hole-depth: drop a marked line or compare a second hole at the same depth. Pass: the bottom mark matches the line, or document the miss.
·[5 min] Gain step: raise and lower gain one click at a time; write what appears and disappears. Pass: a note, not a species name.
·[5 min] Nearby-flasher IR: if another unit is transmitting, step interference rejection and note new rings or lost bottom.
The claim is not backed up
MarCum TrueColor species overclaim
M-series TrueColor flasher (family)
Marketing reads TrueColor as a walleye and target separation as species — rewrite required.
TrueColor is intensity. Maker target separation is an echo-size threshold. Privacy can stay local-only and the claim still fails as species language.
·Rewrite to intensity vs depth only
·Known hole-depth against a marked line
·Do not load Ultra Live 360 imaging claims onto a flasher card
Readout · nothing assumed without evidence
Nothing appears here until you run a check.
Declare what you know, record what you actually read, and the instrument will tell you what it can support — and leave the rest unproven.