SIE file “ragged edge cleanup” on test run stops

Overview: The XR systems (eDAQXR, eDAQXR-Lite, CX23-R) are designed to enforce “ragged edge cleanup” whenever possible when SIE test runs are stopped. The term “ragged edge cleanup” means that the last data sample for all eligible channels will have the same timestamp, which means that the data for all channels will span the same period.

Scope: In general, “ragged edge cleanup” is applicable for all sample rate domains (Decimal, Binary, and Classic) and for all test run modes (Normal, Cyclic, and Remote control). It is applicable for Mode 1 networked systems as well as standalone systems.

  • It is applicable only to channels that use the Collect storage mode. It is not applicable to any channels defined in any DataMode.
  • It is not applicable for Mode 2 networked systems.

Exceptions: In any test scenario where “ragged edge cleanup” is applicable, if a stop time cannot be found in 5 seconds after the search for a test stop with no “ragged edges”, the test run will be stopped with “ragged edges”. There is no GUI notification of this; however, there is a FORCED STOP Log file message generated. Note that this is not considered an error, and as such, the red LED is not turned on. An example message follows.

test stopping "test_name" now = 2019-11-08T19:13:09.014694929 FORCED STOP

Limitations:

  • It is not applicable to channels with sample rates less than 1 S/s. If the sample rate of any channel is below this, it may or may not have a ragged edge relative to the channels with samples rates greater than or equal to 1 S/s.
  • It is not applicable if any Time Base Shifter Computed channel is used in the test.
  • It is not applicable if the Run Stopper Computed channel is used to stop the test run.
  • It is applicable if an Up Sampler or a Down Sampler Computed channel is used in the test, and the sample rate for the computed channel is equal to one of the sample rates available for input channels (e.g., 100, 200, 500, etc. for the Decimal domain). It may be applicable for other sample rates (e.g., 250, 400, 1250, etc.). However, for “unusual” sample rates like 100/3 = 3.3333333 S/s, a FORCED STOP will result.
  • It is not applicable when a test is stopped due to a power supply loss; however, it is applicable if power to the system is switched off (e.g., using the front panel switch).
  • It is not applicable when a test is stopped on an error reset, or when a test is stopped on a user initiated software reset.

NOTE
There may be other unknown test scenarios where the system will attempt to find a test stop time that results in no “ragged edges”, but fails to do so within the 5 second time out period for one reason or another. If this occurs, a FORCED STOP Log file message will be generated.