Behavior of nested containers when moving with Manipulator WB
Forum rules
and Helpful information
and Helpful information
IMPORTANT: Please click here and read this first, before asking for help
Also, be nice to others! Read the FreeCAD code of conduct!
Also, be nice to others! Read the FreeCAD code of conduct!
Behavior of nested containers when moving with Manipulator WB
Not sure this is a Manipulator thing or a Std_Part thing...
Start with the following (note the position of the axis cross):
Use transform to get this:
Now use Manipulator to put it back together by selecting the top of boss and the bottom of the hole in the pcb (again note the axis cross):
But, delete the top level Std_Part (Controller With Mount Plate), keeping the contents, perform the same as above the pcb moves as would be expected and drag them all into a new Std_Part and all is good.
What is it about containers?
Is this a Manipulator issue?
Start with the following (note the position of the axis cross):
Use transform to get this:
Now use Manipulator to put it back together by selecting the top of boss and the bottom of the hole in the pcb (again note the axis cross):
But, delete the top level Std_Part (Controller With Mount Plate), keeping the contents, perform the same as above the pcb moves as would be expected and drag them all into a new Std_Part and all is good.
What is it about containers?
Is this a Manipulator issue?
Star Trek II: The Wrath of Khan: Spock: "...His pattern indicates two-dimensional thinking."
Re: Behavior of nested containers when moving with Manipulator WB
Sorry for the pings, but, I'm not sure the subject is really making it obvious what this post is about...and not sure how to rephrase it to do so.
I think this is a combination of idiosyncrasies of nested Std_Part containers or a bug in Manipulator WB handling of nested containers, or some combination, or none of the above...
I think this is a combination of idiosyncrasies of nested Std_Part containers or a bug in Manipulator WB handling of nested containers, or some combination, or none of the above...
easyw-fc wrote: pinged by pinger macro
TheMarkster wrote: pinged by pinger macro
edwilliams16 wrote: pinged by pinger macro
Star Trek II: The Wrath of Khan: Spock: "...His pattern indicates two-dimensional thinking."
Re: Behavior of nested containers when moving with Manipulator WB
There is an issue in Manipulator WB... it doesn't handle correctly an alignement when a top level 'Part' container has a non 'zero' placement.drmacro wrote: ↑Mon Nov 29, 2021 1:13 pm Sorry for the pings, but, I'm not sure the subject is really making it obvious what this post is about...and not sure how to rephrase it to do so.
I think this is a combination of idiosyncrasies of nested Std_Part containers or a bug in Manipulator WB handling of nested containers, or some combination, or none of the above...
easyw-fc wrote: pinged by pinger macro
There is a tool in kicadStepUp WB to reset the placement of a 'Part' contained assembly to 'zero', maintaining the actual position:
here the related forum thread:
https://forum.freecadweb.org/viewtopic. ... 17#p515417
Re: Behavior of nested containers when moving with Manipulator WB
Hmm...yes I remember that thread. But, in the attached version of the file in the images above, you'll note the container/s are not off origin. And applying the KiCADStepup tool doesn't change the behaviour.easyw-fc wrote: ↑Mon Nov 29, 2021 3:30 pm ..
There is an issue in Manipulator WB... it doesn't handle correctly an alignement when a top level 'Part' container has a non 'zero' placement.
...
here the related forum thread:
https://forum.freecadweb.org/viewtopic. ... 17#p515417
(I had to remove some the other containers to get the file size down to forum allowed. )
- Attachments
-
- ControllerPlusMountPlate-min.FCStd
- (111.71 KiB) Downloaded 26 times
Star Trek II: The Wrath of Khan: Spock: "...His pattern indicates two-dimensional thinking."
Re: Behavior of nested containers when moving with Manipulator WB
I cannot display anything of your file... I can only see the objects in the combo View, but nothing in the 3D view areadrmacro wrote: ↑Mon Nov 29, 2021 4:01 pm Hmm...yes I remember that thread. But, in the attached version of the file in the images above, you'll note the container/s are not off origin. And applying the KiCADStepup tool doesn't change the behaviour.
(I had to remove some the other containers to get the file size down to forum allowed. )
Re: Behavior of nested containers when moving with Manipulator WB
Interesting.
If I open it in 0.19 I get the same, objects in tree, but nothing in 3D.
Fine in 0.20 though.
If I open it in 0.19 I get the same, objects in tree, but nothing in 3D.
Fine in 0.20 though.
Star Trek II: The Wrath of Khan: Spock: "...His pattern indicates two-dimensional thinking."
Re: Behavior of nested containers when moving with Manipulator WB
@drmacro,
unfortunately I cannot see anything in the 3D viewer also with:
unfortunately I cannot see anything in the 3D viewer also with:
Code: Select all
OS: Windows 10 (10.0)
Word size of FreeCAD: 64-bit
Version: 0.20.26498 (Git)
Build type: Release
Python version: 3.8.12
Qt version: 5.12.9
Coin version: 4.0.0
OCC version: 7.5.3
Re: Behavior of nested containers when moving with Manipulator WB
It appears any FreeCAD that is using less than 7.6 OCCT won't display the file.
It loads, reports no error. Geometry check of items in the tree show no error or shape content.
It loads, reports no error. Geometry check of items in the tree show no error or shape content.
Star Trek II: The Wrath of Khan: Spock: "...His pattern indicates two-dimensional thinking."
Re: Behavior of nested containers when moving with Manipulator WB
The attached file has only been changed in 0.19 FC with OCCT 7.3.
I did notice the plate is not a 0,0,0. But, the Part containers are. This may be the source of the issue.
I did notice the plate is not a 0,0,0. But, the Part containers are. This may be the source of the issue.
- Attachments
-
- ControllerPlusMountPlate_min_7p3.FCStd
- (106.38 KiB) Downloaded 20 times
Star Trek II: The Wrath of Khan: Spock: "...His pattern indicates two-dimensional thinking."