<?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>2024-01-02T16:14:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with Dp versions 4.1.341  and 4.2.24

Level triggers now show at t0 in recorded  data  and datapro is setting  Arm attr  attribute (Level Trigger qualification samples) to 5  which is expected ..

</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-07-06T18:43:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-07-06T18:29:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-07-05T20:26:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-05T16:57:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-05T15:40:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-05T15:40:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1@49153
 
I think eric's problem was that he was using a configuraiton already stored on the device and I changed the so that new configurations wouldn't have a 0 for qualification samples.
 
I added code in SLICE6AirBR that forces the channel to 5 even when the configuration on the das is at 0.  I only do this for SLICE6AIRBR, so it's a bit of a unicorn needing this change.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-06-30T20:36:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-06-30T17:30:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>re-activated per EF</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2023-06-30T17:30:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Loc Pham</User>
    <Comment>The issue found in firmware when DSP task is blocked by accessing KSZ registers while initializing for recording/streaming and causes DCT task to drop data because DSP fifo is full.
Problem is fixed by moving all initialization in to DCT to synchronize tasks and DSP filter now only consume data and always ready.

Firmware version N0B6.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-06-29T21:25:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1/4.2@49143
 
It would seem that this would get set to 0 for ALL das with the current implementation, but I've changed it to initialize qualification samples to 5.
 
This should fix the issue according to eric, additionally it should be tested this doesn't break level triggering for any other DAS.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-06-28T22:34:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-06-28T22:32:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Eric Fizer</User>
    <Comment>LevelTriggerQualificationSamples is being set to zero by DataPRO. This is causing the delay when running with S6A-BR.</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-06-28T22:27:39Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Loc Pham</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-26T16:15:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-22T21:56:19Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Tested at multiple sample rates to see delay times.. Results are below..

SPS               delay before T0
8192    ...       ~ 200ms 

4096    ...      ~  620ms

2048    ...      ~  400ms
 
1024    ...      ~  300ms     



128     ...      ~  500ms
 

</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-22T17:31:13Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-22T15:46:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-06-22T15:46:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-06-22T15:44:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>When recording  using level trigger  at 128 SPS  T0 appears   ~ 500ms after the initial level trigger at +200mv  .
The s6 air spec  sheet shows 35.18ms  delay time.


1. I need to revisit this and  run this test at all the sampling rates/ filters as soon as  S6 A bridge HW is available .   




  </Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-06-22T15:44:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>