1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: [EXTERNAL] Data Browser (phoebus) auto data fetching from an Archiver Appliance |
From: | BENEDETTI Florian via Tech-talk <tech-talk at aps.anl.gov> |
To: | "Hartman, Steven" <hartmansm at ornl.gov> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Mon, 25 Oct 2021 07:34:39 +0000 |
Hello,
Thanks for your clear explanation. The ioc runs on computer A and Archiver Appliance is installed on computer B. B is also a bridge between the experiment network and our internal network.
CS Studio is installed on several computers on our internal network for monitoring purpose. I didn't want to expose directly PVs on our internal network for safety reasons, so I tried to used the Archiver for allowing users to monitor the experiment
on our internal network .
I guess that deploying a PV gateway on B is a better solution.
De : Hartman, Steven <hartmansm at ornl.gov>
Envoyé : vendredi 22 octobre 2021 15:50:11 À : BENEDETTI Florian Cc : tech-talk at aps.anl.gov Objet : Re: [EXTERNAL] Data Browser (phoebus) auto data fetching from an Archiver Appliance
Typically, the data browser will get the historic data from the archiver, and then in-fill “live” data from Channel Access or PVAccess going forward, rather than periodically polling the archiver for updates. (The “periodic” and “monitor” settings refer
to the CA subscription.)
Can your client read the PV directly?
|