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

Arrange your boolean data that is to be transmitted to the I/A in
contiguous blocks of boolean memory in the Trident.  (This is fairly
standard practice for communicating data from PLC's to DCS's.)  The latest
version (V4) of Tristation software gives you plenty of flexibility in
assigning the Modbus aliases to do this.

Once you've done this you should have no problem using PAKIN blocks to
bring across 32 bits at a time.  The use of CIN's downstream is optional,
depending on what you're doing with the data.  If you want alarms, you'll
need CIN (or BLNALM) blocks.  If you're just connecting to displays or to
control logic, you could connect directly to the PAKIN's.  However, using
CIN's in all cases in order to assign a tag name to each signal is
generally beneficial.

______________________________________________________________________________________


Greg Hurwitt
Engineering Associate

E-Mail:  gregory.hurwitt@xxxxxxxx
Postal Address:
BASF Corporation
602 Copper Road
Freeport, TX 77541
USA

BASF - The Chemical Company



                                                                           
                         "Dennis                                           
                         Stone"                                            
                         <DStone@                                       To 
                         HUNTREFI         <foxboro@xxxxxxxxxxxxx>          
                         NING.com                                       cc 
                         >                                                 
                         Sent by:                                  Subject 
                         foxboro-         [foxboro] Modbus Communications  
                         bounce@f         between FBM224 and Trident SIS   
                         reelists                                          
                         .org                                              
                                                                           
                                                                           
                         06/28/20                                          
                         07 02:25                                          
                         PM                                                
                                                                           
                                                                           
                          Please                                           
                         respond                                           
                            to                                             
                         foxboro@                                          
                         freelist                                          
                          s.org                                            
                                                                           
                                                                           




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



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