Experimental Physics and
Industrial Control System

My apologies, I just took a closer look at your screen.  You do have the latest version, but it looks wrong because your fonts are a different size.

I am using the file extensions/src/medm/medm/fonts.alias.sun for my font alias file.  Your fonts are larger, which is why they don’t fit.

Mark

On 2018-11-02 20:44 , Mark Rivers Wrote:

Did you also do this?

git pull

That is necessary to get the latest version of master from Github? “git checkout” is a local operation in the repository currently on your system.

Mark


Sent from my iPhone

On Nov 2, 2018, at 7:48 PM, Jason A . Pattie <[email protected]<mailto:[email protected]>> wrote:

Hi Mark,

I'm pretty sure I used:

cd areaDetector/ADEiger
git checkout master

Is there something more I'm missing?

Thanks.




On 2018-11-02 19:30 , Mark Rivers<mailto:[email protected]> Wrote:


Hi Jason,



You should not get the HDF5 decompression errors if you set your DataSource to Stream.  It only needs to decompress the HDF5 files if you set DataSource to FileWriter.  I would not recommend doing that, because then you need to wait for a file to be complete to see the data in areaDetector.



You are still using the old version of the adl file.  The new version in the master branch on Github looks like this.



[cid:[email protected]]



Mark







-----Original Message-----
From: Jason A . Pattie <[email protected]<mailto:[email protected]>>
Sent: Friday, November 2, 2018 2:40 PM
To: [email protected]<mailto:[email protected]>; Mark Rivers <[email protected]<mailto:[email protected]>>
Cc: tech-talk <[email protected]<mailto:[email protected]>>; Sumit Kewalramani <[email protected]<mailto:[email protected]>>
Subject: Re: Re: Controlling Eiger 1M with EPICS



I think we're almost pretty much there.  After going over the installation steps precisely as outlined and overcoming a compilation error which seems to have something to do with the include files for asyn not being seen properly by areaDetector when it is not placed in the support directory of synApps, everything compiled and launched properly.  See attached medm image.  I'm still getting the HDF5 decompression errors, so I will work on implementing Ulrik's suggestions.



Thanks everyone!



Jason A. Pattie

User Support Specialist Sr.

Molecular Biosciences/MIM/CSGID

Computational Facility Manager - Structural Biology Facility

[email protected]<mailto:[email protected]>



________________________________________

From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>

Sent: Friday, November 2, 2018 3:38 AM

To: Jason A . Pattie; Mark Rivers

Cc: tech-talk; Sumit Kewalramani

Subject: Re: Re: Controlling Eiger 1M with EPICS



Hi Jason, Mark,





Regarding the HDF5 filter pipeline errors:





"The above errors are coming because you are telling the Eiger server to save the HDF5 files with lz4 compression, but the areaDetector driver is not configured to read that compressed format.  You need to either save uncompressed, or not try to read the HDF5 files back into areaDetector.  You can get the data into areaDetector using the stream interface rather than via the HDF5 files."



Actually you probably *can* read in the compressed files in areaDetector. The filter pipeline is a feature of the HDF5 group and the LZ4 filter is a "user defined" filter<https://urldefense.proofpoint.com/v2/url?u=https-3A__support.hdfgroup.org_HDF5_doc_H5.user_Filters.html&d=DwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=RK9bzw3LWaAqfh4Y495cwqErHKDaPaWwDJSX_GlPCFI&s=xYvqjvt4bMGYVgrIafhdJpogW39gvmjAUhcxmwlvp8U&e=>, which can be dynamically loaded by the reading (or writing) application by pointing an environment variable (HDF5_PLUGIN_PATH) to the lz4 hdf5 plugin library installation...





The registerred user-defined filters are recorded by the HDF Group here: https://urldefense.proofpoint.com/v2/url?u=https-3A__support.hdfgroup.org_services_contributions.html&d=DwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=RK9bzw3LWaAqfh4Y495cwqErHKDaPaWwDJSX_GlPCFI&s=sBQ9z3RH5TmoLA6ONoR1QTnFFQUidPQPTSBE_fbI32M&e= and LZ4 is filter no. 32004<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_nexusformat_HDF5-2DExternal-2DFilter-2DPlugins_tree_master_LZ4&d=DwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=RK9bzw3LWaAqfh4Y495cwqErHKDaPaWwDJSX_GlPCFI&s=pCvJpafedSbGsTM6mIURgVRM4YTsR8aOUHzd9OJDSXM&e=>.





However, our experience at Diamond is that the "bitshuffle" filter 32008<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kiyo-2Dmasui_bitshuffle&d=DwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=RK9bzw3LWaAqfh4Y495cwqErHKDaPaWwDJSX_GlPCFI&s=VcGZPtAorLgtRWSrYJ-4wJ6rP6I7n8WFKtrfEpC0iQU&e=> (bslz4 in Eiger terminology) is far superior. It uses LZ4 under the hood as well.





Because we need these filters as well as a few others and the build systems of all of these are quite different and sometimes a little tricky to get to work, we have assembled a collection of these filters that we use at Diamond: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_dls-2Dcontrols_hdf5filters&d=DwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=RK9bzw3LWaAqfh4Y495cwqErHKDaPaWwDJSX_GlPCFI&s=Pzb6yHE8lo3HqvX6nLBbIWU_AN9t82x5byRL2IxHLXM&e= - it comes wrapped in a cmake build system and some instructions on how to install and use. If you install this and set the HDF5_PLUGIN_PATH environment variable before running your IOC, then the areaDetector driver should just work and unpack the images from the HDF5 file.





We use this filters in various applications but have not tried it with the areaDetector and Eiger as we use a different DAQ system. For a really fast detector like the Eiger you may find it difficult for the filters to keep up with the data-rate when uncompressing images on the fly...





Cheers,



Ulrik





----------------------------------------------



Ulrik Kofoed Pedersen



Head of Beamline Controls



Diamond Light Source Ltd



Phone: +44 1235 77 8580





________________________________

From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Jason A . Pattie <[email protected]<mailto:[email protected]>>

Sent: 30 October 2018 18:58

To: Mark Rivers

Cc: tech-talk; Sumit Kewalramani

Subject: Re: Re: Controlling Eiger 1M with EPICS



Got it.  Makes sense.  I was wondering why the interface claimed acquisition was complete almost immediately, even though I had the acquire time set to 10 seconds.  I think the thing to do is to compile the most up-to-date version of areaDetector and make sure that all necessary options are configured to be built.  I read the document you sent me.  I should have time to work on that this week and will get back to you with how that goes.



Thanks for all your help and feedback!



Jason A. Pattie

User Support Specialist Sr.

Molecular Biosciences/MIM/CSGID

Computational Facility Manager - Structural Biology Facility

[email protected]<mailto:[email protected]>



________________________________________

From: Mark Rivers <[email protected]<mailto:[email protected]>>

Sent: Tuesday, October 30, 2018 12:39 PM

To: Jason A . Pattie

Cc: Bruno Martins; Sumit Kewalramani; tech-talk

Subject: RE: Re: Controlling Eiger 1M with EPICS



Hi Jason,



> I replaced "busy" with "bo", and CS-Studio and MEDM now show the Acquire Start Stop buttons, and I was able to collect images from the detector to a local directory on the computer.



That will be an OK workaround for now.  The reason for using the busy record rather than the bo record is so that clients can reliably determine when acquisition is complete.



If a bo record is used then the only way to know when acquisition is complete is to poll the state of the Acquire record.  This is difficult to do in a robust way with polling, because on the initial poll the value might not have yet changed to 1.  With a busy record you can use ca_put_callback, and the callback will not occur until acquisition is actually complete.  With ADCore R3-3 and later this can include waiting for all plugins to also be done.



  #003: ../H5Dchunk.c line 3405 in H5D__chunk_lock(): data pipeline read failed

    major: Data filters

    minor: Filter operation failed

  #004: ../H5Z.c line 1357 in H5Z_pipeline(): required filter 'HDF5 lz4 filter; see https://urldefense.proofpoint.com/v2/url?u=http-3A__www.hdfgroup.org_services_contributions.html&d=DwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=yJUC_1FXlkdUAeYvN9eeKHJaI4SJw-eeai1eswEWcys&s=_A4QklO3_sMN_f-PC4MSsQuDkxUZlhXORd4O-5XL1EA&e=' is not registered



The above errors are coming because you are telling the Eiger server to save the HDF5 files with lz4 compression, but the areaDetector driver is not configured to read that compressed format.  You need to either save uncompressed, or not try to read the HDF5 files back into areaDetector.  You can get the data into areaDetector using the stream interface rather than via the HDF5 files.



Mark





-----Original Message-----

From: Jason A . Pattie <[email protected]<mailto:[email protected]>>

Sent: Friday, October 26, 2018 4:52 PM

To: Mark Rivers <[email protected]<mailto:[email protected]>>

Cc: Bruno Martins <[email protected]<mailto:[email protected]>>; Sumit Kewalramani <[email protected]<mailto:[email protected]>>; tech-talk <[email protected]<mailto:[email protected]>>

Subject: Re: Re: Controlling Eiger 1M with EPICS



I thought I had downloaded the latest .adl files.  I'll try that step again.



I'm the one who modified the ADBase.template file a few weeks ago when troubleshooting the IOC startup script.  It kept emitting the following error:



dbLoadRecords("/home/epics-admin/Documents/areaDetector/ADEiger/iocs/eigerIOC/../../db/eiger.template", "P=13EIG1:,R=cam1:,PORT=EIG,ADDR=0,TIMEOUT=1")

Record "13EIG1:cam1:Acquire" is of unknown type "busy"

Error at or before ")" in path "/home/epics-admin/Documents/areaDetector/ADCore/db"  file "ADBase.template" line 426  in file "/home/epics-admin/Documents/areaDetector/ADEiger/iocs/eigerIOC/../../db/eiger.template" line 5

Error: syntax error



I tracked down the issue to the ADBase.template file and ended up commenting out the "Acquire" definition.



record(busy, "$(P)$(R)Acquire") {

   field(DTYP, "asynInt32")

   field(OUT, "@asyn($(PORT),$(ADDR),$(TIMEOUT))ACQUIRE")

   field(ZNAM, "Done")

   field(ONAM, "Acquire")

   field(VAL,  "0")

}



Thank you for displaying those records.  I replaced "busy" with "bo", and CS-Studio and MEDM now show the Acquire Start Stop buttons, and I was able to collect images from the detector to a local directory on the computer.



Now it looks like the only error message left occurs in the st.cmd console when collecting images.  I'm not sure if it's important or affecting anything:



HDF5-DIAG: Error detected in HDF5 (1.10.1) thread 140223997945600:

  #000: ../H5Dio.c line 171 in H5Dread(): can't read data

    major: Dataset

    minor: Read failed

  #001: ../H5Dio.c line 544 in H5D__read(): can't read data

    major: Dataset

    minor: Read failed

  #002: ../H5Dchunk.c line 2050 in H5D__chunk_read(): unable to read raw data chunk

    major: Low-level I/O

    minor: Read failed

  #003: ../H5Dchunk.c line 3405 in H5D__chunk_lock(): data pipeline read failed

    major: Data filters

    minor: Filter operation failed

  #004: ../H5Z.c line 1357 in H5Z_pipeline(): required filter 'HDF5 lz4 filter; see https://urldefense.proofpoint.com/v2/url?u=http-3A__www.hdfgroup.org_services_contributions.html&d=DwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=yJUC_1FXlkdUAeYvN9eeKHJaI4SJw-eeai1eswEWcys&s=_A4QklO3_sMN_f-PC4MSsQuDkxUZlhXORd4O-5XL1EA&e=' is not registered

    major: Data filters

    minor: Read failed

  #005: ../H5PL.c line 389 in H5PL_load(): search in paths failed

    major: Plugin for dynamically loaded library

    minor: Can't get value

  #006: ../H5PL.c line 747 in H5PL__find(): can't open directory: /usr/local/hdf5/lib/plugin

    major: Plugin for dynamically loaded library

    minor: Can't open directory or file

2018/10/26 16:39:22.899 eigerDetector::parseH5File: couldn't read image



Thanks for assisting us in getting to this point!



Jason A. Pattie

User Support Specialist Sr.

Molecular Biosciences/MIM/CSGID

Computational Facility Manager - Structural Biology Facility [email protected]<mailto:[email protected]> ________________________________________

From: Mark Rivers <[email protected]<mailto:[email protected]>>

Sent: Thursday, October 25, 2018 9:28 PM

To: Jason A . Pattie

Cc: Bruno Martins; Sumit Kewalramani; tech-talk

Subject: Re: Re: Controlling Eiger 1M with EPICS



> I had to edit the variable in the .adl file that defined P from 3EIG to 13EIG.





One normally does have to edit a site-specific top-level medm file.  However, your could also just modify the top-level script to load eigerDetector.adl directly, rather than loading eigerTop.adl.  Put this in the script:





medm -x -macro "P=13EIG1:,R=cam1:" /home/epics-admin/Documents/areaDetector/ADEiger/eigerApp/op/adl/eigerDetector.adl &



From your screen shots I can see that you should really load the latest versions of the Eiger medm files from the master branch.  They fix all of the problems with the widget sizesn, fitting into the correct area, etc.





You said in a previous message that dbl showed Acquire_RBV but not Acquire.  It don't see how that is possible, since they are both defined in ADBase.template, one after the other.





********************************



record(bo, "$(P)$(R)Acquire") {

   field(DTYP, "asynInt32")

   field(OUT, "@asyn($(PORT),$(ADDR=0),$(TIMEOUT=1))ACQUIRE")

   field(ZNAM, "Done")

   field(ONAM, "Acquire")

   field(VAL,  "0")

   field(FLNK, "$(P)$(R)SetAcquireBusy")

   info(asyn:READBACK, "1")

}



record(bi, "$(P)$(R)Acquire_RBV") {

   field(DTYP, "asynInt32")

   field(INP, "@asyn($(PORT),$(ADDR=0),$(TIMEOUT=1))ACQUIRE")

   field(ZNAM, "Done")

   field(ZSV,  "NO_ALARM")

   field(ONAM, "Acquiring")

   field(OSV,  "MINOR")

   field(SCAN, "I/O Intr")

}



********************************





Has someone edited ADBase.template at your site?



Mark











________________________________

From: Jason A . Pattie <[email protected]<mailto:[email protected]>>

Sent: Thursday, October 25, 2018 7:22 PM

To: Mark Rivers

Cc: Bruno Martins; Sumit Kewalramani; tech-talk

Subject: Re: Re: Controlling Eiger 1M with EPICS





I think we're getting closer.  medm now connects.  I had to edit the variable in the .adl file that defined P from 3EIG to 13EIG.  However, Acquire still does not exist.  I checked through all the downloaded sources of ADEiger/eigerApp/Db/eiger.template that I have (latest master from git, R2-1, etc.).  They all begin as you see in the second screenshot.  None of them have "Acquire" defined.





Jason A. Pattie

User Support Specialist Sr.

Molecular Biosciences/MIM/CSGID

Computational Facility Manager - Structural Biology Facility [email protected]<mailto:[email protected]> ________________________________

From: Mark Rivers <[email protected]<mailto:[email protected]>>

Sent: Thursday, October 25, 2018 6:23 PM

To: Jason A . Pattie

Cc: Bruno Martins; Sumit Kewalramani; tech-talk

Subject: RE: Re: Controlling Eiger 1M with EPICS





Hi Jason,







I think I might see your problem with medm.







Ø  medm -x -macro "P=3EIG1:,R=cam1:" /home/epics-admin/Documents/areaDetector/ADEiger/eigerApp/op/adl/eigerTop.adl &







You are passing the macro parameters P and R to eigerTop.adl, but it does not actually use those.  It hardcodes P=3EIG1:,R=cam1: when it loads eigerDetector.adl.







The CSS screenshot you sent has P=13EIG1:, not 3EIG1:.  Is your database loaded with P=13EIG1: or P=3EIG1:?







What happens if you do:







medm -x -macro "P=13EIG1:,R=cam1:" /home/epics-admin/Documents/areaDetector/ADEiger/eigerApp/op/adl/eigerDetector.adl &







On your other problem:







Ø  The Acquire PV is not connected.  I ran 'dbl' at the st.cmd epics> prompt.  The only value in the list that has "Acquire" in the name is "Acquire_RBV".



Ø  There is no standalone Acquire name.  Should there be a different PV associated with the Start and Stop buttons in the .opi file?







Something is wrong, there should always be a record called Acquire in any areaDetector IOC.







These are the first few lines in eiger.template:







****************************************



# Database for the records specific to the Eiger driver



# Bruno Martins



# June 2, 2015







include "ADBase.template"



include "NDFile.template"







record(ao,"$(P)$(R)AcquireTime") {



    field(VAL, "1")



}



****************************************







Note that it loads ADBase.template, which is from ADCore.







ADCore/ADApp/Db/ADBase.template contains these lines:







*************************************************



###################################################################



#  These records control  acquisition start and                   #



#  and stop                                                       #



###################################################################







record(bo, "$(P)$(R)Acquire") {



   field(DTYP, "asynInt32")



   field(OUT, "@asyn($(PORT),$(ADDR=0),$(TIMEOUT=1))ACQUIRE")



   field(ZNAM, "Done")



   field(ONAM, "Acquire")



   field(VAL,  "0")



   field(FLNK, "$(P)$(R)SetAcquireBusy")



   info(asyn:READBACK, "1")



}







record(bi, "$(P)$(R)Acquire_RBV") {



   field(DTYP, "asynInt32")



   field(INP, "@asyn($(PORT),$(ADDR=0),$(TIMEOUT=1))ACQUIRE")



   field(ZNAM, "Done")



   field(ZSV,  "NO_ALARM")



   field(ONAM, "Acquiring")



   field(OSV,  "MINOR")



   field(SCAN, "I/O Intr")



}



*************************************************







So ADBase.template loads a record called $(P)$(R)Acquire.  If that is not present in your IOC then something is wrong.







Mark











From: Jason A . Pattie <[email protected]<mailto:[email protected]>>

Sent: Thursday, October 25, 2018 5:38 PM

To: Mark Rivers <[email protected]<mailto:[email protected]>>

Cc: Bruno Martins <[email protected]<mailto:[email protected]>>; Sumit Kewalramani <[email protected]<mailto:[email protected]>>; tech-talk <[email protected]<mailto:[email protected]>>

Subject: Re: Re: Controlling Eiger 1M with EPICS







There was no whitespace in the variable list that I can see:







$ cat ../adl/medm_eigerTop

#!/bin/bash

#

. ~/.bashrc



#edit

#medm /beamline/epics/support/areaDetector-R2-4/ADEiger/eigerApp/op/adl/eigerTop.adl &



#run

medm -x -macro "P=3EIG1:,R=cam1:" /home/epics-admin/Documents/areaDetector/ADEiger/eigerApp/op/adl/eigerTop.adl &











I attached a screenshot of the running version of CS-Studio.  The Acquire PV is not connected.  I ran 'dbl' at the st.cmd epics> prompt.  The only value in the list that has "Acquire" in the name is "Acquire_RBV".  There is no standalone Acquire name.  Should there be a different PV associated with the Start and Stop buttons in the .opi file?







Thanks.







Jason A. Pattie



User Support Specialist Sr.



Molecular Biosciences/MIM/CSGID



Computational Facility Manager - Structural Biology Facility



[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>



________________________________



From: Jason A . Pattie

Sent: Monday, October 22, 2018 8:23 PM

To: Mark Rivers

Cc: Bruno Martins; Sumit Kewalramani; tech-talk

Subject: Re: Re: Controlling Eiger 1M with EPICS







Using the medm_top script in .../ADEiger/eigerApp/op/adl/ modified with our directory locations.  I didn't touch the $P/$R variables in the script, but I will check for whitespace.











On 2018-10-22 19:41 , Mark Rivers<mailto:[email protected]> Wrote:







The only thing I can think of with medm is that the $(P) or $(R) value you are passing has leading or trailing white space. How are you launching the medm screen?



Mark





Sent from my iPhone



> On Oct 22, 2018, at 6:34 PM, Jason A . Pattie <[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>> wrote:

>

> I downloaded and installed CS-Studio.  I think I got it working somewhat.  I copied the opi files from areaDetector/ADEiger/eigerApp/op/opi/*.opi to the ~/.cs-studio/CSS directory, creating a directory called ADEiger, then launched it with:

>

> $ ~/Projects/cs-studio/cs-studio --launcher.openFile '/CSS/ADEiger/eigerDetector.opi'

>

> After clicking on the areaDetector.opi filename on the left side under CSS/ADEiger, the screen appeared populated with values.  I'll trace MEDM at a later date.

>

> Jason A. Pattie

> User Support Specialist Sr.

> Molecular Biosciences/MIM/CSGID

> Computational Facility Manager - Structural Biology Facility

> [email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>

>

> ________________________________________

> From: Mark Rivers

> <[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>>

> Sent: Friday, October 19, 2018 4:04 PM

> To: Jason A . Pattie

> Cc: Bruno Martins; Sumit Kewalramani; tech-talk

> Subject: Re: Controlling Eiger 1M with EPICS

>

> Those look fine.  I don't understand why medm would not connect.

>

>

> Mark

>

>

>

> ________________________________

> From: Jason A . Pattie

> <[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>>

> Sent: Friday, October 19, 2018 3:52 PM

> To: Mark Rivers

> Cc: Bruno Martins; Sumit Kewalramani; tech-talk

> Subject: Re: Controlling Eiger 1M with EPICS

>

> $ caget 13EIG1:cam1:ADCoreVersion_RBV

> 13EIG1:cam1:ADCoreVersion_RBV  3.2.0

>

> $ cainfo 13EIG1:cam1:ADCoreVersion_RBV 13EIG1:cam1:ADCoreVersion_RBV

>    State:            connected

>    Host:             10.42.41.1:5064

>    Access:           read, write

>    Native data type: DBF_STRING

>    Request type:     DBR_STRING

>    Element count:    1

>

> $ printenv | grep EPICS

> EPICS_DISPLAY_PATH=/home/epics-admin/Documents/synApps_5_8/support/dev

> IocStats-3-1-13/op/adl:/home/epics-admin/Documents/areaDetector/ADADSC

> /adscApp/op/adl:/home/epics-admin/Documents/areaDetector/ADAndor3/ando

> r3App/op/adl:/home/epics-admin/Documents/areaDetector/ADAndor/andorApp

> /op/adl:/home/epics-admin/Documents/areaDetector/ADBruker/brukerApp/op

> /adl:/home/epics-admin/Documents/areaDetector/ADCameraLink/cameralinkA

> pp/op/adl:/home/epics-admin/Documents/areaDetector/ADCore/ADApp/op/adl

> :/home/epics-admin/Documents/areaDetector/ADCSimDetector/ADCSimDetecto

> rApp/op/adl:/home/epics-admin/Documents/areaDetector/ADDexela/dexelaAp

> p/op/adl:/home/epics-admin/Documents/areaDetector/ADEiger-backup-alper

> /eigerApp/op/adl:/home/epics-admin/Documents/areaDetector/ADEiger/eige

> rApp/op/adl:/home/epics-admin/Documents/areaDetector/ADFireWireWin/fir

> ewireWinApp/op/adl:/home/epics-admin/Documents/areaDetector/ADLambda/L

> ambdaApp/op/adl:/home/epics-admin/Documents/areaDetector/ADLightField/

> lightFieldApp/op/adl:/home/epics-admin/Documents/areaDetector/ADmar345

> /mar345App/op/adl:/home/epics-admin/Documents/areaDetector/ADmarCCD/ma

> rCCDApp/op/adl:/home/epics-admin/Documents/areaDetector/ADMerlin/merli

> nApp/op/adl:/home/epics-admin/Documents/areaDetector/ADMythen/mythenAp

> p/op/adl:/home/epics-admin/Documents/areaDetector/ADPCO/pcoApp/op/adl:

> /home/epics-admin/Documents/areaDetector/ADPerkinElmer/perkinElmerApp/

> op/adl:/home/epics-admin/Documents/areaDetector/ADPhotonII/PhotonIIApp

> /op/adl:/home/epics-admin/Documents/areaDetector/ADPICam/PICamApp/op/a

> dl:/home/epics-admin/Documents/areaDetector/ADPilatus/pilatusApp/op/ad

> l:/home/epics-admin/Documents/areaDetector/ADPixirad/pixiradApp/op/adl

> :/home/epics-admin/Documents/areaDetector/ADPluginEdge/edgeApp/op/adl:

> /home/epics-admin/Documents/areaDetector/ADPointGrey/pointGreyApp/op/a

> dl:/home/epics-admin/Documents/areaDetector/ADProsilica/prosilicaApp/o

> p/adl:/home/epics-admin/Documents/areaDetector/ADPSL/pslApp/op/adl:/ho

> me/epics-admin/Documents/areaDetector/ADPvCam/pvcamApp/op/adl:/home/ep

> ics-admin/Documents/areaDetector/ADQImaging/App/op/adl:/home/epics-adm

> in/Documents/areaDetector/ADRoper/roperApp/op/adl:/home/epics-admin/Do

> cuments/areaDetector/ADSimDetector/simDetectorApp/op/adl:/home/epics-a

> dmin/Documents/areaDetector/ADURL/urlApp/op/adl:/home/epics-admin/Docu

> ments/areaDetector/aravisGigE/aravisGigEApp/op/adl:/home/epics-admin/D

> ocuments/areaDetector/ffmpegServer/ffmpegServerApp/op/adl:/home/epics-

> admin/Documents/areaDetector/firewireDCAM/iocs/example/exampleApp/opi/

> edl:/home/epics-admin/Documents/areaDetector/NDDriverStdArrays/NDDrive

> rStdArraysApp/op/adl:/home/epics-admin/Documents/areaDetector/pvaDrive

> r/pvaDriverApp/op/adl:/home/epics-admin/Documents/asyn4-33/opi/medm:/h

> ome/epics-admin/Documents/asyn4-33/testApp/adl:/home/epics-admin/Docum

> ents/asyn4-33/testArrayRingBufferApp/adl:/home/epics-admin/Documents/a

> syn4-33/testAsynPortDriverApp/adl:/home/epics-admin/Documents/asyn4-33

> /testEpicsApp/adl:/home/epics-admin/Documents/asyn4-33/testErrorsApp/a

> dl:/home/epics-admin/Documents/asyn4-33/testGpibApp/adl:/home/epics-ad

> min/Documents/asyn4-33/testIPServerApp/adl:/home/epics-admin/Documents

> /asyn4-33/testOutputCallbackApp/adl:/home/epics-admin/Documents/asyn4-

> 33/testOutputReadbackApp/adl:/home/epics-admin/Documents/base-3.15.5/s

> rc/ca/legacy/pcas/example/directoryService:/home/epics-admin/Documents

> /base-3.15.5/src/template/base/top/caServerApp:/home/epics-admin/Docum

> ents/base-3.15.5/templates/makeBaseApp/top/caServerApp:/home/epics-adm

> in/Documents/seq-2.2.5/examples/cmdButtons:/home/epics-admin/Documents

> /seq-2.2.5/examples/demo:/home/epics-admin/Documents/synApps_5_8/suppo

> rt/alive-1-0/aliveApp/op/adl:/home/epics-admin/Documents/synApps_5_8/s

> upport/areaDetector-R2-0/ADCore-R2-2/ADApp/op/adl:/home/epics-admin/Do

> cuments/synApps_5_8/support/asyn-4-26/opi/medm:/home/epics-admin/Docum

> ents/synApps_5_8/support/asyn-4-26/testApp/adl:/home/epics-admin/Docum

> ents/synApps_5_8/support/asyn-4-26/testArrayRingBufferApp/adl:/home/ep

> ics-admin/Documents/synApps_5_8/support/asyn-4-26/testAsynPortDriverAp

> p/adl:/home/epics-admin/Documents/synApps_5_8/support/asyn-4-26/testEp

> icsApp/adl:/home/epics-admin/Documents/synApps_5_8/support/asyn-4-26/t

> estErrorsApp/adl:/home/epics-admin/Documents/synApps_5_8/support/asyn-

> 4-26/testGpibApp/adl:/home/epics-admin/Documents/synApps_5_8/support/a

> syn-4-26/testIPServerApp/adl:/home/epics-admin/Documents/synApps_5_8/s

> upport/autosave-5-6-1/asApp/op/adl:/home/epics-admin/Documents/synApps

> _5_8/support/busy-1-6-1/busyApp/op/adl:/home/epics-admin/Documents/syn

> Apps_5_8/support/calc-3-4-2-1/calcApp/op/adl:/home/epics-admin/Documen

> ts/synApps_5_8/support/camac-2-7/camacApp/op/adl:/home/epics-admin/Doc

> uments/synApps_5_8/support/caputRecorder-1-4-2/caputRecorderApp/op/adl

> :/home/epics-admin/Documents/synApps_5_8/support/dac128V-2-8/dac128VAp

> p/op/adl:/home/epics-admin/Documents/synApps_5_8/support/delaygen-1-1-

> 1/delaygenApp/op/adl:/home/epics-admin/Documents/synApps_5_8/support/d

> evIocStats-3-1-13/op/adl:/home/epics-admin/Documents/synApps_5_8/suppo

> rt/dxp-3-4/dxpApp/op/adl:/home/epics-admin/Documents/synApps_5_8/suppo

> rt/ip-2-17/ipApp/op/adl:/home/epics-admin/Documents/synApps_5_8/suppor

> t/ip330-2-8/ip330App/op/adl:/home/epics-admin/Documents/synApps_5_8/su

> pport/ipUnidig-2-10/ipUnidigApp/op/adl:/home/epics-admin/Documents/syn

> Apps_5_8/support/love-3-2-5/loveApp/op/adl:/home/epics-admin/Documents

> /synApps_5_8/support/mca-7-6/mcaApp/op/adl:/home/epics-admin/Documents

> /synApps_5_8/support/measComp-1-1/measCompApp/op/adl:/home/epics-admin

> /Documents/synApps_5_8/support/modbus-2-7/modbusApp/op/adl:/home/epics

> -admin/Documents/synApps_5_8/support/motor-6-9/motorApp/op/adl:/home/e

> pics-admin/Documents/synApps_5_8/support/optics-2-9-3/documentation/fb

> _epid/source:/home/epics-admin/Documents/synApps_5_8/support/optics-2-

> 9-3/opticsApp/op/adl:/home/epics-admin/Documents/synApps_5_8/support/q

> uadEM-5-0/quadEMApp/op/adl:/home/epics-admin/Documents/synApps_5_8/sup

> port/seq-2-2-1/examples/cmdButtons:/home/epics-admin/Documents/synApps

> _5_8/support/seq-2-2-1/examples/demo:/home/epics-admin/Documents/synAp

> ps_5_8/support/softGlue-2-4-3/softGlueApp/op/adl:/home/epics-admin/Doc

> uments/synApps_5_8/support/sscan-2-10-1/sscanApp/op/adl:/home/epics-ad

> min/Documents/synApps_5_8/support/std-3-4/stdApp/op/adl:/home/epics-ad

> min/Documents/synApps_5_8/support/stream-2-6a/streamDevice/streamApp:/

> home/epics-admin/Documents/synApps_5_8/support/vac-1-5-1/vacApp/op/adl

> :/home/epics-admin/Documents/synApps_5_8/support/vme-2-8-2/vmeApp/op/a

> dl:/home/epics-admin/Documents/synApps_5_8/support/xxx-5-8-3/xxxApp/op

> /adl:/home/epics-admin/Documents/synApps_modules/asyn/opi/medm:/home/e

> pics-admin/Documents/synApps_modules/asyn/testApp/adl:/home/epics-admi

> n/Documents/synApps_modules/asyn/testArrayRingBufferApp/adl:/home/epic

> s-admin/Documents/synApps_modules/asyn/testAsynPortDriverApp/adl:/home

> /epics-admin/Documents/synApps_modules/asyn/testEpicsApp/adl:/home/epi

> cs-admin/Documents/synApps_modules/asyn/testErrorsApp/adl:/home/epics-

> admin/Documents/synApps_modules/asyn/testGpibApp/adl:/home/epics-admin

> /Documents/synApps_modules/asyn/testIPServerApp/adl:/home/epics-admin/

> Documents/synApps_modules/asyn/testOutputCallbackApp/adl:/home/epics-a

> dmin/Documents/synApps_modules/asyn/testOutputReadbackApp/adl:/home/ep

> ics-admin/Documents/synApps_modules/autosave/asApp/op/adl:/home/epics-

> admin/Documents/synApps_modules/busy/busyApp/op/adl:/home/epics-admin/

> Documents/synApps_modules/calc/calcApp/op/adl:/home/epics-admin/Docume

> nts/synApps_modules/seq-2.2.5/examples/cmdButtons:/home/epics-admin/Do

> cuments/synApps_modules/seq-2.2.5/examples/demo:/home/epics-admin/Docu

> ments/synApps_modules/sscan/sscanApp/op/adl

>

> epics> epicsPrtEnvParams

> EPICS_CA_ADDR_LIST is undefined

> EPICS_CA_CONN_TMO: 30.0

> EPICS_CA_AUTO_ADDR_LIST: YES

> EPICS_CA_REPEATER_PORT: 5065

> EPICS_CA_SERVER_PORT: 5064

> EPICS_CA_MAX_ARRAY_BYTES: 5000000

> EPICS_CA_MAX_SEARCH_PERIOD: 300.0

> EPICS_CA_NAME_SERVERS is undefined

> EPICS_CAS_INTF_ADDR_LIST is undefined

> EPICS_CAS_IGNORE_ADDR_LIST is undefined

> EPICS_CAS_AUTO_BEACON_ADDR_LIST is undefined

> EPICS_CAS_BEACON_ADDR_LIST is undefined EPICS_CAS_SERVER_PORT is

> undefined

> EPICS_CA_BEACON_PERIOD: 15.0

> EPICS_CAS_BEACON_PERIOD is undefined

> EPICS_CAS_BEACON_PORT is undefined

> EPICS_BUILD_COMPILER_CLASS: gcc

> EPICS_BUILD_OS_CLASS: Linux

> EPICS_BUILD_TARGET_ARCH: linux-x86_64

> EPICS_TIMEZONE: CST/CDT::360:031302:110602 EPICS_TS_NTP_INET is

> undefined

> EPICS_IOC_LOG_PORT: 7004

> EPICS_IOC_LOG_INET is undefined

> EPICS_IOC_LOG_FILE_LIMIT: 1000000

> EPICS_IOC_LOG_FILE_NAME is undefined

> EPICS_IOC_LOG_FILE_COMMAND is undefined EPICS_CMD_PROTO_PORT is

> undefined

> EPICS_AR_PORT: 7002

> IOCSH_PS1: epics>

> IOCSH_HISTSIZE: 50

>

> Jason A. Pattie

> User Support Specialist Sr.

> Molecular Biosciences/MIM/CSGID

> Computational Facility Manager - Structural Biology Facility

> [email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>

>

> ________________________________________

> From: Mark Rivers

> <[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>>

> Sent: Friday, October 19, 2018 3:28 PM

> To: Jason A . Pattie

> Cc: Bruno Martins; Sumit Kewalramani; tech-talk

> Subject: Re: Controlling Eiger 1M with EPICS

>

> Hi Jason,

>

>

> Please run the caget and cainfo utilities from EPICS base to read those PVs.   I have never had the experience of caget being able to see a PV but medm not being able to see it.

>

>

> medm does not use Python at all.  It only uses the C Channel Access interface from EPICS base.

>

> Please also send the output of the following on the same console where you will run medm.

>

> printenv | grep EPICS

>

> At the IOC prompt please send the output of this command:

> epicsPrtEnvParams

>

> Mark

>

>

> ________________________________

> From: Jason A . Pattie

> <[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>>

> Sent: Friday, October 19, 2018 2:43 PM

> To: Mark Rivers

> Cc: Bruno Martins; Sumit Kewalramani; tech-talk

> Subject: Re: Controlling Eiger 1M with EPICS

>

> Hello,

>

> I've made a few discoveries.  First, iptables lists all three default chains in the ACCEPT state.  I do not believe any firewall rules are applied to the system running EPICS.  /etc/hosts.allow and /etc/hosts.deny have no rules.  So, I don't think there is any security interference preventing TCP/UDP connections on the system.

>

> Second, as you already surmised, all "PV Info" dialogs state that any PV value is in the disconnected state (the reason every PV has a white box instead of a value).  Nothing appears to change with the newer ADEiger/.../op/adl files.  I've been able to target each issue that was emitting errors when running st.cmd, the last one coming down to caRepeater not being available in the PATH for st.cmd (via iocInit()?) to launch automatically.  This removed the output that multiple instances of a server were listening to the same port, since I had previously setup the included caRepeater.service file in systemctl to have caRepeater running all the time.

>

> However, nothing I've tried so far has allowed medm to connect to the IOC.  I have the feeling it has something to do with medm itself or our EPICS installation or the detector interface.  When I used the template Perl CA.pm test script, it connects just fine, and prints out the values of any PV item I provide.  Some of them give errors at the end of the output, though.  I've included some output examples at the end of this message.  I verified that the list of PVs displayed by the 'dbl' command at the "epics>" prompt after running st.cmd match names in the medm interface's white boxes that show disconnected properties when right clicking and selecting PV Info on them.  All PV names tested in the output below were copy/pasted from lines output by 'dbl'.

>

> Does the medm interface use the Python bindings for EPICS at all?  I was going to try the Python test program first, but noticed that our EPICS installation was not compiled with Python included, only Perl.  So, that's why I went with the Perl test program instead.  Should I work on recompiling EPICS and/or MEDM or try to install a different interface?  I read mention of a CS-Studio/Eclipse interface but haven't looked into it, yet.

>

> Thanks to everyone for your patience while wading through these issues with me.

>

> -----Test output-----

>

> $ perl test-pv.pl

>    PV name:       13EIG1:cam1:PortName_RBV

>    Data type:     DBR_STRING

>    Element count: 1

>    Host:          10.42.41.1:5064

>    State:         connected

>    Access:        read, write

>    Value:         EIG

> 13EIG1:cam1:PortName_RBV       ECA_GETFAIL - Channel read request failed

>

> $ perl test-pv.pl

>    PV name:       13EIG1:cam1:FilePerms

>    Data type:     DBR_DOUBLE

>    Element count: 1

>    Host:          10.42.41.1:5064

>    State:         connected

>    Access:        read, write

>    Value:         420

>    Value:         420

>    Severity:

>    Timestamp:     1539730984.104482

>

> $ perl test-pv.pl

>    PV name:       13EIG1:cam1:TimeStamp_RBV

>    Data type:     DBR_DOUBLE

>    Element count: 1

>    Host:          10.42.41.1:5064

>    State:         connected

>    Access:        read, write

>    Value:         0

>    Value:         0

>    Severity:

>    Timestamp:     1539730983.907067

>

> $ perl test-pv.pl

>    PV name:       13EIG1:cam1:PortName_RBV

>    Data type:     DBR_STRING

>    Element count: 1

>    Host:          10.42.41.1:5064

>    State:         connected

>    Access:        read, write

>    Value:         EIG

> 13EIG1:cam1:PortName_RBV       ECA_GETFAIL - Channel read request failed

>

> $ perl test-pv.pl

>    PV name:       13EIG1:cam1:PhotonEnergy

>    Data type:     DBR_DOUBLE

>    Element count: 1

>    Host:          10.42.41.1:5064

>    State:         connected

>    Access:        read, write

>    Value:         8047.77978515625

>    Value:         8047.78

>    Severity:

>    Timestamp:     1539730984.104490

>

> $ perl test-pv.pl

>    PV name:       13EIG1:cam1:Temperature

>    Data type:     DBR_DOUBLE

>    Element count: 1

>    Host:          129.105.37.250:5064

>    State:         connected

>    Access:        read, write

>    Value:         25

>    Value:         25

>    Severity:

>    Timestamp:     1539732428.393049

>

> -----Test script-----

>

> use lib '/home/epics-admin/Documents/base-3.15.5/lib/perl';

> use CA;

>

> my $chan = CA->new('13EIG1:cam1:Temperature');

> #my $chan = CA->new('13EIG1:cam1:AcquireTime');

> #my $chan = CA->new('13EIG1:cam1:PhotonEnergy');

> #my $chan = CA->new('13EIG1:cam1:Gain'); #my $chan =

> CA->new('13EIG1:cam1:FilePerms'); #my $chan =

> CA->new('13EIG1:cam1:TimeStamp_RBV');

> #my $chan = CA->new('13EIG1:image1:PoolMaxMem');

> #my $chan = CA->new('13EIG1:cam1:PortName_RBV');

> #my $chan = CA->new('13EIG1:cam1:DriverVersion_RBV');

> #my $chan = CA->new('13EIG1:cam1:ADCoreVersion_RBV');

> #my $chan = CA->new('13EIG1:cam1:ShutterOpenEPICS');

> #my $chan = CA->new('13EIG1:cam1:ShutterCloseEPICS');

> #my $chan = CA->new('');

> CA->pend_io(1);

>

> my @access = ('no ', '');

> printf "    PV name:       %s\n", $chan->name;

> printf "    Data type:     %s\n", $chan->field_type;

> printf "    Element count: %d\n", $chan->element_count;

> printf "    Host:          %s\n", $chan->host_name;

> printf "    State:         %s\n", $chan->state;

> printf "    Access:        %sread, %swrite\n",

> $access[$chan->read_access], $access[$chan->write_access];

>

> die "PV not found!" unless $chan->is_connected;

>

> $chan->get;

> CA->pend_io(1);

> printf "    Value:         %s\n", $chan->value;

>

> $chan->create_subscription('v', \&callback, 'DBR_TIME_DOUBLE');

> CA->pend_event(10);

>

> sub callback {

>        my ($chan, $status, $data) = @_;

>        if ($status) {

>                printf "%-30s %s\n", $chan->name, $status;

>        } else {

>                printf "    Value:         %g\n", $data->{value};

>                printf "    Severity:      %s\n", $data->{severity};

>                printf "    Timestamp:     %.6f\n",

>                $data->{stamp} + $data->{stamp_fraction};

>        }

> }

>

>

>

> Jason A. Pattie

> User Support Specialist Sr.

> Molecular Biosciences/MIM/CSGID

> Computational Facility Manager - Structural Biology Facility

> [email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>

>

> ________________________________________

> From: Jason A . Pattie

> Sent: Monday, October 15, 2018 1:02 PM

> To: Mark Rivers

> Cc: Bruno Martins; Sumit Kewalramani; tech-talk

> Subject: Re: Controlling Eiger 1M with EPICS

>

> 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

> [email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>

>

> ________________________________________

> From: Mark Rivers

> <[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>>

> 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 <[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]%3cmailto:[email protected]%3cmailto:[email protected]>>>> 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/io

> cs/eigerIOC")

> epicsEnvSet("ADEIGER","/home/epics-admin/Documents/areaDetector/ADEige

> r/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/ADSu

> pport")

> epicsEnvSet("ADCORE","/home/epics-admin/Documents/areaDetector/ADCore"

> )

> epicsEnvSet("AUTOSAVE","/home/epics-admin/Documents/synApps_modules/au

> tosave")

> 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/pv

> CommonCPP")

> epicsEnvSet("PVACCESS","/home/epics-admin/Documents/EPICS-CPP-4.7.0/pv

> AccessCPP")

> epicsEnvSet("PVDATA","/home/epics-admin/Documents/EPICS-CPP-4.7.0/pvDa

> taCPP")

> 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/e

> igerIOC/../../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/NDSt

> dArrays.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/NDSt

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

> [email protected]<mailto:[email protected]<mailto:j-pa<mailto:[email protected]%3cmailto:[email protected]%3cmailto:j-pa>

> [email protected]%3cmailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>>

> ________________________________

> From: Bruno Martins

> <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:brunoseivam

> @gmail.com%3cmailto:[email protected]<mailto:[email protected]>>>>

> 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 <[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]%3cmailto:[email protected]%3cmailto:[email protected]>>>> 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=<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=%3chttps://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<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=%3chttps://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=%3chttps://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=%3chttps://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

> <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:j-p

> [email protected]%3cmailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>>>

> Sent: Tuesday, October 2, 2018 7:15 PM

> To: Mark Rivers

> <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:river

> [email protected]%3cmailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>>>

> Cc:

> [email protected]<mailto:[email protected]<mailto:tech-talk@ap<mailto:[email protected]%3cmailto:[email protected]%3cmailto:tech-talk@ap>

> s.anl.gov<https://urldefense.proofpoint.com/v2/url?u=http-3A__s.anl.gov&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=gLLp6X8BvHFOAIZ5uyCMshxwOcSxLwSxSkKPCrlXND0&s=qKAPSSRrkpQMAwRUYXMk-hIlBEmpX9k1FLKbqboLOKI&e=>%3cmailto:[email protected]<mailto:[email protected]>>>; Sumit Kewalramani

> <[email protected]<mailto:[email protected]><mailto:[email protected]<

> mailto:[email protected]%3cmailto:s-kewalramani@northwest

> ern.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__ern.edu&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=gLLp6X8BvHFOAIZ5uyCMshxwOcSxLwSxSkKPCrlXND0&s=NU-tJtudztjE3koL_HKBrboZlNf0_0tY2MBApbXIEek&e=>>>>

> 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:[email protected]> 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_areaDe

> tector_ADEiger_commit_50e13b24226e6eb702bd88a8dab16ed280c99137-23diff-

> 2Dd1d617fd8427431b5658f2ef750e0a74&d=DwIF-g&c=yHlS04HhBraes5BQ9ueu5zKh

> E7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=bS

> fzhV7igFsQWnjUREPJu5t1fnj-2NeDBg5ngRK2Y80&s=FEaB5dLMy0trKmegUn3FKzoXHg

> IDv2wmHn6obZaK_0o&e=<https://urldefense.proofpoint.com/v2/url?u=https-

> 3A__github.com_areaDetector_ADEiger_commit_50e13b24226e6eb702bd88a8dab

> 16ed280c99137-23diff-2Dd1d617fd8427431b5658f2ef750e0a74&d=DwMFAg&c=yHl

> S04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6

> Zj8BzvIXTi9b2KvA&m=m5_753ZtQ8B3DF7znC3CoudhCQj6br_SUcsei_goexg&s=7Qout

> 4EU6K6aP-Wzj6SwnyPpfEhVTF654YhdYvF871E&e=<https://urldefense.proofpoint.com/v2/url?u=https-3A__urldefense.proofpoin&d=DwIFAw&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=yJUC_1FXlkdUAeYvN9eeKHJaI4SJw-eeai1eswEWcys&s=El5GURD3CdYFQ4_YkWbCW2KWQqVQ8aiVitVWvP3eFSU&e=

> t.com/v2/url?u=https-3A__github.com_areaDetector_ADEiger_commit_50e13b<https://urldefense.proofpoint.com/v2/url?u=http-3A__t.com_v2_url-3Fu-3Dhttps-2D3A-5F-5Fgithub.com-5FareaDetector-5FADEiger-5Fcommit-5F50e13b&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=gLLp6X8BvHFOAIZ5uyCMshxwOcSxLwSxSkKPCrlXND0&s=JvWVTXf_nVH2amzlAqE1Uvy26jrt-HohkGoa95-p9bg&e=>

> 24226e6eb702bd88a8dab16ed280c99137-23diff-2Dd1d617fd8427431b5658f2ef75

> 0e0a74&d=DwIF-g&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSm

> nIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=bSfzhV7igFsQWnjUREPJu5t1fnj-2N

> eDBg5ngRK2Y80&s=FEaB5dLMy0trKmegUn3FKzoXHgIDv2wmHn6obZaK_0o&e=%3chttps

> ://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_areaDetecto<http://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_areaDetecto>

> r_ADEiger_commit_50e13b24226e6eb702bd88a8dab16ed280c99137-23diff-2Dd1d

> 617fd8427431b5658f2ef750e0a74&d=DwMFAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtN

> Xt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=m5_753Z

> tQ8B3DF7znC3CoudhCQj6br_SUcsei_goexg&s=7Qout4EU6K6aP-Wzj6SwnyPpfEhVTF6

> 54YhdYvF871E&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:

> [email protected]<mailto:[email protected]><mailto:[email protected]<mai

> lto:[email protected]<mailto:[email protected]>%3cmailto:[email protected]<mailto:[email protected]>

> ov>>

> <[email protected]<mailto:[email protected]><mailto:[email protected]<ma

> ilto:[email protected]<mailto:[email protected]>%3cmailto:[email protected]<mailto:[email protected]>.

> gov>>> On Behalf Of Jason A . Pattie

> Sent: Tuesday, October 2, 2018 4:19 PM

> To:

> [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:tech-talk@ap

> s.anl.gov<https://urldefense.proofpoint.com/v2/url?u=http-3A__s.anl.gov&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=gLLp6X8BvHFOAIZ5uyCMshxwOcSxLwSxSkKPCrlXND0&s=qKAPSSRrkpQMAwRUYXMk-hIlBEmpX9k1FLKbqboLOKI&e=>%3cmailto:[email protected]<mailto:[email protected]>>>

> Cc: Sumit Kewalramani

> <[email protected]<mailto:[email protected]><mailto:[email protected]<

> mailto:[email protected]%3cmailto:s-kewalramani@northwest

> ern.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__ern.edu&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=xHxpSmnIlNLPkyDYhm0GW22Qmb6Zj8BzvIXTi9b2KvA&m=gLLp6X8BvHFOAIZ5uyCMshxwOcSxLwSxSkKPCrlXND0&s=NU-tJtudztjE3koL_HKBrboZlNf0_0tY2MBApbXIEek&e=>>>>

> 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

> [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:j-pa

> [email protected]<mailto:[email protected]>%3cmailto:[email protected]<mailto:[email protected]>>>

> <Screenshot from 2018-10-12 17-27-08.png> <Screenshot from 2018-10-22

> 17-28-20.png>



--

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.

Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.

Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.

Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom