Start / Stop S3D SCRIPT / G-CODE

noblebran

G28 Z

fcwilt

@noblebran

Great.

Now I don't have any delta printers so I had to check.

For a delta printer the RRF configuration tool doesn't create those four homing files, just homedelta.g

The homeall.g you posted looks like what the homedelta.g file should be.

So get rid of homex.g homey.g and homez.g and then rename homeall.g to homedelta.g.

Now with that out of the way let's turn to config.g.

You have an M587 there which not be used in config.g. You use that command when setting up the WiFi connection but you don't keep it in config.g.

At first glance everything else looks reasonable.

Does the PanelDue work?

Does homing work?

Can you move the nozzle to all places in the printable area?

Can you move over the range of the Z axis?

If you move to Z=10 and do a G30 does the Z probe work?

If you activate the heaters do they heat as expected to whatever temperature you specified?

Do the fans work?

Thanks.

Frederick

noblebran

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

Great.
Now I don't have any delta printers so I had to check.
For a delta printer the RRF configuration tool doesn't create those four homing files, just homedelta.g
The homeall.g you posted looks like what the homedelta.g file should be.
So get rid of homex.g homey.g and homez.g and then rename homeall.g to homedelta.g.

Okay, this is done. Let me go to the next part.

noblebran

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

Now with that out of the way let's turn to config.g.
You have an M587 there which not be used in config.g. You use that command when setting up the WiFi connection but you don't keep it in config.g.
At first glance everything else looks reasonable.
Does the PanelDue work?
Does homing work?
Can you move the nozzle to all places in the printable area?
Can you move over the range of the Z axis?
If you move to Z=10 and do a G30 does the Z probe work?
If you activate the heaters do they heat as expected to whatever temperature you specified?
Do the fans work?

My PanelDue 7i works, I haven't been able to print an enclosure for it so I haven't really been using it, but it connects and shows readings, etc.

Homing does work.

Yes, I can move the nozzle to all places in the printable area.

I can move the nozzle over the range of the z axis using code, I can using the dashboard buttons. Homed it is x0, y0, z515 so when I put in a g1 z- command it goes down.

The z-probe worked, re-calibrated just now (put the bed at z5, now its z6.35), I thought I put that correction in the config, but I guess not (as you know its the distance between the nozzle tip and tip of the probe).

The heaters work, but I have another thread going as I always get faults that my block heater goes way above the set point. I have all e3d parts, I don't have an e3d cartridge thermistor but I didn't get one when I received the parts years ago and it worked when I had the old smoothieware system (MKS Base). The bed works great though.

The fans work (I think). I say I think because my heatsink fan is on 24/7 now, which I know is because of the connection I plugged it in. My part cooling fans are set to turn on when the temp goes above 50 I think but I didn't know how else to control them as I would normally in the slicer.

I did do an autocalibration and it worked

Besides the extruder heater/thermistor and the fans (but they work) I think to answer everything I would say yes besides my comments above. Sorry for the abundance of detail.

DonStauffer

@fcwilt Interesting . Why do it as a call to files on the Duet? You do lose the Simpify3D script variable capability that way.

fcwilt

@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

DonStauffer

@fcwilt I was thinking along those lines but I couldn't quite solidify those thoughts. Makes sense.

noblebran

@fcwilt

@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?

fcwilt

@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

noblebran

@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 map

And 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.

fcwilt

@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 map

If 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

noblebran

@fcwilt

@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?

fcwilt

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

@fcwilt

@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

noblebran

@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.
Frederick

I 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.

fcwilt

@noblebran

Certainly post your files here.

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

Frederick

noblebran

@noblebran Thank you sir! Be well!

noblebran

@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

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

noblebran

@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

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

noblebran

@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

noblebran

@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

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