EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  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  2017  2018  2019  2020  2021  <2022>  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: Octal escape sequence translation issue in base 7.0.6.1?
From: Andrew Johnson via Tech-talk <tech-talk at aps.anl.gov>
To: tech-talk at aps.anl.gov
Date: Tue, 17 May 2022 16:34:28 -0500
Hi Mark,

On 5/17/22 4:17 PM, Mark Rivers via Tech-talk wrote:

Folks,

 

I just switched to using base 7.0.6.1 on my beamlines.  When I try to start a Pilatus detector I get this error:

 

# Set the input and output terminators.

asynOctetSetInputEos("camserver", 0, "\030")

Set EOS failed: camserver illegal eoslen 3

 

It appears that it is interpreting the escape sequence \030 as a string of 3 characters rather than as a single character.  Is this a bug in base 7.0.6.1 or a problem with my syntax?  This used to work fine with base 7.0.4, I have not changed anything.


I assume iocsh is using epicsString.h functions to interpret the escapes inside parameters, these changes appeared in EPICS 7.0.5:

Character Escape Changes

  • The libCom routines epicsStrnRawFromEscaped() and dbTranslateEscape() declared in epicsString.h no longer accept octal escaped characters such as \123 or \41.
  • The routine epicsStrnEscapedFromRaw() now generates hex excaped characters for unprintable characters such as \x1f.
  • Hex escape character sequences \xXX must now contain exactly 2 hex digits.
  • An escape sequence \0 now generates a zero byte in the raw string, but the other digits 1-9 should not appear after a back-slash.

These changes are to more closely follow the JSON5 standard, which doesn't support octal character escapes or the \a (Bel, \x07) escape sequence.


2-digit hex \xXX escapes should work fine on both sides of the change.

- Andrew

-- 
Complexity is free, it's Simplicity that takes work.
Replies:
Re: Octal escape sequence translation issue in base 7.0.6.1? Wlodek, Jakub via Tech-talk
References:
Octal escape sequence translation issue in base 7.0.6.1? Mark Rivers via Tech-talk
Navigate by Date:
Prev: Octal escape sequence translation issue in base 7.0.6.1? Mark Rivers via Tech-talk
Next: Re: Octal escape sequence translation issue in base 7.0.6.1? Wlodek, Jakub via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024 
Navigate by Thread:
Prev: Octal escape sequence translation issue in base 7.0.6.1? Mark Rivers via Tech-talk
Next: Re: Octal escape sequence translation issue in base 7.0.6.1? Wlodek, Jakub via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024 
ANJ, 14 Sep 2022 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·