Hi everyone,

Good news. I was finally able to sort out the login window issues on MOBY today and then get the BSG software updated and then collect some data (2x datasets today). Seems to be working well now. Finally.

So it is now set up to get data during the 22Z session.

• 3 background
• 5 light
• 3 background

One set of 3,5,3 with Es and Lu. And then a second set with just Lu (11 fits files per session).

This is how it was set up for M262.

Questions:

• a) we had talked about not waiting for 10 min for the BSG, but just going ahead and getting data as soon as cooled down - do we still want to go that way (i.e. get rid of the 10 min delay to sync with MOS?)
• b) still go at 22 z or switch to or add another time?
• c) are Ed working on this one? Should I add those? Do you know which track #?
• d) there was a problem with the BSG on M262 whereby switching external shutters caused some glitch that crashed the communications between the camera and the falcon. Thus, we stopped doing darks on M262 and switched to backgrounds only. I had forgotten about this until today when Mike was confused at odd behavior during his calibrations and I remembered��. Do we know if this BSG is expected to have the same problem? Should I try to switch it (i.e. take darks with the external shutter closed and internal open?)

Art ---- Art Gleason

There are two times on the day1 3 OCt data set. I called them day1 and day2 because my programs for the fits files can not haddle two data sets on one day.

In addition there was a data set with the date 2024. Art is checking it out. The data set looked like normal data to me, just the dates are wrong.

They might not be bogus but obviously the date is wrong.  I’ll have to check on that.     Did you look at them? Do they look like real data?    

Art    ----  Art Gleason

Hi Steph,

There is a problem setting the date of the BSG. There is no internal battery, so every time it boots it thinks it is 2011. Usually the date setting works fine, but sometimes when making a large jump (like from 2011 to 2017) it gets confused and apparently goes to 2024.

I’m testing a few possible options for a fix. None perfect yet, but I’ll get it to work. In the meantime, I don’t know a good way to tell exactly when the 2024 files came from. Their order should be correct but not sure which day or exactly the correct time of them.

Art