UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
Posted
· A bunch of things PostProcessingPlugIns and debug
PS:
- "def __init__(self) -> None:"
init doesn't return None, it actually doesn't return anything, so at some point having the "-> None" will break your code.
- if you make your function-entry comments into strings, python will automatically use them as the function's __doc__ property, so that they are documented by help(function_name, and will the life of anyone who looks at your code as well as your own a lot easier 🙂
> ipython
Python3.7.1(default,Dec102018,22:54:23)[MSC v.191564 bit (AMD64)]Type'copyright','credits'or'license'for more information
IPython7.2.0--An enhanced InteractivePython.Type'?'for help.In[1]:def getSettingDataString(self):...:""" You may either use the normal getSettingDataString function or the getSettingDataStringWithInfo
...: the latter will add a comment setting in which you can enter any relevant information
...: you want to insert at the beginning of the GCode file """...:pass...:In[2]: help(getSettingDataString)Help on function getSettingDataString in module __main__:
getSettingDataString(self)You may either use the normal getSettingDataString function or the getSettingDataStringWithInfo
the latter will add a comment setting in which you can enter any relevant information
you want to insert at the beginning of the GCode file
In[3]:
If you'd like to experiment with gcode without always having to remember the gcode names ... it's very preliminary, I've only been hacking at it for a few hours: https://github.com/kfsone/pymcode. If you have a UM3, there's a "ultimaker3.py" script you can run that drops you into an ipython repl with "um3" configured as a connection to your printer and "ops" having all of the command aliases. Or you can then type "repl()" and it will go into a mode where you can basically either type '"M104' to send raw gcode, or you can just use the command names:
🚀 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 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!
Recommended Posts
kfsone 5
PS:
- "def __init__(self) -> None:"
init doesn't return None, it actually doesn't return anything, so at some point having the "-> None" will break your code.
- if you make your function-entry comments into strings, python will automatically use them as the function's __doc__ property, so that they are documented by help(function_name, and will the life of anyone who looks at your code as well as your own a lot easier 🙂
If you'd like to experiment with gcode without always having to remember the gcode names ... it's very preliminary, I've only been hacking at it for a few hours: https://github.com/kfsone/pymcode. If you have a UM3, there's a "ultimaker3.py" script you can run that drops you into an ipython repl with "um3" configured as a connection to your printer and "ops" having all of the command aliases. Or you can then type "repl()" and it will go into a mode where you can basically either type '"M104' to send raw gcode, or you can just use the command names:
Cmd> "M105 Cmd> set_bedtemp 65 Cmd> "T0 Cmd> set_hotendtemp 200 Cmd> wait_hotendtemp 190 Cmd> go
There's a "help" command to list the repl commands.
Link to post
Share on other sites