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  <20172018  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  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Problem when formating a field as HEX32
From: Pilar Gil Jaldo <[email protected]>
To: "[email protected]" <[email protected]>
Date: Tue, 14 Nov 2017 11:17:01 +0100
Dear all,

I am having following problem.

MaskSet is a 32 double variable:

record(ao, "$(user):MaskSet")
{
    field(DTYP ,"asynInt32")
    field(OUT  ,"@asyn($(PORT),$(ADDR),$(TIMEOUT))mask")
    field(LOPR, 0x00000000)
    field(HOPR, 0x7FFFFFFF)
    field(PINI, "YES")
}

For the CSS/BOY,  I have defined a text input field which makes possible to change the value of this field.
When I set "Default" as format type of the field, everything works fine.
The problem comes when changing the format type to "HEX32". In this case,  it is not possible to control the introduced value to the set field.

For example,

if we introduce 0xFFFFFF7, after pressing Enter, the value changes automatically to 0xFFFFFF0.
Or when 0x800007F ->  the input value changes to 0x8000080.

If now,  I change the format type to "Default" again and introduce the value 134217855 ( 0x800007F as decimal) every works as it should.

Have somebody an idea of what is happening?

Kind regards,
Pilar Gil


Replies:
Re: Problem when formating a field as HEX32 Kasemir, Kay
RE: Problem when formating a field as HEX32 Mark Rivers

Navigate by Date:
Prev: Re: areaDetector and HDF5 file saving segafaults Hinko Kocevar
Next: Re: areaDetector and HDF5 file saving segafaults Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: EPICS communication paradigm bob dalesio
Next: Re: Problem when formating a field as HEX32 Kasemir, Kay
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
ANJ, 21 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·