EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: [Bug 1939568] Re: Writing to mbboDirect.VAL does not work any more in EPICS >= 3.15
From: Andrew Johnson via Core-talk <core-talk at aps.anl.gov>
To: core-talk at aps.anl.gov
Date: Fri, 13 Aug 2021 02:33:27 -0000
The Record Reference for the mbboDirect record is a bit contradictory
about what the record should do, and the code doesn't do everything you
might want either.

In the intro at the top it says "The mbboDirect record performs the
opposite function to that of the mbbiDirect record. It accumulates bits
(in the fields B0 - BF) as unsigned characters, and converts them to a
word which is then written out to hardware." That description isn't
really correct because in closed-loop mode the Bn fields are neither
read from nor written to by process(), so they don't reflect the bits in
the VAL field at all.

However the "Desired Output Parameters" section says: "The desired
output can be written into the VAL field via dpPuts at run-time when the
record is in supervisory mode." This describes the result of the change
that Dirk is proposing. It's not particularly efficient since when
dbPut() writes to VAL the new value gets round-tripped into the Bn
fields by special() and back to VAL by process(), but doing anything
else would probably get complicated.

Currently writing "supervisory" to OMSL sets the Bn fields from VAL and
(since my 2012 changes) posts monitors on those Bn fields that change,
but any timestamps that accompany those monitors will be from when the
record last processed. Dirk's change extends that behavior to any writes
to the VAL field while OMSL is supervisory; the Bn timestamps will still
be from the last time the record processed, while the monitor which
process() posts on the VAL field will have the new timestamp.

Do we want to make any other changes while we're fixing this record? I'm
collecting edits in my base-3.15 tree and will merge that up to the 7.0
branch when we're done.

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1939568

Title:
  Writing to mbboDirect.VAL does not work any more in EPICS >= 3.15

Status in EPICS Base:
  New

Bug description:
  In EPICS 3.14, it was possible to write to mbboDirect.VAL. This does not work any longer with EPICS 3.15 or higher.
  However, writing to .VAL was always buggy anyway (did not update the.Bx fields).

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1939568/+subscriptions


References:
[Bug 1939568] [NEW] Writing to mbboDirect.VAL does not work any more in EPICS 7 Dirk Zimoch via Core-talk

Navigate by Date:
Prev: Build failed: epics-base base-regress-link-sevr-738 AppVeyor via Core-talk
Next: [Bug 1939568] Re: Writing to mbboDirect.VAL does not work any more in EPICS >= 3.15 Dirk Zimoch via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
Navigate by Thread:
Prev: [Bug 1939568] Re: Writing to mbboDirect.VAL does not work any more in EPICS >= 3.15 Dirk Zimoch via Core-talk
Next: [Bug 1939568] Re: Writing to mbboDirect.VAL does not work any more in EPICS >= 3.15 Dirk Zimoch via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
ANJ, 13 Aug 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·