Experimental Physics and
Industrial Control System

You could do 

asynSetTraceIOMask(...)
asynSetTraceFile(...)
asynSetTraceMask(...)

on the underlying asyn port before iocInit.  By sending the trace output to a file it has a minimal impact on timing.  You can then see if some operations are timing out.

Mark

________________________________________
From: [email protected] [[email protected]] on behalf of Hinxx [[email protected]]
Sent: Tuesday, December 06, 2016 2:04 AM
To: tech-talk
Subject: streamdevice 2.7.7 and PINI

Hi,

I have 29 stream records with PINI fields set to YES and three of them
show

'Value: VByteArray[[], size 0, INVALID(TIMEOUT_ALARM), 2016/12/06
08:59:18.108]'

No errors are seen in IOC. My proto is not setting any timeout
variables, I guess defaults are used.

If I use 25 records or less with PINI=YES this is not happening.

What limit am I hitting?

Thanks,
Hinko

References:

streamdevice 2.7.7 and PINI Hinxx

Navigate by Date:

Prev: Re: Epics V4 Questions - New to Epics 4 Marty Kraimer

Next: Re: IOC segfaults with epicsMutexLock (pmutexNode=0x0) Blaz Kranjc

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: streamdevice 2.7.7 and PINI Hinxx

Next: TPG-256 driver Peredkov, Sergey

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