RE: ADEiger R3-12-1 TriggerMode Puzzle

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

Hi John,

 

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

 

I just tested and there is indeed a bug.  When you select TriggerMode=Internal Enable or External Enable it should first set NumImages=1 before setting the TriggerMode.  That worked in R3-0 to R3-3.  I broke it in R3-4 during the refactoring to support TriggerMode=Continuous.

 

I have fixed it on the master branch and tested with an Eiger2 detector.

 

Ø  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. 

 

Yes, that is intentional.  I use the Minor alarm state to indicate when a feature is enabled or disabled.  That makes it easy to see at a glance by color (yellow in medm), rather than having to read the string value.  I reserve Major alarm (red in medm) for real errors/problems.

 

Mark

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of John Dobbins via Tech-talk
Sent: Tuesday, July 5, 2022 10:10 AM
To: tech-talk at aps.anl.gov
Subject: ADEiger R3-12-1 TriggerMode Puzzle

 

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

 

www.chess.cornell.edu