<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-03-20T21:53:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-10-08T16:50:06Z</TimeStamp>
    <ReleaseNote>now realtime clock on SLICE devices are synchronized around second boundary</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-02T18:14:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-02T18:13:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-02T18:11:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-01T18:26:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-01T18:14:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with Datapro versions 4.0.1186.51392,4.2.497.51387 and 4.3.430.51397
 Time is set when arming using datapro with Tsr Air on the rollover ( seconds boundary ) 
Usually within +/- 3 ms    as indicated by the datapro logs.

Verified time matches Pc System time  +7 hrs , since time is set to UTC time  which is 7 hrs ahead of local Pc time ( this is expected per Dan   Datapro will always set Tsr Air Time to Utc time )   

test added to testrail here...http://testrailserver/index.php?/cases/view/246945



Test setup was ...


&gt; arming in active streaming and  scheduled modes , no  clock sync  to external clocks.
&gt; verify log shows  SetbaseTime and  time subseconds is close to 0 ms( ~3ms)
  
 

2024-10-01 10:21:25.000 -&gt;  Information - SetBaseSystemTime [00001232], TA0083, local: 192.168.1.20:62239, Remote: 192.168.6.83:8301 System Time: 10/1/2024 5:21:25 PM
 
2024-10-01 10:21:25.005 &lt;-  Information - SetBaseSystemTime [00001232]\[00001232] - (4.9839ms), TA0083

2024-10-01 09:07:59.002 -&gt;  Information - SetBaseSystemTime [00003057], TA0083, local: 192.168.1.20:52109, Remote: 192.168.6.83:8301 System Time: 10/1/2024 4:07:59 PM
 
2024-10-01 09:07:59.007 &lt;-  Information - SetBaseSystemTime [00003057]\[00003057] - (4.9448ms), TA0083




2024-10-01 09:56:18.003 -&gt;  Information - SetBaseSystemTime [00000925], TA0083, local: 192.168.1.20:61208, Remote: 192.168.6.83:8301 System Time: 10/1/2024 4:56:18 PM
 
2024-10-01 09:56:18.008 &lt;-  Information - SetBaseSystemTime [00000925]\[00000925] - (5.0537ms), TA0083


Can use wireshark also to check packet arrival time to das    use dts lua plugin and filter set to ...dts.command_id=="SetBaseSystemTime"   Das fw version  KOF1


  </Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-10-01T18:13:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-01T17:10:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-10-01T15:59:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Time is set when arming Das and command should be sent then and time should be set on the 0 rollover of the clock .

Per Dan - Datapro will  always use Utc time when setting Tsr Air time , so it will be 7 hours ahead of local time but the seconds  will match  on the rollover.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-01T15:59:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.2/4.3@51385
 
All builds of DataPRO (4.x) with a revision &gt;= 51385 should have the change present</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-09-26T20:53:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-09-26T20:47:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-09-26T20:42:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>now DP will wait till we are near a new second to send the setbasesystemtime command.  You'll see this in the log:
 
 
 
2024-09-26 13:38:50.002 -&gt;  Information - SetBaseSystemTime [00000366], TA0164, local: 192.168.1.168:58778, Remote: 192.168.6.64:8301 System Time: 9/26/2024 8:38:50 PM
  
 2024-09-26 13:38:50.006 &lt;-  Information - SetBaseSystemTime [00000366]\[00000366] - (3.9998ms), TA0164
 
in this case it was sent within 2ms of the new second and a response was received within 6 seconds from the device itself, in this example:
 
2024-09-26 13:41:21.000 -&gt;  Information - SetBaseSystemTime [00001009], TA0164, local: 192.168.1.168:58778, Remote: 192.168.6.64:8301 System Time: 9/26/2024 8:41:21 PM
  
 2024-09-26 13:41:21.003 &lt;-  Information - SetBaseSystemTime [00001009]\[00001009] - (3ms), TA0164
 
it was sent perfectly on the second and a response was received within 3 ms of the new second as determined by the PC.
 
unfortunately the ability of the PC to target the second boundary is limited as it's not a realtime OS and time functions are usually ms based granularity, so it won't be able to always hit .00, but it should be close</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-09-26T20:40:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-09-26T18:55:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>requested by f/w, send the SetBaseTime onto 1 secondary boundary - so ms = 0 as close as possible.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2024-09-26T18:55:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>