Re: [foxboro] Modbus gateway question

You might be looking for the functionality that a bridge multiplexor
(BMUX) provides.  We have one of these that allow the integrator 30
to talk through the BMUX to see a Modicon PLC on one ports and several
tank level daisychained on rs485  through an rs485-rs232 converver
on a second port of the BMUX (and Integrator 30 on a third port).

Mark

> I'm not sure I understand what you original question was=20
> about.  If you are
> asking can the gateway talk to more than one PLC, the answer=20
> is yes.  There
> are a number of ways to do this depending on how you connect=20
> to the PLC's.
> One person has already suggested using RS-485 which can be=20
> daisy chained to
> multiple PLC's.  The more data you poll, the longer it takes=20
> so you have to
> slow down the polling and phase the blocks.  We have=20
> Integrator 30's talking
> to multiple remote PLC's using RS-232/RS-485 converters and=20
> modems over
> leased telephone lines at 19.2K baud.  It's a bit of a kludge, and the
> polling is slow (15s range), but works pretty well.  I have=20
> not tried using
> additional ports on a gateway or integrator.
>=20
> Roger B. Smith
> Process Control Engineering
> Department of Watershed Management
> City of Atlanta
> 2440 Bolton Rd., NW
> Atlanta, GA  30318
> 404.350.4952
>=20
>  -----Original Message-----
> From:         foxboro-bounce@xxxxxxxxxxxxx=20
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Ken.E.Moore@xxxxxxxxxxx
> Sent: Wednesday, November 17, 2004 8:44 AM
> To:   foxboro@xxxxxxxxxxxxx
> Subject:      Re: [foxboro] Modbus gateway question
>=20
>=20
> This coming holiday we will be installing a new AW51F (host)=20
> to our system
> running ver 7.0,
> we will also be adding a CP60 and several of the 200 series=20
> FBM's. The rest
> of our system will
> remain at version 6.3 (3 "B" boxes).
> Is the FBM224 a viable option for us?
>=20
> thanks,
>=20
> Ken Moore
>=20
>=20
>=20
>=20
>=20
> "Johnson, Alex (Foxboro)" <ajohnson@xxxxxxxxxxx>@freelists.org on
> 11/16/2004 06:14:31 PM
>=20
> Please respond to foxboro@xxxxxxxxxxxxx
>=20
> Sent by:    foxboro-bounce@xxxxxxxxxxxxx
>=20
>=20
> To:    foxboro@xxxxxxxxxxxxx
> cc:     (bcc: Ken E Moore/US/NSC/ICI)
> Subject:    Re: [foxboro] Modbus gateway question
>=20
>=20
> Ken,
>=20
> Re: "peer-to-peer" Modbus
> I'm not aware of a 'peer-to-peer' version of Modbus. Can you=20
> tell me more
> about what you are using and the configuration? This sounds odd to me.
>=20
>=20
> Re: General use of Modbus Gateway (MDGW) and Modbus Device=20
> Integrator (MGI)
> The MDGW and MDI are both Modbus RTU masters and control the link.
>=20
> In general, one puts multiple slave devices on the link and=20
> let the one
> port
> serve them all.
>=20
> There are extra ports (4 on the CmP15/DI15 HW and 2 on the=20
> CmP30/DI30 HW),
> but they have an impact on each other. The overall performance of the
> device
> does not improve (in fact it declines) if they are used separately.
>=20
> I'm pretty sure that this is covered in the manual, but it's=20
> been a while.
> Do you need a copy?
>=20
> I don't suppose you have a CP60 at V6.5.x? If so, you could=20
> use the FBM224.
>=20
>=20
>=20
> Regards,
>=20
> Alex Johnson
> Invensys Process Systems
> Invensys Systems, Inc.
> 10707 Haddington
> Houston, TX 77043
> 713.722.2859 (voice)
> 713.722.2700 (switchboard)
> 713.932.0222 (fax)
> ajohnson@xxxxxxxxxxx
>=20
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx=20
> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Ken.E.Moore@xxxxxxxxxxx
> Sent: Tuesday, November 16, 2004 3:38 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] Modbus gateway question
>=20
>=20
> I currently have a modbus gateway that is connected to a=20
> Texas Instruments
> PLC, via peer to peer.
> Is it possible to add an additional peer to peer connection=20
> on the second
> port?
> If I upgrade to an Integrator 30 , would two peer to peer=20
> connections be
> possible?
>=20
>=20
> thanks,
>=20
> Ken Moore
> NSCC-Wdrf PLant
>=20
>=20
>=20
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>=20
>=20
> ______________________________________________________________
> _________
> This mailing list is neither sponsored nor endorsed by=20
> Invensys Process
> Systems (formerly The Foxboro Company). Use the info you=20
> obtain here at
> your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html
>=20
> foxboro mailing list:            =20
> http://www.freelists.org/list/foxboro
> to subscribe:        =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe:     =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>=20
>=20
>=20
> ______________________________________________________________
> _________
> This mailing list is neither sponsored nor endorsed by=20
> Invensys Process
> Systems (formerly The Foxboro Company). Use the info you=20
> obtain here at
> your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html
>=20
> foxboro mailing list:            =20
> http://www.freelists.org/list/foxboro
> to subscribe:        =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe:     =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>=20
>=20
>=20
> __
> This email has been scanned for Viruses and Spam.  For more=20
> information
>  please contact your local Information Security representative.
>=20
>=20
>=20
>=20
>=20
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email=20
> ______________________________________________________________________
> =20
> =20
> ______________________________________________________________
> _________
> This mailing list is neither sponsored nor endorsed by=20
> Invensys Process
> Systems (formerly The Foxboro Company). Use the info you=20
> obtain here at
> your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html
> =20
> foxboro mailing list:            =20
> http://www.freelists.org/list/foxboro
> to subscribe:        =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe:     =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
> =20
> =20
> ______________________________________________________________
> _________
> This mailing list is neither sponsored nor endorsed by=20
> Invensys Process
> Systems (formerly The Foxboro Company). Use the info you=20
> obtain here at
> your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html
> =20
> foxboro mailing list:            =20
> http://www.freelists.org/list/foxboro
> to subscribe:        =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe:     =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
>=20
 
 
_______________________________________________________________________
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

Other related posts: