<?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:48:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-15T19:16:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-01-31T18:57:59Z</TimeStamp>
    <ReleaseNote>Adds support for stream output profile 1PPS</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-01-31T18:57:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-01-31T18:57:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>re-opening just to flip release note candidate flag</Comment>
    <StatusString>Reopened</StatusString>
    <TimeStamp>2023-01-31T18:57:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified LTS concerns
 
 
 
4.0.807 &amp;&amp; 4.1.172 (using a 91 db)
 
No 1PPS displayed in Clock Master output clock type drop down menu
 
 
 
 
4.0.807 &amp;&amp; 4.1.172 (using a 92 db)
 
 
All configurations of clock syncs work as previously stated below. 
 
4.0.793 &amp;&amp; 4.1.151 (using a 93 db)
 
 
all clock sync configurations work as expected
 
 
 
Current releaser 4.0 (4.0.729) running a 93 db</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-01-18T22:42:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-01-17T22:25:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>ready for retesting, per JD</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-01-17T22:06:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-17T21:51:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-17T15:15:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>Reopening with all of the LTS concerns added to v4.1
 
Re-run the tests with a remote (central) db:
 
 
this v4.0 &amp; v4.1 against a 92 (this v4.0) db 
 
should act as designed, options should be visible and save &amp; recall normally
 
 
 
this v4.0 &amp; v4.1 against a 93 (v4.1) db 
 
should act as designed, options should be visible and save &amp; recall normally
 
 
 
this v4.0 &amp; v4.1 against a 91 (current release v4.0) db 
 
should no longer see any of the 1PPS out options in Edit Test Setup, otherwise act normally pre-patch
 
 
 
current release v4.0 against a 92 db and current release v4.0 against a 93 db 
 
should act normally for non-1PPS out tests
 
save a test setup to the db with this v4.0 or v4.1 with 1PPS out options chosen then open the test with current release v4.0. chosen options should show up as "None" in current release v4.0 and as chosen in v4.1/this v4.0. if you re-save the test with current release v4.0, should save as "None" and show up that way in v4.1/this v4.0</Comment>
    <StatusString>Reopened</StatusString>
    <TimeStamp>2023-01-13T18:54:04Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified w/ DP v4.1.151
 
 
 
Error message with FW G0N3:
 
 
 
 
With FW G0N5 &amp;&amp; 92 db
 
For the following clock sync profiles in DP:
 
26 = CLOCK_SYNC_PROFILE__SLAVE_E2E_PPS_OUT:        #26 PPS_OUT based on  2
 
 
Set Clock Slave Input Clock type = PTP
 
Clock Slave Output Clock Type = 1PPS
 
Uncheck Clock Master in hardware step (ignores master types)
 
Save test, should be no errors
 
We can also verify all these profiles get set by navigating to FWTU and checking out SA # 106
 
 
 
27 = CLOCK_SYNC_PROFILE__MASTER_E2E_PPS_OUT:        #27 PPS_OUT based on  3
 
 
Set Clock Master Input Clock type = none
 
Clock Master Output Clock Type = PTP + 1PPS
 
Check Clock Master in hardware step (ignores slave types)
 
Run Test and verify no error message. Can verify 1PPS on oscilloscope ✔
 
We can also verify all these profiles get set by navigating to FWTU and checking out SA # 106
 
 
 
28 = CLOCK_SYNC_PROFILE__MASTER_E2E_IRIG_PPS_OUT:  #28 PPS_OUT based on  5
 
 
Have ORCA plugged into test device
 
Set Clock Master Input Clock type = IRIG B
 
Clock Master Output Clock Type =  PTP + 1PPS
 
Check Clock Master in hardware step (ignores slave types)
 
Save test and verify no error message. Can verify 1PPS on oscilloscope
 
 
 
 
32 = CLOCK_SYNC_PROFILE__IRIG_PPS_OUT:              #32 PPS_OUT based on 21
 
 
Have ORCA plugged into test device
 
Set Clock Master Input Clock type = IRIG B
 
Clock Master Output Clock Type = 1PPS
 
Check Clock Master in hardware step (ignores slave types)
 
Save test and verify no error message. Can verify 1PPS on oscilloscope</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-01-12T23:05:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-01-11T22:14:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>v4.0 w/LTS committed in r48024. Now remaining LTS issues to be forward-ported to v4.1 and the issue completely resolved and able to be tested.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-07T01:59:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-01-03T18:31:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-01-03T18:25:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>Basic changes:
 
 
Add new 1PPS out Clock Sync Profiles to enum
 
Add 1PPS Profile validation to SLICE6AIR.cs/IsClockSyncProfileSupported
 
Add necessary UI to EditTestSetup
 
Add all possible profiles that could be created via UI, add validation to IsClockSyncProfileSupported
 
 
v4.1 LTS changes (so far):
 
 
If using a 1PPS out, check if centralized db and version &lt; 92. If so, throw error and don't allow save
 
If using a centralized db and version &lt; 92, don't allow 1PPS out options to show in UI
 
 
Tests (enable clock sources in Settings before starting any of them):
 
1PPS out
 
 
Using a local db (or a remote db version &gt;= 92), create a test with a SLICE6AIR with a firmware of G0N3 or below. Select it in hardware, configure a channel. Go back to Info and set one of the new 1PPS Out profiles created in issue 29821. Save the test. You should be given an error that the profile is NOT supported. You may need to go back and forth to the Hardware tab to set the unit as Clock Master for the profiles that require it and unset it for the profile that doesn't.
 
Update the SLICE6AIR to G0N4 or above. Repeat #1. You should not receive an error. You should be able to run your test normally and see output on the 1PPS pin
 
With any firmware version, selecting an unimplemented profile (None in - 1PPS out (M or S), GPS in - 1PPS out, GPS in - PTP + 1PPS out, GPS + 1PPS in - 1PPS out, GPS + 1PPS in - PTP + 1PPS out, IRIG + 1PPS in - 1PPS out, IRIG + 1PPS in - PTP + 1PPS out, 1PPS in - 1PPS out, 1PPS in - PTP + 1PPS out) should result in an unsupported profile error.
 
 
LTS / v4.0 issues are still being worked out and will be added at a later date following verification that the 1PPS Out functionality works in v4.1.
 
Added to v4.1 with r47966</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-12-16T20:56:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-13T20:11:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-29T16:13:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-15T20:51:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-11-11T23:51:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-10T16:43:54Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-11-10T16:43:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-11-01T20:20:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-01T20:16:19Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T23:00:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T22:54:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T22:09:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T22:09:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T22:09:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T21:59:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>related
 
https://dtsweb.zendesk.com/agent/tickets/10643</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T21:58:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T21:28:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T21:05:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-10-28T21:05:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>see case 29821
 
should be added into 4.1, and then a new issue created to port to 4.0 (and blocked till 4.1 changes validated)
 
Add profiles to available profiles
 
At the least it should validate that the profiles are valid on das in validating a test setup, at best the list of available profiles could be limited to what das in a test support.
 
G0N4 with Protocol version 39. (S6A)
 
will be supported on S6A-Falcon-Id, not known what protocol version for S6A-Falcon-Id, but presumably by first shipped device?
 
will need to be added to system settings, 
 
 
I don't know that we expose it anywhere else?
 
will need to be able to be serialized/deserialized from xml where applicable.
 
_SHOULD_ be LTS friendly which is a little more difficult, because that suggests old clients should be able to read from the database without breaking from the new entries, which may mean writing additional ways of getting the new entries? 
 
also should verify it appears in a readable manner in other places where it shows up, like clock sync table in armchecklist</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-10-28T21:05:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>