<?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:46:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified w/ DP version 4.1.130 &amp;&amp; 4.0.771
 
In Test Setup of TSR AIR
 
Parameters step change range value and run test up to diagnostics
 
In log file verify value is being written in  StackChannelRangesMillivolts attribute:
 
2022-12-15 16:52:16.048 -&gt;  Attribute - SetArmAttribute [00000233], TA0061, local: 192.168.1.177:51825, Remote: 192.168.6.61:8301 Key: StackChannelRangesMillivolts, DataType: Float32Star, Length: 76, Overwrite: True, Value: (32, 32, 32, 0, 0, 0, 2000, 2000, 2000, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0)</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2022-12-16T01:10:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-12-15T02:57:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-12-14T18:15:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2022-11-01T19:43:05Z</TimeStamp>
    <ReleaseNote>IGNORE</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>47779 is 4.0; 47780 is 4.1</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-10-26T22:55:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-25T17:18:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-21T23:08:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>The original design bullet point, "set StackChannelInputRanges appropriately..." is not needed.  Instead, the g values that are input by the user can be passed directly to the StackChannelRangesMillivolts attribute (an array).</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-21T23:07:20Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-21T23:03:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-10-20T15:46:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-10-18T20:31:58Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-18T20:11:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>as a request from Daniel, please keep separate track of design implementation, and dev testing/test design time</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-18T20:05:04Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-10-07T21:53:02Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-10-07T21:11:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Implement in 4.1 and then after closed by SQA open new issue to apply to 4.0 or re-open this issue to re-apply to 4.0.
 
make sure to create some document for referencing the changes for manual if it's needed, as well as testing.
 
Low g and angular rate channels should have adjustable ranges in Edit Test setup Parameters, however the range will be fixed to the highest of the 3 like channels (the highest of the high g channels, the highest of the angular rate channels).  For this issue it's not necessary to resolve that in the UI, we can add an additional manuscript item to add some feedback in the UI to indicate the these channels are locked to each other (unless it can be done in a reasonable amount of time or in the original estimated time).
 
the Range tab on the attached xlsx shows the ranges that can be achieved for those channels - this can also be found at:
 

http://build:8080/svn/firmware/SLICET/MCU/FW/trunk/documentation/sampleRates.xlsx
 
What needs to be done:
 
* make sure parameters for low g and angular rate channels with TSR AIR can be edited (for now don't worry about protocol version locking the controls)
 
* Make sure the proper gain is selected by f/w (can be checked by referencing the scale factor in xlsx)
 
* set StackChannelInputRanges appropriately to get the desired EU.  This is a little tricky as you need to first calculate the sensitivity for that EU using the table in the range tab, then use that scalefactor to calculate what the actual input range you want, then further adjusting the input range between that gain and half way to the next gain to account for any possible cal factor adjustment - for example for 32g the sensitivity is 1/1024, so the input range should be (32*(1/1024)+16*(1/2048))/2.  The firmware will automatically choose the lower gain/higher EU output when between gains, so the goal here is to get it to round up to the 32 EU gain position even after considering any cal factor adjustments, and avoid overshooting to the 64g gain.  This should probably be done when determining the input range to set on the TSR AIR channel.
 
location of supporting f/w:
 
\\dts\files\Software\Private\Builds\Firmware\SLICET\Slice T FW 425 Dev\1.0.895.27736</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-10-07T21:11:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>