Duet 3 and g-code procedures and slicing

[Phaedrux]

@monster said in Duet 3 and g-code procedures and slicing:

LuckyTune.g

Sorry, I forgot that one.

; 0:/macros/Tunes/LuckyTune.g
; Lucky tune to start print off on the right foot
;

M400 ; Empty the movement buffer
M300 P200 S1000
G4 P210
M300 P200 S1250
G4 P210
M300 P200 S1100
G4 P201
M300 P200 S2000
G4 P201
M300 P200 S1500
G4 P201
M300 P200 S1000
G4 P201
M300 P200 S1300
G4 P201
M300 P200 S1000
G4 P201
M300 P300 S1500
M400 ; Empty the movement buffer

[monster]

@Phaedrux why do you use M400 often? I actually don't get why emptying of the buffer needed as command cause I though while one movement command is being executed then next command in script will not start. Which in turn means when next command is being executed all the movement of previous one is done. Or do I get some concept wrong? Perhaps movement buffer is not something I picture myself...

[monster]

@Phaedrux said in Duet 3 and g-code procedures and slicing:

Slicer start gcode

Another piece of setup I do not understand fully.
what is "Slicer start gcode"? (as well as "Slicer End Gcode")
Is it some script that defined in slicer software to be included in each g-code to print?
And then "0:/sys/PrimeNozzle.g" & "0:/sys/StartGCode.g" seems located in your printers files system, right? That means your slicer software is counting on presence of those files in printer, correct?
Or is "Slicer start gcode" an another script in printer that being called right before sliced model to be printed?

There are so many unknown things here I must admit. For example is there a list of standard scripts like start.g stop.g homex.g etc... that getting called in some occasions?

[monster]

@monster said in Duet 3 and g-code procedures and slicing:

@Phaedrux said in Duet 3 and g-code procedures and slicing:

Slicer start gcode

Another piece of setup I do not understand fully.
what is "Slicer start gcode"? (as well as "Slicer End Gcode")
Is it some script that defined in slicer software to be included in each g-code to print?

Got it! It is in printer settings in Cura!

[Phaedrux]

@monster said in Duet 3 and g-code procedures and slicing:

@Phaedrux why do you use M400 often? I actually don't get why emptying of the buffer needed as command cause I though while one movement command is being executed then next command in script will not start. Which in turn means when next command is being executed all the movement of previous one is done. Or do I get some concept wrong? Perhaps movement buffer is not something I picture myself...

Probably unnecessary for the most part, done mostly out of habit during troubleshooting. Basically M400 just says wait until the movement queue is complete up to this point before executing what comes after.

For the music bits I found M400 before helped it play the tones more consistently without stutters, but I haven't tested that in quite some time.

[Phaedrux]

@monster said in Duet 3 and g-code procedures and slicing:

what is "Slicer start gcode"? (as well as "Slicer End Gcode")
Is it some script that defined in slicer software to be included in each g-code to print?

Yes that's right. Most slicers have a section of text boxes that allow you to enter custom gcode commands that will get inserted at certain locations, such as before the print starts, when the print is finished, at layer changes, at tool changes, etc.

Example from PrusaSlicer:

@monster said in Duet 3 and g-code procedures and slicing:

And then "0:/sys/PrimeNozzle.g" & "0:/sys/StartGCode.g" seems located in your printers files system, right?

That's right. M98 allows you to call a macro found on the Duet SD card, either in the macros or sys folder.

@monster said in Duet 3 and g-code procedures and slicing:

For example is there a list of standard scripts like start.g stop.g homex.g etc... that getting called in some occasions?

Yes, there is.
https://duet3d.dozuki.com/Wiki/Setting_up_macro_files_for_common_tasks
https://duet3d.dozuki.com/Wiki/Macros

[resam]

@monster said in Duet 3 and g-code procedures and slicing:

There was a network error: 203 Error transferring ....

Apparently Duet3 with SBC does not provide the same API as RepRapFirmware 2 and previous. This means all the slicer integrations are broken - I know of at least PrusaSlicer, and the Cura plugin (I am the maintainer if it).

Looks like once it is RRF that broke compatibility with slicers - usually it is slicers who break magic comments and other things

@dc42 @chrishamm any thoughts on this topic? It would be really nice if the well-known RRF HTTP API with rr_connect etc. would also be supported on Duet3+SBC!
It's not only slicers, also lots of other scripts, timelapse tools, and other integrations were relying on this API.

[monster]

@Phaedrux said in Duet 3 and g-code procedures and slicing:

@monster said in Duet 3 and g-code procedures and slicing:

For example is there a list of standard scripts like start.g stop.g homex.g etc... that getting called in some occasions?

Yes, there is.
https://duet3d.dozuki.com/Wiki/Setting_up_macro_files_for_common_tasks
https://duet3d.dozuki.com/Wiki/Macros

Priceless!

[monster]

I can't remember where did I read that by now.
But back then when I was choosing controller I did read somewhere that when Duet 3 used with Pi it (or I guess Pi) can do slicing. And if my memory not mistaking that was saying about actually Cura slicer in Pi.

Is it something I could try? I mean try to use that slicer.
Hope it is not to difficult to setup and use. May be that could solve my problem...

[Phaedrux]

Yes you could run a slicer on the pi, but it will be a bit slower than on your PC and I don't think it would solve any of your problems.