Re: [foxboro] Nodebus Cable B fault
- From: Kashif Ijaz <kashifijaz93@xxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Sun, 24 Feb 2008 17:52:10 +0500
I found the current Nodebus test Initiator was AW70(No control), when I changed
this to AW51F. Then the fault disappeared and the LEDs of Switch B also started
flashing.
What can be the cause. Is the AW70 not designed for being the Nodebus Initiator?
Best regards,
Kashif Ijaz
INTECH Process Automation> From: kashifijaz93@xxxxxxxxxxx> To:
foxboro@xxxxxxxxxxxxx> Subject: [foxboro] Nodebus Cable B fault> Date: Sun, 24
Feb 2008 16:10:26 +0500> > I have a system with 3 CP60's and one AW51F, one
AW51B, two WP51Fs, one AW70 (no control, just as OPC server). The system is
version 7.1.1. There are two NCNIs (redundant, one selected at Nodebus A, other
at Nodebus B) connecting to Entersys switches ( two, one for A and other for
B). But I am getting Bad Cable B fault on the Nodebus in SMDH and also there is
red "RB" at AW70.> > Could it be that AW70 is causing the problem but I think
if we use two NCNIs for both Nodebus cables A and B and then RCNIs of AW51F and
WP51Fs and AW70 are connected to both Fiber A and B from the switches.> > also
the LED flickering on the ports of Enterasys switch is slow as compared to A
switch.> > Can anyone suggest way forward to troubleshoot this.> > Regards,> >
Kashif Ijaz> INTECH Process Automation>
_________________________________________________________________> Express
yourself instantly with MSN Messenger! Download today it's FREE!>
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/> > >
_______________________________________________________________________> 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: http://www.freelists.org/list/foxboro> to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=join> to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave>
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
_______________________________________________________________________
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: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
- Follow-Ups:
- Re: [foxboro] Nodebus Cable B fault
- From: Kevin Fitzgerrell
- Re: [foxboro] Nodebus Cable B fault
- From: Kevin Fitzgerrell
- References:
- [foxboro] Peripheral Counters
- From: MClement
- Re: [foxboro] Peripheral Counters
- From: Kevin Fitzgerrell
- [foxboro] Nodebus Cable B fault
- From: Kashif Ijaz
Other related posts:
- » Re: [foxboro] Nodebus Cable B fault
- » Re: [foxboro] Nodebus Cable B fault
- » Re: [foxboro] Nodebus Cable B fault
- » Re: [foxboro] Nodebus Cable B fault
- » Re: [foxboro] Nodebus Cable B fault
- Re: [foxboro] Nodebus Cable B fault
- From: Kevin Fitzgerrell
- Re: [foxboro] Nodebus Cable B fault
- From: Kevin Fitzgerrell
- [foxboro] Peripheral Counters
- From: MClement
- Re: [foxboro] Peripheral Counters
- From: Kevin Fitzgerrell
- [foxboro] Nodebus Cable B fault
- From: Kashif Ijaz