Hi Kay,
> The PV needs to connect. If you get the value right away, you’ll
> receive a null because the PV has not connected and not received the
> initial value, yet.
Thanks for clarifying. So this makes it a bit more unpredictable than I
thought... Waiting thus might not be reliable :-(
> Overall, performing logic like data acquisition should not be handled
> in the user interface.
There are a couple of use cases that do not require any complex logic.
For example saving a snapshot of a waveform PV into a file. For many use
cases it makes more sense to save this file to a client machine.
Example: Reading/writing firmware via waveform PVs. The FPGA engineer
might not even have access to the IOC's file system...
> Better would be to add a listener to the PV which gets notified as
> values arrive.
Sounds reasonable. Can you point us to an example/documentation?
Thanks,
Martin
--
Martin Konrad
Control System Engineer
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: [email protected]
- Replies:
- RE: CSS Boy Write PVs to file Iain Marcuson
- References:
- Re: CSS Boy Write PVs to file Konrad, Martin
- Navigate by Date:
- Prev:
RE: CSS Boy Write PVs to file Mark Rivers
- Next:
RE: CSS Boy Write PVs to file Iain Marcuson
- 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
- Navigate by Thread:
- Prev:
RE: CSS Boy Write PVs to file Iain Marcuson
- Next:
RE: CSS Boy Write PVs to file Iain Marcuson
- 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
|