Re: [foxboro] FBM232 FDSI Configurator

  • From: "Moll, Scott A." <Scott.Moll@xxxxxxxxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Fri, 27 Apr 2012 14:12:46 -0400

Joe,

I'm not familiar with the FBM232, so take what I'm about to say with a
grain of salt from another and slightly similar experience...:

On the older AB30 gateways (for Allen Bradley PLCs) we're using, the
Primary_ECB parameters look ***hauntingly familiar*** to what you
specified below for your system.

[A]  ****[Double-check this parameter...]
One exception:  the "BUSTYP" you have listed is "R".
In the AB30 documentation this is described in the book as:

"Number of consecutive message failures to a PLC before failing the
device.  DO NOT LEAVE AS "R".  Range is 1-5.  3 is recommended."   This
reflects that the manual itself has the DO NOT LEAVE AS "R" in capital
case.  Someone at Foxboro thought that was important to "yell" it in the
text...maybe you should double check your FBM232 documentation to see if
it's still highly recommended to CHANGE it to a number?

Note: from my experience, the system always initializes this BUSYTP to
"R" when you add this kind of module to the system.  Apparently it needs
to be changed.  We do use 3 as the above recommends.

[B] ****[Sometimes what's gotcha is what you can't typically see...]
The other 'gotcha' I've run in to in the past is that there is a
Hardware HEARTBEAT (for our AB30 hardware) that is specified IN THE SYS
CONFG / Commit stage.  This does NOT SHOW UP in the parameters or
PRIMARY_ECB, etc, and can apparently only be changed by doing a
correction then commit (PCHANG or etc.) for that module tweak.  I wonder
if this might be the case for you where heartbeat is turned on, but your
device you're connecting to doesn't (correctly) respond (or at all) to a
heartbeat ping from the hardware FBM232.  

For us, until I discovered this (when converting my AB-KF2 to NET_ENI
modules, which don't respond to the heartbeat), I had the same symptom
of the device (KF2 / CAM / NET_ENI) showing as failed.  The gateway was
doing some kind of initial handshake/heartbeat before it would attempt
to send data as I configured it to.   I discovered this by hooking up an
RS232 splitter (sniffer) and monitored the send and receive data
separately (to my PC using hyperterminal, of all things).  I could see a
repeating sequence from FOX doing the heartbeat and my devices stating
they didn't understand the command.  This of course required some
reading of the manuals to see what these protocols and hex values meant.

------------------------------------------
Since I don't know FBM232 modules, I'm not claiming either of these to
be your silver bullet.  I have learned a few things over the years:

1) Whenever I am (or the team is) stuck and unable to resolve an issue
we tend to find that we're really dealing with MORE THAN ONE issue at a
time which is clouding the problem and causing a delay in resolution.

2) In modification to #1 above, when dealing with communication between
systems, these systems need all settings to be EXACTLY CORRECT or
nothing works properly until that one misapplied setting is corrected.
[This makes the job even tougher]

I feel your pain.  Hope you get it resolved soon.

-Scott Moll
Scott.moll@xxxxxxxxxxxxxxx

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



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: Wednesday, April 25, 2012 8:03 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FBM232 FDSI Configurator

FDSI folks,
I am trying to create a Port, Generic Ethernet xml file for a new
FBM232.
No matter what I enter, when I try to save the configuration, I get an
error message "Exception has been thrown by the target of an
invocation".  Even if I open up an existing one and try to save it with
no changes I get the same error message.  What am I missing?

The configuration parameters are too simple to mess up, there are just
2; Select FBM Type (FBM232) and the IP Address.  Duh!

Any suggestions?  Nothing in the manual offers any help.

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



********************************************************************************************************
This email and any files transmitted with it are confidential and intended 
solely for the 
use of the individual or entity to whom they are addressed. If you are not the 
intended 
recipient or the person responsible for delivering the email to the intended 
recipient, be 
advised that you have received this email in error that any use, dissemination, 
forwarding, printing, or copying of this email is strictly prohibited.  If you 
have received 
this email in error please notify the sender immediately. Please note that we 
reserve 
the right to monitor and read any emails sent and received by the Company in 
accordance with and to the extent permitted by applicable legal rules.


*********************************************************************************************************

 
 
_______________________________________________________________________
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. 04-2012