psi-4ward / s7client Goto Github PK

View Code? Open in Web Editor NEW

43.0 5.0 17.0 2.01 MB

Hi level API for node-snap7 to communication with Siemens S7 PLCs

Home Page: https://psi-4ward.github.io/s7client/

License: MIT License

JavaScript 100.00%

nodejs siemens siemens-s7-plcs snap7 javascript node-snap7 sps plc

s7client's Introduction

S7Client

Hi-Level API for node-snap7 to communicate with Siemens S7 PCLs (See compatibility).

Promise based, async/await support
Returns javascript objects with parsed var objects
EventEmitter: (connect, disconnect, connect_error, value)
Optional auto reconnect

API Documentation

Blog post about my SIMATIC S7 Web HMI project.

Usage

npm install s7client

const {S7Client} = require('s7client');

// PLC Connection Settings
const plcSettings = {
  name: "LocalPLC",
  host: 'localhost',
  port: 9102,
  rack: 0,
  slot: 2
};

// DBA to read
let dbNr = 1;
let dbVars = [
  { type: "CHAR", start: 0 },
  { type: "BOOL", start: 2, bit: 0 },
  { type: 'INT', start: 3 }
];

let client = new S7Client(plcSettings);
client.on('error', console.error);

(async function() {
  await client.connect();

  // Read DB
  const res = await client.readDB(dbNr, dbVars);
  console.log(res);

  // Write multiple Vars
  await client.writeVars([{
    area: 'db', dbnr: 1, type: 'BOOL',
    start: 5, bit: 2,
    value: true
  }]);

  client.disconnect();
})();

Special thanks to

Davide Nardella for creating snap7
Mathias Küsel for creating node-snap7

License & copyright

S7Client: MIT
node-snap7: MIT
snap7: LGPLv3

s7client's People

Contributors

Stargazers

Watchers

Forkers

chtbof madeirajp edot92 zhangyaxu illuillu suribes diegosanz mathiask88 meckyp chrisdoernen caciuto awolf1 dciupka zxb329622888 alexrios22 hubertfeldmann

s7client's Issues

Cannot connect to Siemens Logo8

Hey there!

I was able to connect to our LOGO 8 via tools like http://www.frickelzeugs.de/logocontrol/

However via nodejs S7Client, I have no success.

This is my setup:

const { S7Client } = require('s7client')
const plcSettings = {
    name: "SLOGO8",
    host: '192.168.255.200',
    connectionCheckInterval: 20000,
    maxRetryDelay: 20000,
    alivePkgCycle: 20000,
}

const client = new S7Client(plcSettings)
client.on('error', console.error)

const start = async () => {
    await client.connect()
    // client.disconnect()
}

start()

This is my result:

(node:1597) UnhandledPromiseRejectionWarning: Error: SLOGO8:  ISO : An error occurred during recv TCP : Connection timed out    at S7Client._getErr (/mnt/c/Users/Martin Muzatko/dev/test/slogo/node_modules/s7client/src/index.js:325:12)    
    at /mnt/c/Users/Martin Muzatko/dev/test/slogo/node_modules/s7client/src/index.js:336:36
(node:1597) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1597) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

When I try to connect to another port, I get at least:

``(node:1567) UnhandledPromiseRejectionWarning: TCP : Unreachable peer`

Thank you in advance!

read error for BOOL type

readVar / readVars read BOOL vars
the read result always value: 0, the actual value is true in PLC

but readDB result is true

Can not connect to sinamics drive

The snap 7 client connects to the sinamic drives but the getCpuInfo fails.

async connect() {
...
          resolve(this.getCpuInfo().then(cpuInfo => {
            this.emit('connect', cpuInfo);
            return cpuInfo
          }));
      
  }

An in-range update of debug is breaking the build 🚨

Version 3.2.0 of debug was just published.

Branch	Build failing 🚨
Dependency	debug
Current Version	3.1.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

debug is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes

3.2.0

A long-awaited release to debug is available now: 3.2.0.

Due to the delay in release and the number of changes made (including bumping dependencies in order to mitigate vulnerabilities), it is highly recommended maintainers update to the latest package version and test thoroughly.

Minor Changes

bump vulnerable packages: 853853f
Fix nwjs support (#569): 207a6a2
add instance extends feature (#524): e43e5fe
Add TVMLKit support (#579): 02b9ea9

Patches

move to XO (closes #397): ba8a424
clean up builds: 3ca2331
remove needless command aliases in makefile: 9f4f8f5
no longer checking for BROWSER=1: 623c08e
fix tests: 57cde56
clean up makefile: 62822f1
fix tests: 833b6f8
add .editorconfig: 2d2509e
add yarn-error.log to .gitignore: 7e1d5d9
add Node.js 10, remove Node.js 4 (#583): 05b0ceb
Improve usability of Windows notes w/ examples for prompts & npm script (#577): 1ad1e4a
Drop usage of chrome.storage (or make the storage backend pluggable): 71d2aa7
Detect 'process' package: 225c66f
Update ms to 2.1.1 (#539): 22f9932
Update .npmignore (#527): a5ca7a2
fix colors with supports-color@5: 285dfe1
Document enable() (#517): ab5083f
refactor to make the common code be a setup function (#507): 7116906
Simplify and improve: da51af8

Credits

Huge thanks to @DanielRuf, @EirikBirkeland, @KyleStay, @Qix-, @abenhamdine, @alexey-pelykh, @DiegoRBaquero, @febbraro, @kwolfy, and @TooTallNate for their help!

Commits

The new version differs by 25 commits.

dec4b15 3.2.0
3ca2331 clean up builds
9f4f8f5 remove needless command aliases in makefile
623c08e no longer checking for BROWSER=1
57cde56 fix tests
62822f1 clean up makefile
833b6f8 fix tests
ba8a424 move to XO (closes #397)
2d2509e add .editorconfig
853853f bump vulnerable packages
7e1d5d9 add yarn-error.log to .gitignore
e43e5fe add instance extends feature (#524)
207a6a2 Fix nwjs support (#569)
05b0ceb add Node.js 10, remove Node.js 4 (#583)
02b9ea9 Add TVMLKit support (#579)

There are 25 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

change documentation to use lowercase slot

In the documentation, you use uppercase Slot instead of slot

Error: S7PLC: CPU : Item not available

Hi,
with this code I get the following error: Error: S7PLC: CPU : Item not available, what can I do?
I really appraciate any kind of help.

const {S7Client} = require('S7Client');

const plcSettings = {
    host: '192.168.1.15',
    port: 102,
    rack: 0,
    slot: 2
  };
   

let client = new S7Client(plcSettings);
client.on('error', console.error);

(async function() {
    await client.connect()

    const res = await cpuInfo.readVar({area:"pa", type:"BOOL", start:8, bit: 0})
    console.log(res)

    client.disconnect();
})();

{
  type: "BOOL",
  start: 0,
  bit: 0,
  value: true
},
{
  type: "BOOL",
  start: 0,
  bit: 2,
  value: false
},

Is that even supported because in datatypes, line 36 the formatter allocates a whole byte for the boolean dbVar.
Thanks in advance!