Hi Everyone
how do you handle a client writing NaN to an analog record (which
probably happens by accident)? My intuition tells me that the proper
response for the record is to go into an INVALID status, but apparently
this is not what happens by default...
The problem with accepting NaN is that subsequent tests (e.g. via calc
or sub record) may give wrong results, perhaps leading to motors
starting to move when they should not (it happened to us, which is the
reason why I write this).
Cheers
Ben
--
"Make it so they have to reboot after every typo." â Scott Adams
________________________________
Helmholtz-Zentrum Berlin für Materialien und Energie GmbH
Mitglied der Hermann von Helmholtz-Gemeinschaft Deutscher Forschungszentren e.V.
Aufsichtsrat: Vorsitzender Prof. Dr. Dr. h.c. mult. Joachim Treusch, stv. Vorsitzende Dr. Beatrix Vierkorn-Rudolph
Geschäftsführung: Prof. Dr. Anke Rita Kaysser-Pyzalla, Thomas Frederking
Sitz Berlin, AG Charlottenburg, 89 HRB 5583
Postadresse:
Hahn-Meitner-Platz 1
D-14109 Berlin
http://www.helmholtz-berlin.de
- Replies:
- Re: NaN and analog records Goetz Pfeiffer
- Re: NaN and analog records Ralph Lange
- Re: NaN and analog records Andrew Johnson
- Navigate by Date:
- Prev:
Re: Discussion about licenses, copyrights, business, and source code Benjamin Franksen
- Next:
Re: Problems with Dynamic Array population Benjamin Franksen
- 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: waveform with single element Vishnu Patel
- Next:
Re: NaN and analog records Goetz Pfeiffer
- 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
|