Guilherme Francescon

Sorry for the delayed response, there have been some progress regarding this issue. First of all, there was some error handling missing in the connection phase that I've now implemented,...

I've finally been able to work on this. It was a huge amount of work, not only implementing the needed bits, but also restructuring lots of things so that we...

Hey, for the `node-red-contrib-mpi-s7` issue, the problem had been already fixed on the library and a new version released, but `package-lock.json` of the node-red package had pinned the old version....

> Could it be there is an other reason this error appears? Not really. This error is about a new function I had to implement into the USB library, and...

Just saw there's a typo in my previous comment, i meant to get the `npm ls` from your Node-RED user directory and your Node-RED **installation** directory. My guess was that,...

Oh, I think you may have found it. We need `libusb` in order to have raw access the USB devices, itself needing `libudev` to work. Installing `mpi-s7` should trigger compiling...

Ok, found it. There's this package in the original usb repository called `prebuild-install`, that checks the repository for prebuilt binaries, and install them if it finds one compatible with the...

Please try the new 3.0.0 branch, among many improvements, we have new error handling code there that solves this annoying issue

Closing for now, please feel free to reopen if this still persists after upgrading to 3.0.0

I don't have much experience with S7-200, nor I have one here for testing. But some people have already done this with this node. Just make sure you use the...