<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-12-18T18:07:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-12-18T18:07:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>reopening to set testrail flag to true....</Comment>
    <StatusString>Reopened</StatusString>
    <TimeStamp>2023-12-18T18:07:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-24T20:57:42Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-04-25T17:59:10Z</TimeStamp>
    <ReleaseNote>Adds support for auto adding voltage input settings on channels</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-24T20:27:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-24T17:54:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Added to testrail dp regression  Voltage Sensor is automatically added in Test Setup When dragging Bridge channel from HW . - TestRail</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-24T17:49:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-20T17:11:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Verified in Datapro 4.1.264.48571 That a voltage sensor is added automatically when dragging a Bridge Channel from Hardware onto the channel assignments if there is not already a  sensor assigned and if "create voltage input channels"  checkbox is checked in  System settings.
 
Also verified that test created in dp 4.1 with an auto voltage sensor can be imported into datapro 4.0.916.48572 .
 
Also tested the following  on dp 4.1.264.48571
 
1. Tested  on  new installation  "create voltage input channels"  checkbox is checked by default.
 
2. The default zero method is set to absolute zero as expected.
 
3.The sensor Sn is assigned Voltage Input and iso code is  CH xxx Voltage    "[S6A0047] CH-03 Voltage  for example and this name also shows up  when data is viewed.
 
4. Confirmed  when Saving test setup and changing parameters for the channel  changes are preserved.</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-04-20T17:10:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-19T23:02:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-04-19T22:11:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0@48572 (this just checks in a change to 4.0 so that 4.0 going forward doesn't crash if you edit a test with a voltage input channel, but 4.0 still doesn't support voltage input channels)</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-04-19T21:52:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.1@48571 checkin for 4.1 to support voltage input channels</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-04-19T21:32:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-14T14:55:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-13T17:25:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Jerry, John,
 
I've submitted a patch into 4.1 DEVEL for
 
29764
 Auto-Add Voltage Input Analog sensor in Test Setup
 
I've also included Nate and Chris to see the feature before it gets committed as well to offer any feedback or changes needed.
 
For this feature it seems that it would be a lot easier to simply create a voltage input sensor and prevent the sensor from being edited, but that's not what the feature calls for.
 
This feature is scheduled for 4.1, but it includes some fixes that would also be useful for 4.0 that I noticed while working on it - noticeably TSA_EMBEDDED as a string appears a lot in the UI for TSR AIR when it shouldn't.
 
 I'm not sure this feature would be appreciated by automotive or crash labs ... they might be confused by dragging a hardware channel to channels and suddenly having a datachannel, so I at least put the drag and drop behavior behind a flag in the db, although it's set to true by default.
 
In the UI the setting can be found in System settings-&gt;Test settings-&gt;Create voltage input channels
 
 
The default for the setting should be true, clicking Restore settings at the top of the page should restore the setting to "True"
 
The UI for channels and channel settings can be found in the GroupChannelListViewModel.  Rather than having the MVVM query the database to get the CreateVoltageInputChannels setting, it has a property in the interface that is set by DataPRO.
 
IGroupChannel and GroupChannel also gain a new property "VoltageInsertionSensor" that lets the UI trigger and react on the property.
 
The first step of adding a voltage input channel is dragging a hardware channel to an empty channel.
 
 
When CreateVoltageInputChannels is set to true this will create a new channel set up as a voltage input channel.  When the setting is false this just creates a new channel with a hardware channel assigned, as would be the case before the patch.  If the channel has a sensor already on the channel the hardware assignment is changed but not the sensor assignment, and this includes if there was already a voltage input channel on the the channel.  There's some potential for confusion here as when a voltage input channel is created the channel name is given a user channel name and an iso channel name based on the hardware channel, for example "[S6A0047] CH-03 Voltage".  Dragging on channel 4 would not rename this channel, but that's the default behavior for other channels and this isn't a situation that happens with any other embedded sensors.
 
pressing "Clear" in the hardware channel list removes the channel from the test, this is consistent with TSR AIR channels.  Pressing Delete in the channel list deletes the channel, no change here.  Pressing remove sensor unassigns the voltage input setting for the channel, but leaves the hardware channel assigned.
 
going to the "parameters" nav step shows the channel, and allows changing the range of the channel.  The settings for the numeric up down control are copied from the ordinary range control, which puts a min of .1, but has no max.
 
This control should still show a drop down to change the range for TSR AIR channels that can be edited, and '---' for TSR AIR channels that can't be edited.
 
The default zero method should be Absolute Zero.  I also added Absolute Zero as a valid zeroing method for other embedded sensors, I'm not sure why it was removed for the other TSR AIR embedded sensors ...
 
Saving this test setup and editing it again the channel and settings should be preserved.   Exporting the test setup, deleting the test setup, then importing it again and the settings should still be the same.
 
running a test the channel should resolve just as any other non EID hardware assigned channel.  Clicking clear will remove the sensor and it can be assigned to another channel, but this doesn't make a lot of sense as the channel name won't be changed.
 
 
In Diagnostics the channel will show up with Voltage and '---', with Voltage measurement in the result details.  Shunt is turned off as is remove offset for the channel.  The actual range should reflect what the range parameter was set for in edit parameters, here it's just set for 2400.
 
 
 
 
in realtime the channel should show mV.  It only allows EU, the same as other embedded channels, from which we are borrowing implementations from.
 
 
 
 
in View the channel description (TSA_EMBEDDED for embedded sensors before the patch) is replaced with '---', same with channel description, and the serial number is left blank, similar to how it's handled in parameters and the channel list.
 
 
 
 
the embedded sensor used for the implementation exists in DP 4.0, no changes are needed for the db.  That being said, importing the test into 4.0 will fail (but not crash).  Editing the test setup with a 4.0 client does crash the client (due to the lack of a sensor calibration on a non tsr air channel with a sensor calibration).  This is probably unfixable in old code, but we could either patch 4.0 or just include the changes in 4.0 for newer 4.0 clients.
 
In DiagnosticsBase.xaml.cs shunt is now not enabled for test specific embedded sensors.  Alternatives to this might include checking GroupChannel.IsVoltageInput to be more restrictive, but I don't think we want shunt on any of the embedded channels.
 
this is not enough to turn off the shunt as a diagnostic action, that's done later on in ConfigureActions.  There I turn off shunt, but also turn off the remove offset.
 
In EditTestSettings.xaml.cs (which is used for displaying the test settings) I noticed that the use test object up down wasn't listed in the keys, so I added it.  This could potentially mean the field wouldn't show the correct value if it changed between visiting the page as the notification wouldn't have fired.
 
in GroupChannel.cs prepatch code would set embedded channels to use the default zero method as the zero method, but the default zero method is average over time and I'm not sure we want that with embedded sensors.  I instead changed it to use the first zero method from the zero methods for the sensor calibration, then made sure the voltage insertion would have none as the first zero method available.
 
I also created a method "CreateVoltageInsertionChannel" which is modeled after the CreateTSRAIRChannel, but is simplified as we need to do less for voltage insertion. 
 
In ITestDataSeries and the implementation class I added a SensorSNDisplay.  The sensor SN for embedded channels contain the string TSA_Embedded and this is already used in some places, but I didn't want to display this in the UI, so I created a new property.  This could also be achieved with some triggers in the UI instead, this just seemed simpler since the class is of limited use and not used outside the viewer.
 
You might notice I set BridgeResistance or Shunt in multiple places.  It turns out various actions can cause the sensor to be reloaded from the database, and some of these properties aren't set when loading from the database.  I explored the idea of modifying the sensor gets, but it's a little complicated as the information to know what to set might not be known at get time as the sensors can be retrieved by anything getting sensors, and embedded sensors can have a variety of different EU units, and properties ...</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-04-13T15:34:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-13T14:09:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-13T14:08:48Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-13T14:08:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-04-12T13:54:26Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-11T17:47:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-11T15:37:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-04-11T14:52:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-28T14:54:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-03-27T15:46:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-02-28T22:55:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-02-28T21:57:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-17T22:12:09Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-17T19:19:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-01-03T19:11:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-13T17:10:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-20T21:23:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-20T21:21:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-20T21:21:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>resolving 8 hours for design, 16 for implementation, 8 hours for test &amp; documentation/manual</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-13T17:19:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-10T18:21:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment>hours needed for potential add for 4.1 dev</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-10T18:20:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-10-10T18:20:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment>https://dtsweb.zendesk.com/agent/tickets/10980
 
 
 
 
 
Chris Balogh  less than a minute ago (assign)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Origin: Leonardo Helicopters, Redstone Test Center, HQ, DTS-MI
  
 Threshold Request: As a DataPRO user I would like to be able to add analog hardware channels to the Edit Test Setup &gt; Channels &gt; Channel List table without the need of an analog sensor from the Sensor DB. This is similar to the behavior of adding a TOM squib hardware channel today where a generic squib channel is added with defaulted parameters.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-10-10T18:20:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>