Jump to content

Cuq

Expert
  • Posts

    675
  • Joined

  • Last visited

  • Days Won

    18

Posts posted by Cuq

  1. Theoretically it's possible, but there are several messages here from users who are experiencing problems with pellet extruders.  The main difference on these machines is that it's not possible to manage wire retract to avoid oozing.

     

    So the question is often how to manage this non-retract. I've seen several requests about the possibility of managing G0, with a systematic Z hop or different speeds or combine with Zhop. It's up to you to see what you need to use this type of printer.

  2. Well, it depends: If we talk about printing order, there are two different needs. One is often in One at Time mode where you want to control the order and position of the part to avoid collisions with the Z axis or displacements for part with similar size. In this case we can solve the problem.


    In the second case, we want to have a specific order, for example, to make the small parts first because they do not interfere with the printing process and then launch the largest part at the end of the printing process. In this case it's more complicated because the order of the list will define the printing order. In this case one of the solutions (of Workaround if you prefer)  is to save the models to be made first in a project (3mf file) and the others in a second project.  Then you open the 3mf file  of the parts to be print at the end, and import in this project the first element as model. In this way your modifications, support and other specific parameters defined for every models are preserved and the order is defined.

     

    I rarely use the One At Time mode, but if I had this problem and had to reorganize my objects oftently, I think a Macro or a Plugin could automate this process.

  3. In version 5.3 (maybe it has changed since the previous versions), the printing order is different if you are in the mode :
    All At Once or One at a Time

     

    In the One At Time mode, Cura uses the reverse order of the objects list  to print the parts. In this mode you can define the position of the parts on the bed to organize the printing according to the position you want.

     

    In the All at Once mode, it starts (for a square bed) from the first part in front of the bed on the Left and the following order will be based on the shortest distance between the parts. In this case it is difficult to define an order of printing except to arrange the parts with a distance which imposes the order of creation. But it is very complicated.

    • Heart 1
  4. For me there is no problem just a misunderstanding of the concept of origin and origin offset on CNC machine.  By using the origin setting in the center of the bed in Cura the problem should not exist. But since I still didn't really understand what was wrong with the Cura coordinate system question, maybe I have a wrong idea of the problem.

  5. You can try with : 

    node.getWorldTransformation().getData()

     

     

    But not sure you get what you want . In this case it's the Transformation comming from the 3mf file, With a Stl As you have notice it will gives you  :

     

    [1. 0. 0. 0.]
    [0. 1. 0. (height/2)]
    [0. 0. 1. 0.]
    [0. 0. 0. 1.]

     

     

     You can Also Try SuperSlicer As Free Source Code . It already integrate a Slicer + an integrated Function to generate the milling Toolpath

    image.thumb.png.358fc0d9947b7ac615f3b76f860436ec.png

     

    image.png.d0e7f748db1987ee25490e4f3465b738.png

     

    Again not exactly your request but a good start for this type of project with some interesting option like the milling_extra_size to add some material to the shape to be sure to get enough material to be milled .. 

     

  6. Don't really understand why you not simply create your own predator.def.json file in your local user definition folder as it should be and not try to mess the configuration by duplicating the files in your local configuration. With a unique name you will be sure to avoid all the problem. I m working like that and doesn't have any issue from 4. To 5.3 (except with the issue of this 5.3 alpha sharing the same folder as the 5.3 )

×
×
  • Create New...