EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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  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 
<== Date ==> <== Thread ==>
Subject: Re: StreamDevice, asynDriver or some other solution?
From: Eric Norum <[email protected]>
To: Rod Nussbaumer <[email protected]>
Cc: [email protected]
Date: Tue, 22 Jul 2014 15:56:38 -0700
Specifying the terminators in the startup script rather then the protocol file is useful when an instrument has both a serial or ‘raw TCP’ interface (which require terminators) and a GPIB or USB-TMC interface (which often do not require terminators since they have another ‘end of message’ mechanism).  Omitting the terminator information from the protocol file allows the same protocol file to be used in both cases.
If the instrument in question has only an interface or interfaces needing terminators, then specifying the terminators in the protocol file is probably the best way to go.
YMMV

On Jul 22, 2014, at 3:45 PM, Rod Nussbaumer <[email protected]> wrote:

Bryan:

I completely concur with Mark's assessment that StreamDevice is the optimal approach for an EPICS interface to your device.

I do have a question for Mark, however. In my use of SteamDevice, I typically do not use asynOctetSetInputEos to terminate lines in the asyn driver. Is there some tangible benefit that I am missing by using StreamDevice to specify line terminators? As a developer, it feels more natural to specify the terminator character in the protocol file, where everything else related to the data communication with a device is specified. If there is a good reason to do it int he asyn layer, I will consider doing that way in future systems.

-- 
Eric Norum
[email protected]

Replies:
RE: StreamDevice, asynDriver or some other solution? Mark Rivers
References:
StreamDevice, asynDriver or some other solution? Bryan J. Boardman / Aware Electronics Corp.
RE: StreamDevice, asynDriver or some other solution? Mark Rivers
Re: StreamDevice, asynDriver or some other solution? Rod Nussbaumer
Navigate by Date:
Prev: Re: StreamDevice, asynDriver or some other solution? Rod Nussbaumer
Next: RE: StreamDevice, asynDriver or some other solution? Mark Rivers
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: StreamDevice, asynDriver or some other solution? Rod Nussbaumer
Next: RE: StreamDevice, asynDriver or some other solution? Mark Rivers
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 
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 ·