<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Link to bug 37954</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-11-04T19:35:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>verified with datapro versions 4.0.1190 ,4.2.504.51580 and 4.3.486.51589

Tested issue reported in long list of latest issues and passed:


Database has year 1,_,_,4. Currently EID is on year 4.
Import year 2 MOD file
Expected Result: EID now is on year 2.
Actual Result        --PASS  dp  4.0.1190
                      PASS DP  4.2.504.51580
                      PASS DP  4.3.486.51589 




test step
1)DataPro &gt; test setup &gt; import &gt; THOR 3 FCA Group.xml
This would create sensors serial number end with 1 as year 1 and a group.


2) DataPro &gt; sensor database &gt; import &gt; format  = MOD, file =  ATD THOR03 Year 1 Cal Values.mod
This would update the sensor calibration data to today date.


3)DataPro &gt; sensor database &gt; import &gt; format  = MOD, file = ATD THOR03 Year 3 Cal Values.mod

Expected Result
This would create new sensor serial number end with 3.
Remove EID from the sensor that has same first 6 digit.
Add EDI to the sensor that end with 3
Update group with sensor end with 3



Actual: PASS Datapro 4.0.1190 
            Pass  datapro 4.2.504  
	 Pass  datapro 4.3.486.51589 

Eid is removed form  original sensor  and assigned to new sensor that end with 3
Group is updated 



</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-10-31T20:30:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:52:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Tested issue reported in long list of latest issues and passed:


Database has year 1,_,_,4. Currently EID is on year 4.
Import year 2 MOD file
Expected Result: EID now is on year 2.
Actual Result         --PASS  dp  4.0.1190
                       PASS DP   4.2.504.51580
                       PASS DP   4.3.486.51589  






</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:47:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>All subcases that are set for dp 4.4      are removed since this case if for datapro 4.2 release...</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:18:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:17:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:16:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:16:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:16:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:16:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:16:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:15:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:15:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-10-31T19:15:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-10-22T23:25:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-06T01:35:19Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>50465 is 4.0; 50466 is 4.2; 50467 is 4.3.

Re-importing the same .mod file now does not generate errors.
</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-03-12T21:05:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>I think there's a failure of importing the mod file in step 2 of the sensor_database_import mod docx file earlier in this ticket, all the rest of the failures already have additional child issues attached.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-03-07T22:07:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T23:51:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T23:39:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T23:35:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T23:25:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T23:17:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T23:01:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T22:24:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T22:10:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T22:08:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T21:58:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>Add corner case:  Import MOD file that -1 and -2 years.
result failed:
 After import year 2 MOD. EID is on year 2. And EID is removed from year 4. However Year 3 sensor is created with Cal Date=1/1/0001, and Sensitivity = none


Jerry decided that 50 Character is the Limit for Serial number, name and EID. </Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-26T21:26:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>The test result is getting too long see attached file instead.
Sensor_database_import_MOD_file_2_23_2024
For subsequence update to this file please increase date code.</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2024-02-24T03:02:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-24T03:01:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-23T05:33:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-23T05:32:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>The test result is getting too long see attached file instead.
Sensor_database_import_MOD_file_2_23_2024
For subsequence update to this file please increase date code.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-23T05:17:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-02-23T03:02:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-02-12T20:52:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-02-12T20:51:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Based on "Zendesk 12690: According to Alessandro the sensor serial number will always be a core 6 characters plus the year", compare the first 6 characters of a serial number, instead of all but the last character.  This will allow xxxxxx9 to become xxxxxx10, and the .MOD import will continue until infinity and beyond.

To test: Import sensors with a more-than-one-digit suffix (like xxxxxx10) and ensure that the results are correct.

50348 is 4.0; 50349 is 4.2; 50350 is 4.3</Comment>
    <StatusString>Reopened</StatusString>
    <TimeStamp>2024-02-12T20:51:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-16T20:51:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-16T20:51:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with dp versions 4.0.1121 and 4.2.325 .With sensors first imported from a test setup with eid and out of date cal dates using the attached test setup file.  Then importing  the attached mod file into the sensor db with  new cal dates and eid that match id's of the sensors already imported that new sensor sns are created  with the new cal dates and the id is removed from the old sensor and associated with the  ones in the mod import .

Test added to testrail...http://testrailserver/index.php?/cases/view/217531</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-01-16T20:50:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-11T15:53:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-02T16:22:39Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-12-19T21:24:39Z</TimeStamp>
    <ReleaseNote>MOD import behavior has been updated to account for serial number changes during calibrations</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>UpdateGroupChannels
 
could potentially be improved by rather than calling update on each channel one by one by having a stored procedure that updates all channels at once, or a stored procedure that takes tables as input that updates all the channels between all sensors at once.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-15T18:51:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49974 is 4.0; 49975 is 4.2.

To test:
Import the attached Test Setup .xml.
Move to the Sensor Database tab and import the attached .mod file.
Ensure that all of the sensors import correctly, and are assigned to the Group channels.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-12-13T23:11:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49958 reverts 4.0; 49956 and 49957 revert 4.2.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-13T16:10:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-12-13T16:05:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Reactivated because implementation was incorrect.
Instead of adding a new calibration record to the existing sensor, 
1) a new sensor is supposed to be imported, 
2) the old sensor's EID should be blanked so that the new sensor will have that EID, and 
3) the Group channels are to be updated to use the new sensors. </Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2023-12-12T23:53:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49949 is 4.0; 49950 is 4.2.
Don't delete sensor calibration records when doing a .MOD sensor import.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-12T00:03:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49946, is 4.0; 49947 is 4.2
To test:
Import the attached Test Setup .xml.
Move to the Sensor Database tab and import the attached .mod file.
Ensure that all of the Sensitivities import correctly.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-12-11T23:15:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-12-11T22:17:13Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>10) invalid characters in serial number/comment fields
There is no validation done for characters in the Serial Number field.  Even angle brackets don't interfere with .xml exports:

</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T21:56:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>8) sensor with invalid calibration date
N/A - .MOD file doesn't contain calibration date (today's date is used)

9) sensor missing calibration in file
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T19:19:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>7) sensor with too long of sensor serial number (probably already handled)

Truncates to 30 characters
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T19:17:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>6) sensor appears twice in file (probably just overwrites with the last
one?)

Correct, last entry is imported
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T19:16:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>5) flat out wrong file selected (select a CSV or a DataPRO XML)
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T19:14:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>3) sensor not in the database (probably already handled)

4) sensor in the database (this is the normal use case probably)

Both cases work fine.

</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T19:13:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T19:12:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>2) bad import - probably already handles this, but
b) missing attribute or xml tag
c) garbage in the xml
Correct, already handled.


</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T19:10:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>2) bad import - probably already handles this, but

a) different decimal separator
Could be an issue:




</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T19:09:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Feedback from patch review by Dan:

There's a whole bunch of scenarios which could be in the SQA plan although they might not be relevant to this specific issue ...

1) existing EID on a different sensor (so say sensor A1 and sensor C1, not A1 and A2) - the existing code probably already handles this.

Correct, already handled:

</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T19:04:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Warning message will be bolded, prefixed with "Warning: ", and followed by an exclamation point.
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-11T18:18:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>The implementation allows sensors imported via the MOD sensor import to update a sensor that's already in the database with the same EID, as long as the sensor Serial Number differs only in the last character.

To do this, I created a new signature for CanSensorIdBeAssigned() which returns an existing sensor if it finds one with the EID being tested.  If so, the importing sensor's Serial Number is changed to the existing sensor before the import.

</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-09T00:30:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Kate Martin (DTS)
 
Dec 7, 2023, 13:46 GMT
    Private note    
Hi Dan
  
 Thank you - 4.0 wil be just fine.
  
 As you will have seen from numerous emails to HiTec about getting these files there's just radio silence so I've fudged them myself.
  
 Attached you will find the THOR group file XML with "last years" sensor serial numbers in, along with a .MOD file that I have incremented the serial numbers+1 to simulate "this years" cal values along with a +1 on the sensitivity just so it's easy to see if it is updated.
  
  One extra ask .. can we make this sort of message a bit clearer please as it's sort of lost when we have a file where no sensor will be imported ...
  
 
  
 Thxs
 Kate
 
 
 
Attachment(s)
 THOR 3 FCA Group.xml
 ATD THOR03 This Year Cal Values.mod</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-07T16:10:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-12-05T23:03:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-05T23:01:26Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-05T21:13:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-12-05T21:10:26Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-11-29T23:48:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-11-29T23:48:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>##- Please type your reply above this line -##
 
You are a follower on this request (#12690, #dtsweb.zendesk.com/agent/tickets/12690). Reply to this email to add an internal note to the request.
 
 
 
          
Kate Martin (DTS)
 
Nov 28, 2023, 18:34 GMT
    Private note    
FYI - I am trying to acquire last years THOR .MOD file (I have this years) so we can use these 2 files for testing.
 
 
         
 
          
Kate Martin (DTS)
 
Nov 28, 2023, 18:32 GMT
    Private note    
Hi Dan
  
 I think surfacing the fact that the .MOD file being loaded contains DallasID's that will be removed from existing sensors in the DataPro DB and used in the new imported sensors would be a good along with a list of which groups will be updated with the new sensor serial numbers as a result. That way it will be obvious as these .MOD files are generated on a per ATD basic right now.
  
 Thxs
 
 
         
 
          
Kate Martin (DTS)
 
Nov 28, 2023, 17:35 GMT
    Private note    
Hi Dan
  
 The assumption can be that when we receive a .MOD file it will only have come from FCA's main sensor cal DB and will have sensoers in it with matching DallasID to those already in DataPro DB bit with sensor serial numbers in the new .MOD file that will have been bumped by + 1 as the last character.
  
 Thxs 
 
 
         
 
          
Dan McFadden (DTS)
 
Nov 28, 2023, 16:34 GMT
    Private note    
 
Is the assumption then if we receive a MOD import it should always have serial numbers reduced by 1 or will there be imports from sources other than cal?  Does this need to be a setting exposed in the import?  (whether sensors are from cal or should alter the serial number in the import)?
 
 
                                                                                              Dan McFadden​​​​   Software Engineering Manager               Diversified Technical Systems, Inc.  |  Seal Beach ,  CA                   e:     dan.mcfadden@dtsweb.com     |         o:     +1 562 493 0158 x137     |     www.dtsweb.com                                       CONFIDENTIALITY: This email and any attachments may contain information from Diversified Technical Systems, Inc. (DTS) which​ is confidential ​and/or proprietary. If you received this transmission in error, any use, reproduction or dissemination of this transmission​ is strictly prohibited. ​Please delete this message and notify sender immediately.  
 ​EXPORT CONTROL NOTICE: This e-mail may contain technical data whose export, transfer, and/or disclosure may be controlled by​ the US ​International Traffic in Arms Regulation (ITAR) 22 CFR part 120-130 or the Export Administration Regulations (Commerce).
 ​
 ​                                  
 On 11/28/2023 7:40 AM, Kate Martin (DTS) wrote:
 
 
 
         
 
          
Chris Balogh (DTS)
 
Nov 28, 2023, 16:17 GMT
 
Hi Kate and Alessandro,
  
 We'll talk this over with the engineering team to see what we can do to satisfy this request. We will try to post a response soon.
  
 Talk to you soon,
  
 Chris
  
  
 
 
         
 
          
Chris Balogh (DTS)
 
Nov 28, 2023, 16:15 GMT
    Private note    
workaround for calibrations is to edit .mod to subract 1 from all SNs
  
 
 
 
         
 
          
Kate Martin (DTS)
 
Nov 28, 2023, 15:42 GMT
    Private note    
FYI Rainer - if only Hi Tec had mentioned that FCA increment the serial number annually in our call, all would have been clear. As always too much TOP URGENT smoke without undertanding the real issue.
 
 
         
 
          
Kate Martin (DTS)
 
Nov 28, 2023, 15:40 GMT
 
Hi Dan
  
 This feature request is actually the solution for this ticket that was closed with no resolution... 
  
 https://dtsweb.zendesk.com/agent/tickets/11582
  
 and the og .MOD import feature request ...
  
 https://dtsweb.zendesk.com/agent/tickets/8498
  
 Basically the problem is that although the .MOD import works just as they wanted it, what they forgot to mention was that every year when a sensor is calibrated it's serial number last digit is bumped by one up to 10 thereafter it then returns to 1.
  
 That means that when you come to import a .MOD file for the second year onwards of sensor cals, the .MOD import will not import any sensors because the Dallas ID is already associated with the previous years sensor serial number.
  
 One way to get these imported would be to delete the DallasID's for each of the 131 sensors, or delete these 131 sensors etc before reimporting, but the problem is that the group assigment then needs to be remade as you are now allocating different sensor serial numbers with each ATD channel. Another way is to edit the .MOD file to keep the same serial number but this then breaks the audit trail of sensor serial number. 
  
 What we need because this import is unique to FCA, is a V2 .MOD import where it can create the new sensor serial number with matching Dallas ID in the .MOD file and then delete the same Dallas ID from the existing sensor in the DataPro sensor database - so we keep the cal history albeit it from multiple serial numbers for the same sensor rather than from the cal history for one sensor serial number.
  
 The second part of this V2 import is the trickier bit, where we also need to update any group entry where the existing sensor exists and replace it with the new sensor from the .MOD file. Test Setups should not be touched.
  
 What do you think ? FCA have a central master DB from where the .MOD file is created and imported into DataPro and no change to why they increment the sensor serial number is going to happen as it ties into too many other systems.
  
 If we want to make FCA happy and avoid the hassle with ATD Lab Tech then a V2 .MOD import seems like the only path forward.
  
 Can you think about it and let me know a potential timeline please ?
  
 Thank you
 Kate
  
  
   
  
  
  
  
  
  
 
 
         
 
----------------------------------------------
 Customer Details:
 Name: Alessandro Sorteni ( alessandro.sorteni@hi-tec.it )
 Organization: Hi-Tec (Italy rep)
 
----------------------------------------------
 If you no longer wish to see notifications for this ticket, please use the 'Unfollow' option in the Followers List.
 
 
You are an agent. Add a comment by replying to this email or view ticket in Zendesk Support.
    Ticket # 12690   Status Pending   Requester Alessandro Sorteni   CCs Giuseppe Ciminaghi   Followers Chris Balogh, Dan McFadden, Rainer Rahaeuser   Group Support   Assignee Kate Martin   Priority Normal   Type Problem   Channel Web Form    
 
 This email is a service from DTS. Delivered by Zendesk.
 
 [2MZMJM-9NPX9]Ticket-Id:12690Account-Subdomain:dtsweb</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-11-29T23:48:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>