View Issue Details

IDProjectCategoryView StatusLast Update
0001596PartDesignBugpublic2014-12-26 18:29
Reportermtroback Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformPCOSWindowsOS Version7 64-bit
Product Version0.14 
Summary0001596: Unable to create pocket using selected sketch which is mapped to a face
DescriptionI'm trying to create a pocket on a part (Pad001) by having a sketch mapped to a face of the part. The command fails with the error message

---------------------------
Input error
---------------------------
TopoDS::Face
---------------------------
OK
---------------------------

I have previously been able to create this pocket, but after editing the sketches that were used to create the part (Pad001) it now fails.

I have tried to re-map the sketch to the face, but the operation still fails.
Steps To ReproduceIn the attached file, try to create a pocket using Sketch002.

Sketch002 is mapped to a face of Pad001 and can be seen when viewing from the '6' angle (press num-key 6 to go to the correct view).

The part Pad001 is created by padding the sketch Sketch001. Sketch001 is mapped to a face of part Pad, which is created by padding sketch Sketch.
Additional InformationThis is my first bug report, please let me know how I can improve my input.
TagsNo tags attached.
FreeCAD Information

Activities

mtroback

2014-07-07 13:53

reporter  

ed_guide_faulty.FCStd (253,433 bytes)

mtroback

2014-07-07 13:57

reporter   ~0004776

Full about:

OS: Windows 7
Word size: 64-bit
Version: 0.14.3691 (Git)
Branch: master
Hash: 691fd1128672c8bd472cece87c9e9d07b71d6fee
Python version: 2.7.6
Qt version: 4.8.5
Coin version: 4.0.0a
SoQt version: 1.6.0a
OCC version: 6.6.0

mtroback

2014-07-08 07:56

reporter   ~0004778

I found the problem today, the sketch (Sketch001) used to create the part (Pad001) had errors in a slotted hole. Even though it could create the pad based on the faulty sketch, it is understandable that it couldn't create a pocket in the (faulty) part.

Once fixed there is no longer an issue. Sorry for the spam.

Issue History

Date Modified Username Field Change
2014-07-07 13:53 mtroback New Issue
2014-07-07 13:53 mtroback File Added: ed_guide_faulty.FCStd
2014-07-07 13:57 mtroback Note Added: 0004776
2014-07-08 07:56 mtroback Note Added: 0004778
2014-12-26 18:29 normandc Status new => closed
2014-12-26 18:29 normandc Resolution open => no change required