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 |