Topiom Strokes not detected when rowing "faster"

[IzeQube]

Hi,
i'm currenty trying to use ORM with my Topiom Rower. It was fitted with a TM3 Monitor that works with a reed sensor and two magnets.

I'm basicly using the default config and everything is working nicely when i'm going with a easy SPM under 20. But if I go faster, the strokes are not detected anymore.

When I plottet my raw values in excel I seem to have nice spikes when I do 20 SPM and all my strokes where detected...

My raw values when I go faster do not have so nice spikes and only three strokes were detected at the beginning...

And don't know which parameter should be changed...

This is what was logged in the logfile:

Jun 01 20:49:16 rowingmonitor npm[563]: Rowing started at 20:49:16
Jun 01 20:49:23 rowingmonitor npm[563]: *** RECOVERY phase started at time: 6.7522 sec
Jun 01 20:49:23 rowingmonitor npm[563]: *** Stroke duration of undefined sec is considered unreliable, skipped update cycle statistics
Jun 01 20:49:24 rowingmonitor npm[563]: Time: 7.5767 sec: Delta Time trend is downwards, suggesting power, but waiting for recovery phase length (0.8244 sec) to exceed minimumRecoveryTime (0.9 sec)
Jun 01 20:49:24 rowingmonitor npm[563]: *** DRIVE phase started at time: 7.8979 sec
Jun 01 20:49:24 rowingmonitor npm[563]: *** Calculated drag factor: 17087.7751, slope: 0.07455948, not used because autoAdjustDragFactor is not true
Jun 01 20:49:24 rowingmonitor npm[563]: *** Stroke duration of 7.897850000000005 sec is considered unreliable, skipped update cycle statistics
Jun 01 20:49:24 rowingmonitor npm[563]: stroke: 1, dist: 19.8m, No heartrate detected, pace: ∞/500m, stroke dist: NaNm, strokerate: NaN SPM, drive dur: 6.75s, rec. dur: 1.15s, stroke dur: NaNs
Jun 01 20:49:26 rowingmonitor npm[563]: *** RECOVERY phase started at time: 9.5872 sec
Jun 01 20:49:27 rowingmonitor npm[563]: *** DRIVE phase started at time: 10.5739 sec
Jun 01 20:49:27 rowingmonitor npm[563]: *** Calculated drag factor: 23788.4975, slope: 0.10379690, not used because autoAdjustDragFactor is not true
Jun 01 20:49:27 rowingmonitor npm[563]: stroke: 2, dist: 26.2m, No heartrate detected, pace: 3:25/500m, stroke dist: 6.7m, strokerate: 21.8 SPM, drive dur: 4.22s, rec. dur: 1.07s, stroke dur: 2.76s
Jun 01 20:49:32 rowingmonitor npm[563]: *** RECOVERY phase started at time: 15.4932 sec
Jun 01 20:49:32 rowingmonitor npm[563]: Time: 16.0029 sec: Delta Time trend is downwards, suggesting power, but waiting for recovery phase length (0.5097 sec) to exceed minimumRecoveryTime (0.9 sec)
Jun 01 20:49:32 rowingmonitor npm[563]: Time: 16.2824 sec: Delta Time trend is downwards, suggesting power, but waiting for recovery phase length (0.7892 sec) to exceed minimumRecoveryTime (0.9 sec)
Jun 01 20:49:32 rowingmonitor npm[563]: *** DRIVE phase started at time: 16.5936 sec
Jun 01 20:49:32 rowingmonitor npm[563]: *** Calculated drag factor: 17198.2422, slope: 0.07504149, not used because autoAdjustDragFactor is not true
Jun 01 20:49:32 rowingmonitor npm[563]: *** Stroke duration of 6.019754999999975 sec is considered unreliable, skipped update cycle statistics
Jun 01 20:49:32 rowingmonitor npm[563]: stroke: 3, dist: 41.0m, No heartrate detected, pace: 3:28/500m, stroke dist: 7.1m, strokerate: 21.2 SPM, drive dur: 4.92s, rec. dur: 1.10s, stroke dur: 2.83s
Jun 01 20:49:56 rowingmonitor npm[563]: *** RECOVERY phase started at time: 39.1532 sec
Jun 01 20:49:56 rowingmonitor npm[563]: *** Stroke duration of 23.65999499999998 sec is considered unreliable, skipped update cycle statistics
Jun 01 20:49:57 rowingmonitor npm[563]: *** WARNING: currentDt of 0.5233719999999948 sec is above maximumTimeBetweenImpulses (0.5 sec)
Jun 01 20:49:57 rowingmonitor npm[563]: *** WARNING: currentDt of 0.5737060000000156 sec is above maximumTimeBetweenImpulses (0.5 sec)
Jun 01 20:49:58 rowingmonitor npm[563]: *** WARNING: currentDt of 0.6414269999999931 sec is above maximumTimeBetweenImpulses (0.5 sec)
Jun 01 20:49:59 rowingmonitor npm[563]: *** WARNING: currentDt of 0.7333969999999965 sec is above maximumTimeBetweenImpulses (0.5 sec)
Jun 01 20:49:59 rowingmonitor npm[563]: *** PAUSED rowing at time: 41.0632 sec, rower hasn't moved in 24.4696 seconds and flywheel is dwelling
Jun 01 20:49:59 rowingmonitor npm[563]: *** Calculated drag factor: 17514.0876, slope: 0.07641962, not used because autoAdjustDragFactor is not true
Jun 01 20:49:59 rowingmonitor npm[563]: *** PAUSE MOVING command recieved by RowingEngine at time: 41.0632 sec, distance: 116.76 meters
Jun 01 20:49:59 rowingmonitor npm[563]: stroke: 3, dist: 116.1m, No heartrate detected, pace: ∞/500m, stroke dist: NaNm, strokerate: NaN SPM, drive dur: NaNs, rec. dur: NaNs, stroke dur: NaNs
Jun 01 20:49:59 rowingmonitor npm[563]: Rowing stopped/paused at 20:49:59, at 40.61523 seconds,distance 116.1m
Jun 01 20:49:59 rowingmonitor npm[563]: Activating split settings for split 1
Jun 01 20:49:59 rowingmonitor npm[563]:   Workout parser, recognised justrow interval/split
Jun 01 20:49:59 rowingmonitor npm[563]: Raw data-file has been saved as data/recordings/2025/06/2025-06-01_18-49-15_raw.csv.gz

[Abasz]

I think this is a calibration issue. You need calibrate for this rower. I remember that one user had Topiom Rower: #33 (reply in thread)

You can ask for his settings to see, otherwise I recommend reading the calibration section of the docs: https://github.com/JaapvanEkris/openrowingmonitor/blob/28fa9f4962f130d6482aaed5d7a9f80d96e4bcc1/docs/rower_settings.md

[IzeQube]

I read all docs, but I am not sure what to change so that the Charts are nice and Spikey so that ORM can detect my strokes.

[JaapvanEkris]

I read all docs, but I am not sure what to change so that the Charts are nice and Spikey so that ORM can detect my strokes.

Your charts do not have to be spikey. ORM can take a lot of noise. Just follow the manual Abasz linked from top to bottom and it should work (the manual is made to adress the questions you asked here).

[IzeQube]

Yes, thank you. I got stroke detection working yesterday. The dragfactor was the problem...

I'm currently trying to calibrate the settings that distance is also correct and then I will post my config...

[Balled239]

Hi please share your config