<?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:58:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-05-23T16:25:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Edward Poon</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-16T18:30:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Edward Poon</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-16T18:01:13Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>no changes on software side, changes are on firmware side for issue, nothing to test on software side for this issue.</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-05-15T23:08:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-15T23:08:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>undid changes, not needed with new firmware for SPDB/PPRO</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-05-15T23:07:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1@48766</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-05-15T21:01:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>I can duplicate this when I add a PPro into the configuration, on the second run through the SPDB reports "Incoming status line dropped";
 
the power pro was armed here: 2023-05-15 09:37:09.053 &lt;-  Arm - Arm [00003369]\[00003369] - (88.2348ms), PPR0003
 
SPDB reports incoming status line dropped
 
2023-05-15 09:37:18.500 &lt;-  Arm - QueryArmAndTriggerStatus [00003379]\[00003379] - (58.0406ms), S6DB00002 Event number: 0, Arm Mode: 1 Armed: True, Started: False, Triggered: False, Faulted: True, Diagnostics: False, FlashClear: False, Arming: False, ArmState: 1 Samplerate: 10000, Current Sample: 1000, Total Samples: 12000, Fault Sample Number: 0 Input Voltage: 0.000V, Backup Voltage: 0.000V, Backup Percentage Remaining: 0% System Temp: 42.375C, Actual Current Sample: 1000, Max Sample Available: 12000 Tilt Ch1: 0, Tilt Ch2: 0, Tilt Ch3: 0 Squib Ch1: 0, Squib Ch2: 0, Squib Ch3: 0, Squib Ch4: 0 Squib P17V: 0, Squib PV5: 0, Squib P3p3V: 0, Squib N5V: 0 PTP Enabled: False, PTP Clk Enable: False, PTP Clk Sync Status: False, ADC Clk Sync Status: False Fault Flags: IncomingStatusLineDropped Extended Fault Flags: 1
 
the power pro reports armed,  not started, not triggered in QATS:
 
2023-05-15 09:37:18.455 &lt;-  Arm - QueryArmAndTriggerStatus [00003380]\[00003380] - (13.0407ms), PPR0003 Event number: 0, Arm Mode: 1 Armed: True, Started: False, Triggered: False, Faulted: False, Diagnostics: False, FlashClear: False, Arming: False, ArmState: 1 Samplerate: 10000, Current Sample: 1000, Total Samples: 12000, Fault Sample Number: 0 Input Voltage: 20.762V, Backup Voltage: 12.574V, Backup Percentage Remaining: 0% System Temp: 26.0625C, Actual Current Sample: 1000, Max Sample Available: 12000 Tilt Ch1: 0, Tilt Ch2: 0, Tilt Ch3: 0 Squib Ch1: 0, Squib Ch2: 0, Squib Ch3: 0, Squib Ch4: 0 Squib P17V: 0, Squib PV5: 0, Squib P3p3V: 0, Squib N5V: 0 PTP Enabled: False, PTP Clk Enable: False, PTP Clk Sync Status: False, ADC Clk Sync Status: False Fault Flags: none Extended Fault Flags: none
 
this happens regardless of whether the TDM is hooked up or not.
 
this happens with the latest SQA approved firmware for PPRO (H0D3).
 
I'll work with edward to see if we can identify why this happens.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-15T21:00:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>could not duplicate this with the system below (SPDB/ECM+SPS/TDM) however I was able to duplicate by adding in a PowerPRO
 
by explicitly calling DisableFaultChecking (for spdb and powerpro) I'm able to avoid seeing the issue expressed.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-15T20:54:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-05-15T20:51:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-15T14:16:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-03T14:03:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-05-03T14:02:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Chad Ivan reports that when using a SLICE PRO Distributor -&gt; ECM-&gt;SPS with a TDM attached and using a slow trigger check the first trigger check works fine but any repeated ones fail.  He suspects software is not resetting something.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-05-03T14:02:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>