Re: [foxboro] Modbus Communications between FBM224 and Trident SIS

I don't have a Tricon, but we did exactly this with a Hima SIS PLC.  We 
just set the PAKIN block up to point to a transaction that issued Modbus 
"read coil" function codes; the bits were configured as bits in the Hima 
(i.e., not packed into an integer).

Corey Clingo
BASF Corporation






"Dennis Stone" <DStone@xxxxxxxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
06/28/2007 02:25 PM
Please respond to
foxboro@xxxxxxxxxxxxx


To
<foxboro@xxxxxxxxxxxxx>
cc

Subject
[foxboro] Modbus Communications between FBM224 and Trident SIS





Afternoon,


We recently installed and commissioned our first and second SIS
(Trident) system at our refinery.  The engineering/integration firm
hired for the project implemented communications between the I/A and the
Trident using MODBUS and 100's of IIN blocks tied to CIN's for display
and alarming.  My question is whether anyone has implemented MODBUS to a
Trident using a PAKIN block and then linking to CIN's for diplay and
alarming.  Our current setup puts a tremendous load on our CP  because
each status (single bit) is being represented/transmitted as an integer
value, causing overruns every 15 seconds.  I tried a test using a 32 bit
packed interger value from the trident and bringing that into a PAKIN
block but it doesn't appear that the PAKIN can decode the integer into a
32 binary word.  Any suggestions???



Any feedback is greatly appreciated.



Dennis Stone

Process Control Engineer

Hunt Refining Company

dstone@xxxxxxxxxxxxxxxx <mailto:dstone@xxxxxxxxxxxxxxxx>

(205) 391-3303

(205) 391-3564 FAX



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