Member Login
Search
Jump to a Date
Sponsored Communities
Cool stuff
Neat Stuff

Visit our shop for nerds in control lifestyle products.
Thermal Overload
The threads that wouldn't die...
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
Fortune
I've enjoyed just about as much of this as I can stand.
RSS Feed
www.control.com/rss/
To get a personalized feed, become a member at no cost.
We will build a SCADA system using Modbus/TCP Protocol. SCADA Host (SCADA software) will be client and read data from PLC/RTUs, which are thought to be servers. However, RTU/PLCs need to communicate with each other also. So, for an RTU/PLC, is it possible to open double socket/channel (via ethernet port) one will treat as Client and the other will treat as Server? Or will we need 2 ethernet ports for this purpose?
Best Regards,
Okan Benli
Best Regards,
Okan Benli
Hello,
Sometimes nomenclature can get mixed up.
Ethernet is the media and does not care about the protocol.
I have a PC with an Ethernet port and some software that acts as a MODBUS master and connects to a device (XYZ) that acts as a MODBUS slave.
If the device (XYZ) is capable, it can act as a MODBUS master and connect to a MODBUS slave.
A device can be a master, slave or master/slave.
It would be normal for the device to allow all communications through one Ethernet connection.
The PC I am typing this on will communicate with MODBUS masters, MODBUS slaves, AB EtherNet/IP, Automation Direct, etc all at the same time.
It comes down to the software of the device. Ethernet will not be the limitation other than physical connections. (needing a hub or switch, etc)
Hope that helps.
Cheers,
Mark
www.hmisys.com
Sometimes nomenclature can get mixed up.
Ethernet is the media and does not care about the protocol.
I have a PC with an Ethernet port and some software that acts as a MODBUS master and connects to a device (XYZ) that acts as a MODBUS slave.
If the device (XYZ) is capable, it can act as a MODBUS master and connect to a MODBUS slave.
A device can be a master, slave or master/slave.
It would be normal for the device to allow all communications through one Ethernet connection.
The PC I am typing this on will communicate with MODBUS masters, MODBUS slaves, AB EtherNet/IP, Automation Direct, etc all at the same time.
It comes down to the software of the device. Ethernet will not be the limitation other than physical connections. (needing a hub or switch, etc)
Hope that helps.
Cheers,
Mark
www.hmisys.com
From Control Engineering magazine...
Related articles from Control
Engineering magazine- Free webinar on Zigbee for embedded systems
- WirelessHART compliance verification receiver available
- PTO reports high growth, cross-industry collaboration
- Wireless helps Hexion with smoke detection, control room reporting
- Wireless networks for water and wastewater plant: easy, timely info access
- Chemical company processes critical data via wireless Ethernet
- Enclosures: Improve NEMA designs, enclose wireless equipment, keep cabinets cool
- New products: Supporting wireless communications at every level
- NIWeek: National Instruments targets WiFi, Ethernet, adds LabVIEW 8.6
Above articles copyright 2008 Reed Business Information.
Subject to its Terms of Use.
Your use of this site is subject to the terms and conditions set forth under Legal Notices and the Privacy Policy. Please read those terms and conditions carefully. Subject to the rights expressly reserved to others under Legal Notices, the content of this site and the compilation thereof is © 1999-2008 Control Technology Corporation. All rights reserved.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Patronize our advertisers!




