[foxboro] Additional functionality on RIN blocks

We are currently working an outage and doing the checkout as we roll 
the field wiring from 100 series I/O to 200 series I/O.  As part of 
this, we are replacing the FoxCom pucks with HART pucks.  Except for 
where they decided to go 4-20ma for the transmitters and not install 
a HART puck.  We did most of the outage work at I/A 8.2.  Yesterday 
they had upgraded the I/A to 8.4.x.   What a difference a day 
makes.  Alex was right, (that's right Alex, you were right) the RIN 
functionality is VASTLY improved.  We can alarm stuff, see the raw 
counts for debugging, and there are scaling parameters, plus overspan 
variance is settable.  I now pronounce the RIN blocks usable.  I 
still wish they would add a .PNT parameter to the RINs, come on guys, 
just copy the .MEAS parameter to a .PNT parameter it would make 
retrofits sooo much easier.  But at least it doesn't suck now.

BTW,  while looking at the block parameters, I looked at the ACHNGE 
parameter, which increment/wraps every time a parameter is changed 
with a set command.  So why are uploads so slow?  Seems you could 
read the last ACHNGE and if it hasn't changed, don't bother uploading 
the block.  That would cut down on a lot of traffic.  So think 
about.  (I offer all this valuable advice for no additional charge, 
but really guys a would it kill you to send a T-Shirt of something 
every now and then.)

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: