Lattice workbench [updated Polar Array]

Need help, or want to share a macro? Post here!
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
User avatar
DeepSOIC
Veteran
Posts: 7896
Joined: Fri Aug 29, 2014 12:45 am
Location: used to be Saint-Petersburg, Russia

Re: Lattice workbench [PartDesign invasion]

Post by DeepSOIC »

triplus wrote: Fri Jun 15, 2018 12:20 am And how does that cope with the single solid limitation?
There is a property that switches the enforcement on and off. Off by default.
triplus
Veteran
Posts: 9471
Joined: Mon Dec 12, 2011 4:45 pm

Re: Lattice workbench [PartDesign invasion]

Post by triplus »

DeepSOIC wrote: Fri Jun 15, 2018 10:31 am
triplus wrote: Fri Jun 15, 2018 12:20 am And how does that cope with the single solid limitation?
There is a property that switches the enforcement on and off. Off by default.
I guess we still have some work to do in figuring this out. Having a restriction that could end up being important in the future. But on the other hand doesn't make much sense and it isn't respected ATM.
chrili_rakete
Posts: 54
Joined: Thu May 15, 2014 11:51 am

Re: Lattice workbench [PartDesign invasion]

Post by chrili_rakete »

Hello,

first of all I want to thank you for the development of the lattice workbench – it seems to be just what I was looking for right at the moment. I am not sure that this thread here is the right place to post my question, please apologize if not:

Sketch driven placements via the <Array from shape> command seem to be the most convenient approach for my purposes […, Orient mode: child.Edge, Translate mode: child.Vertex, Compound Traversal: Recursive, …]

If my sketch consists of two lines, the result are two placements – as long as these two lines (edges) do not share one of their vertexes. Then they effect just one placement. I attached a file where the left side of the drawing shows this, whereas the right side illustrates the result I would like to achieve:
Lattice2_Array_from_Shape.fcstd
(12.71 KiB) Downloaded 81 times
I suppose that the geometrical identity of two vertexes of two edges makes them a one-entity "wire" as a "direct child" of the driving sketch. That's why I changed the property <Compound Traversal> from <Direct children only> to <Recursive> – but this had no effect …

Is there a solution or a different approach in lattice2 or do I have to adapt my sketches?

Thank you!
--
Christoph

OS: Ubuntu 18.04 LTS
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.13964 (Git)
Build type: None
Branch: master
Hash: 548511ac30cd07328db60169f854d08975adf047
Python version: 2.7.15rc1
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.2.0
Locale: German/Austria (de_AT)
User avatar
DeepSOIC
Veteran
Posts: 7896
Joined: Fri Aug 29, 2014 12:45 am
Location: used to be Saint-Petersburg, Russia

Re: Lattice workbench [PartDesign invasion]

Post by DeepSOIC »

chrili_rakete wrote: Wed Jun 20, 2018 5:46 pm I suppose that the geometrical identity of two vertexes of two edges makes them a one-entity "wire" as a "direct child" of the driving sketch.
Yes.
Info tool reports:

Code: Select all

Selected document object:
  Name = Sketch
  Label = Sketch
  Is placement/array = False
Structure: 
Compound (5 objects):
    Wire (4 segments)
    Wire (1 segments)
    Wire (1 segments)
    Wire (1 segments)
    Wire (1 segments)
Compound traversal will not make Lattice look into wires for edges. It affects how nested compounds are processed. But yours is a flat one. It will be useful for example if you Part Compound two sketches.

To deal with your problem, downgrade your sketch to edges, amd make the array from the downgrade.

Code: Select all

Selected document object:
  Name = Downgrade
  Label = Edges of Sketch
  Is placement/array = False
Structure: 
Compound (8 objects):
    Edge (<Line object>)
    Edge (<Line object>)
    Edge (<Line object>)
    Edge (<Line object>)
    Edge (<Line object>)
    Edge (<Line object>)
    Edge (<Line object>)
    Edge (<Line object>)
lattice2-array-from-dhape-downgrade.FCStd
(15.64 KiB) Downloaded 77 times
chrili_rakete
Posts: 54
Joined: Thu May 15, 2014 11:51 am

Re: Lattice workbench [PartDesign invasion]

Post by chrili_rakete »

DeepSOIC wrote: Thu Jun 21, 2018 9:26 am To deal with your problem, downgrade your sketch to edges, amd make the array from the downgrade.
Perfect, so easy! I appreciate that very much – thank you!
User avatar
DeepSOIC
Veteran
Posts: 7896
Joined: Fri Aug 29, 2014 12:45 am
Location: used to be Saint-Petersburg, Russia

Re: Lattice workbench [PartDesign invasion]

Post by DeepSOIC »

triplus
Veteran
Posts: 9471
Joined: Mon Dec 12, 2011 4:45 pm

Re: Lattice workbench [PartDesign invasion tutorial]

Post by triplus »

One thing i guess is to invade PartDesign with Lattice. And another thing i guess is a tutorial on how exactly to do that.

Thanks! ;)
User avatar
DeepSOIC
Veteran
Posts: 7896
Joined: Fri Aug 29, 2014 12:45 am
Location: used to be Saint-Petersburg, Russia

Re: Lattice workbench [updated Polar Array]

Post by DeepSOIC »

Polar array was updated.

* it is now attachable
* array on arc of circle
* new orientation modes and possibility to switch axis directions
* array direction reversal
* dropdown commands with fit presets (like linear array)
polar-array-v2.png
polar-array-v2.png (115.65 KiB) Viewed 3430 times
triplus
Veteran
Posts: 9471
Joined: Mon Dec 12, 2011 4:45 pm

Re: Lattice workbench [updated Polar Array]

Post by triplus »

DeepSOIC wrote: Mon Aug 06, 2018 1:30 pm Polar array was updated.
Don't have much time to test ATM. But i am guessing PartDesign workflow invasion is included?
User avatar
Vincent B
Veteran
Posts: 4734
Joined: Sun Apr 05, 2015 9:02 am
Location: La Rochelle, France

Re: Lattice workbench [updated Polar Array]

Post by Vincent B »

Is Paraseries can handle ShapeString? I can't success to modify the string with it. :roll:
Attachments
Capture.JPG
Capture.JPG (33.96 KiB) Viewed 1247 times
Post Reply