Not sure how to get log files #111
Replies: 26 comments 33 replies
-
|
You should copy the file, because default.config.js has a function as well. May I suggest using the v1Beta branch (run the update script with -b v1beta) as that branch is actually a lot better. To create tcx files, you need to set createTcxFiles to true, and make sure dataDirectory is filled with an existing directory. AFAIK, it stores these files in /opt/openrowingmonitor/data by default. I changed it to /home/pi/data When Open Rowing Monitor creates a file, it is noted in the syslog what it is named and where it is stored.. If you want more detailed data, v1Beta also provides excel output: by setting createRowingDataFiles to true you get a lot more information. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you I will will explore this now. |
Beta Was this translation helpful? Give feedback.
-
|
@JaapvanEkris one additional feature ID: enabling changing certain settings via GUI. Not all, but like data file generation and what not. |
Beta Was this translation helpful? Give feedback.
-
@Abasz Could be a good one, although some settings are copied into internal variables, so they become static unexpectedly. So aside a bit of GUI work, we might to look at the variables how they are used. BTW, I already build a config checking function, putting errors and warnings in the syslog when stuff is missing or contains obvious errors. |
Beta Was this translation helpful? Give feedback.
-
|
I think the way this could be implemented (not now but at a later stage) is that we add the settings object to the store and the settings can be requested from the store. The store can negotiate changes with the config manager (and save it to a json settings variable or something). Or the settings store can be separate from the main store and be in the config manager (this is probably simpler). but these are implementation details, I would postpone this when we have the revised v1beta. Any way this needs to be thought trough. I might file an issue to keep track of this idea. |
Beta Was this translation helpful? Give feedback.
-
Ideally, you indeed would have a separate settings store which broadcasts its own config changes and pushes them to the features and the engine. And your idea is a good one: the current configmanager then becomes a way to persist settings and retrieve them again. Honestly, I think that in the end it is a necessity as these buttons are getting pretty small. And the Strave popup is a bit odd as well as you need to do a part through SSH, and a part through the GUI. Having a settings page, potentially per user, where key settings can be edited would be very interesting. Some current settings should actually move to such user settings (like BT, ANT, TCX, RowingData and file location preferences). BTW: the complete settings sanity check is now part of v1Beta_update. It will detect, log and possibly correct settings errors. Just to prevent total chaos when a settings file is corrupted. |
Beta Was this translation helpful? Give feedback.
-
|
I did carry out an update using the beta as suggested. Unfortunately on running the server I received no feedback except the heart rate which toggles with stroke rate (I assume). |
Beta Was this translation helpful? Give feedback.
-
|
Please note that the templates for the rowers has changed. |
Beta Was this translation helpful? Give feedback.
-
|
I have gone back to original version for now because I can use it. The new
one does not report any rowing values, only heart rate. I will investigate
further after I have had a week or rowing. To make up for a few lost days :)
…On Thu, Jan 12, 2023, 9:41 PM Jaap van Ekris ***@***.***> wrote:
Please note that the templates for the rowers has changed.
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCAZHW4RZZOEJAYK6G5DWSACYLANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Can you please enable raw data file generation and then send it here so we can have a look? It should be in settings. That way we could simulate a session locally |
Beta Was this translation helpful? Give feedback.
-
|
I have done that but can not find any data files that have been generated.
I even used 'find' to search whole disk.
Currently I am making my way through
https://github.com/laberning/openrowingmonitor/blob/v1beta/docs/rower_settings.md
To try and fault find. The first step is to create data file. No file is
created.
…On Fri, Jan 13, 2023, 4:13 PM Abasz ***@***.***> wrote:
Can you please enable raw data file generation and then send it here so we
can have a look? It should be in settings. That way we could simulate a
session locally
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA4HUH6LBRCTVM36URTWSEFAZANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Hello Martin, I am not sure whether you are looking for log files or data files. Log files or rather the program's output can be gathered by running Data files (.csv or .tcx files) will be generated when the configuration is correct. ORM's v1 branch failed very silently when I used it for the first time with incorrect settings - I believe Jaap has now introdued some checks when the config files are read. What resolved the issue for me was to copy ALL values from the DEFAULT section of to That gave me at least some (very odd) numbers on the screen when pulling the handle. The next step was to modify the settings for my rower until the values made more sense ie. about 9-10m for each stroke at 20-22 spm and split times of 2:30 for a relaxed row. Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I'll take a look.
…On Fri, Jan 13, 2023 at 9:15 PM Gordon-Shumway2 ***@***.***> wrote:
Hello Martin,
I am not sure whether you are looking for log files or data files.
Log files or rather the program's output can be gathered by running
_journalctl -u openrowingmonitor_
Data files (.csv or .tcx files) will be generated when the configuration
is correct. ORM's v1 branch failed very silently when I used it for the
first time with incorrect settings - I believe Jaap has now introdued some
checks when the config files are read.
What resolved the issue for me was to copy ALL values from the DEFAULT
section of rower.profiles.js into a newly created section for my rower
("neon_pro"). Then I added
`rowerSettings: rowerProfiles.neon_pr`
to config/config.js and restarted the openrowingmonitor service.
That gave me at least some (very odd) numbers on the screen when pulling
the handle. The next step was to modify the settings for my rower until the
values made more sense ie. about 9-10m for each stroke at 20-22 spm and
split times of 2:30 for a relaxed row.
Hope this helps.
Michael
—
Reply to this email directly, view it on GitHub
<#111 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA24DZYM7NYINO4ATNTWSFIO7ANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
I have put a copy of the config.js file
Jan 14 10:41:13 rowingmonitor systemd[1]: Started Open Rowing Monitor.
Jan 14 10:41:16 rowingmonitor npm[1450]: > ***@***.*** start
Jan 14 10:41:16 rowingmonitor npm[1450]: > node app/server.js
Jan 14 10:41:18 rowingmonitor npm[1524]: ==== Open Rowing Monitor 0.8.2
====
Jan 14 10:41:18 rowingmonitor npm[1524]: Session settings: distance limit:
none, time limit: none
Jan 14 10:41:18 rowingmonitor npm[1524]: bluetooth profile: FTMS Rower
Jan 14 10:41:18 rowingmonitor npm[1524]: webserver running on port 80
Jan 14 12:33:37 rowingmonitor npm[1538]: 2023-01-14 12:33:37 sigHandler:
Unhandled signal 18, terminating
Jan 14 12:33:37 rowingmonitor systemd[1]: Stopping Open Rowing Monitor...
Jan 14 12:33:37 rowingmonitor systemd[1]: openrowingmonitor.service:
Succeeded.
Jan 14 12:33:37 rowingmonitor systemd[1]: Stopped Open Rowing Monitor.
Jan 14 12:33:37 rowingmonitor systemd[1]: openrowingmonitor.service:
Consumed 31.068s CPU time.
Jan 14 12:33:37 rowingmonitor systemd[1]: Started Open Rowing Monitor.
Jan 14 12:33:39 rowingmonitor npm[1832]: > ***@***.*** start
Jan 14 12:33:39 rowingmonitor npm[1832]: > node app/server.js
Jan 14 12:33:40 rowingmonitor npm[1844]: ==== Open Rowing Monitor 0.8.2
====
Jan 14 12:33:40 rowingmonitor npm[1844]: Session settings: distance limit:
none, time limit: none
Jan 14 12:33:40 rowingmonitor npm[1844]: bluetooth profile: FTMS Rower
Jan 14 12:33:40 rowingmonitor npm[1844]: webserver running on port 80
Jan 14 12:43:27 rowingmonitor npm[1858]: 2023-01-14 12:43:27 sigHandler:
Unhandled signal 18, terminating
Jan 14 12:43:27 rowingmonitor systemd[1]: Stopping Open Rowing Monitor...
Jan 14 12:43:27 rowingmonitor npm[1858]: 2023-01-14 12:43:27 sigHandler:
Unhandled signal 18, terminating
Jan 14 12:43:27 rowingmonitor npm[1858]: 2023-01-14 12:43:27 sigHandler:
Unhandled signal 15, terminating
Jan 14 12:43:27 rowingmonitor npm[1858]: 2023-01-14 12:43:27 sigHandler:
Unhandled signal 11, terminating
Jan 14 12:43:27 rowingmonitor npm[1858]: 2023-01-14 12:43:27 sigHandler:
Unhandled signal 11, terminating
Jan 14 12:43:27 rowingmonitor systemd[1]: openrowingmonitor.service:
Succeeded.
Jan 14 12:43:27 rowingmonitor systemd[1]: Stopped Open Rowing Monitor.
Jan 14 12:43:27 rowingmonitor systemd[1]: openrowingmonitor.service:
Consumed 48.901s CPU time.
Jan 14 12:43:27 rowingmonitor systemd[1]: Started Open Rowing Monitor.
Jan 14 12:43:28 rowingmonitor npm[1961]: > ***@***.*** start
Jan 14 12:43:28 rowingmonitor npm[1961]: > node app/server.js
Jan 14 12:43:29 rowingmonitor npm[1973]: ==== Open Rowing Monitor 0.8.2
====
Jan 14 12:43:29 rowingmonitor npm[1973]: Session settings: distance limit:
none, time limit: none
Jan 14 12:43:29 rowingmonitor npm[1973]: bluetooth profile: FTMS Rower
Jan 14 12:43:29 rowingmonitor npm[1973]: webserver running on port 80
Jan 14 12:49:44 rowingmonitor npm[1987]: 2023-01-14 12:49:44 sigHandler:
Unhandled signal 15, terminating
Jan 14 12:49:44 rowingmonitor npm[1987]: 2023-01-14 12:49:44 sigHandler:
Unhandled signal 18, terminating
Jan 14 12:49:44 rowingmonitor systemd[1]: Stopping Open Rowing Monitor...
and output from journalctl -u openrowingmonitor
I set up a directory /opt/openrowingmonitor/data ---- but still no data .
I am really not sure what to do right now. I connected my rower reed sensor
back to the simple monitor it came with and it is certainly working and
updating the display. When I put an ohmmeter across the reed sensor there
is one peak pulling and one peak returning.
On Sat, Jan 14, 2023 at 6:49 AM Martin Prior ***@***.***> wrote:
Thanks, I'll take a look.
On Fri, Jan 13, 2023 at 9:15 PM Gordon-Shumway2 ***@***.***>
wrote:
> Hello Martin,
>
> I am not sure whether you are looking for log files or data files.
>
> Log files or rather the program's output can be gathered by running
>
> _journalctl -u openrowingmonitor_
>
> Data files (.csv or .tcx files) will be generated when the configuration
> is correct. ORM's v1 branch failed very silently when I used it for the
> first time with incorrect settings - I believe Jaap has now introdued some
> checks when the config files are read.
>
> What resolved the issue for me was to copy ALL values from the DEFAULT
> section of rower.profiles.js into a newly created section for my rower
> ("neon_pro"). Then I added
>
> `rowerSettings: rowerProfiles.neon_pr`
>
> to config/config.js and restarted the openrowingmonitor service.
>
> That gave me at least some (very odd) numbers on the screen when pulling
> the handle. The next step was to modify the settings for my rower until the
> values made more sense ie. about 9-10m for each stroke at 20-22 spm and
> split times of 2:30 for a relaxed row.
>
> Hope this helps.
> Michael
>
> —
> Reply to this email directly, view it on GitHub
> <#111 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A4JUCA24DZYM7NYINO4ATNTWSFIO7ANCNFSM6AAAAAATY3IGLQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***
> .com>
>
'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 {
// example: change the default log level:
loglevel: {
default: 'debug'
},
// example: set a rower profile:
rowerSettings: rowerProfiles.Chinese_Water_Rower
// example: set custom rower settings:
rowerSettings: {
numOfImpulsesPerRevolution: 1,
dragFactor: 0.03,
flywheelInertia: 0.3
}
// example: set a rower profile, but overwrite some settings:
rowerSettings: Object.assign(rowerProfiles.Chinese_Water_Rower, {
autoAdjustDragFactor: true
})
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
}
~
|
Beta Was this translation helpful? Give feedback.
-
|
I think I see the problem. The ORM is in a boot loop. the v1beta is less forgiving in terms of incorrect settings than the main branch. There is really one file that you need to edit in terms of config and that is config.js. So basically in the config file you should have 3 files:
from the three only the config.js should be edited the other two should generally not. The only exception is rowerProfiles.js if you add a new rower profile. So first please confirm that you added a Second, we should revisit config.js: In your settings you are overriding multiple things: first you set these but later you are overriding this with a new value for the same property rowerSettings: {
numOfImpulsesPerRevolution: 1,
dragFactor: 0.03,
flywheelInertia: 0.3
}with these: rowerSettings: Object.assign(rowerProfiles.Chinese_Water_Rower, {
autoAdjustDragFactor: true
})So the first rowerSettings: Object.assign(rowerProfiles.DEFAULT, {
autoAdjustDragFactor: true,
numOfImpulsesPerRevolution: 1,
dragFactor: 0.03,
flywheelInertia: 0.3
})note the aboe does not use the Also would you be able to go to /opt/openrowingmonitor and issue command Let me know if you have any questions. |
Beta Was this translation helpful? Give feedback.
-
|
I carried out those mods and started the app via nmp. This immediately reported the heartrate monitor but no activity from rowing. The data file is just never used. I have another solution and that is to fit a cadence sensor and use QZ-qdomyos software. Perhpas for time being I should use that. In the meantime I will brush off my C skills and look at how to interface with the reed sensor on the gpio to learn how it works. Once again thank you to all who have contributed. |
Beta Was this translation helpful? Give feedback.
-
|
Can you please post the output of the command We are happy to help and every feedback counts. If you say it's complicated than we need to make it simpler:). Thanks for your time trying it out. It's important we have the logs and output otherwise we don't know what is going on. You can test the gpio with the following command from the terminal of the PI: It should return level=1 for high (magnet) and level=0 low if magnet is there |
Beta Was this translation helpful? Give feedback.
-
The datafile is never used because it demands at least 10 seconds of rowingdata. But as your install crashes before it gets to that point, it won't generate any datafields.
It is doable, just give it a bit time. We will help you through this. when you go to the app and start it, thus cd /opt/openrowingmonitor/app
sudo npm startYou typically get decent feedback from NPM where it crashes, allowing us to understand what goes wrong. My gut feeling, as is @Abasz, is that your settings file really is incomplete. Normally, the default.config.js is copied to config.js, and then you can change stuff. I see a ton of things missing in the config which might or might not work when used for plain default settings. Regardless, ORM shouldn't crash when the config file is empty, it reverts to defaults set in the two other files. However, when these files are changed by users, stuff will crash So making sure that your settings directory contains three files (with two being copies of the clean untouched files from the install) like @Abasz said is step one. Make sure your config.js is a copy of default.config.js and than see what happends.
A cadance sensor ommits the physics behind the scenes of rowing machines. The GPIO-part is doable, but a lot of the other stuff is pretty advanced maths and physics. But when you can read C, you should be able to see where the code goes wrong, IMHO. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for you response. I will re-examine.
…On Sat, Jan 14, 2023, 4:17 PM Abasz ***@***.***> wrote:
I think I see the problem. The ORM is in a boot loop. the v1beta is less
forgiving in terms of incorrect settings than the main branch. There is
really one file that you need to edit in terms of config and that is
config.js.
So basically in the config file you should have 3 files:
- config.js
- default.config.js
- rowerProfiles.js
from the three only the config.js should be edited the other two should
generally not. The only exception is rowerProfiles.js if you add a new
rower profile.
So first please confirm that you added a Chinese_Water_Rower in the
rowerProfiles.js as that is not yet included in the default.
*Second, we should revisit config.js:*
In your settings you are overriding multiple things:
first you set these but later you are overriding this with a new value for
the same property
rowerSettings: {
numOfImpulsesPerRevolution: 1,
dragFactor: 0.03,
flywheelInertia: 0.3
}
with these:
rowerSettings: Object.assign(rowerProfiles.Chinese_Water_Rower, {
autoAdjustDragFactor: true
})
So the first rowerSettings is not necessary as you are overriding it any
way and non of the properties are present. If you want to change those
three settings than this is what should be done:
rowerSettings: Object.assign(rowerProfiles.DEFAULT, {
autoAdjustDragFactor: true,
numOfImpulsesPerRevolution: 1,
dragFactor: 0.03,
flywheelInertia: 0.3
})
note the aboe does not use the Chinese_Water_Rower but rather the
defaults with overrides.
Also would you be able to go to /opt/openrowingmonitor and issue command npm
start? The feedback there is better for errors than the syslog.
Let me know if you have any questions.
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA3U6OZ3ICR4DV6NY2LWSJOIRANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I'll take a look.
…On Sat, Jan 14, 2023 at 9:54 PM Jaap van Ekris ***@***.***> wrote:
I carried out those mods and started the app via nmp. This immediately
reported the heartrate monitor but no activity from rowing. The data file
is just never used.
The datafile is never used because it demands at least 10 seconds of
rowingdata. But as your install crashes before it gets to that point, it
won't generate any datafields.
I think perhaps that I really do not have a enough knowledge for this. I
was excited when the original software worked upon setup apart from the
fact it only read one stroke but at least something appeared. With the beta
I have only ever had the heart rate. To continue means I really need to get
to grips with npm, javascript and so on.
It is doable, just give it a bit time. We will help you through this. when
you go to the app and start it, thus
cd /opt/openrowingmonitor/app
sudo npm start
You typically get decent feedback from NPM where it crashes, allowing us
to understand what goes wrong. My gut feeling, as is @Abasz
<https://github.com/Abasz>, is that your settings file really is
incomplete. Normally, the default.config.js is copied to config.js, and
then you can change stuff. I see a ton of things missing in the config
which might or might not work when used for plain default settings.
Regardless, ORM shouldn't crash when the config file is empty, it reverts
to defaults set in the two other files. However, when these files are
changed by users, stuff will crash So making sure that your settings
directory contains three files (with two being copies of the clean
untouched files from the install) like @Abasz <https://github.com/Abasz>
said is step one. Make sure your config.js is a copy of default.config.js
and than see what happends.
I have another solution and that is to fit a cadence sensor and use
QZ-qdomyos software. Perhpas for time being I should use that. In the
meantime I will brush off my C skills and look at how to interface with the
reed sensor on the gpio to learn how it works. I feel quite bad at taking
your time like this. besides that I am not getting in much rowing and I
also have to run my bakery.....
A cadance sensor ommits the physics behind the scenes of rowing machines.
The GPIO-part is doable, but I'm a bit puzzled that your reaction to a
configuration issue you think you lack the knowledge to resolve is by
writing code yourself. Me and @Abasz <https://github.com/Abasz> are
originally C/C++/C## programmers, and that style is reflected in the Java
as well. So when you can read C, you should be able to see where the code
goes wrong, IMHO.
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA3WXZJPT7GECME5FLLWSKVZTANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
output from npm start. It looks like pigpio error. Itried this
https://github.com/fivdi/pigpio#installation
but still seems to be the same
…On Sat, Jan 14, 2023 at 7:53 PM Abasz ***@***.***> wrote:
Can you please post the output of the command npm start.
We are happy to help and every feedback counts. If you say it's
complicated than we need to make it simpler:). Thanks for your time trying
it out. It's important we have the logs and output otherwise we don't know
what is going on.
You can test the gpio with the following command from the terminal of the
PI:
raspi-gpio get 17 essentially dísz where is the state of the gpio.
It should return level=1 for high (magnet) and level=0 low if magnet is
there
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA4TMC2BPWSDM4JSDILWSKHSJANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Ok, there are several issues:
then check the output of |
Beta Was this translation helpful? Give feedback.
-
martin@rowingmonitor:~ $ sudo pigpiod
|
| Error: "Module did not self-register" |
|---|
| If you are working on a Raspberry Pi and see a "Module did not self- |
| register" error, this typically indicates that the installation |
| instructions were not exactly followed. For further details see the |
| installation section of the readme at |
| https://github.com/fivdi/pigpio#installation |
| Note that step 1 of the installation instructions must be completed |
| before step 2. |
| +-----------------------------------------------------------------------+ |
Invoking require('bindings')('pigpio.node') resulted in the follwoing error:
Error: Module did not self-register: '/opt/openrowingmonitor/node_modules/pigpio/build/Release/pigpio.node'.
at Object.Module._extensions..node (node:internal/modules/cjs/loader:1249:18)
at Module.load (node:internal/modules/cjs/loader:1043:32)
at Function.Module._load (node:internal/modules/cjs/loader:878:12)
at Module.require (node:internal/modules/cjs/loader:1067:19)
at require (node:internal/modules/cjs/helpers:103:18)
at bindings (/opt/openrowingmonitor/node_modules/bindings/bindings.js:112:48)
at /opt/openrowingmonitor/node_modules/pigpio/pigpio.js:8:31
at Object. (/opt/openrowingmonitor/node_modules/pigpio/pigpio.js:43:3)
at Module._compile (node:internal/modules/cjs/loader:1165:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10)
/opt/openrowingmonitor/node_modules/pigpio/pigpio.js:456
pigpio.gpioCfgClock(+microseconds, +peripheral);
^
TypeError: pigpio.gpioCfgClock is not a function
at Object.module.exports.configureClock (/opt/openrowingmonitor/node_modules/pigpio/pigpio.js:456:10)
at createGpioTimerService (file:///opt/openrowingmonitor/app/gpio/GpioTimerService.js:37:10)
at file:///opt/openrowingmonitor/app/gpio/GpioTimerService.js:63:1
Beta Was this translation helpful? Give feedback.
-
|
could be that you didn't install the pigpio c-library. Could you do
|
Beta Was this translation helpful? Give feedback.
-
This is the issue I had. generally this error means that something else is already using the pigpio. For me restart solved the problem, and the can you please provide the output of the following commands: as well as |
Beta Was this translation helpful? Give feedback.
-
|
Appears something to do with pigpio
…On Sat, Jan 14, 2023 at 9:54 PM Jaap van Ekris ***@***.***> wrote:
I carried out those mods and started the app via nmp. This immediately
reported the heartrate monitor but no activity from rowing. The data file
is just never used.
The datafile is never used because it demands at least 10 seconds of
rowingdata. But as your install crashes before it gets to that point, it
won't generate any datafields.
I think perhaps that I really do not have a enough knowledge for this. I
was excited when the original software worked upon setup apart from the
fact it only read one stroke but at least something appeared. With the beta
I have only ever had the heart rate. To continue means I really need to get
to grips with npm, javascript and so on.
It is doable, just give it a bit time. We will help you through this. when
you go to the app and start it, thus
cd /opt/openrowingmonitor/app
sudo npm start
You typically get decent feedback from NPM where it crashes, allowing us
to understand what goes wrong. My gut feeling, as is @Abasz
<https://github.com/Abasz>, is that your settings file really is
incomplete. Normally, the default.config.js is copied to config.js, and
then you can change stuff. I see a ton of things missing in the config
which might or might not work when used for plain default settings.
Regardless, ORM shouldn't crash when the config file is empty, it reverts
to defaults set in the two other files. However, when these files are
changed by users, stuff will crash So making sure that your settings
directory contains three files (with two being copies of the clean
untouched files from the install) like @Abasz <https://github.com/Abasz>
said is step one. Make sure your config.js is a copy of default.config.js
and than see what happends.
I have another solution and that is to fit a cadence sensor and use
QZ-qdomyos software. Perhpas for time being I should use that. In the
meantime I will brush off my C skills and look at how to interface with the
reed sensor on the gpio to learn how it works. I feel quite bad at taking
your time like this. besides that I am not getting in much rowing and I
also have to run my bakery.....
A cadance sensor ommits the physics behind the scenes of rowing machines.
The GPIO-part is doable, but I'm a bit puzzled that your reaction to a
configuration issue you think you lack the knowledge to resolve is by
writing code yourself. Me and @Abasz <https://github.com/Abasz> are
originally C/C++/C## programmers, and that style is reflected in the Java
as well. So when you can read C, you should be able to see where the code
goes wrong, IMHO.
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA3WXZJPT7GECME5FLLWSKVZTANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
when I run sudo pigpiod -v I get 79 so it is installed
New Topic: when installing Pi OS we are not allowed to use/retain
pi/raspberry user/password. so I set myname/password. I see I need to use
sudo a lot to install things which is quite normal for Debian. By the way I
only use Unix/Linux for around 30 years I never use Windows (if I can help
it). Do I need a pi user for the software to install correctly?
…On Sun, Jan 15, 2023 at 8:24 AM Martin Prior ***@***.***> wrote:
output from npm start. It looks like pigpio error. Itried this
https://github.com/fivdi/pigpio#installation
but still seems to be the same
On Sat, Jan 14, 2023 at 7:53 PM Abasz ***@***.***> wrote:
> Can you please post the output of the command npm start.
>
> We are happy to help and every feedback counts. If you say it's
> complicated than we need to make it simpler:). Thanks for your time trying
> it out. It's important we have the logs and output otherwise we don't know
> what is going on.
>
> You can test the gpio with the following command from the terminal of the
> PI:
> raspi-gpio get 17 essentially dísz where is the state of the gpio.
>
> It should return level=1 for high (magnet) and level=0 low if magnet is
> there
>
> —
> Reply to this email directly, view it on GitHub
> <#111 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A4JUCA4TMC2BPWSDM4JSDILWSKHSJANCNFSM6AAAAAATY3IGLQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***
> .com>
>
|
Beta Was this translation helpful? Give feedback.
-
|
Not as far as I know. Some parts need root privileges, but it shouldn't be tied to user pi |
Beta Was this translation helpful? Give feedback.
-
|
[image: image.png]
I purged and resinstalled pigpio
…On Sun, Jan 15, 2023 at 6:01 PM Abasz ***@***.***> wrote:
Ok, there are several issues:
1. the port 80 on which ORM tries to run is already in use (it could
be that ORM is already running as a systemd service - that would cause
issue for pigpio as well or like in my case apache2 on your RPI is already
using it). Recommend changing it to 100 (or to anything that is not being
used). This can currently only set via environment variable (i.e. no
settings for this in the config.js). you can set it for the current
terminal as follows: export PORT=100. I think @JaapvanEkris
<https://github.com/JaapvanEkris> this needs to be added as setting,
ENV vars are
not that obvious.
2. you are right about the pigpio library. Can you please purge pigpio
install and reinstall it if you have not tried it already? Also can you
check the output of pigpiod issued to the terminal and copy past it
here? I had issues with pigpio not exiting properly when ORM shutting down
and remaind running (i have a fix for this that needs a little more
testing) and ORM was not able to start it again.
Can you please issue the following commands:
- service openrowingmonitor stop
- systemctl disable openrowingmonitor - disable auto startup of the
service to prevent confilcts with starting it via npm (it can be reenabled
via systemctl enable openrowingmonitor
- killall pigpiod
- killall node
then check the output of export PORT=100 && npm start.
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA6ABYXM72UBBIMDTQTWSPDGPANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
image is not visible |
Beta Was this translation helpful? Give feedback.
-
|
[image: image.png]
[image: image.png]
…On Sun, Jan 15, 2023 at 6:01 PM Abasz ***@***.***> wrote:
Ok, there are several issues:
1. the port 80 on which ORM tries to run is already in use (it could
be that ORM is already running as a systemd service - that would cause
issue for pigpio as well or like in my case apache2 on your RPI is already
using it). Recommend changing it to 100 (or to anything that is not being
used). This can currently only set via environment variable (i.e. no
settings for this in the config.js). you can set it for the current
terminal as follows: export PORT=100. I think @JaapvanEkris
<https://github.com/JaapvanEkris> this needs to be added as setting,
ENV vars are
not that obvious.
2. you are right about the pigpio library. Can you please purge pigpio
install and reinstall it if you have not tried it already? Also can you
check the output of pigpiod issued to the terminal and copy past it
here? I had issues with pigpio not exiting properly when ORM shutting down
and remaind running (i have a fix for this that needs a little more
testing) and ORM was not able to start it again.
Can you please issue the following commands:
- service openrowingmonitor stop
- systemctl disable openrowingmonitor - disable auto startup of the
service to prevent confilcts with starting it via npm (it can be reenabled
via systemctl enable openrowingmonitor
- killall pigpiod
- killall node
then check the output of export PORT=100 && npm start.
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA6ABYXM72UBBIMDTQTWSPDGPANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
image does not load |
Beta Was this translation helpful? Give feedback.
-
|
Ok I will convert to text files and send in the morning. Gmail seems to be
preventing certain files now.
…On Sun, Jan 15, 2023, 7:50 PM Abasz ***@***.***> wrote:
image does not load
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA2RWHWS6Z4QWNS6QE3WSPP7DANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
There also is a webinterface to GitHub that is much more flexible. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
This to me the above means that rpi picks up the impulses. I think this is really a pigpio issue.
https://abyz.me.uk/rpi/pigpio/faq.html:
So as a next step I would try to install pigpio to the correct location expected. Not sure why it is not installed under the rpi location though. |
Beta Was this translation helpful? Give feedback.
-
|
New desktop is rowingmonitor:1 (192.168.0.19:1)
***@***.***:~ $ sudo apt-get -y install pigpio
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
pigpio is already the newest version (1.79-1+rpt1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
***@***.***:~ $ sudo systemctl mask pigpiod.service
Created symlink /etc/systemd/system/pigpiod.service → /dev/null.
***@***.***:~ $
…On Mon, Jan 16, 2023 at 8:19 AM Jaap van Ekris ***@***.***> wrote:
could be that you didn't install the pigpio c-library. Could you do
sudo apt-get -y install pigpio
sudo systemctl mask pigpiod.service
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCAZGCX4KKBZVZVWD2M3WSSHZ3ANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
***@***.***:~ $ which pigpiod
/usr/local/bin/pigpiod
***@***.***:~ $ which pigpiod | wc -l
1
***@***.***:~ $ node -v
v16.19.0
***@***.***:~ $ sudo node -v
v16.19.0
***@***.***:~ $
just a thought. I was wondering if it would be easier to make an iso of a
working setup. This could be transferred to a ssd and then booted so we
were all on the same playing field. we would of course need to ammend the
config for the rower.
…On Mon, Jan 16, 2023 at 5:41 PM Abasz ***@***.***> wrote:
***@***.***:~ $ sudo pigpiod
2023-01-15 23:36:13 initInitialise: Can't lock /var/run/pigpio.pid
Can't initialise pigpio library
***@***.***:~ $
***@***.***:/opt/openrowingmonitor/app# export PORT=100 && npm
start
This is the issue I had. generally this error means that something else is
already using the pigpio. For me restart solved the problem, and the killall
node
can you please provide the output of the following commands:
which pigpiod
which pigpiod | wc -l
as well as
node -v
sudo node -v
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA4NG7NOXH2OH46WVKDWSUJU3ANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
We support several different devices (i.e RPi 3B, RPi 4B and Pi Zero, etc), which makes this appoach infeasible. The scripts should take care of most issues. I also don't understand why pigpio is installed in a different location. What version of Raspbian are you running? |
Beta Was this translation helpful? Give feedback.
-
|
I guess this is what we are looking for?
***@***.***:/opt/openrowingmonitor/bin# systemctl disable
openrowingmonitor
***@***.***:/opt/openrowingmonitor/bin# killall pigpiod
***@***.***:/opt/openrowingmonitor/bin# export PORT=100 && npm start
***@***.*** start
node app/server.js
==== Open Rowing Monitor 0.8.2 ====
Session settings: distance limit: none, time limit: none
bluetooth profile: FTMS Rower
webserver running on port 100
I made sure all the pig* stuff was as Rasperry pi wanted it. How was
pig* installed in the first place the script or was it on the original
pi ssd? I only started playing with pig* in the last day or so.
It is late now and as a Baker I have to get up early. So assuming this
is OK should I set it back to systemctl?
…On Mon, Jan 16, 2023 at 6:47 PM Abasz ***@***.***> wrote:
This to me the above means that rpi picks up the impulses. I think this is
really a pigpio issue.
/usr/local/bin/pigpiod this install location is interesting as I would
expect it to be installed under /usr/bin/pigpiod
https://abyz.me.uk/rpi/pigpio/faq.html:
The raspberrypi.org image containing pigpio uses different locations.
/usr/include (pigpio.h, pigpiod_if.h, pigpiod_if2.h)
/usr/lib (libpigpio.so, libpigpiod_if.so, libpigpiod_if2.so)
/usr/bin (pig2vcd, pigpiod, pigs)
/usr/man (man pages)
Mostly this doesn't matter as the /usr/local directories will generally be
earlier in the search path. The pigpio built includes, binaries, and
manuals are normally found first.
However the wrong libraries may be linked during the compilation. If this
is the case remove the /usr/lib entries for libpigpio.so ,
libpigpiod_if.so, and libpigpiod_if2.so
So as a next step I would try to install pigpio to the correct location
expected. Not sure why it is not installed under the rpi location though.
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCAZHPFQ2JEOECC3REZ3WSURNDANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
yes, setting the service back is the next logical step in the debugging process. Just to clarify, do I understand the log correctly that now there are no other output i.e. no errors? I am really looking forward to see if the issue gets resolved or not. Please note that if apache2 uses port 80 than the port environmental variable may still need changes. pigpio should be installed by the script |
Beta Was this translation helpful? Give feedback.
-
|
Ah OK, just a thought. My version s Raspian 11.
I did carry out the installation several times and each produced the same
result. I will write this to an iso and then perhaps try to install again.
…On Mon, Jan 16, 2023 at 9:47 PM Jaap van Ekris ***@***.***> wrote:
We support several different devices (i.e RPi 3B, RPi 4B and Pi Zero,
etc), which makes this appoach infeasible. The scripts should take care of
most issues. I also don't understand why pigpio is installed in a different
location.
What version of Raspbian are you running?
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA2MZRILMIRILQFEPGTWSVGNVANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
I just ranas below : I had to make the PORT change to eliminate the first error. the the second error I saw that I needed to check if other processe was running pigpiod but as you can see on the last line there were none. root@rowingmonitor:/opt/openrowingmonitor/bin# export PORT=100
==== Open Rowing Monitor 0.8.2 ==== Session settings: distance limit: none, time limit: none bluetooth profile: FTMS Rower Error: pigpio error -1 in gpioInitialise |
Beta Was this translation helpful? Give feedback.
-
|
I followed threads this and then carried out the following. so pigpiod appears to be OK but I run openrowingmonitor the same problem pos up> root@rowingmonitor:/opt/openrowingmonitor/bin# systemctl daemon-reload Jan 16 23:53:56 rowingmonitor systemd[1]: Starting Daemon required to control GPIO pins via pigpio... root@rowingmonitor:/opt/openrowingmonitor/bin# ./openrowingmonitor.sh
==== Open Rowing Monitor 0.8.2 ==== Session settings: distance limit: none, time limit: none bluetooth profile: FTMS Rower Error: pigpio error -1 in gpioInitialise |
Beta Was this translation helpful? Give feedback.
-
|
Two things:
As the npm pigpio doc says:
That is why the install script and I here let you do
To prevent the deamon from starting. Please, kill the deamon and make sure it stays down! |
Beta Was this translation helpful? Give feedback.
-
|
Yes the issue is that either: a) pigpio is already used by the
b) pigpio is already used by an instance of ORM (service or direct npm call). - solution: you need to purge both instances and start from scratch
|
Beta Was this translation helpful? Give feedback.
-
|
***@***.***:/opt/openrowingmonitor/bin# export PORT=100 && npm start
***@***.*** start
node app/server.js
==== Open Rowing Monitor 0.8.2 ====
Session settings: distance limit: none, time limit: none
bluetooth profile: FTMS Rower
webserver running on port 100
heart rate peripheral connected, name: 'Viiiiva', id: f9d7eb83dbf3
stroke: 0, dist: 0.0m, speed: 0.00m/s, pace: Infinity/500m, power: 0W, cal:
0.0kcal, SPM: 0.0, drive dur: NaNs, rec. dur: NaNs, stroke dur: NaNs
Time: 1.0775 sec: calculateCyclePower error: driveDuration = 0.5775 sec,
_cycleDuration = 0.5775 sec
stroke: 2, dist: 7.1m, speed: 3.16m/s, pace: 2:38/500m, power: 88W, cal:
0.4kcal, SPM: 26.5, drive dur: 0.58s, rec. dur: 1.69s, stroke dur: 2.26s
stroke: 3, dist: 43.9m, speed: 3.36m/s, pace: 2:29/500m, power: 108W, cal:
0.8kcal, SPM: 28.1, drive dur: 0.45s, rec. dur: 5.01s, stroke dur: 2.13s
heart rate peripheral disconnected, searching new one
heart rate peripheral connected, name: 'Viiiiva', id: f9d7eb83dbf3
heart rate peripheral disconnected, searching new one
Looks like it is picking up the rower. I have not touched the config files
at all these are the standard ones.
…On Tue, Jan 17, 2023 at 3:42 PM Abasz ***@***.***> wrote:
Yes the issue is that either:
a) pigpio is already used by the pigpiod service so ORM cannot start
(starting pigpiod specifically is not required for ORM, ORM does the work
on its own) - *solution*: as Jaap said,
1. service stop pigpiod, then
2. systemctl mask pigpiod, then
3. killall pigpiod (just to be sure)
b) pigpio is already used by an instance of ORM (service or direct npm
call). - *solution*: you need to purge both instances and start from
scratch
1. service openrowingmonitor stop then
2. killall node, then you can
3. *restart either*: npm start or service openrowingmonitor start. But
since you need to set the PORT via env var, I would go for direct npm start
and disable the openrowingmonitor service and start ORM manually when
needed:
i) systemctl disable openrowingmonitor and then
ii) export PORT=100 && npm start
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA6RNTDZTOFXJ23X42DWSZEMRANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
ime: 1.0775 sec: calculateCyclePower error: driveDuration = 0.5775 sec,
_cycleDuration = 0.5775 sec
stroke: 2, dist: 7.1m, speed: 3.16m/s, pace: 2:38/500m, power: 88W, cal:
0.4kcal, SPM: 26.5, drive dur: 0.58s, rec. dur: 1.69s, stroke dur: 2.26s
stroke: 3, dist: 43.9m, speed: 3.36m/s, pace: 2:29/500m, power: 108W, cal:
0.8kcal, SPM: 28.1, drive dur: 0.45s, rec. dur: 5.01s, stroke dur: 2.13s
heart rate peripheral disconnected, searching new one
heart rate peripheral connected, name: 'Viiiiva', id: f9d7eb83dbf3
heart rate peripheral disconnected, searching new one
heart rate peripheral connected, name: 'Viiiiva', id: f9d7eb83dbf3
stroke: 4, dist: 100.0m, speed: 3.36m/s, pace: 2:29/500m, power: 108W, cal:
1.2kcal, SPM: 28.1, drive dur: 0.46s, rec. dur: 8.34s, stroke dur: 2.13s
stroke: 5, dist: 111.2m, speed: 3.16m/s, pace: 2:38/500m, power: 88W, cal:
1.5kcal, SPM: 26.5, drive dur: 0.52s, rec. dur: 6.68s, stroke dur: 2.26s
stroke: 6, dist: 190.9m, speed: 2.72m/s, pace: 3:04/500m, power: 61W, cal:
2.1kcal, SPM: 15.8, drive dur: 0.46s, rec. dur: 8.34s, stroke dur: 3.81s
stroke: 7, dist: 201.1m, speed: 3.16m/s, pace: 2:38/500m, power: 88W, cal:
2.5kcal, SPM: 26.5, drive dur: 0.45s, rec. dur: 6.68s, stroke dur: 2.26s
heart rate peripheral disconnected, searching new one
heart rate peripheral connected, name: 'Viiiiva', id: f9d7eb83dbf3
heart rate peripheral disconnected, searching new one
heart rate peripheral connected, name: 'Viiiiva', id: f9d7eb83dbf3
from stroke 4 I did exactly 20 strokes. However I did put two extra magnets
the other day and have not taken them off. I had read somewhere extra
magnets might improve things.
…On Tue, Jan 17, 2023 at 4:17 PM Martin Prior ***@***.***> wrote:
***@***.***:/opt/openrowingmonitor/bin# export PORT=100 && npm
start
> ***@***.*** start
> node app/server.js
==== Open Rowing Monitor 0.8.2 ====
Session settings: distance limit: none, time limit: none
bluetooth profile: FTMS Rower
webserver running on port 100
heart rate peripheral connected, name: 'Viiiiva', id: f9d7eb83dbf3
stroke: 0, dist: 0.0m, speed: 0.00m/s, pace: Infinity/500m, power: 0W,
cal: 0.0kcal, SPM: 0.0, drive dur: NaNs, rec. dur: NaNs, stroke dur: NaNs
Time: 1.0775 sec: calculateCyclePower error: driveDuration = 0.5775 sec,
_cycleDuration = 0.5775 sec
stroke: 2, dist: 7.1m, speed: 3.16m/s, pace: 2:38/500m, power: 88W, cal:
0.4kcal, SPM: 26.5, drive dur: 0.58s, rec. dur: 1.69s, stroke dur: 2.26s
stroke: 3, dist: 43.9m, speed: 3.36m/s, pace: 2:29/500m, power: 108W, cal:
0.8kcal, SPM: 28.1, drive dur: 0.45s, rec. dur: 5.01s, stroke dur: 2.13s
heart rate peripheral disconnected, searching new one
heart rate peripheral connected, name: 'Viiiiva', id: f9d7eb83dbf3
heart rate peripheral disconnected, searching new one
Looks like it is picking up the rower. I have not touched the config files
at all these are the standard ones.
On Tue, Jan 17, 2023 at 3:42 PM Abasz ***@***.***> wrote:
> Yes the issue is that either:
>
> a) pigpio is already used by the pigpiod service so ORM cannot start
> (starting pigpiod specifically is not required for ORM, ORM does the
> work on its own) - *solution*: as Jaap said,
>
> 1. service stop pigpiod, then
> 2. systemctl mask pigpiod, then
> 3. killall pigpiod (just to be sure)
>
> b) pigpio is already used by an instance of ORM (service or direct npm
> call). - *solution*: you need to purge both instances and start from
> scratch
>
> 1. service openrowingmonitor stop then
> 2. killall node, then you can
> 3. *restart either*: npm start or service openrowingmonitor start.
> But since you need to set the PORT via env var, I would go for direct npm
> start and disable the openrowingmonitor service and start ORM manually when
> needed:
> i) systemctl disable openrowingmonitor and then
> ii) export PORT=100 && npm start
>
> —
> Reply to this email directly, view it on GitHub
> <#111 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A4JUCA6RNTDZTOFXJ23X42DWSZEMRANCNFSM6AAAAAATY3IGLQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***
> .com>
>
|
Beta Was this translation helpful? Give feedback.
-
|
Looks pretty decent to me. |
Beta Was this translation helpful? Give feedback.
-
|
Yes I just removed the extra magnets and now have one and it appears to be
counting each stroke. Are we then considered fixed? The only thing I need
to do now is to set up so I get the gui monitor.. Then keep testing and of
course using.
…On Tue, Jan 17, 2023 at 5:11 PM Jaap van Ekris ***@***.***> wrote:
Looks pretty decent to me.
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA5AVSVGHYUYZ25KLR3WSZO4RANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Great news! I will put a TLDR at the end of this issue (and/or create a faq trouble whooting guide discussion) since the process and steps that have been included here may be usefull for others in trouble shooting. @JaapvanEkris what would you prefer? redme or discussion with centrailzed faq or tldr type summary at the end of the issue/discussion (I dont like the last one as I cannot change the title of the discussion and that would be important in my view) |
Beta Was this translation helpful? Give feedback.
-
|
I think a trouble shooting guide would be a great addition to the documentation. Nobody wants to go through a large volume of posts anyway. |
Beta Was this translation helpful? Give feedback.
-
ok I wlil add a tldr; here that can be coppied to redme |
Beta Was this translation helpful? Give feedback.
-
|
Yes thank you all so much. Unfortunately I do not really know what fixed
it.
What should I do now to run it in a regular manner. At the moment I only
get text output and no gui.
To get the data files I see they are under data/recordings/2023/01
…On Tue, Jan 17, 2023, 6:45 PM Abasz ***@***.***> wrote:
Great news! I will put a TLDR at the end of this issue (and/or create a
faq trouble whooting guide discussion) since the process and steps that
have been included here may be usefull for others in trouble shooting.
@JaapvanEkris <https://github.com/JaapvanEkris> what would you prefer?
redme or discussion with centrailzed faq or tldr type summary at the end of
the issue/discussion (I dont like the last one as I cannot change the title
of the discussion and that would be important in my view)
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JUCA2W42VJNHP5AQI5VLTWSZZ4HANCNFSM6AAAAAATY3IGLQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
you need to connect to the GUI over port 100 i.e. what you can do is to shut down the currently running npm start process (ctrl + Z from the terminal, or issue However, if apache2 is already using port 80 than ORM will not work. You need to test if it works by starting the ORM service and check the logs ( |
Beta Was this translation helpful? Give feedback.
-
TLDR;1. Error message:initInitialise: Can't lock /var/run/pigpio.pid Can't initialise pigpio library +-----------------------------------------------------------------------+ Error: "Module did not self-register"If you are working on a Raspberry Pi and see a "Module did not self- Invoking require('bindings')('pigpio.node') resulted in the follwoing error: Error: Module did not self-register: '/opt/openrowingmonitor/node_modules/pigpio/build/Release/pigpio.node'. /opt/openrowingmonitor/node_modules/pigpio/pigpio.js:456 TypeError: pigpio.gpioCfgClock is not a function 2. Error descriptionGeneral the above errors could mean two things: a) pigpio has (for currently unknown reasons) been installed to an iccorect location and the Nodejs library interacting with it does not pick it up 3. Debugging and problem resoltuiona) Checking pigpio install location:Run the following command: The above should return If other location (e.g.
Run the following comand: The above should return the same (i.e. the same version of Nodejs is installed for root and non-root users). If versions are different reinstall/update node so they are the same b) Pigpio is already being usedAll instances that use pigpio need to be closed and any potential service that would instantiate it needs to be disabled:
After the above sequence openrowingmonitor may be tested by directly starting it via npm to have better access to error logs: Run the following command (assuming that openrowingmonitor was installed to the default location):
Openrowingmonitor should start without the pigpio error. If this is the case:
|
Beta Was this translation helpful? Give feedback.
-
|
noted |
Beta Was this translation helpful? Give feedback.
-
I have a Chinese made Water Rower and it looks similar to the one you are or were using. I thought I would have a go at installing the openrowingmonitor. I also have a Raspberry Pi 4. I followed your instructions on the Github page and all worked exactly as you described. Thank you. At the moment I have a connected monitor connected vi HDMI. I access localhost from my browser and the application screen appears and when I row the fields fill with numbers that look sensible.
In the config directory are two files config.js and default-confg.js.
Apart from some entries in Syslog I cannot find any logfiles output like tcx files although I thought I copied that section from the default-config.js to config.js.
I confess to knowing little about how to configure that file. Could I just rename default-config.js to config.js and just turn on or off switches?
I think I would like to see all output and then turn off what I do not require. I thnk then I can take a look at any tuning etc I may require.
Beta Was this translation helpful? Give feedback.
All reactions