It's actually EPICS_CA_MAX_ARRAY_BYTES, not EPICS_CA_MAX_ARRAY_SIZE. That must be set on both the IOC machine and the Python client machine.
Mark
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Matt Newville
Sent: Tuesday, April 12, 2011 10:52 AM
To: Ritesh Sugandhi
Cc: [email protected]
Subject: Re: Python EPICS interface (pyepics 3.1.1) double waveform record (NLEM = 65535 ) record handling exception
Hi Ritesh,
What is EPICS_CA_MAX_ARRAY_SIZE set to? If left unset, I believe you
would see exactly this behavior (arrays using up to 16384 bytes would
work, while larger arrays would fail.
I haven't tested with python 3.2 on 64-bit linux (yet?), so it's
possible there are issues, but I'd expect that if short arrays of
doubles work that longer ones would too.
--Matt Newville
On Tue, Apr 12, 2011 at 10:29 AM, Ritesh Sugandhi
<[email protected]> wrote:
> Dear sir,
>
> My Enviorment is
> ----------------------
> pyepics-3.1.1,
> python 3.2
> Linux kernal 2.6.18-194 ; 64 bit
> Context: Testing pyepics library
> Problem:
> I am using supplied database (test/pydebug.db) and I am not able to use the
> double wave form record of 64k elements. while double wave form record of 2k
> elements works fine.
> Any suggestion are welcome.
> Best regards
> ---- EPICS shell------------------
> epics> dbpr Py:double64k 2
> ACKS: NO_ALARM ACKT: YES APST: Always ASG:
>
> BKPT: 00 BUSY: 0 DESC: long double waveform
>
> DISA: 0 DISP: 0 DISS: NO_ALARM DISV: 1
>
> DTYP: Soft Channel EGU: EVNT: 0 FLNK:CONSTANT 0
>
> FTVL: DOUBLE HOPR: 0 INP:CONSTANT LCNT: 0
>
> LOPR: 0 MPST: Always NAME: Py:double64k NELM: 65536
>
> NORD: 0 NSEV: NO_ALARM NSTA: NO_ALARM PACT: 0
>
> PHAS: 0 PINI: NO PREC: 0 PRIO: LOW
>
> PUTF: 0 RARM: 0 RPRO: 0 SCAN: Passive
>
> SDIS:CONSTANT SEVR: INVALID SIML:CONSTANT SIMM: NO
>
> SIMS: NO_ALARM SIOL:CONSTANT STAT: UDF TIME:
> <undefined>
> TPRO: 0 TSE: 0 TSEL:CONSTANT UDF: 1
>
> VAL: (nil)
> ------------- Python shell -----------------------------
>>>> pv1=PV('Py:double64k')
> Traceback (most recent call last):
> File "_ctypes/callbacks.c", line 259, in 'calling callback function'
> File
> "/home/ITER/sugandr/Desktop/epics-python/Python-3.2/lib/python3.2/site-packages/epics/ca.py",
> line 391, in _onGetEvent
>>>> value = dbr.cast_args(args).contents
> ValueError: NULL pointer access
- Replies:
- Re: Python EPICS interface (pyepics 3.1.1) double waveform record (NLEM = 65535 ) record handling exception Andrew Johnson
- References:
- Python EPICS interface (pyepics 3.1.1) double waveform record ( NLEM = 65535 ) record handling exception Ritesh Sugandhi
- Re: Python EPICS interface (pyepics 3.1.1) double waveform record ( NLEM = 65535 ) record handling exception Matt Newville
- Navigate by Date:
- Prev:
Re: Python EPICS interface (pyepics 3.1.1) double waveform record ( NLEM = 65535 ) record handling exception Matt Newville
- Next:
Re: Python EPICS interface (pyepics 3.1.1) double waveform record (NLEM = 65535 ) record handling exception Andrew Johnson
- 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: Python EPICS interface (pyepics 3.1.1) double waveform record ( NLEM = 65535 ) record handling exception Matt Newville
- Next:
Re: Python EPICS interface (pyepics 3.1.1) double waveform record (NLEM = 65535 ) record handling exception Andrew Johnson
- 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
|