[Dsg-ltcc] ltcc testing

Marc Mcmullen mcmullen at jlab.org
Fri Feb 15 10:01:14 EST 2019


Hi Mauri,

This morning's issue:
Around 7 am the system lost communication with the S1 MFC. This caused the initialize count to escalate, which was what I detailed in the logbook entry this morning. This MFC is not being used, and is not critical. So, I put the system is in a mode that will disregard the communication error until we can investigate it, when there is an opening.


The testing is unrelated to the issue described above.


Today's testing:
I am testing an update to the LTCC gas controls. The code has an interlock built in which changes the flow to zero Lpm if the sector is outside of the minimum (1 iwc) or maximum (2.75 iwc) pressure set points.

Once the pressure is back inside those parameters, the flow needs to return to the previous set point.

The updated code will get the set point value from a configuration file, which gets updated as the set point gets changed and saved. Currently, we have the initial values hard coded in the software.

Regards,
Marc



________________________________
From: Maurizio Ungaro
Sent: Friday, February 15, 2019 9:31 AM
To: Marc Mcmullen; Yordanka Ilieva; Stepan Stepanyan
Subject: ltcc testing

Hi Marc,

Yordanka asked me to answer this. Please go ahead with the testing, can you tell us how long it will take, and the problem you're addressing?

Thanks,

Mauri



Good Morning Yordanka,

I would like to do some more testing, is it ok if I disable the cRIO Comms and ltcc gas alarms?

thanks,
Marc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-ltcc/attachments/20190215/239083f8/attachment.html>


More information about the Dsg-ltcc mailing list