The h2susb6 IO chassis seems to be missing a dac (dac_4). lspci
is listing 4 dacs, but 5 are needed for controls of ETMY and TMSY. See the SUS ETM controls wiring diagram (D1002741). h2susetmy uses dac0, dac1, and half of dac2 for OSEM coil drive signals, h2sustmsy uses half or dac2 for it's OSEM coil drive signals, and h2susetmy uses dac4 for it's ESD drive signals.
The new epics gateways installed to support CA connections between CDS, H2FE and H2PSL LANs enabled an EPICS "loop back" whereby on any LAN both the local IOC and the gateway responded to connection requests. Using the "signore" server ignore argument, these loop backs should now be eliminated.
(Sadecki, Bland, Buckland, Garcia) Today we: Attached the 4 Stay assemblies to the FMy (modification and recleaning complete), dog clamped them down and torqued the bolts to spec. Verified magnet polarities of all magnets on ITMy. Sorted, checked function on medm, and connected the 12 ITMy Top BOSEMs (model/code fixed). Finished the ITMy cable routing. Added ITMy Top Stage split lock collars. And FINALLY, Mated the ITMy Monolithic lower suspension to it's upper structure under the BSC8 ISI! Attached the sleeve (with only a few bolts, because we only want the payload right now and will maybe remove it again). Attached the LS cross braces. Attached Vibration Absorbers (with only a few bolts as these will be removed and replaced again). Again, the FMP tooling helped to ease the process. The mating screws for the Lower to Upper structures and the Sleeve are difficult to attach so we're considering looking into opening up some holes on the future units. Full picture collection from today is on ResourceSpace: https://ligoimages.mit.edu/?c=770 Tomorrow, the SEI crew will add ballast mass and rebalance the table. We will then work on lacing the cables up the suspension, reconnecting the wire segment between the UIM and top mass, and freeing the masses into suspension. Then we'll need to attach and align the BOSEMs before we can take transfer functions. A tall order for the last day of the week.
SUS-SEI cable connections at the cable brackets (ref D1101477): D1000225 - 180" cables: S1104876 cb3 floor2 connects to D100234 s/n 915 S1104877 cb3 floor3 connects to D100234 s/n 920 S1104875 cb3 floor4 connects to D100234 s/n 908 S1104871 cb2 floor2 connects to D1002522 s/n 912/d1002523 s/n 906 S1104874 cb2 floor3 connects to D1002522 s/n 933/d1002524 s/n 906 S1104872 cb2 floor 1 connects to D1001518 TCS Ring Heater - no serialization ESD Cables: D1001617-s1104939 cb4 connects to d1001472 s/n 004
Terry and Christina got second cleaning taken care of this morning. The ICC crew removed bolts from the dome and the appropriate doors, moved the purge air from HAM-9's west door and attached it to the BSC, and started removing feedthroughs and viewports. Mark asked John to have a look at a couple of viewports that had "discoloration" on them: one turned out to be something on the glass surface that was readily removed and the other one seemed to be a spot where a laser had gone astray. On another note, Rai and I spent some time in the optics lab looking at a couple of possible methods for documenting/quantifying particulate depletion on chamber surfaces.
I made a couple of minor tweaks to the h2susitmy model. Most of them were entirely cosmetic, but I did change a couple of the goto/from names to be a little more generic, mostly just to make things easier when porting the model to other quad suspensions (etmy, itmx, etc.). I recompiled the model to confirm that everything was kosher, and restarted it on h2susb478. The seemed to come back up fine after the restart...
However, during the restart I received a flood of the following messages:
CA.Client.Exception............................................... Warning: "Identical process variable names on multiple servers" Context: "Channel: "H2:SUS-ITMY_R0_COILOUTF_F2_SW1R", Connecting to: 10.201.0.28:56833, Ignored: 10.201.0.180:5064errlog = 31 messages were discarded Channel: "H2:SUS-ITMY_R0_COILOUTF_F2_Name03", Connecting to: h2susb478:56833, Ignored: 10.201.0.180:5064" Source File: ../cac.cpp line 1209 Current Time: Thu Oct 13 2011 17:33:47.977845564
I'm not sure what's causing this issue, although I note that Cyrus and Jim were working on EPICS gateway stuff earlier today.... Still investigating the issue...
Previously, we had no guidelines on how to connect our 25-pin cables (they are used for the Trilliums [D1100152] and as Extensions for the GS13s/L4Cs [D1100153]). These cables have Peek connectors on both ends, but one end is nickel plated; we weren't aware of an orientation for these cables, so we randomly had Peek/nickel plated connectors connected at the feedthru.
We were notified that the Peek connector must be connected at the feed-thru. This morning (4) of our cables were flipped around for the BSC8-ISI. BSC6-ISI is also connected correctly as well. Attached are photos of the wrong connectors plugged in at the feed-thru and the right ones plugged in.
The ETMY SUS model (h2susetmy) has been updated and brought into sync with the ITMY SUS model (h2susitmy).
This was done by taking the itmy model, modifying the cdsParameters and subsystem names appropriately, and fixing the IO wiring to match that of the SUS ETM controls wiring diagram D1002741-v3.
NOTE: the DIO stuff was not changed. As far as I can tell from the wiring diagram the BIO wiring for ETMY is the same as that for ITMY. However, I'm not entirely clear how the BIO interface works, so I may be misunderstanding the mapping. I'll try to confirm and post a follow up to this log.
NOTE: the model was compiled and installed but is not currently running.
(Hugh, Jim)
Balancing The System
After the Trillium Installation, the system was balanced today, with the hopes for Vincent to have an assembly to run tests on.
More Cabling Notes
Following up on Greg's cable work, today Hugh & Jim installed the Extensions for the Actuators, GS13, and L4Cs. From Greg's documentation, we can add these cable serial numbers:
Drawing # (D11001__) | S/N (S110____) | LOCATION |
---|---|---|
_48 | 4040 | Corner1_Stage1_Horiz Actuator Extension |
_48 | 4041 | Corner1_Stage1_Vert Actuator Extension |
_48 | 4040 | Corner1_Stage2_Horiz Actuator Extension |
_48 | 4039 | Corner1_Stage2_Vert Actuator Extension |
_53 | 5200 | Corner1_GS13_Extension |
_53 | 5203 | Corner1_L4C_Extension |
_48 | 4037 | Corner2_Stage1_Horiz Actuator Extension |
_48 | 4038 | Corner2_Stage1_Vert Actuator Extension |
_48 | 4034 | Corner2_Stage2_Horiz Actuator Extension |
_48 | 4036 | Corner2_Stage2_Vert Actuator Extension |
_53 | 5201 | Corner2_GS13_Extension |
_53 | 5204 | Corner2_L4C_Extension |
_48 | 4046 | Corner3_Stage1_Horiz Actuator Extension |
_48 | 4045 | Corner3_Stage1_Vert Actuator Extension |
_48 | 4043 | Corner3_Stage2_Horiz Actuator Extension |
_48 | 4044 | Corner3_Stage2_Vert Actuator Extension |
_53 | 4565 | Corner3_GS13_Extension |
_53 | 4563 | Corner3_L4C_Extension |
(Corey, Jim, Mitch, Vincent)
Installing/Testing Trilliums
We received a crate of (4) Trilliums this morning, and we immediately installed them into the BSC6-ISI (aka Unit#2).
One of our Trilliums we ended up pulling out (s/n 03). After it was tested, we were getting ready to bolt it to the Stage1 Floor, but the 1/4-20 bolt had issue dropping through the base flange of the Pod. We pulled out the pod and visually observed the base flange was slightly rotated wrt the pod. Enough so, that it was not easy to pass a 1/4" bolt through the hole. This is when we decided to install #31 here.
All of the Trilliums were passed tests for functionality (Vincent ran 5-10min power spectra), and the pressure sensors were also looked good on all four.
J. Batch, J. Garcia The new "h2susitmy" code was compiled and installed via the standard "make" and "make-install" commands on the "h2build" machine. The FrontEnd code was then begun on the "h2susb478" machine via the 'starth2susitmy' command. The new "h2susitmy" code corrects a Simulink diagram mislabelling.
Two additional EPICS gateways were started this morning to support the PSL network: server client ================ cds h2psl h2fe h2psl This adds to the existing gateways server client =============== cds h2fe h2psl h2fe (started Oct. 11) Linux and Mac workstations have had their login scripts changed to set the EPICS_CA_ADDR_LIST environment variable dynamically according to which network the workstation is connected.
I found what appeared to be some miswiring of a couple of channels from ADC0 to the R0 OSEM inputs to the ITMY QUAD_MASTER block in the h2susitmy model. I found:
ADC0_18 -> R0_OSEM_F1 ADC0_19 -> R0_OSEM_F2 ADC0_20 -> R0_OSEM_F3 ADC0_22 -> R0_OSEM_LF ADC0_23 -> R0_OSEM_RT ADC0_21 -> R0_OSEM_SD
However, according to D1001725-v7 the wiring should be:
ADC0_20 -> R0_OSEM_F1 ADC0_21 -> R0_OSEM_F2 ADC0_22 -> R0_OSEM_F3 ADC0_18 -> R0_OSEM_LF ADC0_19 -> R0_OSEM_RT ADC0_23 -> R0_OSEM_SD
I didn't find anything in the aLOG or svn log to indicate that the wiring should be any different than what's in the wiring document linked above, so I went ahead and fixed the model and committed the change (r1230).
I had made some reordering changes to the "h2susitmy.mdl" to fix the older (committed) version according to the new D1001725-v7 document. The changes I made were the same as mentioned above, but I did not commit the changes to the SVN because the Simulink diagram added a vertical line across the wiring coming from the ADC selector to the ADC inputs after I made the changes. I wanted to confirm changes and resolve this issue before compiling/rebuilding/reinstalling. A back-up of the earlier model before I made changes is in: '/ligo/svncommon/SusSVN/sus/trunk/QUAD/H2/ITMY/h2susitmy_111012_before_jeffg_changes.mdl'
Cleanrooms were moved into place today: 1 over the BSC, 1 over the HAM, 1 for the dome, 1 for garbing/staging, and 1 for wrap-bag-tag of viewports and feedthroughs. (So, this time around we'll be a FIVE-RING circus!) Many other items were staged in preparation for door/dome and table removal on Friday. First cleaning was done this afternoon.
The Main and Reaction Lower suspensions were married up and placed on the FMP lifting equipment today in prep for the move back to the QUAD Upper Structure on the ISI. We stalled on this a bit because the original marriage bolts didn't work with the newly fit Fiber Guards. Will need to update this in the QUAD model! We also started to map out the QUAD Top BOSEMs since we were hoping to get those roughly in place prior to reattaching the monolithic underneath. However, the cable signals were not mapping to what we expected (see Garcia's alog coming...), so we aborted to go sort out code/model issues.
Yesterday, we ran into issues with 2 of the 4 FMy Structure Stays for BSC8, namely that they were too long and could not mate correctly. With a Worden-waiver we cut down the tips of the D090002 pins by 1/4". They were wrapped in foil and ameristat with only the tip exposed during the modification, then they were recleaned and are in an airbake oven for 24 hours. The other 2 Stays were fit checked and mate properly. Kurt from CIT is visiting and found the problem in the SW model, so is updating drawings for the future units not yet procured.
For whatever reason (likely due to a change in the wiring, or just to the trickyness of the wiring to the front end) there were a couple of wiring mistakes in the h2susauxb478 model. I consulted H2 aLIGO BS, ITM and FM Suspensions Controls Wiring (D1001725) and was able to clean it up as best as I could. The model was then recompiled, installed, and restarted on h2susauxb478.
So it turns out that the wiring change was due to a reconfiguration of the cable layout to the QUAD M0 and R0 stages, as specified in #1508 and #1513. The wiring diagram in v7 of D1001725-v7 reflects the proper changes, and this is what the SUSAUX models were brought into line with, so all is good.
R. Lane, A. Ramirez Testing ITMY (QUAD 2) Took the Top Mass OSEM Coil Resistances, Photo Diode Voltages, and LED Voltages today. Took measurements at the connection between the octopus cables (D1000234) and the top mass extension cable. The OSEMS meet the requirements.* Coil Resistances: 39±1Ω PD Voltages: 1.01±0.05V LED Voltages: 0.53±0.05V Main Chain OSEM S/N Cable Coil(Ω) LED(V) PD(V) Face 1 481 695 36.3 1.017 0.554 Face 2 638 695 36.0 1.018 0.551 Face 3 501 695 36.4 1.018 0.558 Left 496 695 36.0 1.017 0.551 Right 499 698 36.5 1.018 0.558 Side 445 698 36.7 1.017 0.558 Reaction Chain OSEM S/N Cable Coil(Ω) LED(V) PD(V) Face 1 471 698 35.9 1.018 0.553 Face 2 484 698 36.4 1.018 0.554 Face 3 472 707 36.9 1.016 0.554 Left 630 707 36.8 1.017 0.562 Right 466 707 36.7 1.019 0.558 Side 415 707 36.0 1.018 0.559 *The requirement for the coil resistance to be 39±1Ω was defined at LLO using "extra long" non final cables. This requirement is not sufficient to determine if the resistance is within standard. I will inquire with the correct authorities to determine what the new value should be for the in-vacuum final cables. However, they do meet the tolerance of ±1Ω. We took the measurement at the octopus cable, not at the vacuum feed through simulator as specified. We did not have the cables available. Although this should not add more than a few tenths of an ohm to the final resistance and would not make up the difference.
The "M0 F2" OSEM now has a S/N 261. This is the current list on the H2 ITMY QUAD in the LVEA.
This solved the problem I was seeing in #1562. Both the h2susitmy and h2susetmy models have been restarted and are running fine.