<html><body><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div>Hello,<br></div><div><br data-mce-bogus="1"></div><div>The changes to trigger an automatic delay and VISA Clear when a Cerenox reads 325 K in the LV cRIO program have been deployed. The modifications are noted in the HBTORUS logbook at link below.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>https://logbooks.jlab.org/entry/3469806</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><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Ruben Fair" <rfair@jlab.org><br><b>To: </b>"Tyler Lemon" <tlemon@jlab.org><br><b>Cc: </b>"bachiman" <bachiman@jlab.org><br><b>Sent: </b>Tuesday, April 11, 2017 8:07:24 AM<br><b>Subject: </b>Re: [Dsg-hallb_magnets] temporary 325 K error solution and TR817FS at 325 K<br></div><br><div data-marker="__QUOTED_TEXT__"><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Thank you Tyler, Rama,<br></div><br><div>If you feel that the team would benefit from another get together to review all the screenshots thus far, please set it up.<br></div><br><div>Regards<br></div><br><div>Ruben<br></div><br><br><hr id="zwchr"><div><b>From: </b>"Tyler Lemon" <tlemon@jlab.org><br><b>To: </b>"bachiman" <bachiman@jlab.org>, "dsg-hallb magnets" <dsg-hallb_magnets@jlab.org><br><b>Sent: </b>Tuesday, April 11, 2017 8:02:17 AM<br><b>Subject: </b>[Dsg-hallb_magnets] temporary 325 K error solution and TR817FS at 325 K<br></div><br><div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div><div style="">Hello,<br></div><div style=""><br></div><div style="">TR817FS was at 325 K this morning. Attached is a screenshot of the Cerenox's raw data from the LV Chassis. The LV cRIO has been reset and TR817FS now reads ~4.5 K.<br></div><div style=""><br></div><div style="">Also, in attempts to find a way where the 325 K error can fix itself, I took the fact that we know restarting the LV cRIO program fixes the 325 K Error and modified the LV cRIO LabVIEW program to cause the entire cRIO wait for about five seconds and also clear all VISA buffers if a Cerenox reads 325 K. The delay/VISA Clear would hopefully replicate at least part of what happens when the LV cRIO is manually restarted. To prevent the LV cRIO from waiting five seconds on all DAQ loops if the delay and VISA Clear does not reset the error, there will also be code added to trigger the five second delay only once when a sensor first reads 325 K.<br style=""></div><br style=""><div style="">Just a note, though: if successful, these new additions should only be a temporary fix, as we still would not know what is really causing the error.</div><div style=""><br style=""></div><div style="">I plan to deploy the modified LabVIEW program to the LV cRIO this afternoon.<br style=""></div><br style=""><div style="">Best regards,<br style=""></div><div style="">Tyler</div></div></div><br>_______________________________________________<br>Dsg-hallb_magnets mailing list<br>Dsg-hallb_magnets@jlab.org<br>https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets</div></div><br></div></div></body></html>