Re: [foxboro] FBM232 FDSI Configurator

  • From: <Bud.Kahovec@xxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Fri, 27 Apr 2012 19:56:11 +0000

With wireshark you will need the hub to connect your PC inline the hub is just 
a repeater, no msg manipulation.
Perhaps with your managed switch, you may need some routing info in the DVNAME 
xxx.xxx.x.xxx/192.168.1.115.

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

We used the A-B Stratix 6000 Ethernet Managed Switch; OK?  Wireshark is the
last item on my list to get just before the hanging...

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 Bud.Kahovec@xxxxxxxxx
Sent: Friday, April 27, 2012 3:22 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FBM232 FDSI Configurator

In the past we have used a hub (not a switch, hubs may be hard to find now
days) and an analyzer like wireshark.
It may help to see what is not working.

bud/


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Joseph M. Riccardi
Sent: April 27, 2012 10:01 AM
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 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
 


 
 
_______________________________________________________________________
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
 


 
 
_______________________________________________________________________
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