Draw two separate routes
The first route runs from a sensor to the recording device. The second runs from that device to an app, cloud service or coach. A heart-rate strap can record successfully on a head unit while the phone upload fails later. Equally, an activity can upload perfectly while containing no power data because the intended meter was never connected. Keeping these routes separate prevents troubleshooting the internet when the actual problem is at the bicycle.
List each channel and its intended source: power from a pedal meter, cadence from that same meter, speed from a hub sensor, position from GNSS and heart rate from a chest strap. More equipment does not always create better data. Two cadence sources can make source selection harder to verify. Garmin Edge, Wahoo ELEMNT and Hammerhead Karoo devices have model-specific sensor menus; inspect the active source rather than assuming a familiar device name means the right unit is connected.
Protocols are not complete specifications
ANT+ supports device profiles that describe particular data types, including cycling power and heart rate. Bluetooth Low Energy also uses defined services and characteristics, with product-specific support layered on top. A Bluetooth logo does not guarantee that every cycling metric, control function or additional sensor channel is available. Likewise, support for basic power does not prove support for all advanced pedalling fields.
Many ANT+ sensors can broadcast to several receivers, while simultaneous Bluetooth connections depend on the exact sensor and its firmware. A phone app or indoor training application may occupy a connection that you intended to use elsewhere. Close unnecessary applications during diagnosis and consult the device’s connection limits. Do not assume every current model behaves like an older unit from the same brand.
| Link | What to verify | What success does not prove |
|---|---|---|
| Power meter → head unit | Sensor ID, supported power profile, selected source | Correct installation or accurate watts |
| Strap → phone or head unit | Protocol, connection limits, contact quality | Absence of motion artefacts |
| Trainer → training app | Power source and control connection separately | That the app uses the intended power source |
| Head unit → cloud service | Account, permissions, upload and activity visibility | Complete original sensor data |
Pair by identity, then verify behaviour
Wake the intended sensor and note its identifier. Where possible, pair away from a crowded workshop, group ride or race start. Rename the stored sensor entry clearly, but retain its ID in your equipment notes. An automatic search can discover nearby equipment; a plausible live watt value is not enough to establish ownership. Confirm that the value changes when you turn your own cranks and stops when your own sensor stops transmitting.
Next, ride with a small set of useful display fields. Include power, cadence, heart rate and elapsed time where relevant. Check that recording actually starts and that auto-pause behaves appropriately for the test. The display may apply smoothing that is not identical to file recording. After saving, inspect an exported activity rather than relying on a screenshot of the ride summary.
Diagnose gaps in a controlled order
Start with battery condition and sensor wake-up. Check strap contact, battery covers, charging state and physical damage. Then inspect connection contention, receiver placement and the active sensor ID. If the sensor supports both ANT+ and Bluetooth, testing the alternative route may help isolate a problem, but change only one variable at a time. Record the outcome, including whether gaps affect one channel or several simultaneously.
A complete head-unit restart can appear to solve a fault without explaining it. Keep the original file and note when the dropouts occurred. Gaps during rough roads, wet conditions or particular riding positions may suggest different causes from gaps that appear only when a training app opens. Radio interference is possible, but it should not become the default explanation for every missing sample.
Terminology note: connection is not synchronisation
Wireless connection delivers data between devices. File synchronisation transfers an activity to another location. Timestamp alignment is a third issue. Use the precise term when describing a failure to support staff.
Check the handover to analysis
A FIT activity can carry detailed records and device information, while GPX and TCX exports vary in which fields they preserve. Format names alone are not a promise that every channel will survive a particular export. Garmin’s FIT documentation is useful when investigating the structure, but the practical test is simple: export from the actual recording workflow and inspect the channels in the destination tool.
Platforms such as Strava, TrainingPeaks, Intervals.icu and GoldenCheetah may process, summarise or display the same activity differently. Keep an original file before cropping, merging or converting it. Confirm time zones, lap boundaries and privacy settings before sharing. Once the sensor-to-file route is stable, analysis becomes a conversation about the ride rather than an investigation into which device supplied the numbers.