Experimental Physics and Industrial Control System
Hello!
I am using Constant Link Values, as documented in [1], to initialize
some waveforms in my IOC. I'm defining my records as shown below:
record(waveform, "Array-Cte"){
field(FTVL, "LONG")
field(NELM, "4")
field(INP, [1,2,3,4])
}
However, when I use camonitor or pvget to receive their values, I am
notified that their values are, in fact, undefined/invalid:
$ pvget Array-Cte
Array-Cte <undefined> INVALID DRIVER UDF [1,2,3,4]
$ camonitor Array-Cte
Array-Cte <undefined> 4 1 2 3 4 UDF INVALID
If I add field(PINI, YES) to the record definition, I no longer get
notified about invalid values or anything. But it feels wrong to have to
add PINI in this case, since I'm declaring an initializer explicitly,
and it also feels ugly to leave the UDF/INVALID text in the output. Is
this expected behavior?
I am using epics-7 at the tip of master as of today
(5eff3803a83fbc3ea855b63841f5359c09830ade). This happens for waveforms
where FTVL is "STRING" as well, at the very least. It also happens if I
use the "{const: [1,2,3,4]}" syntax from [2].
[1] https://epics.anl.gov/base/R3-16/1-docs/RELEASE_NOTES.html
[2] https://epics.anl.gov/base/R7-0/7-docs/links.html
Thank you,
Érico
P.S.: I couldn't find documentation that specified clearly that JSON
links could be used in places like input links for "newer" EPICS
releases, outside of the release notes. That might be an interesting
hole to plug in the docs. Would it go somewhere like [3]? I could try to
tackle it.
[3]
https://docs.epics-controls.org/en/latest/guides/EPICS_Process_Database_Concepts.html
Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.
Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.
- Replies:
- RE: Does using "Constant Link Values" require using PINI=YES? Mark Rivers via Tech-talk
- Re: Does using "Constant Link Values" require using PINI=YES? Timo Korhonen via Tech-talk
- Navigate by Date:
- Prev:
EPICS Support for isel imc-s8 Axis-Controller Sintschuk, Michael via Tech-talk
- Next:
RE: Does using "Constant Link Values" require using PINI=YES? Mark Rivers via Tech-talk
- 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:
EPICS Support for isel imc-s8 Axis-Controller Sintschuk, Michael via Tech-talk
- Next:
RE: Does using "Constant Link Values" require using PINI=YES? Mark Rivers via Tech-talk
- 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