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:
Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more.
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
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