Experimental Physics and
| |||||||||||||||
|
I have a question about how the asyn drivers deal with a read timeout, I am working with a device under devAsyn over a serial line through asynOctet. What I am seeing is that devAsyn is dropping or ignoring input on a read. I send a command to the device to start a long 10-120 sec) process, I recive back an ACK and then wait in a loop that calls asynOctet->read, and check the return for errors or a completion notice. This model works most of the time, but if the completion notice arrives durring a the asyn timeoutHandler, then the data is lost. Is this an intended behavior for devAsyn ? Would using a asynOctetSyncIO where I can block solve this ? If so do I need to change my entire device support to use asynOctetSyncIO , or can I have both a Octet and a SyncIO interface to the same device with out interfering with each other? Thanks for any help. --Bill -- Bill Nolan Washington University Medical School Department of Biochemistry 4566 Scott Ave. Mail Stop 8231 St. Louis, Mo 63110 1.314.362.4445 Fax 1.314.362.7183
| ||||||||||||||
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |