Concept2 ModelD PM3 measurements incorrect #84
Replies: 1 comment 14 replies
-
|
Yeah, those long powerful strokes wil earn Olympic medals :) Are you sure it is set to Model_D? In the settings a small typo (comma too much or too few) results in the file being rejected, which typically leads to this behaviour. |
Beta Was this translation helpful? Give feedback.
-
|
My config: 'use strict'
/*
Open Rowing Monitor, https://github.com/JaapvanEkris/openrowingmonitor
You can modify this file to configure Open Rowing Monitor to your needs.
This file should be placed in the 'config' folder of Open Rowing Monitor.
*/
// eslint-disable-next-line no-unused-vars
import rowerProfiles from './rowerProfiles.js'
export default {
// example: change the default log level:
// Available log levels: trace, debug, info, warn, error, silent
loglevel: {
default: 'debug',
RowingEngine: 'debug'
},
// Defines the GPIO Pin that is used to read the sensor data from the rowing machine
// see: https://www.raspberrypi.org/documentation/usage/gpio for the pin layout of the device
// If you want to use the internal pull-up resistor of the Raspberry Pi you should
// also configure the pin for that in /boot/config.txt, i.e. 'gpio=17=pu,ip'
// see: https://www.raspberrypi.org/documentation/configuration/config-txt/gpio.md
gpioPin: 17,
// Increase the Nice level to boost the system level priority of the thread that
// measures the rotation speed of the flywheel. This might improve the precision of the
// measurements (especially on rowers with a fast spinning flywheel)
// This is the NICE level: a minimum setting is 0, maximum setting is -19
// Setting this below -1 on a non-PREEMPT kernel might cause the app to crash
// Going beyond -7 on a PREEMPT kernel seems to kill the timing of the app
gpioPriority: -7,
// gpio polling interval: this is the interval at which the GPIO is inspected for state
// changes on the gpioPin, in microseconds (us).
// Valid values are 1 (i.e. 1,000,000 samples per second), 2 (i.e. 500,000 per second),
// 4 (i.e. 250,000 per second), 5 (i.e. 200,000 per second) and 10 (i.e. 100,000 per second).
// A high sample rate will burden your CPU more. Normal value is 5us.
// A raspberry pi 4 can handle a polling interval of 1 us, which results in a 16% CPU load.
gpioPollingInterval: 1,
// gpio flank: what flank should be detected?
// Valid values are 'Up' for the upward flank, 'Down' for the downward flank, 'Both' for both flanks
// In practice, it shouldn't matter much which flank you detect, and some machines are even capable of using both.
gpioTriggeredFlank: 'Up',
// gpio minimum pulse length in microseconds. This is the minimum pulse length (i.e. a magnet should be
// present) before Open Rowing Monitor considers a signal valid. Increasing this value reduces ghost readings due
// to bouncing reed switches etc., which typically are detected as very short measurements in the raw logs.
// Making this too long results in missed impulses.
// Normal value is 50 us
gpioMinimumPulseLength: 50,
// Enable this to boost or reduce the system level priority of the thread that processes the flywheel and HR data
// Although this process is not time critical per se, it could get caught up in Linux housekeeping tasks, preventing
// it to process data in a timely manner.
// This is the Linux NICE level: minimum setting is +19, theoretical maximum setting is -20
// Setting this below -1 on a non-PREEMPT kernel might cause the app to crash
// Going beyond -5 on a PREEMPT kernel seems to kill the timing of the app
// 0 keeps the systems default value.
// Please make sure the app has a less high priority than gpioPriority
// Also note that you will require root permissions if you set anything other than 0 here
appPriority: -1,
// The interval for updating all web clients (i.e. the monitor) in miliseconds
// Advised is to update at least once per second (1000 ms), to make sure the timer moves nice and smoothly.
// Around 100 ms results in a very smooth update experience for distance as well
// Please note that a smaller value will use more network and cpu ressources
webUpdateInterval: 250,
// Interval between updates of the bluetooth devices (miliseconds)
// Advised is to update at least once per second, as consumers expect this interval
// Some apps, like EXR like a more frequent interval of 200 ms to better sync the stroke
ftmsUpdateInterval: 1000,
// Interval between updates of the clients using PM5 Bluetooth profile (miliseconds)
pm5UpdateInterval: 1000,
// The number of rowing phases (i.e. either a stroke or recovery) that are considered when averaging metrics.
// Higher values create more stable metrics but make them less responsive to rower actions
numOfPhasesForAveragingScreenData: 4,
// set the default BT profile to the PM5 simulation
// - FTMSBIKE: The FTMS profile is used by Smart Bike Trainers (please note: the speed and power are still aimed for rowing, NOT for a bike!)
// - CPS: The BLE Cycling Power Profile simulates a bike for more modern Garmin watches
// - CSC: The BLE Cycling Speed and Cadence Profile simulates a bike for older Garmin watches
// - OFF: Turns Bluetooth advertisement off
bluetoothMode: 'FTMS',
// Defines the name that is used to announce the FTMS Rower via Bluetooth Low Energy (BLE)
// Some rowing training applications expect that the rowing device is announced with a certain name
ftmsRowerPeripheralName: 'OpenRowingMonitor',
// Defines the name that is used to announce the FTMS Bike via Bluetooth Low Energy (BLE)
// Most bike training applications are fine with any device name
ftmsBikePeripheralName: 'OpenRowingBike',
// Selects the AN+ that is broadcasted to external peripherals and apps. Supported modes:
// - FE: ANT+ Fitness Equipment
// - OFF: Turns Bluetooth advertisement off
antPlusMode: 'FE',
// turn this on if you want support for ANT+ heart rate monitors
// Selects the heart rate monitor mode. Supported modes:
// - BLE: Use Bluetooth Low Energy to connect Heart Rate Monitor (Will currently connect to the first device found)
// - ANT: Use Ant+ to connect Heart Rate Monitor
// - OFF: turns of Heart Rate Monitor discovery
heartRateMode: 'ANT',
// The directory in which to store user specific content
// currently this directory holds the recorded training sessions
dataDirectory: '/opt/openrowingmonitor',
// Stores the raw sensor data in CSV files
createRawDataFiles: true,
// Apply gzip compression to the raw sensor data recording files (csv.gz)
gzipRawDataFiles: false,
// Stores the training sessions as TCX files
createTcxFiles: true,
// Apply gzip compression to the recorded tcx training sessions file (tcx.gz)
gzipTcxFiles: false,
// Stores the training sessions as FIT files
createFitFiles: true,
// Apply gzip compression to the recorded tcx training sessions file (tcx.gz)
gzipFitFiles: false,
// Stores the (in-)stroke data in OpenRowingData CSV files
createRowingDataFiles: true,
userSettings: {
restingHR: 40,
maxHR: 200,
minPower: 90,
maxPower: 300,
distanceCorrectionFactor: 5,
weight: 80,
sex: 'male',
highlyTrained: false
},
// Custom rower settings
rowerSettings: {
numOfImpulsesPerRevolution: 6,
sprocketRadius: 1.4,
maximumStrokeTimeBeforePause: 6.0,
dragFactor: 68,
autoAdjustDragFactor: true,
minimumDragQuality: 0.60,
dragFactorSmoothing: 3,
minimumTimeBetweenImpulses: 0.005,
maximumTimeBetweenImpulses: 0.01375,
flankLength: 12,
smoothing: 1,
minimumStrokeQuality: 0.34,
minimumForceBeforeStroke: 11,
minimumRecoverySlope: 0.00070,
autoAdjustRecoverySlope: true,
autoAdjustRecoverySlopeMargin: 0.01,
minimumDriveTime: 0.60,
minimumRecoveryTime: 0.90,
flywheelInertia: 0.101255,
magicConstant: 2.8
}
} |
Beta Was this translation helpful? Give feedback.
-
|
Okay, I updated the loglevel in the default.config.js to debug. Shows the extreme speed with which I can row. Been eating my spinach. -- Boot b207532b62d746fbbca37df8adcdeccf -- |
Beta Was this translation helpful? Give feedback.
-
|
Weird, your drive duration is way too long to be normal. Could you activate the raw recording and upload a raw file of 20 strokes of rowing? |
Beta Was this translation helpful? Give feedback.
-
|
I figured it out. When I edited the default config to use "rowerSettings: rowerProfiles.Concept2_RowErg," profile, it all started working as expected. Have you seen this behaviour before? It looks like you have your rowerSettings in config.js and don't reference the other files. I haven't had the chance to test if using the above reference in config.js would work. I might be able to test this week. Then, I should be able to help by updating the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting. Thanks for reporting this back and I'll dive into it to see where it goes wrong. For version 0.9.6 I'm already looking at the installation manual and the config settings, and these small errors lead to big frustrations. I indeed have a full config local. I am still perfecting the RowErg config as it is the golden standard we test against, and the best way to have a good configuration management over all setting is to have everything in one file. Thanks again for the pointer, hopefully I can prevent this kind of frustration for next users. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Greatly appreciate your work on this. This project has great potential. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
This is a fantastic project. I have a Concept2 Model D with a PM3. Wanting to get it more robust, ORM is a great system.
I have it all connected with a RPI3b with the extra info from https://github.com/JaapvanEkris/openrowingmonitor/blob/main/docs/hardware_setup_Concept2_RowErg.md. However, the numbers are really far off.
As impressive as it would be for me to row 684m in 3 strokes, I am feeling a little doubtful.
What settings do I need to adjust?
Beta Was this translation helpful? Give feedback.
All reactions