Re: [foxboro] Ghost Connections - OM tool
- From: "Wingard, Robert S. (Inland)" <RWingar@xxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 6 Jun 2002 15:36:22 -0500
This may be of some help. It is straight out of the I30 documentation.
The other variant is that with the LASTGV option selected (set to 1), data
is marked bad (and out-of-service) only if the controller is failed.
Occasional but nonpersistent communications errors which prevent good data
from being obtained by the ABSCAN block are ridden through. That is, data
from the most recent successful transaction with the controller continues to
be used until errors result in the controller being marked as failed. If
LASTGV = 0, any disruption in communications, no matter how transient,
results in bad and out-of-service data.
I am not sure which version of the integrator30 you have, this came out of
the AB version documentation. If you are using an Allen Bradley PLC then
Allen Bradley has a couple of tools that you can use to monitor errors on
the processor or KTx port, number of re-tries, ack time outs etc.
Bob Wingard
Inland Paperboard and Packaging, Inc.
Orange, Texas
Voice (409) 746-7525
Pager (409) 738-1525
Fax (409) 746-7519
-----Original Message-----
From: Loupe, Rory (RJ) [mailto:RJLoupe@xxxxxxx]
Sent: Tuesday, June 04, 2002 12:54 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] Ghost Connections - OM tool
Same thing here.
Rory Loupe
Dow Chemical
-----Original Message-----
From: Brian Long [mailto:blong@xxxxxxx]
Sent: Monday, June 03, 2002 1:59 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Ghost Connections - OM tool
Corey, tell me about the smurfing issues you had with your integrator30. I
may be having similiar problems.
Thanks,
Brian Long
Green Bay Packaging
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Corey R Clingo
Sent: Monday, June 03, 2002 10:50 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Ghost Connections - OM tool
Since no one answered with anything better, try /opt/fox/bin/tools/rsom.
Enter your CP/GW type and letterbug when prompted, then use the ADR command
(don't remember the exact sequence, but I figured it out with no prior
experience with rsom) to list out all the devices (by MAC address) that
have connections to that CP/GW, and number of connections. We had 40
connections to an Integrator 30 that was causing displays to intermittently
smurf. We looked up the MAC in Sys Mgmt, but there might be better ways.
Rebooting the offending AW cleared it up.
Corey Clingo
Sr. Engineer
BASF Corp.
|---------+---------------------------->
| | "Lemieux, Tom" |
| | <TomLemieux@arive|
| | r.com> |
| | Sent by: |
| | foxboro-bounce@fr|
| | eelists.org |
| | |
| | |
| | 05/30/2002 01:46 |
| | PM |
| | Please respond to|
| | foxboro |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------
----------------------------------------------------|
|
|
| To: "Foxboro Mailing List (E-mail)"
|
| cc:
|
| Subject: [foxboro] Ghost Connections - OM tool
|
>---------------------------------------------------------------------------
----------------------------------------------------|
Ladies and Gentlemen:
We currently are having problems with ghost connections on our 12 node,
AW51B, CP30, CP10, INT30, GW15, Version 6.1.2 system. One of the people I
work with wants to use OM tool to fix these problems as they occur and has
asked me if I have the documentation for this utility. I do not but I am
sure one of you does or knows how to get it. If you would be so kind as to
help me out with this documentation and/or any known resolutions to "Ghost
Connections" I'd appreciate it. Answer on or of list will be fine.
Thanks Tom Lemieux
Alabama Pine Pulp
Po Box 100 Perdue Hill, Al 36470
Phone 334-743-8576
Fax 334-743-8295
Email Tomlemieux@xxxxxxxxxx
_______________________________________________________________________
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:
