npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

signalk-generic-pgn-parser

v1.4.0

Published

Allows users to parse PGNs that are not directly supported by SignalK.

Downloads

63

Readme

signalk-generic-pgn-parser

Allows users to parse PGNs that are not directly supported by SignalK.

Getting started

1.) Use the SignalK Appstore to install the signalk-generic-pgn-parser plugin. 2.) Browse to Server => Plugin => Generic PGN Parser and enable it. 3.) Restart SignalK

Configuration - Basic

At the basic level each PGN is required to have the PGN and the path you want to map it. The path is a template that you can specify any data field value or device instance for use in the path. The field value you want to use in the template should be surrounded by {} brackets.

For example if I want to include the instance in the PGN 65005, then I could use a path of electrical.ac.utility.{Instance}.total

Basic Configuration

Configuration - Proprietary

If the PGN you wish to use is proprietary to a manufacturer, then you need to provide the manufacturer name as used in pgn.h.

If I wanted to add Maretron Slave Response PGN 126720, I would go to pgn.h and search for the PGN. Within the PGN I would look for the Manufacturer Code and enter it into the PGN config in the plugin.

Manufacturer Code

Configuration - Advanced

Some PGNs may have additional data that we do not want to import or may be used for source identification in the path.

Advanced - Single Field

You may also specify multiple fields using a comma seperated list.

Advanced - Multiple Fields