<?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:20:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-27T22:49:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-26T22:00:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-26T21:58:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with dp 4.0.1077.49798 and 4.1.478.49798,and dp 4.2.200.49802


Compared UTC timestamps from  csv export to utc timestamps  in live streaming data (netview) and ch10 export timestamps  to verigy they all match  in both analog 1 and analog 2 streaming formats.


Test as follows ...

(System settings need to be enabled as follows      useutc time in csv exports checked , enable input and output clock source options checked, allow streaming modes checked , allow advanced recording modes checked)

1. Create test setup with Das synced set to sync as slave  to PTP  via the grandmaster on dts network or another master das.
2. Set recording mode to record and stream  60 sec post time  add 6 analog channels and the stream out channel and set it to ch10 analog .
3.Arm das , open netview and subscribe to the stream .. give start command on das then trigger ,    download all  data  from das .
4.On export tab  export data to chapter 10 format with include secondary header format unchecked.
5. Next export data to CSV unfiltered format .
6. Open The exported csv file and compare the timestamps to the netview timestamps .
7. Download the ch10 tools  located here https://www.irig106.org/

https://www.irig106.org/downloads/Ch10Tools_v39.exe

install and use the tool to open the ch10 export and verigy the irig computed time shown  matches the start time in the csv export .


8. Close the current session in netview and then open the ch10 exported file using netview and verify the netview timestamps match the timestamps in the csv export.


9. Repeat all theese steps setting the stream  type to ch10 analog time format2 , except the step to check irig computed time in the tool ( it will show 0 for format 2) .And when exporting the  ch10 file check the box to include secondary header .

The exported ch10 files do not  show scaling at this time ...</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-10-26T21:57:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-26T16:16:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified with dp 4.0.1077.49798 and 4.1.478.49798,  cannot  test with 4.2 due to case.. 34408 .


Compared UTC timestamps from  csv export to utc timestamps  in live streaming data (netview) and ch10 export timestamps  to verigy they all match  in both analog 1 and analog 2 streaming formats.


Test as follows ...

(System settings need to be enabled as follows      useutc time in csv exports checked , enable input and output clock source options checked, allow streaming modes checked , allow advanced recording modes checked)

1. Create test setup with Das synced set to sync as slave  to PTP  via the grandmaseter on dts network or another master das.
2. Set recording mode to record and stream  60 sec post time  add 6 analog channels and the stream out channel and set it to ch10 analog .
3.Arm das , open netview and subscribe to the stream .. give start command on das then trigger ,    download all  data  from das .
4.On export tab  export data to chapter 10 format with include secondary header format unchecked. 
5. Next export data to CSV unfiltered format .
6. Open The exported csv file and compare the timestamps to the netview timestamps . 
7. Download the ch10 tools  located here https://www.irig106.org/

https://www.irig106.org/downloads/Ch10Tools_v39.exe

install and use the tool to open the ch10 export and verigy the irig computed time shown  matches the start time in the csv export .


8. Close the current session in netview and then open the ch10 exported file using netview and verify the netview timestamps match the timestamps in the csv export.


9. Repeat all theese steps setting the stream  type to ch10 analog time format2 , except the step to check irig computed time in the tool ( it will show 0 for format 2) .And when exporting the  ch10 file check the box to include secondary header .

The exported ch10 files do not  show scaling at this time ...</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-26T16:03:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-25T20:31:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1/4.2@49798</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-10-25T17:32:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>I guess I'll just use universal time here in the CH10 export too seems a little wrong, but it'll be consistent with CSV export.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-25T16:09:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-25T16:08:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>according to the CH10 export here is the time for the start (t0 after subtracting pretrigger)
 
 
according to the DTS file:
 
here's the time for Trigger:
 
TriggerTimestampSec="1698166361" TriggerTimestampNanoSec="875431625"
 
it looks like there is 2.5684 pre trigger seconds;
 
 
this means 1698166359307031625.0000M nano seconds should be the start time, which results in the 1698166359 and 307031625 #s shown above.
 
CSV export shows for the T0 the time of:
 
 
matching the timestamp in ch10 export
 
it shows the pretrigger time as a less precise -2.568, which appears to match the adjusted start time in nano seconds and seconds.
 
 
(except for the .0004)
 
these functions return very different times.
 
 
it seems chris's short cut won't work.
 
the difference here is that the CSV export is in universal time, as is the viewer, but the CH10 export is in universal time.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-25T16:05:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-25T15:15:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T21:35:57Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T17:39:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T17:38:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T17:37:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T16:44:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Reopening this because timestamps for analog format 1 exports dont match  csv exports or  live netview stream  timestamps.


Tested in both datapro 4.0.1076.49789 and 4.1.477.49789 ,  unable to test in datapro 4.2.197.49789 due to an issue with it starting up ..  case 34405 


Running with Datapro 4.1.477.49789....



 When setting the stream profile to analog format1 and exporting to analog format 1   the timestamps in netview dont match  the original  netview live stream  time or the csv export utc  timestamps.

 Looking at the attached screenshots above.. you can see the live streamed data  in netview shows timestamps at 22:45:26 to 26:46:26 but the exported ch10 analog format 1 file from datapro viewed in netview shows timestamps at  15:05:01  to  15:06:26. The File will also not display any data on the line graph in netview when it is played .

The exported csv utc time matches the netview stream  also (22:45:26 to 26:46:26) , but does not match the exported ch10 analog file time .


Viewing the ch10 file with the ch10 tool also shows irig time of  15:05:01    which doesnt match the original stream  timestamps  or the csv export data .


Also looking at attached screenshots below shows comparison of a second test  timestamps live netview stream vs the exported csv and ch 10  timestamps which match in format 2 when opened and viewed with netview but  the ch10 packet viewer shows irig time of 0     . Using time format 1 the ch10 exported  File timestamps do not match  the csv export or live stream timestamps when viewed in netview or with the packet viewer. 



to Reproduce 

1. Create test setup set for Record and Stream and sync to Grand master 
Set streaming channel to analog time format 1.
2. Start and trigger das and view and record live stream using netview.
3.Download all data from das and export to csv and export to  ch 10 with include secondary header unchecked.


netview live stream time is bit behind on the start since I had to  start the das  first then open the line graph ...

But the ch10 data shows and irig time of  09:12:01   which is much different than the netview and csv start  time of 16:52:39 

When the ch10 exported file is opened with netview  it also shows 9:12:01 start time instead of the   16:52:39  time .  

 When viewing the time format 2 exports they show irig time as 0  in the ch10 packet viewer not sure if this is an issue or not  since   they can be opened with netview and viewed and show the correct timestamps that match the original live stream and csv data .

The data is attached with the exports in it also .






</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2023-10-24T16:42:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T15:25:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T15:24:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T15:24:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T15:10:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T15:05:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Running with Datapro 4.1.477.49789....

Time format 2 issue is fixed and exports to netview now show timestamps that match  the streaming data  with or without trigger.

However when setting the stream profile to analog format1 and exporting to analog format 1 the file cant be played back and viewed with netview .. there is no data shown on the graph and the timestamps in netview dont match .

 Looking at the attached screenshots you can see the live streamed data  in netview shows timestamps at 22:45:26 to 26:46:26 but the exported ch10 analog format 1 file from datapro viewed in netview shows timestamps at  15:05:01   to  15:06:26. The File will also not display any data on the line graph in netview when it is played .

The exported csv utc time matches the netview stream  also (22:45:26 to 26:46:26) , but does not match the exported ch10 analog file time . 


Viewing the ch10 file with the ch10 tool also shows irig time of  15:05:01    which doesnt match the original stream  timestamps  or the csv export data .
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-24T14:44:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-23T15:20:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1/4.2@49789</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-10-20T21:14:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-20T21:14:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-20T16:13:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>CHRIS, John, Farshid,
 
I've attached a patch for 33199.  This is a complicated issue with maybe a problematic fix.
 
33199
 Add Time format 1 as an export option for CH 10 export
 
The original request was to add a time format 1 export to CH10 export, that's implemented but an issue was discovered by Justin while testing this.  Justin had a unit that SAID it was time sync'd, but had no trigger time stamp and the start record time stamp was around 3600s or so, which in unix time since 1970 is still in 1970.  When justin looked at the timestamps in the CSVs exported with "Use UTC" property set for CSV export (shown here)
 
 
 
 
simultaneously there is code to display the timestamp when there is PTP time available (nanoseconds and seconds) in the viewer code.  In the viewer code the timestamps are only used if the year of the date is &gt; 1990.   I took abstracted this condition out to a function in PTPTimeStamps.cs and used it to also turn off using timestamps in the CSV export when the timestamp is &lt; 1990.
 
The CH10 code really kind of requires some timestamp even if it's 1970 and probably bogus, so it uses the timestamp as it is (even if it's 0).
 
So this fixes a couple of issues 1) the start record time stamp can be used if it's available. 2) the discrepancy between the CSV times and the CH10 files is resolved in that the CSV no longer shows date time when it's invalid date/time.
 
CH10 export in a recorder mode recording WITH a valid timestamp for start record is expected, and it's expected to work with a valid T0 with timestamp too.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-20T16:13:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-19T23:45:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-19T23:43:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-19T23:43:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>there's code in other places (viewer) that rejects timestamps that are before 1990, we should probably do that here too ...
 
what I'm receiving given by previous post is that there's a difference in output of the two getdate functions which are making some assumptions on whether it's in UTC or not, but in this case the timestamp itself could be bogus and we might need to ignore it.  Other code ignores stamps &lt;1990, we should do that here too probably ...
 
so to be clear there's multiple things in play here
 
1) use start record when available
 
2) don't use time stamp if you have some crazy &lt;1990 date [in both CSV export and CH10 export...]
 
here is the dataset just was using which was creating different output for CSV export vs CH10 export.
 
needs to be in a folder "s6 air synced"</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-19T23:42:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>re-activating to fix justin's case (export a dataset with no trigger time and a weird start time)</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2023-10-19T18:42:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-18T22:21:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>packet viewer and ch10 validation tool can be found on this page:
 
https://www.irig106.org/
 
https://www.irig106.org/downloads/Ch10Tools_v39.exe
 
there are two applications, 
 
 
the validate chapter 10 streams application only handles certain levels of CH10 data (notably it does not support time format 2)
 
there's an option now "Include secondary header" in the CH 10 export options.  When this option is turned on exports will be in Analog Time Format 2, when the box is unchecked the export will be in analog time format 1.
 
These tests are expected to work
 
1) either time format 1 or time format 2 should display unsigned adc with time stamps that match exported UTC timestamps from DataPRO using export to CSV (you have to turn on UTC timestamps for CSV export first).
 
2) if using analog time packet 1 format the third packet will be a data packet and will indicate the time of the first sample.  This should also match the time in the XLSX.  use the left and right arrow buttons to go to the next or previous packet.
 
 
3) the "Validate Chapter 10 Streams" tool is expected to not return any errors with a Chapter 10 analog time format 1 export (so unclick include secondary headers and export, then run the validate tool against the .ch10 file, click on "validate format of packets" and "Output all packets.  You may also need to select an output director and output file.
 
select OK and then on the next form "Validate"
 
 
the output files will appear wherever they were pointed to (C:\temp\ in my case)
 
look in the files and verify no errors: (if there's an error it'll say "error" with an error code)  both files shouldn't show any errors:
 
 
4) if you use Ch10 analog time format 2 the second packet will be a time packet, it will not contain IRIG time but will contain a secondary header with Time Fmt: IEEE 1588
 
 
4.0/4.1/4.2@49749</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-10-18T21:57:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>there's some current work to be done for this for pax river</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2023-10-17T23:24:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-05T20:01:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-02T22:23:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-02T22:22:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-09-27T21:37:58Z</TimeStamp>
    <ReleaseNote>Adds an option in CH 10 export to not include secondary time headers</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-09-27T18:50:03Z</TimeStamp>
    <ReleaseNote>adds an option in CH 10 export to not include secondary time headers</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-09-19T15:34:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>added a new option to include secondary time header or not into the CH10 export, when this is off it will no longer include the secondary time header in packets, it will no longer include time packets in the export either.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-09-18T21:07:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Huy suggests this may be just removing the secondary time header, but I think it could be more than that as there are actual time packets too.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-09-14T23:18:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-09-13T15:16:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-09-12T17:22:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-09-01T16:18:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-09-01T16:11:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-09-01T16:11:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>