mpvader
commented
6 years ago Some notes on the OE npm-fetcher:
- documentation is here: https://wiki.yoctoproject.org/wiki/TipsAndTricks/NPM
- To generate, for example, a recipe to compile socketcan, run
devtool add "npm://registry.npmjs.org;name=socketcan;version=2.2.2" - To then build it, run
bitbake socketcan.
Success!
So same for mdns:
devtool add "npm://registry.npmjs.org;name=mdns;version=2.3.4"bitbake mdns- fails, missing
dns_sd.h, which makes sense, since mdns compilation requires on some libraries. Probably needs adding some DEPEND in the recipe as made by the devtool.
serialport:
devtool add "npm://registry.npmjs.org;name=serialport;version=6.1.1"bitbake serial-port- no result yet
Note that after above steps, those recipes are still in the devtool workspace. See devtool docs for how to get them in one of the metas.
tkurki
mcules
sbender9
folotp
ghost
but as long as it works and there are no horrible security related problems it is ok. "Officially" we support only 10 and will be moving on to 12, no schedule for it yet. Afaik there are no showstoppers for going to 12, I 
And then nice to haves
The short story:
Status: its ready to be tested; and perhaps its even finished enough to be just used.
How can you use it? See (draft) Venus OS Signalk manual.
Why should I use this to have Signalk? Well; that depends on what you're looking for. If you want to have all things under control; self install, for example, a raspberrypi, configure it, tweak it, modify it; maintain it; and manually install Signalk as well as keep it all update date -manually-; and either already have- or want to learn linux commandline skills, then go here, do that and forget about Venus OS + Signalk.
If you want to use Signalk as if you'd gone to the store and bought a box that should -more or less- just work; then Venus OS + Signalk is good to consider. Its intention is to be a finished (technical-)consumer type product that doesn't need any special computer skills; and especially does not require linux skills.
Where the Venus GX comes in is that its like a raspberrypi; but then in a nice box; with nice connectors; wide input power supply (9 to 70 VDC); canbus; and more. Not such a rat's nest of usb cables like Pi setups.
What about updates? Both Venus OS as well as Signalk keep improving; new versions are released regularly. I'll be regularly making a new version now of
Venus OS + Signalk; which can be installed easily: note that for now; you can only update by USB stick. Using the Firmware update menu will result in installing a normal image: without signalk. Settings; such as configured data providers; will remain in place when doing either update: going back to a normal one; or a newer one that has signalk.What about support? For support on signalk; use its Slack or mailinglist. For support on Venus OS + SignalK; preferably use the #victron channel in SignalK slack. Whatever you do; don't use official Victron support channels; they are not setup to help with this.
Are there limitations? Yes, compared to a self-installed signalk there are limitations. Especially when it comes to installing plugins. Installing plugins that need compilation is currently not possible; and also all plugins will be installed on the data partition; which has its limits when it comes to diskspace. The idea is to have all normally used plugins installed by default: so if you think something is missing; please ping me on the #victron channel on Slack.
OK, I'm convinced; where can I get this? See (draft) Venus OS Signalk manual.
The long story:
0. Introduction
See here for what Venus OS is. The idea is to either add SignalK to standard Venus as released by Victron, or otherwise at least be able to make an alternative build of Venus that includes nodejs & SignalK server.
Its current status is that I can build Venus images that include signalk for both the Venus GX hardware (has two canbus ports) and also the raspberrypy image (for rpi2 & 3) builds. There is no way to put it on the CCGX, as its flash memory is too small. For more details, see below.
This project is looking for people that have spare time. See below for how to get up to the current state of the project and start contributing :smile:.
I. Context
Getting Victron data into SignalK server is already possible, see the venus-plugin. Its common use now is to run SignalK-server one one machine (a raspberrypi most often), and then connect the Venus running on another machine (a Color Control GX, or Venus GX for example).
This project is about running it all in one piece of kit; removing the need for an additional box.
And also this project is an option to make SignalK available more easy: ie pre-installed and very easily and robustly updateable. Note that other options are also pursued elsewhere, see for example #464. And also the recent Docker work by @tkurki (tbd. is there info or a link to somewhere?).
Note that manually installing SignalK on a Venus device has been done, and is documented here.
II. The work:
1. add nodejs & npm. DONE.
2. add signalk. DONE.
3. disk space. DONE.
Adding nodejs and signalk requires quite some extra space (see somewhere below in the comments for how much). And see this overview for available space on various hardware that can run Venus. In more detail per machine (=hw model):