Thu May 2 22:43:36 2024, Tyler, Update, Electronics, RTD Readout Chassis Redesign
|
[Tyler, Jon]
Today the FROSTI RTD readout chassis underwent a redesign:
Instead of the original ratiometric method, which involved wiring the FROSTI RTDs in series, each element is individually powered by separate excitations. Each element additionally possesses its own reference resistor of 100 Ohm. Now, if an RTD experiences an electrical short, it should not affect the measurements of the others in sequence, as it had with the original design.
|
Mon May 13 13:03:41 2024, Tyler, Update, FLIR, Readout Code Updates
|
[Tyler]
Some changes have been made to the FLIR readout code to help improve its functionality:
- More accurate temperature readings than before due to updates in the calculation procedure. A bug was causing one of the parameters to not update correctly; this is now fixed.
- Saved data now stored in HDF5 files rather than CSV.
- User can now enable automatic data storage by specifying a collection interval (in minutes). The choice of manually saving data is still present if desired.
Below is an image of the graphical interface. This is an old screenshot. Visually, there is no difference between the older and newer version. The differences come from the list above, which help the user more reliably measure and store data for later analysis.
|
Mon Jun 3 14:14:39 2024, Tyler, Update, FLIR, Initial CIT FROSTI Analysis
|
[Tyler]
Attached below are the initial results of the CIT FROSTI testing analysis.
|
Mon Jun 10 14:52:38 2024, Tyler, Update, FLIR, CIT FROSTI Analysis Update
|
[Tyler]
Upon further inspection, one adjustment was made to the FROSTI profile analysis: changing the transmission value of the ZnSe viewport. It was initially assumed that the viewport possessed an AR coating, which would bring the transmission into the 90% range. Without the coating, it drops to roughly 70%. Assuming no coating, the estimated delivered power was calculated to be 11.7 W. This is consistent with the estimated power given from the Hartmann sensor analysis, thus it is believed that the viewport indeed had no coating.
Quote: |
[Tyler]
Attached below are the initial results of the CIT FROSTI testing analysis.
|
|
Mon Jul 29 13:39:16 2024, Tyler, Update, DAQ, RTD Parameter Calibration 
|
[Tyler]
Using the data taken during the FROSTI testing at Caltech, I attempted to find a better calibration of the RTD sensors, given our past issues with inaccurate readings. The fit parameters, alpha and beta, are still all different from the initial values given to us by Fralock (alpha = .003, beta = 1.003e-6, R_0 was not given), but the true values will differ based on factors such as part geometry.
Quote: |
Refitted RTD calibration, neglecting quadratic term:
R_0 (ohm) Alpha (1/C)
RTD 0 79.3962 0.002031
RTD 1 78.2874 0.002530
RTD 2 80.9775 0.002381
RTD 3 74.2947 0.003684
RTD 4 80.3199 0.002157
RTD 5 78.2106 0.002297
RTD 6 76.6825 0.002438
RTD 7 82.6645 0.002458
Measurements taken can be found here. An uncertainty of 1 C was assumed for temperature.
Quote: |
[Jon,Tyler]
We noticed that the RTD temperature readings given on the Cymac were off, and traced the issue to miscalibration in the relationship between the resistance and temperature of each RTD (Callendar-Van Dusen eqn). Below is the table of values inferred from independent measurements of temperature and resistance to rectify this problem. This data was then fitted to better determine the coefficients present in the temperature-resistance relation:
R_0 (ohm) Alpha Beta
RTD 0 80.8674 0.001315 4.273e-6
RTD 1 79.5704 0.001887 3.7873e-6
RTD 2 81.7334 0.002014 2.1724e-6
RTD 3 74.3060 0.003677 3.6022e-8
RTD 4 81.1350 0.001761 2.3598e-6
RTD 5 77.9610 0.002423 -7.5192e-7
RTD 6 78.7980 0.001373 6.2909e-6
RTD 7 83.8616 0.001890 3.3529e-6 |
|
|
Mon Jul 29 14:30:16 2024, Tyler, Update, Cleanroom, RIN Measurement Set-up
|
[Tyler]
I have begun moving parts into the cleanroom for the upcoming FROSTI RIN tests that will be conducted within the next few weeks. While waiting for the rest of the equipment to arrive to perform the full-scale tests, I have additionally moved the FROSTI under the shelf above the optical table, where it will stay for the meantime. As always, please use caution when in the cleanroom. Aside from the FROSTI, the IR photodetectors that will be used for the test are delicate and costly to replace.
|
Mon Aug 12 16:24:34 2024, Tyler, Update, Cleanroom, RIN Measurement Update 1 
|
[Tyler]
For some preliminary tests, I moved the IR photodetectors outside of the cleanroom and onto the other optical table. The basic goal was to obtain a signal from both photodetectors. To achieve this, one of the heater cartridges used for early FLIR measurements months ago was hooked up to a power supply (PS). The PS was set to supply 0.20 A with a voltage of 2.8 V; the corresponding power is thus 0.56 W. With this, I was able to measure a signal using the Red Pitaya, the device that will be used for following RIN measurements.
Quote: |
[Tyler]
I have begun moving parts into the cleanroom for the upcoming FROSTI RIN tests that will be conducted within the next few weeks. While waiting for the rest of the equipment to arrive to perform the full-scale tests, I have additionally moved the FROSTI under the shelf above the optical table, where it will stay for the meantime. As always, please use caution when in the cleanroom. Aside from the FROSTI, the IR photodetectors that will be used for the test are delicate and costly to replace.
|
|
Tue Sep 3 18:24:17 2024, Tyler, Update, CDS, Cymac Timing Chassis Issue
|
[Tyler, Jon]
The timing chassis used for the cymac has been shut off due to an unknown issue causing its supplied current to fluctuate. All real-time models will be suspended until a solution is found.
|
Mon Sep 16 14:59:51 2024, Tyler, Update, TCS, FLIR RIN Update 09/16
|
Below is the dark noise spectrum of the Red Pitaya, which was measured over the course of a weekend. Additionally, I have successfully measured a signal from the photodetectors with the FROSTI as the IR source, so it seems there shouldn't be any worry of these particular detectors not being feasible for the RIN measurement. |
Mon Sep 23 15:11:21 2024, Tyler, Update, Scripts/Programs, Effective Emissivity Analysis and RIN Update   
|
A quick update on the effective emissivity analysis for the CIT FROSTI testing:
I was able to (roughly) match the OPD data to a referenced COMSOL model, with an applied power of 12.6 W (as seen below). However, when changing the emissivity of the ETM in COMSOL, the dT profiles do not seem to change much. I am not sure as to why this is the case at the moment, and will continue to look further.
Additionally attached are the current RIN measurements of the FROSTI prototype. Shown is the PSDs of both channels, in reference to their individual backgrounds.
|
Wed Oct 2 12:20:43 2024, Tyler, Update, TCS, Updated FROSTI Analysis 10/02/2024
|
Attached below are updates on current FROSTI prototype analysis. |
Wed Oct 9 13:52:31 2024, Tyler, Update, TCS, RIN Update 10/09/2024
|
I tried adjusting the gain settings on the photodetectors to check if this would help improve the RIN spectra measurements. Overall, it doesn't look like it does, and if anything, looks worse. I assume this is so because as the gain is lowered, the amount of detectable signal from the FROSTI becomes smaller and smaller. |
Tue Oct 29 16:37:35 2024, Tyler, Update, Electronics, Red Pitaya OS Update
|
The Red Pitaya ecosystem has been upgraded to OS 2.00-35, with a key feature being greater freedom in adjusting the sampling frequency for signal analysis. Before, decimation factors could only be applied if they were a power of 2 (i.e 2,4,8,16,...) up to 65536. Now, the factors can be any power of two up to 16, and any whole number greater than 16 up to 65536. Further information can be found here. |
Wed Nov 13 14:03:32 2024, Tyler, Update, Electronics, RIN Update 
|
[Tyler]
We've added two low-pass filters in hopes of reducing any potential aliasing that may be introducing additional noise into the power spectra for the RIN measurements. It still looks like the noise levels are too high. Attached below are some recent measurements taken with the FROSTI powered on and off.
|
Wed Nov 20 12:59:37 2024, Tyler, Update, Electronics, RIN Update
|
I went ahead and compared the noise spectrum of the ADC to those of the photodetectors with the FROSTI on and off. As discussed last meeting, it looks like the measurements with the Red Pitaya (RP) are limited by the ADC noise floor. Another avenue to explore in this measurement could be switching to the cymac ADCs. |
Wed Nov 27 13:48:01 2024, Tyler, Update, Electronics, RIN Update
|
[Tyler]
I downgraded the Red Pitaya back to OS 2.00-18 due to runtime errors during measurement. Once I did this, the device appeared to work much better than it has the last few weeks. First, it appears we can actually see the cutoff of the added low-pass filters that were added in to the RIN setup. Second, there does appear to be a difference again between the FROSTI ON state versus the dark state (i.e. FROSTI OFF). A long measurement of the ADC noise floor in the current configuration still needs to be recorded, but it does appear that the recent highlighted issues with the Red Pitaya have been solved.
|
Wed Dec 11 13:39:30 2024, Tyler, Update, Electronics, RIN Update 12/11/2024
|
[Tyler]
Attached below are updated ASD plots for the FROSTI RIN measurements. The parameters set for this are the following:
- DFT Size (N): 16384
- Sampling Frequency (F_s): 7.629 kHz
- Resolution (F_s/N): 0.47
- CH0 DC Voltage w/FROSTI ON: 113.6 mV
- CH0 DC Voltage w/FROSTI OFF: -5.7 mV
- CH1 DC Voltage w/FROSTI ON: 113.0 mV
- CH1 DC Voltage w/FROSTI OFF: -5.7 mV
Each measurement was recorded over a roughly two-day period. Before each spectrum was computed, the time-series signals were AC-coupled (i.e. the DC offset was subtracted from the data). The low-pass filters are still attached for dark and light noise measurements. ADC noise is measured with two 50-ohm terminators attached to the Red Pitaya inputs rather than the IR photodetectors.
|
Wed Dec 18 15:41:56 2024, Tyler, Update, TCS, FROSTI RIN
|
[Tyler]
I have begun the (hopefully) final RIN measurements at 3:30 PM today. If you need to go into the cleanroom at any time between now and Sunday (the 22nd), please do not touch the FROSTI, the Red Pitaya, the photodetectors, or any of the wiring. |
Mon Dec 23 14:33:36 2024, Tyler, Update, TCS, Latest RIN Measurement Results   
|
Attached below are the measurements I took from the FROSTI from 12/18-12/22. |
Tue Jan 14 10:27:14 2025, Tyler, Update, TCS, RIN Updates
|
[Tyler]
Attached below are updated plots for the FROSTI RIN measurements for Jan 14 group meeting.
|
Fri Jan 17 13:27:07 2025, Tyler, Update, TCS, FROSTI Pre-disassembly 
|
[Tyler, Ma, Cece, Jon, Luke, Cynthia, Michael]
On Tuesday, we prepared the FROSTI for disassembly in anticipation of the APS filming that is set to take place in the labs. The FROSTI has been unbolted from the optical table in the cleanroom, with its wires weighted down and the majority of its screws removed to ensure an easy removal of the reflectors during the filming process.
|
Wed Jan 22 10:50:08 2025, Tyler, Update, TCS, FROSTI Disassembly   
|
[Tyler, Ma, Cece, Luis, Shane, Luke, Cynthia, Liu, Jon]
On Tuesday (Jan 21), we took the FROSTI apart in front of a filming crew. It was a success! The footage is going to be used in an APS video detailing the experimental cosmology research conducted in the department.
The FROSTI reflectors, heater elements, and legs were all bagged separately and a currently being stored in the cleanroom. If you need to do any work in there, please be mindful of these parts. The elements are currently on the shelf above the optical table, and the reflectors are placed on the table in the back corner. |
Tue Feb 18 10:12:39 2025, Tyler, Update, TCS, Final RIN Plot Update   
|
Below is a preview of the final RIN figure that will be included in the FROSTI instrument paper. A quick summary of what is shown below:
The original RIN CSD measurement is shown on the top panel in red. Frequency bins that exhibit external electronics noise (ex. ADC, photodetector noise, etc.) are identified and shaded in gray. These noisy bins are then excluded from the dataset before beginning the next step in the analysis process: rebinning. Here, the resolution of the spectrum can be changed by averaging frequency bins together within a specified interval, with the goal of pushing the measurement curve closer to the A+ requirement shown in the figure. For demonstration below, the spectrum goes from a resolution of ~0.93 Hz to 14.90 Hz.
|
Tue Mar 4 10:28:58 2025, Tyler, Update, TCS, RIN Plot Updates 
|
|
Tue Jun 27 14:04:42 2023, Sophia A. , Update, Measuring Noise in Interferometer, Interferometer set up and connection to red pitaya  
|
Today we (Sophia and Tyler) constructed the set-up for the electrical noise calculation that I will be conducting this summer. I have included images of the setup below. Our system is effectively a green laser, that feeds into a type of polarizer, then into a beam splitter which sends the laser light down two arms into detectors. We started by connecting the detectors to an oscilloscope to determine whether the signal will exceed 1V, as the red pitaya (our planned data collection device) cannot receive signals with a higher voltage than 1V. We spent most of our time calibrating the oscilloscope and fine-tuning the set-up so that we would have approximately equal voltages in each arm of the interferometer. Once confirming that the output voltage would not meet or exceed 1V, we switched from an oscilloscope to the red pitaya for our measurements. Now that the system is set up, we will be able to run code in the red pitaya interface that will run an FFT on the signal, and then do noise analysis from there. |
Tue Jul 18 14:13:46 2023, Sophia , Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis 6x
|
We [Sophia and Tyler] have found a code which will partition our data and generate PSD's and CSD's automatically. We are now in the stage of writing this into a dynamic code, which so far has been fast-paced because of the framework we have built for it over the past few weeks.
Something to note is that we have found, especially over long periods of time, the laser goes through periods of extreme noise and the signals often cross from where we set them at some point throughout our data collection. We have made the assumption that this is something to do with the laser itself, and not our setup or surrounding space because of both the times that these noise/intensity spikes took place and the duration of the spikes (1.5-2.5 hours). To try and correct for this, we have been "cutting" the noise, and just looking at sections which don't include these big fluctuations. An example of the "noise cut data" is shown in the graph titled "Signals Over Time 7-18-23 Noise Cut Data" and all of the PSD/CSD graphs have been made using only these "noise cut" regions. |
Thu Jul 27 11:28:36 2023, Sophia , Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots   
|
This week I have successfully been able to implement our dynamic CSD and PSD plotting code, but along the way I encountered a few challenges which I will outline in this elog post.
Challenges:
1. Once I was able to plot the data through time, I produced a graph of the raw data (shown below in the top to images) which showed pulsed data instead of a continuous stream. On Tuesday (26th of July) Tyler and I fixed this issue, realizing that calling the starting the trigger in the red pitaya was the issue. When I commented that line of code out, it immediately started plotting continuously.
2. When that issue was solved, We then started having problems with the automatically generated lines in the python program which would double back on each new iteration. I am still dealing with this issue, because the line likes to follow the progression of the data intake instead of through the plot. Currently, I am trying to plot the data as a scatter plot and then add the line as this might make it care only about the data's distribution instead of the order of the points in the list, but I am still unsure. I might try out np.sort (or some equivalent to sort the entire data set before plotting) as well. |
Thu Jul 27 14:11:42 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots
|
Here's a screen recording of the dynamic raw data and PSD/CSD plots as they are now. Will begin working on implementing a code to generate the statistical estimator for the CSD uncertainty now. (Will talk to Tyler more about whether I can get the lines to happen or not) |
Mon Jul 31 19:27:30 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots    
|
An update on the CSD/PSD code:
The code is now taking a dynamic average of the points, and that has significantly reduced the noise that we were reading and the issues I was having with the lines in the plots. The graph for the CSD is still putting up a fight though, and amassing many lines that do not appear when just scatter plotted. I plan to fix that tomorrow, alongside inserting my own generated signal into the data. I have plotted the coherence alongside these graphs (as shown in the first screen recording and in one of the images), and it is significantly less than 1-- starting at or below 10^(-1).
As a note, I am unsure of why the raw data looks like this-- the laser goes through periods of extreme noise and I think this data was taken during one of them. |
Tue Aug 1 15:44:31 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots 6x
|
We have identified two problems facing the intensity noise calculations, which we are working to solve.
The first of these problems, is that the red pitaya appears to be taking data approximately 4 times faster than we would expect from the decimation rate based on how quickly it runs. To see if this was affecting our data, we plugged the red pitaya into a function generator. We found that my code is able to identify the driving frequency, but consistently gives predictions that are roughly 7% greater than we expect. When we drive at 100 Hz, the plot says the peak is at 107 Hz, when driven at 400 Hz, we see between 422-427 Hz, etc. While this implies that the red pitaya is not taking data at a faster rate than we would expect (if it did we would anticipate a lower than expected frequency, by a factor of roughly 4), it does imply some intrinsic issue with either the red pitaya or with the code. To fix this, I am going to use my code on artificially generated signals and see if we still observe these issues. |
Mon Aug 7 15:36:18 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots 7x
|
Today I was able to fix the red pitaya's plotting problem, and get my code to recognize driving frequencies from the function generator to within a 0.5 Hz estimation. The sinusoidal plots I have included are from sending a 1 Hz signal into the red pitaya to see the signal in real time. This allowed me to see exactly where the system was messing up, and fix from the ground up. Once I had that working, I began to test sending in frequencies in the range that my PSD/CSD code could observe and I was able to identify each driving frequency within 0.5 Hz. My code was able to correctly identify a 500 Hz signal, while other analyzed frequencies in the observable range have fallen lower than the sent in frequency by a less than 0.5 Hz. I believe this issue comes from the strange speed that the red pitaya is still acquiring data, even with my fixing it to now observe a continuous signal. |
Tue Aug 8 16:47:11 2023, Sophia, Update, Scripts/Programs, Update on Dynamic CSD and PSD Plots  
|
We have fixed our rapid plotting error, and realized that this has not been affecting our data intake! Below is a video of the code progressing, alongside grabbed images of the raw data. The data is now continuous, and performs as we expect. Next, I plan to add a widget which will dynamically show the peak values instead of them just being printed in the terminal after each iteration. (Ignore the red box-- it was from me struggling with a now fixed issue). |
Tue Aug 15 10:35:00 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots    
|
I have successfully added a button to my graphics, but it has posed a strange issue with the CSD and PSD values. When I plot my original code, I still see the pretty peaks that I was getting originally, while my new code (as shown in the video and in the last screenshot) is giving me more of a line. In my code that gives the peak values, the CSD values also tend to fluctuate in this new code as well (shown in the first screenshot), before returning to the real value.
I think that there is a problem with the averaging and am hoping to solve this issue today with Tyler. This is good progress though! |
Tue Aug 15 13:32:37 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots  
|
I have now fixed all issues that I was having this morning, and have added text boxes which show the peak values of both PSD's and the CSD alongside the graphs. They also update continuously with the graph. This is shown in the top image. The laser was driven at 400Hz, and had 0.5V peak to peak voltage, both of which appear correctly in the below graphs.
Now that the code is almost fully working (we will finish debugging the screenshot method later today), our plan tomorrow is to drive the laser and see how the code performs with it. The below graph is from us driving the function generator at 100Hz to test the range.
Update:
Bottom graph is new version of graphs with better distribution of both graphs. |
Mon Jul 1 11:45:45 2024, Sid, Update, Interferometer Simulations,
|
Progress update: Most of last week was spent getting set up with SIS, and learning how to do basic simulations. The goal for this week is to begin reproducing the methodology from T2000338. I have begun with studying perturbations to mirror curvature and position in a simple FP cavity, but thus far have been unable to get the same results. |
Thu Nov 9 13:57:58 2023, Shane, Luis, Aiden, Tyler, Update, Cleanroom, cleanroom cleaning and particle count
|
[Aiden, Shane, Luis, Tyler]
cleaning cleanroom and particle count
- 12:30 pm: Tyler and Aiden started organizing cables in cleanroom
- 12:35 pm: started particle count in flow bench
- 0.3 u: 11681
- 0.5 u: 3284
- 1.0 u: 1039
- 12:50 pm: started cleanroom particle count
- zone 3:
- 0.3 u: 14549
- 0.5 u: 10351
- 1.0 u: 6194
- zone 4:
- 0.3 u: 10808
- 0.5 u: 4655
- 1.0 u: 1953
- 1:07 pm: began surface check and wipedown, including softwalls
- 1:19 pm: started vacuuming the floor
- 1:28 pm: finished vacuuming the floor
- 1:29 pm: started mopping the floor
- 1:33 pm: finished mopping the floor
- 1:34 pm: started cleaning the buckets
- 1:37 pm: started mopping with IPA wipes
- 1:39 pm: finished mopping with IPA wipes
- 1:40 pm: changed sticky floor mats
- 1:41 pm: started particle count
- zone 3:
- 0.3 u: 8397
- 0.5 u: 5071
- 1.0 u: 2618
- zone 4:
- 0.3 u: 6651
- 0.5 u: 4323
- 1.0 u: 2120
|
Mon Dec 11 12:58:57 2023, Shane, Luis, Update, CDS, DAC-ADC loopback test debugging
|
[Luis, Shane]
Working on debugging last week's weird results for the ADC-DAC loopback test for channels 14 and 15. With DAC output channels 12-15 connected to ADC input channels 12-15: tried setting matrix coefficients for channels 12-15 to 1, and as with last week's results, DAC is outputting as expected for all three channels and ADC is not reading in the signal (hovering around -4,-5) for channels 14 and 15. Channels 12 and 13 still reading in correctly. Tried switching DAC output plug into channels 0-3, with ADC input plugged into channels 12-15, and all input/output signals were reading correctly. Then switched to plugging in DAC output to channels 12-15 and ADC input to channels 0-3, and saw that channels 0-3 were only able to receive the first two ADC input values. This shows that channels 12-15 are capable of receiving the correct inputs from other channels, but are failing to produce outputs for channels 14 and 15. |
Thu Nov 2 17:14:36 2023, Shane, Jon , Update, CDS, CyMAC set up permanentized    
|
CyMAC connections have been finalized and made permanent. Also tested voltages, which are all looking good. Warning: power is on. Do not touch power supply terminals or screws connected to grounding cables (see attached images 4 and 5; green wires on back of power supply with black and yellow covers, and exposed positive and negative terminals on back of power supply).
Also established connections from Anti-Aliasing chassis to ADC adapter board, Anti-Imaging chassis to DAC adapter board, and binary in/out chassis to BIO card, all mounted within Cymac host computer. Turned on CyMAC and ran test model, received error message likely pointing to timing signal not being successfully passed to the adapter boards. Next steps are checking to make sure correct timing signal is actually being output, and then checking internal ribbon cable in host chassis, which is another potential cause of the error.
|
Mon Jul 24 16:19:29 2023, Shane, Jon, Update, Electronics, Chassis semi-assembled and moved
|
Began assembly on AA and AI chassis today, moved them both to top work bench shelf (image attached). They are delicate so please do not disturb them or put anything on top of them. |
Thu Jul 27 14:46:55 2023, Shane, Jon, Update, Electronics, AA chassis DC on/off switch assembled
|
Made the first DC on/off switch assembly today and installed in anti-aliasing chassis. Second switch assembly to be completed later. |
Thu Aug 3 18:03:42 2023, Shane, Jon, Update, CDS, Anti-Aliasing chassis complete
|
We finished installing the internal power supply cables in the anti-aliasing chassis today, which concludes its assembly. Work on AI, BI, BO chassis still underway. |
Tue Aug 8 17:03:22 2023, Shane, Jon, Update, CDS, Binary input chassis finished
|
Finished assembly of the binary input chassis today, including DC on/off switch and LED installation. external cable assemblies still needed, but internal work done. |
Wed Aug 16 16:55:40 2023, Shane, Jon, Update, CDS, external power supply cables finished
|
All four external power supply cables for the CyMAC chassis are now assembled. Using them now to test if chassis power up correctly. |
Wed Aug 16 17:17:02 2023, Shane, Jon, Update, CDS, Binary input chassis powering correctly
|
Binary input chassis passed power-on test, and is lighting up as expected. Binary output chassis also successfully powered on. AA and AI chassis not powering on correctly, need to do some debugging to find the problem. |
Thu Sep 14 17:05:38 2023, Shane, Jon, Update, CDS, Timing chassis setup and testing
|
Tested the setup today for the timing chassis (intended to provide the timing reference for the CyMAC). Was able to read the correct frequency, but voltage was significantly lower than needed. Still identifying source of problem, and looking into the relationship between the supportable ohm load and the voltage. |
Fri Sep 29 17:27:30 2023, Shane, Jon, Update, CDS, Timing chassis assembly progress (CyMAC) 
|
Worked on timing chassis assembly today for the CyMAC, settled on layout (see attachment 1). Frequency synthesizer and frequency divider tentatively mounted. Next steps involve putting together and installing an LED and DC on/off switch assembly like the one in the binary input chassis (attachment 2 for comparison; orange and black wires in BI chassis analogous to red and black wires in timing chassis). Will also use front and back panels of BI chassis as a template for the timing chassis panels, with the following alterations: two SMB feedthroughs in place of the ribbon cable connections shown on the back panel, the addition of an LED on the front panel to indicate power, and potentially a spot on the front panel for usb connection to programmable frequency synthesizer. |
Mon Oct 9 16:59:21 2023, Shane, Jon, Update, CDS, timing chassis power cable and AI chassis testing for CyMAC
|
[Shane, Jon]
Today's CyMAC work:
- Finished assembling external power supply cable for the timing chassis (see attached image)
- Also did some debugging of AA and AI chassis re: power issues. After testing voltages at various test points on the power regulator board (TP1-TP6) in the AA chassis, it seems like it's the source of the problem. Used bench DC power supply to test, running 15V, and the correct voltage is coming in to the board but something significantly smaller is being output. We're also getting unexpected negative signs on voltage at certain test points, with leads in correct positions
- Upon further examination, it looks like the lights on the filter boards are actually turning on (in both the AA and AI chassis), though it's only 2/4 lights on each board and they are very faint
- Corrected DC on/off switch spade lug orientation in AI chassis.
- Tested AI chassis power regulator board to see if the problem was the same, and found again that voltage coming in was correct, and voltage going out was not.
- In case of interest in exact numbers, results were as follows:
- Voltage difference between TP1(+Vin) and TP6(-Vin) is ~30V
- Voltage difference between grounded chassis wall and TP1 (+Vin) is ~15V
- Voltage difference between grounded chassis wall and TP6(-Vin) is ~-15 V
- voltage difference between TP2(+Vout) and TP5(-Vout) is ~3V
- Voltage difference between TP3 (gnd) and TP2(+Vout) is -0.065V
- Voltage difference between TP5(-Vout) and ground is ~3V
|
Mon Oct 23 18:02:23 2023, Shane, Jon, Update, CDS, Timing chassis assembly complete  
|
Concluded assembly of timing chassis for CyMAC today; see attachment 1 for interior set up of chassis. Installed front and rear panels, wired on/off switch and LED assembly, and tested to confirm everything is powering on correctly. Also tested the outputted timing reference that will go to DAC and ADC adapter boards (see attachment 2 for output 1 and attachment 3 for output 2). |
Wed Jun 28 15:58:56 2023, Shane, Cao, Infrastructure, VAC, Power trip problem remains, source of smoke is insulation    
|
[Shane, Cao]
With the new change in wiring configuration described in elog 136, we tried to power up the heaters for baking the vacuum chamber again.
Given that we were worried about the turbo pump overheats, we set the setpoints of of bother high temperature controller and PID controller to be 120 deg C before turning the heaters on
1. Evidence of smoke originating from CoolSkin insulation
We then removed most of the CoolSkin insulation on the Pump and RGA lines ( apart from the one around the flexible bypass line connecting the two ) (see image Pumpline_afterRemoveInsul and RGAline_afterRemoeInsul) .
Upon removal of the insulation, we noticed that the insulating foam melted onto the heating tape (see image MeltedInsulation1 and MeltedInsulation2). This is the first indication that the smoke had most likely coming from the insulating foam itself
Once we started baking, upon reaching 80 degree range. We observed no smoke at the location that we removed the insulation. However, We observed smoked coming from underneath the insulation around the flexible pipe, and not from the velcro areas.
What could be causing this, given that the maximum operating temperature of the insulation is 200 deg C? Most likely, the heating tape is much hotter than we think it is. But given that the temperature sensor readout is much lower than 200 deg C, it's likely that this is due to poor thermal contact and it takes a while for sensor to reach a thermal equilibrium with the heating tape. Here, I suggest we should implement the following:
- We should look into usingsome form of thermal tape (if possible to secure the temperature sensors)
- Unfortunately or controller does not allow programming process, we will have to implement manual temperature stepping, emulating ramping process over the first hour, until slowly reach 120 deg C
- OR Tune the PID controller coeffs, especially P and I for longer rise time and settling time
2. The heaters still trip our power
Upon reaching 80 deg C,our main power trip. Unfortunately I don't know how to reset this. Do we need to contact facility on this? Reading elog 136, I noticed that both controllers are connected to the same circuit LP3B 6, which is the same circuit the some of the fan-filters and LED light panels of the cleanroom connected to. From the elog, the circuit has a 20 A limit . An max operation, the 2 heater controllers draw 30 Amps, approx 7 Amps for the fan-filters, and another 1.5 A for LED panel. The combination of these equipment must have overload the circuit and tripped it . Currently half the fans + lights are off in the cleanroom are off due to power trip. Here, I would make a suggestion that each heater controller should be connected to a separate circuit . Currently we LP3B 7 (same side next to LB3B 6) and LB3B 4 (opposite side of the rail) having no equipemts connected to them, but will require cable extensions. |
Fri Jul 28 13:07:39 2023, Shane, Aiden , Update, Cleanroom, cleanroom cleaning and particle count 6x
|
[Aiden, Shane]
cleaning cleanroom and particle count
- 11:08 am: started particle count
- zone 3:
- 0.3 u: 4198
- 0.5 u: 1080
- 1.0 u: 581
- zone 4:
- 0.3 u: 1247
- 0.5 u: 623
- 1.0 u: 415
- 11:24 am: break for removal of vac chamber insulation (pictures attached), with counts before removal as seen above, and counts after removal/replacement for zone 3 as follows:
- zone 3:
- 0.3 u: 2993
- 0.5 u: 415
- 1.0 u: 207
- 12:02 pm: began surface check and wipedown
- 12:13 pm: started vacuuming the floor
- 12:25 pm: finished vacuuming the floor
- 12:26 pm: started mopping the floor
- 12:32 pm: finished mopping the floor
- 12:32 pm: started cleaning the buckets
- 12:37 pm: started mopping with IPA wipes
- 12:43 pm: finished mopping with IPA wipes
- 12:45 pm: changed sticky floor mats
- 12:47 pm: started particle count
- zone 3:
- 0.3 u: 2951
- 0.5 u: 290
- 1.0 u: 41
- zone 4:
- 0.3 u: 290
- 0.5 u: 0
- 1.0 u: 0
|
|