This is interesting. When I wrote the "named Events" feature some years
ago, I tested with something like 2 which became "2" and all was fine.
However I never thought about generating the value from a calc. This
should be fixed, or at least "2.000000" and "2" should be treated as equal.
I will start working on it...
Dirk
On 30.01.2018 17:20, Simon Reiter wrote:
Thanks so far.
postEvent 2
works fine.
Up to now, my event record has an INP field, which links to a calc record.
This calc record only provides the correct value under some conditions.
How can I do this without using a state machine?
record(calc,"$(BOARDNAME):ErrorFlags:calc")
{
field(INPA, "$(BOARDNAME):InitDone:S CPP")
field(CALC, "A ? 2 : 0")
}
record(event, "$(BOARDNAME):ErrorFlags:trg")
{
field(INP, "$(BOARDNAME):ErrorFlags:calc CPP")
}
This is my current code. The value of event is now 2.000000 in the
correct case.
- Replies:
- Re: Scanning on event number fails with EPICS 3.16 Dirk Zimoch
- References:
- Scanning on event number fails with EPICS 3.16 Simon Reiter
- Re: Scanning on event number fails with EPICS 3.16 Benjamin Franksen
- Re: Scanning on event number fails with EPICS 3.16 Simon Reiter
- Navigate by Date:
- Prev:
Re: procServ under systemd service Ralph Lange
- Next:
Data format using NDFileHDF5 steve.kinder
- 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:
Re: Scanning on event number fails with EPICS 3.16 Simon Reiter
- Next:
Re: Scanning on event number fails with EPICS 3.16 Dirk Zimoch
- 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
|