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  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Changing the Timeout for drvAsynSerialPort?
From: Franklin Fuller <[email protected]>
To: Eric Norum <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Thu, 11 Dec 2014 10:43:12 -0800
Boom!  Thank you Eric and Mark!  I tried it both ways, just for educational purposes, and it worked.

For future readers: the dev<app_name>.proto file, which allowed me to affect the terminator and timeout variables, was flagged as "read only", and that made me think I shouldn't be editing it.  This file looks like it was coppied from <app_name>Sup.proto.  Altering <app_name>Sup.proto did nothing, while dev<app_name>.proto did something.

If you alter <app_name>Sup.proto and then rebuild (via make distclean, make in the $TOP).  The changes copy over and it works.

Thanks again

On Thu, Dec 11, 2014 at 10:34 AM, Eric Norum <[email protected]> wrote:
Yes, specifying the terminators in the st.cmd script is the better approach.  

But in response to your comments below, instruments using raw stream TCP/IP (i.e. not VXI-11) usually require terminators too.
USBTMC and GPIB devices have out-of-band “end of message” mechanisms don’t need explicit terminator characters.

On Dec 11, 2014, at 10:29 AM, Mark Rivers <[email protected]> wrote:

In general it’s a better idea to add the termination commands using asynOctetSetOutputEos than using the Terminator command in the StreamDevice protocol file.  That way if you change from using serial to using TCP/IP you only need to change your startup script, not your protocol file.

-- 
Eric Norum
[email protected]


References:
Changing the Timeout for drvAsynSerialPort? Franklin Fuller
RE: Changing the Timeout for drvAsynSerialPort? Mark Rivers
Re: Changing the Timeout for drvAsynSerialPort? Franklin Fuller
Re: Changing the Timeout for drvAsynSerialPort? Eric Norum
RE: Changing the Timeout for drvAsynSerialPort? Mark Rivers
Re: Changing the Timeout for drvAsynSerialPort? Eric Norum

Navigate by Date:
Prev: Re: Changing the Timeout for drvAsynSerialPort? Eric Norum
Next: asyn R4-25 available Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Changing the Timeout for drvAsynSerialPort? Eric Norum
Next: RE: Changing the Timeout for drvAsynSerialPort? Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·