8-ID
  8-ID Beamline logbook mirror, Page 3 of 44  Not logged in ELOG logo
 List |  Find |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    861 Entries 
Goto page Previous  1, 2, 3, 4 ... 42, 43, 44   Next  
ID Date Author Type Category Subject
  834   Wed Mar 23 12:58:46 2022 Eric Dufresne8-ID-EControls8idMZ3 autosave failure at start of WA-XPCS

Lesson learned




8idMZ3 autosave
Narayanan, Suresh <[email protected]>
Tue 3/22/2022 10:00 PM
To: Sullivan, Joseph <[email protected]>; Walsh, Thomas R. <[email protected]>;
Mooney, Tim M. <[email protected]>; Goetze, Kurt <[email protected]>;
Dufresne, Eric <[email protected]>

Hi All,

Yesterday, we found that 8idMZ3 was completely blank, all settings were lost.
We are not sure when it happened as the WAXPCS instrument just started today
this cycle and we did not check earlier.

We had a printout and we manually typed the fields in as they were few of them.
It is not clear where the old autosave files are? There seems to be way too
many circuits that are saved in there.

That said, question for Joe and Tom:

If we trust the printout which makes sense to us functionally, then behavior is not ok.
We seem to be missing a shutter inversion which is not there in the circuit.

Somewhat related to this, last cycle or even before, we were trying to change the 8ide: fast shutter that
is driven by Unidig from its Low/High PV status to Open/Closed to better represent a shutter.
(Tom, please review your notes/email from that period). In that process when Tom was learning how
to set the LOPR and HOPR, things were messed up and it took some effort on your end to restore it
to the Low/High status as Open/Closed never worked although it works in 8idi: and 8idg:. We think
that something might still be messed up here as shutter is opening when are signaling to open.

We have a kludge in our macros to fix this behavior but most of our triggering circuits are broken with this kludge.

Suresh

Re: 8idMZ3 autosave
Sullivan, Joseph <[email protected]>
Tue 3/22/2022 11:21 PM
To:

Mooney, Tim M. <[email protected]>; Narayanan, Suresh <[email protected]>; Walsh, Thomas R. <[email protected]>; Goetze, Kurt <[email protected]>; Dufresne, Eric <[email protected]>

Hi Suresh,



All the microZed (softGlue) IOCs boot from s100dserv.
/net/s100dserv/xorApps/zed/epics/ioc

8idMZ3 autosave files are here:
/net/s100dserv/xorApps/zed/epics/ioc/8idMZ3/iocBoot/ioc8idMZ3/autosave

The IOC’s autosave system is working now.

It has not been saving PV’s because ioc8idMZ3 could not write to it’s settings request file
(built_settings.req) with it first booted (permission problem). I fixed it manually and
reloaded the request file.

Joe

Re: 8idMZ3 autosave
Mooney, Tim M. <[email protected]>
Tue 3/22/2022 11:32 PM
To: Sullivan, Joseph <[email protected]>; Narayanan, Suresh <[email protected]>;
Walsh, Thomas R. <[email protected]>; Goetze, Kurt <[email protected]>; Dufresne, Eric <[email protected]>

Hi Suresh,

All the saved softGlueZynq circuits are here:
/net/s100dserv/xorApps/zed/epics/ioc/8idMZ3/iocBoot/ioc8idMZ3/autosave/*.cfg

Many of those circuits are just samples to give folks ideas on which to build. You can delete the
sample circuits and have a smaller number of circuits that you actually care about in the configMenu
display of softGlueZynq circuits.

Tim Mooney ([email protected]) (630)252-5417
Beamline Controls Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab

RE: 8idMZ3 autosave
Goetze, Kurt <[email protected]>
Wed 3/23/2022 7:35 AM
To: Mooney, Tim M. <[email protected]>; Sullivan, Joseph <[email protected]>;
Narayanan, Suresh <[email protected]>; Walsh, Thomas R. <[email protected]>;
Dufresne, Eric <[email protected]>

If it’s a permissions problem then is was probably there from the start.
My fault Suresh, sorry about that!

Kurt

Re: 8idMZ3 autosave
Narayanan, Suresh <[email protected]>
Wed 3/23/2022 11:18 AM
To: Goetze, Kurt <[email protected]>; Mooney, Tim M. <[email protected]>;
Sullivan, Joseph <[email protected]>; Walsh, Thomas R. <[email protected]>;
Dufresne, Eric <[email protected]>

Hi Tim, Joe, Kurt,

Thanks for clarifying and fixing. It is good to have all the circuits
available in the menu, it was more that we could not find the one we wanted,
maybe that never got saved.

The unsolved problem is, is the fast shutter controls affected in any way.
Can Tom look up his notes on the LOPR etc changes that were attempted last
cycle. Something does not make sense.

Suresh

Fast Shutter.ui Consensus please
  833   Fri Mar 11 18:11:36 2022 Eric Dufresne8-ID GeneralBeamline HardwareCOS for 8-ID says the cylinder is empty at about 150 psi
From: Strzalka, Joe <[email protected]>
Sent: Friday, March 11, 2022 10:07 AM
To: Zhang, Xiaoyi <[email protected]>; DYS_General <[email protected]>;
[email protected] <[email protected]>; Ziegler, Raymond <[email protected]>
Cc: Kastengren, Alan L. <[email protected]>
Subject: RE: Note on helium usage within DYS and TRR - UPDATE

Hi All,

Seems like the COS for 8-ID says the cylinder is empty at about 150 psi, and then draws on
the other cylinder. Does anyone know -- is there a way to lower that setpoint, maybe to 50 psi?

Joe

Re: Note on helium usage within DYS and TRR - UPDATE
Ziegler, Raymond <[email protected]>
Fri 3/11/2022 11:41 AM
To: Strzalka, Joe <[email protected]>; Zhang, Xiaoyi <[email protected]>;
DYS_General <[email protected]>; [email protected] <[email protected]>
Cc: Kastengren, Alan L. <[email protected]>

Good point Joe. I think I had looked into that quite a while ago but came up empty. I'll review my notes
and follow up again. A great idea considering the current circumstances... As a last resort, if you leave
the one low cylinder in place, the COS will eventually use up all possible helium from both cylinders.
Something to consider before swapping a "not so empty" cylinder...

Thanks,
Ray
  832   Tue Mar 1 15:47:10 2022 Eric Dufresne8-ID GeneralDetectorsNew Si BPM from Alibava

PARIS: https://apps.inside.anl.gov/paris/req.jsp?reqNbr=G2-059016
Note that the quote is in the attachement.

Re: quotation for a thin Si BPM and picoammeter
Andrea Mejias Aristeguieta <[email protected]>
Wed 3/2/2022 6:53 AM
To: Dufresne, Eric <[email protected]>
Cc: Juan Herranz <[email protected]>; Info Alibava Systems <[email protected]>;
Alex Navarrete Moraira <[email protected]>

Dear Eric,

Sorry for my late reply.

I was contacting the technical support of Elettra to give you an answer. They gave me the following information:
"With the Picoammeter, we can provide a CE-certified Power Supply. But unfortunately, it isn't NRTL compliant.
Anyhow, if they have its certified power supply, it can be connected to our instrument following the pinout
scheme reported in the Picoammeter User's Manual".

Yesterday, we correctly received the purchase order.

Thank you and best regards,

Andrea Mejías

RE: quotation for a thin Si BPM and picoammeter
Ziegler, Raymond <[email protected]>
Wed 3/2/2022 2:14 PM
To: Dufresne, Eric <[email protected]>; Andrea Mejias Aristeguieta <[email protected]>
Cc: Juan Herranz <[email protected]>; Info Alibava Systems <[email protected]>;
Alex Navarrete Moraira <[email protected]>
1 attachments (4 MB)
PS22xx_Users_Manual.pdf;

Eric,

Thanks for the info…

Question for Alibava,

Can the cover of this power supply be removed? It’s hard to tell from the pictures but as long as this plastic
case can be opened for inspection by removing screws or similar, then it may be allowed as a DEEI inspected device.
If it’s non-NRTL and in a molded (sealed) case, it cannot be used…

Thanks,

Ray

9/13/2022

New Alibava Si X-BPM arrived
We will test this at 28-ID.
Received the Factory Acceptance tests in att. 5.

https://logbook.xray.aps.anl.gov/8id/controls/140 See EPICS controls on 28-ID


9/22/2022

Received wiring diagram in att. 4.
Attachment 1: QA19239_ANL-Dufresne.pdf
Attachment 2: PS22xx_Users_Manual.pdf
Attachment 3: AH501B_UsersManual_v1.3.pdf
Attachment 4: BIM-PICOAMMETER_CABLE.PDF
Attachment 5: 4676_001-FactoryAcceptance.pdf
  831   Wed Feb 16 17:10:08 2022 Eric Dufresne8-ID-ISafety8-ID-I Hutch Door Repair Feb. 28/March 1st
From: Spilker, Matt G <[email protected]>
Date: Wednesday, February 16, 2022 at 12:13 PM
To: Stevens, Andrew <[email protected]>, Lange, Robert G. <[email protected]>, McNamara, Phil <[email protected]>
Cc: VanWingeren, Wendy <[email protected]>, Wayman, Ashley E <[email protected]>, Fieramosca, Bruno G. <[email protected]>,
Clute, Timothy Karl <[email protected]>, Narayanan, Suresh <[email protected]>, Ziegler, Raymond <[email protected]>,
Henry, Michael James <[email protected]>
Subject: 8-ID-I Hutch Door Repair

Hello Everyone,

8-ID-I is experiencing problems with their hutch door making squeaking/crunching noises when opening/closing
which will require some work to be done. Tim Clute from the MOM group checked it out and he told me
that the bearings will likely need to be replaced. This will require Scheck to cut a hole in the shroud
covering at the top of the door for him to remove the old bearings and replace them with new ones. Riggers
will need to lift up the door so that Tim can make the swap. SI should check over the door and its systems
after the work is completed. Health Physics will need to do a type C survey to verify the doors shielding
integrity. Tim believes this will take at least a full day, possibly two days.

After talking with beamline rep Suresh, the best time for them to complete this work without interruptions
on their end would be the upcoming 2 day machine studies period on Feb. 28/March 1st. Ideally we would like
to get this done as soon as possible so as to not risk damaging the rail further but of course all of our
schedules must line up for this to happen.

Andy- would you be able to help coordinate with Scheck and see if they will be available to cut out a
section of the shroud for the repair?

Rob- would you be able to get a crew together to lift the door for repairs?

Mike and Phil- would you be able to have someone take a look at the door after the work is complete?

Thanks,

Matthew Spilker

APS - Floor Coordinator
LOM 435
Argonne National Laboratory
Office: (630) 252-0500
Email: [email protected]

From: Strzalka, Joe <[email protected]>
Date: Thursday, February 17, 2022 at 10:04 AM
To: Narayanan, Suresh <[email protected]>, Zhang, Qingteng <[email protected]>, DYS_General <[email protected]>
Subject: RE: 8-ID-I Hutch Door Repair

Suresh,

I want to make sue I understand the risk. If the door repair takes longer than expected and 8-ID-I
is not operating on Mar 2, then 8-ID-E will also not be able to operate. Is that correct?

Thanks,

Joe

Re: 8-ID-I Hutch Door Repair
Narayanan, Suresh <[email protected]>
Thu 2/17/2022 10:12 AM
To: Strzalka, Joe <[email protected]>; Zhang, Qingteng <[email protected]>; DYS_General <[email protected]>
Joe,

Correct, apparently, the whole sector will be taken offline, reasons not clear to me.

Suresh

Re: 8-ID-I Hutch Door Repair
Narayanan, Suresh <[email protected]>
Thu 2/17/2022 11:35 AM
To: Jensen, Don P., Jr. <[email protected]>; DYS_General <[email protected]>
All,

Here is an explanation on why the whole sector need to be taken offline:

In order to replace the bearings we will likely need to remove the personal safety switches and lock
assemblies that are on the door, these switches relay information on the status of the door to the PSS
(personal safety system). Since we are working with PSS hardware we run the risk of creating a PSS trip
which could cause a storage ring dump, something we would like to avoid. The only way to work on the PSS
system without risking a trip and possible storage ring dump is to take the entire beamline globally offline
which cuts off the communication between the PSS system and the storage ring. Even though the photon shutter
will be closed and the hutch will be APS disabled, this does not turn off the PSS communication with the
rest of the storage ring.

Suresh

Re: BL tours
Narayanan, Suresh <[email protected]>
Sun 2/27/2022 11:14 AM
To: Ziegler, Raymond <[email protected]>;Strzalka, Joe <[email protected]>;Jiang, Zhang <[email protected]>;
Zhang, Qingteng <[email protected]>;Dufresne, Eric <[email protected]>

All,

Monday/Tuesday is the day where 8-ID-I hutch door repair will happen. I have written to the FC letting
them know of the time window where we need access to the hutch for Laurent. FYI…

Suresh

RE: BL tours
Ziegler, Raymond <[email protected]>
Mon 2/28/2022 9:39 AM
To: Narayanan, Suresh <[email protected]>;Jiang, Zhang <[email protected]>;Strzalka, Joe <[email protected]>;
Zhang, Qingteng <[email protected]>;Dufresne, Eric <[email protected]>

Morning update…

The guys are out there now working on the door. I did a cursory cleanup outside the hutch but always
more to be done… No word on their timing for us to get inside the hutch…

Ray
  830   Tue Feb 15 12:06:12 2022 Eric Dufresne8-ID-IEPS8IDI gravity system water flow fault, 2/15/2022
8IDI gravity system water flow fault
Narayanan, Suresh <[email protected]>
Tue 2/15/2022 12:02 PM
To: Wright, Robert <[email protected]>; Collins, Jeffrey T. <[email protected]>; Bechtold, Ralph R. <[email protected]>
Cc: Ziegler, Raymond <[email protected]>; Dufresne, Eric <[email protected]>

All,

We just got a water flow fault in the EPS, flow rate shows 1.74 l/min. Could you please come and take a look?

Thanks.

Suresh

  829   Wed Feb 9 18:22:19 2022 Joseph StrzalkaOffice and LabsDocumentation8-ID Chemistry Lab
Use of the 8-ID chemistry Lab 432E030 requires a valid ESAF. Wear eye protection and other appropriate PPE inside the chemistry lab.

The lab has instrumentation available for users:
a. Leica Zoom 2000 microscope
b. Celestron Digital Microscope Pro
c. Novascan PD4 UV Ozone Cleaner
Attachment 1: zoom_2000.pdf
Attachment 2: CelestronDigitalMicroscopePro.pdf
Attachment 3: NovascanPDUV4ozoneCleaner.pdf
  828   Tue Feb 1 15:53:19 2022 Eric Dufresne8-ID-EUser ManualHow to configure matlab for XPCSGUI2/select_results/specr code to work

Once the code is downloaded to your machine, one needs to update matlab's path

This is shown in attachment 1.
One first opens the Set path window in the Environment tab circled in blue.
Then one must add with subfolder the three subdirectories called:
VIEW_XPCSGUI_RESULTS WAXPCSGUI2 xraylabtool
highlighted in blue that are stored on your machine.

This will not be like /local/xraylab, but will depend on your environment (PC, MAC, linux).

then hit the save button and then close this window.

To run code from the main matlab window, type:
selectresult
specr
xpcsgui

Remember that selectresult uses a *.mat filter, not the default *.hdf file.

ED
Attachment 1: MatlabEnvironmentPath.png
MatlabEnvironmentPath.png
  827   Tue Feb 1 10:38:23 2022 Eric Dufresne8-ID-IImportant Log BooksLogbook notes for 2022-1 for 8-ID-I operation
https://logbook.xray.aps.anl.gov/8id/8-ID/596 Important distances 2018-3
https://logbook.xray.aps.anl.gov/8id/8-ID/674 Lens positions for 1 and 2D focusing
https://logbook.xray.aps.anl.gov/8id/8-ID/701 2020-1 notes
https://logbook.xray.aps.anl.gov/8id/8-ID/721 2020-2 notes
https://logbook.xray.aps.anl.gov/8id/8-ID/744 2020-3 notes
https://logbook.xray.aps.anl.gov/8id/8-ID/761 2021-1 notes
https://logbook.xray.aps.anl.gov/8id/8-ID/761 2021-2 notes
https://logbook.xray.aps.anl.gov/8id/8-ID/827 2022-1 notes

https://anl.app.box.com/folder/130409499261?s=3t71weuketeea2s3xnvoo59tcclxk3dw Handwritten notes

8-ID-I ESAF 2022-1 https://beam.aps.anl.gov/pls/apsweb/esaf0001.start_page?i_attrib=250714

8-ID-E ESAF 2022-1 https://beam.aps.anl.gov/pls/apsweb/esaf0001.start_page?i_attrib=251426

1/27/2022 Report of issue with power cycle on 8ID-A IOC (MaxV card doesn't restore PVs)
See fix https://logbook.xray.aps.anl.gov/8id/8-ID/826

2/1/2022 First day of beamtime 8-ID-I

2/15/2022 Gravity fall water trip/problem
https://logbook.xray.aps.anl.gov/8id/8-ID/830

2/28/2022 8ID-I hutch door repair impacting all of 8ID
https://logbook.xray.aps.anl.gov/8id/8-ID/831

3/22/2022 First day of beamtime in 8ID-E WA-XPCS
I fixed the autoShutter database. For some reasons, it had lost its permit.

Tough day in 8-ID-E. It started with the camera switch being broken.
Then I had no x-rays anywhere, pind3, pind4, etc... so I enventually identified the shutter.
What I should have done was to test the shutter; you can view the shutter open
and close on the viewport.

I finally identified it as a EPICS issue at 5h32. The SG MZ3 unit had losts its
entries. This is described here: https://logbook.xray.aps.anl.gov/8id/8-ID/834
Suresh and I are still thinking there is another problem with the fast shutter EPICS screen
which remains inverted.

4/19/2022

https://logbook.xray.aps.anl.gov/8id/8-ID/838 Displaced the mirror down by 0.5 mm to get back
my flux at 7.35 keV.
  826   Fri Jan 28 18:38:20 2022 Eric Dufresne8-ID GeneralControlsRestoring beamline for operation after shutdown, power shutdown in January, etc...
[1/27/2022 7:16 PM] Dufresne, Eric
Some problem with save/restore on the 8-ID-A IOC.

The WB slits opening should be 2 mm for the vertical gap Sullivan, Joseph. Noted this evening.

[1/28/2022 8:06 AM] Sullivan, Joseph
Dufresne, Eric - Is it ok to do a soft reboot now? The crate should be power cycled.
The MAXv card was not detected with the IOC came up.

[10:19 AM] Sullivan, Joseph
m9-m16 positions will have to be 'Set' - the old positions are not in the autosave files.
Will probably have to pull them from https://ops.aps.anl.gov/logging/8ID.html

[6:33 PM] Dufresne, Eric
Glad to have spoken to Suresh, Sullivan, Joseph. He told me to power off and power on and
it returned all the positions on m9-16. Here is an example below. We should be good to go.
[8ida-m15-Dec21+Jan28.png]
(https://argonnedoe-my.sharepoint.com/personal/dufresne_anl_gov/Documents/Microsoft Teams Chat Files/8ida-m15-Dec21+Jan28.png)

2/1/2022

I reviewed all PVs more accurately with exporting the plots as ascii, per
att 2. Everything looks good on m9-16.
Attachment 1: 8ida-m15-Dec21-Jan28.png
8ida-m15-Dec21-Jan28.png
Attachment 2: Screenshot2022-02-01-094729-8idaIOCrestored.png
Screenshot2022-02-01-094729-8idaIOCrestored.png
  824   Fri Jan 21 15:20:41 2022 Eric Dufresne8-ID-IDetectorsreplacement detector for Rigaku 500K
From: Joseph Ferrara <[email protected]>
Date: Friday, January 7, 2022 at 7:43 AM
To: Narayanan, Suresh <[email protected]>
Subject: replacement detector

Suresh,

I understand the XSPA-500K has been acting up, and my colleagues in Japan are preparing a replacement.
I have been told the replacement should be shipped the week of January 24. Either Taro (Ted) Sera or I
would come to the APS to affect the exchange. Ted worked with Nakaye-san when we installed the detector
in March of 2020, and so has familiarity with the XSPA hardware. Who comes will depend on schedules
and accessibility.

If the detector arrives on time, would the first week of February work for you for the exchange?

Cheers,

Joe

RE: replacement detector
Joseph Ferrara <[email protected]>
Fri 1/21/2022 3:02 PM
To: Narayanan, Suresh <[email protected]>
Cc: Dufresne, Eric <[email protected]>; Zhang, Qingteng <[email protected]>; Miceli, Antonino <[email protected]>
Suresh,

I am sorry it took longer to respond than I promised. The detector will ship from the Rigaku factory no later than February 10.
It will come here for inspection then be forwarded to you. The plan is for our local service engineer, Don Sobczak, to effect the
swap. Don worked with Taro Sera and Nakaye-san back when we installed the XSPA. Don’s Argonne contractor safety training should
be good until 05/12/22. Will this apply to the APS?

Joe

  823   Wed Dec 22 11:56:45 2021 Eric DufresneOtherXPCS-APS-UWhat do you do to initiate PO/SO for APS-U purchased item

The air handling unit for the DHS1100 is broken.
I am sending it back to Anton Paarr for repair.
I've initiated a thread for involving APS-U and ANL Procurement
Find it below.

Question to ask?
  • Is the contract closed?

ED

From: Dufresne, Eric <[email protected]>
Sent: Wednesday, December 22, 2021 9:20 AM
To: Leighton, Michelle L. <[email protected]>
Cc: Mistri, Gayatri K <[email protected]>
Subject: Need to ship something back for repair, part of warranty

Michelle,

some item I received on my DHS1100 oven is defective. I received an RMA.
I need to process a shipping order, and typically I need to use a
Req. along the Ship. Order.

What do I do in these situations?

Eric

From: Dufresne, Eric <[email protected]>
Sent: Wednesday, December 22, 2021 10:32 AM
To: Leighton, Michelle L. <[email protected]>
Cc: Mistri, Gayatri K <[email protected]>
Subject: Re: Need to ship something back for repair, part of warranty

Michelle,

The award is 1A-71342.
Here it is in PARIS:
https://apps.inside.anl.gov/paris/req.jsp?reqNbr=G1-057024.1

Eric

From: Leighton, Michelle L. <[email protected]>
Sent: Wednesday, December 22, 2021 11:14 AM
To: Dufresne, Eric <[email protected]>
Cc: Mistri, Gayatri K <[email protected]>; Kizer, Kelli Trego <[email protected]>; Guerrero, William E <[email protected]>
Subject: RE: Need to ship something back for repair, part of warranty

Eric,

So when returning an item to a vendor due to nonconforming or damage, the buyer needs to initiate the shipping order
so that it is properly backed out of Workday. Kelli Kizer, APS-U Procurement Manager, is currently handling the return
shipping orders and I’ve included her and the original buyer to this email. Can you please specify which line item on
the award 1A-71342 you are sending back and the RMA # the company provided.

Procurement will initiate the shipping order and transfer it to me to completed and I will submit it for approval.
Once I submit it I will send you a copy of the form and you may then take your items to shipping.

Michelle

From: Dufresne, Eric <[email protected]>
Sent: Wednesday, December 22, 2021 11:52 AM
To: Leighton, Michelle L. <[email protected]>
Cc: Mistri, Gayatri K <[email protected]>; Kizer, Kelli Trego <[email protected]>; Guerrero, William E <[email protected]>
Subject: Re: Need to ship something back for repair, part of warranty

Hi Michelle,

I sent you the RMA form in a previous email, it is RMA number: 1444123.
The item number is item 4 in this PO, the Air Service unit.


Eric

RE: Need to ship something back for repair, part of warranty
Kizer, Kelli Trego <[email protected]>
Wed 12/22/2021 11:56 AM
To: Dufresne, Eric <[email protected]>; Leighton, Michelle L. <[email protected]>
Cc: Mistri, Gayatri K <[email protected]>; Guerrero, William E <[email protected]>

I will start the shipping form process now. Thanks!

RE: Need to ship something back for repair, part of warranty
Kizer, Kelli Trego <[email protected]>
Wed 12/22/2021 4:11 PM
To: Dufresne, Eric <[email protected]>; Leighton, Michelle L. <[email protected]>
Cc: Mistri, Gayatri K <[email protected]>; Kizer, Kelli Trego <[email protected]>; Guerrero, William E <[email protected]>
Hi everyone,

I am working on this Shipping Form, however, since this is being sent back on a warranty and the PO is closed out,
I am verifying whether we will need a $0 req to ensure we are tracking items leaving ANL to vendors site and back
to ANL after repair (to reduce risk to ANL). My understanding is receiving can’t track a closed PO, thus we will
need a new req to track the item, but once I verify this, I will let you know.

Thanks,

Kelli

RE: Need to ship something back for repair, part of warranty
Leighton, Michelle L. <[email protected]>
Wed 12/22/2021 4:43 PM
To: Kizer, Kelli Trego <[email protected]>; Dufresne, Eric <[email protected]>
Cc: Mistri, Gayatri K <[email protected]>; Guerrero, William E <[email protected]>
Kelli,

You are correct that since the contract it was purchased under is closed we will need to do a $0
requisition to send it back. I will submit the requisition shortly.

Michelle

PARIS: PARIS - PARIS requisition G1-356041 APS-U 8-ID-E High Temp Cell - Air Service Unit Warrant (XSD) was routed to you on 12/23/2021
Argonne Service Desk <[email protected]>
Thu 12/23/2021 8:31 AM
To: Dufresne, Eric <[email protected]>
PARIS has routed "PARIS requisition G1-356041 APS-U 8-ID-E High Temp Cell - Air Service Unit Warrant (XSD) " for your action.

Reason this was routed to you: Administrative Representative .

Date routed to you: 12/23/2021

Please access PARIS at https://apps.inside.anl.gov/paris/req.jsp?reqNbr=G1-356041 to take appropriate action.

  822   Tue Dec 7 13:57:29 2021 Eric Dufresne8-ID-IComputers and NetworkOdd cache issue with 8idiuser that impacted NX for 8idiuser, other NX stuff
Odd cache issue with 8idiuser
Hoffman, Jeff S <[email protected]>
Tue 12/7/2021 1:23 PM
To: Narayanan, Suresh <[email protected]>; Zhang, Qingteng <[email protected]>; Strzalka, Joe <[email protected]>; Dufresne, Eric <[email protected]>
Cc: Robinson, Brian D. <[email protected]>

Suresh,

When I was at APS yesterday Qingteng showed me the .cache issue that Brian found.
I created a script to work around the issue based on what Brian found.
It is the 8idiuser home directory.

./fixcache.sh will move the wacked out directory out of the way. Then nomachine will work and not exit with a blank screen.

Also, qingteng was trying to run “sudo systemctl restart nxserver”, which won’t work for users 8ide, 8idg and 8ide.
But, “sudo /usr/NX/bin/nxserver --restart” will work for them.

Cheers,

Jeff

On 12/15/21, I copied it in ~8ideuser/bin


  821   Mon Dec 6 16:48:52 2021 Eric Dufresne8-ID-EControlsNew Keysight 33500B Waveform Generator from Detector Pool.
https://logbook.xray.aps.anl.gov/8id/controls/132 Manuals and wait 4-5 min to start IOC

[11/29 4:50 PM] Walsh, Thomas R.
HI Eric, I'm working on it today and will be onsite working on the Keysight waveform generator project.
I found the old proto file and database. It looks like what was used on the Agilent waveform generator should
work on the new Keysight generator. The command list looks like what was used for the Agilent, but there maybe
differences. I noticed something that may answer our "Remote" LAN connection problems with. It takes 4 to 5 minutes
to connect from power up. It must be doing some self testing during that time. At first I thought oh no not this
problem on the new Keysight waveform generator. I got frustrated and worked on another project and about 10 minutes
later I look over and the Keysight waveform Generator was in Remote. So I did a timing test and it took 3 minutes
and 58 seconds from power up to connect with the LAN. This may vary for a warm and cold machine so that is why I
said 4-5 minutes. I'm going to ask Nino and Chris P to test the old Agilent and see if this runs true for them
too. I can't believe it takes that long but I'm glad we know about it.

[12/1 2:05 PM] Walsh, Thomas R.

DP00430 (the DP unit number)

[2:33 PM] Walsh, Thomas R.
Dufresne, Eric Dropping off Keysight 33500B Waveform Generator. I have a sector 8 IP address assiigned (164.54.116.128)
Will you need a network patch cable? Related displays are set in 8ide.ui and there is an alias ioc8idKey33500B to
run stop status ioc.
(1 liked)

which ioc8idKey33500B
ioc8idKey33500B: aliased to $S8_SOFTIOC $EPICS_APP_621/8idKey33500B/iocBoot/ioc8idKey33500B/softioc/8idKey33500B.sh

run: starts a console session
start: runs it in background mode.

https://logbook.xray.aps.anl.gov/8id/8-ID/648 Background and EPICS screens from precursor from Agilent


[6/15/2022 6:15 PM] Dufresne, Eric
Sorted out Keysight Function Generator. Had some issues with the EPICS display, I find it flaky.
When one controls it in spec (with caput), it works well and reliably.

8idpixirad% more batches/2022/June2022/Agilent-example.txt
epics_put("8idKey33500B:FG1:FREQ", 0.004)
epics_put("8idKey33500B:FG1:FUNC", 1) # 0:SIN 1:SQU 2:RAMP 5 Big grinC
epics_put("8idKey33500B:FG1:AMP", 0.5)
epics_put("8idKey33500B:FG1:OFF", 0.75)

In SIN or SQR mode, the amplitude is the peak-to-peak Amplitude. With AMP=1, the signal oscillates from -0.5 to 0.5 V.
It is possible to add an offset to change this. In DC mode, only the offset controls the output. In the SQR wave mode,
the duty cycle is how long the output is High. I attach screenshots for clarity.
Attachment 1: KeysightManualScreenshot.png
KeysightManualScreenshot.png
Attachment 2: KeysightDisplay.png
KeysightDisplay.png
  820   Thu Dec 2 18:21:46 2021 Eric Dufresne8-ID-EManualsUseful debugging commands for Lambda 250k
Original report https://logbook.xray.aps.anl.gov/8id/8-ID/817

Useful debugging commands


  • xspadmin@xspserver:cd ~/xenv$; ./bin/run dcinfo
  • ./bin/run acquire -- {number of frames} {exposure in ms} {low threshold in keV},{high threshold in keV} {bit depth}
  • As for the gui, I installed locally and was using 'nexpy' to view the .nxs (NEXUS) images stored by
    the 'run acquire' xenv script. That should work over NX or ssh equally well, let me know if not.
  • Manual https://logbook.xray.aps.anl.gov/8id/8-ID/661/1 V0.8



Re: Lambda 250K
Julian Schmehr <[email protected]>
Thu 11/4/2021 3:21 AM
To: Narayanan, Suresh <[email protected]>; Andreas Beckmann <[email protected]>; Guruswamy, Tejas <[email protected]>;
Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Suresh,

So it sounds like you are still getting data which is a good sign. One thing you could check is whether
the high voltage is working normally. This is returned as an output when running dcinfo:

cd /home/xspadmin/xenv
run dcinfo

If the high voltage isn’t on this would cause images with only some noisy pixels. Could you send us the
output of dcinfo please? Also if you can send an example datafile that will help with identifying the problem.

Sincerely,

Julian

Re: Lambda 250K
Narayanan, Suresh <[email protected]>
Thu 11/4/2021 6:09 AM
To: Julian Schmehr <[email protected]>; Andreas Beckmann <[email protected]>;
Guruswamy, Tejas <[email protected]>; Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Julian,

xspadmin@xspserver:~/xenv$ ./bin/run dcinfo
run: running make in tasks/basic
make: Nothing to be done for 'all'.
run: v1.1.0
run: logging output to logs/unknown/2021-11-04T06:08:37/run.log 
run: running tasks/basic/dcinfo
                config file: /etc/opt/xsp/system.yml
                output dir : results/unknown/2021-11-04T06:08:37/tasks/basic
                args       :
INFO: test dcinfo started
INFO: loading config from /etc/opt/xsp/system.yml
INFO: found detector system SYS
INFO: found detector lambda: Lambda w/ 1 module(s)

          mod #1:
              FW: 2.2.0 [ctrl=v0, data=v3, feat=0x03]
              Chip IDs:
                  # 3: b32w2-D07,SAL,0x80040247
                  # 4: b32w2-E07,SAL,0x80040257
              HV: 201.046V
              T: 26.5°C 27.3347°C 242.562°C
              Features: HV 1/6-bit
INFO: test dcinfo finished
run: test passed

Re: Lambda 250K
Guruswamy, Tejas <[email protected]>
Thu 11/4/2021 4:39 PM
To: Narayanan, Suresh <[email protected]>; Julian Schmehr <[email protected]>; Andreas Beckmann <[email protected]>;
Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Julian,

Yes, the files we measured yesterday are in xenv/results/2021-11-03 .... Please take a look.

We did restart the hardware and software while testing, so I don't think it should be connected to that.

Here is a dcinfo output from while we were having problems, which seemed reasonable:
INFO: found detector lambda: Lambda w/ 1 module(s)
          mod #1:
              FW: 2.2.0 [ctrl=v0, data=v3, feat=0x03]
              Chip IDs:
                  # 3: b32w2-D07,SAL,0x80040247
                  # 4: b32w2-E07,SAL,0x80040257
              HV: 200.097V
              T: 27.3125°C 27.9499°C 304.75°C
              Features: HV 1/6-bit
Tejas

Re: Lambda 250K
Guruswamy, Tejas <[email protected]>
Thu 11/4/2021 5:07 PM
To: Julian Schmehr <[email protected]>; Narayanan, Suresh <[email protected]>; Andreas Beckmann <[email protected]>;
Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Julian,

You are right, I must have made a mistake when visualizing in nexpy yesterday. Thank you for testing.

To be clear the syntax for using acquire is

./bin/run acquire -- {number of frames} {exposure in ms} {low threshold in keV},{high threshold in keV} {bit depth}

correct?

I just tested the IOC again however and still no luck.
So the detector seems fine after all, but we still have an issue. Perhaps Keenan could have a look?

Thanks
Tejas
  819   Tue Nov 16 14:54:03 2021 Eric Dufresne8-ID-EDrawings8-ID-E optical table 2 pictures

https://anl.box.com/s/ue1hdki7oht6byrjirjaonfyzjd2cngj

From: Dufresne, Eric <[email protected]>
Sent: Tuesday, November 16, 2021 2:27 PM
To: Capatina, Dana <[email protected]>; Wakefield, Kevin J <[email protected]>
Cc: Fisher, Mike V. <[email protected]>; Narayanan, Suresh <[email protected]>; Sandy, Alec R. <[email protected]>
Ziegler, Raymond <[email protected]>; Highland, Matthew J. <[email protected]>
Subject: Re: XPCS team meeting - Wed, 3pm

This is a meeting's follow up, Dana and Kevin.
I took pictures on the 8-ID-E WA-XPCS optical table.
My experience has been good with the jacks on this table.
I will typically scan it in X+Y on a 20 um focused beam to center
it on my 60 um guard slits. It is a 6'x4'x1' table and I was able to get the drawing numbers
for the 3 vertical jacks, and one horizontal motorized slide.
I am missing the other two horizontal slides, one is motorized,
while the other is just a slide. Looking at EPICS screens, it looks like
it has a Z slide as well. Will have to get back to you on this has I don't have access
to the hutch right now, the 8ID-G robot is being tested...



https://anl.box.com/s/ue1hdki7oht6byrjirjaonfyzjd2cngj

It is a table purchased by MIT built by AJR, big round vertical jacks.

Eric



From: Dufresne, Eric <[email protected]>
Date: Tuesday, November 16, 2021 at 2:43 PM
To: Capatina, Dana <[email protected]>, Wakefield, Kevin J <[email protected]>
Cc: Fisher, Mike V. <[email protected]>, Narayanan, Suresh <[email protected]>, Sandy, Alec R. <[email protected]>,
Ziegler, Raymond <[email protected]>, Highland, Matthew J. <[email protected]>
Subject: Re: XPCS team meeting - Wed, 3pm

The first few pictures actually show the Z stage, they are with the vertical jack S/N 048,
so this foot has XYZ, the table has 6 motorized stages.


ED

Re: XPCS team meeting - Wed, 3pm
Sandy, Alec R. <[email protected]>
Tue 11/16/2021 3:05 PM
To: Narayanan, Suresh <[email protected]>; Dufresne, Eric <[email protected]>; Capatina, Dana <[email protected]>;
Wakefield, Kevin J <[email protected]>
Cc: Fisher, Mike V. <[email protected]>; Ziegler, Raymond <[email protected]>; Highland, Matthew J. <[email protected]>

Hi,

The stages and base frame are from a goniometer support assembly from the APS beamline design library from the early-mid 90s.
Can’t remember if it is T6-25 or T6-29 … something like that. There would be paper drawings in the file cabinet in the back
hallway. The motorized slides and followers are by design so that the motions are not over constrained and so the full
EPICS table record can be used. Deming will know all about these.

- Alec

Re: XPCS team meeting - Wed, 3pm
Dufresne, Eric <[email protected]>
Tue 11/16/2021 6:00 PM
To: Capatina, Dana <[email protected]>; Wakefield, Kevin J <[email protected]>
Cc: Fisher, Mike V. <[email protected]>; Ziegler, Raymond <[email protected]>;
Highland, Matthew J. <[email protected]>; Narayanan, Suresh <[email protected]>; Sandy, Alec R. <[email protected]>

Dana, Kevin,

I updated the link below with several pictures taken today, showing
the Z slide a bit more, the Y slides limits status, the manual jack and the feet
positions (Alec reminded me about these: they are low, thanks Alec), the footprint (thanks Suresh).
https://anl.box.com/s/ue1hdki7oht6byrjirjaonfyzjd2cngj

https://anl.box.com/s/r13euz3hniehq7wvlc44wde7l7vcbnx0
This is the approximate footprint, my note on table height (~1.04m), status of
vertical jacks (about 35 mm above lower limit), and travel range.

Learned to interrupt the robot too.

There is a classic SRI ~1995-1996 paper that describes these design by Deming.
We would find what Alec mentioned earlier. This is a classic of old APS designs.

Eric
  818   Mon Nov 15 17:09:31 2021 Eric Dufresne8-ID-IDrawings8-ID-I tilt stages for today's APS and APS-U.

The 8-ID-I sample stage has three stages to tilt the sample,
two are arcs Huber model 5203.20-214 (214 must be Serial Number).
The last one is a large one circle but not from Huber.

The award/req for property tag P075018 is PO Number 5A-38205.
https://apps.inside.anl.gov/paris/req.jsp?reqNbr=F5-168053

Huber catalog:
https://www.xhuber.com/en/products/1-components/12-rotation/2-circle-segments/520320/
  817   Thu Nov 4 11:07:07 2021 Eric Dufresne8-ID-EDetectorsDetector problem 8-ID-E Lambda250k, 11/3/2021 with Oleg's beamtime

Useful debugging commands


  • xspadmin@xspserver:~/xenv$ ./bin/run dcinfo
  • As for the gui, I installed locally and was using 'nexpy' to view the .nxs images stored by
    the 'run acquire' xenv script. That should work over NX or ssh equally well, let me know if not.

Re: Lambda 250K
Julian Schmehr <[email protected]>
Thu 11/4/2021 3:21 AM
To: Narayanan, Suresh <[email protected]>; Andreas Beckmann <[email protected]>; Guruswamy, Tejas <[email protected]>;
Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Suresh,

So it sounds like you are still getting data which is a good sign. One thing you could check is whether
the high voltage is working normally. This is returned as an output when running dcinfo:

cd /home/xspadmin/xenv
run dcinfo

If the high voltage isn’t on this would cause images with only some noisy pixels. Could you send us the
output of dcinfo please? Also if you can send an example datafile that will help with identifying the problem.

Sincerely,

Julian





Re: Lambda 250K
Narayanan, Suresh <[email protected]>
Thu 11/4/2021 6:07 AM
To: Julian Schmehr <[email protected]>; Andreas Beckmann <[email protected]>; Guruswamy, Tejas <[email protected]>;
Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Julian,

Thanks for your response.

Tejas checked HV and it returns 200.00xx, dc run takes data with no errors.
In the entire frame, we see 3 hot pixels, 2 together one place and one in another place.
Tejas checked that calib files are in the right place.
The users were running normally when IOC crashed maybe around that time and then since then this has been like that.
Tejas also installed your xsp-py lib and took images with it, shows the same 3 pixels.

Suresh

Re: Lambda 250K
Narayanan, Suresh <[email protected]>
Thu 11/4/2021 6:09 AM
To: Julian Schmehr <[email protected]>; Andreas Beckmann <[email protected]>;
Guruswamy, Tejas <[email protected]>; Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Julian,

xspadmin@xspserver:~/xenv$ ./bin/run dcinfo

run: running make in tasks/basic
make: Nothing to be done for 'all'.
run: v1.1.0
run: logging output to logs/unknown/2021-11-04T06:08:37/run.log 
run: running tasks/basic/dcinfo
                config file: /etc/opt/xsp/system.yml
                output dir : results/unknown/2021-11-04T06:08:37/tasks/basic
                args       :
INFO: test dcinfo started
INFO: loading config from /etc/opt/xsp/system.yml
INFO: found detector system SYS
INFO: found detector lambda: Lambda w/ 1 module(s)

          mod #1:
              FW: 2.2.0 [ctrl=v0, data=v3, feat=0x03]
              Chip IDs:
                  # 3: b32w2-D07,SAL,0x80040247
                  # 4: b32w2-E07,SAL,0x80040257
              HV: 201.046V
              T: 26.5°C 27.3347°C 242.562°C
              Features: HV 1/6-bit
INFO: test dcinfo finished
run: test passed


Re: Lambda 250K
Narayanan, Suresh <[email protected]>
Thu 11/4/2021 10:47 AM
To: Julian Schmehr <[email protected]>; Andreas Beckmann <[email protected]>;
Guruswamy, Tejas <[email protected]>; Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>;
Lang, Keenan C. <[email protected]>

Hi Julian,

I have given you access to “lapis” over NX. Once on NX, we will make sure it is logged as “8ideuser”,
then in a terminal, you can do “go_lambda” and will take you to the computer.

Eric is around and can help and maybe if Tejas is available.

Let us try to get some diagnosis if that is possible. We were quite stunned to see this issue and we had
users flying in from UCSD and no detector. Luckily, the pool was able to get a spare for us in a happy coincidence.

Suresh

Re: Lambda 250K
Guruswamy, Tejas <[email protected]>
Thu 11/4/2021 4:39 PM
To:

Narayanan, Suresh <[email protected]>; Julian Schmehr <[email protected]>; Andreas Beckmann <[email protected]>; Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Julian,

Yes, the files we measured yesterday are in xenv/results/2021-11-03 .... Please take a look.

We did restart the hardware and software while testing, so I don't think it should be connected to that.

Here is a dcinfo output from while we were having problems, which seemed reasonable:
INFO: found detector lambda: Lambda w/ 1 module(s)
          mod #1:
              FW: 2.2.0 [ctrl=v0, data=v3, feat=0x03]
              Chip IDs:
                  # 3: b32w2-D07,SAL,0x80040247
                  # 4: b32w2-E07,SAL,0x80040257
              HV: 200.097V
              T: 27.3125°C 27.9499°C 304.75°C
              Features: HV 1/6-bit
Tejas

Re: Lambda 250K
Guruswamy, Tejas <[email protected]>
Thu 11/4/2021 5:07 PM
To: Julian Schmehr <[email protected]>; Narayanan, Suresh <[email protected]>; Andreas Beckmann <[email protected]>;
Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Julian,

You are right, I must have made a mistake when visualizing in nexpy yesterday. Thank you for testing.

To be clear the syntax for using acquire is

./bin/run acquire -- {number of frames} {exposure in ms} {low threshold in keV},{high threshold in keV} {bit depth}

correct?

I just tested the IOC again however and still no luck.
So the detector seems fine after all, but we still have an issue. Perhaps Keenan could have a look?

Thanks
Tejas

Re: Lambda 250K
Narayanan, Suresh <[email protected]>
Thu 11/4/2021 5:13 PM
To: Guruswamy, Tejas <[email protected]>; Julian Schmehr <[email protected]>;
Andreas Beckmann <[email protected]>; Dufresne, Eric <[email protected]>;
Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Julian, Tejas,

How can ioc be wrong suddenly while running?

Are you sure Tejas that you saw noise yesterday, changed threshold in ioc and there was nothing in imagej.

Suresh

Re: Lambda 250K
Guruswamy, Tejas <[email protected]>
Thu 11/4/2021 5:30 PM
To: Narayanan, Suresh <[email protected]>; Julian Schmehr <[email protected]>; Andreas Beckmann <[email protected]>; Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>
Hi all,

I can't explain what went wrong yesterday when I was trying the acquire script. As Julian says,
reviewing the data now it looks ok, so I must have made a mistake somewhere, sorry.

But coming back to the IOC , yes even now I still see blank images in ImageJ. Changing threshold in the IOC
seems to make no difference. There are no obvious errors I can see, just no data.
(Also the IOC still crashes over ssh only.)

I am looking through the system logs in case I missed anything. From memory do you remember roughly when
it was last working? 11am Nov 3, or before?

Tejas

Re: Lambda 250K
Narayanan, Suresh <[email protected]>
Thu 11/4/2021 5:34 PM
To: Guruswamy, Tejas <[email protected]>; Julian Schmehr <[email protected]>; Andreas Beckmann <[email protected]>; Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>
Hi Tejas,

It was working around 11 am and ioc crashed at 11:25 am and then no photons on the chip.

Suresh

Re: Lambda 250K
Guruswamy, Tejas <[email protected]>
Thu 11/4/2021 6:43 PM
To: Narayanan, Suresh <[email protected]>; Julian Schmehr <[email protected]>; Andreas Beckmann <[email protected]>; Dufresne, Eric <[email protected]>; Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>
Hi all,

I found some clues but no solution yet.

1. When the IOC crashes, this appears in the system log (this happened at 11:20AM Nov 3, and I can reproduce by trying to acquire over ssh now):
Nov 4 18:17:00 xspserver kernel: [107950.286099] ADLambda::expor[7153]: segfault at 10 ip 00007ffbafa4b0c0 sp 00007ff68d8e0828 error 4 in libCom.so.3.19.0[7ffbafa2c000+38000]
Nov 4 18:17:00 xspserver kernel: [107950.286110] Code: f7 01 00 be 84 00 00 00 48 8d 3d 99 f7 01 00 e8 e6 23 fe ff e9 fd fe ff ff 90 48 8b 7f 10 e9 47 28 fe ff 0f 1f 80 00 00 00 00 <48> 8b 7f 10 e9 67 12 fe ff 0f 1f 80 00 00 00 00 48 8b 7f 10 e9 87

Since it suggests a segfault in an epics library (libCom) I've tried to clean and rebuild everything -- epics, areaDetector, ADLambda.
But so far it still crashes. This issue is probably separate to all others since we had these crashes even before yesterday.

2. Looking at the output of the NDStatistics plugin, I think real data is being measured. The total across all pixels changes
with the IOC threshold in a reasonable way. However all image format outputs (ImageJ, JPEG, TIFF) look like empty data.

3. On Nov 2 Keenan said the following about a new version of the Lambda IOC: "I've switched the data types to be signed
values rather than unsigned." But everywhere I look in the image/output plugins windows I see UInt (unsigned). Not sure if this is correct.

4. Perhaps a vague theory is that Keenan's code change implemented on Nov 2 was not fully loaded initially, because the IOC
was already running and in memory on another user login. But when the IOC crashed at 11:20AM Nov 3, everything would have had
to reload, and this is when the problems started.
So I think the IOC is actually measuring data correctly but somehow one of the conversion steps (NDPluginStdArrays?) is
silently failing. We're at the boundary of my knowledge of epics internals so any insight from others would be appreciated.

Tejas

Re: Lambda 250K
Narayanan, Suresh <[email protected]>
Thu 11/4/2021 9:07 PM
To: Guruswamy, Tejas <[email protected]>; Julian Schmehr <[email protected]>;
Andreas Beckmann <[email protected]>; Dufresne, Eric <[email protected]>;
Miceli, Antonino <[email protected]>; Lang, Keenan C. <[email protected]>

Hi Tejas,

Thanks for digging deeper. Your explanation makes sense. Let us see what Keenan says.

Suresh

Keenan debugging:


[11/6 2:41 PM] Lang, Keenan C.
Had to track down a null-pointer error that was apparently there all along, but not causing any problems
until the current build, but I just ran an acquisition and was able to see static. You should double-check
that the images that are being taken match up with what is expected.

[11/6 3:02 PM] Narayanan, Suresh
Lang, Keenan C. can you explain what caused this, was Tejas' explanation correct?
&#8203;[11/6 3:09 PM] Lang, Keenan C.
I have no idea what caused this. Theoretically, this is something that should have been causing
an issue all along. I do think that the IOC was still running the old version for a bit and then when
something did go wrong, rebooting the IOC just failed worse, but I even rolled back to the version of
the code from before I made any recent changes and still had crashes, so I am unsure what all went wrong.
  816   Wed Nov 3 17:02:25 2021 Eric Dufresne8-ID-EDetectorsSetting up Eiger S 500k 3kfps on 11/03/2021 due to Lambda250K failure


https://logbook.xray.aps.anl.gov/8id/8-ID/647 Previous Eiger loan in 2019

This is a new Unit, Eiger S 500k, 3,000 fps. Above was 9 kfps from Junjing,
so it had different mounting. As such, I attach the mounting pictures below
https://anl.app.box.com/folder/149430416536
and specifically, these pictures are relevant for this Eiger:
My Drawings are also in my Detector folder under Dectris/Eiger
ls ~dufresne/8ID/Detectors/Dectris/Eiger/8-ID-E-YCao/
20190618_173708.jpg MyDrawings
EigerEmailJunjingDeng.txt PicturesOfMount
MiaoqiChuPlate 'TechnicalSpecifications_EIGER_X_500K(1).pdf'

/home/beams/8IDEUSER/Dufresne/Operation/2021/Nov/EigerScreenshots
lapis% ls
EigerAllPlugins.png EigerCodec1.png EigerROI1.png ImageJ.png
Eiger-cam1.png Eiger-HDF1.png EigerStats1.png StartGUIscreens.png





https://wiki.aps.anl.gov/bts/index.php/Detector_Pool_Computing_Information

On C032 the highest counts are 24 and there are 6
pixels with 2^32 and -1.

Re: Eiger maximum count rate per pixel
Miceli, Antonino <[email protected]>
Thu 11/4/2021 11:01 PM
To: Dufresne, Eric <[email protected]>

See: https://www.dectris.com/features/features-eiger-r/outstanding-count-rate-performance/

Need to convert to pixel size!

Re: Eiger maximum count rate per pixel
Dufresne, Eric <[email protected]>
Thu 11/4/2021 11:24 PM
To: Miceli, Antonino <[email protected]>
Cc: Narayanan, Suresh <[email protected]>
Thanks Nino,

do I have the Eiger R then?
1 mm^2 is 177.8 pixels, the curve for 8 keV is more non-linear too (working at 7.35 keV),
so if you say you don't need correction for > 50 Mcps/mm^2 incident,
you should keep the count rate below 281 kcps/pixel!

Eric

Re: Eiger maximum count rate per pixel
Miceli, Antonino <[email protected]>
Thu 11/4/2021 11:28 PM
To: Dufresne, Eric <[email protected]>
Cc: Narayanan, Suresh <[email protected]>

That sounds reasonable. You have an S but the difference is the R is USB and the S is 10G Ethernet.

Nino
Attachment 1: Eiger-HDF1.png
Eiger-HDF1.png
Attachment 2: EigerCodec1.png
EigerCodec1.png
Attachment 3: EigerROI1.png
EigerROI1.png
Attachment 4: EigerStats1.png
EigerStats1.png
Attachment 5: Eiger-cam1.png
Eiger-cam1.png
Attachment 6: EigerAllPlugins.png
EigerAllPlugins.png
Attachment 7: StartGUIscreens.png
StartGUIscreens.png
  815   Tue Nov 2 00:29:55 2021 Eric Dufresne8-ID-ITemperature Controller IssuesRecent findings with QNW stage
Eric Dufresne 2:17 PM
@Suresh Narayanan Chris heated up his sample to 150C briefly. Nothing smelled like plastic inside the hutch.
Any concerns with running at 150C per your experience?

Suresh Narayanan 3:29 PM
150 c is ok, done before, 160 c is the hard limit, wont accept > that



From Chris Takacs:
FYI, I was not able to control at 150C - ran out of heater power. I think slight dip in correlation functions
is due to inability to control. 145C controls OK. Also, we found a bit of coupling between stages (e.g. fairly
large swings) but there was clear coupling in the data. (environment 3 was at 25C, we cooled the other
environments at 90C back to RT and it took quite awhile before we got quality data again).
  814   Thu Oct 14 15:45:50 2021 Eric Dufresne8-ID GeneralAdministrativeOrientation material for 8ID
Credit for sector orientations can be given here:
http://www.aps.anl.gov/Safety_and_Training/
https://beam.aps.anl.gov/pls/apsweb/sst_entry_pkg.start_page


[Yesterday 5:50 PM] Ziegler, Raymond
All,

As I transition away from approving ESAFs, it is very important that each of you monitor
your upcoming ESAFs for updated training and such, and communicate these needs to your users in a timely manner...


I'm attaching the "online" sector orientation. It's really just a Power Point. This can
also be found in the Safety folder in the DYS Box...
https://anl.app.box.com/folder/89584253407


You are now tasked with sending this document to any onsite users who need it. Once
they review it and and are given their on-site hutch training, have them sign the SO
checklist and place it on my door. I will still give them credit for the SO on the
APS Safety and Training website...

My suggested dialog is as follows, but feel free to customize...



"Please review the attached SO slide deck and notify us when complete. The Hutch 'search and secure'
portion will need to be done here at the beamline once you arrive, along with a Chem Lab review
if applicable. Note that the links in the slide deck only work when viewing in "Slide Show" mode..."

As always, I'm still around to assist whenever needed... I'm still the go-to for chem waste,
electrical inspections, and general beamline activities and support, etc... Thanks!
(2 liked)
[8ID Sector Orientation_online_v21_draft.pptx] ()
[Sector 8-ID Orientation checklist_20191015.pdf] ( https://argonnedoe-my.sharepoint.com/personal/rziegler_anl_gov/Documents/Microsoft Teams Chat Files/Sector 8-ID Orientation checklist_20191015.pdf )
Goto page Previous  1, 2, 3, 4 ... 42, 43, 44   Next  
ELOG V3.1.4-395e101