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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: RE: Controlling Eiger 1M with EPICS |
From: | Bruno Martins <[email protected]> |
To: | Mark Rivers <[email protected]> |
Cc: | tech-talk <[email protected]>, [email protected], Sumit Kewalramani <[email protected]> |
Date: | Wed, 3 Oct 2018 12:17:56 -0400 |
Ø Our Eiger firmware version is 1.6.2. The version of ADEiger that we are attempting to use had in one of the RELEASE info files the mention of requiring firmware version 1.6.4+.
The ADEiger documentation here http://cars.uchicago.edu/software/epics/eigerDoc.html says that it has been tested with firmware 1.6.4+. My Eiger 50K has firmware 1.6.6. So I think it is quite possible that the problem is that you are running older firmware.
Mark
From: Jason A . Pattie <[email protected]>
Sent: Tuesday, October 2, 2018 7:15 PM
To: Mark Rivers <[email protected]>
Cc: [email protected]; Sumit Kewalramani <[email protected]>
Subject: Re: RE: Controlling Eiger 1M with EPICS
Hi Mark,
I think I was able to obtain an image using the web interface. I will verify this the next time I'm at the instrument. When running the st.cmd command, the light on the back of the Eiger changes from red to green before spewing errors.
I did a little more digging. Our Eiger firmware version is 1.6.2. The version of ADEiger that we are attempting to use had in one of the RELEASE info files the mention of requiring firmware version 1.6.4+. Do you think this could be our issue? I've downloaded R2-1 which mentions 1.6.2 and am going to attempt to compile it with the areaDetector tree we currently have installed.
Thanks for your help!
On 2018-10-02 18:40 , Mark Rivers Wrote:
Hi Jason,
I had a similar problem with our Eiger 500, but in my case it could only not find link_3 and link_4. This is an expected error on the Eiger 500K because only link_1 and link_2 exist. I fixed the driver for the 500K in this commit:
In your case it is not finding any of the links (link_1 through link_4), probably in the eigerDetector::eigerStatus() function. That does not make sense to me.
Is the detector working otherwise? Can you collect an image?
Mark
From: [email protected] <[email protected]> On Behalf Of Jason A . Pattie
Sent: Tuesday, October 2, 2018 4:19 PM
To: [email protected]
Cc: Sumit Kewalramani <[email protected]>
Subject: Controlling Eiger 1M with EPICS
Hello,
I'm attempting to setup a Dectris Eiger R 1M with EPICS (3.15.5) and have compiled the latest version of asyn, ADSupport, ADCore, and ADEiger driver. Upon running st.cmd, I receive the following errors:
eigerDetectorConfig("EIG", "10.42.41.10", 0, 0)
RestApi::get: [param=description] server returned error code 404
2018/10/02 15:43:48.583 Param[DESCRIPTION]::baseFetch: [param=description] unable to parse json response
[]
2018/10/02 15:43:48.583 Param[DESCRIPTION]::fetch<string>: [param=DESCRIPTION] underlying baseFetch failed
2018/10/02 15:43:48.583 eigerDetector::eigerDetector: Eiger seems to be uninitialized
Initializing... (may take a while)
RestApi::get: [param=link_1] server returned error code 500
2018/10/02 15:44:07.686 Param[LINK_1]::baseFetch: [param=link_1] unable to parse json response
[]
2018/10/02 15:44:07.686 Param[LINK_1]::fetch<int>: [param=LINK_1] underlying baseFetch failed
RestApi::get: [param=link_2] server returned error code 500
2018/10/02 15:44:07.689 Param[LINK_2]::baseFetch: [param=link_2] unable to parse json response
[]
2018/10/02 15:44:07.689 Param[LINK_2]::fetch<int>: [param=LINK_2] underlying baseFetch failed
RestApi::get: [param=link_3] server returned error code 500
2018/10/02 15:44:07.693 Param[LINK_3]::baseFetch: [param=link_3] unable to parse json response
[]
2018/10/02 15:44:07.693 Param[LINK_3]::fetch<int>: [param=LINK_3] underlying baseFetch failed
RestApi::get: [param=link_1] server returned error code 500
2018/10/02 15:44:07.816 Param[LINK_1]::baseFetch: [param=link_1] unable to parse json response
[]
2018/10/02 15:44:07.816 Param[LINK_1]::fetch<int>: [param=LINK_1] underlying baseFetch failed
RestApi::get: [param=link_2] server returned error code 500
2018/10/02 15:44:07.825 Param[LINK_2]::baseFetch: [param=link_2] unable to parse json response
[]
2018/10/02 15:44:07.825 Param[LINK_2]::fetch<int>: [param=LINK_2] underlying baseFetch failed
RestApi::get: [param=link_3] server returned error code 500
2018/10/02 15:44:07.834 Param[LINK_3]::baseFetch: [param=link_3] unable to parse json response
[]
2018/10/02 15:44:07.834 Param[LINK_3]::fetch<int>: [param=LINK_3] underlying baseFetch failed
epics> eigerDetectorConfig("EIG", "$(EIGERIP)", 0, 0)
RestApi::get: [param=link_1] server returned error code 500
2018/10/02 15:44:42.327 Param[LINK_1]::baseFetch: [param=link_1] unable to parse json response
[]
2018/10/02 15:44:42.327 Param[LINK_1]::fetch<int>: [param=LINK_1] underlying baseFetch failed
RestApi::get: [param=link_2] server returned error code 500
2018/10/02 15:44:42.336 Param[LINK_2]::baseFetch: [param=link_2] unable to parse json response
[]
2018/10/02 15:44:42.336 Param[LINK_2]::fetch<int>: [param=LINK_2] underlying baseFetch failed
RestApi::get: [param=link_3] server returned error code 500
2018/10/02 15:44:42.345 Param[LINK_3]::baseFetch: [param=link_3] unable to parse json response
[]
2018/10/02 15:44:42.345 Param[LINK_3]::fetch<int>: [param=LINK_3] underlying baseFetch failed
RestApi::get: [param=link_1] server returned error code 500
2018/10/02 15:44:42.500 Param[LINK_1]::baseFetch: [param=link_1] unable to parse json response
[]
2018/10/02 15:44:42.500 Param[LINK_1]::fetch<int>: [param=LINK_1] underlying baseFetch failed
RestApi::get: [param=link_2] server returned error code 500
2018/10/02 15:44:42.509 Param[LINK_2]::baseFetch: [param=link_2] unable to parse json response
[]
2018/10/02 15:44:42.509 Param[LINK_2]::fetch<int>: [param=LINK_2] underlying baseFetch failed
RestApi::get: [param=link_3] server returned error code 500
2018/10/02 15:44:42.518 Param[LINK_3]::baseFetch: [param=link_3] unable to parse json response
[]
2018/10/02 15:44:42.518 Param[LINK_3]::fetch<int>: [param=LINK_3] underlying baseFetch failed
If you need any other information, please let me know.
Any help figuring this out would be greatly appreciated.
Thank you.
Jason A. Pattie
User Support Specialist Sr.
Molecular Biosciences/MIM/CSGID
Computational Facility Manager - Structural Biology Facility