PM5 verification
Some workout results carry a PM5 verified chip. It marks a piece whose data came with proof, not just a value.
What it means
Every time the PM5 finishes and logs a workout, it computes an 8-byte hash of that result — the Logged Workout Hash. Ergon captures it automatically off the monitor at the end of the piece; there's nothing to turn on or submit yourself. That hash is one of Concept2's own accepted methods for verifying a Logbook result: when a piece is submitted with its hash, the Logbook checks it against the date, time, distance, workout type, and machine type, and marks the piece verified if they match. It's the monitor vouching for its own data, not Ergon asserting anything on its behalf.
Why some pieces don't have it — and why that's normal
No hash, no chip. That's expected, not a red flag, for:
- Results synced from Concept2 rather than captured on a PM5 paired to Ergon.
- Open-ended JustRow pieces — a workout with no fixed end never gets logged the way the hash requires.
- Older captures, from before Ergon started reading the hash off the monitor.
An unverified piece is exactly as real as a verified one. The chip is a statement about provenance — the PM5 hash exists — not about whether the row happened or how hard it was.
What it doesn't claim
A verified chip is not a record submission. Concept2's official lightweight-record process requires a certified weigh-in — a number an app can't produce. Body weight entered in Ergon (Settings → Weight) is self-reported, not a weigh-in, and no chip, badge, or label in the app claims otherwise. Verification confirms the piece's data matches what the PM5 logged; it says nothing about whether that piece is eligible for a Concept2 lightweight record.
Write to support@ergon.training. A human reads every message, usually within one business day.