Raspberry Pi 2 support

[Bcd-Wilz]

Hi,
Just starting out here, I have a Raspberry Pi 2 that I’d like to use, I know it’s not on the list of ‘supported’ devices. Wondering if anyone has the quick answer to why not? Is it just the lack of onboard bluetooth?
I’ve performed the install of the ‘main’ package and already got past a couple issues to have a ‘successful install’. Open Rowing Monitor is running, but the WebUI does not. When I look at the error given and view the .js file throwing the error, it appears to be failing on a bluetooth requirement.
Would a usb BT4.0 dongle help solve my problem? Is there a quick and easy way to disable the requirement for bluetooth, as it’s not entirely necessary for me at this point in time. Or is there any other reason why the Pi 2 might not be suitable?

love to see what you’ve all been doing here, it looks like a great upgrade for my waterower. Really hoping to be able to try this out. Thanks in advance.

[JaapvanEkris]

In part is also the CPU, but as we run on a Pi Zero 2, that should not be too limiting (especially as waterrowers tend to be lower frequency machines). If you install ORM, take the V1Beta_Updates branch, as it is greatly reduces CPU load and you can disable bluetooth.

[Abasz]

Would a usb BT4.0 dongle help solve my problem? Is there a quick and easy way to disable the requirement for bluetooth, as it’s not entirely necessary for me at this point in time. Or is there any other reason why the Pi 2 might not be suitable?

Yes you can use a BT dongle, it sholud work if setup properly. But you can try to disable bluetooth in the config, by setting bluetoothMode to "off" as well as heartRateMode to "off"

[Bcd-Wilz]

In part is also the CPU, but as we run on a Pi Zero 2, that should not be too limiting (especially as waterrowers tend to be lower frequency machines). If you install ORM, take the V1Beta_Updates branch, as it is greatly reduces CPU load and you can disable bluetooth.

Yes you can use a BT dongle, it sholud work if setup properly. But you can try to disable bluetooth in the config, by setting bluetoothMode to "off" as well as heartRateMode to "off"

Thank you for the replies. I (think) I've now installed the V1 beta updates, but still have the same problem, even after disabling the suggested bluetooth settings... Here is the error I am getting, for information I do not have the sensor connected to GPIO 17 yet. From the below, it still looks like it's failing on something to do with bluetooth connection though, but that's just a guess when I look at the .js files mentioned... Please bear in mind, I'm not a developer, just a tinkerer and don't know much about pi/linux etc.

Dec 25 19:58:03 raspberrypi systemd[1]: Started Open Rowing Monitor.
Dec 25 19:58:08 raspberrypi npm[5195]: > [email protected] start
Dec 25 19:58:08 raspberrypi npm[5195]: > node app/server.js
Dec 25 19:58:14 raspberrypi npm[5219]: ==== Open Rowing Monitor 0.8.2 ====
Dec 25 19:58:14 raspberrypi npm[5219]: bluetooth profile: FTMS Rower
Dec 25 19:58:14 raspberrypi npm[5219]: Starting a just row session, no time or distance target set
Dec 25 19:58:14 raspberrypi npm[5219]: webserver running on port 80
Dec 25 19:58:14 raspberrypi npm[5219]: Uncaught Exception: Error: ENODEV, No such device
Dec 25 19:58:14 raspberrypi npm[5219]: at Hci.init (/opt/openrowingmonitor/node_modules/@abandonware/bleno/lib/hci-socket/hci.js:110:35)
Dec 25 19:58:14 raspberrypi npm[5219]: at BlenoBindings.init (/opt/openrowingmonitor/node_modules/@abandonware/bleno/lib/hci-socket/bindings.js:97:13)
Dec 25 19:58:14 raspberrypi npm[5219]: at Bleno. (/opt/openrowingmonitor/node_modules/@abandonware/bleno/lib/bleno.js:49:22)
Dec 25 19:58:14 raspberrypi npm[5219]: at Bleno.emit (node:events:513:28)
Dec 25 19:58:14 raspberrypi npm[5219]: at _addListener (node:events:556:14)
Dec 25 19:58:14 raspberrypi npm[5219]: at Bleno.addListener (node:events:605:10)
Dec 25 19:58:14 raspberrypi npm[5219]: at createFtmsPeripheral (file:///opt/openrowingmonitor/app/peripherals/ble/FtmsPeripheral.js:26:9)
Dec 25 19:58:14 raspberrypi npm[5219]: at createBlePeripheral (file:///opt/openrowingmonitor/app/peripherals/PeripheralManager.js:125:25)
Dec 25 19:58:14 raspberrypi npm[5219]: at setupPeripherals (file:///opt/openrowingmonitor/app/peripherals/PeripheralManager.js:40:11)
Dec 25 19:58:14 raspberrypi npm[5219]: at createPeripheralManager (file:///opt/openrowingmonitor/app/peripherals/PeripheralManager.js:37:3) {
Dec 25 19:58:14 raspberrypi npm[5219]: errno: 19,
Dec 25 19:58:14 raspberrypi npm[5219]: code: 'ENODEV',
Dec 25 19:58:14 raspberrypi npm[5219]: syscall: 'bind'
Dec 25 19:58:14 raspberrypi npm[5219]: }
Dec 25 19:58:14 raspberrypi systemd[1]: openrowingmonitor.service: Main process exited, code=exited, status=1/FAILURE
Dec 25 19:58:14 raspberrypi systemd[1]: openrowingmonitor.service: Failed with result 'exit-code'.
Dec 25 19:58:14 raspberrypi systemd[1]: openrowingmonitor.service: Consumed 11.590s CPU time.
Dec 25 19:58:14 raspberrypi systemd[1]: openrowingmonitor.service: Scheduled restart job, restart counter is at 1.
Dec 25 19:58:14 raspberrypi systemd[1]: Stopped Open Rowing Monitor.
Dec 25 19:58:14 raspberrypi systemd[1]: openrowingmonitor.service: Consumed 11.590s CPU time.

[Abasz]

Dec 25 19:58:14 raspberrypi npm[5219]: bluetooth profile: FTMS Rower

You are starting Bluetooth in ftms mode, so its not off. Please post your config.js file.

[Bcd-Wilz]

Here you go, I basically copied everything over from the default.config.js file... figured it wouldn't hurt at this point in time.
Thank you for viewing.

'use strict'
/*
Open Rowing Monitor, https://github.com/laberning/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.

All available configuration parameters are visible in config/config.default.js
To modify a parameter, copy it to this file and modify the value.

Changes to this file are persisted when you update to new versions.
*/
// eslint-disable-next-line no-unused-vars
import rowerProfiles from './rowerProfiles.js'

export default {
// Available log levels: trace, debug, info, warn, error, silent
loglevel: {
// The default log level
default: 'info',
// The log level of of the rowing engine (stroke detection and physics model)
RowingEngine: 'warn'
},

// 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,

// Enable this to boost or reduce 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 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 -7 on a PREEMPT kernel seems to kill the timing of the app
// 0 keeps the systems default value.
// Also note that you will require root permissions if you set anything other than 0 here
gpioPriority: 0,

// 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: 5,

// Type of flank: what flank should be detected by the GPIO detection?
// 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, although in the presence of debounce,
// a specific flank might provide better filtering capabilities.
// Some machines are even capable of using both, but this requires a strong symmetry in the signal.
gpioTriggeredFlank: 'Up',

// Minumum pulse length in microseconds. This is the minimum pulse length (i.e. a magnet should be
// present) before Open Rowing Monitor considers it 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. Both can be detected in the raw logs easily.
// Normal value is 50 us, but for some rowers, values up to 500 us are known to work.
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: 0,

// Selects the Bluetooth Low Energy Profile that is broadcasted to external peripherals and apps. Supported modes:
// - PM5: the Concept2 PM5 emulator (not functionally complete yet)
// - FTMS: the FTMS profile for rowing machines
// - FTMSBIKE: The FTMS profile is used by Smart Bike Trainers (please note: the speed and power are still aimed for > // - 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: 'OFF',

// Selects the AN+ that is broadcasted to external peripherals and apps. Supported modes:
// - FE: ANT+ Fitness Equipment
// - OFF: Turns Bluetooth advertisement off
antplusMode: 'OFF',

// 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: 'OFF',

// 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',

// 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: 200,

// 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
peripheralUpdateInterval: 1000,

// The number of stroke phases (i.e. Drive or Recovery) used to smoothen the data displayed on your
// screens (i.e. the monitor, but also bluetooth devices, etc.) and recorded data. A nice smooth experience is found > // phases, a much more volatile (but more accurate and responsive) is found around 3. The minimum is 2,
// but for recreational rowers that might feel much too restless to be useful
numOfPhasesForAveragingScreenData: 6,

// The directory in which to store user specific content
// currently this directory holds the recorded training sessions
dataDirectory: 'data',

// Stores the training sessions as TCX files
createTcxFiles: true,

// Stores the (in-)stroke data in OpenRowingData CSV files
createRowingDataFiles: true,

// Stores the raw sensor data in CSV files
createRawDataFiles: true,

// Apply gzip compression to the recorded tcx training sessions file (tcx.gz)
// This will drastically reduce the file size of the files (only around 4% of the original file)
// Some training tools can directly work with gzipped tcx file, however for most training websites
// you will have to unzip the files before uploading
gzipTcxFiles: false,

// Apply gzip compression to the raw sensor data recording files (csv.gz)
gzipRawDataFiles: true,

// EXPERIMENTAL: Settings used for the VO2 Max calculation that is embedded in the tcx file comments
userSettings: {

// The resting Heartrate of the user, to filter abnomral HR values
restingHR: 40,

// The maximum observed heartrate during the last year. If unknown, you can use maxHr = 220 - age
// This is used for filtering abnormal HR values and to project the maximum power a rower produces
maxHR: 190,

// The minimum power a rower can produce, used for filtering abnormal power values
minPower: 50,

// The maximum power a rower can produce, used for filtering abnormal power values
maxPower: 500,

// The effect that doubling the distance has on the maximum achievable average pace. The proposed 5 is based on Pau>    // which states that doubling the distance leads to a slowdown in pace of 5 seconds. This value can be adapted if y>    // your PR (this pace) on both a 1000 meters and on 2000 meters, by substracting the pace.
distanceCorrectionFactor: 5,

// The weight of the rower in kilograms
weight: 80,

// The sex of the rower, as it is needed for Concept 2's calculation
// This can be "male" or "female"
sex: 'male',

// See for this definition: https://www.concept2.com/indoor-rowers/training/calculators/vo2max-calculator
highlyTrained: false

},

// The rower specific settings. Either choose a profile from config/rowerProfiles.js or
// define the settings individually. If you find good settings for a new rowing device
// please send them to us (together with a raw recording of 10 strokes) so we can add
// the device to the profiles.
// !! Only change this setting in the config/config.js file, and leave this on DEFAULT as that
// is the fallback for the default profile settings
rowerSettings: rowerProfiles.DEFAULT,

// command to shutdown the device via the user interface, leave empty to disable this feature
shutdownCommand: 'halt',

// Configures the connection to Strava (to directly upload workouts to Strava)
// Note that these values are not your Strava credentials
// Instead you have to create a Strava API Application as described here:
// https://developers.strava.com/docs/getting-started/#account and use the corresponding values
// When creating your Strava API application, set the "Authorization Callback Domain" to the IP address
// of your Raspberry Pi
// WARNING: if you enabled the network share via the installer script, then this config file will be
// exposed via network share on your local network. You might consider disabling (or password protect)
// the Configuration share in smb.conf
// The "Client ID" of your Strava API Application
stravaClientId: '',

// The "Client Secret" of your Strava API Application
stravaClientSecret: ''
},

// The rower specific settings. Either choose a profile from config/rowerProfiles.js (see
// https://github.com/laberning/openrowingmonitor/blob/main/docs/Supported_Rowers.md) or define
// the settings manually (see https://github.com/laberning/openrowingmonitor/blob/main/docs/rower_settings.md
// on how to do this). If you find good settings for a new rowing device please send them to us (together
// with a raw recording of at least 10 strokes) so we can add the device to the profiles.

// EXAMPLE ROWER CONFIG : using a DKN R-320 Air Rower as is
// rowerSettings: rowerProfiles.DKN_R320

// EXAMPLE ROWER CONFIG: Just set custom rower settings to make it work
// rowerSettings: {
// numOfImpulsesPerRevolution: 1,
// dragFactor: 0.03,
// flywheelInertia: 0.3
// }

// EXAMPLE ROWER CONFIG: set a rower profile, but overwrite some settings:
// rowerSettings: Object.assign(rowerProfiles.DKN_R320, {
// autoAdjustDragFactor: true
// })
}

[Abasz]

I think this settings file is incorrectly formatted (assuming that the copy pasted code is really copied correctly), hence it is not loading correctly. It would have been better if you upload it as file, or format it as code (using conventions of the markdown language) in the commet....

Try removing the below from the end including the coma after the curly brace after the stravaClientSecret: '' line!:

,

// The rower specific settings. Either choose a profile from config/rowerProfiles.js (see
// https://github.com/laberning/openrowingmonitor/blob/main/docs/Supported_Rowers.md) or define
// the settings manually (see https://github.com/laberning/openrowingmonitor/blob/main/docs/rower_settings.md
// on how to do this). If you find good settings for a new rowing device please send them to us (together
// with a raw recording of at least 10 strokes) so we can add the device to the profiles.

// EXAMPLE ROWER CONFIG : using a DKN R-320 Air Rower as is
// rowerSettings: rowerProfiles.DKN_R320

// EXAMPLE ROWER CONFIG: Just set custom rower settings to make it work
// rowerSettings: {
// numOfImpulsesPerRevolution: 1,
// dragFactor: 0.03,
// flywheelInertia: 0.3
// }

// EXAMPLE ROWER CONFIG: set a rower profile, but overwrite some settings:
// rowerSettings: Object.assign(rowerProfiles.DKN_R320, {
// autoAdjustDragFactor: true
// })
}

Besides there is basically zero reason to copy the hole default.config.js thing (as it can only result in a malformed file) as the default.config.js gets loaded as well. So anything that is not set in the normal config.js will be used from default.config.js due to the hierarchical setup. If you want to override a property you just need to add that one property...

'use strict'
/*
  Open Rowing Monitor, https://github.com/laberning/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.

  All available configuration parameters are visible in config/config.default.js
  To modify a parameter, copy it to this file and modify the value.

  Changes to this file are persisted when you update to new versions.
*/
import rowerProfiles from './rowerProfiles.js'

export default {
  heartRateMode: 'OFF',
  bluetoothMode: 'OFF',
  antplusMode: 'OFF',
}

[Bcd-Wilz]

Thank you very much @Abasz , that did it, and I appreciate the lesson along the way. The Web UI is displaying, and strokes are registering as I jumper pt 17 to gnd.

I'll be connecting to my rower and exploring further, thanks for getting me this far!

[Abasz]

Happy to hear it works! Let us know if you bump into further issues