EPICS Controls Argonne National Laboratory

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  2017  2018  2019  2020  2021  <20222023  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  <20222023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Unknown error with an equipment
From: Andrew Johnson via Tech-talk <tech-talk at aps.anl.gov>
To: TONY YU <tonyyucom at gmail.com>, Mark Rivers <rivers at cars.uchicago.edu>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Thu, 17 Mar 2022 15:11:57 -0500
Hi Tony,

The error messages you posted ought to be self-explanatory if you read them in order:

> error:
> IDEA ImpMik:IDEA:Status: Input "#31 hv error detect" mismatch after 4 bytes
> IDEA ImpMik:IDEA:Status: got "hv error detect" where "ok" was expected
> IDEA ImpMik:IDEA:SetFilterOn: Input "#2E impossible, erro" mismatch after 1 byte
> IDEA ImpMik:IDEA:SetFilterOn: got "2E impossible, error" where "0" was expected

Your protocol for reading the status from the device says:

> #
> # Get_Status
> #
> Get_Status {
>     out "Get status";
>     in  "#%2i ok";
>     out "ver";
>     in "EFC_for_NanoESCA V01.03 B0115";
>     out "Set mode remote";
>     in "#04 remote mode";
> }

Thus you're telling StreamDevice that after it sends a "Get status" string, it will get back "#" followed by a 2-digit integer and the word "ok". The first two error message lines explain that instead of "ok" it's seeing the string "hv error detect". Have you looked at the instrument that it's talking to? I would guess there's a problem with some high voltage signal that it isn't seeing. You should probably fix the protocol file so it can accept error strings like that from the device and make them available in a stringin record instead of always assuming that the instrument is working and will never give you an error, but you might be able to resolve your immediate issue by fixing whatever the instrument is complaining about.

Always fix your first error first, then look at any error messages you get in that state — later errors are often caused by earlier ones and may go away once you've fixed the first problem.

HTH,

- Andrew
-- 
Complexity is free, it's Simplicity that takes work.

Replies:
Re: Unknown error with an equipment TONY YU via Tech-talk
References:
Unknown error with an equipment TONY YU via Tech-talk
Re: Unknown error with an equipment Mark Rivers via Tech-talk
Re: Unknown error with an equipment TONY YU via Tech-talk

Navigate by Date:
Prev: Re: Unknown error with an equipment Mark Rivers via Tech-talk
Next: RE: Epics Archiver Appliance and Network Storage slowdown Manoussakis, Adamandios 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  <20222023  2024 
Navigate by Thread:
Prev: Re: Unknown error with an equipment Mark Rivers via Tech-talk
Next: Re: Unknown error with an equipment TONY YU 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  <20222023  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 ·