@LB The space issue I mention is space on the display and not storage -> since PanelDue is a touch screen, each button and action needs enough space to ensure you don't touch the wrong button. It also feature only a 800x480 pixel display (5i and 7i versions).
With the current layout PanelDue only have space to display 3 estimations
A print job that was simulated, have its estimated time saved to the gcode file itself specifically to prevent having to simulate them again.
@User3D Only the Simulation time gets saved; the other estimates (filament, layer, file progress) are calculated while printing and is not saved as these are constantly recalculated and change often. Rerunning the print, can yield different estimations (especially when a change in flow/feed rate was commanded).
@medicusdkfz As mentioned in the quote, "DWC can also display 2 extra estimations" -> DWC is Duet Web Control (the interface you run in your browser when connected over the network - ethernet or wifi). PanelDue is unable to currently show these estimations due to a lack of space. While the 7i is larger than the 5i, they have the same number of pixels.
Perhaps take a look at https://github.com/frank26080115/PanelDueSplashMaker
While it is old, and not updated recently, it is still working even with the latest firmware versions. Simply go to its folder "release_binary" and download the file.
Place the file in an easy to access location and run it (I think it will download the Bossa and bmp2c-escher3d binaries automatically, on first run). It provides a simple to use interface:
The last step is what to do with the resulting firmware. If you want to save it, (for example to upload it with DWC in latest version firmwares, to flash it from ReprapFirmware), click the Save Resulting Firmware and choose your location. If you have the PanelDue directly connected to your (you might still have to save it), you can use the "Final Firmware Binary File Path" and its buttons to flash it (have not used this direct flashing).
This is what I use to create the splash screens for all my various printers.
For the Unload command (similar to the M600), you can set that in your PrusaSlicer's Tool Change gcode, the command for that would be: M702 (I guess you would want this prior to M600).
Another option is to insert the M702 in your M600 macro (filament-change.g in /sys). This will automatically do the Unload for you.
Regarding the the automatic cooldown, I have not seen any way to do this yet. For me, I am typically close to the printer while printing, and especially if there is a need to change filament, I am on standby for it (so the filament don't cook in the nozzle).
Ok my problem was solved, and I further improved my script (I called it duet-tool-change-strip.py)
#! /usr/bin/python3-64
# duet_toolchange-strip.py
import fileinput
import re
import sys
#first we define our regular expressions for a match
extruder_0_pattern = re.compile('^T0') #the first of this is kept
extruders_other_pattern = re.compile('^T([0-9])+') # match any extruder number (if you define 100, in PS, you can use all 100 or even more)
empty_line = re.compile('^$') #we are stipping empty lines
temp_set = re.compile('^M109 S([0-9]+)') #match the deprecated way to set a temperature
temp_set_2 = re.compile('^M104 S([0-9]+)') #match second deprecated way to set temperature
acceleration = re.compile('^M204 S([0-9]+)') #convert to Duet acceleration set
#this variable to is to ensure it still work for single extruder prints
print_have_started = 0
for line in fileinput.input(inplace=True):
if extruders_other_pattern.match(line):
if (extruder_0_pattern.match(line) and print_have_started == 0):
print(line.rstrip("\n")) #we keep the Tool as is.
continue
else:
print_have_started = 1
m = extruders_other_pattern.match(line)
extruder_nr = m.group(1)
print('M291 R"Tool Change" P"Tool #%s " S1 T30\nM600' % extruder_nr)
continue
else:
if not empty_line.match(line):
if temp_set.match(line):
m = temp_set.match(line)
print("G10 P0 S%s" % m.group(1))
continue
if temp_set_2.match(line):
#void we don't want or need this line.
m = temp_set_2.match(line)
print("G10 P0 S%s" % m.group(1))
continue
if acceleration.match(line):
m = acceleration.match(line)
print("M204 P%s" % m.group(1))
continue
print(line.rstrip("\n")) #this is the default - we keep the line as is, if it is not empty
So this script works as explained in a previous post, and now also correct the temperatures and acceleration for RRF. Note that PS adds its heatup command after your own starting Gcode, so if extruding in your starting, it is best to ensure the printer is heated before it.
The acceleration, while PS generates the M204 commands, RRF does not know the S-parameter, here I convert the S to a P for print acceleration..
Both 104 and 109 commands are converted to G10 commands, only setting the S (active temperature), so if you have set the standby, it is kept.
The issue I had, was simply not calling Python directly before the script in the Print Settings > Post Processing scripts. I have used Python 3.8.5, which I placed at: C:\Python38\python.exe (if yours is installed in the default place, instead of wrapping the path in quotes, you should place a "!" before any space - https://manual.slic3r.org/advanced/post-processing). this gave me the entry in my Post-processing scripts as <path to python.exe>\python.exe <path to the script>\duet-toolchange-strip.py;
Some people place the script in a subfolder in their PrusaSlicer installation, that can be overwritten on a new version. Place it in a safe location.
As to a license for the above code: Public Domain. Modify, adapt, distribute as needed.
There may be more efficient ways to do the same.
@T3P3Tony Thank you for your reply.
I am trying to go with option 1: creating a post process. I have a post-process that works directly in my command line, but having trouble getting it to work directly from PS (I have both a Perl and Python version). I have create support post in their support forum, as well as a issue in PS's github.
When I get it working, I plan to post it here. My current code actually waits for a T1 (or higher tool number), before actually starting to work (this assumes the correct first filament is inserted, as I always do) which have the by-product of not doing anything unless a second tool is required.
I also plan to use it to process a few other commands Duet have issue with (like PS's temperature setting, acceleration and other I might find later).
Option 2 might have worked easier if the virtual tools could be hidden from DWC and PanelDue.
So all my printers have single extruder/hotend setups. With S3D I previously made a few print files (very manual process), to use different filament on the same layers, using simple M600 command to change the filament (from the video by Make Anything on YouTube).
Most modern slicers now allow a form to create the gcode files for this (including PrusaSlicer, with its "Single extruder multi material").
However with that setting on, it is still generating T commands (for tools that don't exist). While I can easily go through and remove them one by one (a lot less work than what I did for S3D), it is still a manual process of editing the gcode.
I have now attempted to create a few virtual tools in RRF, but it is showing all of them on the PanelDue and DWC, which is not ideal.
Ideally I want a message prior to any filament change specifying the tool, from the slicer, prior to me having to change the filament (using M291). So basically anytime there is a T command where it is higher than -1 (is used to deselect), simply show a message for a few seconds (non blocking, so that M600 can cause the pause, displaying the new tool number) and then run the M600, without actually going to the new tool (still use T0). How would I go about configuring this?
According to your description for home limit locations, mine is setup very similar (X min, Y min, Z max - stall detected). Z is also allowed to go below 0.
When I set the origin of the stock, I have a macro that simply runs G10 L20 P2 X0 Y0. I run this when I am happy with the current XY as being on top where the cutting should be, and it will show as XY 0 after running (also a good idea to set G54 so that you switch to the first work offset - mine is set in my config, so I am always in it).
Right after the probe, to determine the top of the stock, I run G10 L20 P1 Z24.25 - The Z24.25 is my measured height of the probe block.
The idea of the Work coordinates is that while the machine knows exactly where the spindle is, it can run relative commands related to an origin. As long as the stock does not cross to the outside of the limit switches, it should work as expected.
I have done this upgrade: in short I wanted a bigger nozzle, for improved flow (since the plus is quite big, and using a 0.4mm nozzle will simply take days to print anything bigger than I already could), and have a unified interface across all my machines.
I opted for the Duet Maestro for a few reasons: 1) it have ethernet (I used an ethernet extension, to bring it to the outside; wifi is going to struggle to get in through the chassis); 2) it have sufficient ports and connectors for everything on the Ender 5 Plus; 3) it is not as expensive as a Duet Wifi; 4) improved BL Touch capabilities compares to the Wifi (installing and setting up the BL Touch was simple easy and straight forward - on posts in this forum, I noticed it is harder to do on a Wifi or Ethernet).
I designed a mounting plate, that fits the Ethernet port, and is used as a mounting point for the PanelDue case.
I mounted an E3Dv6 Volcano; using the Petsfang/Bullseye as a mount (extended with a different blower fan mount). This part caused me to lose about 5cm in X direction, and actually gains a few cm in Y, but it works nicely.
I also upgraded the extruder to a BMG, and it is working great.
When upgrading, it is important to have all mounts and parts printed before you start (unless you have an extra printer, but to save time).
The heatbed is the thing that draws the most current, the stock E5+ use a big mosfet board to handle this - I decided to keep using it (technically the Duets can handle the current, but it is near the limits). Note that the Z axis have a shallow angle in the threads (it keeps the bed where it is left), but increases the z steps per mm.
I have been running this configuration since early in the year, and working great.
Which Post Processor are you using?
The purpose of the Post Processor is to convert Fusion's native toolpaths, into gcode which your machine can understand. Since Duet is more meant for 3D printing, and does not support all cnc related codes, you should use a Duet compatible version of a Post Processor - this ensures the right commands and parameters are in the output (and nothing which will cause "Bad command" errors).
I have recently migrated from S3D to PrusaSlicer (Cura clone), for basically the same reasons as @arhi said. S3D was good, but have been surpassed by most, if not all, of the free slicers available. Next version of PrusaSlicer will have a bunch of new features, making it even better (ironing the top layer, painting supports and many others).
One area where S3D is better than PrusaSlicer, is the speed at which it slices. That said, a bunch of the features I use, are labeled as making slicing slower due to increased calculations (and is not available in S3D).
At this time, I am recommending moving away from from S3D.
I have a Wanhao D5S Mini which originally came with 3mm filament support. I have since upgraded it to use the E3Dv6 hotends, and have a bunch of hotends (3mm and 1.75mm versions), allowing me to switch out for different nozzle sizes and filament diameters (for 3mm I use the original geared extruder, and for 1.75mm I have a Bondtech QR extruder, also geared). Having the nozzles and everything ready makes switching out a lot easier (though it still take 20+ minutes for a switch - but no hot parts as would be the case when switching only nozzles).
Ultimately I find using 1.75mm more convenient. Other things that helped with my decision to get 1.75mm capability is the fact that 3mm in my country is getting phased out (no new printers use it, the companies that sell 3mm have very little options in colors - and there is only PLA). I still have many 3mm spools, and if I need something printed in a color I have in 3mm, I will use it until it is done.
The 3mm filament becomes brittle a lot easier than the 1.75mm (and removing the short pieces from a Bowden setup is bad).
Ok, the increasing of the jerk for the extruder sped things up, and estimations are now much more accurately. The pressure advance was enabled and configured at about the same time I switched from S3D to PS, so it might have something to do with it.
The bulges so far remained, though reduced in size. I am now trying it with wipe with retraction, to see if that makes any difference.
My config file is attached. config-e5p.g
@deckingman thank you for your reply, I was not aware of the different ways the Feedrate is used, though not specifically applicable to my issue.
So with separate retraction (PS) vs combined retraction (S3D) as the only noteworthy change (I am not convinced that this cause the issue). Based on my calculations for the time it would take to retract the 4mm of filament (for the Ender 5+ with a volcano hotend), I don't think it would cause this blob (and on the Di3 with Flexion, where retraction is only 1.9mm, I don't think), as it is barely 0.122 seconds (not taking jerk into account, only acceleration, deceleration and remaining distance at full speed).
Based on the above, I decided to turn on the "retract with layer change", and once again it creates a separate command for the retraction just before layer change (not in the same command).
I think I should do a test, by increasing the acceleration and max speeds for the extruder, and see if and how it affects this bulge.
EDIT: Found a post about BMG extruder acceleration and jerk vaues (https://forum.duet3d.com/post/81579), and a quote: "be aware that if you use pressure advance such a low e jerk value will slow down your printing speed" - mine is at 300, which apparently is very low.
While it is reasonable to conclude that the problem should then be with PrusaSlicer, the relevant gcode (at the time the bulges form) being processed by the Duet/RRF are just about identical to my eye.
A few obvious changes, as can be seen above, PS have G1 commands with only the F-feedrate parameter and then others to command the movement of an axis or extruder, while S3D combines the Feedrate into the first movement command. Now, I am not sure how this affects the Duet reading it, it seems that it should actually be identical results - maybe someone that looked at the firmware can explain if there is a difference in performance between the 2 ways.
Maybe also a thing to note, the bulges also happened before I tried to fix the timing, by adding the acceleration to the slicer, thus the M204 with incorrect parameter, is also not causing the bulges.
I have decided to migrate over from Simplify3D to PrusaSlicer, simply because S3D's update is now delayed to the point where many are asking if it will ever be released, and the free slicers are getting to the point where they are better, with improved features etc.
Ever since the switch, I was getting bulges at the start and end of each layer (this happens on all of my printers, all of which have been upgraded with Duet electronics: Duplicator 5S Mini [DuetWifi, Bondtech QR extruder, 800mm bowden tube, E3Dv6 hotend], Duplicator i3 [Duet Maestro, direct drive Flexion extruder], Ender 5 Plus [Duet Maestro, Bondtech BMG, 900mm bowden tube, E3D Volcano hotend]). I attempted to fix the issue with Pressure Advance settings, but found that the bulge did not disappear, but rather a gap formed before the bulge when increasing the PA value - once again, tested on all 3 printers.
I am not sure whether this issue is related to Duet or PrusaSlicer - if we find it is an issue in PS, I can report it there.
Having taken a closer look at the Gcode for a few of the models sliced in S3D vs PS, I see no obvious causes or differences; however I noticed that when printing, there is a noticeable delay between the end of a layer and the start of a new layer, when PS generated the gcode. I think that this dwelling/delay is causing the bulge.
Here is an example of a layer change by S3D:
G1 X84.868 Y99.227 E0.0669
G1 E-5.0000 F3000
; layer 6, Z = 1.800
; feature inner perimeter
G1 Z1.800 F1002
G1 X83.819 Y100.429 F12000
G1 E5.0000 F3000
G1 X87.052 Y94.363 E0.4939 F3600
Compared to PS layer change (on a different model, customizable_box_try2.gcode, full file is attached, which also shows settings used at the end):
G1 X225.782 Y131.958 F12000.000
G1 E4.00000 F3000.00000
M204 S1500
G1 F2400.000
G1 X228.266 Y131.338 E0.16433
M204 S1200
; before layer change
G1 Z13.750 F12000.000
; after layer change
G1 E-4.00000 F3000.00000
G1 X145.341 Y222.207 F12000.000
G1 E4.00000 F3000.00000
M204 S1500
G1 F2400.000
G1 X139.408 Y222.214 E0.38627
PS adds the acceleration changing commands in, but I don't think they do anything related to the issue (other than M204 not having an S-parameter). I also noticed that PS adds a bunch of empty G1 commands (no parameters) when doing thin walls (as can be seen at the end of the file), but the bulge happens on all layers.
Another thing I noticed is that PS estimations are off anywhere from 50% longer to more than double the estimated time. I know it is never perfect, but still S3D was off only about 20% (and it is not like I am using outrageous speeds, or even printing way too slow).
I added the G54 in the section "Other Settings" myself. Since it does not take further parameters, it simply does what it should.
The first part about G53 being machine coordinates, G54 WCS #1 etc are correct.
In my CNC I have the G54 already in the config.g to always use it (while Fusion supports multiple WCSs, I never needed more than 1). This ensures we are on WCS #1.
My macro for setting the XY origin then contains the line: G10 L20 P1 X0 Y0
The P1, will thus set WCS #1 (aka G54); Therefore, P2 will set WCS #2 (aka G55) etc.
Looking at the config, your printer is allowed to move at 200mm/s maximum speed, and the extruder is allowed to push filament at upto 60mm/s (note this is filament speed and 60 is high - that equates to 144.3mm^3 per second for 1.75mm filament, most hotends run at around 10mm^3 per second max).
This means that the config is not your limiting factor.
Typically the limiting factors are: what hotend do you have (some hotends have a theoretical maximum printing speed of 60mm/s at 0.2mm layer heights), what quality do you need (printing faster can reduce the quality of prints, if there are for example play in an axis)?
For my Ender 5+, I swapped out the hotend for a E3Dv6 Volcano, to get a bigger melting zone (thus increasing the filament flow rate), I then made use of a 0.6mm nozzle. This allows me to lay down more filament in the same amount of time (compared to my other printers). By ensuring that the axis are stiff and properly aligned, I am able to increase the printing speed significantly without losing quality (for example there is no ringing).
Another factor in getting a high print speed, is a high quality extruder that can push hard enough. Fast printing have increased pressure in the hotend, and it does not help when the extruder starts skipping steps or worse, grinding the filament.
I am running my CNC (simple 3 axis) on a DuetWifi and it works. As already said, the addons (PanelDue etc) are not CNC friendly, so there are various compromises that I made and workarounds that I continue to make to use it.
That said, the CNC originally came with a very basic controller, which required a computer (A RapsberryPi could work) to stream the gcodes to it, in order to use the CNC. I did not like that and for the price of a simple computer, with screen and accessories that can be used in a dusty environment, I could just as well buy and configure the Duet (with a PanelDue) to handle everything. Now that did mean that I could not start cutting when the machine arrived, and also I surrendered any warranty (I actually arranged at the seller to get a discount due to not taking the controller and stepper drivers).
On my machine the steppers are rated at over 2.5A/phase, but still fine when running them only at 80%. This is a very big consideration - if the builtin drivers don't supply enough current, it gets expensive to buy external drivers and you don't use the silent stepper drivers.
Mine was the 2nd Duet board setup I did, have done a few more since, and it takes time to get everything configured. The RRF configuration tool does not help in setting up the CNC. Recently when I switched over from version 2 to version 3 of RRF, I basically had to regenerate the whole configuration file, by reading the notes for each command and updating it to the new syntax. This took a whole afternoon.
The Duet is very good and it works for my CNC, however you should consider the time spent configuring and maintaining the configuration for the various firmware versions, to keep the machine running optimally.