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  <20192020  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  <20192020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: StreamDevice device locking
From: Joao Afonso via Tech-talk <[email protected]>
To: "[email protected]" <[email protected]>
Cc: Stephen Page <[email protected]>
Date: Fri, 8 Feb 2019 13:24:57 +0000
Hello,

At the moment I am experimenting with StreamDevice, while connecting it to a custom asynPortDriver (instantiated with ASYN_MULTIDEVICE, ASYN_CANBLOCK).

According to the documentation, each protocol command blocks the device for the duration of the protocol, which makes sense.
But an access to two devices on two different addresses should be possible:
  • "The first out command in the protocol locks the device for exclusive access. That means that no other record can communicate with that device. This ensures that replies given by the device reach the record which has sent the request. On a bus with many devices on different addresses, this normally locks only one device. The device is unlocked when the protocol terminates. Another record trying to lock the same device has to wait and might get a LockTimeout."
However, I noticed that if I process two records with stream device, for addresses #1 and #2, it first runs all callbacks for address #1, and only after to #2.
This is contrary to my expectation, which would be to see callbacks to both devices being executed interleaved.

Is there a way to tell StreamDevice to block only on the address level, allowing to different addresses to be processes simultaneously?

Thanks,
Joao Afonso
CERN TE-EPC-CCS



Replies:
Re: StreamDevice device locking Dirk Zimoch via Tech-talk

Navigate by Date:
Prev: Re: Point Grey GigE Blackfly conflict Nilson Pereira via Tech-talk
Next: Re: StreamDevice device locking Dirk Zimoch 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  <20192020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: trying to find information on mvme5100 battery Maren Purves via Tech-talk
Next: Re: StreamDevice device locking Dirk Zimoch 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  <20192020  2021  2022  2023  2024 
ANJ, 13 Feb 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·