Re: [foxboro] FBM224 and ProSoft modules
- From: "Joshua E. Nix" <jenix@xxxxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 20 Jan 2005 15:43:13 -0600
We are currently using the 224 to talk to PLC5, I hope to get funding in
April to remove those AB Stations and add two more.
RE# I'm assuming that I will have access to all the CP60's block set for
# processing data to/from the PLC in this method, is this correct? As
opposed
# to the somewhat limited block set that the integrator 30 supports.
Somebody correct me if I'm wrong, but the way I understand it (according to
Foxboro 's FBM 224 user guide "B0400FK Rev B" Section 5), you must use DCI
blocks. (RIN, ROUT, PAKIN, PAKOUT, BIN, BOUT etc..)
The CP talks with the FBM via the DCI blocks. Once you have been threw the
ECB and DCI blocks then you can use all blocks available on CP 60. So you
end up with a lot more blocks.
RE# Also does the ECB set up port assignments baud parity etc?
Port assignments are used in one ECB, but you will have to build a *.MSL
file with Modbus Port cfg. and then add the file to the ECB FILE_ID.
Second ECB FILE_ID will use a *.MMA file built with Modbus Device cfg. that
will define the addresses and speed of transitions. That clarifies how the
FBM talk with the device. The DCI block will have final say in the
PNT_NO about which transaction, address, and data type.
Is that correct???
****************************************************
Josh Nix
****************************************************
stan
<stanb@xxxxxxxxx> To: foxboro@xxxxxxxxxxxxx
Sent by: cc:
foxboro-bounce@fr Subject: Re: [foxboro] FBM224
and ProSoft modules
eelists.org
01/20/2005 12:55
PM
Please respond to
foxboro
On Thu, Jan 20, 2005 at 12:39:34PM -0500, Johnson, Alex (Foxboro) wrote:
> The FBM224 is a Modbus RTU Master.
>
> Throughput varies with baud rate and turn around time in the PLC.
Generally,
> that's where we see the performance hit. Seems most PLCs think they have
> more important things to do than respond to our requests.
>
Can I assume a smiley there?
In any case, yes, my hope/expectations is that the limitation will be as
follows:
1. PLC processing (see later)
2. RS-232 wire speed.
3. FBM242 processing limits.
As opposed to Gateway 30's that work out something like this:
1. GW 30 CPU
2. wire speed
3. PLC
Now, the ProSoft module will communicate with the PLC data table via block
transfers, which in turn require ladder program support. Only 1 block
transfer can be performed per I/O scan, and each block transfer is limited
to 128 (8 bit) words. I expect that there will probably need to be a
BTW/BTR pair for each data exchange.
Given all the above, I would be very curios as to anyones experience in
prototyping this, or in an actual application.
BTW, I'm assuming that I will have access to all the CP60's block set for
processing data to/from the PLC in this method, is this correct? As opposed
to the somewhat limited block set that the integrator 30 supports.
Also does the ECB set up port assignments baud parity etc?
Thanks.
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
--
Benjamin Franklin
_______________________________________________________________________
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
_______________________________________________________________________
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: