<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000"><div>Hello Tyler,</div><div><br data-mce-bogus="1"></div><div>Could you please edit the user GUI in such a way that we have</div><div>all parameters for each sensor in one line. </div><div>For example</div><div>Name : current value : Low Limit : High Limit : Interlock Status : Enable/Disabl. : Interlock Errors </div><div>For a moment all these parameters are on two pages in different columns.</div><div><br data-mce-bogus="1"></div><div>The summary of interlocks is OK.</div><div><br data-mce-bogus="1"></div><div>We will appreciate if you can do it.</div><div>Thank you,</div><div>Valery</div><div> </div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Tyler Lemon" <tlemon@jlab.org><br><b>To: </b>dsg-rich@jlab.org<br><b>Sent: </b>Monday, November 27, 2017 4:40:03 PM<br><b>Subject: </b>[Dsg-rich] [New Logentry] RICH Hardware Interlock program updated<br></blockquote></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div id="center"><div id="main"><h1 class="node-title"><a href="https://logbooks.jlab.org/entry/3496634" rel="bookmark" target="_blank" data-mce-href="https://logbooks.jlab.org/entry/3496634">RICH Hardware Interlock program updated</a></h1><div class="date-vitals"><p class="author-datetime">Lognumber <a href="https://logbooks.jlab.org/entry/3496634" class="lognumber" target="_blank" data-mce-href="https://logbooks.jlab.org/entry/3496634">3496634</a>. Submitted by <a href="https://logbooks.jlab.org/user/tlemon" target="_blank" data-mce-href="https://logbooks.jlab.org/user/tlemon">tlemon</a> on Mon, 11/27/2017 - 16:35.</p><table class="field-vitals"><tbody><tr><th>Logbooks:</th><td><a href="https://logbooks.jlab.org/book/rich" target="_blank" data-mce-href="https://logbooks.jlab.org/book/rich">RICH</a></td></tr></tbody></table></div><div class="logentry node-content"><p>The LabVIEW program for the RICH hardware interlocks has been updated.</p><p>The updated program (interlock program version 23) has been deployed to the cRIO and set as its start-up application. Changes made in the update are listed below.</p><p>1.) Added subVI containing look-up table for all humidity sensor calibrations. Before, all humidity sensors had their own unique subVI with their calibration constants. Look-up table subVI puts all calibrations constants in the same subVI for easy access and changes. <em><span style="text-decoration: underline;" data-mce-style="text-decoration: underline;">NOTE</span>: all calibration constants in new subVI are the same as before the update. Only coding of how program obtains constants for sensors has changed.</em></p><p>2.) Debugged "threshold control" control on LabVIEW UI. Previously, program was stuck in "EPICS Threshold Control" mode and could not be changed on LabVIEW UI Expert tab. Found part of LabVIEW code causing issue and after correction, threshold control mode can now be toggled between "EPICS Threshold Control" mode and "UI Threshold Control" mode on the LabVIEW UI Expert tab.</p><p>3.) Enabled indicators on LabVIEW UI to show status of keyed override switches. Logic for indicator was already in program, but commented out as keyed switch hardware had not yet been installed. After enabling indicator, it was verified that the indicator correctly reads the status of the override switch.</p></div><div class="attachment-box"><br></div></div></div><br>_______________________________________________<br>Dsg-rich mailing list<br>Dsg-rich@jlab.org<br>https://mailman.jlab.org/mailman/listinfo/dsg-rich<br></blockquote></div></div></body></html>