Sounds like I got two threads crossed! -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Johnson, Alex P Sent: Tuesday, June 21, 2005 5:54 PM To: foxboro@xxxxxxxxxxxxx; 'Stan Brown' Subject: Re: [foxboro] Alarm envrionments I believe that they are using "step-up" operators from one unit to support another. And if there are two operator consoles on the "source" system, redundancy can be provided. Regards, Alex Johnson Invensys Process Systems Invensys Systems, Inc. 10707 Haddington Houston, TX 77043 713.722.2859 (voice) 713.722.2700 (switchboard) 713.932.0222 (fax) alex.johnson@xxxxxxxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Grace, Kathy Sent: Tuesday, June 21, 2005 4:25 PM To: 'Stan Brown'; Grace, Kathy Cc: Foxboro List Subject: Re: [foxboro] Alarm envrionments Did I lose the thread here? I thought the point was the the Unit 2 workstation was not accessible. In which case what good would this do? -----Original Message----- From: Stan Brown [mailto:stanb@xxxxxxxxx] Sent: Tuesday, June 21, 2005 3:37 PM To: Grace, Kathy Cc: Foxboro List Subject: Re: [foxboro] Alarm envrionments On Tue, Jun 21, 2005 at 11:29:32AM -0400, Grace, Kathy wrote: > RE: > I think Alex's suggestion of using the remote AM to view the alarms > from the > other Unit would be the best approach for pre version 8 systems. > > How? This can be done for 8.0 but I have no idea how to do this for > pre 8.0 systems. Am I missing something? > My understanding of what Alex is sugestting is that I run an AM on a unit 1 WP (or AW), and have it's X DISPLAY envirnment variable set to poit to a unit 2 workstation. Is that correct Alex? -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967 _______________________________________________________________________ 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 _______________________________________________________________________ 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 _______________________________________________________________________ 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