<?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-08-24T00:12:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-06-20T01:31:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>Tested with 
s6 + s6 distributor +S6A-BR
SPE+SPS+SPT
S6air + S6A-BR 

Now the SPE and Slice6 distributor doesn't show the check box at the armed step.

However the check trigger steps some time not showing any device. A different ticket opened. 
http://manuscript.dts.local/f/cases/40568/DataPro-Slice6-slice6-Distributor-Trigger-check-didn-t-show-list-of-device</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-06-20T01:31:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-05-09T16:00:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-03-12T20:20:24Z</TimeStamp>
    <ReleaseNote>Removes trigger checkbox in armsystem for distributors and fixes an issue with trigger state getting stuck in "trigger: waiting"</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-12T19:32:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>Note for tester.
The root fail was distributor does not hold the triggered state as DAS.
Distributor only hold the trigger for one sec.

Test needed:
A) Test with different hardware model (slice nano, slice 6 air, slice Pro, TDAS pro)
B) Test start and event trigger issue from computer, issue from interface device, issue from level trigger.
 1) Test with chained devices with and without distributor.
 2) Test with chained distributor.
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-12T17:59:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-12T15:57:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.2/4.3@50461</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-03-12T15:43:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-12T15:32:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>now should show triggered even after the event completes
 
 
 
 
This affects the arm screen for _all_ arm modes and DAS.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-12T15:29:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-12T15:24:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>my note to CPB, EF, LP
 
[8:20 AM] Dan McFadden
 
I'm looking at an issue where there's a complaint that the triggered flag in the UI goes to trigger: waiting after an event completes, looking at the code I note that the QATS goes to triggered: false after the event.  I'll put in code that will only set triggered false in the UI if it's also not armed which might deal with this, but it won't deal with it if you stop monitoring and then complete the event, then start monitoring and attach again.  If the unit is no longer armed we do have the ability to query for a trigger sample # in event attributes.
 
[8:20 AM] Dan McFadden
 
This is just a note in case it ever comes up again.
 
[8:20 AM] Dan McFadden
 
2024-03-11 17:06:03.828 &lt;-  Arm - QueryArmAndTriggerStatus [00001914]\[00001914] - (21.9719ms), SPT00586 Event number: 0, Arm Mode: 1 Armed: True, Started: True, Triggered: True, Faulted: False, Diagnostics: False, FlashClear: False, Arming: False, ArmState: 1 Samplerate: 10000, Current Sample: 411769, Total Samples: 410001, Fault Sample Number: 0 Input Voltage: 12.617V, Backup Voltage: 8.243V, Backup Percentage Remaining: 89% System Temp: 67.76374C, Actual Current Sample: 589436, Max Sample Available: 904569742 Tilt Ch1: 0, Tilt Ch2: 0, Tilt Ch3: 0 Squib Ch1: 0.02354586, Squib Ch2: 0.01184522, Squib Ch3: 0.01562213, Squib Ch4: 0.01588933 Squib P17V: 16.97588, Squib PV5: 4.990226, Squib P3p3V: 3.278639, Squib N5V: -5.076613 PTP Enabled: False, PTP Clk Enable: False, PTP Clk Sync Status: False, ADC Clk Sync Status: False Fault Flags: none Extended Fault Flags: none</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-12T15:23:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>seems to still happen with ECM and a software trigger.</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2024-03-11T23:48:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0@50460
 
4.1/4.2@50459</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-03-11T22:45:54Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-11T22:43:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>it is unclear to me when the original issue was introduced, but I think it was case 33060
 
with that in mind case 33060 probably should be tested after this fix to see if it's re-introduced ...</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-11T21:58:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>this appears to affect more than just SDB ...</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-11T21:50:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>here is the code that sets the triggered status in ArmSystem.GetArmStatus
 
                        Triggered = bTriggered;
 
private void GetArmStatusSuccessCallback(ServiceBase.CallbackData cbd, is where the overall trigger status is determined</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-11T18:48:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Checking with LP he does expect these QueryOMAP functions to report status from down stream devices (in this case I triggered via EOC on a SLICE 1 unit plugged into the SDB), however it's only a pulse mechanism, so if you check the status too slowly you won't see true, additionally if you check it after it's marked triggered it may be reset as well - because of this I will just hide the checkbox for SDB</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-11T17:52:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>as it turns out this firmware version of the SDB says it can monitor triggers status;
 
        public bool GetCanCheckArmStatus()
         {
             return IsCommandSupported(DFConstantsAndEnums.ProtocolLimitedCommands.InitHardwareInputLines);
         }
 
it appears to be connected to the output of these commands;
 
                    var queryOMAPStart = new QueryOMAPnStartMon(this);
                     queryOMAPStart.SyncExecute();
                     if (!queryOMAPStart.Value)
                     {
                         status.IsRecording = true;
                     }
                     var queryOMAPEvent = new QueryOMAPEventMon(this);
                     queryOMAPEvent.SyncExecute();
                     if (!queryOMAPEvent.Value)
                     {
                         status.IsTriggered = true;
                     }</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-11T16:26:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-11T16:05:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>here's the xaml for the trigger box and the binding;
 
&lt;c1:DataGridCheckBoxColumn Header="{root:TranslateExtension ArmSystem_Triggered}" Name="colTriggered" Binding="{Binding Triggered}" SortMemberPath="Triggered" FilterMemberPath="Triggered"/&gt;
 
here's the underlying class being shown in rows;
 
public class ArmSystemDAS : BasePropertyChanged
 
it's triggered is just a simple property;
 
        public bool Triggered
         {
             get =&gt; _triggered;
             set =&gt; SetProperty(ref _triggered, value, "Triggered");
         }
 
suggest we expose a property about whether the DAS cares about trigger or not or gets armed or not and use that to control visibility of the checkbox.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-11T15:53:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>stealing back</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-03-08T01:13:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-03-07T22:12:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-01T19:34:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-28T18:08:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-02-27T23:15:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>Change severity to 1 because this "trigger:waiting" would create too much confusion to users. And need to be fix before release. </Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-22T18:12:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-13T21:46:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-02T20:41:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-02T20:34:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-02-02T20:33:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>DataPro 4.2.339

Devices: Mix of Slice nano, mix hardware and firmwares.

Reproduce rate 100%

issue:
Running the test "Chanined Slice nano" also reproduce with "checking slice nano 069". After arm and trigger the "trigger: waiting" didn't change to "Triggered."

This happens in circular buffer and recorder mode. With or without command status line enable

step:
1 Running the test "Chanined Slice nano" also reproduce with "checking slice nano 069". in circular buffert.
2 run all the way down to Arm 
3 after Arm and run and manual trigger button. 
All device are triggered successful.

expect
the "trigger:waiting" should change to "triggered"

happend

the "trigger:waiting" did not change


If in recorder mode, trigger before start. The check box of triggered would not be checked. Some of the device are triggered. But stilled triggered and ready to download.

</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2024-02-02T20:33:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>