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: How to use asyn with linux-GPIB |
From: | Rod Nussbaumer <[email protected]> |
To: | Feng Laurence <[email protected]> |
Cc: | [email protected] |
Date: | Tue, 15 Mar 2011 09:15:53 -0700 |
Laurence:I find it much more convenient to use streamDevice in conjunction with asyn for communicating with GPIB devices. Linux-gpib with asyn and streamDevice is the standard model used at TRIUMF for all GPIB communications in EPICS.
Like any communications channel used by asyn, the startup script must configure the port driver. In your case it would be the GPIB driver. The details for setup of the linux-GPIB port driver are outlined in
'documentation/asynDriver.html#PortDrivers' included in the asyn package. Rod Nussbaumer ISAC Controls, TRIUMF Vancouver, Canada Feng Laurence wrote:
Hi everyone~ I'm trying to connect a scope via linux-GPIB. The driver had been setup and read/write to the scope was successfully tested with "ibtest" But when typing in iocsh the command GpibBoardDriverConfig("L2",1,0,3,0) I got the error: 2011/03/14 21:48:44.176 L2 addr -1 : EDVR 0: OS error. 2011/03/14 21:48:44.176 L2 addr -1 : EDVR 0: OS error. ........ libgpib: invalid descriptor libgpib: invalid descriptor libgpib: invalid descriptor ........ alot of repeat lines....... Looks like the GPIB device address was not set correctly. However, I can find no hints in the asyn document for the problem. Is there anything I missed here? -- Laurence Feng Superconducting Radio Frequency Group State Key Laboratory of Nuclear Physics and Technology Peking University, 302 Chengfu Road Beijing 100871 China