<?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:47:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified w/ DataPRO 4.1.207, 4.0.857, 3.3.790, 3.1.699
 
Tested:
 
 
Assigned 12 DIM channels and 5 Analog to SIM
 
Ran test up to and including Diagnostics
 
No communication lost when running
 
 
2023-02-15 16:14:02.844 &lt;-  TDAS - QuerySerialNumber *0?N [00000081]\[00000081] - (127.2636ms), DR0328 *0?N ?N DM1249
 2023-02-15 16:14:02.848 -&gt;  TDAS - Test Channel Run (*)  [00000082], DR0328 *0TEST CHANNEL RUN PRE ALL</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-02-16T00:27:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-02-13T16:44:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-01-18T00:09:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2022-12-13T22:04:24Z</TimeStamp>
    <ReleaseNote>Corrects an issue with diagnostics timeouts when TDAS DIMs are configured in a TDAS rack</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-13T22:04:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-12T21:04:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-12T21:04:19Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>From: "ECO Email" &lt;ecoemail@dtsweb.com&gt;
Date: Fri, 09 Dec 2022 11:15:45 -08:00
To: "Dan McFadden" &lt;dan.mcfadden@dtsweb.com&gt;
Cc: 
Subject: (Case 30004) selecting DIM for slowest module can cause rack to stop responding.

</Comment>
    <StatusString>Emailed</StatusString>
    <TimeStamp>2022-12-09T19:15:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>3.1/3.3/4.0/4.1@47941</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-12-09T19:14:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-09T19:09:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-12-09T19:06:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>https://dtsweb.zendesk.com/agent/tickets/11212
 
if you set up a Rack with a SIM and a DIM, and assign more channels on the DIM than the SIM the DIM will be chosen as the slowest module, however Diagnostics on the DIM is very fast and this can result in the TEST CHANNEL READ ALL command being sent to the rack before TEST CHANNEL RUN is done on all channels.  When this happens the rack can lock up and stop communicating.
 
to duplicate the issue I assigned 12 digital inputs and 5 analog inputs to two modules in a rack like this:
 
 
when running the test the DIM was selected as the slowest module as indicated in the logs:
 
2022-12-09 10:20:31.859 (192.168.1.78:8000) [83] *1?N
 2022-12-09 10:20:31.978 (192.168.1.78:8000) [83]\[83] 1?N: DIM035
 
2022-12-09 10:20:31.979 (192.168.1.78:8000) [84] *1TEST CHANNEL RUN PRE ALL
 2022-12-09 10:20:33.144 (192.168.1.78:8000) [84]\[84] 1TEST: CHANNEL RUN PRE ALL OK
 
2022-12-09 10:20:35.182 (192.168.1.78:8000) [85] 0TEST CHANNEL READ PRE ALL
 
this resulted in a diagnostics time out and the rack frozen with a solid com led
 
 
There's a routine used to determine which module is the slowest module that we want to wait for on TEST CHANNEL RUN PRE ALL.  This routine was using the number of configured channels as the largest factor followed by whether a shunt or offset removal is performed.  In this case 12 channels was outweighing even a fully configured SIM at 8 channels.
 
After the patch a single analog sensor SIM will outweigh a fully configured DIM, and the SIM will be selected as the slowest module:
 
2022-12-09 10:55:15.73 (192.168.1.78:8000) [57] *0?N
 2022-12-09 10:55:15.235 (192.168.1.78:8000) [57]\[57] 0?N: DM0302
 
2022-12-09 10:55:15.237 (192.168.1.78:8000) [58] *0TEST CHANNEL RUN PRE ALL
 2022-12-09 10:55:22.954 (192.168.1.78:8000) [58]\[58] 0TEST: CHANNEL RUN PRE ALL OK</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-12-09T19:06:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>