Experimental Physics and
Industrial Control System

Mark Rivers <[email protected]> · Thu, 5 Dec 2013 19:45:08 +0000

Nope, that won't work, because streamDevice does not currently use the asynTrace facility to print error messages.  I've suggested that Dirk change StreamDevice to do this, but it is non-trivial because most of StreamDevice is not aware of asyn, and does not necessarily have access to the required asynUser structure when it needs it.

Mark

________________________________
From: [email protected] [[email protected]] on behalf of Eric Norum [[email protected]]
Sent: Thursday, December 05, 2013 1:41 PM
To: John Dobbins
Cc: EPICS Tech Talk
Subject: Re: StreamDevice "No reply from device" messages

Set the asyn trace flags to 0 for the port in question -- in particular the least-significant-bit which controls error-level messages.
 From the IOC shell
asynSetTraceMask("<port>",-1, 0)
or use an asynRecord and a client of your choice.

On Dec 5, 2013, at 11:33 AM, John Dobbins <[email protected]<mailto:[email protected]>> wrote:

All,

I frequently encounter this situation and am wondering how to best address it:

An IOC will have a device connected via StreamDevice. In my case it is typically a serial device connected though a serial-to-ethernet server. For some reason the serial device is not responding and the IOC console will have frequent "No reply from device" messages making it difficult to use the IOC console.

These messages come from StreamCore which calls error() - defined in StreamError to print to stderr.

I don't see any built in way to redirect these messages. I can imagine various changes but I am wondering what approach others may have taken or might suggest.

Regards,

John Dobbins
Cornell University

epics base R3.14.2
stream 2.5.1
asyn 4.19
linux-x86_64

--
Eric Norum
[email protected]<mailto:[email protected]>

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System