- 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:[email protected]]
Sent: Tue 6/15/2010 4:43 PM
To: Mark Rivers
Cc: [email protected]
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: [email protected]
> [mailto:[email protected]] On Behalf Of William Lu
> Sent: Tuesday, June 15, 2010 2:40 PM
> To: [email protected]
> 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
[email protected]
- Replies:
- Re: Channel Access Writes Failed on Asyn Record Writable Fields Wesley Moore
- 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
- Navigate by Date:
- Prev:
Re: Channel Access Writes Failed on Asyn Record Writable Fields William Lu
- Next:
Re: Channel Access Writes Failed on Asyn Record Writable Fields Wesley Moore
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Channel Access Writes Failed on Asyn Record Writable Fields William Lu
- Next:
Re: Channel Access Writes Failed on Asyn Record Writable Fields Wesley Moore
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|