RE: StreamDevice and AMSG field

[Zimoch Dirk via Tech-talk <tech-talk at aps.anl.gov>]

Hi Dennis

Yes, that field is new and not yet supported by StreamDevice.
The idea of that field is to store clear text error messages together with the alarm status/severity for easier debugging. StreamDevice could use it to store messages like "Parse Error", "Connection lost", "Reply timeout" etc.  
The field is not modifiable by dbPutField and thus neither by caput nor by redirection from a StreamDevice protocol.
As storing something into AMSG uses a totally different method, it would be difficult to make it writable by redirections.

Dirk

> -----Original Message-----
> From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Neidherr, Dennis
> Dr. via Tech-talk
> Sent: Dienstag, 20. Mai 2025 08:57
> To: tech-talk at aps.anl.gov
> Subject: StreamDevice and AMSG field
> 
> Dear all,
> 
> and again a small question:
> According to the documentation there is a (new?) field called AMSG to store
> alarm (or error) messages. Is this somehow also useable with StreamDevice?
> Because this field is marked as "non-writable", I can not simply redirect errors
> into it like I tried here:
> 
> setAmplitude0 {
>     out ":SOUR1:VOLT %f;:SYST:ERR?";
> 	in "+%(myAgilent:ErrorCode)i,\"No error\"";
> 	# @mismatch { in
> "%(myAgilent:ErrorCode)i,\"%(myAgilent:ErrorMsg)#s\"" }
> 	@mismatch { in "%(myAgilent:ErrorCode)i,\"%(AMSG)#s\"" }
> 	@writetimeout { disconnect; }
> 	@readtimeout { disconnect; }
> 	@replyTimeout { disconnect; }
> }
> 
> I can certainly use another record to store errors but with the AMSG-field this
> would be a more elegant way. So, is there some workaround or have I maybe
> missed something?
> 
> Thanks and
> Greetings Dennis