<?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>2023-05-24T20:45:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-24T20:45:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-21T16:54:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-21T16:53:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with DP 4.0.725.47650 and DP 4.1.49.47650  And using  A TSR Air with K0D2 fw .</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2022-09-21T16:52:54Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-21T14:39:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-20T22:58:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>Per Loc &amp; Chris, continued TSRAIR dev from when the initial discussion happened pushed out the running counter of ProtocolVersion past the previously agreed upon Phase Two start. For now, the code is there to support the additional phases, but commented out in both v4.0 maint and v4.1 dev until we have definite FW implementations. Once that implementation happens - scheduled post v4.0 ECO and during v4.1 dev - the code can be uncommented and Protocol Version magic numbers assigned at that time.
 
Changes:
 
 
Comment out all IRIG, GPS, and 1PPS protocol version checks for TSRAIR and resolve false. Leave infrastructure commented out for turning back on once implemented in FW
 
 
Testing:
 
 
Testing can proceed as detailed.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-09-20T22:04:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-20T21:51:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>blocked for f/w</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-20T21:48:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-20T21:48:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-19T22:57:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Tested this with dp 4.0.722.47639 and DP 4.1.43.47631 and was able to save test setup with Clock Master checkbox enabled and  Clock Sync &gt; Clock master input type set to any choice (GPS, iRIG , ETC) And got no pop up error when saving test setup with TSR 0032  K0D2 FW. 
 
 
 
Was able to get a pop up message when creating a TSR Air manually in Data Recorders tab and running the same test. 
 
Reopened after Confirming with John .</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2022-09-19T22:56:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-19T16:19:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-15T17:01:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>When the TSRAIR is chosen as a Clock Master, the only valid input should be None - you should get a save error if GPS, IRIG, etc. are chosen or "Manage clocks outside of DataPRO" is selected.
 
When the TSRAIR is not a Clock Master, None or PTP should be valid and choosing "Manage clocks outside..." should result in an error.
 
 
The "chosen/not chosen as a Clock Master" happens in the Hardware navstep of Edit Test Setup:</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-08-29T17:07:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment>john to include testing notes and reach out to sqa (jaime)</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-08-25T17:35:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>FogBugz</User>
    <Comment>From: "John Dowling" &lt;john.dowling@dtsweb.com&gt;
Date: Fri, 5 Aug 2022 11:07:09 -0700
To: "FogBugz" &lt;fogbugz@dtsweb.com&gt;
Cc: 
Subject: Automatic reply: Manuscript (Case 29358) DataPRO - Extend time sync features to TSRAIR (Phase 1)

I will be out of the office on PTO on Thurdsay 8/4 and Friday 8/5. I will return to work on Monday 8/8/2022.

 

Have a good weekend,

 

John</Comment>
    <StatusString>Incoming Email</StatusString>
    <TimeStamp>2022-08-06T12:28:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Reactivating
 
In DP 4.0.682 with 
 
 
I created a Test Setup in Clock sync I was able to save with Clock Master Input Clock Type set to GPS and got no error</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2022-08-05T18:07:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-08-05T15:46:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-08-03T15:18:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-08-03T15:14:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-08-02T15:15:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>Changes:
 
 
Implement IsClockSyncProfileSupported plumbing following pattern of IsRecordingModeSupported
 
Add TSRAIR to types that can be checked for sync
 
Add validation of ClockSyncProfile support to TestTemplate, EditTestSetupInfoControl
 
Add validation failure warnings
 
 
Testing:
 
 
TSRAIR now supports Clock Sync in latest firmware, so update device in FWTU and turn on that system setting in DataPRO and attempt to configure Clock Sync in Edit Test Setup and save the test setup. 
 
When the TSRAIR is chosen as a Clock Master, the only valid input should be None - you should get a save error if GPS, IRIG, etc. are chosen or "Manage clocks outside of DataPRO" is selected.
 
When the TSRAIR is not a Clock Master, None or PTP should be valid and choosing "Manage clocks outside..." should result in an error.
 
 
 
When running a test and using sync settings that are different than currently configured on the TSRAIR, you should get the warning message and a reboot message in the Hardware Navstep as you do with SLICE6AIR
 
When running a test you should see Clock Sync settings displayed and tested in the Arm Checklist navstep as you do with SLICE6AIR if Clock Sync settings are chosen for Arm Checklist in Edit Test Setup
 
Timestamp, Sync, etc. data should be reflected in the .dts file as it does for SLICE6 family</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-07-27T20:00:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-07-21T21:25:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-07-20T21:44:04Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-07-18T17:54:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-07-18T17:48:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>Currently only SLICE6, SLICE6AIR has features in DataPRO for time sync. Extend these features to TSRAIR:
 
 
TSRAIR inherits IClockSyncActions
 
TSRAIR checks its clock sync settings and adjusts accordingly in CheckHardware
 
TSRAIR checks its clock sync and displays results during Diagnostics
 
TSRAIR checks its clock sync and displays results during ArmCheckList
 
Allow TSRAIR to be selected as Clock Master in Edit Test Setup -&gt; Hardware
 
Current Phase 1 firmware can only send PTP when Clock Master, not sync to GPS, IRIG, 1PPS. Validate TSRAIR to only "None" for Clock Master Input, following pattern set with IsRecordingModeSupported / IsStreamingProfileSupported
 
TSRAIR can receive PTP, similar to SLICE6 family
 
Time, Sync, etc. data should be reflected in the .dts file as it does for SLICE6 family
 
 
Firmware tracking feature at 28139.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-07-18T17:48:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>