Hello, Have started for my first project with node red: System: CentOS 7 Nodejs: 2:10.16.3 Node Red: v1.0.0 S7-1200 CPU1214C, Firmware 4.1 Have configured S7In from node-red-contrib-s7 and connected to debug in Flow. Node Parameter: Cycle: 10000 ms, Timeout: 5000 ms Get sometimes Timeout's: …

The problem is solved. After update to json-c-0.11-4.el7_0.x86_64, the error was gone. Thanks for all help and useful hints.

Have you read the "Notes on S7-1200/1500" of the s7 node ? Maybe some configuration issue...:thinking: I haven't tried the s7 node on 1200/1500 PLCs because we implemented our own TCP-based protocol for communication.

Yes, "Optimized block access" is disabled for the DB. Permit access with PUT/GET is enabled. I still getting values, read from the DB but also a lot of timeouts.

Okay, I found out, the debug error comes not from the S7. 2.10.2019, 11:08:40 node: e768e368.f8cd28 msg : string[41] "Keine Antwort, Neustart der Kommunikation" In debug window, if I select current flow, the error of the node is not visible. If I select ALL NODES the error comes back. I have onl…

Have you tried clicking on the number? It should take you to that node (provided it isn’t in a subflow)

If I filter for the node e768e368.f8cd28 I get no result, also by clicking on the node id [grafik]

Could be the config node (s7-endpoint).

I have exported the flow, in notepade I find the node ID. But I can't as a new user upload the file. So it's placed here: [{"id":"6c23acd6.00a0c4","type":"tab","label":"Flow 1","disabled":false,"info":""},{"id":"e768e368.f8cd28","type":"s7 endpoint","z":"","transport":"iso-on-tcp","address":"192.16…

Please format your shared flows properly. [image] How to share code or flow json FAQs To share code samples or flow json in this forum, you need to take care to format it properly so that it is displayed correctly. The easiest way to do that is to click the 'Preformatted…

The message "Keine Antwort, Neustart der Kommunikation" indicates that the config node re-establishes the PLC connection due to timeouts. I don't know which options the s7 node provides, but is there a configurable timeout that may be too short? Another point could be the PLC cycle time... maybe i…

The PLC has a stable cycle time of 2 ms, maximum 5 ms. I have add a DB (not optimized), in my Main OB1 I do move a value into the DB from which I read in Node red. The timout in S7 Node inside Node Red is set to 10000ms - I think long enougth. The Profinet Options have some Parameters: Keep-Alive…

Node-RED

Node-RED Forum

S7-1200 read variable

General

kuema 7 October 2019 04:53 12

The data is in fact being received every 10 seconds.

I have no other clue what is going on here, could be a problem with the S7-1200/1500 protocol.
I think you should open an issue at Github and/or contact the node's author.

Topic		Replies	Views
S7 Communication General	1	1110	15 January 2020
The node-red and PLC communication General	11	2438	31 July 2021
Creating a fetch/write request to retrieve data from a PLC Industrial	21	755	15 February 2024
S7in problem offline-connecting indefinitely Industrial	5	381	6 August 2024
Node red to S7 1214C communication error Industrial	3	3813	22 March 2021

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

S7-1200 read variable

Related topics