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  2015  2016  2017  2018  2019  2020  2021  <20222023  2024  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  <20222023  2024 
<== Date ==> <== Thread ==>

Subject: Re: asyn IMAX data transfer exceeding EPICS_CA_MAX_ARRAY_BYTES
From: "Siddons, David via Tech-talk" <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, "Marco A. Barra Montevechi Filho" <marco.filho at lnls.br>
Date: Tue, 15 Mar 2022 19:42:11 +0000
Hi Marco,
   Is EPICS_CA_MAX_ARRAY_BYTES set on both ends of the link?
Pete.


From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Marco A. Barra Montevechi Filho via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, March 15, 2022 3:39 PM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: asyn IMAX data transfer exceeding EPICS_CA_MAX_ARRAY_BYTES
 
Hello all

Im debugging an EPICS asyn IOC which was working fine until now. The st.cmd of the IOC has a line which loaded asynRecord.db:

dbLoadRecords("$(ASYN)/db/asynRecord.db","P=$(DEV),R=asynEth,PORT=E873_ETH,ADDR=0,OMAX=256,IMAX=256")

and caput caget BL:H:EQ:asynEth.IFMT 1 (Hybrid)
caget BL:H:EQ:asynEth.BINP

in the IOC machine returned an array of numbers without any problem. However, it is recovering an array from a file much alrger than 256, so i suppose it just threw parts of the file away.
We wanted to get more of the file, so we raised IMAX to 350000 and defined the env variable EPICS_CA_MAX_ARRAY_BYTES=15728645. SO we got the error

caget MGN:A:E873:DIAG:A:asynEth.BINP
CA.Client.Exception...............................................
    Warning: "The requested data transfer is greater than available memory or EPICS_CA_MAX_ARRAY_BYTES"
    Context: "op=0, channel=MGN:A:E873:DIAG:A:asynEth.BINP, type=DBR_TIME_CHAR, count=16406, ctx="server unable to load read (or subscription update) response into protocol buffer PV="MGN:A:E873:DIAG:A:asynEth" max bytes=16408""
    Source File: ../getCopy.cpp line 92
    Current Time: Tue Mar 15 2022 16:32:11.936961493
..................................................................
Read operation timed out: some PV data was not read.
MGN:A:E873:DIAG:A:asynEth.BINP 350000 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 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  (the zeroes continue)

So we tried lowering IMAX to 16406 but still the error persisted:

CA.Client.Exception...............................................
    Warning: "The requested data transfer is greater than available memory or EPICS_CA_MAX_ARRAY_BYTES"
    Context: "op=0, channel=MGN:A:E873:DIAG:A:asynEth.BINP, type=DBR_TIME_CHAR, count=16406, ctx="server unable to load read (or subscription update) response into protocol buffer PV="MGN:A:E873:DIAG:A:asynEth" max bytes=16408""
    Source File: ../getCopy.cpp line 92
    Current Time: Tue Mar 15 2022 16:32:11.936961493
..................................................................
Read operation timed out: some PV data was not read.
MGN:A:E873:DIAG:A:asynEth.BINP 16406 0 0 0 0 0 0

does anyone know if we are doing something wrong or forgetting something? I dont think memory should be the problem here... Where do these "max bytes=16408" come from?


Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.

Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.


Replies:
Re: asyn IMAX data transfer exceeding EPICS_CA_MAX_ARRAY_BYTES Mark Rivers via Tech-talk
References:
asyn IMAX data transfer exceeding EPICS_CA_MAX_ARRAY_BYTES Marco A. Barra Montevechi Filho via Tech-talk

Navigate by Date:
Prev: asyn IMAX data transfer exceeding EPICS_CA_MAX_ARRAY_BYTES Marco A. Barra Montevechi Filho via Tech-talk
Next: Re: Communication error Matt Rippa via Tech-talk
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  <20222023  2024 
Navigate by Thread:
Prev: asyn IMAX data transfer exceeding EPICS_CA_MAX_ARRAY_BYTES Marco A. Barra Montevechi Filho via Tech-talk
Next: Re: asyn IMAX data transfer exceeding EPICS_CA_MAX_ARRAY_BYTES Mark Rivers via Tech-talk
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  <20222023  2024 
ANJ, 14 Sep 2022 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·