In StreamDevice I had seen no reason to have longer Buffers than the
link. But when the limit is raised or removed, I will change the code.
Dirk
On 28.04.2016 16:39, Heinz Junkes wrote:
It’s seems to be a limitation in the protocol parser of the stream module not within the EPICS stuff:
In
StreamEpics.cc:
Line 407:
long streamInitRecord(dbCommon* record, const struct link *ioLink,
streamIoFunction readData, streamIoFunction writeData)
{
char filename[80];
char protocol[80];
char busname[80];
int addr = -1;
char busparam[80];
memset(busparam, 0 ,sizeof(busparam));
buffers are fixed to 80 character sizes
Heinz
On 28 Apr 2016, at 13:57, Michael Davidsaver <[email protected]> wrote:
On 04/28/2016 05:55 AM, Dirk Zimoch wrote:
This happens when the link string is too long. It can have only 78
chars (80 including @ and terminating null byte). This is a
limitiation of EPICS.
FYI, this limit is raised to 254 characters in Base 3.15 series and
removed entirely for 3.16 series.
- References:
- stream Device I/O error Gofron, Kazimierz
- Re: stream Device I/O error Dirk Zimoch
- Re: stream Device I/O error Michael Davidsaver
- Re: stream Device I/O error Heinz Junkes
- Navigate by Date:
- Prev:
Re: Frame grabber for linux box Brian Freeman
- Next:
Re: stream Device I/O error Dirk Zimoch
- 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: stream Device I/O error Heinz Junkes
- Next:
Question about relational database setup ? lzfneu
- 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
|