Comments (21)
gfcittolin
commented on June 19, 2024
Hi,
could you please run lsusb -v as root/sudo and post the content here?
from node-red-contrib-s7.
deltafox1002
commented on June 19, 2024
Bus 001 Device 003: ID 0908:01fe Siemens AG SIMATIC NET PC Adapter A2
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0908 Siemens AG
idProduct 0x01fe SIMATIC NET PC Adapter A2
bcdDevice 0.02
iManufacturer 1 Siemens AG
iProduct 2 SIMATIC PC Adapter USB A2
iSerial 3 SVPL7205657
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
from node-red-contrib-s7.
deltafox1002
commented on June 19, 2024
I think, the idProduct is different. The old version has 0004 and the new version has 01fe. I have already change the udev rule to the new id. But maybe it must be change in the mpi-s7 lib
from node-red-contrib-s7.
gfcittolin
commented on June 19, 2024
Exactly. The mpi-s7 library searches for USB devices by their vendor and product ID. Maybe you can try manually changing it there and check if it works. My only concern is whether this newer version implements the same protocol or not
from node-red-contrib-s7.
gfcittolin
commented on June 19, 2024
The file you'd have to change is mpi-s7/src/nodes7.js. There's a constant "MPI_USB_PID" there on line 42 that you can try putting the other product ID. Let me know the result of that, then maybe we can add as a second possible check
from node-red-contrib-s7.
deltafox1002
commented on June 19, 2024
Hi. unfortunately that does not work. I get this error in Node-RED
"Error connecting to PLC: TypeError: Cannot read property 'on' of undefined"
from node-red-contrib-s7.
gfcittolin
commented on June 19, 2024
Is there any stack trace following this message?
Maybe we can try getting more info by running node-red like the following:
NODE_DEBUG=mpi-s7 path/to/your/node-red -v
This will make the mpi-s7 print a lot of debug info on the console. Could you eventually run your node-red instance like this and post the result?
from node-red-contrib-s7.
deltafox1002
commented on June 19, 2024
[10 Oct 14:45:53 - [info] Starting flows
MPI-S7 2600: create PPPParser
MPI-S7 2600: create PPPSerializer
MPI-S7 2600: create PPPSocket
MPI-S7 2600: create MPIAdapter
10 Oct 14:45:53 - [info] Started flows
10 Oct 14:45:53 - [info] [s7 endpoint:S7-300] Initiating connection to PLC
[153,990063708] Initiate Called - Connecting to PLC with address and parameters:
[153,990129697] { mpiAddress: 2, selfMpiAddress: 0 }
[153,991282392] Connect NOW
[153,991412345] Connection cleanup is happening
[153,991516902] Clearing read PacketTimeouts
[153,991585402] Clearing write PacketTimeouts
MPI-S7 2600: new MPIAdapter
MPI-S7 2600: new PPPSocket
MPI-S7 2600: new PPPParser
MPI-S7 2600: new PPPSerializer
MPI-S7 2600: new MPIParser
MPI-S7 2600: new MPISerializer
MPI-S7 2600: MPIAdapter open
MPI-S7 2600: PPPSocket open
[153,994256791] <initiating a new connection Thu Oct 10 2019 14:45:53 GMT+0200 (CEST)>
[153,994309355] Attempting to connect to host...
[153,994721234] ConnectionReset is happening
[153,995132387] We Caught a connect error TypeError: Cannot read property 'on' of undefined
10 Oct 14:45:53 - [error] [s7 endpoint:S7-300] Error connecting to PLC: TypeError: Cannot read property 'on' of undefined
MPI-S7 2600: MPIAdapter close
MPI-S7 2600: MPIAdapter close not-connected
[155,499765730] ResetNOW is happening
[155,500238626] Clearing an earlier scheduled reset
[155,500902944] mpiAdapter closed
10 Oct 14:45:58 - [info] [s7 endpoint:S7-300] Closing connection to PLC]
from node-red-contrib-s7.
gfcittolin
commented on June 19, 2024
Looks like the adapter's interface is different from all adapters we have here (and therefore the code is prepared to handle). The code expects a device configuration layout that does not match with your adapter's one while initializing the USB device, so the endpoint is left undefined, and we get this error.
Unfortunately I'd say we can't support your adapter right now, as it looks like it will require more work on the library side, and we don't have an adapter like yours here for development and testing.
from node-red-contrib-s7.
deltafox1002
commented on June 19, 2024
Hi. I've tried it with the old version adapter but i get the same error. I roll back all changings, udev and nodes7.js to id 0004 and restart the system.
btw, i run the linux machine in virtualbox 6. Maybe this is a problem.
from node-red-contrib-s7.
gfcittolin
commented on June 19, 2024
I think VirtualBox shouldn't be a problem. Is the lscpi -v of the old one also the same? (or could you post it too?)
We expect a device with ID ID 0908:01fe, one interface at 0, and, two endpoints on 0x02 and 0x82. If it differs from it, we can try figuring out what to do to make it compatible, assuming the protocol they talk is the same.
from node-red-contrib-s7.
deltafox1002
commented on June 19, 2024
Hi
i think you mean lsusb -v and not lspci -v
this is the output from the old version Adapter (6ES7 972-0CB20-0XA0)
Bus 001 Device 003: ID 0908:0004 Siemens AG
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 49
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0908 Siemens AG
idProduct 0x0004
bcdDevice 0.10
iManufacturer 1 SIEMENS AG
iProduct 2 SIMATIC PC Adapter USB
iSerial 3 6ES7 972-0CB20-0XA0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 PC Adapter II
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 0 (Defined at Interface level)
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 5 S7
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0001
Self Powered
and this is the output from the new version (6GK1 571-0BA00-0AA0)
Bus 001 Device 006: ID 0908:01fe Siemens AG SIMATIC NET PC Adapter A2
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0908 Siemens AG
idProduct 0x01fe SIMATIC NET PC Adapter A2
bcdDevice 0.02
iManufacturer 1 Siemens AG
iProduct 2 SIMATIC PC Adapter USB A2
iSerial 3 SVPL7205657
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
You write something about two endpoints. But I can see only one endpoint.
from node-red-contrib-s7.
deltafox1002
commented on June 19, 2024
I was wrong. There are two endpoint :-)
from node-red-contrib-s7.
gfcittolin
commented on June 19, 2024
Just for the reference, here's what the output of my lspcilsusb says:
Bus 003 Device 009: ID 0908:0004 Siemens AG
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 32
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0908 Siemens AG
idProduct 0x0004
bcdDevice 0.10
iManufacturer 1 SIEMENS AG
iProduct 2 SIMATIC PC Adapter USB
iSerial 3 6ES7 972-0CB20-0XA0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 PC Adapter II
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 0 (Defined at Interface level)
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 5 S7
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Device Status: 0x0000
(Bus Powered)
Note that the enpoint addresses are different (0x02, 0x82 vs 0x01, 0x82), but everything else seems to be the same. As there's always only 2 endpoints, I can try dynamically determining the endpoints based on their direction instead of their addresses.
As a test, would you mind changing the hardcoded addresses, so we can check if this is going to work? The file to be changed is mpi-s7/src/ppp-usb/pppSocket.js, on lines 18 and 19 there are the USB_ENDPOINT_IN and USB_ENDPOINT_OUT constants, you can try changing them according to what lsusb tells you.
from node-red-contrib-s7.
deltafox1002
commented on June 19, 2024
I tried your suggestion but this did not work, too. There are more difference at the same adapters. The right one is yours.
from node-red-contrib-s7.
deltafox1002
commented on June 19, 2024
Hi there. Now it's running. It seems that my virtual OS is corrupted. I try it with a fresh debian 10 installation and all worked fine with the old version adapter.
from node-red-contrib-s7.
gfcittolin
commented on June 19, 2024
Oh nice. Have you had to change the endpoint numbers as above? What about the newer version?
from node-red-contrib-s7.
deltafox1002
commented on June 19, 2024
Hi. The connection with the new version adapter can not be established.
21 Oct 10:00:54 - [info] Flows starten
MPI-S7 1832: create PPPParser
MPI-S7 1832: create PPPSerializer
MPI-S7 1832: create PPPSocket
MPI-S7 1832: create MPIAdapter
21 Oct 10:00:54 - [info] Flows gestartet
21 Oct 10:00:54 - [info] [s7 endpoint:2ff1e2a5.2f79b6] Initialisiere Verbindung zur SPS
[290,767786173] Initiate Called - Connecting to PLC with address and parameters:
[290,767910066] { mpiAddress: 2, selfMpiAddress: 0 }
[290,769631526] Connect NOW
[290,769771501] Connection cleanup is happening
[290,769859360] Clearing read PacketTimeouts
[290,769935104] Clearing write PacketTimeouts
MPI-S7 1832: new MPIAdapter
MPI-S7 1832: new PPPSocket
MPI-S7 1832: new PPPParser
MPI-S7 1832: new PPPSerializer
MPI-S7 1832: new MPIParser
MPI-S7 1832: new MPISerializer
MPI-S7 1832: MPIAdapter open
MPI-S7 1832: PPPSocket open
MPI-S7 1832: PPPSocket _onOpen
MPI-S7 1832: PPPSerializer _transform
MPI-S7 1832: PPPSerializer serialize { seqId: 252 }
MPI-S7 1832: PPPSerializer serialize result <Buffer 7e fc 9b cd 7e>
MPI-S7 1832: PPPSocket _writeUsb <Buffer 7e fc 9b cd 7e>
[290,776301435] <initiating a new connection Mon Oct 21 2019 10:00:54 GMT+0200 (GMT+02:00)>
[290,776420189] Attempting to connect to host...
from node-red-contrib-s7.
edilson
commented on June 19, 2024
Hi guys, i'm having the same issue with the old version. The error that i get is LIBUSB_ERROR_ACCESS
from node-red-contrib-s7.
gfcittolin
commented on June 19, 2024
@Sedilson please check out whether you've correctly setup your environment according to the instructions on mpi-s7's Readme
from node-red-contrib-s7.
gfcittolin
commented on June 19, 2024
@deltafox1002 I'm closing this issue for now, and I'm documenting that we currently support only the "old" version of the adapter on the original "mpi-s7" repository. Thanks for your contribution
from node-red-contrib-s7.
Related Issues (20)
- Trigger Read specific adress (S7 Control Node)
- s7-Out, send a Boolean "false" HOT 1
- checkbox for suppressing "Error: connect EHOSTUNREACH" in debug sidebar of NodeRed HOT 10
- ECONNRESET WITH S7-1200 AND S7-1500 HOT 3
- In and out nodes are in-resposive after timeout on http-request HOT 2
- Installation error Node red in Home Assistant. HOT 2
- Invalid properties S7 endpoint with nodered V3.0.2 Node.js 18.14.0 -Windows 10 HOT 14
- S7 out node invalid -endpoint properties
- I am not able to read LREAL HOT 3
- Connecting to S7 300 over NAT not possible
- different behaviour on identical PLCS
- wont work with Simatic RTX
- Dynamic configuration (address, port) change
- Connecting to plc through internet HOT 1
- Error writing arrays
- NAQ doesnt work?
- Persistent variables HOT 3
- Not able to read LREAL
- Symbolic Access (optimized block access)
- S7-in node in connecting status but not connecting
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-red-contrib-s7.