RE: Soft IOC for A GPIB Instrument

["Szalata, Zenon M." <zms@slac.stanford.edu>]

Thank you replying to my plea for help.  I have installed linux-gpib package.  All went well until I ran gipb_config.  Aparrently it expects to find /dev/gpib0, which it does not find, it does not exist.  I have installed the National Instruments NI4882 package.  It installed the kernel modules successfully.  It did not create /dev/gpib0 device.  I do not see anything in /dev which looks like it might be the gpib interface...   I can run example programs that came with the NI4882 package.  The examples work fine.  I used the gpib.conf template file which came in the linux-gpib distribution, which seems to have parameters appropriate to what I am doing.  How do I associate /dev/gpib0 with "L0"?  Is it that specifying minor=0 in the interface part associates "L0" with /dev/gpib0? Any help on this will be greatly appreciated.

Zen

-----Original Message-----
From: Emmanuel Mayssat [mailto:emmanuel_mayssat@lynceantech.com] 
Sent: Monday, August 27, 2007 7:03 PM
To: Szalata, Zenon M.
Cc: tech-talk@aps.anl.gov
Subject: Re: Soft IOC for A GPIB Instrument

You need to declare a gpib interface in your stcmd, which you haven't done. But before you do that you need to compile asyn with gpib support (LINUX_GPIB=YES). Check the asyn docs. And before your do that you need to install the linux-gpib libraries.

Finally while configuring /etc/gpib.conf, you need to associate /dev/gpib0 with the "LO" name (yes that's el-zero!)

Good luck !

--
E


On Mon, 2007-08-27 at 14:58 -0700, Szalata, Zenon M. wrote:
> I am extremely new to EPICS.  To learn EPICS, I am trying to created an IOC application which would run on linux RedHat Enterprise 3 platform.  I have installed a National Instruments PCI-GPIB interface to which I have connected HP34401A multimeter.  I have installed on the same computer National Instruments software package NI4882, which I believe is the device driver for the PCI-GPIB interface.  In the package NI supplied two test programs, which I built and they work.
> 
> I followed a tutorial "How to create EPICS device support for a simple serial or GPIB device" by Eric Norum to create a support module for the HP multimeter.  Then I created a test application, as it is described in the same tutorial.  I start the test application and this is what I get:
> 
> !--------- start of program output ---------------------------------
> zms@esaux1 $ ../../bin/linux-x86/hpmm st.cmd 
> #!../../bin/linux-x86/hpmm ## You may have to change hpmm to something 
> else ## everywhere it appears in this file < envPaths
> epicsEnvSet(ARCH,"linux-x86")
> epicsEnvSet(IOC,"iochpmm")
> epicsEnvSet(TOP,"/afs/slac.stanford.edu/g/esa/esalib/app/epics/hpmm")
> epicsEnvSet(HPMM,"/afs/slac/g/esa/esalib/app/epics/modules/hpmm")
> epicsEnvSet(ASYN,"/afs/slac/g/esa/esalib/app/epics/support/asyn/4-3")
> epicsEnvSet(EPICS_BASE,"/afs/slac/package/epics/R3.14.6/base")
> cd /afs/slac.stanford.edu/g/esa/esalib/app/epics/hpmm
> ## Register all support components
> dbLoadDatabase("dbd/hpmm.dbd",0,0)
> hpmm_registerRecordDeviceDriver(pdbbase)
> ## Load record instances
> cd /afs/slac/g/esa/esalib/app/epics/modules/hpmm
> dbLoadRecords("db/devhpmm.db","P=HPMM:,R=,L=0,A=10")
> cd /afs/slac.stanford.edu/g/esa/esalib/app/epics/hpmm/iocBoot/iochpmm
> iocInit()
> ######################################################################
> ###### ###  EPICS IOC CORE built on Mar  6 2005 ###  EPICS R3.14.6 
> $R3-14-6$ $2004/05/28 19:27:47$ 
> ######################################################################
> ######
> Starting iocInit
> 2007/08/27 14:28:04.494 devSupportGpib:getDeviceInstance link 0 L0 
> failed asynManager:connectDevice port L0 not found
> 
> HPMM:hpmm:idn: init_record : no driver for link 0
> 2007/08/27 14:28:04.494 devSupportGpib:getDeviceInstance link 0 L0 
> failed asynManager:connectDevice port L0 not found
> 
> HPMM:hpmm:read: init_record : no driver for link 0 ## Start any 
> sequence programs #seq sncxxx,"user=zmsHost"
> iocInit: All initialization complete
> epics>
> !---------- end of program output 
> ---------------------------------------
> 
> In the above, the GPIB number is 0, the instrument primary GPIB address is 10 and its secondary address is 0.
> 
> I do not know how to make a connection between the NI4882 driver and the test application.  I tried something as simpleminded as including a shared library, which is in /usr/local/lib/libgpibapi.so, in the build of the test application.  This had no effect.  The reason I tried that is because the NI test programs used that library when binaries are linked.
> 
> Any help will be greatly appreciated.
> 
> Zen
>