|
|
||
Business Industrial Network |
|||
Lean Manufacturing from MRO technical support. |
|||
|
Home - Training Services - Training Products - Articles - News - Downloads |
|
|
Services
Training Products
(No travel cost for industrial training, St. Louis.)
|
Connecting together all PLCs of different vendors in your facility.Some basic advice to help you on your research... There is more than one way to skin a cat. :>)Contents: Networks | Concentrators | Server | Additional Sources
Summary:Part of your solution is dependent on how many PLCs you have from each vendor. The first step is to get all PLCs of each vendor type on their own respective network. (IE: Mitsubishi's MelsecNet, AB's DeviceNet, Modbus, Omron's HostLink, etc.) If you only have one PLC of a particular vendor, then you might consider an SST X-Link converter for that one PLC or an Ethernet adapter card for that specific PLC, or a universal solution like Woodhead's DA Server. (Example: you have 12-Mitsubishi, 6-Omron, and only 1 I-dex. Get converter for I-dex so it can rest on Mitsubishi network or use Ethernet to run directly to your computer software.) The next step is connecting all of the networks together, via Ethernet. Depending on the details of how many of what vendors will determine other factors. Such as setting up a "data concentrator" (PLC or bridge computer) for one line or section of the plant. With only a few PLCs, you may decide to run Ethernet to each PLC and avoid the data concentrator. The third step would be deciding your method of reporting data, accessing all PLCs, etc. Step two above has to be considered while considering this step. You may use Wonderware of some other prepackaged PC software. (More info below) TOP Proprietary PLC Networks:This is the PLC vendor's way of connecting their brand of PLCs together to share information. As each PLC vendor has their own protocol, programming references, addressing, and instructions. Some vendors differ in these protocols amongst their own models. Most PLC vendors have one proprietary network that works on all models of their own PLCs. Allen Bradley has two basic networks that move can be connected to more advanced networks. (AB Micrologics interconnect via DeviceNet, DeviceNet can connect to ControleNet for example. Put it all together and it equals ControlLogix Gateway) AB's PLCs greater than mico size can connect via DH+ (Datahighway Plus). Some other PLC Networks: Alt solution - SST
X-Linx converter: Converts proprietary protocol of one PLC vendor network to
another. Put an GE PLC on a Data Highway Plus for example. (SST currently has
Ethernet drivers for PLC (programmable controller) networks including
Allen-Bradley, Modicon, Reliance, GE, Siemens. Fieldbus connectivity, I/O si) Cool Solution - Ever think you would be accessing Omron, AB, Mitsubishi, or Modbus with a Palm Pilot? TOP Data Concentrators:Data concentrator are responsible for polling the individual PLCs and presenting the data in a consistent way to the server. PLCs as data concentrators collecting data from over 100 PLCs over the proprietary comm. network supplied by the PLC manufacturer. The data concentrators PLC is then connected via Ethernet TCP over an isolated sub-LAN server. (Typically running under UNIX). Some examples we have found are using
a Siemens S7-300 PLC with a Profibus card to connect to those PLCs which
have a Profibus port. A S7-215 with a Profibus DP connection to the SCADA node
for small amount of I/Os being monitored. Siemen's Sinec H1 is yet another
choice, there are a lot of development in this area as you can see from just one
PLC vendor example. You will need a different PLC concentrator for other PLC
proprietary networks like ControlNet
or Mitsubishi's MelsecNet. The Server:The server or a workstation connected to it, is where you would access any PLC in you plant. Although we would recommend only in a read only configuration, you could link servers together for corporate wide monitoring or even condition monitoring via the Internet. The option of monitoring plant processes via the Internet is becoming quite popular. Also companies like VersaCall.com provide automated email and phone notification based on user set alarm algorithms. The software on your server to collect the data should be a commercial SCADA software like Wonderware, Kepware, FIX or Genesis (see the SCADA list). Standard DDE protocol servers, (like Wonderware or Kepware), allow the connection of any DDE aware software. These type can pass on the information to any application you have on your computer now or in the future. One suggestion was a software-based solution. If you have access to OPC servers for your PLCs, a software gateway (or bridge) can be used to move data between the PLCs. The gateway and OPC servers would run on one or more Windows-based PCs. The servers communicate with the PLCs. The gateway moves the data between the PLCs. In addition to the PLCs, data is also collected from inspection CMMs, operator input, production scheduling systems, and mainframe systems either directly through the Ethernet sub-LAN or by serial comm. through the PLCs. TOP Additional resources:PLC Training Seminar:
Check out the best selling books on SCADA and PLCs. Bus
Comparison: For Manuals and OEM resources click here. Also search these major sites... Using these key words ...
|
|
