<?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-08-24T00:16:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-31T17:16:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with Datapro versions... 4.0.1174.51112,4.2.461.51113 and 4.3.300.51137

-------Steps used to Test------
- Created Test Setup with Streaming ( I used Circ Buffer +Streaming)  Using both Analog 
    time Format 1 and then repeating for analog time format 2

- Armed  Das And  opened netview to subscribe to Stream  

- Triggered Das and Downloaded Data with Dp then exported to Ch10 file type ( chose to use 
   secondary header when streaming atf2 and   not use sec header when streaming atf1)

- Opened Exported ch10 file and compared the file header which is tmats text to the ch10 
   export of pre patched version of datapro ... Verified the fields AF-x- field changed 
   from   U to B and BFM switched from UNS to OFF   for each channel .

-  repeated this test for  all 3 versions of datapro both atf1 and 2  and verified Netview 
   can open and  display the stream both the live stream and hen then also open and display 
   the  ch10 file data .







</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-07-31T17:13:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-07-30T20:12:36Z</TimeStamp>
    <ReleaseNote>changes the S6A analog streaming and the CH10 export format TMATS to be unsigned binary with offset</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-30T19:38:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-30T19:38:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-07-29T21:53:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.2/4.3@51072</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-07-18T20:13:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>run streaming with S6A, and export CH10 with any DAS
 
the tmats files produced should have AF-x- field changed from U to B and BFM switched from UNS to OFF
 
there shouldn't be any change to netview and export other than that prepatch to post patch.
 
no changes were made for TSR AIR or other stream formats (PCM, super 128, etc)</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-18T20:13:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>per loc this should be changed to offset binary and offset binary</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-07-18T19:42:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-07-18T19:22:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>##- Please type your reply above this line -##
 
This ticket (#13861) has been updated.
         
   
John Patrick
 
Jul 17, 2024, 17:05 PDT
 
Hello Dan and Maugan,
 
In reviewing the exported CH10 files with our data review tools team we found what was causing our issues with the CH10 export files, below is what they found.
 
We have found the problem. The data is being recorded in OFFSET BINARY format but indicates that it is unsigned binary in the TMATS. OFFSET Binary inverts the most significant bit and makes the number signed. The combination of inverting a bit and using another as a sign bit is what caused the fixed offset between our export and the “truth” data from the excel. This should be rectified in the TMATS export. Currently it looks like in the template it is hardcoded to U which is unsigned binary. Per the standard it should actually be “B”. Similarly, c-d\BFM should also be updated.
         
 
         
   
Dan McFadden (DTS)
 
Jul 11, 2024, 08:57 PDT
 
Happy to help however I can.
  
 If it’s a validation issue with a particular tool you might also check to see whether “include secondary headers” is turned on in the export or not
  
 
 When this is turned off the export will use strictly time format 1 and without the secondary headers.   Depending on the tool secondary headers and time format 2 could cause issues, so trying the export with this turned off might result in output that the tool can use.
  
 Let me know if there’s any way I can help,
  
 ~ Dan
         
 
         
   
Dan McFadden (DTS)
 
Jul 11, 2024, 08:52 PDT
     
Private note
     
Happy to help however I can.
 
 
 
If it’s a validation issue with a particular tool you might also check to see whether “include secondary headers” is turned on in the export or not
 
 
 
 
When this is turned off the export will use strictly time format 1 and without the secondary headers.   Depending on the tool secondary headers and time format 2 could cause issues, so trying the export with this turned off might result in output that the tool can use.
 
 
 
Let me know if there’s any way I can help,
 
 
 
~ Dan
 
 
                         
                         
       
       
                                       
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).
 ​
 ​
                   
 
                 
Attachment(s)
 ~WRD0001.jpg
         
 
         
   
Maugan Robert (DTS)
 
Jul 11, 2024, 00:36 PDT
 
Hello John,
  
 Thanks for creating a ticket. I've assigned it to our software manager who is the expert on the ch10 export function in DataPRO.
 Could you let us know what makes you say "are stated to be not valid"? Are you using a third-party software to read the ch10 export from DataPRO? If so, which one? If not, how are you trying to process the exported data in ch10 format?
  
 The CH10 export function in DataPRO is based on the Analog frame, time format 2 (with 2nd header time format 2). Perhaps there is a compatibility issue with how you try to read it?
  
 
  
 Thanks!
 Maugan
         
 
         
   
John Patrick
 
Jul 10, 2024, 11:25 PDT
 
I am using the CH10 export feature in DataPRO and trying to understand why the IEEE 1588-2008 PTPv2 time packets in the CSDW are stated to be not valid even though the time stamp appears to be correct. Binary and CH10 data files are attached. 
 
Attachment(s)
 2024_07_09 16_49_TC_IMV_TLM_input_TC_v2_data.zip
 2024_07_08 15_26_TC_IMV_CH10_export_verify_x2_v3_data.zip
         

 ------------------------------------------------------------
 CUSTOMER DETAILS:
 Name: John Patrick ( john.patrick@ngc.com )
 Organization: NGC Chandler - Strike
 Customer Details:
 
You are an agent. Add a comment by replying to this email or view ticket in Zendesk Support.
     
Ticket #
   
13861
     
Status
   
Open
     
Requester
   
John Patrick
     
CCs
   
John Baca
     
Followers
   
Chris Balogh, John Moors, Maugan Robert
     
Group
   
Software
     
Assignee
   
Dan McFadden
     
Priority
   
Normal
     
Type
   
Problem
     
Channel
   
Web Form
     
 
 
This email is a service from DTS. Delivered by Zendesk.
 
[MKV53N-P0REV]Ticket-Id:13861Account-Subdomain:dtsweb</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2024-07-18T19:22:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>