Start / Stop S3D SCRIPT / G-CODE
-
@donstauffer said in Start / Stop S3D SCRIPT / G-CODE:
@fcwilt Interesting . Why do it as a call to files on the Duet? You do lose the Simpify3D script variable capability that way.
Yes you do but I haven't found that to be a problem.
For example, I handle required changes based on the current filament type by using the filament handling feature in the DWC.
When you select the current filament type to print it runs a config.g file unique to that filament type. In that file I put bed/hotend temperature settings, adjust the print speed and extrusion rate, etc.
I prefer keeping as much in the Duet as I can which makes using different slicers easier.
Frederick
-
@fcwilt I was thinking along those lines but I couldn't quite solidify those thoughts. Makes sense.
-
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
@donstauffer said in Start / Stop S3D SCRIPT / G-CODE:
@fcwilt Interesting . Why do it as a call to files on the Duet? You do lose the Simpify3D script variable capability that way.
Yes you do but I haven't found that to be a problem.
For example, I handle required changes based on the current filament type by using the filament handling feature in the DWC.
When you select the current filament type to print it runs a config.g file unique to that filament type. In that file I put bed/hotend temperature settings, adjust the print speed and extrusion rate, etc.
I prefer keeping as much in the Duet as I can which makes using different slicers easier.
Frederick
So I don't end up putting the code in the S3D software anymore, it is built into the duet? How do I make sure it comes down, the probe touches and prints from that 'mesh/surface'?
There is also a configoveride now that doesn't have all the information that the config.g file does. I guess I need to make sure it uses that first when making a print. Maybe I need a new slicer?
-
@noblebran said in Start / Stop S3D SCRIPT / G-CODE:
So I don't end up putting the code in the S3D software anymore, it is built into the duet? How do I make sure it comes down, the probe touches and prints from that 'mesh/surface'?
That is entirely up to you. Many folks do, I don't. I found I prefer to have all of my print start and print end code in the Duet.
Everything that needs to happen at the start of the print is in the code I place in my print_begin.g file which includes:
- homing XYZ
- bed leveling
- setting bed/hotend temps,
- waiting for temps to reach the set points
- priming the extruder
- pausing to allow user to clean hotend/bed
- setting the Z=0 datum
- loading the height map
And anything else that I might want to have happen at the start of a print.
There is also a configoveride now that doesn't have all the information that the config.g file does. I guess I need to make sure it uses that first when making a print. Maybe I need a new slicer?
The file config-override.g is processed at boot time when config.g is processed.
There is nothing you need to do with config-override.g at print time.
You can use any slicer you want as I sometimes do.
My approach doesn't care as I simply setup each slicer to call my code at the start and end of a print. My code does not change if I change which slicer I use.
Frederick
-
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
The file config-override.g is processed at boot time when config.g is processed.
There is nothing you need to do with config-override.g at print time.Okay this is the same as Smoothieware on the MKS Base. Thank you!
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
That is entirely up to you. Many folks do, I don't. I found I prefer to have all of my print start and print end code in the Duet.
Everything that needs to happen at the start of the print is in the code I place in my print_begin.g file which includes:homing XYZ
bed leveling
setting bed/hotend temps,
waiting for temps to reach the set points
priming the extruder
pausing to allow user to clean hotend/bed
setting the Z=0 datum
loading the height mapAnd anything else that I might want to have happen at the start of a pring.
Thank you my friend. I’m trying to figure all this out, so I appreciate your patience. If there is anything you can share with me as far as code to get me started I’d appreciate it. I know you don’t have a delta so things will be different but I have some things I promised to print (my director) and then my printer burnt out and I’m in a rush.
I have a new surface and hot end and don’t want to be smashing into it. Maybe I put a piece of cardboard over it or something. But anything is greatly appreciated and I appreciate your patience.
-
@noblebran said in Start / Stop S3D SCRIPT / G-CODE:
homing XYZ
bed leveling
setting bed/hotend temps,
waiting for temps to reach the set points
priming the extruder
pausing to allow user to clean hotend/bed
setting the Z=0 datum
loading the height mapIf there is anything you can share with me as far as code to get me started I’d appreciate it.
Glad to help in anyway I can.
I've listed the primary things that need to get done before a print and thus my print_begin.g file has the commands needed to do those things.
My file also has some code that is just checking to be sure conditions needed for printing are met.
Perhaps if you look back at my print_begin.g file that I posted it will make more sense.
If not ask about any part of it - I can create a simpler version.
Frederick
-
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
Perhaps if you look back at my print_begin.g file that I posted it will make more sense.
I apologize I didn't see where it was, you mean the parts that are listed underneath it or the actual code itself?
-
@noblebran said in Start / Stop S3D SCRIPT / G-CODE:
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
Perhaps if you look back at my print_begin.g file that I posted it will make more sense.
I apologize I didn't see where it was, you mean the parts that are listed underneath it or the actual code itself?
My first post to you included my complete print_begin.g and print_end.g files.
In my next to last post I simply listed the basics things that needed to be done before a print.
I thought perhaps my files might make sense now that we have conversed.
Frederick
-
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
My first post to you included my complete print_begin.g and print_end.g files.
In my next to last post I simply listed the basics things that needed to be done before a print.
I thought perhaps my files might make sense now that we have conversed.
FrederickI am sorry, yes I see it. I can make it work. I don't know if you want me to post here but can I put my files that I create and have you do a sanity check? I appreciate it.
Now I have to deal with my fans not working now (always on fans).
Thank you again sir.
-
Certainly post your files here.
We all are glad to check them over and make suggestions.
Frederick
-
@noblebran Thank you sir! Be well!
-
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
Certainly post your files here.
We all are glad to check them over and make suggestions.
Frederick
Here is my load filament file (not sure if its the most efficient but it works)
M104 P1 S225 M83 M104 S230 T0 M109 S230 T0 G1 E300 F500 ; LOAD FILAMENT M104 P1 S0
-
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
Certainly post your files here.
We all are glad to check them over and make suggestions.
Frederick
UNLOAD
M104 P1 S225 M83 M104 S230 T0 M109 S230 T0 G1 E15 F250 ;LOAD FILAMENT G1 E-600 F3500 ;UNLOAD FILAMENT M104 P1 S0
-
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
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
-
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
Certainly post your files here.
We all are glad to check them over and make suggestions.
Frederick
I kept most of your ending script:
M291 R"Finishing Print" P"Please wait..." T0 M83 ; extruder relative G1 E-1 F3600 ; retract filament M106 P0 S0 ; turn part fan off G10 P0 S-999 R-999 ; turn extruder heater off (also sets temps to zero) T-1 ; deselect all tools M140 S0 ; set bed heater active temp to 0 M140 S-999 ; turn bed heater off G91 ; relative moves G1 Z100 F1200 ; move the nozzle out of the way - step 1 G90 ; absolute moves G1 X0 Y150 F3000 ; move the nozzle out of the way - step 2 G28 M118 L0 P4 S"FT5|Print Finished" M291 R"Print Finished" P"OK" T0
-
@noblebran said in Start / Stop S3D SCRIPT / G-CODE:
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
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
-
@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:
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.
-
@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
-
@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.
-
@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