Jump to content

Recommended Posts

Posted (edited) · Settings in exported gcode name or to octoprint

I find myself sometimes doing tests where I vary the fan speed or temperature and then send the print to octoprint.  I have to remember to name each file something different when I do that so that I don't accidentally overwrite a previous generated gcode.  It would be great to be able to put settings into the name as variables similar to the below where the variable setting is 2 underscores, setting name, and then 2 underscores.

 

SimpleBox-ET__EXTRUDERTEMP__-FanSpeed__FANSPEED__

 

When the gcode is exported or sent to octoprint, the name would be

 

SimpleBox-ET205-FanSpeed100.gcode

 

I can dream anyway 🙂

Edited by Adam324
  • Link to post
    Share on other sites

    Posted (edited) · Settings in exported gcode name or to octoprint

    I think you can do that with a small modification of the @ahoeben custom printjob naming  plugin. Perhaps you could ask him to add in the list of the available parameters these two options..  https://github.com/fieldOfView/Cura-CustomJobPrefix

     

    You just need to add two lines in the PrintInformationPatches.py file in the relacement section :

                "{material_print_temperature}": self._abbreviate_number(extruder_stack.getProperty("material_print_temperature", "value")),
                "{cool_fan_speed}": self._abbreviate_number(extruder_stack.getProperty("cool_fan_speed", "value")),

     

    custom_job_name.JPG

    Edited by Cuq
  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • Help Us Improve Cura – Join the Ultimaker Research Program
        🚀 Help Shape the Future of Cura and Digital Factory – Join Our Power User Research Program!
        We’re looking for active users of Cura and Digital Factory — across professional and educational use cases — to help us improve the next generation of our tools.
        Our Power User Research Program kicks off with a quick 15-minute interview to learn about your setup and workflows. If selected, you’ll be invited into a small group of users who get early access to features and help us shape the future of 3D printing software.

        🧪 What to Expect:
        A short 15-minute kickoff interview to help us get to know you If selected, bi-monthly research sessions (15–30 minutes) where we’ll test features, review workflows, or gather feedback Occasional invites to try out early prototypes or vote on upcoming improvements
        🎁 What You’ll Get:
         
        Selected participants receive a free 1-year Studio or Classroom license Early access to new features and tools A direct voice in what we build next
        👉 Interested? Please fill out this quick form
        Your feedback helps us make Cura Cloud more powerful, more intuitive, and more aligned with how you actually print and manage your workflow.
        Thanks for being part of the community,

        — The Ultimaker Software Team
        • 0 replies
      • Cura 5.10 stable released!
        The full stable release of Cura 5.10 has arrived, and it brings support for the new Ultimaker S8, as well as new materials and profiles for previously supported UltiMaker printers. Additionally, you can now control your models in Cura using a 3D SpaceMouse and more!
          • Like
        • 18 replies
    ×
    ×
    • Create New...