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  <20212022  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: asynUSBTMC communications issue
From: Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>
To: Eric Norum <wenorum at lbl.gov>, "Dudley, David" <dudleyd at frib.msu.edu>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Wed, 1 Dec 2021 19:54:17 -0800
On 12/1/21 1:28 PM, Eric Norum via Tech-talk wrote:
> I wrote the USBTMC driver using the standard as a guide but there are lots of gray areas where I may have interpreted things incorrectly. And I’m no expert on the use of libusb…..
> If someone has a way to trace USB operations I’d be happy to work on the driver so that it produces the same output as the LabView extension.

fyi. Wireshark can capture arbitrary USB traffic.

https://wiki.wireshark.org/CaptureSetup/USB


>> On Dec 1, 2021, at 1:24 PM, Dudley, David via Tech-talk <tech-talk at aps.anl.gov <mailto:tech-talk at aps.anl.gov>> wrote:
>>
>> Mark,
>>  
>> I’m trying to use the asynUSBTMC driver to connect to some SCPI USB devices.  I’ve got a Keithley 3390 Waveform generator, a B&K 9130B Power Supply and a B&K 8600B Electronic load all connected by USB.
>>  
>> All of the units work properly with the supplied LabView extensions on my Windows system.
>>  
>> Using the Asyn driver however, I can send most any query function that I want and get a proper response.  Send a command (even something like *RST or *CLR), and the device reports an invalid termination character on the Keithley, and the B&K’s just fail to answer or lock up.
>>  
>> I’ve tried CR LF, CR, LF, NL as terminations, and they all provide the same problems.
>>  
>> Any ideas on where to start looking?
>>  
> 


References:
asynUSBTMC communications issue Dudley, David via Tech-talk
Re: asynUSBTMC communications issue Eric Norum via Tech-talk

Navigate by Date:
Prev: RE: CA Gateway same VM as IOCs/Phoebus and Access/PVList Setup Manoussakis, Adamandios via Tech-talk
Next: Re: MVME3100 boot failure at "Trying to find CSR on VME" Michael Davidsaver 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  <20212022  2023  2024 
Navigate by Thread:
Prev: Re: asynUSBTMC communications issue Eric Norum via Tech-talk
Next: CentOS Alternatives Abdalla Ahmad 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  <20212022  2023  2024 
ANJ, 05 Dec 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·