EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Streamdevice: wild card in InTerminator?
From: Maren Purves <[email protected]>
To: [email protected]
Date: Thu, 16 Mar 2017 10:07:24 -1000
Agree, is there a way of turning echo off?
(I know there was with Emulex Terminal servers :) )
How is the device connected? It may not be a setting in the
device itself but in whatever it is connected through.

Maren

On 03/16/17 04:42, Mooney, Tim M. wrote:
I'll bet that "53210A>" is a command prompt, intended to be helpful for manual operation.
You should be able to turn it off.  I'd try the SYSTem:COMMunicate:LAN:TELNet:PROMpt command.

Tim Mooney ([email protected]) (630)252-5417
Beamline Controls Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab


________________________________________
From: [email protected] [[email protected]] on behalf of Pearson, Matthew R. [[email protected]]
Sent: Thursday, March 16, 2017 8:47 AM
To: Brown, Garth
Cc: [email protected] list
Subject: Re: Streamdevice: wild card in InTerminator?

Hi,

Is there a way to modify the termination characters that the device sends back?

I’ve used an 53220A before and all it used was a ‘\n’ as it’s terminator. That was a few years ago, so firmware could have changed. But the user manual states that the SCPI terminator used is the new line character. So it’s strange that it’s sending back so much text at the end of the command.

Cheers,
Matt

Data Acquisition and Control Engineer
Spallation Neutron Source
Oak Ridge National Lab


On Mar 15, 2017, at 7:37 PM, Brown, Garth <[email protected]> wrote:

We have a 53210A frequency counter that adds "\r\n53210A> " at the end of its responses. So we specified that as the InTerminator. That worked fine until we got a 53220A. We'd like to use both of them with as little redundant code as possible. The only difference in the protocol is that 1 vs. 2 in the response. Is there a way to accommodate that small difference?
Selected lines from the protocol file:

#
InTerminator  = "\r\n53210A>";
OutTerminator = CR LF;
GET_FREQ            { out "READ?";              in "READ?\r\n%E";}

Messages from asyn related to this:
2017/03/15 16:34:21.577672 agilFC2 FCNT:AS01:1:FREQ_RBCK_RAW: Timeout after reading 39 bytes "...54132E+008<0d><0a>53220A> "
2017/03/15 16:34:22.239 diag-as01-ls02:5024 write 7
READ?\r\n
2017/03/15 16:34:22.240 diag-as01-ls02:5024 read 7
READ?\r\n
2017/03/15 16:34:22.581 diag-as01-ls02:5024 read 32
+1.18999946460060E+008\r\n53220A>
2017/03/15 16:34:27.585987 agilFC2 FCNT:AS01:1:FREQ_RBCK_RAW: Timeout after reading 39 bytes "...60060E+008<0d><0a>53220A> "

Garth







Replies:
Re: Streamdevice: wild card in InTerminator? Takashi OBINA
References:
Streamdevice: wild card in InTerminator? Brown, Garth
Re: Streamdevice: wild card in InTerminator? Pearson, Matthew R.
RE: Streamdevice: wild card in InTerminator? Mooney, Tim M.

Navigate by Date:
Prev: RE: Asyn 4-30 Problem on Arm processor Mark Rivers
Next: Re: Streamdevice: wild card in InTerminator? Takashi OBINA
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Streamdevice: wild card in InTerminator? Torsten Bögershausen
Next: Re: Streamdevice: wild card in InTerminator? Takashi OBINA
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024