<?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>2025-03-20T21:52:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>Tested on 4.3.436 no issue found with cases listed

However after first test run, make change to current ROI and do second run, during download ROI, it would show the setting from first run, while downloading config. Once complete then UI update to correct ROI setting. Open separate case</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-10-09T01:24:19Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-09-30T21:42:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Release note was already present.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-08-27T23:01:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Reactivating to add Release note.</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2024-08-27T23:01:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>51280 is 4.0; 51281 is 4.2; 51282 is 4.3</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-08-26T15:26:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-14T23:28:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2024-08-13T22:23:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-13T21:28:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>Wait for Jerry finish refactoring ROI logic then test again.

squib channels + digital out + analog channels 

case 1) in test setup added hardware channel and does not assign sensor. Assign ROIs by the channels.  


2) in test setup added hardware channel and sensor that has EID.   At the run test check sensor ID step If the EID physically is in the different channel than assigned, then DataPro would show message. Reassign the sensor to channel. Complete the test run and download ROI. Expect ROI channel and Sensor are as reassigned.

3) in test setup add sensor that has EID but not add hardware channel. Assign ROIs by the sensor.  
 At the run test check sensor ID step, the sensor would automatically assign to the channel that had EID physically. Complete the test run and download ROI. Expect ROI channel and Sensor are label correctly. -- this is currently failing with DP4.3.328

4) create single ROI test setup.
During download ROI, download as is
During download ROI, add new ROI

5)create Multi ROI test setup.
During download ROI, download as is
During download ROI, add new ROI
During download ROI, enable/disable ROI
During download ROI, change ROI duration
During download ROI, change ROI channel

</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-13T21:26:54Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-08-13T20:15:33Z</TimeStamp>
    <ReleaseNote>Addresses an issue where not all channels were downloaded warning could be displayed errantly when there was a squib in a dataset and not in an ROI</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment>Tested with DataPro 4.3.328
SPS01435 A1R8
SPT0001 D0M8
SPE0165 B0B6

Validated using the KM Copy and new setup using squib channels + digital out + analog channels with multiple ROIs. 

Issue is fixed.
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-13T03:44:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Randy Chu</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-08-09T02:15:39Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>51055 and 51061 are 4.2; 51062 is 4.3
51063 is 4.2
51079 is 4.2
51089 is 4.2
51180 is 4.0; 51181 is 4.2; 51182 is 4.3

To test:
Import a Squib sensor using a .csv file (an example file is attached).
Create a Test Setup that uses that sensor and include it in one of the ROIs.
Run the Test.
Ensure that no errors occur, and that the channels (Voltage and Current) associated with that sensor are downloaded.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-08-02T20:36:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-01T15:14:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-07-31T16:20:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-30T20:10:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-07-24T23:02:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Latest:
We should ignore the squib serial number, and just use "SQUIB" instead, since the hardware channel number makes it unique.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-21T15:52:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>Customers use the value of the UserValue1 field in the SensorsSquib table of the database for identifying sensor type when viewing the Sensors Available table on the Channels step of Edit Test Setup.
 
Therefore, instead of using the Comment (or, in one case, SquibDescription) property of a squib setting for identifying a ROI channel, we should use the SensorData.SerialNumber (or, in one case, ChannelName2).</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-19T05:30:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-18T17:40:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-18T15:23:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-18T15:16:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>The issue of ROI warnings is due to the presence of a non-blank UserValue1 field in the SensorsSquib table of the DataPRO database.

In the attached Test Setup, that field contains "Pyro Test Lead", which is causing a mismatch when that value is compared to the sensor Serial Number (in this case, 041704, 040393, 040391, and 047301).

When entering a Squib Setting manually into the database via the DataPRO Sensor Database tab, only the Name field is used for identifying the "sensor".  However, it is possible via a sensor import, as seen in the attached .csv sensor import.

One method for fixing existing Test Setups is to Export a Test Setup, modify the resulting .xml as follows:

1) Remove the, in this case, "Pyro Test Lead" value from the &lt;Sensors&gt;&lt;SensorData&gt;&lt;Comment&gt; and &lt;UserValue1&gt; fields.

2) Change the &lt;TestSetups&gt;&lt;TestSetup&gt;&lt;Fields&gt;&lt;RegionsOfInterest&gt;&lt;RegionOfInterest&gt;&lt;ChannelNames&gt; values by replacing, in this case, "Pyro Test Lead" with the appropriate squib setting Serial Number ("041704" for SQ-01, "040393" for SQ-02, etc.).

and re-import the Test Setup using the Overwrite option.

Note that any Voltage input channels that were in an ROI may need to have their checkbox re-checked, due to a possible, but not yet proven, software bug.


Going forward, when adding squib settings (sensors) to the database, refrain from entering a value for CommonField/UserValue1.

This issue exists in 1.10 also, so not sure how MIRA didn't experience it while using that version.

More to come.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-18T00:06:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-07-16T21:58:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-16T21:06:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-16T20:42:13Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-16T20:15:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-07-15T18:12:27Z</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 (#13880, #dtsweb.zendesk.com/agent/tickets/13880). Reply to this email to add an internal note to the request.
         
   
Kate Martin (DTS)
 
Jul 12, 2024, 18:23 GMT+1
 
Hi Dan
  
 I've been working with MIRA on a few issues these past few days.
  
 This is a problem that we need to take a look at please ...
  
 Clearly the back image shows the ROI periods still have these channels selected but the user gets a warning.
  
 
  
 
  
 and the data is there. 
  
  
  
 
  
  
 
  
 However, critically although I seem to be able to duplicate what is happening onsite at MIRA to an extent they do not get the data in either ROI download - only from Download ALL.
  
 My logs attached.
  
 2024-07-12 17:11:17.963 DownloadService.Download : calling service available
 2024-07-12 17:11:18.033 ModalWindow: Channel "041704" (hardware channel "Assigned by ID \ [SPT00015] SQ-01") has not been assigned to an enabled Region of Interest
 Channel "040393" (hardware channel "Assigned by ID \ [SPT00015] SQ-02") has not been assigned to an enabled Region of Interest
 Channel "040391" (hardware channel "Assigned by ID \ [SPT00015] SQ-03") has not been assigned to an enabled Region of Interest
 Channel "047301" (hardware channel "Assigned by ID \ [SPT00015] SQ-04") has not been assigned to an enabled Region of Interest
 2024-07-12 17:14:11.994 User Admin pressed PageButton:DataProPage_ModalWindow_OK
  
 I thought maybe "post test diagnostics" was messing things up but it's the same MO when you don't have this in test setup.
  
 Thxs
 Kate
 
Attachment(s)
 DataPRO.log
 DataPRO 2024-07-12 17.16.29.log
 DataPRO 2024-07-12 17.07.35.log
 2024_07_12 17_00.xml
         
----------------------------------------------
 Customer Details:
 Name: Kate Martin ( kate.martin@dtsweb.com )
 Organization: DTS
 
----------------------------------------------
 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 #
   
13880
     
Status
   
Pending
     
Requester
   
Kate Martin
     
CCs
   
-
     
Followers
   
Dan McFadden, Jerry Lawrence
     
Group
   
Support
     
Assignee
   
Kate Martin
     
Priority
   
Normal
     
Type
   
Problem
     
Channel
   
Web Form
     
 
 
This email is a service from DTS. Delivered by Zendesk.
 
[79VZM6-LNKGX]Ticket-Id:13880Account-Subdomain:dtsweb</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2024-07-15T18:12:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>