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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | EPICS record name question |
From: | Rolf Keitel via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Mon, 23 Jan 2023 20:11:00 +0000 |
Working on upgrades to my tdct database configuration tool, I am struggling to find a definition for what constitutes a valid EPICS record name.
a-z A-Z 0-9 _ + - : . [ ] < > ; These are all legal characters for process variable names, although . is not allowed in a record name since it separates the record from
the field name in a PV name. “ This sentence tells me what’s legal for a record name, but not what a legal record name is. So I made a database: record(ai,"T12345") { field(SCAN,".2 second") field(INP,"12345") field(LINR,"LINEAR") } record(ai,"12345") { field(SCAN,".2 second") field(LINR,"LINEAR") } To my surprise the IOC loads this database, I can issue dbpr and dbpf to the record 12345, and I can caget and caput. Admittedly, this is all a bit pathological and setting the INP to 12345.VAL instead of 12345, makes things work. But that brings me back to my original question: what is the definition of a valid EPICS record name. Happy New Year - rolf - Rolf Keitel, Ph.D TRIUMF, 4004 Wesbrook Mall Vancouver, BC, V6T 2A3 Tel.: 604 222 7453 e-mail:
rolf at triumf.ca -- The old generation has to die off so that a new set of idiots can make the same mistakes all over again -- |