<?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:47:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified w/ DP 4.0.807, 4.1.170
 
Tested:
 
 
Create 3 separate Stream Output sensors in sensor database with same UDP address (nothing to change)
 
With 3 S6As in a test setup
 
Use the 3 sensors created in sensor database in Channels step including them in the Stream Out channels of the S6A
 
Save
 
Warning message appears:
 
 
Run Test is able to run the test
 
 
 
 
 
In config file changed DisplayDuplicateUDPStreamOutWarning to False
 
 
Follow the same steps. 
 
Though no message appears when saving
 
Verified✔</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-01-17T23:51:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-01-13T22:06:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-01-03T18:22:02Z</TimeStamp>
    <ReleaseNote>Addresses an issue where an error could be displayed when setting a das to streaming</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-03T18:21:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-22T17:26:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>To test:
Create a Test Setup with multiple SLICE6Air or TSR AIR DAS that have stream output channels to the same UDP address.  Verify that a warning is displayed, but that the Test Setup can still be run, and verify that the warning is not displayed when the new config setting, DisplayDuplicateUDPStreamOutWarning, is changed to False.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-20T18:58:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Config file additions: 47974 is 4.0; 47975 is 4.1</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-12-20T18:04:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>47972 is 4.0; 47973 is 4.1
Scope-creep: Add an option to the config file to suppress the warning, which displays when a Test Setup is edited, but not when a Test Setup is run.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-20T17:53:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-12-20T17:05:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Per CPB: . The stream header information can identify individual das. There’s no reason that the PORT has to identify the das because the header already can. 

Per LP: if user does want to have that, we should let them do it. In streaming ch10, I can see the need to separate till we know how to combine stream TMATS. 
But TmNS and IENA streams are fine to be mixed.  Each unit has their open setting to be sorted at the receiver!
 I would take that validation out or treat it as a reminder while user is working preparing the test.
</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-12-20T17:05:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>