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  2014  <20152016  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  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: "No conversion between src & dest" warning with pcaspy
From: Jameson Graef Rollins <[email protected]>
To: EPICS tech-talk <[email protected]>
Date: Mon, 02 Mar 2015 14:09:04 -0800
Hi, folks.  We have applications using pcaspy (v0.4.1) to serve up
character array records for long strings.  Whenever we use MEDM to
connect to one of these character array channels, we see the following
error messages:

On the server side:

filename="../../../../src/cas/generic/casStrmClient.cc" line number=895
No conversion between src & dest types no conversion between event app type=16 and DBR type=18 Element count=60

On the MEDM side:

medmUpdateChannelCb: Bad status [400] for T1:TEST-SYS_STR: No reasonable data conversion between client and server types

Using caget I don't see any particular issue with the channel (other
than maybe the "Status: UDF" and "Severity: INVALID"):

servo:~/ligo/src/guardian [master*] 0$ caget -d DBR_CTRL_CHAR T1:TEST-SYS_STR
T1:TEST-SYS_STR
    Native data type: DBF_CHAR
    Request type:     DBR_CTRL_CHAR
    Element count:    60
    Value:            0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Status:           UDF
    Severity:         INVALID
    Units:            
    Lo disp limit:           0
    Hi disp limit:           0
    Lo alarm limit:          0
    Lo warn limit:           0
    Hi warn limit:           0
    Hi alarm limit:          0
    Lo ctrl limit:           0
    Hi ctrl limit:           0
servo:~ 0$ 

After the channel has been updated at all, even if it's been set back to
an empty array, new screens do not produce this error.  So it appears
there's something peculiar about how pcaspy is initializing char arrays
that is problematic.  If I configure the server to set the
alarm/severity so that they both show up as NO_ALARM the problem
persists, so I don't think it has to do with that.

Anyone know what might be causing this, and how to avoid it?  Is there a
way to get a full dump of the channel record that might help illuminate
what it is that's different between the cases when it the error is throw
and when it's not?

jamie.

Attachment: signature.asc
Description: PGP signature


Replies:
Re: "No conversion between src & dest" warning with pcaspy Wang Xiaoqiang (PSI)
Re: "No conversion between src & dest" warning with pcaspy Andrew Johnson

Navigate by Date:
Prev: RE: asyn R4.26 Mark Rivers
Next: Re: "No conversion between src & dest" warning with pcaspy Wang Xiaoqiang (PSI)
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Experience with Nutaq devices Greg Tchilinguirian
Next: Re: "No conversion between src & dest" warning with pcaspy Wang Xiaoqiang (PSI)
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 16 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·