<?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:50:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified w/ DataPRO version 4.0.900, 4.1.247
 
In DataPRO.exe.config file we see the following new setting:
 
      &lt;setting name="OneShotWaitTimeMs" serializeAs="String"&gt;
         &lt;value&gt;3000&lt;/value&gt;
       &lt;/setting&gt;
 
Tested:
 
With a S6DB and S6 connected via a CPY cable to a SPDB, and a breakout board that connects to one of the ports on a S6DB to deliver an event. I created a test and in the check trigger step shorted trigger and verified DataPRO detects shorted trigger
 
Shorted Trigger:
 
 
Triggered:
 
 
Armed S6DB via SPDB</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-03-27T17:57:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-03-27T16:35:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-15T17:50:39Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-03-15T17:50:32Z</TimeStamp>
    <ReleaseNote>Adds a property in config file OneShotWaitTimeMs with default 3000ms (previous default 1700ms)</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-15T17:49:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-03-07T19:25:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-03-07T19:24:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>here's what it looks like when it fails:</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-03T21:55:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-03T21:54:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-03T21:53:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>testing for this is just to make trigger check still funtions normally (detects shorted trigger, detects pressed trigger) in trigger check and that the system can arm with a S6DB and a SLICE PRO DB
 
4.0/4.1@48374
 
it could be difficult to find equipment to test this, you might have to wait for equipment availability.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-03-03T21:53:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>added new setting in DataPRO.exe.config with default 3000 ms;
 
OneShotWaitTimeMs
 
this is used in the places where the one shot wait time was incurred</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-03T21:44:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-03-03T21:43:26Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-03-03T21:42:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Per Loc and Myron, the SLICEPRO DB cap for one shot trigger will last 2.4s, and while observations on S6DB suggested 1.6 would be sufficient for S6DB, it's not clear where the limit for ECMs ever came from or what it should be, but 3s will probably cover everything but a minidb, which may last more than 3 seconds.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-03-03T21:42:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>