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

@mrcamilletti/node-red-contrib-serial-modbus-api

v1.1.1

Published

serial-modbus Server and API implemented for NodeRED

Downloads

15

Readme

Serial Modbus API Server for NodeRED

npm version

Installation:

Requires NodeRED installed, check here.

$ cd ~/.node-red
$ npm i @mrcamilletti/node-red-contrib-serial-modbus-api

Modbus request node

Modbus Server: Select configuration node (required) msg.topic: Select option to change message topic. Default: Keep Retries: Number of retries in case of timeout.

Modbus Server configuration node

Port: Serial device location. i.e.: /dev/ttyUSB0 Settings: : Baud rate, data bits, parity check and stop bits. Timeout: Response timeout from device request. Value in milliseconds. Interval: Sleep time between transactions. Value in milliseconds. Queue capacity: Máximum number of transactions in the queue.

Access to single and multiple devices through node

Payload format for reading:

{ 
    "id": <number> | <Array>,
    "read" : <string> "coil" | "input" | "holding" | "discrete",
    "addr": <number>,
    "quantity": <number>
}
{ 
    "id": <number> | <Array>,
    "read" : <string> "coil" | "input" | "holding" | "discrete",
    "from": <number>,
    "to": <number>
}

Payload format for writting:

{ 
    "id": <number> | <Array>,
    "write": <string> "coil" | "holding",
    "addr": <number>,
    "value": <Array>
}

Read Coils from single device using address and quantity:

msg.payload = {
    id: 1,
    read: "coil",
    addr: 0,
    quantity: 5
}

Read Coils from single device using from and to:

msg.payload = {
    id: 2,
    read: "coil",
    from: 1,
    to: 2
}

Read Inputs and Holdings from single device:

msg.payload = {
    id: 1,
    read: "input",
    from: 0,
    to: 1
}
msg.payload = {
    id: 2,
    read: "holding",
    from: 0,
    to: 1
}

Write Coils and Holdings to device 1:

msg.payload = {
    id: 1,
    write: "holding",
    addr: 0,
    value: [1,2,3,4]
}
msg.payload = {
    id: 1,
    write: "coil",
    addr: 0,
    value: [1,0,1,0]
}

Read and Write Coils and Holdings to multiple devices:

msg.payload = {
    id: [1,2,5],
    write: "coil",
    addr: 0,
    value: [1,1,1,1]
}
msg.payload = {
    id: [1,2,5],
    read: "coil",
    addr: 0,
    quantity: 4
}

Check responses from results and error objects

Transaction success (first output)

msg.payload = {
    ...
    result: {
        "data":[ ... ],
        "buffer":[ ... ]
    }
}

Transaction error (second output)

msg.payload = {
    ...
    error: {
        "name": "...",
        "message": "...",
        "errno": "..."
    }
}

Add number of retries

In case of timeout error, the message can be pushed back to the queue a number of times specified by payload.retries

msg.payload = {
    ...
    retries: 5
}