<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with DataPRO v4.2.221, 4.1.486, 4.0.1085
 
Tested:
 
 
In DataPRO import the attached xml file
 
After importing, export the OOP\CRABI... sensor via EQX format
 
This drops it into C:\DTS\DTS.Suite\4.2.221\SensorDatabase (this is my path and could be different for your)
 
Right click on SensorDB.e2x and compare to .xml file that was used to import (not the xml inside step 3's path)
 
 
Notice that the .e2x file uses the later version of the calibration history when exporting. This also reflects in DataPRO sensor db:</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-01-11T23:14:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-02T16:21:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-11-21T19:21:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-11-21T19:21:17Z</TimeStamp>
    <ReleaseNote>Corrects issue with calibration exported with EQX sensor export</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-11-16T18:38:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-11-10T18:22:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>Changes:
 
 
Add case to LINQ statement in GetEQXSensorsFromSensorData to account for cases of 2+ sensor calibrations from the same day, differentiating using ModifyDate
 
 
Testing:
 
 
Import Kate's Sensor Database attached to this issue
 
Export just the "OOP\CRABI...." sensor to EQX format
 
Open the file (it's XML) in whichever text viewer you like
 
The values assigned to the sensor in the export should be from the 9:39am calibration. Earlier versions of DataPRO were exporting the values from the 9:36am calibration.
 
 
Edge cases:
 
 
The gist of the bug is "if the latest calibrations for a sensor occur on the same day, EQX export was picking the first one instead of the last". However the Sensor DB here only had 2 same-day latest cals. Creating a sensor with 3 or more and attempting the test hasn't been done yet.
 
I believe the other sensor exports include all of the calibrations, not just the last one like EQX. Might be worth confirming.
 
[dtm] may also want to consider what happens if you try to export a sensor that has no calibrations, and what happens if you have one with a dual calibration.  You may want to manually delete the calibration in the db to test no calibrations.
 
 
Committed to v4.0 maint, v4.1 maint, and v4.2 dev in r49864</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-11-08T20:17:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-11-08T15:57:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-11-07T20:20:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-11-03T21:59:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>Stealing</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-11-02T19:24:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-31T14:37:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Kate Martin</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-30T13:08:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Kate Martin</User>
    <Comment>As reported in HC#12579 we do not export the latest cal values when there are multiple cal values on the same day. It appears that althought this was reported in 3.3x it is still a bug in 4.0.1035 for example..
 
This export parse shows the correct sensitivivty but the resulting EQX file will not have this value - it will have the value from the earliest time on that day not the latest.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-10-30T13:08:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>