Re: [foxboro] Relocating Workstations
- From: "Matic.Hank" <Hank.Matic@xxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 4 Jan 2005 14:49:12 -0600
Did you reboot the DNBI?=20
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Jones, Charles R. (Chuck)
Sent: Tuesday, January 04, 2005 2:21 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: [foxboro] Relocating Workstations
Greetings All,
I have a situation for which I have not yet found a solution. I had to
swap the locations of two machines within the same control room. There
are five workstations on the local node. The AP is in the same room.
All six are 51 series machines in a standard Industrial Enclosure. The
cables are all securely tie-wrapped in place for protection in the event
of nuclear blasts or tectonic plate shifts. So, it was easier to power
down and move the two boxes in the racks. (I also swapped their
annunciator panels.) I found out (on the second attempt), if I change
the letterbug on the DNBI, they will even come back up with the correct
identity. Almost everything came back up and ran fine. =20
The problem is that we have several in-house applications that run on
the AP. The operating displays for these functions reside on the AP and
are called up from any of the attached workstations and run from there.
They continue to work for all of the stations except the two that were
swapped.
The swapped workstations can ping and be pinged. The graphs on the
swapped stations display fully populated with historical data, so that
particular connection to the AP is established. But, the in-house
applications will not run from the swapped stations. I checked one of
the graphics in question to find the command line information that was
passed via dmcmd script. It was simply: =20
/path/ApplicationName GCLBUG & =20
So, I got on the AP console, went to the appropriate directory, and
typed in the command. I could not force the display to appear that way,
either. (I can, however, get this to work on any of the unaffected
machines.) I checked the log file created by the application and could
see that it was working in the background, had populated the shared
variables for the display (that didn't come up), and was waiting for a
user response from the screen.
By the way, I have also rebooted the AP. I didn't think it would help,
but I knew it wouldn't hurt either.
So at this point, the problem appears to be that the letterbug
designation is not functioning as I expect for the two affected
machines. I can't believe that I am the only one to have swapped the
locations of workstation within the same control room. Perhaps someone
has sweated out the answer to this problem before. I believe I've ruled
out Link-Layer, Network Layer, and Transport Layer problems.
Application Layer problems have their documentation so spread out that
it is daunting to even guess where to look.
Does anyone know why I cannot get this to work? =20
Chuck Jones
Refinery Automation Technologist
Tate & Lyle -- Lafayette South Plant
765.477.5324 - Office | 877.536.9219 - Pager
************************************************************************
*****************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you are not the intended recipient or the person
responsible for delivering the email to the intended recipient, be
advised that you have received this email in error that any use,
dissemination, forwarding, printing, or copying of this email is
strictly prohibited. If you have received this email in error please
notify the sender immediately. Please note that we reserve the right to
monitor and read any emails sent and received by the Company in
accordance with and to the extent permitted by applicable legal rules.
************************************************************************
*****************************
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
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:
