2/21/2024 We bundled up the experiment again (but did not do all the securing of harnesses and connectors). Mated electrically but not mechanically with TM. No shutter door for this test. Lindsay ran the GSE solo for this test. Connected with TM: - power - EVTM - video - commands - SPARCS - shutter door harness - events GSE computer in CUS room. EVTM and umbi ethernet both into switch into computer. Connected the serial command cable. Note: Thanasi says that it's uncertain what will happen if both are plugged into the same computer during the test. May get two of everything on display and in logger. Perhaps best to test these one by one. ### `run1` 9:59 am Setting up for test. - Plugging EVTM data directly into GSE computer. Will check Umbi connection later. - Current 1.5A - Powering on SAAS as a check that commands work. 10:02 am. SAAS did indeed power on, good. Got the crosshairs! - 10:03 Power on CMOS1. - No EVTM packets. Troubleshooting. - Let's try switching to the other PSL cable. (I thought that one was the Umbi). - With this cable connected, I can see (I think) that CMOS1 is on. But I do not see Wireshark packets. - 10:09 switching back to EVTM cable. - 10:10 proceeding with turn-on, since commanding seems to work at least. - 10:11 CMOS2 on - 10:13 Everything is now on, current 3.9A - 10:15 Start data taking CdTe, full readout mode. - 10:16 Start CMOS data taking. - 10:17 Everything looks good (all systems powered on, GSE windows look good.) Gave TM the ok to start. - 10:19:00 on GSE computer clock is T-300 seconds exactly. - Note: wireshark is not showing me the packets; I'm guessing I do not have it set to capture from the right place. Not taking the time to troubleshoot this now since the acquired data looks fine. - Note: this test goes to +571 s, so we can do all the usual commands. - As practice, I will do the following commands: - T-100 Turn on HK power/temp readings - Hmmm. Power numbers did not appear in the GSE. Rest of display is still updating. It is possible that HK has already hung. - +30s Sent HV=0 command (set_can_broadcast_hv0v). HV values in GSE still say 60V. Seems that it didn't work. GSE display is still updating, so I don't think it's a hung GSE or telemetry issue. - T+120s Tried again. Same effect. - 10:26 set_can_broadcast_start. no change. - 10:27 Try stopping observation. This worked, and NOW HV updates to 0V. - 10:28 am Back to 60V. - 10:28 Started observation again. set_can_broadcast_start - Summary of situation: I could not get evidence that HV change during observation was correctly applied. Once I stopped the observation, the HV value that I had set DID update in the GSE. Issue is either that the HV still cannot be changed during OBS, or else that the DE HK HV value does not update during OBS. Perhaps the DE queues the command? - Around +449 I will start powering systems off. - 10:31:30 Timpix off. SAAS off. - Note: SAAS had already turned off! I did not see when this happened. - 10:32 current is 3.2A. - 10:33 powered off the DE and canisters. Test complete. 10:41 am They want to replay their EVTM file for me. Wireshark is not displaying packets for me (has not been today) so I'll just look at the GSE. Also try changing the ethernet port I'm using; maybe Wireshark is set to a particular port. (Shouldn't be, though, since it should be set by address.) ### `run2` - Did not mess with wireshark; we just replayed the data and I looked at it on the GSE. This was mid-stream, so I could see CdTe pedestals updating and the rate numbers changing. Looks fine, so we're calling this good. Sounds like their DECOM recorder is working now. I am not entirely sure that I got the run1 and run2 data files in the right place, but I took a stab at it. Use these notes to collate the data later if needed. Note: We did not try the Umbi ethernet connection after all. Try it in Alaska! ### `Timepix assessment` - 4:45 pm Milo and Lindsay - During the X-ray test on Saturday and Monday, it was found that Timepix was not functional. Late Monday, it was found that by turning on the HV while plugged directly into Timepix, we could get good data. Working hypothesis is that commands are not working to Timepix through the formatter. We think this *was* working post-vibe during the Timepix software updates, so it's possible that something got dropped during the last formatter software changes. - We are plugging in power and formatter data, and command uplink cable, and also plugging in Milo's computer directly to the Timepix box. Goal is to try sending commands and see if they are being received or not. We do not have a way to assess whether the HV is actually on, but Milo will look at the data files and see if the size is as expected and whether there are cosmic rays. - Power on to EXP 4:46 pm. Current is 0.35A as expected. - 4:49 pm powering on Timepix - Letting it sit for 5 minutes to get a "baseline" measurement. - 4:56 pm sending timepix erase_storage several times. This had no effect, so it is consistent with the idea that commands are not getting through. - 4:59 pm sending hv_ramp_up_start. We don't have a way to confirm whether this gets through, but Milo does not see a change in the size of the files. (Usually they see a change in the size of the files.) Taking data here for 2-3 minutes. - 5:04 pm Milo is changing HV via ssh. The 1s data files quickly get bigger (by a lot). This is typical while the HV is changing and settling. Will stay here for ~10 minutes to see how the data file size changes over time as things settle. - Result: After a few/several minutes, file size relaxed (not down to HV0 size, but to a medium size). - 5:22 pm Powered down Timepix.