Experimental Physics and
Industrial Control System

Hi,

On 2012-05-30 Ralph Lange wrote:
> 
> Of course, any CA client may decide to use any format to write the data.
> It's just the stupid caput tool that always uses DBR_STRING for
> everything it writes.

As long as you're not doing this on Windows (the CA Perl library is too hard 
to build for that platform so the Perl scripts are not available there) the 
caput.pl script will default to using the channel's native type when putting 
array data.  The main difference between caput.pl and caput is that caput.pl 
does not expect the array length to precede the data, but otherwise the two 
are very similar.

- Andrew
-- 
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte

References:

Problem when caput to waveform record 王林

Re: Problem when caput to waveform record Ralph Lange

Navigate by Date:

Prev: RE: [StreamDevice] parsing rapid inputs Mark Rivers

Next: Re: Proposed change in asyn - request for comments Ernest L. Williams Jr.

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: Problem when caput to waveform record 王林

Next: ether_ip problem reading DINT arrays Bob Gunion

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