<?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:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-19T03:54:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-15T17:13:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Tested with Dp 4.1.129   and Dp 4.0.770  Using iena-p plugin and wireshark .
 
Firewall in windows needs to be turned off , and will continually turn back on every few minutes , so you need to keep turning it off for this test to work .
 
 
 
Steps to test..
 
1.Create test setup add stream out channel  and  set Das to streaming ( checkbox in test setup ) set port to      51000
 
2. Arm Das and reboot , Make sure firewall is disabled in windows.
 
 
 
Iena packets can be seen in wireshark.
 
Verified Port number is set in 165 and Iena Key is set in  162 (value 3) 
 
 
 
 
 
To install plugins for Wireshark see this case for instructions....case11515</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2022-12-15T17:11:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-15T16:50:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-15T16:49:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-15T16:49:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-15T16:49:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-15T16:48:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Dp 4.1 Iena seems to be working ...</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-15T16:24:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-14T22:42:43Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2022-12-13T22:01:36Z</TimeStamp>
    <ReleaseNote>Adds additional stream out configuration options and UI</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-13T22:01:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2022-12-13T22:00:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>related case for additional CH10 parameter:
 
case 29987</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-06T17:51:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1@47910</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-12-06T17:14:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>now sensor database tile will also only show relevant parameters for stream outputs, so IENA will only show IENA parameters, etc.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-06T16:42:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-05T23:57:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Jerry, John,
 
I've submitted a patch into 4.0 MAINT for
 
29844
 Add support/UI for configuring additional streaming parameters
 
this is a high priority issue for sales as they claim they need it by DEC 15th for the customer, so I developed in DP 4.0 first (IENA support).  The IENA support is only one part of this manuscript issue, but it was all bundled in together, so here we go!
 
in the issue Loc indicated a bunch of parameters that need to be updated, and hinted to a new streaming mode that would need to be added:
 
IRIG106 UDP Chapter 10:
 - UDP Streaming IP:Port        = SysteAttribute#149.  default = UDP://239.1.2.10:8400
 - Time Interval (u16)          = SystemAttribute#154. default  500. 0 = disable.
 - CGDP (TMATS) interval (u16)  = SystemAttribute#145. default 1000. 0 = disable.
 - Time Channel ID (1-64K)      = SystemAttribute#162 value[0].
 - Data Channel ID (1-64K)      = SystemAttribute#162 value[2].
 - Data Format (PCM, Analog..)  = SystemAttribute#152 UDP Stream Profile.
 
 TmNS (wit PCM payload format)
 - UDP Streaming IP:Port        = SysteAttribute#149.  default = UDP://239.1.2.10:8400
 - SubFrameID (16bit)            = SysteAttribute#165 value[0].
 - Message ID (16bit)            = SysteAttribute#165 value[1].
 - Minor per Major (16bit)      = SysteAttribute#165 value[2].
 - TMATS Port (same streaming IP)= SysteAttribute#165 value[3].  with 2nd header time format 2.
 
 IENA (P-Type. Position parameter only.)
 - UDP Streaming IP:Port        = SysteAttribute#149.  default = UDP://239.1.2.10:8400
 - Source Port number (16it)    = SysteAttribute#165 value[4].
 - IENA Key("Data Channel ID")  = SystemAttribute#162 value[2].
 
first going over UI changes:
 
in the sensor database streaming output already had some of these settings contained in a field "TMNS config".  I preserved this internally but broke the fields out in the UI so that they can be changed less ambiguously:
 
 
the settings that are only relevant for a streaming mode are shown, so the CH10 parameters are shown for CH10 formats, the IENA parameters are shown for the IEPE profiles, etc:
 
There is also an IENA positional only stream mode now.
 
 
 
 
 
 
 
 
note that - CGDP (TMATS) interval (u16)  = SystemAttribute#145. default 1000. 0 = disable. is not included, this parameter is not in this patch, I'll create a separate issue to add that parameter into the UI at a much lower priority.
 
changes should be saved and restored when editing a stream output setting.
 
 the stream out parameters now break these out as well, except all parameters have to be shown - but '---' is shown when a parameter is not valid for the selected streaming mode.
 
 
 
 
changes should save and be restored when going to Edit test setup-&gt;Parameters -&gt; stream output
 
note that to have streaming in a test setup you may need to turn on allow streaming modes in system settings -&gt; test setup settings
 
 
finally if you want to run a test setup with a streaming mode you'll need to set the das to streaming assuming a S6Air is being used:
 
 
in the list above Loc indicates which INDEX of the TMNS config the parameters are stored in.
 
if you set the das to streaming and arm the values can be validated using the FWTU and the fields loc indicates for example:
 
2022-12-02 10:52:24.122 &lt;-  Realtime - I106StreamConfigSet [00000400]\[00000400] - (6.9989ms), S6A0079 Stream Profile Number: 13 UDP IP PORT: System.Byte[] Irig Config: 1 TMNS: 0, 6, 60, 0, 2, 0, 0, 0,
 
 
 
Attribute 162 INDEX 2 (number 3) should match IENA key
 
attribute 165 INDEX 4 (number 5) should match IENA port
 
in an older application version (say DP 4.0.729 the release version of DP), if you try to run a test with IENA streaming you'll get this:
 
 
The sensor database will not warn you, it'll just show CH 10 analog time format (the default) instead of IENA
 
If you try to save a test setup and the S6A does not support it (protocol version 93), it should warn you:
 
 
if you run a test but the hardware does not support it, then CheckHardware should warn you:
 
 
I don't have any specifics on how to test IENA streaming mode other than through attributes, but Loc may have details on how to test it using wireshark or netview.
 
protocol version 93 and IENA is implemented in S6A firmware G0N5.  This firmware is not released yet, but can definitely be obtained from f/w dept.
 
here's one location it can be found at:
 
\\dts\files\Software\Private\Builds\Firmware\SLICE\Slice 6 AIR FW\1.0.320.27868\SLICE6AIR-FW-G0N5
 
Now implementation-wise, there are no new database changes and only one new profile value, so although there are UI changes everywhere, there's not a ton of code changes.
 
I added a new class DTS.Common\Classes\TMNSConfig that simplifies going from the split out values and the (x,....y) string field that is stored in the database.  I did not change the storage mechanism at all.
 
in StreamConfigureUDP.cs I broke out the TMNS1-TMNS7 to named fields so it'll make more sense when looking at code.
 
in SensorData.cs I broke out/exposed the new fields, but internally have it change the TMNSConfig property
 
a similar thing happens in GroupChannel.cs, I expose the properties so they can be used by the parameters UI, but internally it's stored in the TMNSConfig which was already present.
 
In StreamOutputRecord.cs I added the new IENA stream profile as an available profile type.
 
In SLICE6AIR.cs I added the constant IENA_PTYPE_STREAM_MIN_PROTOCOL, and updated IsStreamingProfileSupported to be aware of it.  I'm not sure if/when support is planned for any other hardware?
 
EditStreamOutputControl, and GroupChannelSettingsListView both had to be updated to be aware of the new fields and expose them in the UI.
 
in SLICE Service Realtime.cs, where the actual parameters are sent to the S6Air it now breaks them out more cleanly using the TMNSConfig class.</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-12-05T18:01:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-30T00:18:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>RSV13 will be renamed to IENA_PTYPE_STREAM</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-30T00:18:19Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Loc Pham</User>
    <Comment>Added IENA wireshark plug-in. IENA document is in SVN.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-29T19:07:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-11-29T16:44:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-29T16:38:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-29T16:25:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-29T15:34:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-11-29T15:30:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T21:26:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-28T21:25:46Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-10-28T21:25:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>case 29839
 
should be implemented in 4.1 first, then a new issue opened to apply to 4.0 and blocked and then re-activated after SQA validates.
 
Due to time constraints (customer needs apparently by 12-15) implement in 4.0 first.
 
these should probably be per stream parameters, and would need to be serializable and also LTS friendly.
 
Old clients should work with a new database that has streams with these parameters set.  The parameters should be serializable/deserializable (import/export).
 
old 4.0 clients should work with new db.  new clients should work with old db.
 
I'm listing out what could be parameters that Aerospace USERs are interested in configuring UDP streaming
 
 IRIG106 UDP Chapter 10:
 - UDP Streaming IP:Port        = SysteAttribute#149.  default = UDP://239.1.2.10:8400
 - Time Interval (u16)          = SystemAttribute#154. default  500. 0 = disable.
 - CGDP (TMATS) interval (u16)  = SystemAttribute#145. default 1000. 0 = disable.
 - Time Channel ID (1-64K)      = SystemAttribute#162 value[0].
 - Data Channel ID (1-64K)      = SystemAttribute#162 value[2].
 - Data Format (PCM, Analog..)  = SystemAttribute#152 UDP Stream Profile.
 
 TmNS (wit PCM payload format)
 - UDP Streaming IP:Port        = SysteAttribute#149.  default = UDP://239.1.2.10:8400
 - SubFrameID (16bit)            = SysteAttribute#165 value[0].
 - Message ID (16bit)            = SysteAttribute#165 value[1].
 - Minor per Major (16bit)      = SysteAttribute#165 value[2].
 - TMATS Port (same streaming IP)= SysteAttribute#165 value[3].  with 2nd header time format 2.
 
 IENA (P-Type. Position parameter only.)
 - UDP Streaming IP:Port        = SysteAttribute#149.  default = UDP://239.1.2.10:8400
 - Source Port number (16it)    = SysteAttribute#165 value[4].
 - IENA Key("Data Channel ID")  = SystemAttribute#162 value[2].</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-10-28T21:25:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>