Experimental Physics and
Industrial Control System

[email protected] · Wed, 11 Jan 2012 16:40:39 +0100

Hi Stuart,

we have recently set up a small linux box with ines_pci_gp5130 board.

See the small snipped from st.cmd how we call GpibBoardDriverConfig

#  GpibBoardDriverConfig(portName,autoConnect,BoardIndex,timeout,priority)

GpibBoardDriverConfig("L1",1, 0, 3.0, 0)

and content of file gpib.conf of that box:

more /etc/gpib.conf

/***********************************************************************

                 GPIB.CONF
IEEE488 library config file

         -------------------

   copyright            : (C)
2002 by Frank Mori Hess

      (C) 1994 by C.Schroeter

   email                :
[email protected]

***************************************************************************/

/***************************************************************************

 *

 *   Syntax:

 *

 *         interface { ... } starts new interface
board section

 *         device {...} device configuration

 *

***************************************************************************/

interface {

        minor = 0

        board_type = "ines_pci_gp5130"

        name = "L1"

        pad = 0

        sad = 0

        eos = 0x0a      /* EOS Byte,
0xa is newline and 0xd is carriage 

return */

        set-reos = yes  /* Terminate read if
EOS */

        set-bin = no    /* Compare EOS 8-bit
*/

        set-xeos = no   /* Assert EOI whenever
EOS byte is sent */

        set-eot = yes   /* Assert EOI with last
byte on writes */

        master = yes

}

We have connected instruments of different vendors to the bus: Keithley,

HP, Datron and we also get replies where the first character is NULL. We

never saw this on an E5810 LAN-GPIB gateway, thus it must be due to the

board or linux-gpib driver.

Currently we are using epics 3.14.12.1 and asyn 4-16

What sw releases and kind of board are you using?

Regards

Peter

Am 09.01.2012 14:28, schrieb Wilkins, Stuart:

> Hi!

>

> I have been using linux-gpib and asyn (and StreamDevice) for

> communication with Keithley Electrometers. I have one comment on the

> documentation and one bug which I would like to see if anyone else
has seen.

>

> Firstly, according to the asyn documentation the following command
at

> the iocsh sets up the board.

>

> GpibBoardDriverConfig(portName,autoConnect,BoardIndex,timeout,priority)

>

>  From this documentation, it looks like you assign the GPIB board
with

> the integer "board index", however after about 2 hrs of
trying to get

> this working, I delved into the souce code for this driver. In fact,

> this is not the behavior in the code, the port driver tries to open
the

> gpib card with the same name as the portName as defined in

> /etc/gpib.conf. I think (although in places the code is fairly cryptic)

> it is only if you open a certain gpib address that it uses board index,

> but I cannot find the config to give the primary and secondary address

> at the iocsh. It might be a good idea to update this in the asyn

> documentation (or at least clarify it!)

>

> Having got past this stage, I noticed that some of my communications
are

> being garbled, with replies returning where the first character is
NULL

> [chr$(0)] instead of the correct character. Has anyone seen this

> behavior. I am not sure if it is due to the linux-gpib driver, asyn
or

> the Keithley. I plan to put another device on the bus to see if it
is

> just this combination. Is anyone out there using this combination?

>

> Best wishes,

> Stuart

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System