Release Note
Motion Scope

Description:
"Active" means that the Recorder is currently recording data. The preceding sentence has been added to the "Choose Another Recorder" dialog box. More explicitly, a Recorder is considered "InActive" either if the MPIRecorderStatus.enabled bit is not set (as returned by a call to meiControlRecorderStatus) or if both the MPIRecorderStatus.enabled and MPIRecorderStatus.full bits are set. The latter case is interpreted as the Recorder as having been "abandoned" as it is full of data that has not been retrieved.

Description:
The AtTarget, AtVelocity, InFine, and InCoarse labels were being displayed as part of the Motion Supervisor object and not the Axis object. Status bits are now read from Axis.Status rather than from MS.Status. The traces dialog box now correctly lists these bits as part of the Axis object. The change applies to AtTarget, AtVelocity, Done, InFinePosition, and InCoursePosition.

Description:
If you change the recorder period outside of Motion Scope, then try to use Motion Scope again, its period is the same as the previous recorder used, not zero. Motion Scope does not set its own recorder period to 0. Recorder period is now explicitly set by Motion Scope to zero before any recording takes place.

Description:
If you select the group name in the Group highlighted traces window and click the Modify button, no action will occur.

This feature is actually working as intended. When the Modify button is pressed, the currently highlighted Traces will be associated with the highlighted Group. Before the Modify button is pressed, the user can select or de-select individual Traces using the Control and/or Shift keys. If no Traces have been added or removed from the Group after selecting a Group, then pressing the Modify button will appear to do nothing. In other words, the Modify button sets the association of a set of Traces with a Group. If no changes have been made in the membership set of Traces, pressing the Modify button will do nothing. 

Description:
In Motion Scope, even when a Trace was set to not autoscale, it would automatically revert all the traces into an autoscale mode when the Stop button was pressed after running a plot. It should not autoscale when the Stop button is pressed. This problem has been fixed. Now, AutoScale does not occur as a result of pressing the Stop button.

Description:
When the sample rate on the XMP is changed, Motion Scope is not aware of it. Motion Scope checks the XMP sample rate at various points in its operation and updates the X-axis scale to reflect any changes. This will change the appearance only if the X-axis units selected is in milliseconds (i.e., not in samples). Motion Scope now checks the XMP sample rate when a new Pane is opened, when the Pane Mode dialog has been used, whenever Traces are reconfigured, and whenever the Arm/Go button is pressed. This problem was fixed.