EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20252026  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  <20252026 
<== Date ==> <== Thread ==>

Subject: RE: synchronizing the value of a read/write record
From: Žiga Oven via Tech-talk <[email protected]>
To: "Thomas, Patrick" <[email protected]>, "[email protected] Talk" <[email protected]>
Date: Thu, 14 Aug 2025 07:09:45 +0000

Hi Patrick,

 

There are several existing device supports for Beckhoff ADS protocol in EPICS.
For one, Cosylab has developed and is supporting the following version:
https://github.com/Cosylab/adsDriver

It already has support for the output readback functionally, provided from the community:
https://github.com/Cosylab/adsDriver/pull/8

Please use the master branch, as we have not had time for proper release yet…

Best regards

 

From: Tech-talk <[email protected]> On Behalf Of Thomas, Patrick via Tech-talk
Sent: Wednesday, August 13, 2025 19:31
To: Torsten Bögershausen <[email protected]>; [email protected] Talk <[email protected]>
Subject: Re: synchronizing the value of a read/write record

 

Hi Torsten,

 

This is device support for Beckhoff ADS, which is a communications protocol for reading and writing from and to a TwinCAT PLC. So the other source is anything else that changes the value of the variable in the PLC. This would usually be a user setting it through the TwinCAT interface, or the value being requested through EPICS but not successfully being changed in the PLC.

 

Thank you,

Patrick

 


From: Torsten Bögershausen <[email protected]>
Sent: Wednesday, August 13, 2025 2:31 AM
To: Thomas, Patrick <[email protected]>; [email protected] Talk <[email protected]>
Subject: Re: synchronizing the value of a read/write record

 

Hej Patrick,

Before answering with a longer answer, I would like to understand
what "the other source" is.

Is it
a)
   The same device,that you are controlling ?
   May be a device that has a user interface on its own,
   display, keyboard, touch screen ?
   Or are the values changed throug a user program,
   engineering tool, something in that style ?
b)
   The new values come from a different device, and are
   stored in a different record.
   May be a controll-loop where device1 says that device2
   (the one you are talking about) "please use this value"

Hope this questions are understandable.


On 2025-08-13 02:41, Thomas, Patrick via Tech-talk wrote:
> Hello,
>
> I'm attempting to write device support to handle the scenario where
> changes to the value of a hardware device can be made from both EPICS
> and another source. I would like the value of the hardware to be changed
> if I write a value to the record through channel access, and also to
> continuously monitor the hardware device for changes made from the other
> source and update the value of the record to match. One approach I have
> considered is to use separate output and input records, where the output
> records write values set from channel access to the hardware and the
> input records periodically scan the hardware and update their values
> accordingly. I am wondering however if there is a way to do this with
> the val field of just an output record. Is there any way to synchronize
> things so that write requests coming from channel access are always
> written to the hardware and not overridden by periodic updates from
> reading the hardware?
>
> Thank you,
> Patrick
>


References:
synchronizing the value of a read/write record Thomas, Patrick via Tech-talk
Re: synchronizing the value of a read/write record Torsten Bögershausen via Tech-talk
Re: synchronizing the value of a read/write record Thomas, Patrick via Tech-talk

Navigate by Date:
Prev: Re: Mapping customised pva structures to epics v4 Normative Types and v3 PVs (channel access). Michael Davidsaver via Tech-talk
Next: Re: synchronizing the value of a read/write record Torsten Bögershausen via Tech-talk
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  <20252026 
Navigate by Thread:
Prev: Re: synchronizing the value of a read/write record Thomas, Patrick via Tech-talk
Next: Re: synchronizing the value of a read/write record Torsten Bögershausen via Tech-talk
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  <20252026 
ANJ, 19 Mar 2026 · Home · News · About · Talk · Base · Modules · Extensions ·
· Distributions · Download · Documents · Links · Licensing ·