<?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:18:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with DataPRO v4.0.1067, 4.1.455, 4.2.161
 
Created a test with DataPRO and enabled "Display offset in EU" in system settings
 
 
Ran a test with an offset coming from signal generator
 
In diagnostics step (in table view) notice Initial offset (EU) column</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-10-02T17:52:54Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-09-21T21:37:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>could not duplicate in 4.1.  I have a sensor with remove offset set to false, but with check offset to true and it outputs the row.  I suspect if check offset is off it will not output the row, that's by design.  I did make a change to not show the offset(mv) column when show offset in eu is on, and vice versa
 
 
 
 
4.0/4.1/4.2@49617</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-09-19T17:15:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-09-13T15:17:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-09-13T15:16:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-09-12T20:59:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>I added a note here. Calspan is using the updated version you built a couple of weeks ago--thank you! However they report that sensor w/o remove offset enabled do not display the measured offset during diagnostics. It looks like we used to show it in 3.1</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2023-09-12T20:08:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Nate Brown</User>
    <Comment>Calspan reports that voltages, pressure sensors still do not show Measured EU during Diagnostics. I believe Calspan would have these all configured to not remove offset, however they would still like to be able to see the measured offset in EU during diagnostics.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-09-12T18:50:04Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-09-12T17:29:54Z</TimeStamp>
    <ReleaseNote>Addresses Offset in EU not being displayed in diagnostics table</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.1/4.2@49466</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-08-31T20:38:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-31T20:37:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-08-31T17:03:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>John, Jerry,
 
I've submitted a patch into 4.02 DEVEL for
 
33195
 table mode does not show offset in EU
 
This issue was reported as very important for CALSPAN.
 
to enable display in EU you need to change this setting;
 
 
all you need to do with see the issue on a default db is to change this setting to TRUE, then run a test and view diagnostics in table view mode.
 
the Initial offset in EU is blank even though the offset was clearly measured as indicated by the offset in mV right next to it.
 
 
I tracked this down to a condition.
 
if (null != MyChannel.Sensor &amp;&amp; null != MyChannel.Sensor.Calibration &amp;&amp; CalibrationEnforcement.NonLinear != CalibrationEnforcement &amp;&amp;
                 (!MyChannel.Sensor.Calibration.NonLinear || MyChannel.Sensor.Calibration.LinearAdded))
 
With this condition in place a non linear sensor always goes into the "not supported" area and the offset in eu is never calculated.  I believe this was broken by issue 18011
 
the patch more or less leaves the condition as is as I didn't understand what the original condition was trying to do, but I added to it so that a non linear sensor will pass through and calculate offset.  I think the original conditional must have been related to dual sensitivity channels with in Use Both mode, so that should probably be retested as well.</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-31T17:01:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-31T16:26:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-08-31T16:26:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>this appears to have been broken in case 18011
 
the issue is with this constraint:
 
            if (null != MyChannel.Sensor &amp;&amp; null != MyChannel.Sensor.Calibration &amp;&amp; CalibrationEnforcement.NonLinear != CalibrationEnforcement &amp;&amp;
                 (!MyChannel.Sensor.Calibration.NonLinear || MyChannel.Sensor.Calibration.LinearAdded))
 
 
 
if you have NonLinear as your calibration enforcement policy (the default) even if you have a non linear sensor it drops to the "not supported" section and doesn't update.
 
to test, create a test setup with a non linear sensor and run diagnostics and switch to table view:
 
To turn on display offset in EU need to change this setting.
 
            if (null != MyChannel.Sensor &amp;&amp; null != MyChannel.Sensor.Calibration &amp;&amp; CalibrationEnforcement.NonLinear != CalibrationEnforcement &amp;&amp;
                 (!MyChannel.Sensor.Calibration.NonLinear || MyChannel.Sensor.Calibration.LinearAdded))</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-08-31T16:26:26Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>