<?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>Closed</StatusString>
    <TimeStamp>2024-01-16T21:35:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-01-16T21:35:13Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Reopened</StatusString>
    <TimeStamp>2024-01-16T21:35:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-01-16T21:08:41Z</TimeStamp>
    <ReleaseNote>Now DAS boot count are queried at arm and download time</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-01-16T21:08:31Z</TimeStamp>
    <ReleaseNote>now DAS boot count are queried at arm and download time</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with DataPRO v4.0.1119, 4.2.234
 
Tested with 
 
 
Created a simple test with ECM + SPS
 
Ran test, armed, triggered, and downloaded
 
Ran with new version of DataPRO and compared to pre patch. 
 
 
ArmingService.PreparedArmNow:
 
 
DownloadService</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-01-12T18:13:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-12T00:38:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.2@50033
 
there are now additional boot count queries after you arm and before you download on SLICE devices (not including ECM and distributors, power pros, etc)</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-01-08T22:47:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>arming goes through this process:
 
 
here's where we can put the query into;
 
                                            (data.Unit as IArmActions)?.PreparedArmNow(MyCallback,
                                                                               data,
                                                                               eventGuid, armNowTimeout,
                                                                               checkoutMode,
                                                                               maxNumberEvents, sysMode);
 
 
 
we could put the download one here:
 
2024-01-05 14:50:32.236 Entering DownloadService.QueryDownload on thread 1 with units: (SL60130, SL60129) Called from: Download.GetEventInfo Line: 4402
 
SLICEHandling has this functionality present;
 
        protected void DummyRetreiveDasBootCount(DTS.Common.Interface.DASFactory.ICommunication dev)
         {
             try
             {
                 var query = new QuerySystemAttribute(dev) {Key = AttributeTypes.SystemAttributes.DASBootCount};
                 query.SyncExecute();
             }
 
            catch
             {
                 // we don't care about any errors, we're just trying to get the command into the log file!
             }
         }</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-05T22:56:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-05T22:45:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-05T16:06:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>sure, currently I would expect it to query the information when you first connect to it.
 
for the post-event I suggest we query it when we query to see if the das has an event/eventcount.
 
 
 
On 1/5/2024 5:16 AM, Nathan Brown wrote:
 
 
 
Hi guys,
 
 
 
I see this BootCount attribute on a s6db3:
 
        &lt;Attribute&gt;
 
          &lt;DASType&gt;SLICE6DB3&lt;/DASType&gt;
 
          &lt;Type&gt;System&lt;/Type&gt;
 
          &lt;Id&gt;13&lt;/Id&gt;
 
          &lt;Name&gt;BootCount&lt;/Name&gt;
 
          &lt;Setting&gt;266&lt;/Setting&gt;
 
        &lt;/Attribute&gt;
 
 
 
Can we query and log boot count of any SLICE modules in DataPRO when we arm, and when we start the first post-test process?
 
 
 
This would be super helpful when troubleshooting issues during a test.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2024-01-05T16:06:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>