APAR status
Closed as Permanent restriction.
Error description
SCENARIO: When the mesh is activated/Updated after performing Remove Mesh, the mesh is not recreated and error message appear. Error Message Impossible to mesh connection Mesh Part : Contact Connection Mesh.1 Projection is impossible. Possible causes: 1. Connection is designed to link 2 close geometries/meshes. - projection tolerance = 1.41421mm as result of internal computation based on meshes to connect. - Reduce distance between geometries/meshes to get a connection mesh 2. Projection sources are projection targets 3. No source to project. PROBLEM: The mesh is not recreated when the mesh is activated or Updated after performing Remove Mesh. EXPECTED RESULT: The mesh which is removed by Remove Mesh function, should be retrieved normally after Update mesh or performing Activate / Deactivate on mesh.
Local fix
empty
Problem summary
SCENARIO: When the mesh is activated/Updated after performing Remove Mesh, the mesh is not recreated and error message appear. Error Message Impossible to mesh connection Mesh Part : Contact Connection Mesh.1 Projection is impossible. Possible causes: 1. Connection is designed to link 2 close geometries/meshes. - projection tolerance = 1.41421mm as result of internal computation based on meshes to connect. - Reduce distance between geometries/meshes to get a connection mesh 2. Projection sources are projection targets 3. No source to project. PROBLEM: The mesh is not recreated when the mesh is activated or Updated after performing Remove Mesh. EXPECTED RESULT: The mesh which is removed by Remove Mesh function, should be retrieved normally after Update mesh or performing Activate / Deactivate on mesh.
Problem conclusion
THIS PROBLEM IS PERMANENT RESTRICTION IN CATIA Additional Closure Information: . INCIDENT DIAGNOSIS: The contact connection mesh cannot be updated successfully after performing Remove Mesh. . RESTRICTION EXPLANATION: In order to create a contact connection mesh, it has to be possible to project a node from one surface to other, meaning that the two surfaces should face each other. However the BR data (created on R18 level) contains two faces that do not face each other. i.e. a Node from surface 1 cannot be projected onto the surface 2 with normal projection direction. On R18 level, it was possible to define contact connection even though there is no overlap between the two surfaces. However such result is physically not relevant. Therefore a new development has been done so that operator does not allow user to generate such FE model. In addition, whenever user updates such contact connection mesh (faces having no overlap between them) an appropriate error message is thrown to educate the user about the situation. Please refer QA00000005264 to know more about the contact connection mesh. . By-pass: Move the geometry so that faces will overlap i.e. a node from one surface can be projected on to other.
Temporary fix
Comments
APAR Information
APAR number
HE02153
Reported component name
CATIA V5 WIN 64
Reported component ID
569165000
Reported release
520
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-26
Closed date
2010-12-03
Last modified date
2010-12-03
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
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"520","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
03 December 2010