<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment>Ticket: SLICE6 AIR | CSV Export – DTS – Zendesk</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-06T17:19:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-24T20:44:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified w/ DP 4.0.722, 4.1.46, 3.3.770
 
Tested using SPS, recorder mode, 3 events, 5 seconds post
 
Ran up to arm and hit start and event using USB Controller while pushing down on weight load
 
Exported CSV unfiltered, filtered, mV, ADC
 
After comparing no two files are alike</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2022-09-19T22:11:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-19T16:19:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-14T22:57:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>3.3/4.0/4.1@47615</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-09-14T16:21:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>from Jerry's testing:
 
 
 
I also did a quick check on all of the other exports and it looks like the following also need the fix: Chapter10, TDAS, TDMS, and XLSX.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-14T15:43:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Subject:
 please review 29631,Export in Run test exports the first event repeatedly    
From:
 Dan McFadden &lt;dan.mcfadden@dtsweb.com&gt;    
Date:
 9/13/2022, 2:08 PM        
To:
 DTSSoftwareDev &lt;DTSSoftwareDev@dtsweb.com&gt;    

 
 
 
Jerry, John, Chris,
 
I've submitted a patch into 3.3 maint for:
 
29631
 Export in Run test exports the first event repeatedly
 
To duplicate this issue, setup a test in multiple event recorder mode, with say 3 events, and Export CSV selected.  Run the test and download all and export all.  I also did download ROI and export ROI, but these were not affected by the issue in my testing.
 
for instance, looking at two ROI csv exports would show believe differences between exports:
 
 
while the CSV export for all would be identical between two event numbers:
 
 
tracking this down in the code there was already a fix in the ROI path that was not executed in the ALL path.  I abstracted this out of the ROI path, and now it applies to both the ROI and ALL paths.
 
Because of the scope of this feature, there may be a lot of testing required, both the ROI and All paths were changed, and while this fixes CSV the same issue may be in other exports as well like XLSX if they used similar logic to start ...
 
after the patch there should be differences in the export all csv files;
 
 
 
 
 Attachments: 
    DTM_29631_ExportAllMultipleEvents.patch 4.4 KB</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-13T23:01:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-13T17:32:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-09T23:31:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-09T23:30:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment>https://dtsweb.zendesk.com/agent/tickets/10696</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-09T16:55:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-09T16:45:39Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>#10696 Data pro multievent mode not exporting files correctly
 
 
 
 
Submitted
 
July 29, 2022 at 09:23
 
   
 
Received via
 
Web Form
 
   
 
Requester
 
Zachery Clarke &lt;zachery.w.clarke@nasa.gov&gt;
 
 
 
 
CCs
 
Chris Balogh &lt;chris.balogh@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
 
Question
 
   
 
Priority
 
Normal
 
   
 
Group
 
Support
 
   
 
Assignee
 
Nathan Brown
 
 
 
 
 
Ticket Source
 
Help Center
 
   
 
Product Family
 
Software::DataPRO
 
   
 
Software Version
 
DataPro 3.1.576
 
   
 
Problem Source
 
Software::Unidentified
 
 
 
 
 
Zachery Clarke July 29, 2022 at 09:23
 
 
 
After using the Multi event mode on Data Pro version 3.1.576 I have noticed a reoccurring but random problem during exporting the data after the test. The run test screen goes as expected but when looking at the data all events exported are the first event. Aka if the test has 4 events then all four will show the same data on the exported file. If you re export the events separately in export data menu then it does as expected. I am not sure why this is happening and it is not a huge problem but thought I would bring it to your attention. I have attached a log file of the test that I last saw this behavior. Unfortunately I can't test any fixes with this setup as it has been shipped to another testing location. 
 
Thank you 
 
Zack 
 
 
 
 
 
Mike Beckage July 29, 2022 at 14:38
 
 
Zack,
  
 I am guessing this issue has been solved in a later version of DataPRO. I have assigned this to Nate for follow-up and copied Chris our software manager to chime in.
  
 Best regards, Mike
 
 
 
 
Chris Balogh August 1, 2022 at 09:16Internal note
 
 
First, 3.1 did not include support for Multi-event recording modes.
  
 Test data attached by Zachery is recorded in 3.3.705 but he's talking about 3.1576. Not sure if this is the reason for the error.
  
 The CSV export folder he has shows different data for event 1 and 2. I'm thinking this could have been after the "If you re export the events separately in export data menu then it does as expected"
  
 Nathan Brown let me know if you need anything?
  
 CC Dan McFadden 
 
 
 
 
Ariel Muckenhirn August 9, 2022 at 14:29Internal note
 
 
Updated Problem Source: Software --&gt; Unidentified
 
 
 
 
Dan McFadden August 29, 2022 at 13:17Internal note
 
 
adding the extra decoration was a feature requested by SQA to make their job easier by making the filenames consistent and uniform across different export, recording mode, and events.  I agree adding the extra decoration can easily make it too long for filenames and cause issues with exports.  We could add a switch in the settings to turn off the adornment (ROI suffix/Event Number)
  
 Nathan Brown  any thoughts?
  
 here's an example of what his test id looks like from the zip;
  
 MSR Aug 2022_Checkout1Set1_2022_07_21 08_25
 
 
 
 
Zachery Clarke September 8, 2022 at 11:48
 
 
 
Any updates to this problem? I am suppose to go back out to Utah at the end of the month and would like to have a fix before I leave. 
 
Thank you 
 
Zack 
 
 
 
 
 
 
 
Dan McFadden September 8, 2022 at 13:39
 
 
Hi Zachery,
  
 I'd like to help out with this issue. I have some confusion at how to reproduce the issue that you might be able to help out with.  Multiple event recording modes wasn't supported in DataPRO until 3.3.  In the zip attached I see v3.3.705, so maybe this was the version the multiple events was recorded in?
  
 looking at the binaries in the dataset attached in 3.3.703, I see similar but different data
  
 
  
 for sure there have been relevant fixes to exports;
      26937 - Export ROI start improperly set in Run Test Export       26732 - Export using browse to file with dataset names files improperly in ISO AND CSV export    but I'd like to give a shot at duplicating the issue first to check if the issue is addressed.  Specifically I think the primary complaint in this ticket is 
   
 
with 3.3.705 run test with multiple events exports event 1 multiple times rather than the actual events
 
  
 Do I have this right?
 
 
 
 
Zachery Clarke September 9, 2022 at 05:52
 
 
 
Dan,
 
 
 
The version that we have been using and having issues with is 3.3.705. The binary files would work correctly it was the .CSV and .XLSX that would only export the first event multiple times. The test data that I sent shows that in the export folder. I can easily recreate the issue by taking a test that has multiple events using the slice nano and exporting the data using the export in the run test mode. Let me know if you can recreate the problem.
 
 
 
Have a good day
 Zack
 
 
 
 
 
Dan McFadden September 9, 2022 at 09:44
 
 
Hi Zachery,
  
 I was able to reproduce with the by running at test with recorder multiple events with a SPS, then downloading and exporting in run test tab with both ROI and ALL downloads.  The ROI data did not duplicate the issue, but the ALL dataset did have identical data:
 ROI:
 
 All:
 
  
 I will create an issue for this and schedule the work
 
 
 
 
 
Support Software by Zendesk</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-09-09T16:45:39Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>