I was sitting at anchor the other day and the wind was blowing like stink outside when it occurred to me that a graph of wind speed vs time would be quite interesting.
My setup involves NMEA 0183 feeding to a pi3 running OpenPlotter and this data stream is distributed via wifi in the boat.
I took the signalK data, extracted the wind speed and fed that to a line graph of wind speed vs time. It was supposed to run for an hour. It started just fine (after a bit of trial and error, mostly error) but then after about 5 minutes or so no additional data reached the graph. I could still see wind speed data on the wifi feed but no data was shown on the graph.
I did some googling and found out that there was/is a crashing issues with signalK when too much data is received. I don't know if this is still the case but we are talking maybe one or two data points per second, nothing really high.
Questions:
Is signalK robust enough to use or is it still alpha level stuff?
Is this something that other people have seen and maybe solved?
The way I interpret the graphing output, it is run for x amount of time or x number of data points - is it possible to configure a continuously running graph that displays only the last x hours or x data points. In other words I could look at the last hour of wind speed data whenever I wanted to, the graph is continuousy updated but data older than x hours is dropped from the graph.
I am still having lots of issues wrapping my mind around all this stuff and quite frequently my data stream as far as signalK is concerned just breaks. I use the debug display a lot and for reasons unknown to me, data is not displayed in the debug window a lot of times. I have no idea what I am doing wrong because if I restart processes every once in a while the data starts flowing like I expect it to. At this time I have come to the conclusion that either I am flaky or SignalK and/or node red is flaky. It would be interesting to find out if it is me or if other people have issues like that.
To be clear, I really haven't got a clue of what I am doing yet and I know that I am not giving enough data to really figure out what is happening but rather than banging my head against the wall I figured I would post this rambling story and maybe get a hint to lead me in the right direction ....
Thanks for reading my ramblings ....
BTW, I am running the latest version of OpenPlotter (0.11.6 ??)
My setup involves NMEA 0183 feeding to a pi3 running OpenPlotter and this data stream is distributed via wifi in the boat.
I took the signalK data, extracted the wind speed and fed that to a line graph of wind speed vs time. It was supposed to run for an hour. It started just fine (after a bit of trial and error, mostly error) but then after about 5 minutes or so no additional data reached the graph. I could still see wind speed data on the wifi feed but no data was shown on the graph.
I did some googling and found out that there was/is a crashing issues with signalK when too much data is received. I don't know if this is still the case but we are talking maybe one or two data points per second, nothing really high.
Questions:
Is signalK robust enough to use or is it still alpha level stuff?
Is this something that other people have seen and maybe solved?
The way I interpret the graphing output, it is run for x amount of time or x number of data points - is it possible to configure a continuously running graph that displays only the last x hours or x data points. In other words I could look at the last hour of wind speed data whenever I wanted to, the graph is continuousy updated but data older than x hours is dropped from the graph.
I am still having lots of issues wrapping my mind around all this stuff and quite frequently my data stream as far as signalK is concerned just breaks. I use the debug display a lot and for reasons unknown to me, data is not displayed in the debug window a lot of times. I have no idea what I am doing wrong because if I restart processes every once in a while the data starts flowing like I expect it to. At this time I have come to the conclusion that either I am flaky or SignalK and/or node red is flaky. It would be interesting to find out if it is me or if other people have issues like that.
To be clear, I really haven't got a clue of what I am doing yet and I know that I am not giving enough data to really figure out what is happening but rather than banging my head against the wall I figured I would post this rambling story and maybe get a hint to lead me in the right direction ....
Thanks for reading my ramblings ....
BTW, I am running the latest version of OpenPlotter (0.11.6 ??)