HOME SBOX THOMX MINICAV Utilities
THOMX orders THOMX installation THOMX commissioning THOMX control command
  Status of commissioning, report also here plots are reports., Page 21 of 24  Not logged in ELOG logo
ID Date Author Status Type Category Location Titledown
  189   Thu Feb 23 10:15:30 2023 Ronic ChicheFixedreportlasers and optics | softwareThomX iglooAlphanov amplifier beam profile measurement

Yesterday, Guillaume Machinet and Vincent Clet from Alphanov came to fixe some issues with the laser amplifier:

- 1) they fixed the "rep. rate" measurement issue.
previously, the voltage range in which it was possible to detect the correct rep rate (33MHz) was very narrow ~ 50mV.
we had fixed this threshold at 1V but any small voltage variation, making the signal a bit lower than this threshold, was triggering an alarm and stopping the amplifier.
it was the reason we put this threshold at 0.7V but with a false rep rate measurement of 100MHz.
the origin of this problem was a saturation of the input signal photodiode, which magnify the pulse oscillations and produce false rep rate detection.
Guillaume put a 3dB optical filter after the tap measuring the ~ 5.9mW of input power => no more saturation on this photodiode.
the range for detecting the correct rep rate is now wider, between 0.3V and 0.7V, thus we put the threshold at 0.5V at which we measured properly ~33MHz

2) they also fixed the issue of the output power estimation on the "LAL" software.
previously, even with the amplifier @ 0%, this output power estimation was around 35W !
the issue was double :
- there is a real drift of the DC voltage, from ~50mV when Guillaume made the amplifier to ~200mV now, coming from their photodiode measuring this output power.
this drift is not really understood and could come from a DC current from the ThomX setup (induction ?) or from a “faulty” Alphanov photodiode board.
this voltage is reported on the PD_EXT2 window from the "Line2" of the "Alphanov" internal software.
- the file making a correspondence between the measured voltage of the photodiode and the estimated output power was not properly filled.
in particular, 35W was corresponding to 200mV on one line of this file, which explains why the "LAL" software was showing 35W when the DC offset was reaching 200mV without any output power.
then, we redid the calibration between output power % and photodiode voltage to take into account this DC voltage change and we changed the associated corresponding file :
Pout = 0.3W / Voltage = 0.2V / P% = 0%
etc...
then, we have put back the safety parameters, surveying the output power variations :
for P% > 20%, the software checks that the voltage variations are not changing by 30% for more than 10 consecutive measurements.

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

information about the Watchdog values from the "Alphanov" internal software.
the FPGA on the controller board reads the input signal data every ~3ns (330MHz).
then, it is able to check if a signal is present every 30ns (33MHz).
the watchdog values are : min = 20ns and max = 200ns.
above and below these values, the watchdog alarm is triggered and the amplifier stops.

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

information about input power check:
the photodiode signal is integrated in a capacitor with a long decay time (at the 'ms' scale ?)
then, at each pulse, the signal increases and the software measures how long it takes to reach 1V => let's say ~1.5µs.
if the input power drops, it will take a longer time to reach 1V.
we put a threshold at ~3µs => if it is above, the input power dropped too much and the amplifier stops.

Ronic Chiche wrote:

On Monday 20th of February, Daniele and Viktor took some beam profile measurement data @ 50% of power amplification.

data and analysis can be found in the attached file.

Ronic Chiche wrote:

This morning with Daniele, we did a second measurement of the beam profile using a different lens of focal 400 mm.

at a power amplification of 20%

the amplifier stayed on for around one hour and a half with no errors. 

tomorrow will attemt to do one at higher amplification percentage.

data will be added after processing.

Ronic Chiche wrote:

This morning,

- with the "Alphanov" software => Central panel => "system" button => Watchdog "Period Max" was at 100ns and has been set to 200ns.
(Alphanov told me to change the value from 50ns to 100ns but it was already at 100ns, then I set it to 200ns).
=> to be checked with Alphanov : what is the meaning of this parameter.

- it seems the watchdog alarm is related to the "PD_IN" parameter value of the "LAL" software (5.5mW is OK, but 5.2mW triggers the alarm).
my understanding is the Threshold Voltage, which detects the input signal to measure the repetition rate, could be at a too high level... even very close to the max level of the signal.
then if the input decreases a little bit, the signal goes below this Threshold Voltage => the software does not detect a signal any more => it triggers the watchdog alarm and the amplifier stops
(which stops also the preamplifier, related to the PD_CRI of the "Alphanov" software which goes to ~0W. PD_Preamp2 is a copy of PD_CRI but in the "LAL" software).

then, I changed back the Threshold Voltage from 0.96V (to detect properly 33MHz rep rate) to 0.7V which is close to the original value (0.67V) but for which the software detects ~100MHz rep. rate !
with this Threshold level, I did a test by detuning very slightly the input power by unscrewing a little bit the fiber-fiber coupler => PD_IN = 4.9mW => no alarm triggered !
then I screwed back the coupler => PD_IN = 5.6mW.

I did a power test with 3rd stage of the amplifier at 20% during 15 minutes => no alarm.

conclusion : there is an issue with the rep rate detection.
at 33MHz, one needs to put the threshold at the limit of the signal which fires an alarm if the signal decreased a little bit.
by lowering the threshold => no more alarm (I hope) but a wrong rep rate value !

Ronic Chiche wrote:

With Daniele after, we took a readings of the beam with a lens of 750 mm.

From the observed data, we can state that the beam is not completely Gaussian M2 > 1, due to the variation of the ellipticity of the beam along the focused path 

readings have been saved and will be added after processing them.

Also adding to the previous comment about the error, after closing the bunker and starting the measurement we did not have issue for around 20 min then the same error appeared (alarm triggered by Watchdog) it shows when the input average power detected by the software was around 5.474 mW , I did a reset of the software then turned the amplifier on and the reading is 5.515mW it works for about 2 minutes (enough to take 2 readings) then it switches off. In addition, there was a drop in the power reading on the PD_preamp2 (which seems related to watchdog issue) we had to do this many times in order to finish taking the readings .

 

 

 

Ronic Chiche wrote:

we have had this new issue (watchdog alarm switching off the amplifier) for several days.

Alphanov mentionned it could come from the input oscillator stability (modelock loss for example).

Today,

- I tried to start the amplifier at 0% but it ended immediately in a "watchdog alarm" which stopped the amplifier
the input average power detected by the software was around 5.2mW, far above the 2mW needed by the amplifier.

- I checked the 33MHz oscillator at the output of the fiber connected to the Shafter-Kirchhoff fiber coupler with the Labbuddy fiber photodiode and a scope.
see the picture below : the peak are clean and at 33MHz... then, the Onefive oscillator is not faulty.

- after plugging back the fiber to the amplifier input, the input average power detected by the software increased a bit around 5.5 - 5.6mW.
I tried to start again the amplifier at 0% and now, it worked without any alarm !!!
then, the origin of the "watchdog alarm" was maybe the threshold on this input power.

Then, I launched the "Alphanov" software and changed again the "threshold level", previously set at 1V (see previous post below), to 0.96V !
with this threshold level, the Alphanov software detects at the beginning a frequency of 66MHz and then decreases slowly to 33MHz => to be understood.
it should allow also more room before triggering again the "watchdog alarm" if the input average power decreases a bit => to be confirmed by Alphanov.

 

Ronic Chiche wrote:

the laser amplifier worked for some days but it ended to a "watchdog" alarm which switches off the amplifier... investigation is ongoing

Ronic Chiche wrote:

Ronic on Friday operated the Amplifier from the Alphanov software, switched it off then turned on the LAL software,

and it worked for 40 min without issues or error appearing,

 

Ronic Chiche wrote:

this morning with Manar,

- we fixed the chiller problem (+/-2°C fluctuation around the set temperature value = 25°C).
we opened and closed several times the water valve of the primary circuit to remove air bubles => no effect on the temperature variations.
we put the chiller in "Auto-Tuning" (AT) mode, then pressed the "AT" key => the chiller tune its PID parameters to optimize its temperature stabilization => no more fluctuations (+/-0.2°C fluctuation around the set temperature value = 25°C).
we had anyway a "temperature case" alarm from the Alphanov software at P=40%*Pmax, which stops the amplifier.
we put the chiller it AT mode again but with some power in the amplifier => no difference, the temperature regulation seems very good now, but we still have some "temperature case" alarms... => contact Alphanov for that.

- we changed the mount of the 2nd wedge by a kinematic mount to help for the alignment and we added an iris in the path.
now the optical path seems OK to make the beam profile measurement easily.
as we have still amplifier stops due to "temperature case" alarm, even at low power (P=20%*Pmax), we stopped the measurements => see Manar logbook post.

 

Ronic Chiche wrote:

this morning with Manar,

- we checked first the chiller problem.
the fluctations of +/-2° around 25°C are still there.
I discussed with Jean-Noel Cayla about the possible problem of the "dirty" water in the primary circuit.
he told me that the water goes through 3 "effective" filters, then the water should not be too dirty in the primary circuit even if one uses "common water" to fill it.
he told me also that the water temperature could be a bit higher than before, around 22°C, and that could prevent a good thermal exchange with the secundary circuit (the one of the amplifier).
=> the resistivity is about 7Mohmhs.
we had again a "case temperature alarm" from the Alphanov Software, after 1h of work @ 20%
this stopped the amplifier, we did not restart it.

- we measured the beam path with the wedges :
compressor box output to mirror :    17cm
mirror to 1s wedge :                          24 cm
1st wedge to 2nd wedge :                 24.5 cm
2nd wedge to lift bottom mirror :       136 cm
lift bottom mirror to top mirror :          14 cm
lift top mirror to beam profiler (x=0) :   7 cm

- we measured the beam profile at 3 positions with amplifier @ 20% + 2 wedges :
the power is ~ 70 µW
we made the measurements at x=0, x=60 cm, x=120cm
after that, we had the Alphanov amplifier "temperature case incident" and we stopped the measurements.
 

Ronic Chiche wrote:

yesterday morning with Manar,

1) we fixed the threshold level of the laser input signal which makes the measurement of the repetition rate.
(if the rep rate is not measured properly, the amplifier safety interlock stops immediately the amplification).

we followed a tutorial from Guillaume Machinet.
when you start the Alphanov control software, 4 panels pops up : central control, 2nd stage amplifier, and 2 panels for controlling the pumps of the 3rd stage amplifier.
!!! Warning !!! ..... if you switch ON the amplifier using the central control panel, the amplifier starts immediately AT FULL POWER..... !!! Warning !!!
it is not mentionned in the tutorial document.
to prevent this problem, you first need to switch "Laser OFF" on the 2 panels controlling the pumps of the 3rd stage amplifier and let "Laser ON" only on the panel controlling the 2nd stage.

after starting the amplifier, we tried to find the median value of the threshold to get ~33MHz instead of 100MHz measured previously.
the initial voltage threshold on the photodiode measuring the rep rate was 0.4V which leads to get 100MHz.
first, we changed step by step the threshold to reach 0.87V => one gets 33MHz.
we tried the find the maximum threshold but once the level is above the signal maximum value, it triggers an alarm and stops immediately the amplifier.
then, one needs to restart completely the software which can be tedious due to connections/alarms issues.
finaly, we found out that the low and high level thresholds to get 33MHz were not reproductible at each start of the amplifier... :-(
then, we put the threshold at 1V following the turial procedure which seems to work.

2) we installed the optical scheme to make the beam profile measurement : see attached image
we used the HR mirror close to the amplifier output (as putting a wedge at that place is not convenient if you want to properly dump the transmission and reflections).
and then, we placed 2 wedges, using the front reflection to get low power beam profile.
the Thorlabs LB2 has been used to dump the transmission of the first wedge, it can handle 25kW/cm² and 25J/cm².
we used black aluminium screens to dump the secondary beams.
we measured after the 2 wedges :
amplifier at 20% => 71µW
amplifier at 30% => 139µW
amplifier at 40% => 200µW

it has to be compared with the amplifier power :
amplifier at 20%               =>               8.7 W
amplifier at 30%               =>               17 W
amplifier at 40%               =>               26 W

which leads to a reflection coefficient of the wedge of 0.28%.
=> OK, as one uses PS811-B Thorlabs 4° wedges with B coating.
with B coating, the reflectivity given by the manufacturer is around 0.3% @ 1030nm.

unfortunately, we had a "case temperature alarm" coming from the Alphanov software when we reached 40% for the amplification level.
this alarm stopped immediately the amplifier.
we saw that the chiller was in warning state too and the "present temperature PV" was not stable at all, flutuating by 3-4 degrees after the amplifier has been turned off...
we restarted several times the chiller to see if the problem disapears but it was still there ! => to be investiguated !

PS : we changed the USB cable between the amplifier controler and the PC to try to fix the several "connexion lost" problems but it didn't help...

PS2 : after discussing with Sophie Chance and Marie Jacquet, ThomX suffered a water circuit leakage on Monday:
the full circuit has been emptied and they had to remplace the water by some common water and not demineralized water....
it can be related to the chilller issue observed yesterday !

Ronic Chiche wrote:

today with Manar, we brought everything to make the profile measurement.

the chiller was in error because of the water level : we filled it in.
! warning ! there is no alarm signal, only a message on the screen.

we checked the incoming power measured by the software : 5.5 mW => OK
and we measured the output power (with pump) for :
0% => ~ 300 mW
10% => ~900 mW
20% => 8.65 W
30% => 17W

=> same as before.

the first HR mirror at the output of the amplifier was slightly scratched => we replaced it.

for sake of simplicity, we plan to use first a HR mirror and then 2x wedges for the profile measurement => to be checked next time.
we have to remove secundary beam reflections, then wedges are easier to use than AR/AR mirrors (as the 2 reflected beams are parallele).

at full power, the output power is ~ 70W
after 1st wedge : 2.8W
after 2nd wedge : 112 mW => the power should be low enough to use absorptive filters in front of the beam profiler.

 

 

 

 

 

 

 

 

 

 

 

 

  190   Mon Feb 27 18:23:13 2023 Ronic ChicheFixedreportlasers and optics | softwareThomX iglooAlphanov amplifier beam profile measurement

This morning with Victor we took a reading of the beam profile using a 400 mm lens at 70 % and 100 % amplification.

Will process the data and add after

Note : after an hour and half of amplifier on at 70% we increased the power to 100%, and after ~ 10 minutes the amplifier turned off and showed an error on the software called MMD3

and an error of the power mentioning " Le laser a été arrêté parce que sa puissance est trop éloignée de la puissance nominale"

"The laser has been stopped because its power is too far from the nominal power"

after that, the amplifier worked in varying intervals until it switched off because of the previously mentioned error.

solution could be related to the configuration file values ??????

 

Ronic Chiche wrote:

On Monday 20th of February, Daniele and Viktor took some beam profile measurement data @ 50% of power amplification.

data and analysis can be found in the attached file.

Ronic Chiche wrote:

This morning with Daniele, we did a second measurement of the beam profile using a different lens of focal 400 mm.

at a power amplification of 20%

the amplifier stayed on for around one hour and a half with no errors. 

tomorrow will attemt to do one at higher amplification percentage.

data will be added after processing.

Ronic Chiche wrote:

This morning,

- with the "Alphanov" software => Central panel => "system" button => Watchdog "Period Max" was at 100ns and has been set to 200ns.
(Alphanov told me to change the value from 50ns to 100ns but it was already at 100ns, then I set it to 200ns).
=> to be checked with Alphanov : what is the meaning of this parameter.

- it seems the watchdog alarm is related to the "PD_IN" parameter value of the "LAL" software (5.5mW is OK, but 5.2mW triggers the alarm).
my understanding is the Threshold Voltage, which detects the input signal to measure the repetition rate, could be at a too high level... even very close to the max level of the signal.
then if the input decreases a little bit, the signal goes below this Threshold Voltage => the software does not detect a signal any more => it triggers the watchdog alarm and the amplifier stops
(which stops also the preamplifier, related to the PD_CRI of the "Alphanov" software which goes to ~0W. PD_Preamp2 is a copy of PD_CRI but in the "LAL" software).

then, I changed back the Threshold Voltage from 0.96V (to detect properly 33MHz rep rate) to 0.7V which is close to the original value (0.67V) but for which the software detects ~100MHz rep. rate !
with this Threshold level, I did a test by detuning very slightly the input power by unscrewing a little bit the fiber-fiber coupler => PD_IN = 4.9mW => no alarm triggered !
then I screwed back the coupler => PD_IN = 5.6mW.

I did a power test with 3rd stage of the amplifier at 20% during 15 minutes => no alarm.

conclusion : there is an issue with the rep rate detection.
at 33MHz, one needs to put the threshold at the limit of the signal which fires an alarm if the signal decreased a little bit.
by lowering the threshold => no more alarm (I hope) but a wrong rep rate value !

Ronic Chiche wrote:

With Daniele after, we took a readings of the beam with a lens of 750 mm.

From the observed data, we can state that the beam is not completely Gaussian M2 > 1, due to the variation of the ellipticity of the beam along the focused path 

readings have been saved and will be added after processing them.

Also adding to the previous comment about the error, after closing the bunker and starting the measurement we did not have issue for around 20 min then the same error appeared (alarm triggered by Watchdog) it shows when the input average power detected by the software was around 5.474 mW , I did a reset of the software then turned the amplifier on and the reading is 5.515mW it works for about 2 minutes (enough to take 2 readings) then it switches off. In addition, there was a drop in the power reading on the PD_preamp2 (which seems related to watchdog issue) we had to do this many times in order to finish taking the readings .

 

 

 

Ronic Chiche wrote:

we have had this new issue (watchdog alarm switching off the amplifier) for several days.

Alphanov mentionned it could come from the input oscillator stability (modelock loss for example).

Today,

- I tried to start the amplifier at 0% but it ended immediately in a "watchdog alarm" which stopped the amplifier
the input average power detected by the software was around 5.2mW, far above the 2mW needed by the amplifier.

- I checked the 33MHz oscillator at the output of the fiber connected to the Shafter-Kirchhoff fiber coupler with the Labbuddy fiber photodiode and a scope.
see the picture below : the peak are clean and at 33MHz... then, the Onefive oscillator is not faulty.

- after plugging back the fiber to the amplifier input, the input average power detected by the software increased a bit around 5.5 - 5.6mW.
I tried to start again the amplifier at 0% and now, it worked without any alarm !!!
then, the origin of the "watchdog alarm" was maybe the threshold on this input power.

Then, I launched the "Alphanov" software and changed again the "threshold level", previously set at 1V (see previous post below), to 0.96V !
with this threshold level, the Alphanov software detects at the beginning a frequency of 66MHz and then decreases slowly to 33MHz => to be understood.
it should allow also more room before triggering again the "watchdog alarm" if the input average power decreases a bit => to be confirmed by Alphanov.

 

Ronic Chiche wrote:

the laser amplifier worked for some days but it ended to a "watchdog" alarm which switches off the amplifier... investigation is ongoing

Ronic Chiche wrote:

Ronic on Friday operated the Amplifier from the Alphanov software, switched it off then turned on the LAL software,

and it worked for 40 min without issues or error appearing,

 

Ronic Chiche wrote:

this morning with Manar,

- we fixed the chiller problem (+/-2°C fluctuation around the set temperature value = 25°C).
we opened and closed several times the water valve of the primary circuit to remove air bubles => no effect on the temperature variations.
we put the chiller in "Auto-Tuning" (AT) mode, then pressed the "AT" key => the chiller tune its PID parameters to optimize its temperature stabilization => no more fluctuations (+/-0.2°C fluctuation around the set temperature value = 25°C).
we had anyway a "temperature case" alarm from the Alphanov software at P=40%*Pmax, which stops the amplifier.
we put the chiller it AT mode again but with some power in the amplifier => no difference, the temperature regulation seems very good now, but we still have some "temperature case" alarms... => contact Alphanov for that.

- we changed the mount of the 2nd wedge by a kinematic mount to help for the alignment and we added an iris in the path.
now the optical path seems OK to make the beam profile measurement easily.
as we have still amplifier stops due to "temperature case" alarm, even at low power (P=20%*Pmax), we stopped the measurements => see Manar logbook post.

 

Ronic Chiche wrote:

this morning with Manar,

- we checked first the chiller problem.
the fluctations of +/-2° around 25°C are still there.
I discussed with Jean-Noel Cayla about the possible problem of the "dirty" water in the primary circuit.
he told me that the water goes through 3 "effective" filters, then the water should not be too dirty in the primary circuit even if one uses "common water" to fill it.
he told me also that the water temperature could be a bit higher than before, around 22°C, and that could prevent a good thermal exchange with the secundary circuit (the one of the amplifier).
=> the resistivity is about 7Mohmhs.
we had again a "case temperature alarm" from the Alphanov Software, after 1h of work @ 20%
this stopped the amplifier, we did not restart it.

- we measured the beam path with the wedges :
compressor box output to mirror :    17cm
mirror to 1s wedge :                          24 cm
1st wedge to 2nd wedge :                 24.5 cm
2nd wedge to lift bottom mirror :       136 cm
lift bottom mirror to top mirror :          14 cm
lift top mirror to beam profiler (x=0) :   7 cm

- we measured the beam profile at 3 positions with amplifier @ 20% + 2 wedges :
the power is ~ 70 µW
we made the measurements at x=0, x=60 cm, x=120cm
after that, we had the Alphanov amplifier "temperature case incident" and we stopped the measurements.
 

Ronic Chiche wrote:

yesterday morning with Manar,

1) we fixed the threshold level of the laser input signal which makes the measurement of the repetition rate.
(if the rep rate is not measured properly, the amplifier safety interlock stops immediately the amplification).

we followed a tutorial from Guillaume Machinet.
when you start the Alphanov control software, 4 panels pops up : central control, 2nd stage amplifier, and 2 panels for controlling the pumps of the 3rd stage amplifier.
!!! Warning !!! ..... if you switch ON the amplifier using the central control panel, the amplifier starts immediately AT FULL POWER..... !!! Warning !!!
it is not mentionned in the tutorial document.
to prevent this problem, you first need to switch "Laser OFF" on the 2 panels controlling the pumps of the 3rd stage amplifier and let "Laser ON" only on the panel controlling the 2nd stage.

after starting the amplifier, we tried to find the median value of the threshold to get ~33MHz instead of 100MHz measured previously.
the initial voltage threshold on the photodiode measuring the rep rate was 0.4V which leads to get 100MHz.
first, we changed step by step the threshold to reach 0.87V => one gets 33MHz.
we tried the find the maximum threshold but once the level is above the signal maximum value, it triggers an alarm and stops immediately the amplifier.
then, one needs to restart completely the software which can be tedious due to connections/alarms issues.
finaly, we found out that the low and high level thresholds to get 33MHz were not reproductible at each start of the amplifier... :-(
then, we put the threshold at 1V following the turial procedure which seems to work.

2) we installed the optical scheme to make the beam profile measurement : see attached image
we used the HR mirror close to the amplifier output (as putting a wedge at that place is not convenient if you want to properly dump the transmission and reflections).
and then, we placed 2 wedges, using the front reflection to get low power beam profile.
the Thorlabs LB2 has been used to dump the transmission of the first wedge, it can handle 25kW/cm² and 25J/cm².
we used black aluminium screens to dump the secondary beams.
we measured after the 2 wedges :
amplifier at 20% => 71µW
amplifier at 30% => 139µW
amplifier at 40% => 200µW

it has to be compared with the amplifier power :
amplifier at 20%               =>               8.7 W
amplifier at 30%               =>               17 W
amplifier at 40%               =>               26 W

which leads to a reflection coefficient of the wedge of 0.28%.
=> OK, as one uses PS811-B Thorlabs 4° wedges with B coating.
with B coating, the reflectivity given by the manufacturer is around 0.3% @ 1030nm.

unfortunately, we had a "case temperature alarm" coming from the Alphanov software when we reached 40% for the amplification level.
this alarm stopped immediately the amplifier.
we saw that the chiller was in warning state too and the "present temperature PV" was not stable at all, flutuating by 3-4 degrees after the amplifier has been turned off...
we restarted several times the chiller to see if the problem disapears but it was still there ! => to be investiguated !

PS : we changed the USB cable between the amplifier controler and the PC to try to fix the several "connexion lost" problems but it didn't help...

PS2 : after discussing with Sophie Chance and Marie Jacquet, ThomX suffered a water circuit leakage on Monday:
the full circuit has been emptied and they had to remplace the water by some common water and not demineralized water....
it can be related to the chilller issue observed yesterday !

Ronic Chiche wrote:

today with Manar, we brought everything to make the profile measurement.

the chiller was in error because of the water level : we filled it in.
! warning ! there is no alarm signal, only a message on the screen.

we checked the incoming power measured by the software : 5.5 mW => OK
and we measured the output power (with pump) for :
0% => ~ 300 mW
10% => ~900 mW
20% => 8.65 W
30% => 17W

=> same as before.

the first HR mirror at the output of the amplifier was slightly scratched => we replaced it.

for sake of simplicity, we plan to use first a HR mirror and then 2x wedges for the profile measurement => to be checked next time.
we have to remove secundary beam reflections, then wedges are easier to use than AR/AR mirrors (as the 2 reflected beams are parallele).

at full power, the output power is ~ 70W
after 1st wedge : 2.8W
after 2nd wedge : 112 mW => the power should be low enough to use absorptive filters in front of the beam profiler.

 

 

 

 

 

 

 

 

 

 

 

 

Attachment 1: WhatsApp_Image_2023-02-27_at_6.07.00_PM.jpeg
WhatsApp_Image_2023-02-27_at_6.07.00_PM.jpeg
  191   Wed Mar 8 14:49:12 2023 Ronic ChicheFixedreportlasers and optics | softwareThomX iglooAlphanov amplifier beam profile measurement

this morning with Manar,
we checked the Alphanov amplifier issue : "The laser has been stopped because its power is too far from the nominal power".

the photodiode voltage measuring the output power has drifted again and then, the estimated output power was wrong, triggering an alarm issue.
I changed the "calibration" file to fix the issue : see the attached file
 

Ronic Chiche wrote:

This morning with Victor we took a reading of the beam profile using a 400 mm lens at 70 % and 100 % amplification.

Will process the data and add after

Note : after an hour and half of amplifier on at 70% we increased the power to 100%, and after ~ 10 minutes the amplifier turned off and showed an error on the software called MMD3

and an error of the power mentioning " Le laser a été arrêté parce que sa puissance est trop éloignée de la puissance nominale"

"The laser has been stopped because its power is too far from the nominal power"

after that, the amplifier worked in varying intervals until it switched off because of the previously mentioned error.

solution could be related to the configuration file values ??????

 

Ronic Chiche wrote:

On Monday 20th of February, Daniele and Viktor took some beam profile measurement data @ 50% of power amplification.

data and analysis can be found in the attached file.

Ronic Chiche wrote:

This morning with Daniele, we did a second measurement of the beam profile using a different lens of focal 400 mm.

at a power amplification of 20%

the amplifier stayed on for around one hour and a half with no errors. 

tomorrow will attemt to do one at higher amplification percentage.

data will be added after processing.

Ronic Chiche wrote:

This morning,

- with the "Alphanov" software => Central panel => "system" button => Watchdog "Period Max" was at 100ns and has been set to 200ns.
(Alphanov told me to change the value from 50ns to 100ns but it was already at 100ns, then I set it to 200ns).
=> to be checked with Alphanov : what is the meaning of this parameter.

- it seems the watchdog alarm is related to the "PD_IN" parameter value of the "LAL" software (5.5mW is OK, but 5.2mW triggers the alarm).
my understanding is the Threshold Voltage, which detects the input signal to measure the repetition rate, could be at a too high level... even very close to the max level of the signal.
then if the input decreases a little bit, the signal goes below this Threshold Voltage => the software does not detect a signal any more => it triggers the watchdog alarm and the amplifier stops
(which stops also the preamplifier, related to the PD_CRI of the "Alphanov" software which goes to ~0W. PD_Preamp2 is a copy of PD_CRI but in the "LAL" software).

then, I changed back the Threshold Voltage from 0.96V (to detect properly 33MHz rep rate) to 0.7V which is close to the original value (0.67V) but for which the software detects ~100MHz rep. rate !
with this Threshold level, I did a test by detuning very slightly the input power by unscrewing a little bit the fiber-fiber coupler => PD_IN = 4.9mW => no alarm triggered !
then I screwed back the coupler => PD_IN = 5.6mW.

I did a power test with 3rd stage of the amplifier at 20% during 15 minutes => no alarm.

conclusion : there is an issue with the rep rate detection.
at 33MHz, one needs to put the threshold at the limit of the signal which fires an alarm if the signal decreased a little bit.
by lowering the threshold => no more alarm (I hope) but a wrong rep rate value !

Ronic Chiche wrote:

With Daniele after, we took a readings of the beam with a lens of 750 mm.

From the observed data, we can state that the beam is not completely Gaussian M2 > 1, due to the variation of the ellipticity of the beam along the focused path 

readings have been saved and will be added after processing them.

Also adding to the previous comment about the error, after closing the bunker and starting the measurement we did not have issue for around 20 min then the same error appeared (alarm triggered by Watchdog) it shows when the input average power detected by the software was around 5.474 mW , I did a reset of the software then turned the amplifier on and the reading is 5.515mW it works for about 2 minutes (enough to take 2 readings) then it switches off. In addition, there was a drop in the power reading on the PD_preamp2 (which seems related to watchdog issue) we had to do this many times in order to finish taking the readings .

 

 

 

Ronic Chiche wrote:

we have had this new issue (watchdog alarm switching off the amplifier) for several days.

Alphanov mentionned it could come from the input oscillator stability (modelock loss for example).

Today,

- I tried to start the amplifier at 0% but it ended immediately in a "watchdog alarm" which stopped the amplifier
the input average power detected by the software was around 5.2mW, far above the 2mW needed by the amplifier.

- I checked the 33MHz oscillator at the output of the fiber connected to the Shafter-Kirchhoff fiber coupler with the Labbuddy fiber photodiode and a scope.
see the picture below : the peak are clean and at 33MHz... then, the Onefive oscillator is not faulty.

- after plugging back the fiber to the amplifier input, the input average power detected by the software increased a bit around 5.5 - 5.6mW.
I tried to start again the amplifier at 0% and now, it worked without any alarm !!!
then, the origin of the "watchdog alarm" was maybe the threshold on this input power.

Then, I launched the "Alphanov" software and changed again the "threshold level", previously set at 1V (see previous post below), to 0.96V !
with this threshold level, the Alphanov software detects at the beginning a frequency of 66MHz and then decreases slowly to 33MHz => to be understood.
it should allow also more room before triggering again the "watchdog alarm" if the input average power decreases a bit => to be confirmed by Alphanov.

 

Ronic Chiche wrote:

the laser amplifier worked for some days but it ended to a "watchdog" alarm which switches off the amplifier... investigation is ongoing

Ronic Chiche wrote:

Ronic on Friday operated the Amplifier from the Alphanov software, switched it off then turned on the LAL software,

and it worked for 40 min without issues or error appearing,

 

Ronic Chiche wrote:

this morning with Manar,

- we fixed the chiller problem (+/-2°C fluctuation around the set temperature value = 25°C).
we opened and closed several times the water valve of the primary circuit to remove air bubles => no effect on the temperature variations.
we put the chiller in "Auto-Tuning" (AT) mode, then pressed the "AT" key => the chiller tune its PID parameters to optimize its temperature stabilization => no more fluctuations (+/-0.2°C fluctuation around the set temperature value = 25°C).
we had anyway a "temperature case" alarm from the Alphanov software at P=40%*Pmax, which stops the amplifier.
we put the chiller it AT mode again but with some power in the amplifier => no difference, the temperature regulation seems very good now, but we still have some "temperature case" alarms... => contact Alphanov for that.

- we changed the mount of the 2nd wedge by a kinematic mount to help for the alignment and we added an iris in the path.
now the optical path seems OK to make the beam profile measurement easily.
as we have still amplifier stops due to "temperature case" alarm, even at low power (P=20%*Pmax), we stopped the measurements => see Manar logbook post.

 

Ronic Chiche wrote:

this morning with Manar,

- we checked first the chiller problem.
the fluctations of +/-2° around 25°C are still there.
I discussed with Jean-Noel Cayla about the possible problem of the "dirty" water in the primary circuit.
he told me that the water goes through 3 "effective" filters, then the water should not be too dirty in the primary circuit even if one uses "common water" to fill it.
he told me also that the water temperature could be a bit higher than before, around 22°C, and that could prevent a good thermal exchange with the secundary circuit (the one of the amplifier).
=> the resistivity is about 7Mohmhs.
we had again a "case temperature alarm" from the Alphanov Software, after 1h of work @ 20%
this stopped the amplifier, we did not restart it.

- we measured the beam path with the wedges :
compressor box output to mirror :    17cm
mirror to 1s wedge :                          24 cm
1st wedge to 2nd wedge :                 24.5 cm
2nd wedge to lift bottom mirror :       136 cm
lift bottom mirror to top mirror :          14 cm
lift top mirror to beam profiler (x=0) :   7 cm

- we measured the beam profile at 3 positions with amplifier @ 20% + 2 wedges :
the power is ~ 70 µW
we made the measurements at x=0, x=60 cm, x=120cm
after that, we had the Alphanov amplifier "temperature case incident" and we stopped the measurements.
 

Ronic Chiche wrote:

yesterday morning with Manar,

1) we fixed the threshold level of the laser input signal which makes the measurement of the repetition rate.
(if the rep rate is not measured properly, the amplifier safety interlock stops immediately the amplification).

we followed a tutorial from Guillaume Machinet.
when you start the Alphanov control software, 4 panels pops up : central control, 2nd stage amplifier, and 2 panels for controlling the pumps of the 3rd stage amplifier.
!!! Warning !!! ..... if you switch ON the amplifier using the central control panel, the amplifier starts immediately AT FULL POWER..... !!! Warning !!!
it is not mentionned in the tutorial document.
to prevent this problem, you first need to switch "Laser OFF" on the 2 panels controlling the pumps of the 3rd stage amplifier and let "Laser ON" only on the panel controlling the 2nd stage.

after starting the amplifier, we tried to find the median value of the threshold to get ~33MHz instead of 100MHz measured previously.
the initial voltage threshold on the photodiode measuring the rep rate was 0.4V which leads to get 100MHz.
first, we changed step by step the threshold to reach 0.87V => one gets 33MHz.
we tried the find the maximum threshold but once the level is above the signal maximum value, it triggers an alarm and stops immediately the amplifier.
then, one needs to restart completely the software which can be tedious due to connections/alarms issues.
finaly, we found out that the low and high level thresholds to get 33MHz were not reproductible at each start of the amplifier... :-(
then, we put the threshold at 1V following the turial procedure which seems to work.

2) we installed the optical scheme to make the beam profile measurement : see attached image
we used the HR mirror close to the amplifier output (as putting a wedge at that place is not convenient if you want to properly dump the transmission and reflections).
and then, we placed 2 wedges, using the front reflection to get low power beam profile.
the Thorlabs LB2 has been used to dump the transmission of the first wedge, it can handle 25kW/cm² and 25J/cm².
we used black aluminium screens to dump the secondary beams.
we measured after the 2 wedges :
amplifier at 20% => 71µW
amplifier at 30% => 139µW
amplifier at 40% => 200µW

it has to be compared with the amplifier power :
amplifier at 20%               =>               8.7 W
amplifier at 30%               =>               17 W
amplifier at 40%               =>               26 W

which leads to a reflection coefficient of the wedge of 0.28%.
=> OK, as one uses PS811-B Thorlabs 4° wedges with B coating.
with B coating, the reflectivity given by the manufacturer is around 0.3% @ 1030nm.

unfortunately, we had a "case temperature alarm" coming from the Alphanov software when we reached 40% for the amplification level.
this alarm stopped immediately the amplifier.
we saw that the chiller was in warning state too and the "present temperature PV" was not stable at all, flutuating by 3-4 degrees after the amplifier has been turned off...
we restarted several times the chiller to see if the problem disapears but it was still there ! => to be investiguated !

PS : we changed the USB cable between the amplifier controler and the PC to try to fix the several "connexion lost" problems but it didn't help...

PS2 : after discussing with Sophie Chance and Marie Jacquet, ThomX suffered a water circuit leakage on Monday:
the full circuit has been emptied and they had to remplace the water by some common water and not demineralized water....
it can be related to the chilller issue observed yesterday !

Ronic Chiche wrote:

today with Manar, we brought everything to make the profile measurement.

the chiller was in error because of the water level : we filled it in.
! warning ! there is no alarm signal, only a message on the screen.

we checked the incoming power measured by the software : 5.5 mW => OK
and we measured the output power (with pump) for :
0% => ~ 300 mW
10% => ~900 mW
20% => 8.65 W
30% => 17W

=> same as before.

the first HR mirror at the output of the amplifier was slightly scratched => we replaced it.

for sake of simplicity, we plan to use first a HR mirror and then 2x wedges for the profile measurement => to be checked next time.
we have to remove secundary beam reflections, then wedges are easier to use than AR/AR mirrors (as the 2 reflected beams are parallele).

at full power, the output power is ~ 70W
after 1st wedge : 2.8W
after 2nd wedge : 112 mW => the power should be low enough to use absorptive filters in front of the beam profiler.

 

 

 

 

 

 

 

 

 

 

 

 

 

Attachment 1: 20230308_124313.jpg
20230308_124313.jpg
  194   Mon Mar 13 16:10:24 2023 Ronic ChicheFixedreportlasers and optics | softwareThomX iglooAlphanov amplifier beam profile measurement

We took reading of the beam profile of the amplifier without a lens @ 30 cm from the 2nd wedge for amplification percentages

20-30-40-50-60-70-80-90-100 % another additional 3 readings will be taken at different locations for all amplification percentages.

 

Ronic Chiche wrote:

this morning with Manar,
we checked the Alphanov amplifier issue : "The laser has been stopped because its power is too far from the nominal power".

the photodiode voltage measuring the output power has drifted again and then, the estimated output power was wrong, triggering an alarm issue.
I changed the "calibration" file to fix the issue : see the attached file
 

Ronic Chiche wrote:

This morning with Victor we took a reading of the beam profile using a 400 mm lens at 70 % and 100 % amplification.

Will process the data and add after

Note : after an hour and half of amplifier on at 70% we increased the power to 100%, and after ~ 10 minutes the amplifier turned off and showed an error on the software called MMD3

and an error of the power mentioning " Le laser a été arrêté parce que sa puissance est trop éloignée de la puissance nominale"

"The laser has been stopped because its power is too far from the nominal power"

after that, the amplifier worked in varying intervals until it switched off because of the previously mentioned error.

solution could be related to the configuration file values ??????

 

Ronic Chiche wrote:

On Monday 20th of February, Daniele and Viktor took some beam profile measurement data @ 50% of power amplification.

data and analysis can be found in the attached file.

Ronic Chiche wrote:

This morning with Daniele, we did a second measurement of the beam profile using a different lens of focal 400 mm.

at a power amplification of 20%

the amplifier stayed on for around one hour and a half with no errors. 

tomorrow will attemt to do one at higher amplification percentage.

data will be added after processing.

Ronic Chiche wrote:

This morning,

- with the "Alphanov" software => Central panel => "system" button => Watchdog "Period Max" was at 100ns and has been set to 200ns.
(Alphanov told me to change the value from 50ns to 100ns but it was already at 100ns, then I set it to 200ns).
=> to be checked with Alphanov : what is the meaning of this parameter.

- it seems the watchdog alarm is related to the "PD_IN" parameter value of the "LAL" software (5.5mW is OK, but 5.2mW triggers the alarm).
my understanding is the Threshold Voltage, which detects the input signal to measure the repetition rate, could be at a too high level... even very close to the max level of the signal.
then if the input decreases a little bit, the signal goes below this Threshold Voltage => the software does not detect a signal any more => it triggers the watchdog alarm and the amplifier stops
(which stops also the preamplifier, related to the PD_CRI of the "Alphanov" software which goes to ~0W. PD_Preamp2 is a copy of PD_CRI but in the "LAL" software).

then, I changed back the Threshold Voltage from 0.96V (to detect properly 33MHz rep rate) to 0.7V which is close to the original value (0.67V) but for which the software detects ~100MHz rep. rate !
with this Threshold level, I did a test by detuning very slightly the input power by unscrewing a little bit the fiber-fiber coupler => PD_IN = 4.9mW => no alarm triggered !
then I screwed back the coupler => PD_IN = 5.6mW.

I did a power test with 3rd stage of the amplifier at 20% during 15 minutes => no alarm.

conclusion : there is an issue with the rep rate detection.
at 33MHz, one needs to put the threshold at the limit of the signal which fires an alarm if the signal decreased a little bit.
by lowering the threshold => no more alarm (I hope) but a wrong rep rate value !

Ronic Chiche wrote:

With Daniele after, we took a readings of the beam with a lens of 750 mm.

From the observed data, we can state that the beam is not completely Gaussian M2 > 1, due to the variation of the ellipticity of the beam along the focused path 

readings have been saved and will be added after processing them.

Also adding to the previous comment about the error, after closing the bunker and starting the measurement we did not have issue for around 20 min then the same error appeared (alarm triggered by Watchdog) it shows when the input average power detected by the software was around 5.474 mW , I did a reset of the software then turned the amplifier on and the reading is 5.515mW it works for about 2 minutes (enough to take 2 readings) then it switches off. In addition, there was a drop in the power reading on the PD_preamp2 (which seems related to watchdog issue) we had to do this many times in order to finish taking the readings .

 

 

 

Ronic Chiche wrote:

we have had this new issue (watchdog alarm switching off the amplifier) for several days.

Alphanov mentionned it could come from the input oscillator stability (modelock loss for example).

Today,

- I tried to start the amplifier at 0% but it ended immediately in a "watchdog alarm" which stopped the amplifier
the input average power detected by the software was around 5.2mW, far above the 2mW needed by the amplifier.

- I checked the 33MHz oscillator at the output of the fiber connected to the Shafter-Kirchhoff fiber coupler with the Labbuddy fiber photodiode and a scope.
see the picture below : the peak are clean and at 33MHz... then, the Onefive oscillator is not faulty.

- after plugging back the fiber to the amplifier input, the input average power detected by the software increased a bit around 5.5 - 5.6mW.
I tried to start again the amplifier at 0% and now, it worked without any alarm !!!
then, the origin of the "watchdog alarm" was maybe the threshold on this input power.

Then, I launched the "Alphanov" software and changed again the "threshold level", previously set at 1V (see previous post below), to 0.96V !
with this threshold level, the Alphanov software detects at the beginning a frequency of 66MHz and then decreases slowly to 33MHz => to be understood.
it should allow also more room before triggering again the "watchdog alarm" if the input average power decreases a bit => to be confirmed by Alphanov.

 

Ronic Chiche wrote:

the laser amplifier worked for some days but it ended to a "watchdog" alarm which switches off the amplifier... investigation is ongoing

Ronic Chiche wrote:

Ronic on Friday operated the Amplifier from the Alphanov software, switched it off then turned on the LAL software,

and it worked for 40 min without issues or error appearing,

 

Ronic Chiche wrote:

this morning with Manar,

- we fixed the chiller problem (+/-2°C fluctuation around the set temperature value = 25°C).
we opened and closed several times the water valve of the primary circuit to remove air bubles => no effect on the temperature variations.
we put the chiller in "Auto-Tuning" (AT) mode, then pressed the "AT" key => the chiller tune its PID parameters to optimize its temperature stabilization => no more fluctuations (+/-0.2°C fluctuation around the set temperature value = 25°C).
we had anyway a "temperature case" alarm from the Alphanov software at P=40%*Pmax, which stops the amplifier.
we put the chiller it AT mode again but with some power in the amplifier => no difference, the temperature regulation seems very good now, but we still have some "temperature case" alarms... => contact Alphanov for that.

- we changed the mount of the 2nd wedge by a kinematic mount to help for the alignment and we added an iris in the path.
now the optical path seems OK to make the beam profile measurement easily.
as we have still amplifier stops due to "temperature case" alarm, even at low power (P=20%*Pmax), we stopped the measurements => see Manar logbook post.

 

Ronic Chiche wrote:

this morning with Manar,

- we checked first the chiller problem.
the fluctations of +/-2° around 25°C are still there.
I discussed with Jean-Noel Cayla about the possible problem of the "dirty" water in the primary circuit.
he told me that the water goes through 3 "effective" filters, then the water should not be too dirty in the primary circuit even if one uses "common water" to fill it.
he told me also that the water temperature could be a bit higher than before, around 22°C, and that could prevent a good thermal exchange with the secundary circuit (the one of the amplifier).
=> the resistivity is about 7Mohmhs.
we had again a "case temperature alarm" from the Alphanov Software, after 1h of work @ 20%
this stopped the amplifier, we did not restart it.

- we measured the beam path with the wedges :
compressor box output to mirror :    17cm
mirror to 1s wedge :                          24 cm
1st wedge to 2nd wedge :                 24.5 cm
2nd wedge to lift bottom mirror :       136 cm
lift bottom mirror to top mirror :          14 cm
lift top mirror to beam profiler (x=0) :   7 cm

- we measured the beam profile at 3 positions with amplifier @ 20% + 2 wedges :
the power is ~ 70 µW
we made the measurements at x=0, x=60 cm, x=120cm
after that, we had the Alphanov amplifier "temperature case incident" and we stopped the measurements.
 

Ronic Chiche wrote:

yesterday morning with Manar,

1) we fixed the threshold level of the laser input signal which makes the measurement of the repetition rate.
(if the rep rate is not measured properly, the amplifier safety interlock stops immediately the amplification).

we followed a tutorial from Guillaume Machinet.
when you start the Alphanov control software, 4 panels pops up : central control, 2nd stage amplifier, and 2 panels for controlling the pumps of the 3rd stage amplifier.
!!! Warning !!! ..... if you switch ON the amplifier using the central control panel, the amplifier starts immediately AT FULL POWER..... !!! Warning !!!
it is not mentionned in the tutorial document.
to prevent this problem, you first need to switch "Laser OFF" on the 2 panels controlling the pumps of the 3rd stage amplifier and let "Laser ON" only on the panel controlling the 2nd stage.

after starting the amplifier, we tried to find the median value of the threshold to get ~33MHz instead of 100MHz measured previously.
the initial voltage threshold on the photodiode measuring the rep rate was 0.4V which leads to get 100MHz.
first, we changed step by step the threshold to reach 0.87V => one gets 33MHz.
we tried the find the maximum threshold but once the level is above the signal maximum value, it triggers an alarm and stops immediately the amplifier.
then, one needs to restart completely the software which can be tedious due to connections/alarms issues.
finaly, we found out that the low and high level thresholds to get 33MHz were not reproductible at each start of the amplifier... :-(
then, we put the threshold at 1V following the turial procedure which seems to work.

2) we installed the optical scheme to make the beam profile measurement : see attached image
we used the HR mirror close to the amplifier output (as putting a wedge at that place is not convenient if you want to properly dump the transmission and reflections).
and then, we placed 2 wedges, using the front reflection to get low power beam profile.
the Thorlabs LB2 has been used to dump the transmission of the first wedge, it can handle 25kW/cm² and 25J/cm².
we used black aluminium screens to dump the secondary beams.
we measured after the 2 wedges :
amplifier at 20% => 71µW
amplifier at 30% => 139µW
amplifier at 40% => 200µW

it has to be compared with the amplifier power :
amplifier at 20%               =>               8.7 W
amplifier at 30%               =>               17 W
amplifier at 40%               =>               26 W

which leads to a reflection coefficient of the wedge of 0.28%.
=> OK, as one uses PS811-B Thorlabs 4° wedges with B coating.
with B coating, the reflectivity given by the manufacturer is around 0.3% @ 1030nm.

unfortunately, we had a "case temperature alarm" coming from the Alphanov software when we reached 40% for the amplification level.
this alarm stopped immediately the amplifier.
we saw that the chiller was in warning state too and the "present temperature PV" was not stable at all, flutuating by 3-4 degrees after the amplifier has been turned off...
we restarted several times the chiller to see if the problem disapears but it was still there ! => to be investiguated !

PS : we changed the USB cable between the amplifier controler and the PC to try to fix the several "connexion lost" problems but it didn't help...

PS2 : after discussing with Sophie Chance and Marie Jacquet, ThomX suffered a water circuit leakage on Monday:
the full circuit has been emptied and they had to remplace the water by some common water and not demineralized water....
it can be related to the chilller issue observed yesterday !

Ronic Chiche wrote:

today with Manar, we brought everything to make the profile measurement.

the chiller was in error because of the water level : we filled it in.
! warning ! there is no alarm signal, only a message on the screen.

we checked the incoming power measured by the software : 5.5 mW => OK
and we measured the output power (with pump) for :
0% => ~ 300 mW
10% => ~900 mW
20% => 8.65 W
30% => 17W

=> same as before.

the first HR mirror at the output of the amplifier was slightly scratched => we replaced it.

for sake of simplicity, we plan to use first a HR mirror and then 2x wedges for the profile measurement => to be checked next time.
we have to remove secundary beam reflections, then wedges are easier to use than AR/AR mirrors (as the 2 reflected beams are parallele).

at full power, the output power is ~ 70W
after 1st wedge : 2.8W
after 2nd wedge : 112 mW => the power should be low enough to use absorptive filters in front of the beam profiler.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Attachment 1: Beam_wavefront_30cm_no_Lens.jpg
Beam_wavefront_30cm_no_Lens.jpg
  202   Mon Mar 20 17:55:25 2023 Ronic ChicheFixedreportlasers and optics | softwareThomX iglooAlphanov amplifier beam profile measurement

due to several "case temperature" issues, I change the "Max case temperature" in the "general config" of the "Alphanov Software" from 50°C to 55°C.
=> validated by Alphanov.

Ronic Chiche wrote:

We took reading of the beam profile of the amplifier without a lens @ 30 cm from the 2nd wedge for amplification percentages

20-30-40-50-60-70-80-90-100 % another additional 3 readings will be taken at different locations for all amplification percentages.

 

Ronic Chiche wrote:

this morning with Manar,
we checked the Alphanov amplifier issue : "The laser has been stopped because its power is too far from the nominal power".

the photodiode voltage measuring the output power has drifted again and then, the estimated output power was wrong, triggering an alarm issue.
I changed the "calibration" file to fix the issue : see the attached file
 

Ronic Chiche wrote:

This morning with Victor we took a reading of the beam profile using a 400 mm lens at 70 % and 100 % amplification.

Will process the data and add after

Note : after an hour and half of amplifier on at 70% we increased the power to 100%, and after ~ 10 minutes the amplifier turned off and showed an error on the software called MMD3

and an error of the power mentioning " Le laser a été arrêté parce que sa puissance est trop éloignée de la puissance nominale"

"The laser has been stopped because its power is too far from the nominal power"

after that, the amplifier worked in varying intervals until it switched off because of the previously mentioned error.

solution could be related to the configuration file values ??????

 

Ronic Chiche wrote:

On Monday 20th of February, Daniele and Viktor took some beam profile measurement data @ 50% of power amplification.

data and analysis can be found in the attached file.

Ronic Chiche wrote:

This morning with Daniele, we did a second measurement of the beam profile using a different lens of focal 400 mm.

at a power amplification of 20%

the amplifier stayed on for around one hour and a half with no errors. 

tomorrow will attemt to do one at higher amplification percentage.

data will be added after processing.

Ronic Chiche wrote:

This morning,

- with the "Alphanov" software => Central panel => "system" button => Watchdog "Period Max" was at 100ns and has been set to 200ns.
(Alphanov told me to change the value from 50ns to 100ns but it was already at 100ns, then I set it to 200ns).
=> to be checked with Alphanov : what is the meaning of this parameter.

- it seems the watchdog alarm is related to the "PD_IN" parameter value of the "LAL" software (5.5mW is OK, but 5.2mW triggers the alarm).
my understanding is the Threshold Voltage, which detects the input signal to measure the repetition rate, could be at a too high level... even very close to the max level of the signal.
then if the input decreases a little bit, the signal goes below this Threshold Voltage => the software does not detect a signal any more => it triggers the watchdog alarm and the amplifier stops
(which stops also the preamplifier, related to the PD_CRI of the "Alphanov" software which goes to ~0W. PD_Preamp2 is a copy of PD_CRI but in the "LAL" software).

then, I changed back the Threshold Voltage from 0.96V (to detect properly 33MHz rep rate) to 0.7V which is close to the original value (0.67V) but for which the software detects ~100MHz rep. rate !
with this Threshold level, I did a test by detuning very slightly the input power by unscrewing a little bit the fiber-fiber coupler => PD_IN = 4.9mW => no alarm triggered !
then I screwed back the coupler => PD_IN = 5.6mW.

I did a power test with 3rd stage of the amplifier at 20% during 15 minutes => no alarm.

conclusion : there is an issue with the rep rate detection.
at 33MHz, one needs to put the threshold at the limit of the signal which fires an alarm if the signal decreased a little bit.
by lowering the threshold => no more alarm (I hope) but a wrong rep rate value !

Ronic Chiche wrote:

With Daniele after, we took a readings of the beam with a lens of 750 mm.

From the observed data, we can state that the beam is not completely Gaussian M2 > 1, due to the variation of the ellipticity of the beam along the focused path 

readings have been saved and will be added after processing them.

Also adding to the previous comment about the error, after closing the bunker and starting the measurement we did not have issue for around 20 min then the same error appeared (alarm triggered by Watchdog) it shows when the input average power detected by the software was around 5.474 mW , I did a reset of the software then turned the amplifier on and the reading is 5.515mW it works for about 2 minutes (enough to take 2 readings) then it switches off. In addition, there was a drop in the power reading on the PD_preamp2 (which seems related to watchdog issue) we had to do this many times in order to finish taking the readings .

 

 

 

Ronic Chiche wrote:

we have had this new issue (watchdog alarm switching off the amplifier) for several days.

Alphanov mentionned it could come from the input oscillator stability (modelock loss for example).

Today,

- I tried to start the amplifier at 0% but it ended immediately in a "watchdog alarm" which stopped the amplifier
the input average power detected by the software was around 5.2mW, far above the 2mW needed by the amplifier.

- I checked the 33MHz oscillator at the output of the fiber connected to the Shafter-Kirchhoff fiber coupler with the Labbuddy fiber photodiode and a scope.
see the picture below : the peak are clean and at 33MHz... then, the Onefive oscillator is not faulty.

- after plugging back the fiber to the amplifier input, the input average power detected by the software increased a bit around 5.5 - 5.6mW.
I tried to start again the amplifier at 0% and now, it worked without any alarm !!!
then, the origin of the "watchdog alarm" was maybe the threshold on this input power.

Then, I launched the "Alphanov" software and changed again the "threshold level", previously set at 1V (see previous post below), to 0.96V !
with this threshold level, the Alphanov software detects at the beginning a frequency of 66MHz and then decreases slowly to 33MHz => to be understood.
it should allow also more room before triggering again the "watchdog alarm" if the input average power decreases a bit => to be confirmed by Alphanov.

 

Ronic Chiche wrote:

the laser amplifier worked for some days but it ended to a "watchdog" alarm which switches off the amplifier... investigation is ongoing

Ronic Chiche wrote:

Ronic on Friday operated the Amplifier from the Alphanov software, switched it off then turned on the LAL software,

and it worked for 40 min without issues or error appearing,

 

Ronic Chiche wrote:

this morning with Manar,

- we fixed the chiller problem (+/-2°C fluctuation around the set temperature value = 25°C).
we opened and closed several times the water valve of the primary circuit to remove air bubles => no effect on the temperature variations.
we put the chiller in "Auto-Tuning" (AT) mode, then pressed the "AT" key => the chiller tune its PID parameters to optimize its temperature stabilization => no more fluctuations (+/-0.2°C fluctuation around the set temperature value = 25°C).
we had anyway a "temperature case" alarm from the Alphanov software at P=40%*Pmax, which stops the amplifier.
we put the chiller it AT mode again but with some power in the amplifier => no difference, the temperature regulation seems very good now, but we still have some "temperature case" alarms... => contact Alphanov for that.

- we changed the mount of the 2nd wedge by a kinematic mount to help for the alignment and we added an iris in the path.
now the optical path seems OK to make the beam profile measurement easily.
as we have still amplifier stops due to "temperature case" alarm, even at low power (P=20%*Pmax), we stopped the measurements => see Manar logbook post.

 

Ronic Chiche wrote:

this morning with Manar,

- we checked first the chiller problem.
the fluctations of +/-2° around 25°C are still there.
I discussed with Jean-Noel Cayla about the possible problem of the "dirty" water in the primary circuit.
he told me that the water goes through 3 "effective" filters, then the water should not be too dirty in the primary circuit even if one uses "common water" to fill it.
he told me also that the water temperature could be a bit higher than before, around 22°C, and that could prevent a good thermal exchange with the secundary circuit (the one of the amplifier).
=> the resistivity is about 7Mohmhs.
we had again a "case temperature alarm" from the Alphanov Software, after 1h of work @ 20%
this stopped the amplifier, we did not restart it.

- we measured the beam path with the wedges :
compressor box output to mirror :    17cm
mirror to 1s wedge :                          24 cm
1st wedge to 2nd wedge :                 24.5 cm
2nd wedge to lift bottom mirror :       136 cm
lift bottom mirror to top mirror :          14 cm
lift top mirror to beam profiler (x=0) :   7 cm

- we measured the beam profile at 3 positions with amplifier @ 20% + 2 wedges :
the power is ~ 70 µW
we made the measurements at x=0, x=60 cm, x=120cm
after that, we had the Alphanov amplifier "temperature case incident" and we stopped the measurements.
 

Ronic Chiche wrote:

yesterday morning with Manar,

1) we fixed the threshold level of the laser input signal which makes the measurement of the repetition rate.
(if the rep rate is not measured properly, the amplifier safety interlock stops immediately the amplification).

we followed a tutorial from Guillaume Machinet.
when you start the Alphanov control software, 4 panels pops up : central control, 2nd stage amplifier, and 2 panels for controlling the pumps of the 3rd stage amplifier.
!!! Warning !!! ..... if you switch ON the amplifier using the central control panel, the amplifier starts immediately AT FULL POWER..... !!! Warning !!!
it is not mentionned in the tutorial document.
to prevent this problem, you first need to switch "Laser OFF" on the 2 panels controlling the pumps of the 3rd stage amplifier and let "Laser ON" only on the panel controlling the 2nd stage.

after starting the amplifier, we tried to find the median value of the threshold to get ~33MHz instead of 100MHz measured previously.
the initial voltage threshold on the photodiode measuring the rep rate was 0.4V which leads to get 100MHz.
first, we changed step by step the threshold to reach 0.87V => one gets 33MHz.
we tried the find the maximum threshold but once the level is above the signal maximum value, it triggers an alarm and stops immediately the amplifier.
then, one needs to restart completely the software which can be tedious due to connections/alarms issues.
finaly, we found out that the low and high level thresholds to get 33MHz were not reproductible at each start of the amplifier... :-(
then, we put the threshold at 1V following the turial procedure which seems to work.

2) we installed the optical scheme to make the beam profile measurement : see attached image
we used the HR mirror close to the amplifier output (as putting a wedge at that place is not convenient if you want to properly dump the transmission and reflections).
and then, we placed 2 wedges, using the front reflection to get low power beam profile.
the Thorlabs LB2 has been used to dump the transmission of the first wedge, it can handle 25kW/cm² and 25J/cm².
we used black aluminium screens to dump the secondary beams.
we measured after the 2 wedges :
amplifier at 20% => 71µW
amplifier at 30% => 139µW
amplifier at 40% => 200µW

it has to be compared with the amplifier power :
amplifier at 20%               =>               8.7 W
amplifier at 30%               =>               17 W
amplifier at 40%               =>               26 W

which leads to a reflection coefficient of the wedge of 0.28%.
=> OK, as one uses PS811-B Thorlabs 4° wedges with B coating.
with B coating, the reflectivity given by the manufacturer is around 0.3% @ 1030nm.

unfortunately, we had a "case temperature alarm" coming from the Alphanov software when we reached 40% for the amplification level.
this alarm stopped immediately the amplifier.
we saw that the chiller was in warning state too and the "present temperature PV" was not stable at all, flutuating by 3-4 degrees after the amplifier has been turned off...
we restarted several times the chiller to see if the problem disapears but it was still there ! => to be investiguated !

PS : we changed the USB cable between the amplifier controler and the PC to try to fix the several "connexion lost" problems but it didn't help...

PS2 : after discussing with Sophie Chance and Marie Jacquet, ThomX suffered a water circuit leakage on Monday:
the full circuit has been emptied and they had to remplace the water by some common water and not demineralized water....
it can be related to the chilller issue observed yesterday !

Ronic Chiche wrote:

today with Manar, we brought everything to make the profile measurement.

the chiller was in error because of the water level : we filled it in.
! warning ! there is no alarm signal, only a message on the screen.

we checked the incoming power measured by the software : 5.5 mW => OK
and we measured the output power (with pump) for :
0% => ~ 300 mW
10% => ~900 mW
20% => 8.65 W
30% => 17W

=> same as before.

the first HR mirror at the output of the amplifier was slightly scratched => we replaced it.

for sake of simplicity, we plan to use first a HR mirror and then 2x wedges for the profile measurement => to be checked next time.
we have to remove secundary beam reflections, then wedges are easier to use than AR/AR mirrors (as the 2 reflected beams are parallele).

at full power, the output power is ~ 70W
after 1st wedge : 2.8W
after 2nd wedge : 112 mW => the power should be low enough to use absorptive filters in front of the beam profiler.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  178   Mon Jan 9 14:03:16 2023 Manar AmerFixedreportlasers and optics | detectors and electronicsThomX iglooAlphanov amplifier beam profile Data

Adding the schematic of the measurements.,

the 4° Beam Deviation, AR Coating ( B coating)

The 3 data points taken of the beam profile are fitted in Gaussian Beam with taking the beam waist at the output of the compressor box.

Background is subtracted for all data points, the fit is more than 90% for all points.

a reading was observed with distance less than 200 cm before the periscope and the fit starts to degrade

reason probably be related to the bump beam !!! To be investigated by placing an iris.

Attachment 1: 2023_Alphanov_Beam_Profile_setup.jpg
2023_Alphanov_Beam_Profile_setup.jpg
Attachment 2: 20230109_beamprifile_20perc_ampli_X0.bmp
Attachment 3: 20230109_beamprifile_20perc_ampli_X60.bmp
Attachment 4: 20230109_beamprifile_20perc_ampli_X120.bmp
Attachment 5: 20230109_beamprifile_20perc_ampli_X0_fit.jpg
20230109_beamprifile_20perc_ampli_X0_fit.jpg
Attachment 6: 20230109_beamprifile_20perc_ampli_X60_fit.jpg
20230109_beamprifile_20perc_ampli_X60_fit.jpg
Attachment 7: 20230109_beamprifile_20perc_ampli_X120_fit.jpg
20230109_beamprifile_20perc_ampli_X120_fit.jpg
Attachment 8: Beam_data_fit.jpg
Beam_data_fit.jpg
  183   Mon Jan 30 17:40:10 2023 Manar AmerFixedreportlasers and optics | detectors and electronicsThomX iglooAlphanov amplifier beam profile Data

This Morning with Victor the amplifier was turned on @ 20% amplification (output ~ 9 W ) for approximately 3 hours and no error appeared.

I took data of the beam profile at different points without a lens after the 2 wedges 

@ 0% (only pump beam), output ~ 300 mW (taken from previous data) , output after 2 wedges 2.2 uW  

@ 20% amplification , output ~ 9 W (taken from previous data) , output after 2 wedges 58.6 uW

fit to be added after processing the Beam Profiles data files.

Data with the lens to be taken !!

Manar Amer wrote:

Adding the schematic of the measurements.,

the 4° Beam Deviation, AR Coating ( B coating)

The 3 data points taken of the beam profile are fitted in Gaussian Beam with taking the beam waist at the output of the compressor box.

Background is subtracted for all data points, the fit is more than 90% for all points.

a reading was observed with distance less than 200 cm before the periscope and the fit starts to degrade

reason probably be related to the bump beam !!! To be investigated by placing an iris.

 

  144   Fri Apr 8 13:34:54 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Pulse Duration

The pulse duration from the amplifier compressor output will be measured using PulseCheck autocorelator

a first alignment of the device was done, continuation in the afternoon.

YouTube link attached of the general operation of pulse check < 5 min :  https://www.youtube.com/watch?v=J1pNHYySSYg

Attachment 1: pulse-check_compressed.pdf
  145   Fri Apr 8 19:24:32 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Pulse Duration

Measurement of the pulse was done at the end of the afternoon, Pulse Duration FWHM = 12.9 ps

After a long process of adjusting the alignment and angle of the crystal inside the device

The power input on the PulseCheck device should be above the sensitivity, in our case we had 1 mW input.

To reach it, we removed one of the wedge mirrors and used dielectric mirrors with an amplification of 20% ~ 25 W direct output power.

The input to the pulsecheck must be horizontally polarized, which is why we used a polarizing beam splitter (PBS).

For a better pulse shape, Victor adjusted the "beam distance" and  "beam focus" nobs on the device.

Manar Amer wrote:

The pulse duration from the amplifier compressor output will be measured using PulseCheck autocorelator

a first alignment of the device was done, continuation in the afternoon.

YouTube link attached of the general operation of pulse check < 5 min :  https://www.youtube.com/watch?v=J1pNHYySSYg

 

Attachment 1: 20220401_Alphanov_Pulse_Duration.jpg
20220401_Alphanov_Pulse_Duration.jpg
Attachment 2: 20220408_AMplifier_133MHz_Pulse_duration.jpg
20220408_AMplifier_133MHz_Pulse_duration.jpg
Attachment 3: 20220408_AMplifier_133MHz_Pulse_duration_better_alignment.jpg
20220408_AMplifier_133MHz_Pulse_duration_better_alignment.jpg
  146   Fri Apr 8 19:25:16 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Pulse Duration

Pulse Duration FWHM = 12.9 ps

Manar Amer wrote:

Measurement of the pulse was done at the end of the afternoon, Pulse Duration FWHM = 12.9 ps

After a long process of adjusting the alignment and angle of the crystal inside the device

The power input on the PulseCheck device should be above the sensitivity, in our case we had 1 mW input.

To reach it, we removed one of the wedge mirrors and used dielectric mirrors with an amplification of 20% ~ 25 W direct output power.

The input to the pulsecheck must be horizontally polarized, which is why we used a polarizing beam splitter (PBS).

For a better pulse shape, Victor adjusted the "beam distance" and  "beam focus" nobs on the device.

Manar Amer wrote:

The pulse duration from the amplifier compressor output will be measured using PulseCheck autocorelator

a first alignment of the device was done, continuation in the afternoon.

YouTube link attached of the general operation of pulse check < 5 min :  https://www.youtube.com/watch?v=J1pNHYySSYg

 

 

  135   Tue Mar 22 21:19:48 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Profile

Today: Manar, Ronic and Aurlien started the study of the beam profile of the alphanov amplifier at high power.

The setup shown in the image shows how the power is reduced by using Anti-reflective mirrors,

pick up 1 : Anti-reflective coating on both sides , pick up 2 : Anti-reflective coating on one side and High reflectivity on the other

 

using this method, we avoid saturation and damage to the beam profiler from the high power amplified laser

in addition, an OD3 filter is placed in front of the beam profiler. and a reflective mirror is placed close to deflect the reflection from the mirror(pick up 1) second surface.

The beam observed is relatively well shaped and fitted up to 50% of amplification is where the shape starts to deform a little and is not well-fitted by a Gaussian. (image attached shows the fit for 60% amplification)

The cause is yet to be determined, as it could only be related to the reflections that occur from the mirrors (pick up 1 and pick up 2)

 

*** Note be always careful at High Power :)

 

 

 

 

Attachment 1: 22-03-2022_Alphanov_Beam_setup.png
22-03-2022_Alphanov_Beam_setup.png
Attachment 2: 22032022_10perc_133MHz_Amplifier_beamShape.bmp
Attachment 3: 22032022_20perc_133MHz_Amplifier_beamShape.bmp
Attachment 4: 22032022_30perc_133MHz_Amplifier_beamShape.bmp
Attachment 5: 22032022_40perc_133MHz_Amplifier_beamShape.bmp
Attachment 6: 22032022_50perc_133MHz_Amplifier_beamShape.bmp
Attachment 7: 22032022_60perc_133MHz_Amplifier_beamShape.bmp
Attachment 8: 22032022_60perc_133MHz_Amplifier_beamFit.png
22032022_60perc_133MHz_Amplifier_beamFit.png
  136   Tue Mar 22 21:20:28 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Profile

 

Manar Amer wrote:

Today: Manar, Ronic and Aurlien started the study of the beam profile of the alphanov amplifier at high power.

The setup shown in the image shows how the power is reduced by using Anti-reflective mirrors,

pick up 1 : Anti-reflective coating on both sides , pick up 2 : Anti-reflective coating on one side and High reflectivity on the other

 

using this method, we avoid saturation and damage to the beam profiler from the high power amplified laser

in addition, an OD3 filter is placed in front of the beam profiler. and a reflective mirror is placed close to deflect the reflection from the mirror(pick up 1) second surface.

The beam observed is relatively well shaped and fitted up to 50% of amplification is where the shape starts to deform a little and is not well-fitted by a Gaussian. (image attached shows the fit for 60% amplification)

The cause is yet to be determined, as it could only be related to the reflections that occur from the mirrors (pick up 1 and pick up 2)

 

*** Note be always careful at High Power :)

 

 

 

 

 

  137   Wed Mar 23 13:55:11 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Profile

Adding the fitted beam in 1D in Horizontal and vertical axis.

for 10%   to  60%

Manar Amer wrote:

 

Manar Amer wrote:

Today: Manar, Ronic and Aurlien started the study of the beam profile of the alphanov amplifier at high power.

The setup shown in the image shows how the power is reduced by using Anti-reflective mirrors,

pick up 1 : Anti-reflective coating on both sides , pick up 2 : Anti-reflective coating on one side and High reflectivity on the other

 

using this method, we avoid saturation and damage to the beam profiler from the high power amplified laser

in addition, an OD3 filter is placed in front of the beam profiler. and a reflective mirror is placed close to deflect the reflection from the mirror(pick up 1) second surface.

The beam observed is relatively well shaped and fitted up to 50% of amplification is where the shape starts to deform a little and is not well-fitted by a Gaussian. (image attached shows the fit for 60% amplification)

The cause is yet to be determined, as it could only be related to the reflections that occur from the mirrors (pick up 1 and pick up 2)

 

*** Note be always careful at High Power :)

 

 

 

 

 

 

Attachment 1: 22032022_10perc_133MHz_Amplifier_beamFit.png
22032022_10perc_133MHz_Amplifier_beamFit.png
Attachment 2: 22032022_20perc_133MHz_Amplifier_beamFit.png
22032022_20perc_133MHz_Amplifier_beamFit.png
Attachment 3: 22032022_30perc_133MHz_Amplifier_beamFit.png
22032022_30perc_133MHz_Amplifier_beamFit.png
Attachment 4: 22032022_40perc_133MHz_Amplifier_beamFit.png
22032022_40perc_133MHz_Amplifier_beamFit.png
Attachment 5: 22032022_50perc_133MHz_Amplifier_beamFit.png
22032022_50perc_133MHz_Amplifier_beamFit.png
Attachment 6: 22032022_60perc_133MHz_Amplifier_beamFit.png
22032022_60perc_133MHz_Amplifier_beamFit.png
  138   Fri Apr 1 23:59:51 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Profile

Today a second reading of the beam profile was done , with Victor ,Ronic, Aurlien and Manar

an additional set-up was made using two 4 deg wedges instead of High reflecting (HR) and Anti-reflecting (AR) mirrors.

Two reading were taken:

  • at the output of the compressor with a NE30A filter on the beam profiler
  • at the output of the amplifier with NE30A + NE10A filter on beam profiler

 

 

Manar Amer wrote:

Adding the fitted beam in 1D in Horizontal and vertical axis.

for 10%   to  60%

Manar Amer wrote:

 

Manar Amer wrote:

Today: Manar, Ronic and Aurlien started the study of the beam profile of the alphanov amplifier at high power.

The setup shown in the image shows how the power is reduced by using Anti-reflective mirrors,

pick up 1 : Anti-reflective coating on both sides , pick up 2 : Anti-reflective coating on one side and High reflectivity on the other

 

using this method, we avoid saturation and damage to the beam profiler from the high power amplified laser

in addition, an OD3 filter is placed in front of the beam profiler. and a reflective mirror is placed close to deflect the reflection from the mirror(pick up 1) second surface.

The beam observed is relatively well shaped and fitted up to 50% of amplification is where the shape starts to deform a little and is not well-fitted by a Gaussian. (image attached shows the fit for 60% amplification)

The cause is yet to be determined, as it could only be related to the reflections that occur from the mirrors (pick up 1 and pick up 2)

 

*** Note be always careful at High Power :)

 

 

 

 

 

 

 

  139   Sat Apr 2 00:45:25 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Profile

Readings of the beam shape and horizontal (upper plot) and vertical (lower plot) axis fit at the direct output of the amplifier.

The beam shape relatively shaped like an egg.

Manar Amer wrote:

Today a second reading of the beam profile was done , with Victor ,Ronic, Aurlien and Manar

an additional set-up was made using two 4 deg wedges instead of High reflecting (HR) and Anti-reflecting (AR) mirrors.

Two reading were taken:

  • at the output of the compressor with a NE30A filter on the beam profiler
  • at the output of the amplifier with NE30A + NE10A filter on beam profiler

 

 

Manar Amer wrote:

Adding the fitted beam in 1D in Horizontal and vertical axis.

for 10%   to  60%

Manar Amer wrote:

 

Manar Amer wrote:

Today: Manar, Ronic and Aurlien started the study of the beam profile of the alphanov amplifier at high power.

The setup shown in the image shows how the power is reduced by using Anti-reflective mirrors,

pick up 1 : Anti-reflective coating on both sides , pick up 2 : Anti-reflective coating on one side and High reflectivity on the other

 

using this method, we avoid saturation and damage to the beam profiler from the high power amplified laser

in addition, an OD3 filter is placed in front of the beam profiler. and a reflective mirror is placed close to deflect the reflection from the mirror(pick up 1) second surface.

The beam observed is relatively well shaped and fitted up to 50% of amplification is where the shape starts to deform a little and is not well-fitted by a Gaussian. (image attached shows the fit for 60% amplification)

The cause is yet to be determined, as it could only be related to the reflections that occur from the mirrors (pick up 1 and pick up 2)

 

*** Note be always careful at High Power :)

 

 

 

 

 

 

 

 

Attachment 1: 20220401_Alphanov_Beam_setup_before_compressor.jpg
20220401_Alphanov_Beam_setup_before_compressor.jpg
Attachment 2: 20220401_Amplifier_beforeCompressor_40perc_133MHz.bmp
Attachment 3: 20220401_Amplifier_beforeCompressor_50perc_133MHz.bmp
Attachment 4: 20220401_Amplifier_beforeCompressor_60perc_133MHz.bmp
Attachment 5: 20220401_Amplifier_beforeCompressor_70perc_133MHz.bmp
Attachment 6: 20220401_Amplifier_beforeCompressor_40perc_133MHz_BeamFit.png
20220401_Amplifier_beforeCompressor_40perc_133MHz_BeamFit.png
Attachment 7: 20220401_Amplifier_beforeCompressor_50perc_133MHz_BeamFit.png
20220401_Amplifier_beforeCompressor_50perc_133MHz_BeamFit.png
Attachment 8: 20220401_Amplifier_beforeCompressor_60perc_133MHz_BeamFit.png
20220401_Amplifier_beforeCompressor_60perc_133MHz_BeamFit.png
Attachment 9: 20220401_Amplifier_beforeCompressor_70perc_133MHz_BeamFit.png
20220401_Amplifier_beforeCompressor_70perc_133MHz_BeamFit.png
  140   Sat Apr 2 00:51:07 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Profile

Readings of the beam shape and fit at the output of the compressor

differance from previous reading is that here we used wedges instead of HR mirrors.

Similar to previous readings, the beam shape deforms and the Gaussian fit is bad after 50% amplification

Manar Amer wrote:

Readings of the beam shape and horizontal (upper plot) and vertical (lower plot) axis fit at the direct output of the amplifier.

The beam shape relatively shaped like an egg.

Manar Amer wrote:

Today a second reading of the beam profile was done , with Victor ,Ronic, Aurlien and Manar

an additional set-up was made using two 4 deg wedges instead of High reflecting (HR) and Anti-reflecting (AR) mirrors.

Two reading were taken:

  • at the output of the compressor with a NE30A filter on the beam profiler
  • at the output of the amplifier with NE30A + NE10A filter on beam profiler

 

 

Manar Amer wrote:

Adding the fitted beam in 1D in Horizontal and vertical axis.

for 10%   to  60%

Manar Amer wrote:

 

Manar Amer wrote:

Today: Manar, Ronic and Aurlien started the study of the beam profile of the alphanov amplifier at high power.

The setup shown in the image shows how the power is reduced by using Anti-reflective mirrors,

pick up 1 : Anti-reflective coating on both sides , pick up 2 : Anti-reflective coating on one side and High reflectivity on the other

 

using this method, we avoid saturation and damage to the beam profiler from the high power amplified laser

in addition, an OD3 filter is placed in front of the beam profiler. and a reflective mirror is placed close to deflect the reflection from the mirror(pick up 1) second surface.

The beam observed is relatively well shaped and fitted up to 50% of amplification is where the shape starts to deform a little and is not well-fitted by a Gaussian. (image attached shows the fit for 60% amplification)

The cause is yet to be determined, as it could only be related to the reflections that occur from the mirrors (pick up 1 and pick up 2)

 

*** Note be always careful at High Power :)

 

 

 

 

 

 

 

 

 

Attachment 1: 20220401_Alphanov_Beam_setup_after_compressor.jpg
20220401_Alphanov_Beam_setup_after_compressor.jpg
Attachment 2: 20220401_Amplifier_AfterCompressor_50perc_133MHz.bmp
Attachment 3: 20220401_Amplifier_AfterCompressor_60perc_133MHz.bmp
Attachment 4: 20220401_Amplifier_AfterCompressor_50perc_133MHz_BeamFit.png
20220401_Amplifier_AfterCompressor_50perc_133MHz_BeamFit.png
Attachment 5: 20220401_Amplifier_AfterCompressor_60perc_133MHz_BeamFit.png
20220401_Amplifier_AfterCompressor_60perc_133MHz_BeamFit.png
  141   Mon Apr 4 14:23:14 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Profile

Adding the readings  20% , 30% ,  40%  for output of amplifier after the compressor

 

Manar Amer wrote:

Readings of the beam shape and fit at the output of the compressor

differance from previous reading is that here we used wedges instead of HR mirrors.

Similar to previous readings, the beam shape deforms and the Gaussian fit is bad after 50% amplification

Manar Amer wrote:

Readings of the beam shape and horizontal (upper plot) and vertical (lower plot) axis fit at the direct output of the amplifier.

The beam shape relatively shaped like an egg.

Manar Amer wrote:

Today a second reading of the beam profile was done , with Victor ,Ronic, Aurlien and Manar

an additional set-up was made using two 4 deg wedges instead of High reflecting (HR) and Anti-reflecting (AR) mirrors.

Two reading were taken:

  • at the output of the compressor with a NE30A filter on the beam profiler
  • at the output of the amplifier with NE30A + NE10A filter on beam profiler

 

 

Manar Amer wrote:

Adding the fitted beam in 1D in Horizontal and vertical axis.

for 10%   to  60%

Manar Amer wrote:

 

Manar Amer wrote:

Today: Manar, Ronic and Aurlien started the study of the beam profile of the alphanov amplifier at high power.

The setup shown in the image shows how the power is reduced by using Anti-reflective mirrors,

pick up 1 : Anti-reflective coating on both sides , pick up 2 : Anti-reflective coating on one side and High reflectivity on the other

 

using this method, we avoid saturation and damage to the beam profiler from the high power amplified laser

in addition, an OD3 filter is placed in front of the beam profiler. and a reflective mirror is placed close to deflect the reflection from the mirror(pick up 1) second surface.

The beam observed is relatively well shaped and fitted up to 50% of amplification is where the shape starts to deform a little and is not well-fitted by a Gaussian. (image attached shows the fit for 60% amplification)

The cause is yet to be determined, as it could only be related to the reflections that occur from the mirrors (pick up 1 and pick up 2)

 

*** Note be always careful at High Power :)

 

 

 

 

 

 

 

 

 

 

Attachment 1: 20220401_Amplifier_AfterCompressor_20perc_133MHz.bmp
Attachment 2: 20220401_Amplifier_AfterCompressor_30perc_133MHz.bmp
Attachment 3: 20220401_Amplifier_AfterCompressor_40perc_133MHz.bmp
Attachment 4: 20220401_Amplifier_AfterCompressor_20perc_133MHz_BeamFit.png
20220401_Amplifier_AfterCompressor_20perc_133MHz_BeamFit.png
Attachment 5: 20220401_Amplifier_AfterCompressor_30perc_133MHz_BeamFit.png
20220401_Amplifier_AfterCompressor_30perc_133MHz_BeamFit.png
Attachment 6: 20220401_Amplifier_AfterCompressor_40perc_133MHz__BeamFit.png
20220401_Amplifier_AfterCompressor_40perc_133MHz__BeamFit.png
  142   Fri Apr 8 13:12:34 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Profile

This Morning, another reading was taken for the output of the amplifier after the compressor using 2 wedge mirrors.

In addition, a start of the calibration of a PulseCheck "Autocorrelator" to measure the pulse duration. 

note, the pulsed laser used is OneFive 133.33 MHz

Manar Amer wrote:

Adding the readings  20% , 30% ,  40%  for output of amplifier after the compressor

 

Manar Amer wrote:

Readings of the beam shape and fit at the output of the compressor

differance from previous reading is that here we used wedges instead of HR mirrors.

Similar to previous readings, the beam shape deforms and the Gaussian fit is bad after 50% amplification

Manar Amer wrote:

Readings of the beam shape and horizontal (upper plot) and vertical (lower plot) axis fit at the direct output of the amplifier.

The beam shape relatively shaped like an egg.

Manar Amer wrote:

Today a second reading of the beam profile was done , with Victor ,Ronic, Aurlien and Manar

an additional set-up was made using two 4 deg wedges instead of High reflecting (HR) and Anti-reflecting (AR) mirrors.

Two reading were taken:

  • at the output of the compressor with a NE30A filter on the beam profiler
  • at the output of the amplifier with NE30A + NE10A filter on beam profiler

 

 

Manar Amer wrote:

Adding the fitted beam in 1D in Horizontal and vertical axis.

for 10%   to  60%

Manar Amer wrote:

 

Manar Amer wrote:

Today: Manar, Ronic and Aurlien started the study of the beam profile of the alphanov amplifier at high power.

The setup shown in the image shows how the power is reduced by using Anti-reflective mirrors,

pick up 1 : Anti-reflective coating on both sides , pick up 2 : Anti-reflective coating on one side and High reflectivity on the other

 

using this method, we avoid saturation and damage to the beam profiler from the high power amplified laser

in addition, an OD3 filter is placed in front of the beam profiler. and a reflective mirror is placed close to deflect the reflection from the mirror(pick up 1) second surface.

The beam observed is relatively well shaped and fitted up to 50% of amplification is where the shape starts to deform a little and is not well-fitted by a Gaussian. (image attached shows the fit for 60% amplification)

The cause is yet to be determined, as it could only be related to the reflections that occur from the mirrors (pick up 1 and pick up 2)

 

*** Note be always careful at High Power :)

 

 

 

 

 

 

 

 

 

 

 

Attachment 1: 20220408_Amplifier_compressor_20perc.bmp
Attachment 2: 20220408_Amplifier_compressor_40perc.bmp
Attachment 3: 20220408_Amplifier_compressor_60perc.bmp
Attachment 4: 20220408_Amplifier_compressor_70perc.bmp
Attachment 5: 20220408_Amplifier_compressor_80perc.bmp
Attachment 6: 20220408_Amplifier_compressor_90perc.bmp
Attachment 7: 20220408_Amplifier_compressor_BeamFit_20perc.png
20220408_Amplifier_compressor_BeamFit_20perc.png
Attachment 8: 20220408_Amplifier_compressor_BeamFit_40perc.png
20220408_Amplifier_compressor_BeamFit_40perc.png
Attachment 9: 20220408_Amplifier_compressor_BeamFit_60perc.png
20220408_Amplifier_compressor_BeamFit_60perc.png
Attachment 10: 20220408_Amplifier_compressor_BeamFit_70perc.png
20220408_Amplifier_compressor_BeamFit_70perc.png
Attachment 11: 20220408_Amplifier_compressor_BeamFit_80perc.png
20220408_Amplifier_compressor_BeamFit_80perc.png
Attachment 12: 20220408_Amplifier_compressor_BeamFit_90perc.png
20220408_Amplifier_compressor_BeamFit_90perc.png
  147   Fri Apr 15 19:00:20 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Profile

Victor, Ronic, Manar

Today  was dedicated to the study of the CVBG, and it's effect on the beam profile

we opened the box containing the 2 CVBGs : The 2CVBG are glued from the bottom on a copper surface .

Using the beam viwer, the beam line inside the two CVBG is not at the exact center but not at the edges too and not hitting the boarders.

From the sides you see two lines, one is reflection on the metal.

 

To observe the effect of the first CVBG by itself, we blocked the second reflection into the 2nd CVBG.

By placing the D-shaped mirror just at the entrance of the 2nd CVBG (there was just enough space to put it)

Beam Profiler + OD 10E + OD 30E + OD(not known) placed at ~ 1 m from the output of compressor.

We see clearly a much better circular shape of the beam and a better Gaussian fit,

only above 90% where we see the fit percentage going down to ~ 86% and on just the Horizontal Axis.

 


 

 

 

Manar Amer wrote:

This Morning, another reading was taken for the output of the amplifier after the compressor using 2 wedge mirrors.

In addition, a start of the calibration of a PulseCheck "Autocorrelator" to measure the pulse duration. 

note, the pulsed laser used is OneFive 133.33 MHz

Manar Amer wrote:

Adding the readings  20% , 30% ,  40%  for output of amplifier after the compressor

 

Manar Amer wrote:

Readings of the beam shape and fit at the output of the compressor

differance from previous reading is that here we used wedges instead of HR mirrors.

Similar to previous readings, the beam shape deforms and the Gaussian fit is bad after 50% amplification

Manar Amer wrote:

Readings of the beam shape and horizontal (upper plot) and vertical (lower plot) axis fit at the direct output of the amplifier.

The beam shape relatively shaped like an egg.

Manar Amer wrote:

Today a second reading of the beam profile was done , with Victor ,Ronic, Aurlien and Manar

an additional set-up was made using two 4 deg wedges instead of High reflecting (HR) and Anti-reflecting (AR) mirrors.

Two reading were taken:

  • at the output of the compressor with a NE30A filter on the beam profiler
  • at the output of the amplifier with NE30A + NE10A filter on beam profiler

 

 

Manar Amer wrote:

Adding the fitted beam in 1D in Horizontal and vertical axis.

for 10%   to  60%

Manar Amer wrote:

 

Manar Amer wrote:

Today: Manar, Ronic and Aurlien started the study of the beam profile of the alphanov amplifier at high power.

The setup shown in the image shows how the power is reduced by using Anti-reflective mirrors,

pick up 1 : Anti-reflective coating on both sides , pick up 2 : Anti-reflective coating on one side and High reflectivity on the other

 

using this method, we avoid saturation and damage to the beam profiler from the high power amplified laser

in addition, an OD3 filter is placed in front of the beam profiler. and a reflective mirror is placed close to deflect the reflection from the mirror(pick up 1) second surface.

The beam observed is relatively well shaped and fitted up to 50% of amplification is where the shape starts to deform a little and is not well-fitted by a Gaussian. (image attached shows the fit for 60% amplification)

The cause is yet to be determined, as it could only be related to the reflections that occur from the mirrors (pick up 1 and pick up 2)

 

*** Note be always careful at High Power :)

 

 

 

 

 

 

 

 

 

 

 

 

Attachment 1: 20220415_Inside_CVBG_Box.jpg
20220415_Inside_CVBG_Box.jpg
Attachment 2: 20220415_CVBG.jpg
20220415_CVBG.jpg
Attachment 3: 20220415_Compressor_Box.png
20220415_Compressor_Box.png
Attachment 4: 10p_1CVBG.bmp
Attachment 5: 20p_1CVBG.bmp
Attachment 6: 30p_1CVBG.bmp
Attachment 7: 40p_1CVBG.bmp
Attachment 8: 50p_1CVBG.bmp
Attachment 9: 60p_1CVBG.bmp
Attachment 10: 70p_1CVBG.bmp
Attachment 11: 90p_1CVBG.bmp
Attachment 12: 20220415_D_shaped_Mirror_Blocking_2ndCVBG.jpg
20220415_D_shaped_Mirror_Blocking_2ndCVBG.jpg
Attachment 13: 10p_1CVBG_BeamFit.png
10p_1CVBG_BeamFit.png
Attachment 14: 20p_1CVBG_BeamFit.png
20p_1CVBG_BeamFit.png
Attachment 15: 30p_1CVBG_BeamFit.png
30p_1CVBG_BeamFit.png
Attachment 16: 40p_1CVBG_BeamFit.png
40p_1CVBG_BeamFit.png
Attachment 17: 50p_1CVBG_BeamFit.png
50p_1CVBG_BeamFit.png
Attachment 18: 60p_1CVBG_BeamFit.png
60p_1CVBG_BeamFit.png
Attachment 19: 70p_1CVBG_BeamFit.png
70p_1CVBG_BeamFit.png
Attachment 20: 90p_1CVBG_BeamFit.png
90p_1CVBG_BeamFit.png
  148   Tue Apr 19 12:15:43 2022 Manar AmerFixedreportlasers and opticsThomX iglooAlphanov amplifier Beam Profile

For better comparison ,

the measurements done previously with 2 CVBGs was done at ~ 30 cm and the one done on Friday was for 1 CVBG is at 1 m

so we did additional measurement for 2 CVBGs at 1 m, for 20 , 50 and 70 % amplification 

we clearly see the similar deformation at high power.

Conclusion : the effect is most likely coming from the 2nd CVBG

At 70 % victor optimized the horizontal axis for the injection mirror into 2nd CVBG , we see an improvement in the Gaussian fit on Horizontal and vertical axis of ~ 2%

Manar Amer wrote:

Victor, Ronic, Manar

Today  was dedicated to the study of the CVBG, and it's effect on the beam profile

we opened the box containing the 2 CVBGs : The 2CVBG are glued from the bottom on a copper surface .

Using the beam viwer, the beam line inside the two CVBG is not at the exact center but not at the edges too and not hitting the boarders.

From the sides you see two lines, one is reflection on the metal.

 

To observe the effect of the first CVBG by itself, we blocked the second reflection into the 2nd CVBG.

By placing the D-shaped mirror just at the entrance of the 2nd CVBG (there was just enough space to put it)

Beam Profiler + OD 10E + OD 30E + OD(not known) placed at ~ 1 m from the output of compressor.

We see clearly a much better circular shape of the beam and a better Gaussian fit,

only above 90% where we see the fit percentage going down to ~ 86% and on just the Horizontal Axis.

 


 

 

 

Manar Amer wrote:

This Morning, another reading was taken for the output of the amplifier after the compressor using 2 wedge mirrors.

In addition, a start of the calibration of a PulseCheck "Autocorrelator" to measure the pulse duration. 

note, the pulsed laser used is OneFive 133.33 MHz

Manar Amer wrote:

Adding the readings  20% , 30% ,  40%  for output of amplifier after the compressor

 

Manar Amer wrote:

Readings of the beam shape and fit at the output of the compressor

differance from previous reading is that here we used wedges instead of HR mirrors.

Similar to previous readings, the beam shape deforms and the Gaussian fit is bad after 50% amplification

Manar Amer wrote:

Readings of the beam shape and horizontal (upper plot) and vertical (lower plot) axis fit at the direct output of the amplifier.

The beam shape relatively shaped like an egg.

Manar Amer wrote:

Today a second reading of the beam profile was done , with Victor ,Ronic, Aurlien and Manar

an additional set-up was made using two 4 deg wedges instead of High reflecting (HR) and Anti-reflecting (AR) mirrors.

Two reading were taken:

  • at the output of the compressor with a NE30A filter on the beam profiler
  • at the output of the amplifier with NE30A + NE10A filter on beam profiler

 

 

Manar Amer wrote:

Adding the fitted beam in 1D in Horizontal and vertical axis.

for 10%   to  60%

Manar Amer wrote:

 

Manar Amer wrote:

Today: Manar, Ronic and Aurlien started the study of the beam profile of the alphanov amplifier at high power.

The setup shown in the image shows how the power is reduced by using Anti-reflective mirrors,

pick up 1 : Anti-reflective coating on both sides , pick up 2 : Anti-reflective coating on one side and High reflectivity on the other

 

using this method, we avoid saturation and damage to the beam profiler from the high power amplified laser

in addition, an OD3 filter is placed in front of the beam profiler. and a reflective mirror is placed close to deflect the reflection from the mirror(pick up 1) second surface.

The beam observed is relatively well shaped and fitted up to 50% of amplification is where the shape starts to deform a little and is not well-fitted by a Gaussian. (image attached shows the fit for 60% amplification)

The cause is yet to be determined, as it could only be related to the reflections that occur from the mirrors (pick up 1 and pick up 2)

 

*** Note be always careful at High Power :)

 

 

 

 

 

 

 

 

 

 

 

 

 

Attachment 1: 20p_2CVBG.bmp
Attachment 2: 50p_2CVBG.bmp
Attachment 3: 70p_2CVBG.bmp
Attachment 4: 70p_2CVBG_CVBG_Input_Mirror_Optimize.bmp
Attachment 5: 20p_2CVBG_BeamFit.png
20p_2CVBG_BeamFit.png
Attachment 6: 50p_2CVBG_BeamFit.png
50p_2CVBG_BeamFit.png
Attachment 7: 70p_2CVBG_BeamFit.png
70p_2CVBG_BeamFit.png
Attachment 8: 70p_2CVBG_CVBG_Input_Mirror_Optimize_BeamFit.png
70p_2CVBG_CVBG_Input_Mirror_Optimize_BeamFit.png
ELOG V3.1.4-395e101