Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Curved slicer guide and troubleshooting #87

Open
ioannaMitropoulou opened this issue Nov 24, 2020 · 9 comments
Open

Curved slicer guide and troubleshooting #87

ioannaMitropoulou opened this issue Nov 24, 2020 · 9 comments
Labels

Comments

@ioannaMitropoulou
Copy link
Collaborator

Write a guide with all the steps that one needs to take to use the curved slicer and all the caveats that one can run into. In particular;
-Mesh sanitizing + welding
-Targets generation
-Generation of different segments

This could be part of the curved slicer tutorial

@Mostafarhmi
Copy link

Hello, hello I have a problem with Targets generation or Boundary LOW and HIGH generation, I don't know where and how I have to generate this Json file. can you please help me?

Mostafa Rahimi

@ioannaMitropoulou
Copy link
Collaborator Author

These json files contain each a list of the indices of the vertices that are in your desired boundary. Each file looks like this:

[ 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29 ]

An easy way to generate them, is by using the component that you can find in the examples/2_curved_slicing/curved_slicing_master.gh

If you look at the top part, you find the following components. There you should make sure to select the correct curves on each target (see screenshot below)

image

Then you can press the "Save" button, and the two files are automatically saved on your specified data folder.

image image

Let me know if this works for you.

@Mostafarhmi
Copy link

Thank you very much for your detailed answer. it works for me, but for determining new boundary for my own model I have problem .
short question! In the curved_slicing area, how can I define max and min layer height?

@ioannaMitropoulou
Copy link
Collaborator Author

Would you like to share the model you are using and what targets you want so I can see the problem?

In the curved_slicer you cannot set a min and max layer height, you can only set an average layer height, which determines how many layers will be produced. The min and max layer height then derives from the number of layers and the distances between the provided targets.

@Mostafarhmi
Copy link

Unbenannt

@OjasMahajan
Copy link

Hello @ioannaMitropoulou
I am having problems generating "out_printpoints.json" for this. I have your code from the repository. Can you help me out?

image

@ioannaMitropoulou
Copy link
Collaborator Author

Hello Ojas,
The result seems to reasonable for the inputs that you display in the image. Could you explain in more detail what is the challenging you are facing? Perhaps consider also attaching the files that you are using.
Best,
Ioanna

@OjasMahajan
Copy link

OjasMahajan commented Sep 24, 2024

Hello @ioannaMitropoulou,
1- My requirement comes from the printing process. We want to print this piece with WAAM. And want to avoid such corners (circled in red). A gradual fillet or flat line at these corners will help a lot. If I try to change the values in your code, it does not export the "out_printpoints.json" file. Is there another way to have this control?
image

2- I see that your script joints all the paths into spiral toolpaths, but is there a way to have them layer by layer? Sometimes we need to wait for the metal to cool down before we start the next layer.
image
TO
image

@Mostafarhmi
Copy link

How can I define not only upper and lower boundaries but also additional boundaries in the middle, wherever necessary? In Python, I currently only have upper and lower boundaries. Could you please explain how I can do this in Rhino Grasshopper, and how should I modify my Python code for this new boundary?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants