| 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: FLNK length limit |
| From: | "Kasemir, Kay" <[email protected]> |
| To: | Hinko Kocevar <[email protected]>, EPICS Tech Talk <[email protected]> |
| Date: | Fri, 9 Feb 2018 13:43:26 +0000 |
> Is the FLNK limited to 40 chars? No. What's limited to 40 chars would be TheNewLinkValue if you write it like this, which sends the value as a it as a DBF_STRING: caput record.FLNK "TheNewLinkValue" But you can write it as a byte waveform by using record.FLNK$ as a channel name. The only limitation should be related to the record name based on dbDefs.h:#define PVNAME_STRINGSZ 61 -Kay