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> 2025 | 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> 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: CryoTel GT Cooler: different startup and shutdown StreamDevice protocols |
From: | boj via Tech-talk <tech-talk at aps.anl.gov> |
To: | Ralph Lange <ralph.lange at gmx.de>, EPICS Tech Talk <tech-talk at aps.anl.gov> |
Date: | Fri, 24 May 2024 07:38:38 +0200 |
Dear Ralph
Thanks for the suggestion.
I read up om the BO record (I am running 3.15) using the HIGH
field for the "Push bottom" behavior.
As I understand that documentation, the record is processed again
when going low after the specified time.
I guess that will mean that the protocol is executed twice? Any
way to avoid that?
This brings back the problem that the response from the device
depends on its current state
(it is different when going from On -> Off, and from Off ->
Off).
A Simple push bottom that executes an protocol entry ones, will be very usefull for me.
Best
Bo
On Thu, 23 May 2024 at 21:19, boj via Tech-talk <tech-talk at aps.anl.gov> wrote:
I need to send one of the following commands:
SET SSTOP=1
or
SET SSTOP=0
However, the response is different in the two cases.
I think a "BO" record, should be used, but is there anyway I can have
different protocol definitions for the "1" and "0" state?
Alternatively, is there an easy way to separate this into two records?
I would just map the behaviour:Create two protocols for on and off, with hardcoded values and command-specific replies.Use two bo records, push-button style, HIGH=0.1, and connect them to the two protocols.
If you need a switch instead of two push-buttons, add another bo for the switch, FLNKing to a seq record in SELM=specified mode that writes a 1 to the appropriate push-button.
Cheers,
~Ralph