<html><body><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div data-marker="__QUOTED_TEXT__"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000" data-mce-style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000;"><div>Nick,<br></div><br><div>It looks like somehow VT24-DAQ got removed from the cRIO. I will make the changes to correct this now. </div><div><br data-mce-bogus="1"></div><div>Deploying the changes will trip the Controlled Ramp Down interlock for Fast-Daq cRIO Comm but it will be able to be reset as communication is re-established.<br></div><div><br data-mce-bogus="1"></div><div>Best regards,<br data-mce-bogus="1"></div><div>Tyler<br data-mce-bogus="1"></div><br><hr id="zwchr"><div><b>From: </b>"Nicholas Sandoval" <sandoval@jlab.org><br><b>To: </b>"Tyler Lemon" <tlemon@jlab.org><br><b>Cc: </b>"Probir Ghoshal" <ghoshal@jlab.org>, "Ruben Fair" <rfair@jlab.org><br><b>Sent: </b>Wednesday, January 25, 2017 2:53:16 PM<br><b>Subject: </b>Check IDCCT Torus_FastDAQ:I.Data[24]<br></div><br><div>Hi Tyler,<br><br>IDCCT has not changed in the PLC since 12/13/16. Please double check that it is being sent to the PLC.<br><br>It may correlate to software changes or updates that was performed on that date.<br><br>Thank you,<br><br>Nick</div></div><br></div></div></body></html>