<?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:56:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-05T20:06:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with datapro 3.1.703 ,3.3.793, 4.0.903,4.1.252   . Tested in automatic mode with attached test setup SPS And SPT HW .  Datapro version before patch gets "stuck" at post test diagnostics step , and  datapro version post patch is able proceed to download step and successfully download data from the Hw.</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-04-03T18:24:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-03-31T18:54:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>3.1 is 48435; 3.3 is 48436; 4.0 is 48437; 4.1 is 48438</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-03-24T20:01:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-20T15:56:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-20T15:55:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>To test:

I've attached a Test Setup that you can import.  I think the key is that more than one Group is needed, a TOM is needed, and all of the TOM channels need to be in the same Group.

Run the test in Automatic mode and without the patch, it will hang after Post-test diagnostics.  With the patch, it will go on to Download and then View the data before stopping.
 
There is a known bug (29397) in 4.1 (at least, but not 3.1) that causes Automatic mode to stop after the "Check sensor ID" step.  The workaround is to just click the "Resume (Automatic mode)" button when this happens.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-20T15:55:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-03-20T14:58:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-03-16T15:26:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>this got resurrected by support with _slightly_ more information</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-03-15T21:00:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-15T17:13:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-13T20:55:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-13T20:55:13Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>re-opened with more information;
 
ZF using Automatic Mode
  
 Tyler can't remember if we ever tested using manual step-through
  
 Tyler will send us db MDF/LDF
       
Tyler Kohler
 
Mar 6, 2023, 13:14 EST
 
 
Database MDF and LDF files to help software group replicate issue as discussed in weekly meeting 3/6/23.
 
 
 
 
Attachment(s)
 DataPro_US.zip</Comment>
    <StatusString>Reopened</StatusString>
    <TimeStamp>2023-03-06T21:07:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>closed per nate's resolution.</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-03-03T16:42:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Nathan Brown (DTS)
 
Mar 3, 2023, 10:16 CST
 
Notes from Chad--found a loose power socket (and missing bolt on back) on SPE00600, causing system to power down after recording.
  
 I'm dropping off the ECM at Novi now.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-03T16:42:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-02-28T21:29:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-02-22T16:41:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>don't know the total time elapsed as I took the ticket over late into the issue's cycle.  Assuming 16h</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-02-22T00:24:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>there's a couple of things that could be relevant.  Maybe the order of das, maybe whether automatic mode is used, etc.  Attaching the db might help duplicate?  I did notice there's a process that starts as soon as you enter the post test diagnostics step.  I waited for it to complete before I pressed run, but maybe it's possible to press run right away?
 
 
 
I'll turn this over to SQA with the additional notes on duplicating to see if they have better luck duplicating.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-02-22T00:23:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>could not reproduce using the xxx test (which did not have post test diagnostics selected, but I added it) in the latest 3.1 diagnostics.
 
 
 
 
there may be other steps that are important to duplicating, need steps to duplicate.  Other things that might be relevant, path to arming, maybe even order of das in the rack.  In my case I'm using SPS and then SPT, shouldn't matter but anything that we can do to duplicate.
 
Other things that might be relevant, was automatic mode used?  I noticed there was a process that starts when you hit the post test diagnostics step.  I waited for it to complete before I hit run, do they hit it right away maybe?  Looking for steps to duplicate.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-02-22T00:18:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>no luck duplicating with SPT with squibs and digital out defined with the latest 3.1</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-02-21T22:19:04Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-02-21T21:57:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-02-15T22:45:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>moving to SW 4.1.13, officially starting tomorrow, unofficially starting today</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-02-14T18:12:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>original title issue in post test diagnostics with squibs and it doesn't allow going to download</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-02-09T16:50:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-31T18:20:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>might want to ping on zendesk ticket</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-17T21:58:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-17T21:51:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-03T19:10:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-12-23T16:06:54Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-12-20T23:44:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-12-15T16:49:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-13T20:11:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-13T16:51:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-12-13T16:50:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-13T15:49:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-29T16:44:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-29T16:37:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-29T16:29:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-11-21T17:21:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>#11129 SLICE PRO: Data Download Issues
 
 
 
 
Submitted
 
November 16, 2022 at 07:11
 
   
 
Received via
 
Web Form
 
   
 
Requester
 
Rob Seymour &lt;robert.seymour@zf.com&gt;
 
 
 
 
CCs
 
Ariel Muckenhirn &lt;ariel.muckenhirn@dtsweb.com&gt;, Chad J Ivan &lt;chad.ivan@dtsweb.com&gt;, Dan McFadden &lt;dan.mcfadden@dtsweb.com&gt;, Mike Beckage &lt;mike.beckage@dtsweb.com&gt;, Nathan Brown &lt;nathan.brown@dtsweb.com&gt;
 
 
 
 
Status
 
Open
 
   
 
Type
 
Problem
 
   
 
Priority
 
Normal
 
   
 
Group
 
DataPRO Support
 
   
 
Assignee
 
Dan McFadden
 
 
 
 
 
Ticket Source
 
Help Center
 
   
 
Product Family
 
Software::DataPRO
 
   
 
Software Version
 
3.1.678
 
   
 
Problem Source
 
Software::Unidentified
 
   
 
Current Department [Optional]
 
Tech Support
 
 
 
 
 
Rob Seymour November 16, 2022 at 07:11
 
 
 
Two test setups exactly the same except one has squibs and one does not.  The setup without the squibs run through the test sequence with no issues but the setup with squibs added to the test setup the sequence locks up at the data download section looking for user input put won't give you any options to download the data.  you have to restart datapro and manually download the data
 
 
 
 
 
Ariel Muckenhirn November 16, 2022 at 07:32
 
 
Rob,
  
 I'm taking a look at these now.  Will get back to you shortly with some feedback.
  
 Ariel
 
 
 
 
Ariel Muckenhirn November 16, 2022 at 08:24
 
 
Rob,
  
 I need to see some info from the full test setups to be able to diagnose this issue better.  Can you zip up the whole test folders for these and attach them here?
  
 Ariel
 
 
 
 
Rob Seymour November 16, 2022 at 10:33
 
 
 
ZF Confidential
 
 
 
Here you go
 
This Message from Ariel Muckenhirn (DTS) &lt;support@dtsweb.zendesk.com&gt; has a different reply-to address: support+id11129@dtsweb.zendesk.com - proceed with caution!
 
-------------------------------
 
 
 
 
 
Ariel Muckenhirn November 17, 2022 at 11:25Internal note
 
 
Quick notes: 
  
 Test 10 = With Squibs  
 
  
 Completed Services:
 
   
Test 9 = No Squibs
 
  
 Completed Services:
 
 
 
 
 
Ariel Muckenhirn November 17, 2022 at 11:41Internal note
 
 
Notes from Test 10 (No Squibs):
  
 First attempt to download, following the Arming Service:
  
 
  
 Warning at line #589 indicates that the number of samples doesn't match.
 Happens at 06:11:19.
   
Happens again at line #844:
 
 This is at 06:22:26.
   
Both warnings show the same incorrect number of samples (6,473,500 vs 6,513,550).  Difference is 40,050 samples.  
 Sample rate for test = 20,000 --&gt; ~2 seconds.
 
 
 
 
Ariel Muckenhirn November 17, 2022 at 11:51Internal note
 
 
SPS01217 has 6473500 samples:
 
  
 SPT00610 has 6153550 samples:
 
  
 
 
 
 
Ariel Muckenhirn November 17, 2022 at 12:08Internal note
 
 
Test 9:
 After the first set of DownloadService calls are made:
 
 This warning is made:
 
  
 Next set of DownloadService calls begin:
 
  
 It seems that the SPS values are matched during the two calls, as there are no further warnings.
  
 
 
 
 
Ariel Muckenhirn November 18, 2022 at 08:07Internal note
 
 
 
 Assigning to Dan McFadden 
  
 I need some help with looking into this issue further.  Nathan Brown and I went through the logs as best we could here, but we've run into a wall with figuring out what is going on between these two tests.  There was a 45 second 'lag' in Test 10 that resulted in the customer deciding that the software was 'stuck' and pressing the cancel button, closing DataPRO, and restarting to download the data.  The only difference between these test setups is that Test 9 had Squibs and Test 10 did not.  However, looking at the logs, there is an unexplained 45 second 'hang-up' during Test 10's ConfigurationService.ApplyLevelTriggers call that didn't happen in Test 9.  See description below.
   
So, this is the progression for Test 10:  
 
  
 This is where the 45-second hang-up happened and the user chose to press the Cancel Button:
 
  
  
 There is no information in the logs to tell us what might have been happening here.
  
 There is an error/warning earlier in the log, but this error also appears in Test 9 and does not seem to have affected to automatic download process in that run:
  
In Test 9, This is the progression that we can see:
 
 
 
 
 There is no hang-up in this same functional period during this test run:
 
 
 
 
 
Ariel Muckenhirn November 18, 2022 at 08:10
 
 
Rob,
  
 We're assigning this to our Software people to take a deeper look into why the software stalled during your Test 10 setup.  Do you happen to have logs available from when you restarted DataPRO and downloaded Test 10's data?  We'll keep you in the loop with what we find regarding the issue you reported.
  
 Ariel Muckenhirn
 
 
 
 
Dan McFadden November 18, 2022 at 08:53Internal note
 
 
always happy to help, but I'm straight locked up in meetings for some time and am already fully allocated as well.  I'll add it to my list and get to it as soon as I can.
 
 
 
 
 
Support Software by Zendesk</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-11-21T17:21:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>