AXY:Element Coordination/ATP

From SoftMC-Wiki
Revision as of 13:47, 11 November 2012 by Miborich (talk | contribs) (Maser/Slave relationship)
Jump to: navigation, search
Element Coordination Verification Procedure


Test Requirements

AMCS Firmware version: 4.11.? Application Framework: ?


Related Documentation

Functionality ATP

Data Creation

Test Case №:
1
Date:


Performed by:


HW Rev:
FW Rev:

Test Purpose

There are two kinds of Moving Frame (MF) objects in the aico.control system: axis-based and robot-based. Both of them are created in the same way as axes-based means using the command:

COMMON SHARED <mf name> as moving frame of <mf-type>

The difference between axes-based and robot-based moving frames is in the argument supplied to the MasterSource command. We should be able to supply <ROBOT>.SETPOINT and <ROBOT>.HERE values.

Test Equipment
  • aico.control
  • MIB StandAlone or Extend
  • Simulated or Real system


Test Procedure
  1. Load configuration with more than 2 robots (Robot1, Robot2)
  2. Create a Moving Frame Object MF
  3. Assign MF.MasterSource to Robot2.setpoint or Robot2.Here
  4. Assing MF to MasterFrame of the robot Robot1.MasterFrame = MF
  5. Activate tracking: Robot1.En =1 and Robot1.Slave = 5
Expected Values
  • No movement


Measured Values
Test Results
Comments








Type parameter

Test Case №:
2
Date:


Performed by:


HW Rev:
FW Rev:

Test Purpose

Check if it is in accordance to: TYPE

Test Equipment
  • aico.control
  • MIB StandAlone or Extend
  • Simulated or Real system


Test Procedure
  1. Load configuration with more than 2 robot
  2. Try different combinations of master & slave robots
  3. Master: ( position-only, orientation-only, position&orientation, 1,2,3 coordinates)
  4. Slave: ( position-only, orientation-only, position&orientation, 1,2,3 coordinates)
  5. Check if it behaves according to the table in: TYPE
Expected Values
  • No movement


Measured Values
Test Results
Comments



ObjectLoc parameter

Test Case №:
3
Date:


Performed by:


HW Rev:
FW Rev:

Test Purpose

Check if it is in accordance to: TYPE

Test Equipment
  • aico.control
  • MIB StandAlone or Extend
  • Simulated or Real system


Test Procedure
  1. Load configuration with more than 2 robot
  2. Try different combinations of master & slave robots
  3. Master: ( position-only, orientation-only, position&orientation, 1,2,3 coordinates)
  4. Slave: ( position-only, orientation-only, position&orientation, 1,2,3 coordinates)
  5. Check if it behaves according to the table in: TYPE
Expected Values
  • No movement


Measured Values
Test Results
Comments



Moving Frame Base parameter

Test Case №:
5
Date:


Performed by:


HW Rev:
FW Rev:

Test Purpose

Check if it is in accordance to: MF.BASE

Test Equipment
  • aico.control
  • MIB StandAlone or Extend
  • Simulated or Real system


Test Procedure
  1. Load configuration with more than 2 robot
Expected Values
  • No movement


Measured Values
Test Results
Comments

Maser/Slave relationship

Test Case №:
6
Date:


Performed by:


HW Rev:
FW Rev:

Test Purpose

Check if it is in accordance to: MF.BASE

Test Equipment
  • aico.control
  • MIB StandAlone or Extend
  • Simulated or Real system


Test Procedure
  1. Load configuration with more than 2 robot
Expected Values
  • No movement


Measured Values
Test Results
Comments

Point Type transformation

Test Case №:
4
Date:


Performed by:


HW Rev:
FW Rev:

Test Purpose

Check if it is in accordance to: MF.BASE

Test Equipment
  • aico.control
  • MIB StandAlone or Extend
  • Simulated or Real system


Test Procedure
  1. Load configuration with more than 2 robot
Expected Values
  • No movement


Measured Values
Test Results
Comments