M
A couple of days ago Modbus/TCP was submitted to IETF as an Internet Draft.
You can find the RFC on the IETF web site at "http://www.ietf.org/internet-drafts/draft-dube-modbus-applproto-00.txt":http://www.ietf.org/internet-drafts/draft-dube-modbus-applproto-00.txt
I believe this is great. Modbus over Ethernet TCP/IP is already widely used in the industry: most of the industrial devices embedding Ethernet TCP/IP support Modbus among their application protocols.
Modbus/TCP covers the communication needs of a wide range of equipment.
Modbus/TCP is a very cost-effective solution in terms of memory/CPU requirement.
Modbus/TCP is also very easy to implement thus reducing development cost.
Establishing Modbus/TCP as an IETF RFC demonstrates that Modbus is now in the public domain.
I think this is great for scalability of Industrial Ethernet protocol stacks.
This could mean that Modbus/TCP will become the first universal application protocol running on every device with embedded Ethernet port?
Any comment on this?
Thanks,
Marc
You can find the RFC on the IETF web site at "http://www.ietf.org/internet-drafts/draft-dube-modbus-applproto-00.txt":http://www.ietf.org/internet-drafts/draft-dube-modbus-applproto-00.txt
I believe this is great. Modbus over Ethernet TCP/IP is already widely used in the industry: most of the industrial devices embedding Ethernet TCP/IP support Modbus among their application protocols.
Modbus/TCP covers the communication needs of a wide range of equipment.
Modbus/TCP is a very cost-effective solution in terms of memory/CPU requirement.
Modbus/TCP is also very easy to implement thus reducing development cost.
Establishing Modbus/TCP as an IETF RFC demonstrates that Modbus is now in the public domain.
I think this is great for scalability of Industrial Ethernet protocol stacks.
This could mean that Modbus/TCP will become the first universal application protocol running on every device with embedded Ethernet port?
Any comment on this?
Thanks,
Marc