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: A couple of drvAsyn/devGpib questions |
From: | Eric Norum <[email protected]> |
To: | "LYNCH, Damien" <[email protected]> |
Cc: | [email protected] |
Date: | Thu, 5 Jan 2006 16:07:01 -0600 |
What a truly bizarre command set. I think that devGpib can handle this if you: 1) Set a really long I/O timeout value 2) Provide your own GPIBCVTIO routine to call the low level read and write routines. This is quite simple because the GPIBCVTIO routine and low-level read and write routines operate in a single-threaded blocking environment. You asked what sort of record would be appropriate for the final command/response example. This depends on which of the response lines you're interested. If you want to capture the whole thing you could use a waveform record with FTVL set to CHAR. A gensub record or a sequence program could then distribute the values to multiples PVs. On Jan 5, 2006, at 2:54 PM, LYNCH, Damien wrote:
|