Re: [foxboro] FDSI driver AB CSP or FDSI Driver Ethernet/IP

Hear hear!

I haven't used FDSIs, but I think this is indicative of an issue I've seen 
with Invensys numerous times in the past.  They often seem to design and 
develop in a vacuum, without feedback from the users on what they really 
want or need.  This results in answers to questions no one asked, and 
(more annoyingly) removal of features or "quirks" we have come to rely on.


Please, Invensys, I (and probably others) implore you: make it a *standard 
practice* to talk to a cross-section of users before you embark on 
development of new additions to your product line, and then listen and 
incorporate the feedback.  We will both benefit.


Corey Clingo
BASF Corp.






"Johnson, David" <David.Johnson@xxxxxxxxxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
09/30/2010 09:39 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
"foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
cc

Subject
Re: [foxboro] FDSI driver AB CSP or FDSI Driver Ethernet/IP






Hahahahahahahaha that's the sound the FDSI development team made when 
asked if they had actually looked at what the AB Integrator 30s did. We've 
been down this road more than once and the answer is ugly work around 
after ugly work around.  When someone has enough time and money we have 
rebuilt whole sections (displays, icc connections, etc.) to use the new 
FDSIs effectively.  And good luck if you had intentionally place a MCOUT 
in manual and used it as a mailbox to the PLC, that's going to be a 
re-write.


We get to do a lot of these as retrofits, and people did the most amazing 
things with the Integrator 30's quirks.  They would double read registers 
as MCINs and AINS, or read and write the same address, often in different 
compounds.  Now maybe they shouldn't have done any of that, but they did, 
and the new FDSI won't, so it's always an adventure.

I can't believe that the bit ordering, or being able to read the I:XXX and 
O:XXX registers as packed bits is too difficult to do.  It's either 
laziness, or sloppiness on the part of the development team.  I do like 
being able to use Ethernet/IP to the CLX though.

Come on Invensys, tighten up.

Regards,
David



 
 
_______________________________________________________________________
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: