Hi,

I've added the option for sending G-Codes to Duet and already created a pull request for it (https://github.com/prusa3d/Slic3r/pull/1051)
Let's see if Prusa will overtake it into their repo.

If someone is interested in testing it can be cloned from https://github.com/mloidl/Slic3r/tree/duet

Best regards,
Martin

mloidl created this issue in prusa3d/Slic3r

closed Added possibility for upload to Duet #1051

@fcwilt

I have a magnetic build plate (not from buildtak) in use with a BL-Touch without problems so far

PrusaSlicer will add a M600 command when requesting a colorchange

If you're using Firmware 2.02 or later then filament-change.g is called if existent. Otherwise like M226 pause.g is called.

My workflow is at follows:

• Initiate Pause (M600 calling pause.g)
• unload the Filament (M702)
• load the new Filament (M701)
• resume the print (M24)

Edit:
for reference, these are my macros

; pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool on Tue Feb 20 2018 18:59:20 GMT+0100 (CET)
M83            ; relative extruder moves
G1 E-10 F3600  ; retract 10mm of filament
G91            ; relative positioning
G1 Z5 F360     ; lift Z by 5mm
G90            ; absolute positioning
G1 X0 Y0 F6000 ; go to X=0 Y=0''

;filaments/PETG/load.g
M291 P"Please wait while the nozzle is being heated up" R"Loading PETG" T5 ; Display message
 G10 S225 ; Set current tool temperature to 225C
 M116 P0; Wait for hotend temperature to be reached
 M291 P"Feeding filament..." R"Loading PETG" T5 ; Display new message
 G1 E5 F600 ; Feed 10mm of filament at 600mm/min
 G1 E40 F3000 ; Feed 45mm of filament at 3000mm/min
 G1 E55 F250 ; Feed 55mm of filament at 250mm/min
 G4 P1000 ; Wait one second
 G1 E-5 F1800 ; Retract 5mm of filament at 1800mm/min
 M400 ; Wait for moves to complete
 M292 ; Hide the message

;filaments/PETG/unload.g
M291 P"Please wait while the nozzle is being heated up" R"Unloading PETG" T5 ; Display message
 G10 S225 ; Heat up the current tool to 225C
 M116 P0; Wait for the hotend temperature to be reached
 M291 P"Retracting filament..." R"Unloading PETG" T5 ; Display another message
 G1 E10 F300;
 G1 E-10 F4500 ; Retract 30mm of filament at 4500mm/min
 G1 E-70 F3000 ; Retract 70mm of filament at 3000mm/min
 M400 ; Wait for the moves to finish
 M292 ; Hide the message again

As already mentioned by @Mordekain, the latest Slic3r PE Release 1.41.0 contains the duet upload functionality.
Unfortunately the timestamps for uploaded files are not set correctly. This has been fixed and is already submitted to the master branch, so it will be part of the next bug fix release.

@Phaedrux I thought about it. Since the Upload dialog is the same for OctoPrint and for Duet i would not like to change to a radio button or to a dropdown because this would add a 3rd option (None).
I'll give the second checkbox a try. This would mean the dialog would look the same for OctoPrint as for now. For Duet upload there would be two checkboxes. When ticking one the other one will be deselected automatically.

Unforunately i'm currently not able to compile the source. Will need to investigate.

@jens55
'X' on the right upper corner is standard in Windows. This is not true for e.g. Mac OS X (left top corner). Also most Linux WM can be configured in a way the user want it.

DWC 2 is build around Material Design. This is the reason for the location of the 'X' Button. See https://material.io/components/dialogs/#full-screen-dialog for the specification.

IMO the correct PA value is where YOU get the best results.

I'm having the same extruder on a Hypercube Evolution and the best PA value is exactly 0.1 for 'Spectrum PETG'.

I used the same method you did to get the PA-Value.

I‘m sorry to hear that, but it was worth a try.

@Phaedrux Seems that there is currently a large refactoring in progress. So i'll have to wait until this is finished, otherwise i'm not able to merge it.
This is the commit (not on master yet) https://github.com/prusa3d/Slic3r/commit/4fa874904e6ec54591ce7783d83722c463748bfd

When the refactoring is done i'll try to implement the start simulation action.

0 vojtechkral committed to prusa3d/Slic3r

Print host improvements: presistent path & start print, bugfixes
Fixes #1219
Fixes #1004
Fixes #1106
Fixes #1173

No print done so far, but clicked through the menus executed some macros and did a simulation.
No problems so far.

Simulated time was shown during the already simulated print after pressing "Simulate again".

I will do a real print in the evening.

Tested on a PanelDue: v2-4.3"

The simulated times left seems be to shown correctly after a print with 3.3.0-rc3.
Thanks a lot @mfs12 for the fix.

@mfs12 said in PanelDue Firmware 3.3.0-rc2 released:

slicer

Just saw your answer after pressing submit.
Your suggestion would be fine, but since slicerTime (job:timesLeft:slicer) is not a constant value this would lead to RRF changes too.

Edit:
I think i'm wrong. printTime in M36's response seems to be the slicer time, so it would be possible.

The current fields in the object model should not be changed, since they are fine and logical.
Simulated time is a static attribute of a file like file size, file name, .... both in M36 and in the M409 K"job" response (note: it's in the file structure => job:file:simulatedTime).

Best would be to extend the timesRemaining struct by adding a simulation field. This would not change the current behavior for backward compatibility but let RRF calculate the remaining time based on the simulated times as it is already done with the slicer time.

@mfs12 Yes. Maybe it's a misunderstanding from my side. I assumed the simulated time is decremented during the print because it's in the "Time left" section. Before v3.3 all times (layer, filament, ..) were decrementing too.

Hi,

The simulated time left is still not being recalculated during a print.

Both times (simulated & slicer) were nearly identical at the beginning of the print.

Versions

• RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
• PanelDueFirmware 3.3.0-rc2 on v2-4.3. (same problem on 3.3.0-rc1)

I can confirm the start print / simulate print problem from 3.3.0-rc1 is fixed with 3.3.0-rc2

Thanks a lot @mfs12 for the fast fix.

@dc42 SD Card in the Duet. I have no SD-Card in the PanelDue inserted.

Now i've tried to do a real print an got an error because the file was not found.
.

Seems PanelDue is not sending the full path to RRF. The full path of the file was "0:/gcodes/Schuhloeffel_Hacken_0.2mm_PLA_2x.gcode".
Also renaming the file to a shorter filename without having a 'dot' in between did not work.

When starting the print from DWC the Times left (Simulated and from Slicer) are shown correctly but simulated time is never updated during the print.

If it's relevant:

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.3 (2021-06-15)
Duet WiFi Server Version: 1.26

No print done so far, but clicked through the menus executed some macros and did a simulation.
No problems so far.

Simulated time was shown during the already simulated print after pressing "Simulate again".

I will do a real print in the evening.

Tested on a PanelDue: v2-4.3"

IMO the correct PA value is where YOU get the best results.

I'm having the same extruder on a Hypercube Evolution and the best PA value is exactly 0.1 for 'Spectrum PETG'.

I used the same method you did to get the PA-Value.