Desired Ethernet/IP feature set?

[BobO]

Assuming we were to develop an Ethernet/IP module for Do-more, what would you want it to do?

Some obvious possibilities would be:
1. Instruction-based explicit messaging
2. I/O master
3. I/O slave
4.

Sound off!

[plcnut]

I have no experience with Ethernet/IP, but am currently programming a system with 4 DataLogic image based scanners that are Ethernet/IP capable. From looking at the DataLogic documentation, the Ethernet/IP would be simple, but DMD can't do it...yet... So I am trying to set up each scanner as a MODBUS TCP slave instead, and hoping that the network will be fast enough...

All that to say: I don't know what instructions this would require, but it would be great to be able to talk to these scanners. This is my second project using them, with at least one more on my todo list.

[BobO]

Ethernet/IP shouldn't confer much of an improvement to network load over Modbus/TCP, and may actually be heavier due to added complexity.

[Controls Guy]

I/O Master.  If you do an I/O slave, I'd recommend it be a CPU-slot rack adapter like an EBC.

[davidbgtx]

Don't know much about Ethernet/IP but I'm with ControlsGuy

[odwyerpw]

OPC Client functionality..
If it could talk to devices that use imbedded OPC Servers and fetch data...