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  <20102011  2012  2013  2014  2015  2016  2017  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: Re: Channel Access Writes Failed on Asyn Record Writable Fields
From: Wesley Moore <wmoore@jlab.org>
To: William Lu <weiwei@jlab.org>
Cc: tech-talk@aps.anl.gov
Date: Wed, 16 Jun 2010 07:30:22 -0400
William,
I've got it working. I copied your exact configuration so we should be able to determine what is going on with yours. Here's the dbpr after writing to AOUT with caput from another machine.


epics> dbpr wmoore:asyn, 2
ACKS: MINOR ACKT: YES ACMD: None ADDR: 0
AINP: AOUT: hey there AQR: 0 ASG:
AUCT: autoConnect BAUD: Unknown BINP: 0 BKPT: 00
BOUT: 0 CNCT: Disconnect DBIT: Unknown DESC:
DISA: 0 DISP: 0 DISS: NO_ALARM DISV: 1
DRVINFO: DTYP: asynRecordDevice ENBL: Enable
EOMR: None ERRS: 0x9ffc160 EVNT: 0 F64INP: 0
F64IV: 0 F64OUT: 0 FCTL: Unknown FLNK:CONSTANT 0
GPIBIV: 0 I32INP: 0 I32IV: 0 I32OUT: 0
IEOS: IFACE: asynOctet IFMT: ASCII IMAX: 80
LCNT: 0 MCTL: Unknown NAME: wmoore:asyn NAWT: 0
NORD: 0 NOWT: 80 NRRD: 0 NSEV: NO_ALARM
NSTA: NO_ALARM OCTETIV: 1 OEOS: OFMT: ASCII
OMAX: 80 OPTIONIV: 0 PACT: 0 PCNCT: Connect
PHAS: 0 PINI: NO PORT: sockserv PRIO: LOW
PRTY: Unknown PUTF: 0 REASON: 0 RPRO: 0
SBIT: Unknown SCAN: Passive SDIS:CONSTANT SEVR: MINOR
SOCK: SPR: 0 STAT: STATE TB0: On
TB1: Off TB2: Off TB3: Off TB4: Off
TFIL: Unknown TIB0: Off TIB1: Off TIB2: Off
TIME: 2010-06-16 07:24:58.887761646 TINP: TIOM: 0
TMOD: Write/Read TMOT: 1 TMSK: 1 TPRO: 0
TSE: 0 TSEL:CONSTANT TSIZ: 80 UCMD: None
UDF: 0 UI32INP: 0 UI32IV: 0 UI32MASK: 4294967295UI32OUT: 0 VAL:



Wesley


Mark Rivers wrote:
- caput again on the LS450PS:asyn.AOUT field gave the same error message as before.

I want to see the IOC output when you do that caput, after turning on the asynTraceMask in the previous step. I think sure you should see some diagnostic output.
Please also send the output of the dbpr command.
Did you try Ralphs suggestion of doing the following from the iocsh prompt?
dbpf LS450PS:asyn.AOUT "hi there"
Mark


________________________________

From: William Lu [mailto:weiwei@jlab.org]
Sent: Tue 6/15/2010 4:43 PM
To: Mark Rivers
Cc: tech-talk@aps.anl.gov
Subject: Re: Channel Access Writes Failed on Asyn Record Writable Fields



Thank you for the help.

- Sending a string from the asynRecord.edl screen gave me the error
message same as the error message I got from caput.

- The .ERRS field contains 100 zero's and these values do not change as
I tried to caput on the record's AOUT field.

- dbpr command gave no data pointing to the problem.

- "asynSetTraceMask sockserv 0 0xff" generated the following message on
the iocsh screen:
sockserv -1 exception 3 occurred calling exceptionUser
sockserv -1 exception 3 occurred calling exceptionUser
LS450PS:asyn: exception 3

- caput again on the LS450PS:asyn.AOUT field gave the same error message
as before.

At the point, I don't know the problem yet.

Thanks,
William Lu


Mark Rivers wrote:
I am not sure what the problem is, but here are some ways to find out:

- Load the medm screen for the asyn record (asynRecord.adl).  You can
then interactively send commands to the port and observe the response
and any error status.

- The asyn record has an error string field (.ERRS) which may contain
useful information.

- Execute the following iocsh command to get all the record field
values:
dbpr LS450PS:asyn 5

- Enable all debugging on that asyn port with the following iocsh
commands

asynSetTraceIOMask sockserv 0 0x2
asynSetTraceMask sockserv 0 0xff

Then do your caput again or type in the asyn records .AOUT text widget
and see if there is useful information in the output.

Mark


-----Original Message----- From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of William Lu Sent: Tuesday, June 15, 2010 2:40 PM To: tech-talk@aps.anl.gov Subject: Channel Access Writes Failed on Asyn Record Writable Fields

I am having problems with channel access writes on asyn record's
writable fields such AOUT and PORT.  I created the following asyn tcp/ip

port and the asyn record:

In a startup iocsh script:
  drvAsynIPPortConfigure("sockserv","127.0.0.1:9099",0,0,0)

The asyn record:
  record(asyn, LS450PS:asyn) {
  field(DTYP, "asynRecordDevice")
  field(PORT, "sockserv")
  field(ADDR,"0")
}

After the record has been loaded to the ioc, I cannot write the AOUT or
PORT fields of the record through channel access.  When I caput on those

fields, I got the error messages like the following:

 >caput LS450PS:asyn.AOUT "abc"
Old : LS450PS:asyn.AOUT
CA.Client.Diagnostic..............................................
    Message: "Could not perform a database value put for that channel"
    Severity: "Warning" Context: "detected by: devl17.acc.jlab.org:5064
for: LS450PS:asyn - with request chan=LS450PS:asyn.AOUT op=1 data
type=DBR_STRING count=1"
..................................................................
New : LS450PS:asyn.AOUT

What is the problem? Any help would be gratefully appreciated.

William Lu
Jefferson Lab


-- Weiwei Lu 757-269-7476 weiwei@jlab.org



begin:vcard
fn:Wesley Moore
n:Moore;Wesley
org:Thomas Jefferson National Accelerator Facility;Free Electron Laser
adr:Suite 19, MS 18;;12000 Jefferson Avenue;Newport News;VA;23606;USA
email;internet:wmoore@jlab.org
title:FEL Computer Scientist
tel;work:(757) 269-6033
tel;fax:(757) 269-6384
tel;pager:(757) 584-6033
url:http://www.jlab.org/FEL/
version:2.1
end:vcard


References:
Channel Access Writes Failed on Asyn Record Writable Fields William Lu
RE: Channel Access Writes Failed on Asyn Record Writable Fields Mark Rivers
Re: Channel Access Writes Failed on Asyn Record Writable Fields William Lu
RE: Channel Access Writes Failed on Asyn Record Writable Fields Mark Rivers

Navigate by Date:
Prev: RE: Channel Access Writes Failed on Asyn Record Writable Fields Mark Rivers
Next: RE: Channel Access Writes Failed on Asyn Record Writable Fields Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017 
Navigate by Thread:
Prev: RE: Channel Access Writes Failed on Asyn Record Writable Fields Mark Rivers
Next: Re: Channel Access Writes Failed on Asyn Record Writable Fields Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·