IBM Support

HC42908: PLANES CREATED BY CATIA CAN NOT BE TAKEN INTO ACCOUNT IN APPROACH OR RETRACT MACROS AS APPROACH OR RETRACT PLANES.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MFGPROG
    Cst level:420-1
    Here is the scenario of the problem:
    In an ADTSRC file for the simple contouring and finish there are
    an Approach and a Retract macros specified.
    These macros simply approach /retract form a plane down/up the
    tool axis. They are standard macros.
    When applying the ADTSRC file to a machining operation, Catia
    creates a plane which then used within the macros.
    Now to ensuure a clearance, if you create a plane at for example
    z=200 and name it 'CLEAR1',you have to specify it into ADTSRC
    According to the user's guide the file should be built as it
    follows:
    <macro approach_macro     = user.mcatstd.appaxis
                    retract_macro            = user.mcatstd.retaxis
                    approach_plane      = **************
                    retract_plane             = **************>
    If you replace********by the plane name 'CLEAR1' or type a
    coordinate z=200. But on doing so the machining operation is not
    created and you get an error message of unknown keyword command.
    The possible By-Pass is to define the 'CLEAR1'plane as safety
    plane of the PO while editing the PO. Then in the ADTSRC file
    you add two lines defining the plane:
    ...
       APPROACH_PLANE = %PART_OP.MFG_SAFE_PLANE
       RETRACT_PLANE = %PART_OP.MFG_SAFE_PLANE
    ...
    Doing so the plane is taken into account and you can check it
    replaying the tool motion.
    

Local fix

Problem summary

  •  INCIDENT DIAGNOSIS:
    Impossible to use CATIA Ident to valuate attributes inside
    the ADT files
    
     TECHNICAL EXPLANATION FOR THE CORRECTION:
    This was not implemented
    
     ANSWER AND POSSIBLE BY-PASS:
    How to use this functionality?
    You have to put the Catia identifier as a valuation of an
    attribute or a keyword.
       Example:
         <MACRO  APPROACH_MACRO   = USER.MCATUSR.APPCIDIP
                 APPROACH_RADIUS  = %TOOL.MFG_NOMINAL_DIAM*0.4
                 APPROACH_PLANE   = *PLN1
                 APPROACH_DIST    = -%TOOL.MFG_NOMINAL_DIAM*0.28
    3>
    
    This is available for all attributes or keywords referencing
     a Catia element.
    

Problem conclusion

  • THIS PROBLEM WILL BE FIXED ON
      CATIA VERSION 4 RELEASE 2.1 REFRESH 1 GA level  (FREL421R1)
    

Temporary fix

Comments

APAR Information

  • APAR number

    HC42908

  • Reported component name

    CATIA FOR SUN

  • Reported component ID

    562640000

  • Reported release

    G20

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1999-02-11

  • Closed date

    1999-03-05

  • Last modified date

    1999-06-02

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

    HC42905

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

Modules/Macros

  •    FILE
    

Fix information

  • Fixed component name

    CATIA FOR SUN

  • Fixed component ID

    562640000

Applicable component levels

  • RG20 PSN

       UP

  • RH20 PSN

       UP

  • R421 PSN UB92113

       UP99/06/02 I 1000

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSLJ45","label":"CATIA-CADAM"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"G20","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
02 June 1999