Obsidian surge 500, Stroke Detection Issues #205
Replies: 2 comments 15 replies
-
|
Your settings are far from optimal. With the following I get better results: It isn't perfect yet. Please check if the magnet is connected to the impellor, not to the handle. The exploded view in the manual isn't conclusive about that. I also see a ratio of 1:0.6 (recovery is way too short), which also might indicate that not rushing the recovery might provide better data. But as I have no insight in how the stroke is composed, it is difficult to optimize. |
Beta Was this translation helpful? Give feedback.
-
Just for the sake of accuracy and for future reference, on the pictures those are not hall sensors but reed switches. Those are passive component (unlike hall). From a practical perspective this might not be too relevant but the noise handling of those differ (reed can suffer from bounce, which with so few magnets probably not going to be an issue). |
Beta Was this translation helpful? Give feedback.




Uh oh!
There was an error while loading. Please reload this page.
-
I was able to get everything working besides the stroke detection. I have an obsidian surge 500 water rower, and I was able to get quite accurate distance calculations and have tried just about everything to get the strokes to detect but nothing seems to work. At best, I can get 2 detections across 20 strokes and typically it detects none at all. I think my data is relatively clean, but I have attached the raw csv, an image of the log which shows that the recovery stroke conditions are never met, and an image of my current config settings.I have attached a single magnet to the axle of the rower, as well as repurposing one of the hall effect sensors as the original magnet was on the handle spool which moved back and forth. Any and all help is appreciated.


2026-02-25_06-54-35_raw.csv
Beta Was this translation helpful? Give feedback.
All reactions