#EXECUTABLE_BLOCK_START

1 messages · Page 1 of 1 (latest)

trim sonnet
#

I'm trying to find how to remove the headed bed and nozzle temperature settings from the GCode:
; EXECUTABLE_BLOCK_START
M486 S0 A"Cube_id_0_copy_0"
M486 S-1
M73 P0 R6
M190 S90 ; set bed temperature and wait for it to be reached
G10 S240 ; set nozzle temperature
;TYPE:Custom

I'm using Duet / RepRap which has been targetting to depreciate G10 for this use. I am using the Generic Tool Changer profile using a Duet 3.

Since there is no tool selected this will only generate an error and won't actually turn on a tool.
Tool heating is being handled in the Printer Start GCode. I'd prefer to use the current M568 P{toolNum} S{print_temp} R{standby_temp} A{heater_state}

I want to use an M140 to set a target Bed Temperature, then move on to initializing the other tools and once everything is ready for homing then wait for the M190 target temperature. This makes start-up printing much faster.

I just can't find where to turn these 2 settings off between EXECUTABLE_BLOCK_START and TYPE:Custom
Using OrcaSlicer v2.3.1

velvet tendon
#

if i remember its somethiing like this
G10 P1 R140 S205 ; set standby and active temperatures for tool 1

#

do you have orca slicer set to RRF

velvet tendon
trim sonnet
#

The Tools are all setup and I have things working in other slicers, just trying to migrate to OrcaSlicer.
I have 3 tools identified in the Printer Settings.

The issue is that OrcaSlicer is placing this G10 & M190 command in from somewhere into this EXECUTABLE_BLOCK_START. I am unable to find where it's coming from.

I have the print settings setup to perform the M568 as needed in the Printer Settings > Start GCode.

The G10 isn't a concern as it's not going to do anything but generate a benign error in this case, though I have found bugs with using G10 for temperature settings during prints likely due to Reprap moving towards being depreciated in favor of M104 / M568. However, the M190 does stop the print until it's completed.
https://docs.duet3d.com/en/User_manual/Reference/Gcodes

I can remove them manually, but would like to be able to send the prints directly to the printer.
I'm just trying to get these unnecessary GCodes occurring in this EXECUTABLE_BLOCK_START from being added.

velvet tendon
#

do you have orca slicer set to RRf

trim sonnet
velvet tendon
#

ok

#

what slicer are you using that is working?

trim sonnet
#

IdeaMaker / Simplify3D

velvet tendon
#

ok ive used S3D with RRF you should beable to copy the start gcode from S3D and paste it into orca

#

icluding the tool changing

trim sonnet
#

Well I have things working. Just trying to get after those erroneous GCodes in the EXECUTABLE_BLOCK_START.

#

I have been removing them manually, but that stops me from being able to send directly to the printer through the slicer.

velvet tendon
#

is your orca "start gcode" the same as your S3D

#

?

trim sonnet
#

My start code doesn't appear to have any impact on that code block.

velvet tendon
#

can you post a 3mf file

trim sonnet
#

Okay. I think I just discovered if I include the M190 manually in the Start GCode it will remove it from the upper part. I suppose then I have to do some fake out of the G10 to get it to remove that as well?

#

Okay. So I did another update to utilize G10 for setting the extruder temp vs M568 and this appears to pull the statement out of the EXECUTABLE_BLOCK_START. I can live with that for now.

#

Thank you for the assistance!

velvet tendon
#

no problem , i used multipul tools with rrf but i manually swap them and use macros to do all the changes

trim sonnet
#

Yeah - I was going to utilize a Print_Start Macro, but it appears OrcaSlicer would be fighting things a bit with how it's handling things. Oh well at least I can get it to work now!