M486 processor for Cura?



  • Since a search didn't turn up anything, I guess that the answer is "no". But, I am optimistic and gotta ask if someone knows of a way to be able to use Cura and get support for M486 with some sort of plugin/post processor.

    But, since I have noticed that cura doesn't put much in the way of comments in the code, I will as the subject indicates guess "No".


  • administrators

    M486 recognises Cura MESH comments.



  • @dc42 said in M486 processor for Cura?:

    M486 recognises Cura MESH comments.

    Oh, egg on my face.

    But, Then I am not understanding how I can check Cura or generated gcode to see which Mesh corresponds to which object.

    Is there any writeup somewhere on this?


  • administrators

    Try putting several different objects on the build plate in Cura, slice it, simulate it, pause the simulation, and send M486 to list the objects.



  • @dc42 said in M486 processor for Cura?:

    Try putting several different objects on the build plate in Cura, slice it, simulate it, pause the simulation, and send M486 to list the objects.

    Simulate... Of course.. Why on earth have i not been able to find that with all my google-ing. Thank you.

    M486
    0: X -27 to 27mm, Y -117 to 117mm, Rack235mm.stl
    1: X -45 to -37mm, Y -32 to 32mm, FilterTemplate.stl


  • administrators

    One issue I have heard of when using M486 with Cura is that Cura apparently labels all support with the same MESH comment. So if you cancel an object, the support for that object will continue to be printed, unless you cancel all support.



  • @dc42 said in M486 processor for Cura?:

    One issue I have heard of when using M486 with Cura is that Cura apparently labels all support with the same MESH comment. So if you cancel an object, the support for that object will continue to be printed, unless you cancel all support.

    THAT info I actually did manage to find during my searches. But I thank you for adding it.

    Silly, I went bonkers trying to figure out how to do this in "static testing", but had i just tested during an actual print the answer would have been "right there"... 🙂


Log in to reply