NordicTrack RX800 Default Settings #58
Replies: 2 comments 8 replies
-
|
Congrats on getting a nice machine (used to own one myself). I can imagine the settings might need an update (last real test was over two years ago, and the engine looked different then). What version are you running, main or architecture_update? Is there a specicific reason you changed the following settings:
Especially flankLength could create a lot of noise that hinders stroke detection. |
Beta Was this translation helpful? Give feedback.
-
|
I had followed the default install and that got me the main branch. With a little thinking I managed to work out I could update to the most recent development branch using the command:
Note that there were a few errors and warnings, mostly due to dependencies. I also updated the config to the settings you list above. It is much better, but I am still getting missed strokes. What do you mean by the magnet getting stuck at the far end? |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm finding it tricky to get the config right for a new NordicTrack RX800 that I inherited from a friend (without a monitor, hence getting ORM set up with a fresh install on a brand new Pi Zero 2 W). Any tips?
I have the damper set to 6 because it feels pretty much like a drag factor on the Concept 2 I am very familiar with for a 130 drag factor on the PM5. The default settings did not seem to be right for stroke detection so I have altered it a bit. The current config works ok if I row slow, but as soon as I power up it seems to be missing strokes. I have attached the raw log, rowing data and config file. The config was copied and modified from rowerProfiles.js.
rowingData.zip
I checked to make sure I had four pulses per revolution of the flywheel. The raw data does not look noisy.
This graph shows the timings of the detected strokes (from rowingdata.csv, plotted in red at 0.04 just to show them next to the peaks) overlayed on top of the raw data. At about 35 seconds I power up a bit and the strokes are not being recognised. When I power off again slightly at 60 seconds the detection starts to work again.
Key settings are:
numOfImpulsesPerRevolution: 4,
minimumTimeBetweenImpulses: 0.015,
maximumTimeBetweenImpulses: 0.06,
sprocketRadius: 3.0,
autoAdjustDragFactor: true,
minimumDragQuality: 0.83,
dragFactorSmoothing: 3,
flywheelInertia: 0.189,
dragFactor: 460,
flankLength: 9,
minimumStrokeQuality: 0.34,
minumumRecoverySlope: 0.001,
autoAdjustRecoverySlope: true,
autoAdjustRecoverySlopeMargin: 0.036,
minumumForceBeforeStroke: 20,
minimumDriveTime: 0.28,
minimumRecoveryTime: 0.90
Beta Was this translation helpful? Give feedback.
All reactions