User Activity

  • Posted a comment on discussion Help on PyCAM

    The number of openscad lines is not a safe indicator for the complexity of a model :) With the CSG modeling you will need to take care that you do not create near-infinitly small gaps between different components (e.g. by adding a bit of extra size in all dimensions).

  • Posted a comment on discussion Help on PyCAM

    The docs mention a new, experimental waterline algorithm. Is there a way to try it? I am not exactly sure, but I guess, the current default waterline algorithm was meant. There are better algorithms out there in other libraries - it just needs someone to integrate one of them into pycam. I'll try simplifying the object. Maybe remove the central hole... I did not intend to suggest a real change of the model :) I thought about a simplification of the mesh/triangle representation. Maybe you can try...

  • Posted a comment on discussion Help on PyCAM

    Hi Moshe, I am afraid, that you stumbled upon the instability of the waterline algorithm of pycam. I do not see a good way to fix that code (it should probably be replaced with an external library). I could imagine, that your model contains some interesting "interior" triangles, that could confuse the waterline algorithm. Thus maybe it could help to "simplify" the model with a 3D modelling program (I am not aware of details in this area - this is just a wild guess). If this does not help, then you...

  • Posted a comment on discussion Open Discussion on PyCAM

    You can take a look at the function "get_fixed_grid" in pycam/Toolpath/MotionGrid.py. Here you could change "start_position=StartPosition.Z" to "start_position=(StartPosition.X | StartPosition.Y | StartPosition.Z)" - this should move the starting point from (0, 0, maxz) to (maxx, maxy, maxz). Of course, this is just a manual (hard-coded) modification. Probably the difficulty part starts when you try to turn this into a configurable option being available in the user interface :) Have fun!

  • Posted a comment on discussion Open Discussion on PyCAM

    This is mainly an issue with the user interface, since it complicates the interface even further. Anyway: contributions are always welcome!

  • Posted a comment on discussion Open Discussion on PyCAM

    I can assure you, that your expectations are in line with the goals of the developers :) I assume that you created a toolpath (and saw it in the preview window)? And then you selected this toolpath and clicked on the "export" tab in the lower part of the screen? Was there a filename selection dialog? Was a non-empty file created? Feel free to describe, where exactly pycam did not behave, as you expected.

  • Posted a comment on discussion Help on PyCAM

    Ah - ok. We should just skip the "below step width" axis (and keep the other axes of the location). This sounds reasonable - I will take a look at that.

  • Posted a comment on discussion Help on PyCAM

    Hi, the current StepWidth logic within pycam is defined as follows (see pycam/Toolpath/Filters.py: line 476): calculate the distances between every two successive locations (for all three axes) if all three distances (x, y, z) are smaller than their defined StepWidth (here: 0.002), then this location is skipped For your example it means, that probably some points in between were already skipped, but somewhen the x stepping exceeded the limit - thus the point was recorded. I do not have a machine...

View All

Personal Data

Username:
sumpfralle
Joined:
2005-12-12 04:35:54

Projects

Skills

  • No skills entered.

Personal Tools