.

Release Note
MPI Library Version 04.04.02

Release Type
MPI Version
Release Date
Production Release
04.04.02
18Nov2016
Production Release
04.04.01
18Nov2016
Production Release
04.04.00
15Apr2016

 

  Table of Contents
    Notes
      System Requirements
Software Installation Instructions
Important Things to Know - This section highlights the most important changes in this release.
     
    New Features
     

Version 04.04.00
    64-bit applications are now supported

    General Changes
      Version 04.04.00
     Firmware Pointer Changed to uint32_t
     MPI Function Changes
     Dual Compare

    Fixed Bugs
     

Version 04.04.02
    Incorrect MoScope HEX Format Export Data
    Firmware Address Size Check for MPI 64bit
    mpiUserLimitConfigSet/Get()
    Unexpected NearTarget (Coarse) Status
    Fixed Motor Gear Problem
    ESTOP-ABORT Does Not Work on Cordinated Motion
    MPIRecorderRecordTypeAXIS Bug

Version 04.04.01
    mpiMapPtrToSymbol() Function Does Not Work With MPICapture.Data.State address

Version 04.04.00
    <none>

    Open Issues
     

Existing Bugs
    <none>

Limitations
    Motion Console and Motion Scope Require Administer User Permissions
    Simserver
    MechaWare

         

New Features

Version 04.04.00

64-bit applications are now supported

General Changes

Version 04.04.00

  Firmware Pointer Changed to uint32_t
    Reference Number:
    Type: Change Feature
    MPI Version: 04.04.00
   

Description:

The new firmware pointer ‘_MFWPTR_ (type)’ clearly distinguishes between 32-bit firmware pointer and 32-bit or 64-bit host pointer.

It is defined in MFPTR.H. MFWPTR.H is an additional header file to access 32-bit firmware from a 64-bit host. And the 64-bit host handles the 32-bit firmware pointer as 'uint32_t'. No changes have been made to the 32-bit host.

Related definitions:

MPI64: Identifies whether running a 64-bit OS or 32-bit OS. If it has been defined, it handles pointer of the firmware as ‘uint32_t’.

MPI_PLATFORM_WIN64: The identifier for Microsoft Windows7 64 bit.

 

  MPI Function Changes
    Reference Number:
    Type: Change Feature
    MPI Version: 04.04.00
   

Description:

A new argument '_MFWPTR_(type)' was added to support 32-bit firmware pointers on a 64-bit host. It is found in the following functions:

For more information see the Important Things to Know section.

 

  Dual Compare
    Reference Number:
    Type: Change Feature
    MPI Version: 04.04.00
   

Description:

The MPICompareConfig structure now includes an additional member ‘engineNumber’ to support multiple compare engines for a given motor. The default value should be set to ‘0’.

At this time, the AKD drive supports engineNumber 0 and 1 (aka dual compare).

Fixed Bugs

Version 04.04.02

  Incorrect MoScope HEX Format Export Data
    Reference Number: MT 1522
    Type: Fixed Bug
    MPI Version: 04.04.02
   

Problem:

When data is exported as hex to file, the values are bad.

   

Cause:

Eg.: When controller data was 0x80000001, exported data was 0x80000000.

   

Fix/Solution:

Also: Hex format display wasn't implemented correctly.


  Firmware Address Size Check for MPI 64bit
    Reference Number: MPI 2732
    Type: Fixed Bug
    MPI Version: 04.04.02
   

Problem:

This feature checks and validates the size of firmware address for 64-bit MPI builds.

The size of the firmware address is 32-bit. But if a customer made a mistake and set the wrong software build option, the firmware address becomes a 64-bit value.

This feature is introduced to catch this error. However, it will be 64-bit when customer sets wrong software build option.

   

Cause:

NA

   

Fix/Solution:

Check firmware address size when application call the mpiControlCreate().
If it is bad, it will return "Control: Firmware address size mismatch.".

Call yjr mpiControlCreate()


  mpiUserLimitConfigSet/Get()
    Reference Number: MPI 2730
    Type: Fixed Bug
    MPI Version: 04.04.02
   

Problem:

If the application uses the 'Capture State' address by MPIUserLimitConditionTypeCUSTOM and sets configuration using mpiUserLimitConfigSet, then, when calling mpiUserLimitConfigGet(), the type is returned as MPIUserLimitConditionTypeCAPTURE_STATE.

   

Cause:

mpiUserLimitConfigGet().

It is determined only by the address that set the condition type. Additionally, the custom setting is changed to the simple setting of each condition type.

   

Fix/Solution:

The condition type is stored in a firmware field and retrieved when mpiUserLimitConfigGet is called.

The types that are set are read properly in the get functions.


  Unexpected NearTarget (Coarse) Status
    Reference Number: MPI 2729
    Type: Fixed Bug
    MPI Version: 04.04.02
   

Problem:

For AKD & S200 drives, if the user generates an Abort action (Disable action), the 'Near Target' status will be TRUE.

   

Cause:

The motor status data was incorrectly getting reflected in the axis status and causing a spurious status.

   

Fix/Solution:

When motion is aborted, the wrong bit from motor status is not copied to the axis status.


  Fixed Motor Gear Problem
    Reference Number: MPI 2728
    Type: Fixed Bug
    MPI Version: 04.04.02
   

Problem:

In a certain situations, the motor gearing function did not work well.Example is when using a high value for the resolution and spinning the motor shaft at high speed.

   

Cause:

This problem was in unit size of firmware calculation.

   

Fix/Solution:

The calculation was fixed and the motor gearing works as expected.


  ESTOP-ABORT Does Not Work On Cordinated Motion
    Reference Number: MPI 2726
    Type: Fixed Bug
    MPI Version: 04.04.02
   

Problem:

Axes are assigned to the following:

1. MS - Axis map
MS#0: Axis#0
MS#1: Axis#1
MS#3: Axis#0 + Axis#1

2. Motion start
MS#0: start.

3. EStopAbort
MS#2: EStopAbort.

4. Problem
Axis#0 abort soon.

   

Cause:

This problem occurs when two or more axes are assigned to a motion supervisor (MS). The axis staus of the 2 or more axes were not combined properly.

   

Fix/Solution:

When multiple axes are being assigned to a motion supervisor, each axis staus is properly combined to set the motion supervisor status.

It works correctly to abort all the axes at the right time.


  MPIRecorderRecordTypeAXIS Bug
    Reference Number: MPI 2581
    Type: Fixed Bug
    MPI Version: 04.04.02
   

Problem:

When using MPIRecorderRecordTypeAXIS in mpiRecorderRecordConfig(), the
DAC output value was always 0.

   

Cause:

DAC output was assigned filter output and MechaWare firmware does not have filter.

   

Fix/Solution:

Check Mechaware or Standard firmware. If it is Mechaware firmware, DAC output is assigned for Motor commutation input.

Version 04.04.01

  mpiMapPtrToSymbol() Function Does Not Work With MPICapture.Data.State addresss
    Reference Number: MPI 2720
    Type: Fixed Bug
    MPI Version: 04.04.01
   

Problem:

Map: symbol not found is returned when setting the map pointer as MPICapture.Data.State address and calling the mpiMapPtrToSymbol() function.

   

Cause:

Improper coding of the mpiMapPtrToSymbol() function.

   

Fix/Solution:

The mpiMapPtrToSymbol() function was corrected.

Version 04.04.00

<none>

Open Issues

Existing Bugs

<none>

Limitations

  Motion Console and Motion Scope Require Administer User Permissions
    Reference Number: N/A
    Type: Limitation
    MPI Version: 04.04.xx
   

Description:

If installed in the default installation directory (C:\Program files), Motion Console and Motion Scope require administrator privileges to run. This is due to increased security measures by Microsoft in Windows 7 and above. Installing to an alternate directory will circumvent this requirement.

 

  SimServer Still Under Development
    Reference Number: N/A
    Type: Limitation
    MPI Version: 04.04.xx
   

Description:

At the time of the release, the development of SimServer had not been completed. This feature is available as a standalone package and is not included in the MPI distributables.

 

  MechaWare Still Under Development for 64-bit Applications
    Reference Number: N/A
    Type: Limitation
    MPI Version: 04.04.xx
   

Description:

At the time of the release, the development of MechaWare for 64-bit applications had not been completed. This feature is released as a standalone package and is not included in the MPI distributables. MechaWare is planned to be completed and supported in future releases.

Mechaware is available for 32-bit applications in the 04.03 release.

 

 

 

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