I plan on making a couple of changes to the ASYN TCP port driver. Here's the salient portion of the release notes:
drvAsynIPPort
===========
1) A return of 0 from a read of a TCP stream is treated as an END condition rather than as an error. This makes it easier to handle devices that close the connection at the end of a reply.
2) Support has been added for devices such as web servers that require a connect at the beginning of each transaction. To enable this behaviour, specify "http" as the protocol in the drvAsynIPPortConfigure command and ensure that each transaction ends with a read that detects the broken connection from the device. Note that the device will always appear connected. The connect/disconnect around each transaction is handled within the drvAsynIPPort driver.
I hope that these changes are neither too controversial nor too disruptive. The first one I believe falls under the "principle of least surprise" and the second takes effect only when changes are made to a startup file command.
--
Eric Norum
[email protected]
P.S. Thanks go out to Marty Kraimer and Mark Rivers for their help in making these changes.
- Navigate by Date:
- Prev:
Re: Reading an array of strings from a Waveform record Andrew Johnson
- Next:
RE: Rethinking asyn motor drivers matthew.pearson
- 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: EDM GUI disable/enable Ralph Lange
- Next:
displaying areaDetector Video with EDM or MEDM John Dobbins
- 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
|