implementing two reed sensors

[ThreeSpaceTab]

My rowing machine (Xterra ERG650W Water) has two reed sensors and 2 magnets. I am not sure where to begin for what settings to adjust to add the second sensor in, or if I even need to?

[JaapvanEkris]

Where is the second sensor located? To ask more precisely: is it connected to the rotating thingy in the watertank or more by the handle?

[ThreeSpaceTab]

I am back to looking at this. I am going to try the code modification you suggested. I appreciate you looking at the service manual for my rowing machine. So if I were to also provide a direction within GpioTimerService.js, would I just add a new function to watch the second Gpio?
const sensorB = new Gpio(config.gpioPinB, 'in','rising')
Replicate the sensor.watch with sensorB.watch,
Then add a new function that calculates which time is smaller between hrDelta[0] and hrDeltaB[0]? I have written that, but am not sure how to send the result or where to send it to. Does process.send accept this if I were to add process.send(CCW or CW)? I have tried looking for where process.send would go but have not found it.

[JaapvanEkris]

So if I were to also provide a direction within GpioTimerService.js, would I just add a new function to watch the second Gpio? const sensorB = new Gpio(config.gpioPinB, 'in','rising') Replicate the sensor.watch with sensorB.watch, Then add a new function that calculates which time is smaller between hrDelta[0] and hrDeltaB[0]?

I think it should work like that indeed. So if Sensor B fires before A, it will probably move in one direction, and if A fires before B, it will move the other way around. But I haven't looked at all edge cases here.

I have written that, but am not sure how to send the result or where to send it to. Does process.send accept this if I were to add process.send(CCW or CW)? I have tried looking for where process.send would go but have not found it.

I would make currentDt a more complex object, something like

currentDt = {
  value = something
  direction = 'CW'
}

Then, in Rower.js you could change flywheel.pushValue(currentDt) into flywheel.pushValue(currentDt.value). Directly under that statement you'll find a case-statement that basically decides whether the flywheel is been driven or that the rower is recovering. There you need to add some intelligent behaviour to handle the currentDt.direction.

[ThreeSpaceTab]

Where is the define statement for currentDT? I haven't been able to find it.

[ThreeSpaceTab]

@swedchef

Hi - i don't want to sidetrack the discussion, but i have just purchased a water rower with a very similar look and setup regarding reed sensors (this one: https://livingsport.dk/titan-life-rower-r72), so i am very interested in your setup and configuration as the included monitor (as far as i can see) does not live up to the "Bluetooth" label that is put as part of the sales pitch.

I am a programmer, and i have the rower (but no free raspberry yet), so please let me know if i can assist in any way - just reach out.

Have a great day!

Yes that would be great if you could help on the coding side. I have a second reed sensor added on pin 2 and am struggling on how to code that in. Ideally I would like to make a config setting that can implement all of these changes automatically.

[JaapvanEkris]

Where is the define statement for currentDT? I haven't been able to find it.

See https://github.com/JaapvanEkris/openrowingmonitor/blob/v1beta_updates/docs/Architecture.md , it's kife is initiated in GpioTimerService.js

[ThreeSpaceTab]

Here is my raw time between pulses for a single magnet. I have not gotten it to recognize 2 strokes yet.
10.184347368
0.066513033
0.239776213
0.044281606
0.171469163
0.033884384
0.139913486
0.029869266
0.124045412
0.025661283
0.111500631
0.024470134
0.104967119
0.023392369
0.101812734
0.022706117
0.101215805
0.022792888
0.179474398
0.110073126
0.021838041
0.082709285
0.018668916
0.077320205
0.018618395
0.085997681
0.023405703
0.106882282
0.028645564
0.123718849
0.028488844
0.117305807
0.027139621
0.116567262
0.028938013
0.127295006
0.033553445
0.236290316
0.200822385
0.03778924

[JaapvanEkris]

When I have run the update script, it says I am up to date on the default version. I have set the minimumTimeBetweenImpulses to 0.1 to try to negate the skip but it is still not catching a second stroke. I have no issue taking the machine apart if required.

You need to rerun the install script where you replace the repository name by

GIT_REMOTE="https://github.com/laberning/openrowingmonitor.git"

with

GIT_REMOTE="https://github.com/jaapvanekris/openrowingmonitor.git"

And you need to change the repository. First approach is to change the repo in the install script by searching for main and replacing it by Backend_Redesign. Alternatively, you can update using the updatescript

updateopenrowingmonitor.sh -b Backend_Redesign

This installs the new brach.

minimumTimeBetweenImpulses will not help you, as the noise is too systematic. That is why @Abasz and I introduced the new gpioMinimumPulseLength setting, that kills this kind of noise in a decent way.

[ThreeSpaceTab]

Great thank you for this. I have the backend_redesign installed using that updatescript. Thank you for your help and insight!

[Abasz]

Great thank you for this. I have the backend_redesign installed using that updatescript. Thank you for your help and insight!

Note, the backend_redesign have been merged into betaV1 on the main repo: https://github.com/laberning/openrowingmonitor/tree/v1beta

[ThreeSpaceTab]

That would make sense why it was not working. Thanks!
Just going through the process of getting multiple strokes to be recognized in a row still.

[JaapvanEkris]

There is a manual for that, see https://github.com/laberning/openrowingmonitor/blob/v1beta/docs/rower_settings.md