<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-05T20:33:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-05T20:30:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-05T20:29:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-05T20:27:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-05T20:26:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-05T20:25:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified using datapro  4.1.314.48820 and 4.0.955.48807

Test 1.  Set Remove Leap seconds checkbox  and verified  datapro 
         logs  show  attribute sa 107  is set to 1 after running 
         diagnostics .

         Used Fwtu to check that SA107 is set to 1 and  setting is 
         retained after a reboot of Das.

Test 2. Created test setup in dp and set clock slave input type to 
        PTP to sync to grandmaster Clock  on DTS network added 
        analog 
        channel and a 
        streaming channel.Set Remove Leap seconds checkbox  .Armed 
        unit in Analog Streaming mode time format 2 and rebooted.
        Opened Netview  and opened a line graph and displayed 
        channel from the s6 air , also opened current utc time on  
        webpage  
        https://www.timeanddate.com/worldclock/timezone/utc

 Created event by tapping on S6 air gently  and at same time 
 taking windows snapshot of utc time from webpage ( shift +windows 
 key+s) this is eaiser if you  keep holding  shift+ windows key 
 and then press  s  at the moment you tap the s6 air .

 Then clicked the pause button in netview line graph display 

 Compared the time in the screenshot of the utc time to the event 
 on the line graph  in netview . Time should match when Remove Leap Seconds is set ,   repeat test with  Remove Leap Seconds 
 unchecked and time will not match and the event in Netview  will "lag" the utc time    .
 
See attached last two screenshots....
</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-06-05T17:57:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-06-05T14:48:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-24T20:58:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-24T20:14:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-05-24T03:34:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-05-23T21:00:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-05-23T21:00:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-05-23T17:46:19Z</TimeStamp>
    <ReleaseNote>Adds support in system settings for removing leap seconds from S6A streaming time stamps (requires G0N7 or greater fw)</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1@48782</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-05-22T20:07:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-05-22T20:05:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Subject:
 Please review 31747, Add support for GPS Time leap seconds    
From:
 Dan McFadden &lt;dan.mcfadden@dtsweb.com&gt;    
Date:
 5/19/2023, 4:11 PM        
To:
 DTSSoftwareDev &lt;DTSSoftwareDev@dtsweb.com&gt;    
 
 
 
Jerry, John,
 
I've submitted a patch into both 4.0 MAINT and 4.1 DEVEL for
 
31747
 Add support for GPS Time leap seconds
 
This issue is easy on the surface, just set an attribute based on a setting in datapro!  what could go wrong?
 
In 4.0 the new setting is added in System settings-&gt;Network settings
 
 
this doesn't exist in 4.1, and the setting can be found in Advanced settings instead
 
 
The default value is false, so hitting restore to defaults should reset it to false.
 
in checkhardware if the setting is set to TRUE the protocol version of all units is checked according to loc the version of firmware that supports it should be 42 (protocol version)
 
if it's a streaming test and there's a S6A unit with firmware version &lt;42 then it will display
 
 
it will display this for all das &lt; 42
 
whenever it is configuring a S6A, if the protocol version of the firmware is &gt;= 42 it will set the attribute to 1 or 0.  This can be seen in the log:
 
2023-05-19 14:05:23.102 -&gt;  Attribute - SetSystemAttribute [00000127], S6A0047, local: 192.168.3.28:62302, Remote: 192.168.4.47:8301 Key: RemoveLeapSeconds, DataType: UInt8, Length: 1, Overwrite: True, Value: 0
 
this should never happen, but if the firmware doesn't support that attribute (version &lt; 42 it will do )
 
 
 
2023-05-19 14:05:23.108 &lt;-  Attribute - SetSystemAttribute [00000127]\[00000127] - (6.0978ms), S6A0047 StatusAttributeInvalidNumber
 
note that we don't send the command to &lt; 42 so you shouldn't see this.
 
~ Dan
 
 
 
 Attachments:    DTM_31747_LeapSeconds_40.patch 19.0 KB   DTM_31747_LeapSeconds.patch 18.3 KB</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-05-19T23:26:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-19T23:14:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-19T23:14:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>System attribute #107 repurposed to enable(1)/disable(0) removal of GPS Seconds Time Leap from timestamp.
 
Protocol version 42 will have support for this attribute. All previous version will response with error status STATUS_ATTRIBUTE_INVALID_NUMBER (0x20)
 
Firmware version G0N7. Protocol 42.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-19T17:28:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-05-19T17:11:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>case 30626</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-05-19T17:11:39Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>