adds an option to configure the ftms device names
This commit is contained in:
parent
191dc3aaec
commit
15c1553e42
|
|
@ -14,11 +14,11 @@
|
||||||
import bleno from '@abandonware/bleno'
|
import bleno from '@abandonware/bleno'
|
||||||
import FitnessMachineService from './ftms/FitnessMachineService.js'
|
import FitnessMachineService from './ftms/FitnessMachineService.js'
|
||||||
import DeviceInformationService from './ftms/DeviceInformationService.js'
|
import DeviceInformationService from './ftms/DeviceInformationService.js'
|
||||||
|
import config from '../tools/ConfigManager.js'
|
||||||
import log from 'loglevel'
|
import log from 'loglevel'
|
||||||
|
|
||||||
function createFtmsPeripheral (controlCallback, options) {
|
function createFtmsPeripheral (controlCallback, options) {
|
||||||
const peripheralName = options?.simulateIndoorBike ? 'OpenRowingBike' : 'OpenRowingMonitor'
|
const peripheralName = options?.simulateIndoorBike ? config.ftmsBikePeripheralName : config.ftmsRowerPeripheralName
|
||||||
// const peripheralName = options?.simulateIndoorBike ? 'OpenRowingBike' : 'S1 Comms 1'
|
|
||||||
const fitnessMachineService = new FitnessMachineService(options, controlPointCallback)
|
const fitnessMachineService = new FitnessMachineService(options, controlPointCallback)
|
||||||
const deviceInformationService = new DeviceInformationService()
|
const deviceInformationService = new DeviceInformationService()
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,8 +7,9 @@
|
||||||
!!! Note that changes to this file will be OVERWRITTEN when you update to a new version
|
!!! Note that changes to this file will be OVERWRITTEN when you update to a new version
|
||||||
of Open Rowing Monitor. !!!
|
of Open Rowing Monitor. !!!
|
||||||
|
|
||||||
To change the settings you should modify the 'config.js' in this folder. If 'config.js' does not
|
To change the settings you should modify the 'config.js' in this folder. Simply copy the
|
||||||
exist, you can use the example file from the 'install' folder.
|
options that you would like to change into that file. If 'config.js' does not exist, you
|
||||||
|
can use the example file from the 'install' folder.
|
||||||
*/
|
*/
|
||||||
import rowerProfiles from './rowerProfiles.js'
|
import rowerProfiles from './rowerProfiles.js'
|
||||||
|
|
||||||
|
|
@ -25,6 +26,14 @@ export default {
|
||||||
// supported modes: FTMS, FTMSBIKE, PM5
|
// supported modes: FTMS, FTMSBIKE, PM5
|
||||||
bluetoothMode: 'FTMS',
|
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',
|
||||||
|
|
||||||
// the rower specific settings. Either choose a profile from config/rowerProfiles.js or
|
// 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
|
// 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
|
// please send them to us (together with a raw recording of 10 strokes) so we can add
|
||||||
|
|
|
||||||
|
|
@ -4,7 +4,6 @@ This is the very minimalistic Backlog for further development of this project.
|
||||||
|
|
||||||
## Soon
|
## Soon
|
||||||
|
|
||||||
* add a configuration option to change the FMTS device name
|
|
||||||
* add support for ANT+ heart rate monitors with USB dongles
|
* add support for ANT+ heart rate monitors with USB dongles
|
||||||
* add an option to the installation script to directly attach a touchscreen to the Raspberry Pi and automatically show WebUI on this in kiosk mode
|
* add an option to the installation script to directly attach a touchscreen to the Raspberry Pi and automatically show WebUI on this in kiosk mode
|
||||||
* validate FTMS with more training applications and harden implementation (i.e. Holofit and Coxswain)
|
* validate FTMS with more training applications and harden implementation (i.e. Holofit and Coxswain)
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue