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

nodbus

v1.1.7

Published

Client for ModBus Protocol written in pure JavaScript for Node.JS

Downloads

25

Readme

nodbus logo

Slave Controller for ModBus TCP Protocol. Written for Node.JS in full JavaScript

Build Status


# First steps #

## Instalation ## Once we have installed Node.JS and NPM, write in console the next command:

npm install nodbus

Declaring a simple ModBus TCP device

To start reading or writing data with NodBus just have to create a "nodbus" object for each ModBus Master that we want to connect. This example show how to connect to a ModBus master with IP 192.168.1.20, declaring two tags for read and write.

var nodbus = require("nodbus");

device = new nodbus("NameOfDevice", "TCP", {
  ip: '192.168.1.20',
  puerto: 502,
  tags: {
    TagName: {posicion: 602, tipo: 'FLOAT'},
    TagName2: {posicion: 604, tipo: 'DINT'}
  }
});

device.on("connected", function() {
  // Connected correctly to device
});

Read tags

For read tags, have to execute the corresponding function and define what tags want to read. In the example we read two tags through FC3 function (ReadMultipleRegisters). These tags were defined previously.

device.readMultipleRegisters({'TagName', 'TagName'}, function(data) {
  // Tags read correctly.
  console.log(data);
});

Or we can read all the tags defined:

device.readMultipleRegisters(function(data) {
  // Tags read correctly.
  console.log(data);
});

Writing tags

For writing tags, we have to execute the corresponding function. In this example, we use the function FC16 (WriteMultipleRegister) to write 452 in "TagName" tag.

device.writeMultipleRegisters('TagName', 452, function() {
  // Tag written correctly.
});

# Advanced configuration #

Device parameters

For each device we can configure a lot of optional parameters. For example, this is the complete defition for ModBus TCP protocol:

device = new nodbus("DeviceName", "TCP", {
  id: 1,
  ip: '192.168.1.20',
  puerto: 502,
  endian: 'LE',
  bytesPorPosicion: 2,
  tags: {
    TagName: {posicion: 602, tipo: 'FLOAT'},
    TagName2: {posicion: 604, tipo: 'DINT'}
  }
});

id is the ID of the device. This is configured in the device
ip is the IP direction
puerto is the port
endian can be defined like BE (Big Endian), LE (Little Endian), BEW (Big Endian by Word) or LEW (Little Endian by Word)
bytesPorPosicion define the amount of bytes for one position in the master device
tags configure position and data type for each tag in the device

Data types

  • BYTE 8 bits
  • INT Signed Integer of 16 bits
  • UINT Unsigned Integer of 16 bits
  • DINT Signed Integer of 32 bits
  • UDINT Unsigned Integer of 32 bits
  • FLOAT Floating Point number of 32 bits
  • DOUBLE Floating Point number of 64 bits

Alias

  • device.readMultipleRegisters FC3
  • device.writeSingleRegisters FC6
  • device.writeMultipleRegisters FC16 (limited to one register)