<?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:48:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-02-07T19:57:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Retested  with Files Dan provided , placing them in the Datapro.exe directories of each installation .
 
Exported  CSV calculated channel data does not match kogawa-san xlsx.  Data
 
Realtime seems to work correctly as per what testrail test calls for which was original issue case was opened for  though . 
 
Tested with dp 3.3 3.3.789.48047, 4.0.793.48044, and 4.1
 
 
 
I tested as follows..
 
Import the attached test setup , swap out hw , run test arm and collect data while injecting 87mv on 3 channels and download roi  -.05   to  .190 
 
place the 3 txt files Dan attached in the datapro.exe directory ...
 
Export roi unfiltered to Csv , compare cvs with  original attached data  , calculated channels are very  close to original as they should be  . , hw channels are very close as  they should be</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-02-07T19:56:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>SO if I dont have a folder structure like what is shown (No Binary folder) Where would I put the Txt files?</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-02-07T00:12:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-02-06T23:45:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-01-31T19:17:24Z</TimeStamp>
    <ReleaseNote>Addresses an issue where 3D IR-TRACC data did not match expectations on export</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-01-31T19:16:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>still works in 4.0, the key here is that the .txt files needs to be in the binary directory, not the test data directory, so for example - here it is next to DataPRO.exe</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-01-24T21:41:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-17T17:19:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>sounds like the testing method was probably inaccurate, we can check it out again though.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-17T16:28:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-16T23:10:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-16T23:06:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Exported  CSV calculated channel data does not match kogawa-san xlsx.  Data
 
Realtime seems to work correctly as per what testrail test calls for which was original issue case was opened for  though . 
 
Tested with dp 3.3 3.3.789.48047, 4.0.793.48044, and 4.1
 

  
 
 The issue is Exported csv Calculated channels do not match however 
 
here are the 4 columns from kogawa-san's xlsx
 
 
They dont match the exported csv calculated channels .
 
 
 
 
 
From Dp 3.3 3.3.789.48047
 
 
And with DP 4.0.793.48044
 
 
 
 
And with dp 4.1.149
 
 
 
 
 
 
 
 
 
 
I tested as follows..
 
Import the attached test setup , swap out hw , run test arm and collect data while injecting 87mv on 3 channels and download roi  -.05   to  .190 
 
place the 3 txt files Dan attached in the binary folder for the data just collected 
 
Export roi unfiltered to Csv , compare cvs with  original attached data  , calculated channels differ quite a bit. , hw channels are very close as  they should be
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Realtime data and recorded data shows correct response per the original testrail test on hw channels. 
 
 
realtime  4.0.793 potY channel ..</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2023-01-16T23:04:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-11-03T23:19:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-18T17:46:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0@47704</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-10-04T23:08:26Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Tracy Smail</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-04T17:20:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-10-04T15:20:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-04T15:09:26Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-04T15:06:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-04T14:55:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-28T14:57:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>supplemental patch</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-27T17:29:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-27T17:28:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>3.3/4.1@47678  (on hold for 4.0)</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-27T15:21:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>updated to change the serial number of output calculated channels too</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-27T15:09:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-26T22:00:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Subject:
 Please review 29654,dp 4.0 476 3D IRTRACC DATA does not match expected data when injecting dc input per test steps    
From:
 Dan McFadden &lt;dan.mcfadden@dtsweb.com&gt;    
Date:
 9/26/2022, 2:31 PM        
To:
 DTSSoftwareDev &lt;DTSSoftwareDev@dtsweb.com&gt;    

 
 
 
Chris, Jerry, John,
 
I've submitted a patch into 4.1 DEVEL for
 
29654
 dp 4.0 476 3D IRTRACC DATA does not match expected data when injecting dc input per test steps
 
This patch would also need to go into 4.0 and potentially into earlier versions as well.
 
The first issue is corrected by the change to DiagnosticBase.xaml.cs in the patch.
 
This portion of the issue does not appear to be present in 3.3 or earlier versions.  I think this happened because NONE got added as an initial offset possibility for all calibrations.  This means that it could select the EU corresponding to the NONE offset on the calibration.  Instead it should use the EU for initial offset for the channel which was identified as using initial EU.
 
The next issue I detected is probably present in 3.1 and 3.3, but maybe was never noticed before.  Looking at the xlsx from kogawasan (dts internal only, do not distribute), I noticed that
 
                //this is column r
                 var xa1 = δ * Math.Sin(θyprime * Math.PI / 180) + r * Math.Cos(θzprime * Math.PI / 180) * Math.Cos(θyprime * Math.PI / 180);
 
and
 
                //this is column t
                 var za1 = δ * Math.Cos(θyprime * Math.PI / 180D) - r * Math.Cos(θzprime * Math.PI / 180D) * Math.Sin(θyprime * Math.PI / 180D);
 
where using -δ in the xlsx but not in the code.
 
Now testing the issue is important, but it can be difficult to exactly simulate the sensors in question.  To deal with that I created a function ReplaceDataIfNeeded that allows us to use EU data from a file rather than the actual EU data we collected - letting us use the exact same data as in the xlsx.
 
to test:
 
place ZPOTEU.txt, DISPLEU.txt, YPOTEU.txt into your binary directory.  These contain the EU from the kogawa-san xlsx.
 
import the test setup in the issue (also attached for convenience).  Before you import this you'll need to setup allow calculated channels (and allow overdue hardware and sensors in system settings)
 
 
 
 
import the test setup and re-assign the channels to whatever hardware you actually have:
 
 
 
 
finally adjust the ROI period to what's in the xlsx (-.050 to 190)
 
 
when you download roi and it creates the calculated channels it will actually use what's in your files, not what was collected.
 
run a test, and download roi, export ROI CSV unfiltered, compare with the kogawa-san xlsx.
 
The two files will not match perfectly (because we don't put EU into the chn files we put ADC and a scale factor, and then re-calculate the EU), but will match pretty closely
 
here are the 4 columns from kogawa-san's xlsx
 
 
here are the same 4 columns from the export CSV
 
 
note that the resultant is not in kogawa-san's xlsx, as that was a separate request from honda http://manuscript.dts.local/f/cases/10709/
 
 
 
 Attachments: 
    DTM_29654_3DIRTRACC.patch 7.6 KB   thor_m_3d_irtracc_kogawa_san_confidential_dts_internal_only_include_data_new.xlsx 6.7 MB   ZPOTEU.txt 24.1 KB   DISPLEU.txt 29.3 KB   YPOTEU.txt 26.8 KB   right_lower_chest_ir_trac_569.xml 2.0 MB</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-26T21:39:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>first testing this I encountered an issue with one of the connectors on the Takashi Box/Greg Box - cable 1 excitation was behaving as shorted.
 
The unit I was using also seemed badly out of calibration and gave different mV readings even when all plugs were connected to the same sig gen source.
 
I changed the code to always read the same ADC and the same mV roughly for all sensors, which got me in the ballpark.  Checking out the 3D-IRTracc create method, I then discovered this issue;  InitialEU is 0 but we were expecting a value, tracking it down it seems maybe this value is in InitialOffset;</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-23T17:46:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-21T16:20:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-20T21:01:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-20T20:51:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-20T20:51:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-09-13T19:51:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-13T19:50:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>realtime data is not correct for all channels

![](index.php?/attachments/get/30315)

![](index.php?/attachments/get/30316)

![](index.php?/attachments/get/30317)


and in recorded data om ch 2 

![](index.php?/attachments/get/30318)


ch 3 looks correct in recorded data  

![](index.php?/attachments/get/30320)

incorrect recorded data for ch 1
![](index.php?/attachments/get/30321)

good data for ch 3
![](index.php?/attachments/get/30322)

T438526: 3D IRTRACC data is accurate [Needs updating]
http://testrailserver/index.php?/tests/view/438526</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-09-13T19:50:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>