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: caPutLog breaks monitoring of PV when the same channel is used for putting |
From: | Érico Nogueira Rolim via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Fri, 5 Apr 2024 12:35:54 +0000 |
On Thu, Apr 4, 2024 at 1:28 PM Érico Nogueira Rolim via Tech-talk <tech-talk at aps.anl.gov> wrote:
...It also seems relevant that puts
to these waveforms don't show up in the resulting log.
...
I saw a similar-ish issue in the caPutLog bugtracker [1], but it was
specifically about QSRV1.
I don't think #22 issue is limited to QSRV1. Rather there is a race condition involving caPutLog and monitoring VAL of waveformRecord and similar.
I see, that makes sense. It would be good to update the commit message in that PR, then. Our affected IOCs don't even link any PVAccess libraries, so I assumed it wouldn't apply to us.
It seems to have worked. I will leave a comment in the PR as well.
Thank you for the pointer!
Our versions of things:
In the IOCs and sequencer client:
- epics-base: 7.0.7
- caPutLog: R4.0
- Sequencer: R2-2-9
One of the PyDM interfaces (via conda):
- PyDM: 1.10.3
- pyEPICS: 3.5.0
Other PyDM interface report (via conda):
- PyDM: 1.22.0 or 1.19.1
- pyEPICS: 3.5.1 (from pip)
Cheers,
Érico
[1] https://urldefense.us/v3/__https://github.com/epics-modules/caPutLog/issues/22__;!!G_uCfscf7eWS!ejmmpa48B5Lg-cSSwalI96o2gTPgfS-fdi3OeNW5T6si95vrsnEEIouNzK6cet7e6zcOuYs5JytQ8Xs9sGnrzYO4c64$
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.