Re: Changing the Timeout for drvAsynSerialPort?

[Franklin Fuller <fdfuller@lbl.gov>]

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 <wenorum@lbl.gov> 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 <rivers@cars.uchicago.edu> 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
wenorum@lbl.gov