Re: [foxboro] R: DNBI Cabling for long Distance

Corey,

Quoting Corey R Clingo <corey.clingo@xxxxxxxx>:
> We've also had NFD declare 1/2 or greater of the stations on the nodebus
> bad a few times, but no smurfing occurred, so I am concluding that this
> is bogus. Usually the G box gets very confused also, and requires a reboot.
> It is so intermittent though that we have not gotten a handle on what is
> causing it yet.

I've run into a issues with the mesh vs nodebus too.

1) We only have one V8.x workstation currently.  If there is a nodebus cable
fault, someone has to truck over to that workstation to clear the fault. 
Because we haven't had a chance to install 6.5.2 on our control stations to fix
the A station islanding issue, when we get a nodebus cable fault we sometimes
loose control stations (they stay on control, but drop off the nodebus).  It
would be nice to be able to issue a cable test from the 6.5.1 stations, or to be
able to do it from the command line of the 8.1 box via telnet, but I can't
figure out how yet.  As I get more 8.x workstations the problem will ease, but
if anyone has and idea for a more immediate solution I'm all ears!

2) We had a system monitor alarm on the mesh side.  Somebody did an ack-all on a
V6.5.1 station which acked the alarm on the mesh workstation, but all the 6.5
and 6.5.1 workstations continued to show a red system button.  Had to reboot
them all before it finally cleared.

Regards,

Kevin FitzGerrell
+64 27 460 9994

 
 
_______________________________________________________________________
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

Other related posts: