Ethernet/IP

[Dana]

Has anybody heard of using AutoIt to communicate with industrial devices using Ethernet/IP?  (in this case "IP" is "Industrial Protocol", not IP address.)  I have a series of scripts that currently communicate with devices with RS232 and it works well, but for various reasons we're moving toward Ethernet/IP for these systems. 

[FrancescoDiMuro]

Maybe this could help?

[Dana]

21 hours ago, FrancescoDiMuro said:

Maybe this could help?

Nothing about Ethernet/IP there except the original question.

[dmob]

On 10/5/2018 at 5:52 PM, Dana said:

Nothing about Ethernet/IP there except the original question.

I think he's pointing you to the TCP* functions?

[FrancescoDiMuro]

@dmob 
Exactly

[water]

According to Wikipedia Ethernet/IP uses UDP on layer 4. So you would need to use UDP* functions. 

[TheXman]

Actually, according to Wikipedia, it uses both TCP & UDP:

 

EtherNet/IP classifies Ethernet nodes into predefined device types with specific behaviors. Among other things, this enables:

• Transfer of basic I/O data via User Datagram Protocol (UDP)-based implicit messaging
• Uploading and downloading of parameters, setpoints, programs and recipes via TCP (i.e., explicit messaging.)
• Polled, cyclic and change-of-state monitoring via UDP.
• One-to-one (unicast), one-to-many (multicast), and one-to-all (broadcast) communication via IP.
• EtherNet/IP makes use of TCP port number 44818 for explicit messaging and UDP port number 2222 for implicit messaging