Re: Controlling Eiger 1M with EPICS

["Jason A . Pattie" <j-pattie@northwestern.edu>]

Ok.  That makes sense.  There is only a single 10Gbit Ethernet cable connecting the Eiger R1M to the DCU computer.

I didn't even think that the firewall could be an issue.  I'll check and get back to you as well as attempt to upgrade medm.

Thanks!

Jason A. Pattie
User Support Specialist Sr.
Molecular Biosciences/MIM/CSGID
Computational Facility Manager - Structural Biology Facility
j-pattie@northwestern.edu

________________________________________
From: Mark Rivers <rivers@cars.uchicago.edu>
Sent: Friday, October 12, 2018 10:31 PM
To: Jason A . Pattie
Cc: Bruno Martins; Sumit Kewalramani; tech-talk
Subject: Re: Controlling Eiger 1M with EPICS

Hi Jason,

How many 10 GigE cables does your Eiger have connecting the detector to the computer? If only one then it makes sense that only LINK_0 is defined.

The white medm screens are probably a separate issue. If you type “dbl” at the IOC prompt do you see the same PV names that are white on the medm screens? If so then you probably have a firewall preventing medm from connecting to the IOC.

It also looks like you should get the latest medm screen from the master branch on Github.  I improved that recently.

Mark


Sent from my iPhone

On Oct 12, 2018, at 5:36 PM, Jason A . Pattie <j-pattie@northwestern.edu<mailto:j-pattie@northwestern.edu>> wrote:


I successfully applied the firmware update to the DCU, and it now shows 1.6.6.  However, we are still in the same boat.  I checked the link_N URLs individually against the DCU's server through my browser, and verified that only link_0 functioned and returned status.  All other links returned a 500 error with a message about not being able to forward properly to an internal proxy.  So, I commented out in the eigerDetector.cpp all lines associated with link(s)_1 through 3 and recompiled.  That eliminated the error messages we were receiving regarding those links and made the output a lot cleaner.  I'm assuming the Eiger R1M only has one link, maybe?


However, medm still displays the same blank info screens (screenshot attached).  Here is the output of st.cmd.  Should we be concerned about the line that states "ServerContext configured with not Providers will do nothing!"?


Thank you all for all your help with this.


$ ./st.cmd
#!../../bin/linux-x86_64/eigerDetectorApp
< envPaths
epicsEnvSet("IOC","iocEiger")
epicsEnvSet("TOP","/home/epics-admin/Documents/areaDetector/ADEiger/iocs/eigerIOC")
epicsEnvSet("ADEIGER","/home/epics-admin/Documents/areaDetector/ADEiger/iocs/eigerIOC/../..")
epicsEnvSet("SUPPORT","/home/epics-admin/Documents")
epicsEnvSet("ASYN","/home/epics-admin/Documents/asyn4-33")
epicsEnvSet("AREA_DETECTOR","/home/epics-admin/Documents/areaDetector")
epicsEnvSet("ADSUPPORT","/home/epics-admin/Documents/areaDetector/ADSupport")
epicsEnvSet("ADCORE","/home/epics-admin/Documents/areaDetector/ADCore")
epicsEnvSet("AUTOSAVE","/home/epics-admin/Documents/synApps_modules/autosave")
epicsEnvSet("EPICS_BASE","/home/epics-admin/Documents/base-3.15.5")
epicsEnvSet("PVA","/home/epics-admin/Documents/EPICS-CPP-4.7.0")
epicsEnvSet("PVCOMMON","/home/epics-admin/Documents/EPICS-CPP-4.7.0/pvCommonCPP")
epicsEnvSet("PVACCESS","/home/epics-admin/Documents/EPICS-CPP-4.7.0/pvAccessCPP")
epicsEnvSet("PVDATA","/home/epics-admin/Documents/EPICS-CPP-4.7.0/pvDataCPP")
epicsEnvSet("PVDATABASE","/home/epics-admin/Documents/EPICS-CPP-4.7.0/pvDatabaseCPP")
epicsEnvSet("NORMATIVETYPES","/home/epics-admin/Documents/EPICS-CPP-4.7.0/normativeTypesCPP")
errlogInit(20000)
dbLoadDatabase("/home/epics-admin/Documents/areaDetector/ADEiger/iocs/eigerIOC/dbd/eigerDetectorApp.dbd")
eigerDetectorApp_registerRecordDeviceDriver(pdbbase)
epicsEnvSet("PREFIX", "13EIG1:")
epicsEnvSet("PORT",   "EIG")
epicsEnvSet("QSIZE",  "20")
epicsEnvSet("XSIZE",  "1030")
epicsEnvSet("YSIZE",  "1065")
epicsEnvSet("NCHANS", "2048")
epicsEnvSet("CBUFFS", "500")
epicsEnvSet("EIGERIP", "10.42.41.10")
epicsEnvSet("EPICS_DB_INCLUDE_PATH", "/home/epics-admin/Documents/areaDetector/ADCore/db")
epicsEnvSet("EPICS_CA_MAX_ARRAY_BYTES", "5000000")
eigerDetectorConfig("EIG", "10.42.41.10", 0, 0)
RestApi::get: [param=description] server returned error code 404
2018/10/12 16:39:58.876 Param[DESCRIPTION]::baseFetch: [param=description] unable to parse json response
[]
2018/10/12 16:39:58.876 Param[DESCRIPTION]::fetch<string>: [param=DESCRIPTION] underlying baseFetch failed
2018/10/12 16:39:58.876 eigerDetector::eigerDetector: Eiger seems to be uninitialized
Initializing... (may take a while)
dbLoadRecords("/home/epics-admin/Documents/areaDetector/ADEiger/iocs/eigerIOC/../../db/eiger.template", "P=13EIG1:,R=cam1:,PORT=EIG,ADDR=0,TIMEOUT=1")
# Debug
#asynSetTraceMask("$(PORT)", 0, 0x11)
# Create a standard arrays plugin
NDStdArraysConfigure("Image1", 5, 0, "EIG", 0, 0)
dbLoadRecords("/home/epics-admin/Documents/areaDetector/ADCore/db/NDStdArrays.template", "P=13EIG1:,R=image1:,PORT=Image1,ADDR=0,TIMEOUT=1,TYPE=Int32,FTVL=LONG,NELEMENTS=1096950, NDARRAY_PORT=EIG")
NDStdArraysConfigure("Image2", 5, 0, "EIG", 1, 0)
dbLoadRecords("/home/epics-admin/Documents/areaDetector/ADCore/db/NDStdArrays.template", "P=13EIG1:,R=image2:,PORT=Image2,ADDR=0,TIMEOUT=1,TYPE=Int32,FTVL=LONG,NELEMENTS=1096950, NDARRAY_PORT=EIG")
# Load all other plugins using commonPlugins.cmd
< /home/epics-admin/Documents/areaDetector/ADCore/iocBoot/commonPlugins.cmd
set_requestfile_path("/home/epics-admin/Documents/areaDetector/ADEiger/iocs/eigerIOC/../../eigerApp/Db")
iocInit()
Starting iocInit
############################################################################
## EPICS R3.15.5
## EPICS Base built Nov 13 2017
############################################################################
2018/10/12 16:40:18.588 asynPortDriver:drvUserCreate: addr=0, cannot find parameter LINK_1
13EIG1:cam1:Link1_RBV devAsynInt32::initCommon drvUserCreate
2018/10/12 16:40:18.588 asynPortDriver:drvUserCreate: addr=0, cannot find parameter LINK_2
13EIG1:cam1:Link2_RBV devAsynInt32::initCommon drvUserCreate
2018/10/12 16:40:18.588 asynPortDriver:drvUserCreate: addr=0, cannot find parameter LINK_3
13EIG1:cam1:Link3_RBV devAsynInt32::initCommon drvUserCreate
cas warning: Configured TCP port was unavailable.
cas warning: Using dynamically assigned TCP port 32859,
cas warning: but now two or more servers share the same UDP port.
cas warning: Depending on your IP kernel this server may not be
cas warning: reachable with UDP unicast (a host's IP in EPICS_CA_ADDR_LIST)
iocRun: All initialization complete
2018-10-12T16:40:19.098 ServerContext configured with not Providers will do nothing!

2018-10-12T16:40:19.099 Using dynamically assigned TCP port 37019.
# Avoid deluge of messages when debugging
#dbpf $(PREFIX)cam1:PoolUsedMem.SCAN Passive
# save things every thirty seconds
create_monitor_set("auto_settings.req", 30, "P=13EIG1:")
save_restore:readReqFile: unable to open file auto_settings.req. Exiting.
epics>


Jason A. Pattie
User Support Specialist Sr.
Molecular Biosciences/MIM/CSGID
Computational Facility Manager - Structural Biology Facility
j-pattie@northwestern.edu<mailto:j-pattie@northwestern.edu>
________________________________
From: Bruno Martins <brunoseivam@gmail.com<mailto:brunoseivam@gmail.com>>
Sent: Wednesday, October 3, 2018 11:17 AM
To: Mark Rivers
Cc: Jason A . Pattie; Sumit Kewalramani; tech-talk
Subject: Re: RE: Controlling Eiger 1M with EPICS

I think that at some point after 1.6.2 Dectris changed "linkN" to "link_N". I think the easiest solution is to update the firmware.

Bruno


On Tue, Oct 2, 2018 at 10:27 PM Mark Rivers <rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>> wrote:

>  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 https://urldefense.proofpoint.com/v2/url?u=http-3A__cars.uchicago.edu_software_epics_eigerDoc.html&d=DwIF-g&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=bSfzhV7igFsQWnjUREPJu5t1fnj-2NeDBg5ngRK2Y80&s=Ari77QPTEjPzRXsLmyOdo7LbVzUu7XNwxjceJh8LBog&e=<https://urldefense.proofpoint.com/v2/url?u=http-3A__cars.uchicago.edu_software_epics_eigerDoc.html&d=DwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=iIC3CmFamYclh9aeWQG1w6GTNSbnhDzIOs95jta-Z3s&s=V43R4qUXCAPFn_j7_W5j-S9EgA_l0DnNKEuCCFyuiyQ&e=> 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 <j-pattie@northwestern.edu<mailto:j-pattie@northwestern.edu>>
Sent: Tuesday, October 2, 2018 7:15 PM
To: Mark Rivers <rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>>
Cc: tech-talk@aps.anl.gov<mailto:tech-talk@aps.anl.gov>; Sumit Kewalramani <s-kewalramani@northwestern.edu<mailto:s-kewalramani@northwestern.edu>>
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<mailto:rivers@cars.uchicago.edu> 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:

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_areaDetector_ADEiger_commit_50e13b24226e6eb702bd88a8dab16ed280c99137-23diff-2Dd1d617fd8427431b5658f2ef750e0a74&d=DwIF-g&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=bSfzhV7igFsQWnjUREPJu5t1fnj-2NeDBg5ngRK2Y80&s=FEaB5dLMy0trKmegUn3FKzoXHgIDv2wmHn6obZaK_0o&e=<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_areaDetector_ADEiger_commit_50e13b24226e6eb702bd88a8dab16ed280c99137-23diff-2Dd1d617fd8427431b5658f2ef750e0a74&d=DwMFAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=m5_753ZtQ8B3DF7znC3CoudhCQj6br_SUcsei_goexg&s=7Qout4EU6K6aP-Wzj6SwnyPpfEhVTF654YhdYvF871E&e=>

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: tech-talk-bounces@aps.anl.gov<mailto:tech-talk-bounces@aps.anl.gov> <tech-talk-bounces@aps.anl.gov<mailto:tech-talk-bounces@aps.anl.gov>> On Behalf Of Jason A . Pattie
Sent: Tuesday, October 2, 2018 4:19 PM
To: tech-talk@aps.anl.gov<mailto:tech-talk@aps.anl.gov>
Cc: Sumit Kewalramani <s-kewalramani@northwestern.edu<mailto:s-kewalramani@northwestern.edu>>
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
j-pattie@northwestern.edu<mailto:j-pattie@northwestern.edu>
<Screenshot from 2018-10-12 17-27-08.png>