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: | autosave for V4 PVA record |
From: | Sandeep Kumar Malu - UKRI STFC via Tech-talk <tech-talk at aps.anl.gov> |
To: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Wed, 2 Sep 2020 15:28:38 +0000 |
Hi All, I am following the same procedure to do the autosave for V3 db records & V4 PVA records. My IOC looks similar to https://github.com/epics-base/exampleCPP/tree/master/database. Autosave lines in st.cmd are set_requestfile_path("$(TOP)/autoSaverestore") set_savefile_path("$(TOP)/autoSaverestore") set_pass0_restoreFile("autosaverecord.sav") set_pass1_restoreFile("autosaverecord.sav") cd "${TOP}/iocBoot/${IOC}" iocInit create_monitor_set("autosaverecord.req", 5) The output on epics console has error: save_restore: connect failed for channel 'PVA_Double_Test' “autosaverecord.req” file has both V3 & V4 record & has contents PVA_Double_Test CA_Double_Test ***************************************************** autosaverecord.sav file after autosave gives below contents # autosave R5.3 Automatically generated - DO NOT MODIFY - 200902-193433 CA_Double_Test 8.9 So, the bottom line is autosave works for V3 type record but fails to do for V4 type PVA record. Any suggestion would be highly appreciated. Many Thanks Sandeep This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI. |