<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:27:09 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INSTRM-642] Adapt to new gatevalve interlock hardware and logic</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-642</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;The new gatevalve controller logic follows, per email. As far as safety goes, this takes over nearly all of the existing logic in the software. We still need to run (but modify) most of the &lt;tt&gt;gatevalve open&lt;/tt&gt; code, since that is what tells humans understandable diagnostics.&lt;/p&gt;

&lt;p&gt;------------------------------------------------------------------------------------------&lt;/p&gt;

&lt;p&gt;The new board has logic and a PIC&#8230; The logic for allowing the gate valve to open is as follows:&lt;/p&gt;

&lt;p&gt;GATE VALVE SOLENOID = OPEN &amp;amp; (TURBO_UPTO_SPEED | TURBO_OVERRIDE) &amp;amp; !TURBO_LOCKOUT &amp;amp; (PRESSURE_EQUAL | GATE_VALVE_OPEN) &amp;amp; PCM_24V&lt;/p&gt;

&lt;p&gt;TURBO_OVERRIDE is a latch, and is set when OPEN low, and cleared when turbo is up to speed.&lt;br/&gt;
TURBO_ LOCKOUT is a latch, and is cleared when open is low, disabled when TURBO_OVERRIDE is high, and set when TURBO_UPTO_SPEED drops out.&lt;/p&gt;

&lt;p&gt;All of the above is determined by logic gates, with the exception of the PRESSURE_EQUAL input, which is controlled by the PIC. The PIC will read 2 pressure sensors either side of the gate valve to make this determination. The logic overrides this signal once the gate valve is open.&lt;/p&gt;

&lt;p&gt;The PIC will also monitor the logic. The signals it will monitor are:&lt;/p&gt;

&lt;p&gt;OPEN&lt;br/&gt;
GATE_VALVE_OPEN&lt;br/&gt;
GATE_VALVE_CLOSED&lt;br/&gt;
TURBO_UPTO_SPEED&lt;br/&gt;
DEWAR_PRESSURE&lt;br/&gt;
ROUGHING_PRESSURE&lt;br/&gt;
GATE_VALVE_SOLENOID&lt;/p&gt;

&lt;p&gt;You will have a similar interface to before&#8230; You will control the OPEN signal, and monitor the GATE_VALVE_SOLENOID signal. You will no longer get GVO or GVC. Instead you will get access to all signals via an RS232 port.&lt;/p&gt;

&lt;p&gt;You will still need to assert the port on the PCM to allow the gate valve to be energized. This will be your secondary means of locking the gate valve.&lt;/p&gt;</description>
                <environment></environment>
        <key id="13509">INSTRM-642</key>
            <summary>Adapt to new gatevalve interlock hardware and logic</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="cloomis">cloomis</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>SM1</label>
                    </labels>
                <created>Wed, 3 Apr 2019 18:49:04 +0000</created>
                <updated>Wed, 5 Jun 2019 13:38:39 +0000</updated>
                            <resolved>Thu, 30 May 2019 20:43:46 +0000</resolved>
                                                                    <component>ics_xcuActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="15487" author="cloomis" created="Wed, 22 May 2019 14:56:19 +0000"  >&lt;p&gt;First interlock board will probably be available on b2 week of 05-27. This will take clock time to do.&lt;/p&gt;</comment>
                            <comment id="15603" author="cloomis" created="Thu, 30 May 2019 20:43:46 +0000"  >&lt;p&gt;Merged at c303d0e, tagged 1.9.0&lt;/p&gt;

&lt;p&gt;The PIC bootloader is not finished. I &lt;em&gt;believe&lt;/em&gt; the existing xcu code will work; if not I&apos;ll make a new ticket.&lt;/p&gt;

&lt;p&gt;Also, I was not able to test backward compatibility. Probably works and probably does not matter, unless we run into a fatal problem with the new board. The board has been pretty well tested so I&apos;d be surprised.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|u0009r:zzzzy1yi</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="51">SM1-2019 H</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        </customfields>
    </item>
</channel>
</rss>