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  <20142015  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  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: asyn vxi11 problem
From: Dirk Zimoch <[email protected]>
To: Eric Norum <[email protected]>
Cc: [email protected]
Date: Wed, 30 Apr 2014 14:10:21 +0200
There is an asyn USBTMC driver? I will check that.
Dirk

On 29.04.2014 17:59, Eric Norum wrote:
On Apr 29, 2014, at 12:34 AM, Dirk Zimoch <[email protected]> wrote:

Hi Peter,

Maybe you are using a too old version of StreamDevice?

For most devices, I try to read first 1 byte with ReplyTimeout and then the rest with ReadTimeout. For serial and socket this works fine. But GPIB devices must be addressed to talk and then deliver complete messages. If I now ask for only 1 byte, the GPIB driver reports overflow. (Unfortunately it does not store the message in some local input buffer where could pick it up later.)

Thus I have modified StreamDevice to handle GPIB devices differently and read larger messages. I have changed that behavior quite some time a

BTW: At the moment, I am working on a more flexible solution, because there are other devices, that behave similarly without having a asynGpibType interface (e.g. usbtmc). Progress is slow however because of lack of time.

The asyn USBTMC driver does read large blocks from the device and buffers them for later delivery to higher level code.  This results in an extra copy operation but provides more flexibility in the size of transfers requested by the higher level code.  So StreamDevice should work as-is since the USBTMC driver semantics match those of serial and socket devices.

Also, the USBTMC driver properly reports ‘end-of-message’ conditions so the higher level code can use that in place of, or in addition to, terminator characters to detect the end of data.



References:
asyn vxi11 problem peter.owens
Re: asyn vxi11 problem Dirk Zimoch
Re: asyn vxi11 problem Eric Norum

Navigate by Date:
Prev: cannot run medm rightly on ubuntu 13.04 ahwwq
Next: [CSS] freeze and lost running PV in Boy Screens Maurizio Montis
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: asyn vxi11 problem Eric Norum
Next: looking for a part time developer for EPICS kingcomsh
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·