Start / Stop S3D SCRIPT / G-CODE

noblebran

@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:

@noblebran said in Start / Stop S3D SCRIPT / G-CODE:
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:

@noblebran

Certainly post your files here.

We all are glad to check them over and make suggestions.

Frederick

My start in my slicer:
G28; HOME
;G32 (REMOVE SEMI IF YOU WANT TO REMAP)
G29 S1; USE STORED MESH
G92 E1; SET EXTRUDER TO 1
Does your homing script set the Z=0 datum?

And why are you not waiting for temps to reach their set points?

Frederick

When it comes z=515. 0 would right at the print surface. I have found on the deltas this is the correct way?

In the config.g it calls out for the temps to reach their set points.

fcwilt

@noblebran said in Start / Stop S3D SCRIPT / G-CODE:

When it comes z=515. 0 would right at the print surface. I have found on the deltas this is the correct way?

Don't know what you mean.

In the config.g it calls out for the temps to reach their set points.

Config.g? You mean the main config.g?

Frederick

noblebran

@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:

Don't know what you mean.

0 is the print surface, so when I home z=515 and when it prints it’s .xxxx

@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:

Config.g? You mean the main config.g?

Yes sir.

fcwilt

@noblebran said in Start / Stop S3D SCRIPT / G-CODE:

Config.g? You mean the main config.g?

Yes sir.

How can you be waiting for hotends/bed to reach temps when you cannot, as a practical matter, set them in config.g?

Frederick

noblebran

@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:

@noblebran said in Start / Stop S3D SCRIPT / G-CODE:

Config.g? You mean the main config.g?

Yes sir.

How can you be waiting for hotends/bed to reach temps when you cannot, as a practical matter, set them in config.g?

Frederick

It must be done in the slicer? I choose the bed and temp setting, after I slice it in S3D, it has the code in the file (part GCODE file).

fcwilt

@noblebran said in Start / Stop S3D SCRIPT / G-CODE:

How can you be waiting for hotends/bed to reach temps when you cannot, as a practical matter, set them in config.g?

Frederick

It must be done in the slicer? I choose the bed and temp setting, after I slice it in S3D, it has the code in the file (part GCODE file).

No, it does not have to be done in the slicer.

I do it using the filament handling feature in the DWC.

I have entered in a number of different filaments that I use into the DWC.

For each filament entered there is a special config.g file created.

My start code is in a file named print_begin.g and is invoked from the slicer with M98 P"print_begin.g"

In that file I have (among other things) this:

T0							; select tool 0 so extruder commands below will work
M703							; configure selected filament (sets bed/extruder temps, extrusion multiplier)
; some other unrelated commands
M116							; wait for temps to reach set points

That M703 command invokes the special config.g file for the currently selected filament and in that file I have any commands I want unique to that filament and in that file I set, at a minimum, the bed temp, the hotend temp and the extrusion multiplier.

I have found this to be an effective way to set my temps and I can use different slicers easily as the start code is on the Duet, not in the slicer.

But this is just my way. You should do it in whatever way suits you the best.

Frederick

noblebran

@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:

@noblebran said in Start / Stop S3D SCRIPT / G-CODE:

How can you be waiting for hotends/bed to reach temps when you cannot, as a practical matter, set them in config.g?

Frederick

It must be done in the slicer? I choose the bed and temp setting, after I slice it in S3D, it has the code in the file (part GCODE file).

No, it does not have to be done in the slicer.

I do it using the filament handling feature in the DWC.

I have entered in a number of different filaments that I use into the DWC.

For each filament entered there is a special config.g file created.

My start code is in a file named print_begin.g and is invoked from the slicer with M98 P"print_begin.g"

In that file I have (among other things) this:
T0							; select tool 0 so extruder commands below will work
M703							; configure selected filament (sets bed/extruder temps, extrusion multiplier)
; some other unrelated commands
M116							; wait for temps to reach set points
That M703 command invokes the special config.g file for the currently selected filament and in that file I have any commands I want unique to that filament and in that file I set, at a minimum, the bed temp, the hotend temp and the extrusion multiplier.

I have found this to be an effective way to set my temps and I can use different slicers easily as the start code is on the Duet, not in the slicer.

But this is just my way. You should do it in whatever way suits you the best.

Frederick

Thank you sir, I find I like to 'master' one slicer and I guess I almost put all my eggs in one basket so to speak. I will certainly take advantage of the way you are doing it but I want to get successful at printing the way I am now. I can say my load and unload macros work, ha ha... baby steps

Again thank you for helping!

Phaedrux

@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:

when you cannot, as a practical matter, set them in config.g?

Well, you can set the nozzle and have it take effect with a G10 and T0 to select the tool you can get it to heat right at boot. Whether or not you SHOULD is another matter entirely.

fcwilt

@phaedrux said in Start / Stop S3D SCRIPT / G-CODE:

@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:

when you cannot, as a practical matter, set them in config.g?

Well, you can set the nozzle and have it take effect with a G10 and T0 to select the tool you can get it to heat right at boot. Whether or not you SHOULD is another matter entirely.

Which is why I said practical. Editing config.g just to specify different temperatures is not what I would call practical.

But that's just me.

Frederick

Phaedrux

@fcwilt In that case, yes you're completely right. It's very impractical and ill advised.

noblebran

@phaedrux @fcwilt

Thank you both!

fcwilt

@noblebran said in Start / Stop S3D SCRIPT / G-CODE:

@phaedrux @fcwilt

Thank you both!

Glad to help in anyway we can.

And if we cannot help we will try our best not to mess things up too badly.

Frederick

noblebran

@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:

@noblebran said in Start / Stop S3D SCRIPT / G-CODE:

@phaedrux @fcwilt

Thank you both!

Glad to help in anyway we can.

And if we cannot help we will try our best not to mess things up too badly.

Frederick

ha ha thats all I can ask for!

Now it is just fine tuning...