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 <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: | Can't get device capability and Can't clear buffers |
| From: | 문석호 via Tech-talk <tech-talk at aps.anl.gov> |
| To: | rivers at cars.uchicago.edu, ericnorum at gmail.com |
| Cc: | tech-talk at aps.anl.gov |
| Date: | Tue, 19 Oct 2021 17:45:04 +0900 |
First of all, I'm sorry that sending the reply with different email address.
There is some issue at my university mail system so I send the mail with gmail.
Thanks for your support, Mark Rivers and Eric Norum. However, I faced some other issue with usbtmc.
After I saw the Eric's fixed code. I change the drcAsynUSBTMC.c file like Eric but I saw the new message like below
The version of asyn and base is 4-26, 3.14.12.5 which is same with past.
There is some issue at my university mail system so I send the mail with gmail.
Thanks for your support, Mark Rivers and Eric Norum. However, I faced some other issue with usbtmc.
After I saw the Eric's fixed code. I change the drcAsynUSBTMC.c file like Eric but I saw the new message like below
The version of asyn and base is 4-26, 3.14.12.5 which is same with past.
I try to use the latest version of asyn but some error occured. I think there is some compatibility issue in my environment so I used the 4-26 version.
But when I check the drcAsynUSBTMC.c file of asyn-4.26 and latest version, there was no difference so I think it is not a problem.
But when I check the drcAsynUSBTMC.c file of asyn-4.26 and latest version, there was no difference so I think it is not a problem.
- Centos 7 environment (libusb_ver=0.1.4)
- Rasberrypi3 environment (libusb_ver=1.0)
In different environment, the epics shows the same message.
To check the usb cable and the dg812 equipment, I communicate with dg812 by using Ultra Sigma(Program of RIGOL) and Ni-Max test panel but there were no error.
Best Regards
SeokHoMoon
- Navigate by Date:
- Prev: RE: Measurement Computing USB-1608G_2AO support Mark Rivers via Tech-talk
- Next: Re: aravisGigE driver for AVT Manta camera Palaha, Arvinder (DLSLtd, RAL, LSCI) 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 <2021> 2022 2023 2024
- Navigate by Thread:
- Prev: RE: Measurement Computing USB-1608G_2AO support Mark L Rivers via Tech-talk
- Next: Re: Can't get device capability and Can't clear buffers Mark Rivers 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 <2021> 2022 2023 2024
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·