Re: [foxboro] FBM230 and DH+
- From: jrmcleish63@xxxxxxxxxxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 29 Apr 2010 20:03:44 +1000
Jack,
as far as I know you need to have a separate license for each CP and a separate
license for each FDSI that is configured for that CP, hope so because we have
purchased heaps. If you are only going to install FDSI on that particular CP
with no IO type FBM then there is a special license which covers this and is
much less expensive.
The FCP is good for 4000 the same as the ZCP and as you mentioned 2000 blocks
for the FDSI. What we have found is that it is easy have a large number of
serial data and having to use DCI blocks to interface to standard blocks makes
the problem worse. In our case all of our ex ABSTN graphics pointed to ether
MCIN or MCOUT blocks, we were unable to get graphic to look at the packed
output of the PACKIN so had to retain the MCINs. Version 8.4 has help some in
reducing this but not eliminated the DCI - Standard IA block problem.
We have now two FCPs with FDSI's only and are buying another two to do a
similar job.
We also put in 6 x 232's and directly wired to an Anybus modbus-devicenet
gateways to replace some of our ABSTN and PLC5's this has worked well.
My only gripe, and it's the old UNIX / Windoz argument is that the AB Serial
drivers don't work in UNIX we were unable to load the driver. We got round this
be configuring a dummy FDSI on a AW70, loading the FDSI then plugging it in to
the CP hosted on the SOTM machine. Not the best solution but it does work. I
still have to chase this up with Foxboro.
Regards, Rob.
_______________________________________________________________________
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:
