HD68932: DMUKIN:WRONG CONSTRAINTS ARE CREATED IN DMU KINEMATICS WHICH CAN NOT BE CREATED IN ASSEMBLY DESIGN.

APAR status

• Closed as Permanent restriction.

Error description

• DMUKIN:WRONG CONSTRAINTS ARE CREATED IN
  DMU KINEMATICS WHICH CAN NOT BE CREATED
  IN ASSEMBLY DESIGN.
  .
  SCENARIO:
  1. Launch CATIA V5R17SP5,
  open "TEST.CATProduct" & goto Assembly W/b.
  2. Click "Coincidence Constraint" icon in
  Constraints toolbar, then select "Line.1" in "Part1"
  and "Line.1" in "Part2".
  3. A warning window opens : "Loop design between
  geometry and constraints"
  4. In the same way, a constraint can not be
  created between "Plane.1" in "Part1" and "Plane.2"
  in "Part2"
  5. Now Switch to "DMU Kinematics" w/b.
  6. Click "Fixed Part" icon to create a new
  mechanism, then select "Part.1" to fix it.
  7. Click "Prismatic Joint" icon in "Kinematics Joints"
  toolbar.
  8. A window "Joint Creation: Prismatic" opens.
  9. For Line 1, select Line of part 1 & for Line 2,
  select line of Part 2.
  10.Similarly select Plane 1 & Plane 2. Click
  on "Length Driven" option & click "OK"
  11.A information window opens "The Mechanism
  can be simulated", Click "OK".
  12.In specification tree, Constraints are created
  although they can not be created at step no. 2 & 4.
  13.Now move the Part 2 in such away that Plane 2
  is not parallel to the Plane 1.
  14.Click on "Update" icon.
  15.Part 2 does not come to its original position.
  16.Execute a simiration.A warning message
  appears to perform update.
  17.Click on "Yes". Then the simulation can be done
  with the partial constraints & Part 2 is not in its
  original position.
  .
  RESULT: The constraints which can not be created
  in ASSEMBLY DESIGN, can be created in DMU
  KINEMATICS.
  .
  EXPECTED RESULT: Wrong constraints should not
  be created on DMU Kinematics workbench as in
  Assembly Design workbench.
  

Local fix

Problem summary

• DMUKIN:WRONG CONSTRAINTS ARE CREATED IN
  DMU KINEMATICS WHICH CAN NOT BE CREATED
  IN ASSEMBLY DESIGN.
  .
  SCENARIO:
  1. Launch CATIA V5R17SP5,
  open "TEST.CATProduct" & goto Assembly W/b.
  2. Click "Coincidence Constraint" icon in
  Constraints toolbar, then select "Line.1" in "Part1"
  and "Line.1" in "Part2".
  3. A warning window opens : "Loop design between
  geometry and constraints"
  4. In the same way, a constraint can not be
  created between "Plane.1" in "Part1" and "Plane.2"
  in "Part2"
  5. Now Switch to "DMU Kinematics" w/b.
  6. Click "Fixed Part" icon to create a new
  mechanism, then select "Part.1" to fix it.
  7. Click "Prismatic Joint" icon in "Kinematics Joints"
  toolbar.
  8. A window "Joint Creation: Prismatic" opens.
  9. For Line 1, select Line of part 1 & for Line 2,
  select line of Part 2.
  10.Similarly select Plane 1 & Plane 2. Click
  on "Length Driven" option & click "OK"
  11.A information window opens "The Mechanism
  can be simulated", Click "OK".
  12.In specification tree, Constraints are created
  although they can not be created at step no. 2 & 4.
  13.Now move the Part 2 in such away that Plane 2
  is not parallel to the Plane 1.
  14.Click on "Update" icon.
  15.Part 2 does not come to its original position.
  16.Execute a simiration.A warning message
  appears to perform update.
  17.Click on "Yes". Then the simulation can be done
  with the partial constraints & Part 2 is not in its
  original position.
  .
  RESULT: The constraints which can not be created
  in ASSEMBLY DESIGN, can be created in DMU
  KINEMATICS.
  .
  EXPECTED RESULT: Wrong constraints should not
  be created on DMU Kinematics workbench as in
  Assembly Design workbench.
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN Realistic Simulation
  Additional Closure Information:
  THIS PROBLEM IS PERMANENT RESTRICTION IN
  CATIA.
  Incident Diagnosis
  DMUKIN:WRONG CONSTRAINTS ARE CREATED IN
  DMU KINEMATICS WHICH CAN NOT BE CREATED
  IN ASSEMBLY DESIGN.
  .
  Restriction Explanation
  This is not a defect but a methodology problem,
  plesae refer to attached ppt.
  .
  By-Pass
  build the assembly structure in a different way
  (skeleton methodology). This configuration is not
  supported by KIN application.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels