Re: [foxboro] Directing alarms at thin clients
- From: Russell Boulay <Russ.Boulay@xxxxxxxxxxxxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 10 Apr 2017 17:15:36 -0400
set_alarm_source still comes down to pointing to an AW letterbug or WPLN name.
The source you are selecting is not another CAD ....it is a destination WP
Logical name.
When they use the term "remote workstation" in this context of
set_alarm_source, they do not mean RDP client, they mean another Mesh AW that
is "remote" to the local AW.
So instead of receiving alarms that you may be configured to receive
locally....you use set_alarm_source to point to another alarm destination AW.
The RDP client would have to receive alarms from some other AW on the Mesh
besides it's Host......i am not sure that would have even been
tested....especially loading and performance.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Redmond, Sean S
Sent: Monday, April 10, 2017 1:48 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Directing alarms at thin clients
Hi,
I have had several people tell me that you can direct alarms to a thin client
that is running Foxview without any additional custom software.
Depending on how you have set up your alarm groups you may be able to use the
alarm manager command "set_alarm_source"
This allows the AM to behave (if that is the right word) like the AM manager
you point it to. It can tricky, but I like the feature. It is very useful for
commissioning.
Sean
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [
mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Johnson, David
Sent: Tuesday, 11 April 2017 3:46 a.m.
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Directing alarms at thin clients
Hello all,
I have had several people tell me that you can direct alarms to a thin client
that is running Foxview without any additional custom software.
Thin clients are using RDP (or something similar) to open a session on the
Foxboro Server itself, right? If so, what does the configuration look like?
How does a thin client get alarms "sent" to it, instead of the hosting AW?
If anyone can shed some light on this, I would appreciate it.
Thanks,
David
________________________________
NOTICE - This message and any attached files may contain information that is
confidential, legally privileged or proprietary. It is intended only for use by
the intended recipient. If you are not the intended recipient or the person
responsible for delivering the message to the intended recipient, be advised
that you have received this message in error. Any dissemination, copying, use
or re-transmission of this message or attachment, or the disclosure of any
information therein, is strictly forbidden. BlueScope Steel Limited does not
represent or guarantee that this message or attachment is free of errors, virus
or interference.
If you have received this message in error please notify the sender immediately
and delete the message. Any views expressed in this email are not necessarily
the views of BlueScope Steel Limited.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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 email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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:
