.

Release Note
Motion Scope

Motion Scope Version
MPI Release
Release Date
01.21.41
20Oct2005
01.21.39
03.03.00
Production Release
29July2005
01.21.24
03.02.00
Production Release
16Dec2004
01.21.24
20Sept2004
01.21.23
03.01.00
Production Release
30Jul2004
01.21.11
20031222
Production Release
22Dec2003

  Table of Contents
    Version
     

01.21.41
01.21.40
01.21.38
01.21.31
01.21.30
01.21.26
01.21.23
01.21.20
01.21.18
01.21.17
01.21.16
01.21.15
01.21.14
01.21.13
01.21.12


01.21.41

Discrepency Report

  Title: Motion Scope crashes during display configuration changes
  Ref #: 1227
 

Description:
The problems (described in the email below) can be reproduced by:

  1. Use Motion Console to command point-to-point motion with repeat.
  2. Configure Motion Scope for:
    • A large MaxBuf. Failures occur with 50000, 100000, 200000. Larger buffers seem to make the problem occur more often.
    • Select 8 or more traces. Failures occur with 4, 6, 8 traces. More traces seem to make the problem occur more often.
    • Set the trigger conditions:
      Start Condition = Motion Start,
      End Condition = Buffer Full
  3. Arm with Repeat.
  4. While the data is collected and the display is updating:
    • Open the Display window.
    • Select "show all samples" and deselect "Connect points," then press OK.
    • Open the Display window.
    • Select "Average samples" and select "Connect points," then press OK. Go to the first bullet.

Within a few tries, the display will refresh from two locations simultaneously (Failure 3). Within 10~50 tries, a memory access violation (Failure 2) or a "recorder already started" message (Failure 1) will occur.

After Motion Scope is shut down and re-started, the data recorder is stuck. Motion Scope/MPI thinks that rRecorder 0 is still running, so the user can't create a second recorder. The only way to recover is with a controller reset OR to clear the recorderInUse flag in the controller's memory.

Failure 1
Motion Scope claims that recorder 0 is being used by some other process when Motion Scope was already sucessfully using recorder 0. No other instance of Motion Scope or any recorder program was being run at the time. This failure is captured in "MoScope Error.zip"

Failure 2
Motion Scope causes a memory access violation error when changing display settings from "average points" to "show all points" (or vice versa) and unselecting "connect points" and then hitting the OK button. The failure occurs within MS_XMP_NT.EXE.

Failure 3
Motion Scope redraws previous trace points with new data. Choose a large buffer (something like 200000 ms), choose 8+ traces to record, choose "display all points" display option.

 

01.21.40

Feature Enhancement

  Title: Set Pane Display defaults to "connect" and "average"
  Ref #: 1239
 

Description:
The defaults for the Pane Display are now "connect" and "average."

Discrepency Report

  Title: FFT plots not diplayed correctly in Motion Scope
  Ref #: 1224
 

Description:
When displaying a data set of type FFT, Motion Scope does not connect the dots (it only plots dots, not the lines), regardless of display type. This can be reproduced with File -> Import FFT and opening ImportExampleBode1.fft (located in the moscopesrc dir in the Motion Scope tree).

 

01.21.38

Discrepency Report

  Title: Incorrect scaling for FFT X-axis: "points" and "all samples"
  Ref #: 1225
 

Description:
Motion Scope has incorrect scaling for FFT X-axis: "points" and "all samples"

 

01.21.31

Feature Enhancement

  Title: Users need access to RecorderInUseMask
  Ref #: 1166
 

Description:
User can now select and reuse existing inactive Recorders upon Pane creation.

 

01.21.30

Feature Enhancement

  Title: Motion Scope Traces for I/O
  Ref #: 1095
 

Description:
Traces have been added for digital and analog inputs/outputs.
There are I/O from several sources:
    - Motor
    - Node
    - Controller
    - CAN

 

01.21.26

Feature Enhancement

  Title: Add drive monitor fields to default traces
  Ref #: 968
 

Description:
In earlier versions, in order to add a drive monitor field, a customer had to use VM3 and find out what address to use. Three drive monitor fields have been added in the list of selectable common traces.

Discrepency Report

  Title: Motion Scope is crippled by recorder triggers
  Ref #: 1147
 

Description:
Motion Scope is crippled by recorder triggers.

 

01.21.23

Discrepency Report

  Title: Motion Scope does not release MPI Recorder memory upon exit
  Ref #: 1089
 

Description:
Motion Scope, in the Pane shutdown procedure, now stops the Recorder before deleting it.
As a result, MPI memory is released.

 

01.21.20

Discrepency Report

  Title: Motion Scope hangs when opening a file multiple times
  Ref #: 769
 

Description:
Motion Scope will sometimes hang when opening a .PAN file. This can be recreated by opening a .PAN file and then closing the pane. Repeat until the hang occurs--usually after the 4th or 5th time.

 

01.21.18

Discrepency Report

  Title: Motion Scope data not aligned with scale lines
  Ref #: 713
 

Description:
When collecting/displaying data, sometimes the data points do not align properly with the scale markers on the X axis. This is easiest to see by turning on the "sample band" in the Pane Display configuration and Displaying in Units of Samples. The problem can be corrected by forcing a re-draw of the data: sliding the data on/off the screen, minimizing/maximizing, or zooming in/out.

 

01.21.17

Minor Improvement

  Title: Remove Motion Scope restriction of max one Pane per Controller
  Ref #: 1062
 

Description:
The restriction of max one Pane per Controller has been removed, so that Traces from the same Controller may be displayed independently in different window Panes.

 

01.21.16

Feature Enhancement

  Title: Display coordinates of cursor on the status bar
  Ref #: 471
 

Description:
Display the current X and Y coordinates of the cursor in the pane on the status bar. This would make it easier to select a very accurate zoom area.In addition, Status Bar will be turned on if this display is selected (via the Pane Display dialog). Status Bar viewing is saved in the Initialization file.

 

01.21.15

Discrepency Report

  Title: "Save Pane" Corrupts timebase.
  Ref #: 896
 

Description:
The following problem was reported using MPI 20021219 and has been fixed in Motion Scope version 1.21.15:

  1. Open Motion Scope, and configure it to record a measured position, then capture some data. See the first screen shot in the attached file.
  2. Save the Motion Scope pane using File -> Save As.
  3. Close the view using File -> Close.
  4. Load the previously saved pane using File -> Open.

The time axis is now the same in both cases, as would be expected.

 

01.21.14

Discrepency Report

  Title: Motion Scope crashes when no printer
  Ref #: 1060
 

Description:
Motion Scope will report a "printer error" if no printer is configured when asked to print.

 

01.21.13

Discrepency Report

  Title: Motion Scope hangs when zooming upon read-only pane files
  Ref #: 1016
 

Description:


Change Request

  Title: No Recorders Available
  Ref #: 1018
 

Description:
Upon Pane creation, if the MPI thinks there are no more Recorders available, Motion Scope will pop up a dialog box asking the user for a new Recorder number to use, and the number of records to allocate for the new Recorder. A list of current recorders and records used is shown in the dialog, as well as the available memory and records for use by the new Recorder. Upon Pane destruction, the newly allocated Recorder will be deleted from the Mpi Configuration.

 

01.21.12

Discrepency Report

  Title: Strange gaps in data when using Go/Stop buttons
  Ref #: 1017
 

Description:
The MPI data Recorder is re-Configed everytime the Motion Scope Go/Arm button is pressed, effectively clearing the MPI Recorder internal data buffer, which had been causing "strange gaps" to appear in Motion Scope data.


 

 

 

       Legal Notice  |  Tech Email  |  Feedback
      
Copyright ©
2001-2010 Motion Engineering