[foxboro] RE : Communication problem b/w FBM231 & AB PLC
- From: "Doucet, Terrence" <tdoucet@xxxxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 17 Sep 2007 11:14:22 -0400
Imran,
The AB Gateway (or Integrator30) limiting resource is usually the RS232 baud
rate, likely 19, 200. Each serial communication consists of overhead
(addresses, security check, etc) that do not provide information about your
process and data (your process good stuff) that all must be part of the 19,200
baud. You need to try and minimize the overhead by reading (or writing)
contiguous bytes of PLC data.
Most users get the PLC logic to move the various pieces of information in the
PLC into contiguous data areas in the PLC and then the Foxboro Integrators read
that contiguous data with the largest read that is possible.
If you just read your input data directly, most of your 19,200 baud would be
overhead. It takes a little work to map the data in and then read it out on the
Foxboro side but it is well worth the effort. At 19,200 baud you can usually
read about 350 bytes per second of your data but there are a lot of other
factors (like the number of PLC's on your DH+ network) that could lower this
350 bytes per second. Also you need to keep writes from the Foxboro to the PLC
to low numbers per second.
________________________________
De: foxboro-bounce@xxxxxxxxxxxxx de la part de Miller, Jeff
Date: ven. 2007-09-14 18:44
À: foxboro@xxxxxxxxxxxxx
Objet : Re: [foxboro] Communication problem b/w FBM231 & AB PLC
Imran,
The B3 file is located in the PLC5. You have to configure the file and
set the number of words that you will need to transfer the data. We get
the data into the B3 table by using the ladder logic to write the input
or output to the B3 bit. Example 4.8:O goes to B3:1.1 etc. I believe
you could also use a data transfer block to send several words at one
time from the input or output file to the B3 file. =20
JAM
Our system is currently using AB KF2 converters to go from DH+ to RS-232
and a Comm 15 module.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Imran Waheed Butt
Sent: Thursday, September 13, 2007 10:12 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Communication problem b/w FBM231 & AB PLC
Dear All,
The communication issue is resolved by changing the DIP switch settings
of
CAM and by putting the correct CAM address in ECB 201.
But the point numbers are we cant translate to the format of BIN or RIN
blocks we don't understand the format Like B3:4/6 the file B3 what and
where
is this file and how to translate the 4.8:0 to above format.
you can see the details in at the end of this e-mail.
Previously AIN, AOUT, CIN and COUT blocks are in the database of DI15
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.
If and one experience the same issue kindly guide me
On 9/13/07, Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx> wrote:
>
> Imran,
>
> You need to know which CAM you have. There will be an AB part number
> on the device your serial cable from the Foxboro switch block plugs in
> to. What is it?
>
> Regards,
>
> Kevin FitzGerrell
>
> On 9/12/07, Imran Waheed Butt <butt.imran@xxxxxxxxx> wrote:
> > Dear Scott,
> > I have that document and I followed that and switch setting which
you
> > provide does not work and we don't know the modem numebr but the
modem
> is
> > also of AB and AB PLC is PLC 5/40 and it is connect to CAM or Modem
by
> DH+,
> >
> > and we configured the .XML file as
> >
> > Port 1
> > Mode=3D RS-232
> > Baud Rete=3D9600
> > Parity=3D none
> > stop bits=3D1
> > databits=3D8
> > driver=3DDHPlus/CRC
> >
> > Kindly guide me.
> >
> > Thanks and Rgds
> > Imran Butt.
> >
> >
>
>
>
_______________________________________________________________________
> 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=3Djoin
> to unsubscribe: mailto:
foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>
>
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 DI15 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. DI15 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 (DI15
configuration selection switch) to the FBM231 TA, the switch settings
are
as,
DI15>>> 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
DI15 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.
=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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
-- File: winmail.dat
_______________________________________________________________________
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:
