Experimental Physics and
Industrial Control System

Emmanuel Mayssat <[email protected]> · Mon, 14 Jan 2008 09:35:40 -0800

Hello,

The first thing that come to mind is that asyn doesn't pass the reply to
devGpib. You may have to review your terminator settings.
Did you set the input and output terminators at the asyn as well as at
the devGpib level?

You may want to try to attach an asynRecord to the interface and
communicate with it directly. Doing so, you will bypass devGpib.

Before you jump into devGpib, you may want to have a look at
streamDevice.

--
E

On Mon, 2008-01-14 at 16:29 +0800, zhangdemin99 wrote:
>  
> Dera all,
>  I am trying to communicate with the GPIB device on the softIOC with
> GPIB bus.
> When I write to the device:
> epics> dbpf PSM6003:PSM6003Record:current-step 0.5
> DBR_STRING:          0.5
> it appears erro information after a few seconds:
> epics> 2008/01/14 10:51:45.364 L0 addr 0 : device timed out.
> 2008/01/14 10:51:45.365 PSM6003:PSM6003Record:current-step write
> status "L0 writeGpib failed EABO 6: Operation aborted
> " requested 19 but sent 5211728 bytes
> 2008/01/14 10:51:45.365 PSM6003:PSM6003Record:current-step error.
> 2008/01/14 10:52:15.362 L0 addr 0 : device timed out.
> 2008/01/14 10:52:15.362 PSM6003:PSM6003Record:current-step
> respond2Writes read failed
> Why it says device timed out. I am sure the device and the PCI-GPIB
> card are 
> connected well. "requested 19 but sent 5211728 bytes", should I clean
> the buffer, how to?
> The command array I set are:
>  {&DSET_SO,GPIBWRITE,IB_Q_LOW,NULL,":CURRent:STEP %
> S",50,50,NULL,0,0,NULL,NULL,NULL},
>     
>     {&DSET_SI,GPIBREAD,IB_Q_LOW,":CURRent:STEP?","%39[^\r
> \n]",0,50,NULL,0,0,NULL,NULL,NULL}
> 
> many thanks in advance
>  
>  
> 
> 
> 
> ______________________________________________________________________
> ç æ æ é è å ïï å ç æ å å ç å è è æ ä è è å ï å
> æ 2 å ï 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System