<?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:16:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-08-01T17:45:15Z</TimeStamp>
    <ReleaseNote>Corrects issue with PCM streaming template channel for TSR AIR.</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with Datapro versions  4.0.1014.49271,4.1.375.49270 and 4.2.63.49271

Pcm Mode ch10 pcm  time format 2  now has correct scaling in tmats and when streaming to netview .
Verified by performing 2g rolls on accels channels and mounting a reference 6dx on top of Tsr air and rotating for ars channels to a slice base and comparing recorded data.


Verified  Tmats file now  have..  C-1\DCN:{CHANNEL 1 NAME};
C-1\MN1:{CHANNEL 1 NAME}; 




Ars Channel X has has an issue when streaming in pcm modes it is not showing ars data but instead is showing duplicate data from the low G Accel X channel ,Opened a separate issue for this after  mentioning to Eric and Dan .This only happens when streaming in pcm modes, and does not occur in analog streaming modes , relatime or recorded data.

   opened case 33017  for fw issue

 

</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-07-28T21:45:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Found seperate issue with ARS x channel and Accel channel data   opened case 33017  for fw issue</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-28T21:25:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Just got netview installed locally testing today also ..</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-28T15:39:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-07-28T15:38:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.2@49271
 
4.1 already had the patch applied apparently.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-07-28T14:11:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>I did make those changes!
 
 
I think for some reason that change was only made in 4.1, I'll apply to 4.0 and 4.2 again.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-07-28T13:47:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Kate Martin</User>
    <Comment>Testing today did not resolve the issue
 
 
 
 
The templates
 
 
 
 
for TSR Air PCM doesn;t appear to contain the right syntax for MN1 on the right section :-
 
C-1\DCN:{CHANNEL 1 NAME};
 C-1\BFM:TWO;
 C-1\DCT:COE;
 C-1\MN4:PCM
 C-1\CO\N:1;
 C-1\CO:{CHANNEL 1 OFFSET EU};
 C-1\CO-1:{CHANNEL 1 SCALEFACTOR EU};
 C-1\MN3:{CHANNEL 1 EU};
 C-1\MOT1:{CHANNEL 1 MAX RANGE EU};
 C-1\MOT3:{CHANNEL 1 MAX RANGE EU};
 C-1\MOT5:{CHANNEL 1 MAX RANGE EU};
 C-1\MOT2:{CHANNEL 1 MIN RANGE EU};
 C-1\MOT4:{CHANNEL 1 MIN RANGE EU};
 C-1\MOT6:{CHANNEL 1 MIN RANGE EU};
 
which from testing yesterday should be
 
C-1\DCN:{CHANNEL 1 NAME};
 C-1\MN1:{CHANNEL 1 NAME};
 C-1\BFM:TWO;
 C-1\DCT:COE;
 C-1\MN4:PCM
 C-1\CO\N:1;
 C-1\CO:{CHANNEL 1 OFFSET EU};
 C-1\CO-1:{CHANNEL 1 SCALEFACTOR EU};
 C-1\MN3:{CHANNEL 1 EU};
 C-1\MOT1:{CHANNEL 1 MAX RANGE EU};
 C-1\MOT3:{CHANNEL 1 MAX RANGE EU};
 C-1\MOT5:{CHANNEL 1 MAX RANGE EU};
 C-1\MOT2:{CHANNEL 1 MIN RANGE EU};
 C-1\MOT4:{CHANNEL 1 MIN RANGE EU};
 C-1\MOT6:{CHANNEL 1 MIN RANGE EU};
 
Thxs</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2023-07-28T12:20:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-07-27T22:46:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1/4.2 @49267
 
to test use PCM view with a TSR AIR in netview using streaming with format PCM 144 analog time format 2 and it _should_ view.  Additionally in the TMATS file these two fields should appear as expected.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-07-27T22:12:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-07-27T22:01:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>per testing by CPB and KM;
 
C-X\MN1:{CHANNEL X NAME}; needs to be added for each channel
 
C-X\DCT:NON;  should be changed to COE for each channel</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-07-27T22:01:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>