Jim and I have been investigating DAQ issues with HEPI ETMY which started over the weekend. Brian noticed that HPI ETMY's L4C Sat Counter started looking like the WD threshold, and was also counting down from 89k to 30k which it should no longer need to do.

We are unsure about the details, but it appears that when Jeff restarted h1hpietmy at 15:02PDT Saturday afternoon , the old INI file was archived but the newer file was used. It would appear that the INI Checksum the FE sends to the DAQ was calculated from the archived file, so DAQ did not show a 0x2000 error for this model. At a later time of 18:50PDT Saturday Jeff restarted the DAQ, at which point the FE DAQ status went to 0x2000 and the data in the DAQ was mixed up (resulting in a WD threshold being named the Sat Count). When I pressed the "DAQ RELOAD" button for HPI ETMY monday morning at 10:24PDT the FE and DAQ synced up and the DAQ data became good again.

When the model was restarted on Sauturday it read the safe.snap file which set the WD threshold level high, hence the ramping back down to 30,000. The safe.snap is being corrected by Brian and Hugo.

I had to "DAQ RELOAD" h1hpibs on monday as well, so it could have the same issues over the weekend.

We suspect the fact that the make-install and model restart occured very close to each other may be a possible cause of the INI file mismatch, but this is pure speculation.

If commissioners suspect any DAQ issues with h1hpietmy and h1hpibs we should restart the models.