RE: NDArrayData Access

[Mark Rivers <rivers@cars.uchicago.edu>]

Hi Yingbing,

You showed the following output:

1 0 0 0 0 0 ...
2 0 0 0 0 0 ...

What application produced that output?  Was it caget?

I suspect your problem is that you have not set the environment variable EPICS_CA_MAX_ARRAY_BYTES correctly.  You should set that to a value a little larger than the maximum array size you will use (in bytes).  It must be set in both the IOC application and on the channel access client.

To check if it is set correctly on the IOC you can use the following command at the IOC shell:

IepicsPrtEnvParams

To see if it is set correctly on the client end you can just use the following command at the Linux shell:

printenv | grep EPICS


Mark

________________________________________
From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of Yingbing Yan [yanyingbing@sinap.ac.cn]
Sent: Monday, May 28, 2012 8:58 AM
To: tech-talk@aps.anl.gov
Subject: NDArrayData Access

Dear all,

I want to implement a application via a costumed class, which inherits
directly from the asynNDArrayDriver. It is similar with simDetector in
the areaDetector, just skips the ADDriver.There is no error during
compiling and running. The parameters (asynOctet, asynInt32,
asynFloat64) can also be read & write using caget & caput. But I can not
get the correct array data of NDArray object using NDStdArrays plugin,
the output are just
1 0 0 0 0 0 ...
2 0 0 0 0 0 ...
No matter how I modify the parameters or the source codes.

Finally, I try to use simDetector directly(the defalut ioc startup
script), but the problem is similar, even using the prebuilt
areaDetector.
How to access the NDArrayData through NDStdArrays plugin? Are other
configurations required?


Best regards
Yingbing