EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  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  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: read status nin "" 0 error with
From: Mark Rivers <[email protected]>
To: "'Eric Norum'" <[email protected]>, Ana Malagon <[email protected]>
Cc: EPICS mailing list <[email protected]>
Date: Wed, 10 Dec 2014 20:42:16 +0000

> I’m at a loss then.  I have no idea why enabling ASYN diagnostic messages is having no effect.

 

I know why it is happening.  Ana is doing this before iocInit.

asynSetTraceMask("L0", -1, 0xFF)

The problem is that using the address of -1 on asynSetTraceMask set the trace mask of all device address that are currently connected to that asyn port.  However, at that point the GPIB device at address 19 has not yet been connected, so its asynTraceMask does not get set.

The solution is to move that line to after iocInit.  You won’t see any trace information that should happen as part of iocInit, but you will see everything after that command is issued.

We might want to change the way asynSetTraceMask($(PORT), -1, MASK) works to avoid this confusion.  Someone else ran into this a couple of weeks ago.

Mark

 

 

 

From: [email protected] [mailto:[email protected]] On Behalf Of Eric Norum
Sent: Wednesday, December 10, 2014 2:23 PM
To: Ana Malagon
Cc: EPICS mailing list
Subject: Re: read status nin "" 0 error with

 

I’m at a loss then.  I have no idea why enabling ASYN diagnostic messages is having no effect.

What platform is this on?

Perhaps a complete rebuild of base and modules might help?

 

A handy thing to try is to rebuild your IOC with only a single ASYN record — then use the GUI tools to use the record to set diagnostic message levels and send/receive commands by hand.

 

 

On Dec 10, 2014, at 12:13 PM, Ana Malagon <[email protected]> wrote:

 

Thanks Eric for the suggestions! For the terminator character error message, I get : Set EOS failed: L0 setOutputEos not implemented

when enabling asynOctetSetInputEos("L0",-1,"\n") and asynOctetSetOutputEos("L0",-1,"\n").

Good point about the double cast on atof - there was no reason for it, have removed it. I tried turning on more diagnostics but weirdly enough don't even see any communication with the device in terms of bytes being read or written. However I can see the frequency change on the device so I know that setting the frequency works. Here's the output from the ioc:

cd /home/admx/admxepics/iocs/SdCarLO

## Register all support components

dbLoadDatabase "dbd/SdCarLO.dbd"

SdCarLO_registerRecordDeviceDriver pdbbase

prologixGPIBConfigure("L0", "10.95.101.74:1234")

asynOctetSetInputEos("L0",-1,"\n")

asynOctetSetOutputEos("L0",-1,"\n")

Set EOS failed: L0 setOutputEos not implemented

asynSetTraceIOMask("L0", -1, 0x2)

asynSetTraceMask("L0", -1, 0xFF)

## Load record instances

cd /home/admx/admxepics/devices/ag83620b

dbLoadRecords("db/devAG83620B.db","SIGGEN=SDCARLO, L=0, A=19")

cd /home/admx/admxepics/iocs/SdCarLO/iocBoot/iocSdCarLO

iocInit

############################################################################

## EPICS R3.14.12.4 $Date: Mon 2013-12-16 15:51:45 -0600$

## EPICS Base built May 20 2014

############################################################################

## Start any sequence programs

#seq sncxxx,"user=admxHost"

epics> 2014/12/10 12:08:57.985 SDCARLO:GET:FREQ read status "" nin 0

2014/12/10 12:08:57.985 SDCARLO:GET:FREQ error.

2014/12/10 12:08:57.985 asynManager::portThread port=L0 callback

epics> dbpf SDCARLO:SET:FREQ 12

DBR_DOUBLE:         12                  

epics> 2014/12/10 12:09:12.743 SDCARLO:GET:FREQ read status "" nin 0

2014/12/10 12:09:12.743 SDCARLO:GET:FREQ error.

dbtr SDCARLO:GET:FREQ

ACKS: INVALID       ACKT: YES           ADEL: 0             ALST: 0             

AOFF: 0             ASG:                ASLO: 1             BKPT: 00            

DESC: Query Frequency ouput MHz         DISA: 0             DISP: 0             

DISS: NO_ALARM      DISV: 1             DTYP: AG83620B      EGU: MHz            

EGUF: 0             EGUL: 0             EOFF: 0             ESLO: 1             

EVNT: 0             FLNK:CONSTANT 0     HHSV: NO_ALARM      HIGH: 0             

HIHI: 0             HOPR: 0             HSV: NO_ALARM       HYST: 0             

INIT: 0             INP:GPIB_IO #L0 A19 @4 CPP              LALM: 0             

LBRK: 0             LCNT: 0             LINR: NO CONVERSION LLSV: NO_ALARM      

LOLO: 0             LOPR: 0             LOW: 0              LSV: NO_ALARM       

MDEL: 0             MLST: 0             NAME: SDCARLO:GET:FREQ                  

NSEV: NO_ALARM      NSTA: NO_ALARM      ORAW: 0             PACT: 1             

PHAS: 0             PINI: YES           PREC: 0             PRIO: LOW           

PROC: 0             PUTF: 0             ROFF: 0             RPRO: 0             

RVAL: 0             SCAN: Passive       SDIS:CONSTANT       SEVR: INVALID       

SIML:CONSTANT       SIMM: NO            SIMS: NO_ALARM      SIOL:CONSTANT       

SMOO: 0             STAT: READ          SVAL: 0             

TIME: 2014-12-10 12:09:12.743268858     TPRO: 0             TSE: 0              

TSEL:CONSTANT       UDF: 1              VAL: 0              

epics> 2014/12/10 12:09:22.508 SDCARLO:GET:FREQ read status "" nin 0

 

2014/12/10 12:09:22.508 SDCARLO:GET:FREQ error.

 

 

 

-- 
Eric Norum
[email protected]

 


Replies:
Re: read status nin "" 0 error with Eric Norum
Re: read status nin "" 0 error with Eric Norum
References:
read status nin "" 0 error with Ana Malagon
Re: read status nin "" 0 error with Eric Norum
Re: read status nin "" 0 error with Ana Malagon
Re: read status nin "" 0 error with Eric Norum

Navigate by Date:
Prev: Re: read status nin "" 0 error with Eric Norum
Next: Re: read status nin "" 0 error with Eric Norum
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: read status nin "" 0 error with Eric Norum
Next: Re: read status nin "" 0 error with Eric Norum
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·