<?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>2024-01-02T16:17:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-09-11T16:09:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with Dp versions 
4.0.1052.49567
4.1.436.49567
4.2.135.49567

Teseting by first discovering Tsr air with streaming enabled addign to test setup , running diagnostics .
Then disabled streaming channel on Tsr Air using Fwtu..
Deleted Tsr Air from DP db and rediscovered added to test setup and verified no errors .

 </Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-09-11T16:08:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-30T15:00:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-08-29T20:40:22Z</TimeStamp>
    <ReleaseNote>Addresses an issue where TSR AIR could report a channel count mismatch</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-08-29T20:40:06Z</TimeStamp>
    <ReleaseNote>Addresses an issue where TSR AIR could report a channel count mismatch when switching between streaming supported and not supported configuration</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-25T18:13:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.1/4.2@49417,4.0@49418</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-08-23T15:29:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>This issue happens when you turn on or off the Streaming support in firmware for a TSR AIR after you've already run data collection with the unit.
 
In the code we check the number of channels in the configuration on the unit against the number of channels in the database for the unit, but in this case if you configured the unit originally when streaming was supported then there will be an additional channel in the configuration versus what we have in the database.  Presumably the opposite is true too, if you turn on streaming support after you have run a test with streaming turned off in firmware the configuration on the unit will be missing a channel.
 
The patch deals with this by adjusting the number of channels returned by either adding a channel or removing a channel based on IsStreamingSupported and the configuration on the unit.  This is a bit of a hack, but it's also a bit of a weird situation that someone is running a test with a unit where the attribute for streaming supported has changed value ...
 
To test, running data collection with a TSR AIR normally, then turn off streaming support.  Delete the test and the DAS from the database, discover it in the database and create a new test setup and run the test, you should end up with a channel count mismatch like justin shows in manuscript.  After the patch you should be able to run data collection normally.</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-22T17:46:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-22T17:20:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-22T17:05:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>this code in CheckChannelCount is responsible for the mismatched channel count message;
 
 
in this case the version in the database has 19 channels, while the attached das reports it has 20 channels, this is coming from the count as it was last run, so if you have run it as with streaming it has 20 channels, go to FWTU and change it to not support streaming, the existing configuration on the device still has that streaming channel and still has 20 channels.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-22T17:02:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-22T16:53:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-22T16:48:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-21T19:20:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>When attempting to arm  a tsr air that has streaming disabled  datapro versions 4.1.404 , 4.0.1038 , and  4.2.1038   give channel count mismatch error at hw step of run test and fail to arm in any mode.


This feature was originally tested at datapro 4.1.257 and works in that version.
 
http://manuscript.dts.local/f/cases/30094/Implement-solution-to-disable-streaming-on-a-per-DAS-basis

http://testrailserver/index.php?/cases/view/215247


to reproduce..

1. Use fwtu connect to tsr air .. navigate to slice tools&gt;stack&gt;manage 
  
2. From system attribute dropdown menu on 1st page select disable streaming feature dropdown and set the value to 1 and click the write button this disables the streaming feature in fw.

3. Use datapro , discover the tsr air , create a test setup using the tsr air attempt to arm in active mode , at run test hw step the unit fails and gives message channel count mismatch and you cannot continue to arm.

info from the logs..
2023-08-21 12:07:10.575 -&gt;  Information - QueryFileData [00000161], TA0164, local: 192.168.1.100:57833, Remote: 192.168.6.64:8301 Store ID: 3, Start Byte: 0, End Byte: 399
 
2023-08-21 12:07:10.580 &lt;-  Information - QueryFileData [00000161]\[00000161] - (4.9833ms), TA0164 BytesDownloaded: 400
 
2023-08-21 12:07:10.580 -&gt;  Information - SetFileData [00000162], TA0164, local: 192.168.1.100:57833, Remote: 192.168.6.64:8301 Store ID: 3, Start Byte: 0, End Byte: 400
 
2023-08-21 12:07:10.585 &lt;-  Information - SetFileData [00000162]\[00000162] - (5.0703ms), TA0164
 
2023-08-21 12:07:10.585 -&gt;  Information - QueryFileData [00000163], TA0164, local: 192.168.1.100:57833, Remote: 192.168.6.64:8301 Store ID: 3, Start Byte: 0, End Byte: 399
 
2023-08-21 12:07:10.590 &lt;-  Information - QueryFileData [00000163]\[00000163] - (5.156ms), TA0164 BytesDownloaded: 400
 
2023-08-21 12:07:10.590 TA0164 has completed service DiagnosticsService
 
2023-08-21 12:07:10.590 DiagnosticsService finished - total time (0m 0s 30ms)
 
2023-08-21 12:07:10.590 CalibrationService.MeasureTransferSpeed: All units are now finished, calling ServiceAvailable
 
2023-08-21 12:07:10.596 failing channel count for  TA0164  18 != 19
 
2023-08-21 12:07:10.611 ModalWindow: No data recorders included in the test are available.
 
2023-08-21 12:07:20.600 User Admin pressed PageButton:DataProPage_ModalWindow_OK
 
</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-08-21T19:20:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>