Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: RE: Question on supporting GPIB waveform acquisition from a variety of scopes
From: "Allison, Stephanie" <saa@slac.stanford.edu>
To: "Chestnut, Ronald P." <ronc@slac.stanford.edu>, <tech-talk@aps.anl.gov>
Date: Wed, 21 Jun 2006 10:30:25 -0700
Hi Ron,

For the TDS3xx support (code mostly taken Ben Franksen's TDS540 support), we do the conversion in the "convert" routine provided in the gpibCmd structure (see page 9 of:
http://www.aps.anl.gov/epics/modules/soft/asyn/R4-6/devGpib.pdf).
The convert routine is done before record processing - it takes the string from the gpib driver, parses it, and fills in bptr and nord.  For an example, you can download the tds3xx GPIB support from the EPICS hardware support page (unfortunately, it's still 3.13) or in your case, look at /afs/slac/package/epics/R3.13.6/site/src/tdsGpib.  

Better to look at Nick DiMonte's support first.

Stephanie

> -----Original Message-----
> From: Chestnut, Ronald P. [mailto:ronc@slac.stanford.edu] 
> Sent: Wednesday, June 21, 2006 9:50 AM
> To: tech-talk@aps.anl.gov
> Subject: Question on supporting GPIB waveform acquisition 
> from a variety of scopes
> 
> We are moving our legacy VMS-based GPIB control and 
> acquistion to EPICS. SLAC uses a number of different scopes 
> from different vendors. The more modern scopes, like the 
> Tektronix TDS3000 support GPIB commands which return a 
> "preamble" with the waveform data. This preamble contains, 
> among other things, scaling information needed for proper 
> display. Other, older scopes, require that each tidbit of 
> information be requested individually.
> 
> The TDS3000 "WAVFrm?" command returns:
> 
> Write returned 0 and wrote 7 bytes
> Read returned 0 and stopped for 1 read 1024 bytes
> Buffer: 2;16;BIN;RI;MSB;10000;"Ch2, AC coupling, 5.0E-2 
> V/div, 4.0E-7 s/div, 10000 points, Sample 
> mode";Y;4.0E-10;0;-2.08E-6;"s";7.8125E-6; 0.0E0;1.5744E4;"V";#520000
> 
> Has someone addressed the problem of a generic method to 
> receive these interesting strings and parse the information out?
> 
> I can see a few ways to do each device with GENSUB or driver 
> code or even (my favorite hammer) some SEQ program, but am 
> hoping someone has a clever solution already.
> 
> Ron Chestnut
> 


References:
Question on supporting GPIB waveform acquisition from a variety of scopes Chestnut, Ronald P.

Navigate by Date:
Prev: Re: Question on supporting GPIB waveform acquisition from a variety of scopes Luedeke Andreas
Next: RE: epics php Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017 
Navigate by Thread:
Prev: Re: Question on supporting GPIB waveform acquisition from a variety of scopes Luedeke Andreas
Next: [Fwd: Re: Question on supporting GPIB waveform acquisition from a variety of scopes] Ned Arnold
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·