As you know we are working hard on OpenPlotter 1.x.x
It would be great to add a defaults file with some samples of parsing signal k data. Any volunteer?
I would share my node red code, it is not very professional, but uses a lot of features . May be it would be good to have a look on it before giving it to so else.
Can you PN me your mail adress?
Currently I'm quite busy but you can contact me if you need help regarding JS, HTML or CSS.
Right now I'm not running Openplotter but nodered is working on my home server.
Hi all, sorry for the delay. We are getting closer to the new release and we would really appreciate a default flow to be included. We are focussed on other parts and you guy know more node-red than us.
Alpenskipper, could you prepare a basic version with standard features? I mean some dashboard with standard sailing data (position, course, speed...), and some example of parsing signal k data...
My node red installation includes a lot of examples for sensors, dashboard, switches, seatalk ng import ... wich all basicaly work, but it is programed very lousy and therefore not a version that can be published.
Maybe s.o. more experienced can have a look on it before.
Where can I send the code via mail?
I am not a node-red expert at all but I will try. Send it to info(youknowwhat)sailoog.com
I recently gave up on node-red because of stability issues. It would run fine then go bonkers and then eat resources. even when run from Laptop. Concept awesome but unless it can fix memory cpu issues i can not use it.
(2018-06-07, 01:09 PM)ddelorme Wrote: [ -> ]I recently gave up on node-red because of stability issues. It would run fine then go bonkers and then eat resources. even when run from Laptop. Concept awesome but unless it can fix memory cpu issues i can not use it.
you probably have a node thats doing that.
the arduino node & serial node has caused problems for me at times. it would lock up and become unusable.
(2018-06-07, 01:09 PM)ddelorme Wrote: [ -> ]I recently gave up on node-red because of stability issues. It would run fine then go bonkers and then eat resources. even when run from Laptop. Concept awesome but unless it can fix memory cpu issues i can not use it.
Something sounds wrong there... I've been running it 24h a day for nearly a year with no problems, publishing a dashboard and recording signalk data to a data base. Very stable and using little resources -
Interesting I am sure it was a bad node. I will try again it is a nice tool. samples would be nice