Re: [foxboro] DNBX Solution - foxboro site

  • From: "Schouten, Frits JF" <Frits.Schouten@xxxxxxxxxxxx>
  • To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
  • Date: Thu, 20 Mar 2003 07:09:17 +1100

Tom,

coming back on the FONBE's I now remember that we had a issue with them.
They are actually on the same nodebus where the DNBX had its home.
The fault we found was basically a crossover of the nodebus between two
enclosures sitting behind the FONBE's. This offcourse aggravated the issues
we had with the DNBX.
There was no real problem with the FONBE's, as we found out.

Cheers,
Frits.
BHP-NZSteel.

-----Original Message-----
From: tom.vandewater@xxxxxxxxxxxxxx
[mailto:tom.vandewater@xxxxxxxxxxxxxx]
Sent: Thursday, 20 March 2003 07:13
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] DNBX Solution - foxboro site



Brian,
        We don't have any DNBX's but have nodebus extenders, (NBE's), which
are connected to the nodebus in a similar fashion to DNBX's.  I discovered
that other users were experieincing problems on their display/work stations
using DNBX's  that sounded similar to problems we were seeing on our
display/work stations that were communicating to CP's across nodebus
extenders.  This list was the source of information about DNBX communication
problems.  
        As I said in my reply to Frits, grounding wasn't our issue with
NBE's although that was one of the first things we suspected.  Replacing
Copper/Thicknet connected NBE's with Fiber connected FONBE's made no
difference for us.  We still had the communication issues.  DNBX's are a
single module in dual nodebus cell that connects a to single workstation in
a remote location.  NBE's and/or FONBE's are used to extend the A and B
nodebus individually to another cell bus in a remote location and require
four modules A&B local and A&B remote to accomplish their task.  Symptoms
that we experienced with NBE's were extremely slow graphic call ups,  CYAN
screens caused by workstations inability to communicate with data sources
such as CP's, high frequency of hot remarries of FT modules, FT modules
going offline/non FT, and points that were marked as DELETED in AW som
object manager lists that were really good points running in a CP.  
        Our problems with Nodebus Extenders are not yet resolved but we are
making progress with Foxboro.  If Frits has no more problems with DNBX
connected stations, I assume his issue was caused  by a ground loop lssue
that the use of fiber eliminated.

Tom VandeWater
Control Systems Developer Analyst
Dow Corning Corp.
Carrollton, KY

-----Original Message-----
From: Brian Long [mailto:blong@xxxxxxx]
Sent: Tuesday, March 18, 2003 12:23 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] DNBX Solution - foxboro site



Tom / Fritz,

In your opionions was this a good solution to your problems or do you still
have issues with the DNBX's?

Brian Long
Arkansas Kraft

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of
tom.vandewater@xxxxxxxxxxxxxx
Sent: Monday, March 17, 2003 8:49 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] DNBX Solution - foxboro site



Frits,
        I really liked your ASCII ART and it came through with no problem
for me.  You are very creative.  I have a little simpler solution that can
eliminate the 5 port hub and UTP cabling that you mention.  There are many
Thinnet to Fiber Converters available that are the same form factor as the
Fiber to AUI converter that you showed in your ART.  I listed the first one
that I found on the web at:
http://www.visiostencils.com/home/visiostencils_desc.asp?selSten=LAN_Product
s.vss&manufacturer=CanogaPerkins#

Thinnet to Fiber Converter
Unique EQID: CP010
Manufacturer: CanogaPerkins
Equipment Type: Converter
Product Line LAN Products
Product Description: [8808]Thinnet to Fiber Converter

Fiber to AUI Extender
Unique EQID: CP008
Manufacturer: CanogaPerkins
Equipment Type: Extender
Product Line LAN Products
Product Description: [8805]Fiber AUI Extender

So here is another possible solution.
-----        --------------         --------       -------
| D |        | Thinnet  RX|<--------|TX    |       |     |
| N |   3m   | to Fiber   |  150m   |/     |  2m   | SUN |
| B |->thin->| Converter  |->Fibre->|Optics|->AUI->| BOX |
| X |        |          TX|-------->|RX    |       |     |
-----        --------------         --------       -------

        We looked at grounding as a source of the problems that we were
having with nodebus extenders which are similar to DNBX's.  The original
installation documents for nodebus extenders showed the thicknet shield or
jacket grounded at each end.  If the ground potential at each end of the
thicknet was different, it allowed a continuous current flow from one
building to the other across the shield of the thicknet coax.  That current
flow could induce interference/noise onto the center conducter.  If this
solution fixed your problem that is probably what was happening.  In or
case, even fiber optic nodebus extenders didn't solve the problem so we knew
that grounding wasn't our issue.

Tom VandeWater
Control Systems Developer Analyst
Dow Corning Corp.
Carrollton, KY

-----Original Message-----
From: Schouten, Frits JF [mailto:Frits.Schouten@xxxxxxxxxxxx]
Sent: Sunday, March 16, 2003 3:31 PM
To: 'blong@xxxxxxx'
Cc: Foxboro DCS Mail List (E-mail)
Subject: Re: [foxboro] DNBX Solution - foxboro site


With the wrapping of the lines I was afraid that a bit of confusion might
happen.

Okay, here we go:

>From the DNBX I run a short piece of thin coax to one of those small 5 port
hubs which has a thin net connection on the back. From one of the UTP
connections on the hub I go to a utp to fibre converter. Now we're on fibre
and go anyware we like, distance wise sort of. On the WP end I unplugged the
aui connection from the ST500 (thick to aui converter) and connected the aui
cable to the fibre converter. Circuit completed. We have lift off.

All could have been a bit simpler with a 'thick to fibre' converter near the
DNBX but we didn't have one . I'm actually not sure if they exist.

Well, that's our solution to this very nagging DNBX problem.

Cheers,
Frits Schouten.
BHP-NZSteel


-----Original Message-----
From: Brian Long [mailto:blong@xxxxxxx]
Sent: Saturday, 15 March 2003 02:44
To: Frits.Schouten@xxxxxxxxxxxx
Subject: DNBX Solution - foxboro site


Fritz,

Could you possibly go into a little more detail on your DNBX solution.  I
did not quite understand your diagram.  Thanks in advance!

Thanks,
Brian Long
E&I Superintendent
Green Bay Packaging
Arkansas Kraft Division
501-354-9205



EOM

NOTICE - This message and any attached files may contain information that is
confidential and/or subject of legal privilege intended only for use by the
intended recipient. If you are not the intended recipient or the person
responsible for delivering the message to the intended recipient, be advised
that you have received this message in error and that any dissemination,
copying or use of this message or attachment is strictly forbidden, as is
the disclosure of the information therein.  If you have received this
message in error please notify the sender immediately and delete the
message.




_______________________________________________________________________
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 email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________


_______________________________________________________________________
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 email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
 
 
_______________________________________________________________________
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
 

EOM 

NOTICE - This message and any attached files may contain information that is
confidential and/or subject of legal privilege intended only for use by the
intended recipient. If you are not the intended recipient or the person
responsible for delivering the message to the intended recipient, be advised
that you have received this message in error and that any dissemination,
copying or use of this message or attachment is strictly forbidden, as is
the disclosure of the information therein.  If you have received this
message in error please notify the sender immediately and delete the
message.


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