GENESYS setup trigger

screen shot

https://clipboard.acc.gsi.de/screenshot-app/screenshots/tcl1064/2024-05-14_23-46-56-017.png

two pages of log book on paper for teh first setup,
injection into ESR and tuning primary beam 100Mo and fragment 98Mo.

Sergey started with a setting with quadrupoles already changed like in 2021.
Ths was used for the first isochronicity curves.
It also gave soem, however, not good peak shapes with scrapers closed.
But after a failure only a new setting of quads could revover the peaks.

Then more cooler curves were measured and found to have quite a slope.
Changing ESR energy does not change the curves much, but changing the quads does.
With the stronger variation of quads (+1.65% on two quadrupole families) the curve tilts to opposite side.

All curves in EXCEL.
Cooler voltage converted to Brho with gamma ~ 1.4 and curves in relative frequency spread shifted on top of each other.
In new injections the quads are set new, which causes a frequency jump. Pasted parts of curves to remove jump.

empty shots for test.

Stable beam after a long time:


from below ones, only the last 4 ones are probably best.

RSA01-2024.05.14.17.36.49.211.tiq
RSA01-2024.05.14.17.38.25.867.tiq
RSA01-2024.05.14.17.38.39.827.tiq
RSA01-2024.05.14.17.38.54.555.tiq
RSA01-2024.05.14.17.39.08.523.tiq

and

RSA02-2024.05.14.17.32.58.640.tiq
RSA02-2024.05.14.17.36.48.947.tiq
RSA02-2024.05.14.17.37.02.258.tiq
RSA02-2024.05.14.17.38.25.603.tiq
RSA02-2024.05.14.17.38.39.587.tiq
RSA02-2024.05.14.17.38.54.315.tiq
RSA02-2024.05.14.17.39.08.283.tiq

Cooler curve measurement

# First run:
# V, RSA01-File, RSA02-File
-2300, RSA01-2024.05.14.15.21.21.576.tiq, RSA02-2024.05.14.15.21.21.334.tiq
-2200, RSA01-2024.05.14.15.22.56.743.tiq, RSA02-2024.05.14.15.22.56.501.tiq
-2100, RSA01-2024.05.14.15.24.17.833.tiq, RSA02-2024.05.14.15.24.17.591.tiq
-2000, RSA01-2024.05.14.15.25.34.248.tiq, RSA02-2024.05.14.15.25.34.006.tiq
-1900, RSA01-2024.05.14.15.26.39.602.tiq, RSA02-2024.05.14.15.26.39.359.tiq
-1800, RSA01-2024.05.14.15.27.41.204.tiq, RSA02-2024.05.14.15.27.40.962.tiq
-1700, RSA01-2024.05.14.15.28.45.781.tiq, RSA02-2024.05.14.15.28.45.539.tiq
-1600, RSA01-2024.05.14.15.29.49.831.tiq, RSA02-2024.05.14.15.29.49.589.tiq
-1500, RSA01-2024.05.14.15.31.02.912.tiq, RSA02-2024.05.14.15.31.02.670.tiq
-1400, RSA01-2024.05.14.15.32.53.806.tiq, RSA02-2024.05.14.15.32.53.564.tiq
-1300, RSA01-2024.05.14.15.34.02.599.tiq, RSA02-2024.05.14.15.34.02.357.tiq
-1200, RSA01-2024.05.14.15.35.32.079.tiq, RSA02-2024.05.14.15.35.31.836.tiq
-1100, RSA01-2024.05.14.15.36.35.601.tiq, RSA02-2024.05.14.15.36.35.359.tiq
-1000, RSA01-2024.05.14.15.37.52.778.tiq, RSA02-2024.05.14.15.37.52.536.tiq
-900, RSA01-2024.05.14.15.39.20.656.tiq, RSA02-2024.05.14.15.39.20.414.tiq
-800, RSA01-2024.05.14.15.40.24.019.tiq, RSA02-2024.05.14.15.40.23.777.tiq
-700, RSA01-2024.05.14.15.41.41.963.tiq, RSA02-2024.05.14.15.41.41.721.tiq
-600, RSA01-2024.05.14.15.42.53.140.tiq, RSA02-2024.05.14.15.42.52.899.tiq
-500, RSA01-2024.05.14.15.43.55.830.tiq, RSA02-2024.05.14.15.43.55.588.tiq


# Second run:

-1400, RSA01-2024.05.14.16.01.38.472.tiq, RSA02-2024.05.14.16.01.38.231.tiq
-1410, RSA01-2024.05.14.16.02.42.778.tiq, RSA02-2024.05.14.16.02.42.536.tiq
-1420, RSA01-2024.05.14.16.03.50.044.tiq, RSA02-2024.05.14.16.03.49.802.tiq
-1430, RSA01-2024.05.14.16.05.04.612.tiq, RSA02-2024.05.14.16.05.04.371.tiq
-1440, RSA01-2024.05.14.16.06.16.606.tiq, RSA02-2024.05.14.16.06.16.364.tiq
-1450, RSA01-2024.05.14.16.07.31.414.tiq, RSA02-2024.05.14.16.07.31.172.tiq
-1460, RSA01-2024.05.14.16.08.43.864.tiq, RSA02-2024.05.14.16.08.43.622.tiq
-1470, RSA01-2024.05.14.16.09.59.912.tiq, RSA02-2024.05.14.16.09.59.670.tiq
-1480, RSA01-2024.05.14.16.11.08.625.tiq, RSA02-2024.05.14.16.11.08.384.tiq
-1490, RSA01-2024.05.14.16.12.12.699.tiq, RSA02-2024.05.14.16.12.12.458.tiq
-1500, RSA01-2024.05.14.16.13.20.061.tiq, RSA02-2024.05.14.16.13.19.820.tiq
-1510, RSA01-2024.05.14.16.14.31.982.tiq, RSA02-2024.05.14.16.14.31.741.tiq
-1520, RSA01-2024.05.14.16.15.30.129.tiq, RSA02-2024.05.14.16.15.29.887.tiq
-1530, RSA01-2024.05.14.16.16.41.026.tiq, RSA02-2024.05.14.16.16.40.784.tiq
-1540, RSA01-2024.05.14.16.17.51.499.tiq, RSA02-2024.05.14.16.17.51.257.tiq
-1550, RSA01-2024.05.14.16.18.49.853.tiq, RSA02-2024.05.14.16.18.49.612.tiq
-1560, RSA01-2024.05.14.16.19.58.297.tiq, RSA02-2024.05.14.16.19.58.054.tiq
-1570, RSA01-2024.05.14.16.21.14.503.tiq, RSA02-2024.05.14.16.21.14.262.tiq
-1580, RSA01-2024.05.14.16.22.29.616.tiq, RSA02-2024.05.14.16.22.29.375.tiq
-1590, RSA01-2024.05.14.16.24.26.365.tiq, RSA02-2024.05.14.16.24.26.124.tiq
-1600, RSA01-2024.05.14.16.25.34.823.tiq, RSA02-2024.05.14.16.25.34.582.tiq
-1610, RSA01-2024.05.14.16.26.43.576.tiq, RSA02-2024.05.14.16.26.43.335.tiq
-1620, RSA01-2024.05.14.16.27.57.633.tiq, RSA02-2024.05.14.16.27.57.391.tiq
-1630, RSA01-2024.05.14.16.28.59.107.tiq, RSA02-2024.05.14.16.28.58.865.tiq
-1640, RSA01-2024.05.14.16.30.03.861.tiq, RSA02-2024.05.14.16.30.03.619.tiq
-1650, RSA01-2024.05.14.16.31.06.942.tiq, RSA02-2024.05.14.16.31.06.701.tiq
-1660, RSA01-2024.05.14.16.32.25.911.tiq, RSA02-2024.05.14.16.32.25.670.tiq
-1670, RSA01-2024.05.14.16.33.46.951.tiq, RSA02-2024.05.14.16.33.46.710.tiq
-1680, RSA01-2024.05.14.16.34.56.720.tiq, RSA02-2024.05.14.16.34.56.479.tiq
-1690, RSA01-2024.05.14.16.36.54.877.tiq, RSA02-2024.05.14.16.36.54.636.tiq
-1700, RSA01-2024.05.14.16.38.06.854.tiq, RSA02-2024.05.14.16.38.06.613.tiq


# Third run:

-1590, RSA01-2024.05.14.16.40.04.235.tiq, RSA02-2024.05.14.16.40.03.994.tiq

here computer crashed.


1. Preliminary result.

Exactly this was the question. If several devices fail at the same time and you look for the course you might get suspicious.
 
Anyhow,
 
the NAS is working again. I assume this was only a temporary alert. I cannot trace the alert back to something special. One could do a S.M.A.R.T oft he HDDs to read out their status.
 
The bad new ist that the NI PXIe-1075 (crate) power supply seems to have a failure (95% sure). It is in a shuttle unit and can in priciple be replaced as a whole.
The shuttle itself is not easy to open itself, so to really measure the voltages is diffcult/takes some time. I tried to measure the voltages at an external connector (DB9 at backside of the crate) but as 
you might know it doesn’t have a „hard switch“ but some push button that starts some logic. Depending on the number of modules in the crate or if I switch on the fans on full intensity (as a load) the 
power of the crate immediately switches off or stays on a little bot longer. If you take out one or more modules (no particular one) the crate stays on a little bit longer. Some of the modules show an 
error then. I assume is because of wrong/missing power.
Again, I had no chance for a careful measurement of this behaviour, so I am not fully sure whether I am right.
 
Unfortunately, the crate itself cannot be bougth anymore (discontinued), similar ones are incredibly expensive and also usually not on stock
 
I suggest a twofold strategy :  We can bring the „power supply shuttle“ (that i shte name) to a specialist here at GSI, may be Shahab knows someone (or Jan/Uwe). May be there is a quick way to fix it.
In former times weh ad someone here at GSI.
 
Or try to get a new power supply shuttle (but it might be discontinued as well).
 
The full replament part (someone would need to contact NI and/or search the net, if a company/ebay still has it) is called:
 
„PXIe-1075 PowerSupplyShuttle“
I found two part numbers for it:
198136B-01L (original part number ont he back of the deivce)
780292-01 (official replacement part number) . However, NI doesn’t know about it on the web page.
 
http://download.ni.com/support/manuals/372539a.pdf
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019N2CSAU&l=de-DE
 
Evtl. hier anfragen:
https://www.rosenkranz-elektronik.com/de/messgeraete/273795/national-instruments-ni-pxie-1075
 
or datatec, they also have a lot NI Pxie stuff.
https://www.datatec.eu/pxi-chassis
 
ebay?
 
However, again I am not 100% sure about the PS, but there are strong hints.
 
A few notes at the end:
 
Although none of the below is likely the reason for the failure, yet,
 
If a label on crate a states „please leave some headroom for ventilation“ then please do it. There might be a reason.
Please consider the maximum power that can be drawn from a single mains connection. Two crates (NIM/NI) + a server computer are quite something, in particular on a multi-outlet power strip….
Bending of cables, in particular of optical fibres… Don’t bend them two tight. The NI optical cable can also not be ordered anymore. Stiff long cables on tiny connector (found on several places on the NI 
crate).
 
I cannot take further care about the issue since I am pretty busy here with the Etarget beamtime but may be it helps soemhow.
 
Best,
 
Carsten

After moving the NTCAP system from HKR to ESR Messhutte, we tested the system with a signal generator on 16th February and confirmed that it was functioning correctly.

On 7th May, I and David tried to start the NTCAP system again. However, the main computer of the NTCAP system took a significantly longer time to boot up on 7th May. We 
managed to collect some data and subsequently shut down the LabVIEW interface on 7th May. The NTCAP system was running well during the test. In the afternoon of 7th May, to 
replace the new monitor, I turned off the NTCAP system except the hard disk of NTCAP.

 

On the morning of 8th May, I noticed an alert warning on the hard disk of the NTCAP system. Moreover, I found the NTCAP computer unexpectedly turned on. When I 
tried to start the system today at the office, it failed to boot. The SP Device indicator was flashing, and then the system powered down by itself.


I am concerned that not shutting down the hard disk might have contributed to these issues, although I am not entirely sure. 

1. Comparison of tdms files between 16th February and 7th May.
iq:
IQ_2024-02-16_11-00-53  0000000.iq.tdms   4196035 kB
IQ_2024-02-16_11-00-53  0000001.iq.tdms   4196035 kB
IQ_2024-02-16_11-00-53  0000002.iq.tdms   4196035 kB

IQ_2024-05-07_10-24-21  0000000.iq.tdms   4196035 kB
IQ_2024-05-07_10-24-21  0000001.iq.tdms   4196035 kB
IQ_2024-05-07_10-24-21  0000002.iq.tdms   4196035 kB

sc:
SC 2024-02-16[11-01-31 0000000.sc.tdms  386 kB
SC 2024-05-07 10-23-49 0000000.sc.tdms  136 kB

The iq and sc files recorded on 7th May are the same as the files which were recorded on 16 February. However, it took a long time to start the NTCAP system on 7th 
May. It seems that the status of NTCAP was wrong on 7 May. 

2. The hard disk of the NTCAP system was the old one on 06 February. The hard disk was replaced on 6th February and 7th May. 

RSA file sync with server was up with LXIR131 through to the Lustre.