Re: [foxboro] FBM230 Communication with AB PLC5 over DH+
- From: Ali Ahmed Zahidi <alizahidi@xxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Sat, 17 May 2008 10:28:00 +0000
Thank you for all who shared knowledge and experiece to solve our problem. We
got our problem solved last week.
The problem was with the CAM (AB 1770 KF2) device address. Our CAM device
address was 020 (octal). The Foxboro I/A Series has
some conflict with this address. When we changed the address to 030 it started
data exchange with AB PLC5.
Rgds,
Ali Ahmed Zahidi
> Date: Tue, 13 May 2008 11:55:28 +0500> From: butt.imran@xxxxxxxxx> To:
> foxboro@xxxxxxxxxxxxx> Subject: Re: [foxboro] FBM230 Communication with AB
> PLC5 over DH+> > Dear Sir,> I have received the same problem, kindly confirm
> that integer register> address is correct. In our case we have address like
> N100:0 (16Bit Unsigned> Integer for digital).> Check the PLC data addressing
> format.> > Thanks and Best Regards,> Imran Waheed Butt> > On 5/12/08, Ali
> Ahmed Zahidi <alizahidi@xxxxxxxxxxx> wrote:> >> > Hi list,> > I am working on
> integration of Allen Bradley PLC5 with Foxboro I/A version> > 8.3 over AB DH+
> protocol. I have installed an FBM230 with FCP270 and> > configured ECB200 and
> EC201 as parent and child ECB. I am using AB 1770 KF2> > interface unit
> between PLC5 and Foxboro I/A FBM230. Port-1 of FBM230 is used> > for serial
> communication. For parent and child ECBs I first configured> > ECB200 and
> then and ECB201 for CAM and then an ECB201 for PLC5. The> > communication
> between the PLC5 and FBM230 via 1770 KF2 has been established> > and I can
> see the CAM and PLC5 online on SMDH. I have configured a DCI block> > PAKIN
> to read PLC5 integer register e.g. N23:26/S2 (S2 is used to read 16> > bit
> signed integer) and made proper connection to iom_id parameter e.g.> >
> 04CP01_ECB:WTP_01 (where WTP_01) is ECB201 for PLC5 but I am unable to get> >
> data from PLC5. As seen in block detail display, all data bits in the DCI> >
> block are in cyan color means no data is not being retrieved from PLC5. I> >
> also checked PLC5 configuration> > for data read/write previliges and found
> to be configured as Read/Write.> > Do anyone have any idea of the problem?>
> >> > Rgds,> > Ali Ahmed Zahidi> >> >
> _________________________________________________________________> >> >
> Discover and Win with Live Search> >> >
> http://clk.atdmt.com/UKM/go/msnnkmgl0010000007ukm/direct/01/> >> >> >
> _______________________________________________________________________> >
> 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: //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: //www.freelists.org/list/foxboro> to subscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=join> to unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave>
_________________________________________________________________
All new Live Search at Live.com
http://clk.atdmt.com/UKM/go/msnnkmgl0010000006ukm/direct/01/
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
