Funny that you mention this.
Since we went to version 6, I have problems with an extended nodebus connection.
Several times a day, like 50-60 times a day, we are getting RA failures on a DNBX.
I've inhibited the alarms on that station but it is frustrating for the operators to
get cyan connections al the time.
We've replaced the WP, the DNBX and the thicknet terminator and it made no difference.
I've reported it to our local FOXBORO rep. and they don't seem to have an answer for
it either.
Frits.
-----Original Message-----
From: Eudilson N��ez Cossio [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 25, 2001 5:11 AM
To: 'Foxboro DCS Mail List'
Subject: Node Bus Problems
Hi list,
I looking for detailed information about how the node bus on I/A Foxboro DCS
works.
Recently we had have problems with a nodebus extended redundant (250 meters
length), the internal node bus contact inside the enclosures (slots
conectors) and conection between the enclosures too.
We solve the problems with a simple cleaning and changing a cable RG-58 (of
ten years old) by a new RG-8 for the nodebus extension for channel B, the
channel A remains with a RG-8 in good conditions. But remains a problem
with the DNBI that conects the AW51B (the system�s host) to node bus that
reports RA problem.
We change the DNBI and the system monitor was relaxed ;-). The alarms not
appear more.
But I wonder why is so important a RA failure only for a DNBI station that
compromises the entire system.
How the system use the node bus to guarantee redundancy? It is possible
that our configuration have some problems?
Thank you very much for your help, information and experiencies.
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All postings from
this list are the work of list subscribers and no warranty is made or implied as to
the accuracy of any information disseminated through this medium. By subscribing to
this list you agree to hold the list sponsor(s) blameless for any and all mishaps
which might occur due to your application of information received from this mailing
list.
To be removed from this list, send mail to [EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
EOM
NOTICE - This message contains information intended only for the use of the addressee
named above. It may also be confidential and/or privileged. If you are not the
intended recipient of this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it. If you have received this
message in error please notify [EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All postings from
this list are the work of list subscribers and no warranty is made or implied as to
the accuracy of any information disseminated through this medium. By subscribing to
this list you agree to hold the list sponsor(s) blameless for any and all mishaps
which might occur due to your application of information received from this mailing
list.
To be removed from this list, send mail to [EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
