Re: [foxboro] Foxboro and Allen Bradley

Bob,=20

I think you caught many on vacation since this topic usually has many
interested subscribers willing to dive in. While I was at lunch tough I
did see Joe provided some feedback also.

The AB30 is a standard Foxboro module that can be configured redundant.
One of the ports is configured to communicate to the CAM (see modules
listed below) that converts it to DH+. The limitations are: "The Gateway
supports a maximum of 16 I/A Series Allen-Bradley Scan Blocks (ABSCAN)
to perform input/output functions with up to eight PLC controllers". I
believe these are not hard limitations but mostly throughput limitations
one should follow. This module is basically just a control processor 30
that can interface to PLCs. It only performs control functions.

The Foxboro edocs indicate the interface modules that can be used with
the the AB30 are " The Gateway interfaces to the Allen-Bradley Data
Highway using 1771-KE/KF, 1770-KF2 Series B, or 1779-KFL (in 1771-KE/KF
Emulation Mode) Communication Adapters". Note that they are all for data
highway and not direct to ENET. I looked at the information on the
1761-NET-ENI and it seems like it should work also but Rockwell has the
following note on their about this module: "Lets you connect MicroLogix
(or other products with an RS-232-C port and DF1 protocol) to an
EtherNet/IP network and initiate a single-hop message with any
EtherNet/IP device via a connected CIP message. Supports the NetLinx
services." - Note the single hop - I am not sure how your network looks.

As Joe indicated, the other options to go directly to the PLCs on
Ethernet is using either a 51 series(Solaris) or 70 series Integrator -
though these are not redundant. Basically these are either a Sun Box or
a Windows NT PC that run the Foxboro blocks inside and connect to the
PLC directly on Ethernet. I have not tried the 70 series integrator but
have used the 51 series. On these AB Interchange software is loaded and
is used to communicate to the PLCs. These also have a lot more
horsepower for blocks and your limitation is not the number of PLCs but
the throughput on the communication network and the ability of the PLC
to respond in adequate time. Since you mention the AB30 module I am
guessing you have a typical Foxboro nodebus system and not a standard
Ethernet system. You can add a second Ethernet card to these integrators
to connect them to the PLC Ethernet network and connect the first
Ethernet to a DNBT cart so that the integrator is also on your standard
Foxboro nodebus network.

Give me a call if you want to discuss further.

Rick de la Cierva
DLC SOLUTIONS CORP.
203-207-9917


-----Original Message-----
From: Marchal, Andre L. [mailto:AMarchal@xxxxxxxxxxxxxxx]=20
Sent: Friday, December 28, 2001 10:36 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] Foxboro and Allen Bradley


Bob,

I also tried to connect an INT30 to Allen Bradley 5/40E's without =3D
success.
I used an 1761-NET-ENI to do the DF1-RS232/Ethernet conversion.
I do not know what the problem was (improper wiring, protocol, etc...).
Please let me know if you find a successful method.

Bob, this is what I understand:  the INT30 for Allen Bradley can =3D
communicate
with up to 8 PLCs.  It has 2 redundant RS232 ports (that is a powerful =
=3D
and
easy to use feature).  If you want to communicate with more PLCs, you =
=3D
would
have to use one of the configured PLCs as a "mail box".

Here is what I used for my test:
INT30=3D20
SCSI cable P0500UX
Serial connector P0970VB
Ethernet interface 1761-NET-ENI (Allen Bradley)
Serial cable 1761-CBL-PM02 (Allen Bradley)

Andr=3DE9 Marchal
-----Original Message-----
From: Robert Driscoll [mailto:rdrisco@xxxxxxxxxxx]
Sent: Friday, December 28, 2001 7:55 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Foxboro and Allen Bradley



Hello List,

I am installing several Allen Bradley PLCs and I want to connect them =
=3D
to a=3D20
Foxboro system.  I know a few things about the Foxboro hardware but I =
=3D
have a

few questions.

How many PLCs can a single AB30 module be directly connected to?  The =
=3D
module

has four ports, so I assume it can go to four different PLCs?

I read the Foxboro on-line document and it discussed the RS232 =
direct=3D20
connection to a PLC, or a connection through a CAM.  My PLCs will =
be=3D20
networked together through a hub.  Is there a Foxboro way of =3D
communicating=3D20
to the PLCs via ETHERNET?  I could not find that in the
documentation.  Is it possible to connect the Fox module(s) into the =3D
hub and

have the devices talk that way?

Any other pitfalls with the AB30 (or other modules that may apply =3D
here)?

Bob Driscoll
Bravo Northwest Power Systems



_________________________________________________________________
Join the world's largest e-mail service with MSN Hotmail.=3D20
http://www.hotmail.com

=3D20
=3D20
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=20
=20
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave

 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: