Experimental Physics and
Industrial Control System

Eric Norum <[email protected]> · Tue, 15 Mar 2011 09:48:52 -0700

Laurence is using the ASYN Linux-Gpib driver.   The port configuration command looks right, too:

	GpibBoardDriverConfig("L2",1,0,3,0)

This is:
	configuring ASYN port "L2"
	enabling autoConnect  (note that the ASYN documentation has a typo that makes it confusing to determine whether this argument is 'noAutoConnect' or 'autoConnect' -- unlike several other port configuration commands this GpibBoardDriverConfig argument really is 'autoConnect')
	associating ASYN port "L2" with linux-gpib board 0 ("/dev/gpib0").
	setting a timeout 3 seconds .  The "3" happens to end up matching one of the linux-gpib timeout codes, so really does result in a timeout of exactly 3 seconds.
	setting tjhe ASYN port thread to run at the default priority

What are the contents of "gpib.conf"?
What does "ls -l /dev/gpib0" show?

I'm guessing that they are correct, since the 'ibtest' program was able to find the board, but that's about all I can think of to check.

On Mar 15, 2011, at 9:15 AM, Rod Nussbaumer wrote:

> 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
>> 
> 

-- 
Eric Norum
[email protected]

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System