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

ace-msg-parser

v1.0.10

Published

A node native add-on for Aceinna device message parser

Downloads

17

Readme

Node Aceinna Message Parser

This is a native addon to parse Aceinna device message. It helps you to split the binary data to payload by packet type. Do some decode work based on the user manual if you want to know the actual value from Aceinna device.

You need to have Node 10.5.0 or later installed.

Usage

const parsers = require("ace-msg-parser");

const allowedNMEATypes = [
    "$GPGGA", "$GNGGA", "$GPRMC", "$GNRMC", "$GPGSV",
    "$GLGSV", "$GAGSV", "$BDGSV", "$GPGSA", "$GLGSA",
    "$GAGSA", "$BDGSA", "$GPZDA", "$GNZDA", "$GPVTG",
    "$PASHR", "$GNINS",
];

const uartParser = new parsers.MessageParser({
    key: 'uart-parser-key',
    user: {
        allows: [
            0x7331, //s1, 
            0x7332, //s2, 
            0x674e, //gN,
            0x694e, //iN,
            0x6431, //d1,
            0x6432, //d2,
            0x7354, //sT,
            0x6f31, //o1,
            0x664d, //fM,
            0x7274, //rt,
            0x7350, //sP
        ],
        packetLengthType: 'uint8',
    },
    nmea: {
        allows: allowedNMEATypes
    }
});

API

MessageParser

constructor(options:Options)

Accept a options to initialize the parser.

receive(data: Buffer): ResultList

Receive some buffer data, and parse the result

Options

| Name | Data Type | Optional | Description | | - | - | - | - | | key | string | No | A unique key| | user | UserOptions | Yes| The options to parse user packet | | nmea | NMEAOptions | Yes | The options to parse NMEA packet |

UserOptions

| Name | Data Type | Optional | Description | | - | - | - | - | | allows | number[] | No | Only data with packet type in the list could be pared | | packetLengthType | string | No | The packet length type of user packet, uint8 or uint32 |

NMEAOptions

| Name | Data Type | Optional | Description | | - | - | - | - | | allows | string[] | No | Only data with NMEA type in the list could be pared |

ResultList

A list of parsed result | Name | Data Type | Optional | Description | | - | - | - | - | | packetType | number | No | The packet type. 0x6e4d is for NMEA packet | | payload | string or Buffer | No | The content of parsed packet. User packet is Buffer, and NMEA is string |