Mikel,
I think you really don't want to try to modify the 40 character limit on EPICS strings. There are probably too many things that will break.
It will be much easier to figure out why Labview is not able to read the BINP array. IDL can read such arrays with no problem, using the ezca library.
Mark
________________________________
From: Mikel Eguiraun [mailto:[email protected]]
Sent: Thu 6/28/2007 10:08 AM
To: Mark Rivers; [email protected]
Subject: Re: asynRecord and Labview problem
hello,
I can not configure labview to get information from BINP, but i am still
trying. But I can use TINP to take the points step by step, but it
requires a lot of time since its size is limited to 40 bytes andI have
to take 2500 points. This size is set by epics base, isn't it? Does
anybody know if is possible to change this value to a higher one? I have
been looking in the code but i don't find any clue.
many thanks
Mikel
> I suspect the problem is with Labview, not with asynRecord, since BINP works OK in other applications.
>
> I don't know the Labview interface. You need to make sure that it is trying to read a char array for BINP, not an EPICS string PV.
>
> Mark
>
>
> ________________________________
>
> From: [email protected] on behalf of Mikel Eguiraun
> Sent: Tue 6/26/2007 5:46 AM
> To: [email protected]
> Subject: asynRecord and Labview problem
>
>
>
> hello,
>
> I have an epics server publishing information from an osciloscope using
> asynRecord, and i want to take this information using Labview (8.5b). I
> have problem reading BINP field of asynrecord to take the points of the
> scope's screen (the rest of the fields are ok), i get the following
> error in Labview:
>
> "Warning -1950679034 occurred at Shared Variable Read in server.vi
> Possible reason(s):
> LabVIEW: (Hex 0x8BBB0006) The shared variable has no value.
> This warning occurred while reading \\My Computer\server\Variable1
> (\\192.168.0.5\server\Variable1)"
>
> but if I use the command shell i am able to take those points. I am new
> to epics and labview, so i don't know in which side the problem is, has
> anybody have any suggestion to fix this problem?
>
> many thanks in advance
> Mikel Eguiraun
>
>
>
>
>
>
>
- References:
- asynRecord and Labview problem Mikel Eguiraun
- RE: asynRecord and Labview problem Mark Rivers
- Re: asynRecord and Labview problem Mikel Eguiraun
- Navigate by Date:
- Prev:
Re: PV save and restore tool sought John Sinclair
- Next:
RE: medm, edm, other on fc6 Adams, Billy R. (LARC-D401B)[RAYTHEON TECHNICAL SERVICES CO]
- 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: asynRecord and Labview problem Mikel Eguiraun
- Next:
Use of modbus tcp driver Touchard Dominique
- 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
|