Nodebus AW51x communicating to SLC505, PLC5E or CL is as John states the most reliable, and consistent IA offering. The primary advantage of AW70x Ethernet offering is cost as compared to Nodebus AW51x. Nodebus AW70x is about 70% the cost of Nodebus AW51x, and Mixed Node (Ethernet) AW70x is only about 30% the cost of Nodebus AW51x. For non-critical applications, the Ethernet AW70x is a very cost-effective solution. For mission critical applications, the Nodebus AW51x is clearly the way to go. Mark V. Urda Synergy Systems Inc. 528 West 5th Avenue Naperville, IL 60563 phone: 630-778-1960 fax: 630-778-7926 cell: 630-248-9382 web: www.synsysinc.com -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of John Metsker Sent: Thursday, March 28, 2002 4:47 PM To: 'foxboro@xxxxxxxxxxxxx' Subject: Re: [foxboro] AW70 Connected to AB SLC 505 PLC's. James, At General Mills we do a lot of control utilizing AW51-I's (AW51X, aka AW with control) interfacing to AB PLCs (including SLC5/05's) on nodebus or peer-to-peer Ethernet systems. It is nice to have a common, consistent solution to interface to AB PLCs over Ethernet for nodebus or Ethernet I/A systems. It is also nice to have a solution that provides exceptional scalability to address a few words in 1 PLC or thousands of words across multiple PLCs. This product is built on top of AB Interchange so it is possible to communicate to all AB Processor types including ControlLogix. To make this solution more robust as part of larger I/A installations, we try to NOT utilize any "AW" functionality on the machine and simply deploy the machine as a "AB gateway 51". So to answer your question. An AW51-Integrator talks on nodebus through a normal DNBT (or DNBI) connection and then communicates to PLCs on a dedicated control network segment through the 3rd NIC card in the Sun box. (All Foxboro Sun machines at our sites sit on a general purpose plant network segment for remote access and support.) Thanks, John Metsker General Mills, Inc -----Original Message----- From: Hyde, James [mailto:James.Hyde@xxxxxxxxxxxxxx] Sent: Thursday, March 28, 2002 3:54 PM To: 'foxboro@xxxxxxxxxxxxx' Subject: Re: [foxboro] AW70 Connected to AB SLC 505 PLC's. Will you be doing control thru Foxboro to the SLC505's? If so, I'm curious to know how they are going to talk on the node bus. Thru an Intergrator? -----Original Message----- From: John Metsker [mailto:John.Metsker@xxxxxxxxxxxx] Sent: Thursday, March 28, 2002 2:43 PM To: 'foxboro@xxxxxxxxxxxxx' Subject: Re: [foxboro] AW70 Connected to AB SLC 505 PLC's. David, The AW51-Integrator will work fine as a way to communicate to AB SLC5/05's over Ethernet. Why don't Foxboro salespeople know all of the available options within their own family of products to a given problem? John Metsker General Mills, Inc -----Original Message----- From: David Standerfer [mailto:DStander@xxxxxxxxxx] Sent: Thursday, March 28, 2002 1:18 PM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] AW70 Connected to AB SLC 505 PLC's. Is anyone out there using this approach? If so, we are wondering if you = would recommend it to us. We are being pushed by a variety of people to = use this in a non-critical installation for a material handling system = that is geographically spread out.=20 The systems integrator that will be doing the bulk of the work for us has = been told by Foxboro that this is the only approach for what we want to = do. However, we do not have any AW70's on site and aren't looking forward = to jumping on the NT bandwagon. Our preference would be to stick with an = AW51 and connect it to the PLC's via ethernet. We are worried about the = robustness of the AW70 approach and about how much work we will have to do = to port our display standards over to the NT system. Any advice is = appreciated. Dave Standerfer Agrium US Inc. Kenai, Alaska _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave