<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:21:05 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-58] [xcuActor] Gatevalve normal operation is &quot;blocked&quot; by interlock</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-58</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;During normal operation, when we want to close the gatevalve and then open it again, we cannot do it directly but we need to make a power cycle of interlock before.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11408">INSTRM-58</key>
            <summary>[xcuActor] Gatevalve normal operation is &quot;blocked&quot; by interlock</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="10100" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="No further work should be done on this.">Won&apos;t Fix</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="cloomis">cloomis</assignee>
                                    <reporter username="fmadec">fmadec</reporter>
                        <labels>
                            <label>SM1</label>
                    </labels>
                <created>Tue, 27 Dec 2016 01:02:16 +0000</created>
                <updated>Wed, 15 May 2019 16:36:31 +0000</updated>
                            <resolved>Wed, 15 May 2019 16:36:31 +0000</resolved>
                                                                    <component>ics_xcuActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="12182" author="arnaud.lefur" created="Thu, 18 May 2017 16:05:27 +0000"  >&lt;p&gt;It happened again this week, here what we have done:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;close the gatevalve&lt;/li&gt;
	&lt;li&gt;stop the turbo&lt;/li&gt;
	&lt;li&gt;stop the roughing&lt;/li&gt;
	&lt;li&gt;put the cryostat and the roughing back to atmosphere&lt;/li&gt;
	&lt;li&gt;restart the roughing&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Then we wanted to restart the pump down so we needed to open the gatevalve. &lt;br/&gt;
But we couldn&apos;t do it, so I&apos;ve power cycle the interlock and then it worked.&lt;/p&gt;

&lt;p&gt;Is that a normal behaviour ? If the pressure is at atmosphere in the cryostat, we shouldn&apos;t have an interlock right ?&lt;/p&gt;

</comment>
                            <comment id="13740" author="cloomis" created="Thu, 5 Jul 2018 14:03:54 +0000"  >&lt;p&gt;Are you describing a logic or a physical problem? If the cryostat is at atmosphere and the roughing line is pumped down, the gate valve will not and should not open.&lt;/p&gt;</comment>
                            <comment id="14402" author="cloomis" created="Tue, 6 Nov 2018 22:14:28 +0000"  >&lt;p&gt;I belatedly looked at the logs. I had hoped for a user error (sorry!), but we do need to try to duplicate this at JHU: the behavior is wrong. Specifically, the gatevalve was closed before the turbo was stopped. Having the gatevalve open when the turbo spins down through 75% is the only thing (besides pulling the jumper) which should trigger the interlock. &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=shope&quot; class=&quot;user-hover&quot; rel=&quot;shope&quot;&gt;shope&lt;/a&gt; &lt;span class=&quot;error&quot;&gt;&amp;#91;This was on r0, BTW: the thermal cryostat&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;2017-05-16 13:31:37.487Z cmds             20 Actor.py:425 new cmd: gatevalve open
2017-05-16 13:31:37.520Z root             20 gatevalve.py:85 port 0 read: 0xf2
2017-05-16 13:31:37.520Z cmds             20 CommandLink.py:118 &amp;gt; 2 99 i gatevalve=0xf2,closed,closed
2017-05-16 13:31:37.521Z root             20 gatevalve.py:64 port 0 read: 0xf2
2017-05-16 13:31:37.521Z root             20 gatevalve.py:64 setting port 0 to 0x08
2017-05-16 13:31:37.522Z root             20 gatevalve.py:64 port 0 read: 0xfa
2017-05-16 13:31:37.522Z root             20 gatevalve.py:85 port 0 read: 0xfa
2017-05-16 13:31:37.522Z cmds             20 CommandLink.py:118 &amp;gt; 2 99 i gatevalve=0xfa,closed,blocked
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;That said, any new xcuActor (1.7.11+) would have rejected your request: with the roughing pump on and the cryostat at atmosphere the pressure differential across the valve would be too high. &lt;/p&gt;</comment>
                            <comment id="15452" author="cloomis" created="Wed, 15 May 2019 16:36:31 +0000"  >&lt;p&gt;New interlock board will address latching logic.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="12623">INSTRM-406</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|s001rz:c06</customfieldvalue>

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