Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- From: "Imran Waheed Butt" <butt.imran@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Wed, 12 Sep 2007 11:40:03 +0500
Dear Kevin,
Sorry there there was not MG30 that is COMM15 we were using now that is
replaced by FBM231.
Thanks and Regards,
Imran
On 9/12/07, Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx> wrote:
>
> Imran,
>
> How are you using an MG30 to communicate with an AB PLC? Are you
> using a Prosoft card?
>
> Regards,
>
> Kevin FitzGerrell
>
> On 9/12/07, Imran Waheed Butt <butt.imran@xxxxxxxxx> wrote:
> > Dear All,
> > Our customer is upgrading the I/A version form V4.3 Unix to V8.2 on XP
> and
> > previous system has CP30FT communicating with 100 series FBMs and FBCs
> and
> > quantity 3 MG30 gateways communicating with Allen Bradley PLC through
> CAM or
> > Modem which is provided by Allen Bradley.
> >
> > The CP30FT is upgraded to FCP270FT and 100 series FBM and FBC are remain
> > same.
> >
> > The 3 no. MG30 are replaced by and other FCP270FT with FBM231 (FT).
> >
> > I am at the commissioning/installation of the system and facing
> following
> > problems,
> >
> > 1. FBM231 is not communicating with AB PLC through CAM or Modem as we
> > translate the same DIP switch setting which is on the P0970VN (MG30
> > configuration selection switch) to the FBM231 TA, the switch settings
> are
> > as,
> > MG30>>> SW1-1,2,3,4,7,8 & SW2-1,3,4,6,8 are closed and
> > remaining are open
> > we translate them form documents B0193RL-Rev H page 49-50 and form
> > B0700AH Rev E page 62-63 and translated switch setting are as,
> > FBM231 TA>>> A-2,4,6,8 & B-4,8 & C-1 are close and
> > remaining are open.
> > But it is not communicating with PLC.
> > 2. The cable part number which is connecting PLC to Gateway is
> > P0970WY-C and we are using the same cable.
> > 3. Previously AIN, AOUT, CIN and COUT blocks are in the database of
> > MG30 which communicate with PLC, and now these blocks we can't use
> with
> > FBM231 to communicate with PLC so, we create RIN, ROUT, BIN and BOUT
> blocks
> > and connect the out put of these blocks to the input of AIN and CIN
> and
> > output of COUT and AOUT to input of BOUT and ROUT.
> > Now problem is that the previous addressing of PNT parameter of CIN is
> > and COUT are like 4.12:0 and 16.15:0 and for AIN and AOUT have like
> > 126:0 at their PNT parameter. Kindly guide me how to translate the
> above
> > format to PNT parameter to the format of BIN,BOUT, RIN and ROUT.
> > We copy the same PNT no. to the PNT of BIN, BOUT, RIN, ROUT's PNT but
> > when loaded to FCP it gives error W65.
> >
> > Kindly all the experts provide me solution of above issues.
> >
> >
> >
> > Thanks and Best Regards,
> >
> > Imran Butt,
> >
> > System Engineer,
> >
> > Manstock.
> >
> >
>
>
> _______________________________________________________________________
> 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
>
>
--
Thanks and Best Regards,
Imran Butt
System Engineer
Manstock Engineering Company (Pvt.) Ltd.
39-42 Farid Chambers, Abdullah Haroon Road
Karachi â?? 74400, Pakistan
Cell: +92-321-2102686
Home: +92-21-4590568
Office: +92-21-5678952, 5678953, 5673145
FAX: +92-21-5682576
E-mail: butt.imran@xxxxxxxxx
URL: http://www.manstock-engg.com
_______________________________________________________________________
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
- Follow-Ups:
- Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- From: Imran Waheed Butt
- References:
- [foxboro] Communication problem b/w FBM231 & AB PLC
- From: Imran Waheed Butt
- Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- From: Imran Waheed Butt
- Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- From: Kevin Fitzgerrell
Other related posts:
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- » Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- From: Imran Waheed Butt
- [foxboro] Communication problem b/w FBM231 & AB PLC
- From: Imran Waheed Butt
- Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- From: Imran Waheed Butt
- Re: [foxboro] Communication problem b/w FBM231 & AB PLC
- From: Kevin Fitzgerrell