-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LOGO! and Node-RED communications #30
Comments
I am seeing the same issue. It stays on failure state for an undetermined time. Did you get any solution to this @tsangiotis ? |
I observed the same issue with the Modbus node red module so I believe it has something to do with an underlying library. I ended up using the node red daemon module along with https://github.com/riptideio/pymodbus in a simple script. |
Hi guys, The node should always reconnect automatically. There's currently another open issue (#26) regarding a connection being kept open, that is caused by the underlying communication library. To confirm this hypothesis, could one of you please simulate the issue with the "Debug" option set to "On", and then post here the Node-RED logs of it? |
I don't have access to one now but I'll do the test in probably 3 weeks. |
I run Node-Red in a docker container. After I few times I got an error with my LOGO! connection: `[200704,681450500 192.168.178.222 S2] Address DB1,X1106.3 has value false and quality OK npm ERR! Linux 4.9.125-linuxkit npm ERR! Please include the following file with any support request: |
@gfcittolin on Debug panel, it comes only: |
Hi guys, |
We are using the 1.6.0 and also get the same error: nodered_1 | [106045,280937200 192.168.0.1 S2] ReadResponse called We could also provide wireshark logs. But for us it would be best if in case of an error this exception is catched and our system doesn't crash. |
I don't know how I missed that on the logs of @nymJ, but there's indeed another issue, not related to the connection problem we had before On the Buffer printed out, we can calculate that the last byte is missing, and that's why it drops the connection in the first place. The bigger issue then happens when we receive the missing byte in another packet, that is, a single byte telegram. The I'm opening an issue there, so we can work on a fix for it. |
@Sascha-Leadbetter could you please post here (or send me privately if you prefer) the wireshark dumps, so I can confirm that we're receiving a single-byte telegram, and then test with the fixes? |
Hi. I just tested with 1.6.0 and I still get the same error:
|
What exactly is the error you're reporting? As far as I understood, there's the first issue with the node not being able to reconnect. and another one that crashed node-red. If possible, please send the whole logs of node-red with the issue, as I unfortunately don't have a Logo here for testing. Thanks! |
Hi, my last message was regarding the first issue, with Node-Red not reconnecting. I'll repeat the test and see what other logs I can send you. Thank you! |
@gfcittolin We believe to have found a solution for this. It was actually on one dependency, nodes7, and I am not sure if this is really a bug on nodes7 for users that are not using Node-Red. We forked both repositories and you can see the fix here. We added bad quality as a condition for comm reset. For us it worked as expected. |
Is this still an issue after the improvements done on nodes7? I'm closing this issue for now since the last activity was almost one year ago, but feel free to reopen it and let me know if there's still any kind of connectivity issue. |
I get the following behavior:
I connect to a Siemens LOGO! and read some inputs without a problem.
When I disconnect the LOGO! from power and reconnect after a while, I get only "Failure (Bad values)".
The only way to go back to a working situation is to do a Full Deploy or restart my Node-RED instance.
Here is the flow:
Any ideas on how to get a stable connection?
The text was updated successfully, but these errors were encountered: