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

plc

v0.3.0

Published

module to connect to PLCs

Downloads

17

Readme

node-plc

Node.js module to communicate with PLCs. At the moment only the Siemens LOGO! PLC (0BA7and 0BA8) is supported.

Build Status Dependency Status NPM version

Usage

npm install --save plc
var plc = require("plc");

Logo class


var myLogo = new plc.Logo("192.168.0.1", {
  markers: 6,   // default is 8
  inputs: 4,    // default is 8
  timeout: 500  // socket timeout in milliseconds
});

myLogo.on("error", function(err){
  console.error(err.message);
});

myLogo.on("connect", function(){

  var result = myLogo.getInputs();
  if (result instanceof Error){
    return console.error(result.message);
  }
  console.log(result); // [true, false, false, true, false, true]

  result = myLogo.getMarkers();
  if (result instanceof Error){
    return console.error(result.message);
  }
  console.log(result); // [true, false, true, true]

  result = myLogo.setMarker(2);
  if (result instanceof Error){
    return console.error(result.message);
  }

  myLogo.disconnect();
});

myLogo.connect();

Simulation

var plc  = require("plc");

var myVirtualLogo = new plc.Logo("192.168.0.1", { simulate: true });

myLogo.on("connect", function(){

 /**
  * Since we cannot manipulate the inputs of a real PLCs
  * there is no "setInput" method. But within the simulation
  * mode we can use the special methods "setSimulatedInput"
  * and "clearSimulatedInput".
  */

  myVirtualLogo.setSimulatedInput(2);
  myLogo.getInput(2); // true
  myVirtualLogo.clearSimulatedInput(2);
  myLogo.getInput(2); // false

 /**
  * Markers can be used as usual.
  */

  myVirtualLogo.setMarker(1);
  myVirtualLogo.getMarker(1); // true
  myVirtualLogo.clearMarker(1);
  myVirtualLogo.getMarker(1); // false

});

myVirtualLogo.connect();

Comfort features

The LOGO! can be configured with state and action schemata. A states could be described like this:

var myStates = {
  stateOne:   { input:  0 },
  stateTwo:   { marker: 2 },
  stateThree: { input:  2 }
};

An action consists of an array with defined desired states:

var actions = {
  actionOne:
    [
      { type: 'clear', marker: 1 },
      { type: 'set',   marker: 3 }
    ],
  actionTwo:
    [ { type: 'set', marker: 2 } ],
  actionThree:
    [ { type: 'alias', actions: ['actionOne','actionTwo'] } ]
};

This is a full example:

var config = {
  timeout:  500   // connection timeout
  interval: 250   // read state interval
  states: {
    x:   { input:  0 },
    y:   { input:  2 },
    foo: { marker: 0 },
    bar: { input:  1 }
  actions: {
    switchOne:
      [
        { type: 'set', marker: 3 }
      ],
    switchTwo:
      [
        { type: 'set',   marker:   1             },
        { type: 'alias', switches: ['switchOne'] }
      ]
    }
  }
};

var dev1 = new Device("192.168.0.201", config);

dev1.on("connect", function(){
  console.log("Device 1 connected");
});

dev1.on("timeout", function(){
  console.log("Device 1 connection timeout occoured");
});

dev1.on("disconnect", function(){
  console.log("Device 1 disconnected");
});

dev1.on("error", function(err){
  console.error("something went wrong: ", err.message);
});

dev.on('state-change', function(state){
  console.log(state);
  // { x: true, y: false, foo: true, bar: false }
});

dev1.connect();
dev1.startWatching();

// ...

dev1.stopWatching();
dev1.disconnect();

API

Constructor

new require("plc").Logo(ipAddress, options);

Following options are available

  • inputs - number of used inputs
  • markers - number of used markers
  • simulate - simulation mode
  • timeout - the socket timeout

Properties

  • ip
  • isConnected

Methods

  • connect()
  • disconnect()
  • setMarker(nr)
  • clearMarker(nr)
  • getMarker(nr)
  • getMarkers()
  • getInput(nr)
  • getInputs()
  • setSimulatedInput(nr)
  • clearSimulatedInput(nr)
  • getState()
  • setSimulatedState(stateName, value)
  • setVirtualState(stateName, value)
  • triggerAction(action)
  • startWatching
  • stopWatching

Events

  • error
  • connect
  • disconnect
  • timeout
  • state
  • state-change

Test

npm test

License

This project is licensed under the LGPL license.