Re: [foxboro] FBM232 FDSI Configurator

  • From: "Joseph M. Riccardi" <Joe@xxxxxxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Tue, 1 May 2012 14:28:10 -0400

Folks,  

Although I am not 100% there, I did make some major progress with the help
of Mark McKinney at Premier-System.  Mark reviewed all of my configuration
parameters and *.xml files and after some minor changes without success,
Mark's conclusion was that the problem was in the communication Network
between the FBM and the PLC.  With new-found confidence I recommended we use
the test bed PLC and its Network settings and direct connect it to the Plant
FBMs.  Bingo, it worked and at least proved the FBM/ECB/XML settings have
been correct, in addition to the cables and various Network switches along
the way.  The variables that I now need to sort through are the different
Network settings and the PLC Controller/Network cards; although they are
supposed to be the same hardware/software revision levels.

My thanks to everyone that offered helpful suggestions, and especially Mark
McKinney and Dave Johnson at Premier-System for their personal involvement. 

When I finally sort out the last few obstacles, I'll update the list
database if it is anything significant.

Joseph M. Riccardi

386-441-0250 Office
386-451-7607 Cell
 
Joe@xxxxxxxxxxxxx
 
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams


-----Original Message-----
From: Joseph M. Riccardi [mailto:Joe@xxxxxxxxxxxxx] 
Sent: Friday, April 27, 2012 4:25 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: RE: [foxboro] FBM232 FDSI Configurator

Yes, I originally had the Compound name prefix the ECB name because that is
what was stated in the manual.  But...

With all of the version level and configuration issues that have surfaced, I
should mention that we also have a test bed here at the same IA System level
(Mesh V8.2 & V6.4) and it has the same hardware/software as the Plant
System.  The FBM232 and ControlLogix PLC are communicating successfully on
the test bed system.  When I could not get it all to work following the
manuals, or if they were not clear or conflicted with other manuals, I
followed the test bed system configuration guidelines.  I ended up with the
same basic configuration pattern in the Plant System as the test bed system
even though some of it does not follow the manual.  The test bed system does
not have the Compound name prefix in the PARENT parameter.  It did not make
sense to me but that one is working.

I would copy the ECBs and C:Bs over and just modify them except the PLC
database is totally different.  It may still be an option but since I have
the same basic configuration pattern I am not sure it is worth the effort.

Joseph M. Riccardi

386-441-0250 Office
386-451-7607 Cell
 
Joe@xxxxxxxxxxxxx
 
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Joseph M. Riccardi
Sent: Friday, April 27, 2012 12:01 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FBM232 FDSI Configurator

My FDSI God, my God, why hast thou forsaken me?
I appreciate the help from the list so far and I have made some progress.
But after 2 days I still cannot communicate to 2 ControlLogix PLCs; FCP270 >
FBM232 > ECB200 > ECB201 for each PLC.

I have the ECB200s communicating and on-line but I cannot get the ECB201s to
work.  As soon as I Enable Communications they fail.  Below are the ECB
listings.  Just FYI:
*       As near as I and our Elite Team of 4 can tell, we have followed all
procedures and instructions despite some confusing and conflicting
documentation.
*       My focus has been on the DEV_ID because that is where much of the
confusing and conflicting documentation exists.  It is also the Parameter on
the Select Display for the ECB201 blocks that is highlighted in red along
with the ECB Status (DEV FAIL) field.  The other fields are a variety of
greens and cyans.
*       To the best of our abilities, the variety of *.xml files have been
created and downloaded properly.  The names and details do show up in the
SMDH Equip Info displays.
*       We have tried a variety of variations of ECB parameters and we have
also tried unsuccessfully with and without a point and block configured.
*       I can ping the 2 FBM232s and the 2 PLCs.
*       In desperation I have Deleted and Undeleted everything; more than
once.  In further desperation I have even rebooted everything; more than
once.

Before I hang myself, does anyone see something wrong with the ECB
configurations, or have any suggestions?

Integrated Control Configurator
Configuration = PC5AXX
Fri Apr 27 10:43:18 2012

PC5AXX_ECB:PRIMARY_ECB

  NAME   PRIMARY_ECB
  TYPE   ECBP
  DESCRP
  NRBUS  2
  BUSOPT 3
  BUSTYP R
  PIOWDT 250
  MPOLL  7
  FIBER  0
  BADALM 0

PC5AXX_ECB:PC5A03

  NAME   PC5A03
  TYPE   ECB200
  DESCRP FBM232 LHM PLC
  PERIOD 1
  PHASE  0
  DEV_ID PC5A03
  HWTYPE 232
  SWTYPE 232
  PORTEX 1
  FILEID PC5A03.XML
  FSENAB 0
  FSDLAY 1000
  WDTMR  10
  SFILID ETHERNETIP.ZIPH
  SYSCFG 1000
  SYSOPT 0

PC5AXX_ECB:PC5A04

  NAME   PC5A04
  TYPE   ECB200
  DESCRP FBM232 TFF PLC
  PERIOD 1
  PHASE  0
  DEV_ID PC5A04
  HWTYPE 232
  SWTYPE 232
  PORTEX 1
  FILEID PC5A04.XML
  FSENAB 0
  FSDLAY 1000
  WDTMR  10
  SFILID ETHERNETIP.ZIPH
  SYSCFG 1000
  SYSOPT 0

PC5AXX_ECB:LHMX03

  NAME   LHMX03
  TYPE   ECB201
  DESCRP LHM PLC
  PERIOD 1
  PHASE  0
  DEV_ID LHMX03
  HWTYPE 232
  SWTYPE 232
  PARENT PC5A03
  DVNAME 192.168.1.115
  DVADDR
  DVOPTS EIP/CLX+SN=0
  PORTNO 1
  FILEID LHMX03.XML
  SFILID
  MANFTR
  DVTYPE
  VERNUM
  ERROPT 0xFFFE

PC5AXX_ECB:TFFX04

  NAME   TFFX04
  TYPE   ECB201
  DESCRP TFF PLC
  PERIOD 1
  PHASE  0
  DEV_ID TFFX04
  HWTYPE 232
  SWTYPE 232
  PARENT PC5A04
  DVNAME 192.168.1.105
  DVADDR
  DVOPTS EIP/CLX+SN=0
  PORTNO 1
  FILEID TFFX04.XML
  SFILID
  MANFTR
  DVTYPE
  VERNUM
  ERROPT 0xFFFE




IMPORTANT NOTICE ! This E-Mail transmission and any accompanying attachments
may contain confidential information intended only for the use of the
individual or entity named above. Any dissemination, distribution, copying
or action taken in reliance on the contents of this E-Mail by anyone other
than the intended recipient is strictly prohibited and is not intended to,
in anyway, waive privilege or confidentiality. If you have received this
E-Mail in error please immediately delete it and notify sender at the above
E-Mail address.  Agrium uses state of the art anti-virus technology on all
incoming and outgoing E-Mail. We encourage and promote the use of safe
E-Mail management practices and recommend you check this, and all other
E-Mail and attachments you receive for the presence of viruses. The sender
and Agrium accept no liability for any damage caused by a virus or otherwise
by the transmittal of this E-Mail.
 
 
_______________________________________________________________________
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
 

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

  1. Home
  2. foxboro
  3. Archive
  4. 05-2012