@phaedrux Yes - thank you!!

I have a Tevo Little Monster and its just the frame that is left now that I have the Duet Wifi and PanelDue 7i. It is a delta printer that is 350 x 550mm.

@fcwilt Okay, thank you for the explanation my friend.

@phaedrux yes I read all those. I changed the baud rate on the screen to match what the code was. Then to update the firmware I had to connect via USB to the panel. Thank you.

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

@noblebran Thank you sir! Be well!

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

Thank you both!

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

@phaedrux said in ADDING SCRIPT TO HAVE Z-PROBE 'PROBE' BED TO 0 BEFORE PRINTS.:

https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer

Thank you

@jay_s_uk said in ADDING SCRIPT TO HAVE Z-PROBE 'PROBE' BED TO 0 BEFORE PRINTS.:

@noblebran sorry, thought I pasted the link to the delta page

All good - thank you

@jay_s_uk said in ADDING SCRIPT TO HAVE Z-PROBE 'PROBE' BED TO 0 BEFORE PRINTS.:

@noblebran you really want the calibrate a delta page. But I use the G30 trick when I make major changes to mine

What do you mean a delta page?

I incorporated the G30 'trick' and I believe it has worked for me, I am lost on the delta page. Sorry if I seem ignorant. Just learning and don't want to break anything.

@phaedrux said in ADDING SCRIPT TO HAVE Z-PROBE 'PROBE' BED TO 0 BEFORE PRINTS.:

@jay_s_uk said in ADDING SCRIPT TO HAVE Z-PROBE 'PROBE' BED TO 0 BEFORE PRINTS.:

It is a single probe that will then establish the distance between the endstops at the top of the machine to the bed.

Not really, it will tell you where Z0 is. If you want to measure the distance between Z0 and the endstops after that you could use G1 H3 Z4000 to measure the actual endstop position relative to Z0 and set the M208 maxima.

https://duet3d.dozuki.com/Wiki/Gcode#Section_G0_G1_Move

I will go through the Wiki's... Thank you. I do have the z-probe offset in G31 in the main config. I will add G30 and then do a G32.

I will confirm I can get this to work and then I will do a more thorough calibration including the nozzle M208 Maxima command. Thank you sir.

@phaedrux said in ADDING SCRIPT TO HAVE Z-PROBE 'PROBE' BED TO 0 BEFORE PRINTS.:

G30 Z3.89; Check I ADDED

That doesn't do what you think it does.

https://duet3d.dozuki.com/Wiki/Gcode#Section_G30_Single_Z_Probe

G30 will use the probe to find the bed surface. When the probe triggers it will set the current position to whatever you have set in G31 Z as the probe offset.

G30 is the best way to determine where the bed surface actually is. When you home to Z max as you do in a delta, you can't be totally certain that the M208 maxima position is accurate to where Z0 actually is. Even if you measure the Z max position accurately, thermal expansion of nozzle and bed can make the actual nozzle to bed position change.

Calibrate your probe offsets and then use G30 to determine Z0 before doing G32 so that you have an accurate reference for the bed position.

https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

Excellent, thank you.

@jay_s_uk Thank you.

@jay_s_uk Or do you mean run the G30 but remove the Z3.89 after it? Wouldn't I then need to then set absolute dimensions or does the G30 command by itself do that?

@jay_s_uk said in ADDING SCRIPT TO HAVE Z-PROBE 'PROBE' BED TO 0 BEFORE PRINTS.:

@noblebran do a G30 first. Then run G32. Your printer height must be incorrect

I checked and the offset from the probe is that 3.89 I have as Z. The height of the printer is correct, but I was curious as too how to probe and make sure / verify the 0 height before a mapping?

Hello my fellow Duetians,

I have been trying and I could paste about 50 different bed.g codes but I have had the nozzle slam into the glass, go way out and steppers grind, etc.

I am trying to add to my bed.g for my delta for the probe to come down, know the offset from the config or maybe I have to add it to bed.g again, make sure its zeroed and then the mesh and the print is zeroed out accurately and should be as accurate as possible. I put "I ADDED" but have since taken out as it doesn't seem to work. Any help / advice is greatly appreciated. Thank you greatly

Please see the code below and I am using a BL-Touch, Duet 2 wifi and a PanelDue 7i. Thank you.

; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jul 05 2021 14:33:32 GMT-0400 (Eastern Daylight Time)
M561 ; clear any bed transform
G28  ; home all towers
M190 S65  ;PRE-HEAT BEFORE AUTOCALIBRATE
; Probe the bed at 6 peripheral and 6 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
;G1 Z5 F10000; lower nozzle I ADDED
;G30 Z3.89; Check I ADDED
;G90; Absolute positioning I ADDED
G30 P0 X0 Y132.28 H0 Z-99999
G30 P1 X121 Y69.86 H0 Z-99999
G30 P2 X129.9 Y-75 H0 Z-99999
G30 P3 X0 Y-150 H0 Z-99999
G30 P4 X-129.9 Y-75 H0 Z-99999
G30 P5 X-121 Y69.86 H0 Z-99999
G30 P6 X0 Y59.15 H0 Z-99999
G30 P7 X56.09 Y32.38 H0 Z-99999
G30 P8 X64.95 Y-37.5 H0 Z-99999
G30 P9 X0 Y-75 H0 Z-99999
G30 P10 X-64.95 Y-37.5 H0 Z-99999
G30 P11 X-56.09 Y32.38 H0 Z-99999
G30 P12 X0 Y0 H0 Z-99999 S6
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)
G29 ;SAVES FIRST LAYER POINTS

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