hello every body
i am a student in electrical ingineering
i try to build my first communication between my PLC S7 1211C and node-red via the PLC module and after i configure my first node i will have these probleme 
3 May 16:44:04 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
3 May 16:44:19 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
3 May 16:44:34 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
3 May 16:44:49 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
3 May 16:45:04 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
3 May 16:45:19 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
3 May 16:45:34 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
3 May 16:45:49 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
3 May 16:46:04 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
3 May 16:46:19 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
3 May 16:46:34 - [error] [s7 endpoint:jneafea] Error: Timeout connecting to the transport
i dont know whats the real reason of the probleme, please help if you can and i will be grateful to you.
Can you ping the PLC from the machine running node-red?
hello machadotiago , thank you very much for your reaction
whene i ping the PLC from the machine running node-red i have this message:
C: \ Users \ Admin> ping 192.168.0.3
Sending a 192.168.0.3 'Ping' request with 32 bytes of data:
Timeout exceeded the demand.
Response from 192.168.0.158: Unable to reach the destination host.
Timeout exceeded the demand.
Response from 192.168.0.158: Unable to reach the destination host.
Ping statistics for 192.168.0.3:
Packages: sent = 4, received = 2, lost = 2 (50% loss),
my PLC IP Adress is 192.168.0.3:
thank you a seconde time for your help.
i am sorry for my bad english because i am from a French-speaking country.
This means that you don't have connection with the PLC, the problem is not with the node, but with your connections.
You should be able to ping the PLC before trying to communicate with it.
Are you sure you are using a network with fixed IPs?
No I thank taht i dont use a fixed IPs? shall I do?
If you are using DHCP, are you sure that the IP of the PLC is correct?
Hello,
I have the same error, nevertheless the ping is allright. What else could it be?
root@iot2050-debian:~# ping 192.168.200.4
PING 192.168.200.4 (192.168.200.4) 56(84) bytes of data.
64 bytes from 192.168.200.4: icmp_seq=1 ttl=128 time=0.509 ms
64 bytes from 192.168.200.4: icmp_seq=2 ttl=128 time=0.424 ms
64 bytes from 192.168.200.4: icmp_seq=3 ttl=128 time=0.566 ms
64 bytes from 192.168.200.4: icmp_seq=4 ttl=128 time=0.969 ms
64 bytes from 192.168.200.4: icmp_seq=5 ttl=128 time=1.15 ms
^C
--- 192.168.200.4 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 66ms
rtt min/avg/max/mdev = 0.424/0.723/1.149/0.284 ms
Do you mean exactly the same error message as shown in the first post?
I got the error in the S7 Node.
C:\Users\JAVI>node-red
31 May 16:40:18 - [info]
Welcome to Node-RED
31 May 16:40:18 - [info] Node-RED version: v1.3.4
31 May 16:40:18 - [info] Node.js version: v14.16.1
31 May 16:40:18 - [info] Windows_NT 10.0.19041 x64 LE
31 May 16:40:19 - [info] Loading palette nodes
31 May 16:40:20 - [info] Dashboard version 2.29.0 started at /ui
31 May 16:40:20 - [info] Settings file : C:\Users\JAVI.node-red\settings.js
31 May 16:40:20 - [info] Context store : 'default' [module=memory]
31 May 16:40:20 - [info] User directory : \Users\JAVI.node-red
31 May 16:40:20 - [info] Projects directory: C:\Users\JAVI.node-red\projects
31 May 16:40:20 - [info] Server now running at http://127.0.0.1:1880/
31 May 16:40:21 - [info] Active project : Node-Red
31 May 16:40:21 - [info] Flows file : C:\Users\JAVI.node-red\projects\Node-Red\flows.json
31 May 16:40:21 - [info] Starting flows
31 May 16:40:21 - [info] Started flows
31 May 16:40:31 - [error] [s7 endpoint:d23569b.3092d98] Error: Timeout connecting to the transport
31 May 16:40:46 - [error] [s7 endpoint:d23569b.3092d98] Error: Timeout connecting to the transport
31 May 16:41:01 - [error] [s7 endpoint:d23569b.3092d98] Error: Timeout connecting to the transport
31 May 16:41:16 - [error] [s7 endpoint:d23569b.3092d98] Error: Timeout connecting to the transport
31 May 16:41:31 - [error] [s7 endpoint:d23569b.3092d98] Error: Timeout connecting to the transport
31 May 16:41:46 - [error] [s7 endpoint:d23569b.3092d98] Error: Timeout connecting to the transport
31 May 16:42:01 - [error] [s7 endpoint:d23569b.3092d98] Error: Timeout connecting to the transport
It is probably worth raising an issue against the node on it's github page, assuming it has one, since no-one here seems to have any suggestions.
Did you configured the Rack, Slot correctly? Have you also enabled the put and get on your PLC?
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
