Topiom V2 config

[FabianEckermann]

I managed to configure ORM on a Raspberry Pi 3B for my Topiom V2 indoor water rower and want to share my config and a raw logfile as suggested in the documentation:

As a reference for the number of strokes (1200), I used my Garmin Venu 2.
I tweaked the minimumForceBeforeStroke, the dragFactor and the flywheelInertia to also match the calories estimate from my Venu 2.

topiom_profile.js
TopiomV2_1magnet.csv

Setting up the stroke detection worked flawlessly but tweaking the calories estimate was quite difficult, as from a certain point the dragFactor would interfere with the stroke detection.

[JaapvanEkris]

I managed to configure ORM on a Raspberry Pi 3B for my Topiom V2 indoor water rower and want to share my config and a raw logfile as suggested in the documentation:

Thanks, that is helpfull. I'll add it to the list of supported devices.

As a reference for the number of strokes (1200), I used my Garmin Venu 2. I tweaked the minimumForceBeforeStroke, the dragFactor and the flywheelInertia to also match the calories estimate from my Venu 2.

Calorie estemates vary wildly across brands and devices. So it isn't the best basis for getting accurate estimates for Flywheel inertia and dragfactor. Essiest way to do that is compare your pace against a Concept 2. But it will do :)

Setting up the stroke detection worked flawlessly but tweaking the calories estimate was quite difficult, as from a certain point the dragFactor would interfere with the stroke detection.

It indeed does. Thanks for reporting this. When you increase the dragfactor or flywheel inertia (which in its turn increases calculated dragfactor if you do the auto update), the reported forces for the same flywheel acceleration increase as a result. So you need to change the minimumForceBeforeStroke accordingly to get stroke detection to work properly again. I've added this to the tips in the rower settings manual of the upcomming 0.9.7 version.

[DrChaoss]

Dear Fabian, dear Jaap,

thank you both a lot for your work. I returned after not using ORM and my Topiom Rower for quite a while. I use the Topiom V1 (I assume), but I added a second magnet.
I have set up my ORM with Fabians settings (besides changing the impulse), and it seems to work in general - however, when I position the sensor close to the wheel, I get what I consider an accurate reading of the distance (about 10m per stroke, I don't have an opportunity to compare), but only few strokes are recognized. If I place the magnet in a greater distance, my strokes are recognized correctly, but then the distance is off. I read the configuration guide, but I am not sure where to start when trying different settings. Is it better to have a correct assessment of the distance or the strokes?

Thanks in advance!
Markus

[DrChaoss]

Sorry, it was of course my mistake - I overwrote the maximum force setting. I have now set minimumTimeBetweenImpulses: 0.05 and
maximumTimeBetweenImpulses: 2.0 due two my two magnets, and apparently that works now. Thank you all very much for your work, which made the setup very easy!

[JaapvanEkris]

This machine is now on the official supported list for release 0.9.7. You can replace the manualy configured profile with

  rowerSettings: rowerProfiles.Topiom_V2