<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:22:03 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-149] Choose between NTP and PTP</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-149</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;These days, Linux includes decent PTP support, and PTP can be used in place of NTP. Do we want to? The underlying question is whether we will ever need instrument-wide timing better than a few milliseconds.&lt;/p&gt;

&lt;p&gt;The one obvious problem which could benefit from precise relative instrument-wide timing is matching fiber motion or LED strobes to MCS rows. If there is any chance we will want to synchronize those I believe we should use PTP. If not, NTP is fine.&lt;/p&gt;

&lt;p&gt;I don&apos;t think there is a significant difference in management effort these days. The head server can use the observatory NTP feed for its absolute time, regardless of the chosen protocol.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11693">INSTRM-149</key>
            <summary>Choose between NTP and PTP</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="-1">Unassigned</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                    </labels>
                <created>Wed, 12 Jul 2017 16:33:00 +0000</created>
                <updated>Fri, 17 Mar 2023 21:21:08 +0000</updated>
                            <resolved>Fri, 17 Mar 2023 21:21:08 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                <comments>
                            <comment id="12389" author="atsushi.shimono" created="Wed, 12 Jul 2017 16:49:52 +0000"  >&lt;p&gt;Subaru provides NTP over their summit network, under their stratum 1 from GPS.&lt;br/&gt;
I am not sure they can proveide PTP to us, but it is definitely important for us to have (some) precise timestamp, even if it is not synced to precise time, so let the project office to discuss/propose something to subaru (next week - week of 17th 07/2017).&lt;/p&gt;</comment>
                            <comment id="12431" author="atsushi.shimono" created="Wed, 26 Jul 2017 10:22:06 +0000"  >&lt;p&gt;We need to get time from Subaru via NTP from stratum 2 NTP server at summit. I&apos;d vote to have both NTP and PTP if we really want to have PTP in PFS ICS, since some hardware, including UPS, need NTP but not support PTP.&lt;/p&gt;

&lt;p&gt;One concern for using PTP for timing of LED strobes is how we can use. Two light sources (FFIS in PFI, BIA in SpS) is controlling LED driver by GPIO of ethernet connected Arduino. Commanding to Arduino are done by remote computer (actor), CB2F for FFIS, SpS/5th rack for BIA, and there are some uncertain latency from commanding actor and hardware. Also it would be quite difficult to have PTP like timing software in Arduino.&lt;/p&gt;</comment>
                            <comment id="12434" author="rhl" created="Wed, 26 Jul 2017 13:43:56 +0000"  >&lt;p&gt;I don&apos;t care about UPS time, but for subsystems that we care about I really don&apos;t think we want two time protocols to get out of sync (although we could add a component to check for that, I suppose, and warn)&lt;/p&gt;

&lt;p&gt;It appears that arduinos do support PTP (but Shimono-san and Craig are the experts); &lt;a href=&quot;https://forum.arduino.cc/index.php?topic=348881.0&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://forum.arduino.cc/index.php?topic=348881.0&lt;/a&gt; says that&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
$ opkg list | grep ptpd

returns:

ptpd - 2.1.0-2 - The PTP daemon (PTPd) &lt;span class=&quot;code-keyword&quot;&gt;implements&lt;/span&gt; version 2 of the Precision Time Protocol (PTP) as defined by the IEEE 1588-2008 standard. PTP was developed to provide very precise time coordination of LAN connected computers.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="12435" author="atsushi.shimono" created="Wed, 26 Jul 2017 13:57:12 +0000"  >&lt;p&gt;I don&apos;t think Arduino Ethernet can run OpenWrt... Yun could be, which has processor and microcontroller.&lt;/p&gt;</comment>
                            <comment id="32445" author="arnaud.lefur" created="Fri, 17 Mar 2023 21:21:08 +0000"  >&lt;p&gt;the answer is NTP&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="12059">INSTRM-291</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|ii02g7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>