<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: New Network Tables -- Issue with time between systems preventing value writes in LabVIEW Code Questions</title>
    <link>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4279899#M55</link>
    <description>&lt;P&gt;According to the network tables spec, time is supposed to be synchronized between server and clients.&amp;nbsp;&lt;A href="https://github.com/wpilibsuite/allwpilib/blob/main/ntcore/doc/networktables4.adoc#timestamps" target="_blank"&gt;https://github.com/wpilibsuite/allwpilib/blob/main/ntcore/doc/networktables4.adoc#timestamps&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 26 Jan 2023 02:45:43 GMT</pubDate>
    <dc:creator>sciencewhiz</dc:creator>
    <dc:date>2023-01-26T02:45:43Z</dc:date>
    <item>
      <title>New Network Tables -- Issue with time between systems preventing value writes</title>
      <link>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4279237#M52</link>
      <description>&lt;P&gt;NT appears to use time to decide which values are newest. Time is different among different computers.&amp;nbsp; This isn't an issue unless multiple computers try to write to the same entry.&amp;nbsp; Only the computer with the largest time value can write.&amp;nbsp; For PC/WPILIB it appears to use microseconds since Jan 1,1970 UTC.&amp;nbsp; Raspberry PI may be similar.&amp;nbsp; For PC/LabVIEW it appears to use microseconds since Jan 1, 1904 wall time (maybe).&amp;nbsp; For the roboRIO/LabVIEW it appears to use FPGA time.&amp;nbsp; These are all quite different.&amp;nbsp; The problem also includes timezone and EST/DST offsets issues..&amp;nbsp; Attached is a zip file demonstrating the issue and providing one possible work around.&amp;nbsp; This work around may not be the best one.&amp;nbsp;&amp;nbsp; See the read_me.txt file in the zip file for additional information.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Jan 2023 17:55:07 GMT</pubDate>
      <guid>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4279237#M52</guid>
      <dc:creator>JimASim</dc:creator>
      <dc:date>2023-01-23T17:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: New Network Tables -- Issue with time between systems preventing value writes</title>
      <link>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4279899#M55</link>
      <description>&lt;P&gt;According to the network tables spec, time is supposed to be synchronized between server and clients.&amp;nbsp;&lt;A href="https://github.com/wpilibsuite/allwpilib/blob/main/ntcore/doc/networktables4.adoc#timestamps" target="_blank"&gt;https://github.com/wpilibsuite/allwpilib/blob/main/ntcore/doc/networktables4.adoc#timestamps&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2023 02:45:43 GMT</pubDate>
      <guid>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4279899#M55</guid>
      <dc:creator>sciencewhiz</dc:creator>
      <dc:date>2023-01-26T02:45:43Z</dc:date>
    </item>
    <item>
      <title>Re: New Network Tables -- Issue with time between systems preventing value writes</title>
      <link>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4279905#M56</link>
      <description>&lt;P&gt;I did get a chance to read (skim) the NT4 specification.&amp;nbsp; Each client is supposed to maintain a time offset so it can send with timestamps that match the time on the NT server (robot).&amp;nbsp; It appears that the base time should be the FPGA time.&amp;nbsp; This makes sense because that is the time that is used most often in dealing with time.&amp;nbsp; The symptoms of the problem remain, but perhaps the source of the issue is the creation, maintenance, and application of this time offset.&amp;nbsp; I'll try and do some more debugging to track the source of the problem, but I don't have access to the documentation, prototypes (incclude files) of the DLL/SO files that are called by the NT4 LV library.&amp;nbsp; Let me know what additional information will help track this down.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2023 05:01:23 GMT</pubDate>
      <guid>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4279905#M56</guid>
      <dc:creator>JimASim</dc:creator>
      <dc:date>2023-01-26T05:01:23Z</dc:date>
    </item>
    <item>
      <title>Re: New Network Tables -- Issue with time between systems preventing value writes</title>
      <link>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4279906#M57</link>
      <description>&lt;P&gt;One additional detail. The clients that help demonstrate this issue are Shuffleboard running on a PC, and PhotonVision (java) running on a Raspberry PI&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2023 05:04:01 GMT</pubDate>
      <guid>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4279906#M57</guid>
      <dc:creator>JimASim</dc:creator>
      <dc:date>2023-01-26T05:04:01Z</dc:date>
    </item>
    <item>
      <title>Re: New Network Tables -- Issue with time between systems preventing value writes</title>
      <link>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4280133#M58</link>
      <description>&lt;P&gt;I did some more testing to confirm the issue.&amp;nbsp; This time with shuffleboard, smart dashboard, and LabVIEW dashboards and a run at startup robot program.&amp;nbsp; Same issue with the time - the clients are sending their local time, not their adjusted to server time.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I looked through the NT VI and didn't see anywhere that the NT server was setting anything other than the FPGA time.&amp;nbsp; (There was one place in NT server where a global variable was set, but I changed that to see if anything changed and it didn't.)&amp;nbsp; I think that may mean that the issue is buried in the DLL/SO files or a DLL routine isn't being called that should be..&amp;nbsp; Sorry, I realize this isn't a lot of help.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Attached are my test programs, screen shots and additional notes.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2023 19:10:29 GMT</pubDate>
      <guid>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4280133#M58</guid>
      <dc:creator>JimASim</dc:creator>
      <dc:date>2023-01-26T19:10:29Z</dc:date>
    </item>
    <item>
      <title>Re: New Network Tables -- Issue with time between systems preventing value writes</title>
      <link>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4282531#M63</link>
      <description>&lt;P&gt;I heard that NI found the root cause of the issue, but I don't know what plans there are for an update.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2023 19:53:08 GMT</pubDate>
      <guid>https://forums.ni.com/t5/LabVIEW-Code-Questions/New-Network-Tables-Issue-with-time-between-systems-preventing/m-p/4282531#M63</guid>
      <dc:creator>sciencewhiz</dc:creator>
      <dc:date>2023-02-07T19:53:08Z</dc:date>
    </item>
  </channel>
</rss>

