Issue recording CSV #59
-
|
Thanks Lars for your work on this, getting it set up has been a very enjoyable way of avoiding many other important and urgent tasks. The hints and comments in other board posts have been very helpful for someone fairly inexperienced with this sort of project. I have a very cheap magnetically damped rower bought from the Warehouse in New Zealand for $300 (about £150). It's sold under their "Active Intent" brand, and has model number GB-K101A. On the inside it looks nearly identical to the Abilica Winrower 2.0 mentioned in another post. It had the same arrangement of 2 reed switches on the drive belt, I've relocated one to the fly wheel, and am starting to get some sensible readings with just one magnet (a little neodymium one which clings securely directly to the flywheel). 2 magnets seemed to be giving me confused readings, and since there are about 16 full revolutions of the flywheel for a stroke, I don't think resolution should be lacking. I've been trying to optimise parameters for the rower, but can't get CSV recording to work, which would be really useful to see what's going on. Another post mentioned uncommenting and editing a line in Here's the relevant bit of my config.js _export default {
loglevel: {
default: 'trace',
RowingEngine: 'trace'
},
dataDirectory: 'data',
createTcxFiles: true,
recordRawData: true,
rowerSettings: rowerProfiles.GBK101A_
And here are the rower settings I'm using
_GBK101A: {
minimumTimeBetweenImpulses: 0.01,
maximumTimeBetweenImpulses: 0.8,
maximumDownwardChange: 0.05, // effectively the maximum acceleration
maximumUpwardChange: 1.75, // effectively the maximum decceleration
smoothing: 1,
flankLength: 2,
numberOfErrorsAllowed: 0,
numOfImpulsesPerRevolution: 1,
naturalDeceleration: 0,
maximumImpulseTimeBeforePause: 3.0, // maximum time between impulses before the rowing engine considers it a pause
minimumDriveTime: 0.300, // minimum time of the drive phase
minimumRecoveryTime: 1.00, // minimum time of the recovery phase
flywheelInertia: 0.1,
dragFactor: 14000
},_I haven't figured out how to view the log using websockets, but can list it in ssh using Any suggestions on how to get CSV recording working would be very welcome. I presume that files should appear in the data directory as I've specified in config.js. Also any hints on optimising parameters. Reviewing this now I can see that maximumDownwardChange is much too low, hopefully correcting that will avoid the noise filter. Calculated power and distance are far too high, is this just down to getting the flywheelinertia right? Thanks again, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
That line was needed before Lars perfected the code and made it a configuration setting. As one of the people developping OpenRowingMonitor, I typically run a
in the background. the CSV is helpful if you want to replay things without having to row yet another 2K, but if you want to see what OpenRowingMonitor is doing, and why it is doing it, the syslog is much more helpful in my experience. In your case, your speed is a bit high: 50km/h is pretty fast, I usually reach 14 km/h. So you probably need to do something about the Inertia setting. But stroke detection seems to be pretty stable. The noise filter is kicking in a bit too often for a reason I don't understand (the change is with respect to an identical value? That is a new one for me). What version of OpenRowingMonitor are you using? |
Beta Was this translation helpful? Give feedback.
-
|
Hi Dave, great that you are having a fun journey with this project. After all that's basically why I started this project - to fiddle around with some stuff and probably build something that might be useful 😄 Lately I've squished quite a few bugs in the project, one of them was that the CSV-Export was not working any more (fc00c01), so maybe you are not yet running the latest version? If you used the installer-script you can update by running Also note that the parameter for writing csv has been renamed (see in // Stores the training sessions as TCX files
createTcxFiles: true,
// Stores the raw sensor data in CSV files
createRawDataFiles: false,There is also a new Option to automatically store the different recordings in compressed format, if you want you can enable that with: // 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 ras sensor data recording files (csv.gz)
gzipRawDataFiles: true,Another way to watch the logs while debugging that I use quite often is to start Open Rowing Monitor directly. So you would do something like: # work as root
sudo su
# shutdown the system service
systemctl stop openrowingmonitor
# change to working directory of application
cd /opt/openrowingmonitor
# start the application directly
npm start
# you should see all log output now on the console
# to stop the service press ctrl + cGood luck with your investigations, let us know if you find good settings for your rower so we can add those to the rowing presets. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Lars and Jaap for the speedy, helpful and detailed replies, I'm looking forward to spending some time on this over the weekend.
I only installed it for the first time about a week ago, but evidently it's a very active project, so I'll do the update first, sounds like that'll solve a few issues.
Cheers, Dave
…________________________________
From: Lars Berning ***@***.***>
Sent: Friday, February 4, 2022 6:22:14 AM
To: laberning/openrowingmonitor ***@***.***>
Cc: speed-david ***@***.***>; Author ***@***.***>
Subject: Re: [laberning/openrowingmonitor] Issue recording CSV (Discussion #59)
Hi Dave,
great that you are having a fun journey with this project. After all that's basically why I started this project - to fiddle around with some stuff and probably build something that might be useful :-)
Lately I've squished quite a few bugs in the project, one of them was that the CSV-Export was not working any more (fc00c01<fc00c01>), so maybe you are not yet running the latest version?
If you used the installer-script you can update by running updateopenrowingmonitor in the ssh terminal.
Also note that the parameter for writing csv has been renamed (see in config.js), it is now:
// Stores the training sessions as TCX files
createTcxFiles: true,
// Stores the raw sensor data in CSV files
createRawDataFiles: false,
There is also a new Option to automatically store the different recordings in compressed format, if you want you can enable that with:
// 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 ras sensor data recording files (csv.gz)
gzipRawDataFiles: true,
Another way to watch the logs while debugging that I use quite often is to start Open Rowing Monitor directly.
So you would do something like:
# work as root
sudo su
# shutdown the system service
systemctl stop openrowingmonitor
# change to working directory of application
cd /opt/openrowingmonitor
# start the application directly
npm start
# you should see all log output now on the console
# to stop the service press ctrl + c
Good luck with your investigations, let us know if you find good settings for your rower so we can add those to the rowing presets.
—
Reply to this email directly, view it on GitHub<#59 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXS43EU3LBSZ32W4NM3X4JTUZK2UNANCNFSM5NOO4RGQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I blame @laberning for that, as he is making the major improvements :). I'm just tweaking the stuff he designed here and there, small changes that hopefully make some impact in the end. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks guys, with the new version, and some tweaking of the inertia I'm getting very close to real sounding numbers. Having a live readout of the log was far more useful than looking at csv files. I'm going to try and do some benchmarking against a concept 2 next time I get the chance, to check that my output numbers are reasonable, and then I'll send through my final parameters. Thanks again for the awesome work on this, hugely appreciated |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! Yes, every file except So if you work with a new, not yet published rower profile you should place it in the Just add rowerSettings: {
dragFactor: 0.03,
flywheelInertia: 0.3
}and add all parameters that differ from the default profile... |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
Hi Dave,
great that you are having a fun journey with this project. After all that's basically why I started this project - to fiddle around with some stuff and probably build something that might be useful 😄
Lately I've squished quite a few bugs in the project, one of them was that the CSV-Export was not working any more (fc00c01), so maybe you are not yet running the latest version?
If you used the installer-script you can update by running
updateopenrowingmonitorin the ssh terminal.Also note that the parameter for writing csv has been renamed (see in
config.js), it is now: