Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

OPC and Ethernet (2)

Status
Not open for further replies.

ICman

Industrial
Feb 28, 2003
165
This was posted in another Forum (Measurement & Control Software Engineering), but I thought I'd also ask here. This Forum seems to get more traffic. Please excuse the redundancy.
----------
I want to install a PLC network to control some compressors. I will have one PLC/compressor, with the PLCs connected together thru "Ethernet/IP" (Allen-Bradley).

The problem is that I need to pass nearly ALL of the information contained in those PLCs to a DCS (Honeywell TPS). The DCS also talks "Ethernet", but it somehow operates differently.

Both vendors talk about "OPC compliancy" and I think they should be able to pass information to each other through this, but I really don't know how it works or what has to be done to make it work. Throwing $$$ at the problem will force it on someone else, but doesn't help me or my company.

Can anyone point me to a document or something that would explain IN SIMPLE TERMS what I need to do to achieve this communication? The authors, so far, seem to be too close to their subject, and lose me really fast. Some hand-holding would be nice.

. . . Steve
 
Replies continue below

Recommended for you

It's been a long time it seems since I did any of this with Honeywell, but as I recall some thing like this.

Not sure what Honeywell TPS system you have but with Ver5 of the TDC2000 systems that ran on regular NT and above.

1. Install on the Honeywell computer RSlinx pro V2.3 Higher.
2. Configure RSLinx to the Ethernet Devices.
3. Configure Honeywell to RSLinx OPC.
4. Done

Although this did take a few days to get working.

Is the Honeywell Computer the only computer or is there others? The RSLinx can be installed on any computer connected to the network.

Make sure you have all the same Network ID's and matching Subnet Masks, in your IP that was a problem one time for us.

By the way, we found AB OK for support and took a while to reach someone at Honeywell that knew anything. Witch is the #1 reason many of my customers have removed their systems and replaced with PLC control. Perhaps if your customer has same problem talk them in to a SCADA (RSView) system.
 
Thanks. More info:

The Honeywell TPS is an updated TDC-3000. I am replacing the functions of the old Logic Manager (IPC-620) with A-B SLC5-05's. Honeywell wants $40K+ for a redundant A-B gateway. For about the same amount, we can upgrade to their new Experion PKS, which has native ControlNet and Ethernet capabilities.

We haven't had good luck with ControlNet, so we want to use Ethernet.

I have had similar experiences with A-B and Honeywell support. Like many vendors, neither is very good UNLESS they see $$$ from helping out. A-B is improving, but then, we have spent a lot of money with them lately. Nearly all of our other plants use A-B PLC-5's or SLC's with RSView.

I'll check to see if we can implement RSView on the Experion PKS server (basically a computer, right?). That may be the easiest way to go. Thanks for your help!

. . . Steve
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor