| Error |
Dominio(Entorno) |
Sintoma
(Visible para el usuario) |
Problemas Técnicos |
Operación que ejecuta CATDUA |
Después de ejecutar
CATDUA (Visible para el usuario) |
| Hoja anterior |
|
|
| DET_0 (3) (*) |
Drafting |
Document too
big or/and extra links in Edit/Links. |
2D component
not used anymore. |
Deletion of
the unused 2D component. |
Document is
the same but smaller. |
| DET_1 (3) (*) |
Drafting |
Document
contains unusable elements and/or extra links. |
2D component
non typed through interface. They cannot be used anymore. |
Deletion of
the unused 2D component. |
Document is
the same but smaller. Extra links can disappear |
| DET_2 (2) (*) |
Drafting |
2D Component
instance has its reference outside its document. |
Cut Copy
Paste problems during V5R11 and V5R12. |
The 2D
component reference is created inside the same document and replace the
wrong one. |
The document
is self-content again. No problem if external document disappears. |
| DET_3 (1) |
Drafting |
2D Component
instance has too big or too small scale. |
Cut Copy
Paste problems during V5R11 and V5R12. |
Deletion of
the scale. |
The view that
was containing such object recover his frame. |
| DET_4 (2) (*) |
Drafting |
After
exploding all 2D component instances (i.e. dittos) in a CATDrawing,
Edit/Links shows residual external links to catalog. |
Redundant local reference exists in the model. They cannot be deleted
by user.
|
Instances of
the redundant local reference are redirected to the good one and
redundant local reference is deleted. |
Document size decrease. No more ghost link after exploding dittos.
|
| DET_6 (1) |
Drafting |
Unpredictable behavior when using a drafting detail/ditto.
|
There is 2D
component instance that is not structurally valid and must be discarded. |
The invalid
2D component instance is deleted. |
2D Component instance can be exploded without error or crash.
|
| DET_7 (2) (*) |
Drafting |
Open a CATDrawing document, a warning with the following error
message appears: "The files in the following list could not be found or
contain the wrong information for the active document", but a document
mentioned in the list does not appear when using File/Desk or Edit/links
command. The user cannot correct the ghost link.
|
During the explode operation of a 2DComponent instance, some
instance/reference links were kept between some elements in the
2DComponent and the document where the 2DComponent was originally
created.
|
The fixing action consists in unplugging the View sub-components with
ghost links from their "ghost" reference and to plug them again to their
startups in current document.
|
No more warning pop-up when opening the document, and no more
GhostLink in SendTo command.
|
| DOB_0 (1) (*) |
Drafting |
A CATDrawing containing isolated views has still some links to 3D
parts/product. This is detected when using File/SendTo.
|
The breakout
operator in Generative Drafting isolated views maintains some links to
3D documents, despite the fact that the view is isolated and no link
should exist. |
The CATDUA modifies the breakout operator and deletes the links to 3D
documents.
|
No link to 3D
will exist anymore on this operator - File/SendTo will not detect these
links. |
| DOC_1 (2) |
SpecsModeler |
A pointed
document can not be loaded. |
The type of
the pointed document is not specified in the symbolic link. |
The type is
set according to the extension of the pointed document. |
Pointed
document can be loaded. |
| DOC_3 (2) |
SpecsModeler |
No visibility
(can lead to the lost of a link until V5R10). |
Internal
counter to determine whether a link to a document has to be kept not
correctly valuated. |
Set the
counter to the correct value. |
No
visibility. |
| DOC_4 (3) |
SpecsModeler |
Unused
external links shown in Edit Links. |
Internal
counter not correctly valuated. |
Set the
counter to the correct value. |
In Edit
Links, there are no more unused external links. |
| DOC_5 (2) |
SpecsModeler |
Objects
located in a pointed documents can not be accessed. |
A link to a
container in a pointed document has been lost. |
The link to
the container is rebuilt. |
Objects of
the pointed document are accessible. |
| DOC_6 (3) |
SpecsModeler |
A document
cannot be stored in ENOVIAVPM. |
Applicative
container with no stream in the document. |
Creation of
an empty stream for this applicative container. |
The document
can be stored in ENOVIAVPM. |
| DOC_11 (3) (*) |
SpecsModeler |
SendTo on a
CATPart shows a GhostLink to an useless CATPart. |
The Ref-Ref
links repository contains no Input or Inputs that are no more pointed,
so the link to the other CATPart owned by the repository is useless. |
The
meaningless repository is deleted. |
SendTo does
not show a link to a useless CATPart. |
| DOC_7 (2) (*) |
Product
Structure |
When working
in context of corrupted CATProduct, changes made to a pointed
sub-product or part are not saved. Undo is not working on this
sub-product or part. |
Need to save
information is corrupted. |
Establishes
correct Need to save information in the link.. |
After close
and reopen of data, modification will be taken into account. |
| DOC_8 (3) |
Product
Structure |
Bad
performance when opening a document. |
When link
counters in the index table of inter-document, it goes down to 0 (link
no more seen by the user), ObjectModeler does not delete this link in
Session, only CATDUA is authorized to perform this operation. |
The link
that does not appear to end-user is deleted in table of inter-document
links, the table is just compacted. |
Better
performance at open. |
| DOC_9 (3) |
Product
Structure |
Update of a
CATPart cannot be completed if there are more than one Ref-Ref link
federator in the Ref-Ref link container. |
Only one
object should federate the different pointed documents by Ref-Ref link
for a given CATPart. If there is more than one, Ref-Ref links cannot be
solved. |
Data
contained in all federators are put into one federator and empty
federators are deleted. |
Update is now
possible. |
| DOP_0 (1) (*) |
Generative
Drafting |
A CATDrawing
containing isolated views has still some links to 3D parts/product. This
is detected when using File/SendTo. |
The
projection operator in Generative Drafting isolated views maintains some
links to 3D documents, despite the fact that the view is isolated and no
link should exist. |
The CATDUA
modifies the projection operator and deletes the links to 3D documents. |
No link to
3D will exist anymore on this operator - File/SendTo will not detect
these links. |
| DOS_0 (1) (*) |
Generative
Drafting |
Unrelated document can be pointed by the drawing document (it appears
using Send To). Ghost Link.
|
A section operator has an invalid link.
|
Deletion of the invalid link.
|
No more
Ghost Link in Send to command. |
|
DOS_1 (1) (*)
|
Generative Drafting
|
Unrelated document can be pointed by the drawing document (it appears
using Send To).
|
A section operator is not aggregated.
|
Deletion of
the object. |
No more
ghost links in Send To command. |
| DRF_0 (3) |
PartDesign |
When
deleting the draft, some related data are left in the document. |
Data model
Inconsistency. |
Remove Rsur
Features from Geometrical Set to PartBody under Draft feature. |
Data model
inconsistency is now solved for this draft feature. If deleting the
draft the life cycle management will be better.
Document needs to be updated. |
| DRF_1 (3) |
PartDesign |
When
creating a new draft feature the geometry selected to define the pulling
direction is inconsistent with the pulling direction vector. |
Inconsistency between the vector and the selected object in the
definition of default values. |
Default
pulling direction in object and vector is reset. |
Default
draft pulling direction is changed. The next created draft will use this
new default pulling direction. |
| DRW_0 (1) (*) |
Drafting |
No
visibility. |
More than one
drawing in the document. Others drawings are useless. |
Deletion of
the useless drawings. |
No impacta, solo reduce el tamaño del documento. |
| DRW_1 (1) (*) |
Drafting |
Ghost links might be visible in a part document via edit links, or a
Part document's size might be strangely big.
|
A DrwDrawing
with external links is inside the CATPrtCont. It is not visible in the
specstree. |
Removal of
the DrwDrawing. |
El tamaño del documento se reduce. Desaparecen los los Links fantasmas en el comando SendTo. |
| DST_0 (1) |
Drafting |
Balloon,
datum feature, datum target, roughness symbol and coordinate dimension
not displayed. |
A simple text
must aggregate at least one sub-text. |
Delete
annotation. |
No more
annotation. |
| DST_1 (1) (*) |
Drafting |
A ghost link
appears in the old drawing containing a section view. |
The callout
text kept old links after a copy-paste. |
Removes the
link but keeps the text as it was. |
There isn't
any ghost link anymore. The functionality that links the section view
name to the callout text will not work on cleaned models, as it was
already the case. |
| DTE_0 (3) |
Drafting |
Ghost link
visible in SendTo command and when opening the document. |
An internal
drafting data is erroneously referencing another document. |
Deletion of
the link. |
No behavior
modification except no more ghost link when opening the document. |
| DVB_0 (3) |
Part Design |
An Applicative Design Table cannot be deleted. Edit->Link command
shows a link on a standard file which should not be shown.
|
A Design table link found even when no feature was using it. In Part
Document Design table link exists even though the Hole/ Thread feature
using the standard is not available.
|
The design table link is deleted.
|
No more link in Edit/Link command. Applicative Design Table can be
deleted.
|
| DVM_0 (2) |
Drafting |
Error when
saving a CATDrawing. |
Useless
viewmakeup detected. |
Deletion of
the useless viewmakeup. |
CATDrawing is
correctly saved. Reduce the size of the document. |
| DWA_1 (3) |
Drafting |
Associativity
between 3D and section (cut) views can be wrong. |
An object
managing cut-views associativity is isolated and no more used by a view
(it should have been removed). |
Deletion of
the useless object. |
No impacta, solo reduce el tamaño del documento. |
| DWC_1 (3) |
Drafting |
An incorrect
profile section can be visualized in the drawing document. |
A profile
section is isolated and no more used by a view (it should have been
removed). |
Deletion of
the useless object. |
No impacta, solo reduce el tamaño del documento. |
| DWE_0 (1) |
Generative Drafting |
Ghost Link in SendTo command. Unrelated document can be
pointed by the drawing document (using SendTo). |
An object managing links between Views and 3D document
points an unrelated document. This can happen after replacing an
assembly, if this assembly contains different structures. |
Deletion of the useless object. |
No more ghost links in Send To command. |
| DWG_0 (1) |
Drafting |
Unrelated
part document is pointed by the drawing document. |
An object
managing dimensions generation is no more used by a view (it should have
been removed). |
Deletion of
the constraint. |
Document
needs to be updated. The constraint can be used again. |
| DWG_1 (3) |
Drafting |
Unrelated
part document can be pointed by the drawing document. |
An object
managing dimensions generation is isolated (it should have been
removed). |
Deletion of
the useless object. |
No impacta, solo reduce el tamaño del documento. |
| DWH_1 (3) |
Drafting |
Unrelated
part document can be pointed by the drawing document. |
A generative
hatching pattern is isolated (it should have been removed). |
Deletion of
the useless object. |
No impacta, solo reduce el tamaño del documento. |
| DWP_0 (3) |
Drafting |
No
visibility. |
A not
referenced pattern mapping table is useless. |
Deletion of
useless pattern mapping table. |
No impacta, solo reduce el tamaño del documento. |
| DWP_1 (1) |
Drafting |
No visibility. |
A pattern
mapping table is not aggregated. |
Deletion of
the pattern mapping table. |
No impacta, solo reduce el tamaño del documento. |
| DWR_0 (3) |
Drafting |
No
visibility. |
An useless
relation has been detected: either the in or the out of the relation is
(are) not valuated. |
Deletion of
the useless DrwRelation. |
No impacta, solo reduce el tamaño del documento. |
| DWS_0 (2) |
Drafting |
Impossible to
select a view (not allowed), Grid disappear, or impossible to activate
Drafting workbench. |
Internal
value which determines the order of the views is not set correctly. |
Internal
value set correctly : order of the views is correct. |
The view can
be selected. |
| DWS_1 (1) (*) |
Drafting |
No
visibility. |
A corrupted
sheet has been detected: either it has not the minimum required views
(background and main view) or it is not under the drawing. |
Deletion of
the corrupted sheet. |
No impact,
reduce the size of the document. |
| DWT_1 (3) |
Drafting |
Ghost Link in
SendTo command. |
Pattern not
aggregated correctly. |
Deletion of
the Pattern. |
No more Ghost
Link in SendTo command. |
| DWV_0 (1) (*) |
Drafting |
No
visibility. |
One or
several rules for a view in the drawing is not respected:
(1) a view must have a parent
(2) a view of type Pure_sketch must not have a sheet as its parent
(3) a view which is not of type Pure_sketch must have a sheet as its
parent. |
Deletion of
the View. |
CATDrawing
is correctly saved. Reduce the size of the document. |
| DWV_1 (2) |
Drafting |
Ghost Link in
SendTo command. |
A View is
linked with another Drawing. |
Deletion of
the Link. |
No more Ghost
Link in SendTo command. |
| DWV_2 (2) (*) |
Drafting |
When opening
a CATDrawing document, a warning with the following error message
appears: "The files in the following list could not be found or contain
the wrong information for the active document", but a document mentioned
in the list does not appear when using File/Desk or Edit/links command.
The user cannot correct the ghost link. |
During the
explode operation of a 2DComponent instance, some instance/reference
links were kept between some elements in the 2DComponent and the
document where the 2DComponent was originally created. |
The fixing
action consists in unplugging the View sub-components with ghost links
from their "ghost" reference and to replug them to their startups in
current document. |
No more
warning pop-up when opening the document |
| DWV_3 (3) |
Drafting |
The local
transformations of geometries in views (like translations, scaling,
rotations, offset) do not work, usually when some 2D Component instances
have been exploded or exposed in the CATDrawing. |
The
geometrical result of the axis component of a view has been lost. These
geometries are necessary to perform operations on other geometries in
the view. |
Update of the
SketchSupport in order to rebuild the result. |
Local transformations are available again on geometries. Reduce the
size of the model.
Document needs to be updated.
|
| DWV_4 (3) |
Drafting |
Axis elements
of the sketch support associated with a view that have been put in the
no-show space before CXR14 cannot be visualized in the show space
anymore. |
The sketch support is in the no-show space.
|
The sketch
support is put in the show-space and its axis elements are put in the
no-show space. |
The sketch support axis elements can be seen in the show space
(provided the user puts them in it).
|
|
DWV_5 (3) (*)
|
Drafting |
Ghost links
appear in File/SendTo command from a CATDrawing. |
A useless link exist on the view to an external document.
|
Remove the invalid link.
|
No more ghost link from the drawing in File/SendTo/Directory.
|
| EDL_1 (3) |
Electrical |
Electrical
part document is modified during the Instantiation from catalog. |
Electrical
features in part need to be updated. Update is performed during
instantiation and the part is modified. |
Update
electrical features in the part. |
Electrical
part document is not modified during the instantiation from catalog. |
| EHI_1 (3) |
Electrical |
Update error window "Sketch is not valid for feature you
want to create" when updating Bundle Segment of MultiBranchable part. |
Flexible curve attributes are not correctly valuated. |
Set the flexible curve attributes to correct value. |
No more error
window. |
| EHI_2 (2) |
Electrical |
The display of the names of electrical harness features (
Branch and Bundle Segments ) are not NLS (National Language Support)
compatible. |
The display of the name of electrical harness features is
given by Reference Designator attribute value and is not NLS compatible. |
Unset Reference Designator attribute value for Branch and
Bundle Segments. |
New names are displayed for electrical harness features
(Branch and Bundle Segments) , enabling NLS. compatibility. |
| EHI_3 (2) (*) |
Electrical |
In file mode, if the root document is moved in another directory and
the geometrical bundle document opened, electrical knowledge formula
will not be visible.
|
Electrical knowledge formulas under a geometrical bundle are not
correctly created.
|
If all formulas under the geometrical bundle are electrical, the
relation set will be recreated correctly with the correct formulas.
|
The root and
geometrical bundle documents needs to be saved. |
|
EHI_4 (1)
|
Electrical |
Bundle
segments lead to twisted configuration if minimum bend radius is smaller
than the diameter. |
The standard Rib geometrical feature cannot be collapsed.
|
Replace the
standard Rib by a collapsible one. |
No more update error (twisted configuration) for bundle segments have
a bend radius smaller than the diameter.
|
| EXT_0 (3) (*) |
Specs Modeler |
Ghost Link in
SendTo command. |
A link still
exists to the pointing documents due to unused extensions feature. |
Unused
extensions feature are deleted. |
Document
needs to be updated.
No more ghost links |
| EXT_2 (3) (*) |
Specs
Modeler |
Ghost links when opening a CATProduct. A Pop up message is displayed.
|
The
reference of an extension is not in the same document that the reference
of its base feature (probably after a replace). |
The startup of the extension becomes also the reference of the
extension. No data lost, only rerouting a link.
|
No more
ghost links to documents containing the old reference. |
| FGM_1 (3) |
Topological
Objects |
Size of
CATPart abnormally huge comparatively to the number of elements. |
Some
vertices have unnecessary geometric data (linked curves / surfaces). Some surfaces are over defined (unnecessarily extrapolated). |
Remove
unnecessary geometric data. |
El Part es el mismo, pero mas pequeño. |
| FIL_0 (2) |
Part Design |
During the
edition of the fillet, an error "Internal error in mechanical modeler"
is flashed. |
Support of some PointOnEdges (used to define radius for variable
fillet) belongs to a ribbon different from the one to which the
PointOnEdge itself belongs. Hence when the support edge is removed by
the user (de-selection from UI), the corresponding PointOnEdge is not
removed. This PointOnEdge then remains without support and gives an
error "Internal error in mechanical modeler" when we try to access its
support.
|
Move the
PointOnEdge (FilletRadius object containing it) to appropriate the
ribbon. |
Some objects (the fillet concerned and its impacted features) are
seen non-updated. Document needs to be updated.
|
| FS4_1 (3) |
V4V5integration |
ENOVIAVPM User views some ghost links pointing a V4 Model in a part created by
V4toV5Interoperability. |
Declaration
of a invalid Extension. Internal not used Extension. |
Deletion of
Unwanted Extension. |
No more
invalid V4 ghost links in V4ToV5Part. |
| FTA_1 (1) (*) |
3D
Functional Tolerancing & Annotation |
Sometimes,
unused external links (shape representation of a product) shown in Edit
Links or File Desk. |
The TTRS (
Technologically and Topologically Related Surface ) features become
invalid because their StartUp has been removed from the container. |
Deletion of
the invalid TTRS features. |
In Edit
Links, there are no more unused external links. |
| FTA_2 (3) |
3D Functional
Tolerancing & Annotation |
No
visibility. |
Unused
elements (RGE, Reference Geometrical Elements) are present. |
Deletion of
unused elements. |
El documento es el mismo, pero mas pequeño. |
| FTA_3 (3) |
3D Functional
Tolerancing & Annotation |
No
visibility. |
Unused
elements (TTRS) are present. |
Deletion of
unused elements. |
El documento es el mismo, pero mas pequeño. |
|
FTA_4 (3)
|
3D Functional
Tolerancing & Annotation |
Deletion of FTA annotations does not delete all Drafting internal
entities (the visualization of FTA annotations is based on Drafting).
Data size of a document is abnormally huge regarding its elements.
|
When remove
was called for FTA annotation, nothing was done in order to delete the
Drafting annotations. |
Delete all Drafting annotations which are not pointed by FTA one.
|
Reduce the size of the document. There is no link anymore between
drafting annotations and FTA annotations.They are not used anymore in
CATPart, CATProduct, CATProcess documents (they are in fact lost). Document needs to be updated.
|
| GIE_0 (2) |
Drafting |
A generated
item cannot be used while creating associative dimensions. |
Generated
Item without any associated reference curve. |
Deletion of
the generated item. |
No impact,
reduce the size of the document. |
| GME_0 (1) (*) |
Generative
Drafting |
Unrelated document can be pointed by the drawing document (it appears
using Send To).
|
An object managing graphic properties of generated items is not
aggregated.
|
Deletion of the object.
|
No more ghost
links in Send To command. |
| GME_1 (1) (*) |
Generative
Drafting |
Unrelated document can be pointed by the drawing document (it appears
using Send To).
|
An object
managing graphic properties of generated items has an invalid link to a
3D document. |
Deletion of the invalid link.
|
No more ghost
links in Send To command. |
| GNL_1 (3) (*) |
Generic
Naming |
Ghost links
in SendTo or Edit Links item. |
An internal
of a Brep feature refers to a ghost external document. |
The external
reference is removed. |
Ghost links
have been removed. |
| GNL_3 (3) (*) |
Generic
Naming |
Abnormal size
of a document. |
A
GenericNaming Feature is not aggregated, resulting in a useless memory
cost. |
The useless
feature is removed. |
Reduce the
size of the document. |
| GSD_0 (3) |
Generative
Shape Design |
Sometimes,
the user can only see invalid "Parent / Children" or impact analyses. |
An object is
aggregated under "Component" attribute but it is never used elsewhere. |
Suppresses
these useless objects. |
Visually no
impact, better 'Parent / Children' or impact analyses, reduces the size
of the document. |
| GSD_1 (1) |
Generative
Shape Design |
The
reference planes have the datum mask on their icon and can have been
moved with the compass. |
The
reference planes are turned into datum or flagged as contextual
features. |
Reset the
datum and\or contextual flags to 0. If a reference plane has been moved,
a new one is created and added at the place of the moved reference
plane. The moved reference place is renamed with the add of "moved by
cleaner" to its alias. |
The icon of
the reference plane has not the datum mask any more. A reference plane
moved is renamed and a new reference plane is created. |
| GST_0 (2) |
Generative
Shape Design |
The user
opens a CATPart with an unidentified object (broken icon) called
RollingOffset. |
The Start-up
inheritance of the object is broken, it is due to incorrect
CATHybridShape.feat catalog construction. |
Re-plugs the
broken instance with the correct start-up in the CATHybridShape catalog. |
Object now
corresponding to a valid Rolling Offset. |
| HIE_3 (3) |
SpecsModeler |
A product
instance has too many sub-products. |
Hierarchy
problem : the father of the reference is not the reference of the
father. |
Over
sub-products are deleted and product instance is synchronized. |
No more over
sub-products. |
| HIE_4 (1) (*) |
SpecsModeler |
When opening
a CATProduct document or using the "Send to directory" command, a linked
document is not found but that document should not be linked as it does
not participate in the product structure. |
An internal
object (connector) has an inconsistent state and retains an
instance-reference link to a useless document. |
Remove the
offending connectors. |
No more
warning pop-up when opening the document |
| HIE_5 (3) |
SpecsModeler |
After first clean, DOC_3 error is still there. |
A change of
reference is made during save as operation when a private component can
not find its reference, this change must be done by the CATDUA. |
The CATDUA
change the reference of this component. |
Error DOC_3 is fixed completely by first pass of CATDUA. |
| HIE_6 (1) |
Product
Structure |
Impossible
to update the model: some assembly data (constraints) are invalid. |
Instance /
Reference model mapping error for CONNECTION objects leads to invalid
constraints: CONNECTION reference objects aggregated by an instance of
ASMDISCIPLINE object. |
Invalid
connections deletion. |
Document is
now updated or can be updated, invalid constraints are deleted. |
| HLV_0 (1) (*) |
Generative Drafting
|
Unrelated document can be pointed by the drawing document (it appears
using Send To).
|
A generative view is not aggregated.
|
Deletion of
the object. |
No more
ghost links in Send To command. |
| HLV_1 (1) (*) |
Generative Drafting
|
The drawing
document size can be out of proportion regarding the useful data
contained inside. Unrelated document can be pointed by the drawing
document (it appears using Send To). |
A
generative view is not aggregated |
Deletion of the non aggregated generative view.
|
The drawing document size is normal again. No more ghost links in
Send To command.
|
| IGP_1 (1) |
Robotics |
When cleaning any mechanism that has constraint created by
FramesOfReference in Device Building, the constraint is deleted.
|
TagConnectors created on constraint definition is not aggregated to
any parent. So when cleaning up the document for any reason, the LIF_8
rules deletes all the floating connectors, that is why this TagConnector
is deleted too. Hence the parts associated with the constraints are
disconnected.
|
Aggregate
the floating TagConnectors with the TagGroup being its logical parent. |
TagConnectors are no more deleted when cleaning the document.
|
| IGS_0 (3) |
Sketcher |
Use edges
created when constraints created, then when deleting these constraints,
use edges are not deleted and are therefore unnecessary (severity 3
since R9SP3). |
Use edges
are not deleted when associated constraints are deleted. Unused elements
(phantom operators) stay in the document. |
Deletion of
unused elements. |
Document
needs to be updated. Document is the same but smaller. |
| JNT_1 (1) |
DMU
Kinematics |
Mechanism
cannot be simulated |
One or more
kinematics joint axis are corrupted |
Deletion of
the corrupted joint. |
Some joints
are deleted. If you want to play again the Mechanism, you have to
recreate the deleted joints. |
| JNT_2 (1) |
DMU
Kinematics |
Mechanism
cannot be simulated. |
One or more
geometries pointed by a kinematics joint are corrupted. |
Deletion of
the corrupted joint. |
Some joints
are deleted. If you want to play again the Mechanism, you have to
recreate the deleted joints. |
| JNT_3 (1) |
DMU
Kinematics |
This Message
is displayed when trying to play a Mechanism: "There is no Kinematics
Data". |
Several
Mechanism containers exist in the same CATProduct document. |
Deletion of
all Mechanism containers except the first non-empty one. |
All the
previous Mechanisms are restored correctly. |
| JNT_4 (2) |
DMU
Kinematics |
The user
opens a document containing a mechanism, he modifies some constraints
associated to the joints of the mechanism, updates the mechanism and
saves his work. After reloading the document, the associated constraints
are broken. When clicking on the "Mechanism Analysis" command, you can
see "CATMacroPointCGM" or "CATSimCurveCGM" or any "CATXXXCGM"
in the "Geometry 1" or "Geometry 2" columns. |
The problem
was occurring at the joint creation. The joint creation command analyses
the geometry selected by the user to create the joint and convert this
geometry into "persistent" geometry. This conversion was not correctly
done and the geometric stored objects were not understandable any more
by the assembly model after saving it and reloading it. |
Repair the joint and the associated constraints by replacing the
incorrect pointed geometric element by a correct one.
|
When clicking on the "Mechanism Analysis" command, the geometry name
is a correct name like "Point.1" or "Curve.1" for
instance.
Document needs to be updated.
|
| JNT_5 (2) |
DMU
Kinematics |
The user
opens a document containing a mechanism with at least one "Point on
Curve" joint. He clicks on "Simulation with commands". One part involved
in "Point On Curve" joint, jumps on a wrong position different from its
current position. |
A "Point on Curve" Joint simulation is not correct. The problem comes
from the Point on Curve Joint creation. The Point on Curve joint as a
regular kinematic joint contains among its internal data some local
frames. These frames locate the joint position regarding the parts and
are used in the kinematic solver for simulation. In some rare case, the
internal frames of the joint can not be created correctly. Note that a
Point on Curve joint can only be repaired if the joint is not broken
(i.e. the point is effectively on the curve.)
|
Internal frames of the joint are updated.
|
User can click on the "Simulation with commands" without any strange
displacement for parts involved in a point on curve joint.
Document needs to be updated
|
| KWE_1 (1) |
Knowledge |
No visible
symptom. |
Knowledge
Objects not aggregated. |
If these
objects are not pointed, they are destroyed. If it is a parameter that
is pointed, it is added to the parameter set. If it is a relation that
is pointed, it is added to the relation set. |
No
Visibility. |
| KWE_2 (1) |
Knowledge |
a "!"
information is displayed on a broken relation. |
A relation in
a CATPart document points to elements in other documents. |
The relation
is destroyed. |
Broken
relation disappears. |
| KWE_3 (2) |
Knowledge |
The output
value of a relation is not consistent. After forcing relation
evaluation, its value changes. |
The output
parameter has been saved with a wrong value. |
The
evaluation is forced. |
The output
parameter is set to the good value. |
| KWE_4 (2) |
Knowledge |
A Knowledge
Check is broken. "!" information is displayed. |
An error in
the stream involves bad pointing in the Check attributes. |
The links are
restored correctly. |
The check is
not broken. |
| KWE_5(2) |
Knowledge |
A parameter
external Reference was synchronized but with a wrong value. |
Even it was
not possible to synchronize the External Ref and get the pointed value,
the information of synchronization was stored. |
if the
external Reference is synchronized and has a wrong value, the value is
updated with the good one. |
The external
Reference is synchronized and with a good value. |