<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-02-02T20:54:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-02-02T20:54:13Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Reopening to set In TestRail flag to true</Comment>
    <StatusString>Reopened</StatusString>
    <TimeStamp>2024-02-02T20:54:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-01-16T21:35:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-01-16T21:35:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Reopened</StatusString>
    <TimeStamp>2024-01-16T21:35:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-01-16T21:07:35Z</TimeStamp>
    <ReleaseNote>Now prevents arming TSR AIR with wakeup with motion and a level trigger less than or equal to 5g</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified with DataPRO v4.2.322, 4.0.1119
 
Tested:
 
 
Discover and query TSR AIR
 
In system settings enable level triggers and change min percentage to 0.0005 
 
Create a test setup with this TSR AIR and enable wake with motion, set a level trigger to 0.5g
 
Click Save</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-01-09T23:54:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-09T22:54:03Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0@50043</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-01-09T22:39:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>re-activated to apply fix to 4.0 per CPB</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2024-01-09T18:54:19Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.2@50036
 
now shows this warning
 
 
to test just create a TSR AIR test with wake up on motion checked;
 
and a level trigger of 5G or less
 
you should be shown the above error and prevented from running the test (although it will let you save it)</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-01-09T01:04:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>here's the new warning:</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-09T01:00:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-09T00:41:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>here's where we set the level trigger levels;
 
2024-01-05 14:54:39.100 -&gt;  Attribute - SetArmAttribute [00018489], TA0073, local: 192.168.1.16:59897, Remote: 192.168.6.73:8301 Key: LevelTriggerGreaterThanLimit, DataType: Float32Star, Length: 80, Overwrite: True, Value: (0, 0, 0, 0.5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0)
 
index 4,5,6 (.5 in above example) is the BMI sensor which must be &gt; 5g to work with wake-up motion.
 
according to EF the LessThanLimit contains the actual limits that the firmware uses for the sensors.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-08T23:42:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>taking</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-08T23:33:59Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-05T23:39:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-05T23:38:50Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-05T23:38:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>According to Eric the sensor can only handle either level trigger below 5g or wake with motion. Not both. 
 
This is the primary thing to correct in the issue I think, don't allow this configuration to be run since we know it's not supported.
 
 
 
[4:22 PM] Eric Fizer
 
right, that's the checkbox
 
[4:24 PM] Eric Fizer
 
have to prevent wake up with motion when using lvl trigger less than or equal to 5g</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-05T23:37:54Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-05T23:03:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-01-05T23:02:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>In DataPRO, users are currently able to create a test with TSR AIR configured with a level trigger below 5g and wake-up motion enabled. However, upon reaching the arm step and attempting to arm the test, a "Failed to Arm" message is encountered. The expected behavior should be a prevention of test creation with these conflicting settings. Tested as admin user and TSR AIR user
 
System Settings:
 
Enable level-trigger ✔
 
Level Trigger max percentage = 0.75
 
Level Trigger min percentage = 0.0005
 
Steps to Reproduce:
 
Open DataPRO and navigate to test creation.
 Configure TSR AIR with a level trigger set below 5g and enable wake-up motion.
 Proceed to the arm step and attempt to arm the test.
 
Expected Behavior:
 
DataPRO should prevent the creation of a test when TSR AIR is configured with a level trigger below 5g and wake-up motion is enabled.
 Users should be alerted to the incompatible settings and guided to make the necessary adjustments.
 

 Actual Behavior:
 A test with conflicting settings can be created, but the arming process fails with a "Failed to Arm" message.
 
Logs:
 2024-01-05 14:54:52.758 !!  An exception of type: System.Exception occurred Module: ICommand.dll, Name: InternalSyncExecuteMessage: TA0073 was executing  DTS.DASLib.Command.SLICE.Arm   and reported SyncExecute: response.Status = StatusArmUnimplementedArmMode for sequence 18590\18590.  Please report this information to Technical Support StackTrace:    at DTS.DASLib.Command.AbstractCommandBase.InternalSyncExecute() StackTrace:    at DTS.DASLib.Command.AbstractCommandBase.SyncExecute()    at DTS.DASLib.Service.Slice`1.AsyncPreparedArm(Object asyncInfo)</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2024-01-05T23:02:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>