<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-06T23:49:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-01-16T21:12:36Z</TimeStamp>
    <ReleaseNote>Adds import and export support for IRTRACC sensors with radius calibration and EQX</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with DataPRO v4.2.324, 4.0.1119
 
Tested:
 
 
Non-Linear enabled ✔
 
Create a sensor in sensor database as the following:
 
 
Click save
 
Export this sensor with EQX export format 
 
should show up as an option for export
 
 
Pre-Patch (4.2.220) would not show non-linear sensors
 
 
 
 
open .e2x in an editor and verify  
 
Lets do some simple math 
 
In the .e2x file 
 
sensor cal factor from sensitivity details in UI = -1000/sensitivity1 -&gt; -1000/-294.117645 = 3.4
 
 
Exponent from UI should match the sensitivity 2 field of the .e2x file
 
 
 
Intercept = sensitivity3 / sensitivity1 =&gt; -617.64705882352939/-294.117645 = 2.1000000147
 
 
 
 
 
This test should get exported and reimported. Some rounding is not being handled correctly but as mentioned this is expected.</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-01-15T23:43:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-11T23:16:04Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.2@50042
 
since there are differences between the requests from (-1000 in the image, 1000 in the text).  The user themselves might have to formally validate this change, however I've done what I think the request is.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-01-09T22:16:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-09T22:13:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-09T18:53:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>after exporting and re-importing there were some float/double conversion errors.  I don't think these can be corrected in the short term, the are part of using floats and doubles and doing math with them and imposed by the EQX schema itself (which uses float for sensitivity)</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-09T18:29:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>after reviewing image above that -1000 was used in the image rather than the 1000 that was used in the text.
 
I assume the image is correct and -1000 should be used...</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-09T18:09:13Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>set sensor up like this:
 
 
before the patch EQX export does not show non linear sensors;
 
 
here is the function that is determining which sensors are shown in the table;
 
        private void SetSensorTableFiltering(bool showTDCOnly, bool showSlicewareOnly)
         {
             _sensorListVm.ShowOnlyTDCSensors = showTDCOnly;
             _sensorListVm.ShowOnlySlicewareSensors = showSlicewareOnly;
 
currently it appears to ONLY be excluding CAlfactor;
 
            if (ShowOnlySlicewareSensors)
             {
                 //FB14750: When exporting sensors in SLICEWare XML format only compatible Analog sensors should display as potentially being exported
                 if (NonLinearStyles.IRTraccCalFactor.ToString() == s.NonLinearCalculationType) { return false; }
             }
 
 
 
here is the code that is getting the sensitivities right now;
 
                            SensitivitySpecified = eqxScalingMethod == EqxScalingMethod.Linear,
                             Sensitivity = (float)GetEqxSensitivity(sc, 1),
                             Sensitivity2Specified = eqxScalingMethod != EqxScalingMethod.Linear,
                             Sensitivity2 = GetEqxSensitivity(sc, 2),
                             Sensitivity3Specified = eqxScalingMethod != EqxScalingMethod.Linear,
                             Sensitivity3 = GetEqxSensitivity(sc, 3),
                             Sensitivity4Specified = eqxScalingMethod == EqxScalingMethod.CubicPolynomial,
                             Sensitivity4 = GetEqxSensitivity(sc, 4),
                             Sensitivity5Specified = eqxScalingMethod == EqxScalingMethod.CubicPolynomial,
                             Sensitivity5 = GetEqxSensitivity(sc, 5),
 
I'll split this into two functions, one for the existing behavior and one for IRTracc-calfactor ...</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-09T17:58:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>from kate:</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-09T16:47:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-09T16:44:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-09T16:44:13Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>when importing from EQX, if it's an IR-TRACC sensor
 
set the cal factor to 1000/sensitivity1, and set intercept to Sensitivity3/Sensitivity1
 
when exporting,
 
set EU to mV, set Sensitivity1 to 1000/Cal factor, set sensitivity 3 to (Intercept/calfactor)*1000?</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-09T16:33:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-19T23:12:39Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-19T22:05:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-19T22:03:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-04T17:00:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Kate Martin</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-12-04T13:46:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Kate Martin</User>
    <Comment>https://dtsweb.zendesk.com/agent/tickets/12401
 
The EQX working group have declined a request to add an "mm" aka EU category to the XSD used to define IRTRACC sensors.
 
This is not desirable as it means the factors listed in the EQX file are not easily traced to the actual DataPro set up GUI by the user who may query results.
 
However the EQX working group is made up of a lot of Kistler users who having added a digital category for DTI systems are reluctant to support more methods...
 
 
As a result this request is to perform a series of data conversions when exporting/importing IRTRACC sensors when they are calibrated with radius calibration to support EQX users with IRTRACC radius cal sensors
 
&lt;ScalingMethod&gt;IRTRACC&lt;/ScalingMethod&gt;
 
&lt;Sensitivity&gt; aka cal factor
 
This is calculated from (1 / DP GUI "CalFactor") * 1000 so that it is in mV/Vlin/mm 
 
&lt;/Sensitivity&gt;
 
 &lt;EngineeringUnit&gt;mV&lt;/EngineeringUnit&gt;
 
 &lt;Sensitivity2&gt; aka exponent
 
This remains as the exponent 
 
&lt;/Sensitivity2&gt;
 
&lt;Sensitivity3&gt; aka radius zero position intercept
 
This is calculated from  (DP GUI "Intercept" / DP GUI "Cal Factor") *1000 so that it is in mVlin
 
&lt;/Sensitivity3&gt;
 
 Then when we consume suech an EQX it would be the reverse.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-12-04T13:46:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>