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: ADEiger R3-12-1 TriggerMode Puzzle
From: John Dobbins via Tech-talk <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Tue, 5 Jul 2022 15:09:44 +0000
All,

I had been using ADEiger R2-7 with an EIGER2 and saw in the release notes for R2-8 a fix for a problem I observed:

Fixed a problem that occurs with 2020.2.2 firmware on the Eiger2.
Changing the TriggerMode to Internal Enable ("inte") or External Enable ("exte") fails if NumImages is not 1. The driver was changed to set NumImages=1 just before changing TriggerMode to either of these values.

I have updated to ADEiger R3-12-1 and still see this behavior, so I am puzzled. 

i.e. if NumImages ~= 1, then trying to set TriggerMode = InternalEnable or ExternalEnable generates error messages at the IOC console

epics> RestApi::put: [param=trigger_mode] server returned error code 400
2022/07/05 10:52:16.546 Param[TRIGGER_MODE]::basePut: [param=TRIGGER_MODE] underlying RestAPI put failed
2022/07/05 10:52:16.546 Param[TRIGGER_MODE]::put<int>: [param=TRIGGER_MODE] underlying basePut failed
2022/07/05 10:52:16.546 eigerDetector::writeInt32: error status=1 function=81, value=1
2022/07/05 10:52:16.546 EIG500:EIG:TriggerMode devAsynInt32::processCallbackOutput process write error


Did I go wrong somewhere?

EIGER2 Firmware Version   release-2020.2.6
SDK version                            1.8.0
Driver Version                        3.4.0
ADCore versioin                     3.12.1



Another question: I see that the readback for various PVs display on the MEDM screen in yellow. They have .STAT = STATE. Looking at the MEDm screen shots in the ADEiger documentation this appears to be intentional. 

EIG500:EIG:Threshold1Enable_RBV
EIG500:EIG:FWEnable_RBV
EIG500:EIG:FlatfieldApplied_RBV
EIG500:EIG:CountrateCorrApplied_RBV
EIG500:EIG:PixelMaskApplied_RBV
EIG500:EIG:AutoSummation_RBV
EIG500:EIG:ArrayCallbacks_RBV


Thanks,

John Dobbins

Research Support Specialist
Cornell High Energy Synchrotron Source
Cornell University





Replies:
RE: ADEiger R3-12-1 TriggerMode Puzzle Mark Rivers via Tech-talk

Navigate by Date:
Prev: Re: EPICS IOC BOOTP timeout at RTEMS on MVME6100 Heinz Junkes via Tech-talk
Next: RE: ADEiger R3-12-1 TriggerMode Puzzle Mark Rivers 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: Doubts about DISS field Andrew Johnson via Tech-talk
Next: RE: ADEiger R3-12-1 TriggerMode Puzzle Mark Rivers 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 ·