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: | Re: Writing PVs from an amalgamated structure |
From: | "Arnold, Ned D." <[email protected]> |
To: | Iain Marcuson <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Mon, 9 Oct 2017 13:49:55 +0000 |
Hey Iain -
I would do this in the sequencer (SNL - State Notation Language). The sequencer will do all the connection handling to the PVs and you can include your own library (C/C++) for the file operations. I think you'll find it a nice environment to work in on
the IOC.
Ned From: [email protected] <[email protected]> on behalf of Iain Marcuson <[email protected]>
Sent: Monday, October 9, 2017 08:23 AM To: Johnson, Andrew N. Cc: EPICS Tech Talk Subject: RE: Writing PVs from an amalgamated structure I have attached a diagram of what we are planning at the moment. The functions ReadConfigFile() and WriteConfigFile() would be called when the user requests a load or save. The configuration data would be stored in one big structure.
GetData() returns a pointer to the structure, and is intended as the link between the PVs and the library.
> -----Original Message----- > From: Johnson, Andrew N. [mailto:[email protected]] > Sent: Saturday, October 07, 2017 6:59 AM > To: Iain Marcuson <[email protected]> > Cc: EPICS Tech Talk <[email protected]> > Subject: Re: Writing PVs from an amalgamated structure > > Hi Iian, > > I think we need to know quite a bit more about what you're trying to do, and > where/when these configuration files will be read and/or written. The > answers are likely to be very different depending on what you tell us, and I > don't think anyone wants to spend time answering the wrong question. > > - Andrew > > -- > Sent from my iPad > > > On Oct 6, 2017, at 6:22 PM, Iain Marcuson > <[email protected]> wrote: > > > > I need to create support for reading and writing a configuration file, but I > also have to support non-EPICS environments. I am thus considering making > a library to be used in the IOC. My present idea is to pass EPICS a pointer to a > structure containing all the configuration options. However, I do not know > what best practices are for mapping PVs to the memory location. What are > the accepted methods? > > > > Thank you, > > > > Iain. > > > > |