My DeltaD3H (DIY Delta printer)

DannerD3H · 15 Jan 2018, 18:58

Thankyou Gone2Far!

After spending my entire sunday on spaghetti it brought me significantly closer to my first print. tonight i also got to calibrate the motion system of the machine. everything seem to work, both the heaters, fans and BlTouch. Movement seem fast and tight. I am generally fairly satisfied so far. Here is a little motion demo.. i love the way these things move!
https://youtu.be/CvmyG0Acp_0

This is my heightmap after a couble of G32's (i think it is acceptable, correct me if i am wrong):

However i am a little confused. My BlTouch has a trigger height of roughly 2,4 mm. But this is my nozzle posistion at Z0 after the G32 auto calibration no matter if i enter the z ofset in G31 as 2.4 or -2.4:

What am i not understanding here?

dc42 · 15 Jan 2018, 21:44

Do you have a G31 command in config-override.g as well?

DannerD3H · 16 Jan 2018, 06:41

Hmm it seems that i do not even have a config-override.g file..

Is this file a must have?

dc42 · 16 Jan 2018, 06:55

No, it's not a must-have.

Are you finding the Z=0 nozzle position too high immediately after you run auto calibration, or only after you have restarted and homed the printer again?

Please post your config.g and bed.g files.

DannerD3H · 16 Jan 2018, 06:58

Aaaah found my error. I had two G31 commands in the config.g file. Srry that was a stupid question then.

I am still getting used to this duet way of doing things. It is really clever once you get the hang of it!

DannerD3H · 24 Jan 2018, 21:04

Hello again!

Does anyone know how i can make my machine turn on (send M80) before the machine heats up?
I am using Simplify3D as a slicer. The problem is S3D inserts heating commands (and wait until heated) before my start-script. This means that the printer will try to reach bed temp without power, thus never getting to my M80 command from my start code.
I have read something on S3D's forum:

But i am not clever enough to understand what to put in my M140 and M104 so that i don't have to change it every time..
Currently this is my startscript:

[[language]]
M80	;Turn on

G28 		;Home all axes
G32		;Auto calibration
G29 S1		;Load height map

This is what the slicer outputs:

[[language]]
G90
M83
M106 S255
G4 P500
M106 S0
M140 S60
M190 S60
M104 S200 T0
M109 S200 T0
M80		:Turn on
G28 		;Home all axes
G32		;Auto calibration
G29 S1		;Load height map

Another question:
My printer always makes a short pause of 1-2 seconds between the first and second layer. does anyone know why this is? (The fans start on the third layer).

DannerD3H · 26 Jan 2018, 06:16

Any ideas?

dc42 · 26 Jan 2018, 09:05

What I think you need to include in your start gcode is:

T0 ; select tool 0
M140 S[bed_temperature] ; set bed temperature
M104 S[extruder0_temperature] ; set extruder temperature
M116 ; wait for temperatures to be reached

EasyTarget · 26 Jan 2018, 12:23

@DannerD3H:

My printer always makes a short pause of 1-2 seconds between the first and second layer. does anyone know why this is? (The fans start on the third layer).

If the temperature changes (first layer hotter than others) then maybe this is another forced pause until the head has cooled to the new temp?
PS: Lovely printer, the pop out electronics bay makes me jealous..

DannerD3H · 26 Jan 2018, 22:36

Thank you easy target!
But don't be jealous.. It seemed like a good idea on the drawing but in reality it is not! It makes proper wire management near impossible as all wires have to be at least 30 cm to long to be able to pull out the tray.. I will most likely ditch it and mount the board permanently instead.

I have a constant temperature all the way so shouldn't be the case.. Will look closely on the g-code tomorrow to see if I can figure out whether it's a slicer or firmware thing..

Dc42, if I do that, won't I then have to change something in the start code to use my second nozzle?
If I ever have to change values on the start code, then I would rather turn on the machine manually first.. But would be cool if starting a print automatically would send the m80 command before executing any of the print file…

number40fan · 26 Jan 2018, 23:26

You could always edit the .gcode in a text editor and put the M80 in front of everything. Little time consuming, but should get the job done.

dc42 · 27 Jan 2018, 08:48

I have often thought that slicers should support 2 sets of start gcode: one to execute right at the start, and one after the slicer has generated the temperature-setting code before the print starts.

DannerD3H · 27 Jan 2018, 13:16

Yes but the post processing of the g-codes are exactly what i want to avoid..

DC42, yes either that or at least a setting so that the slicer would automatically include the m80 command as the first command..
Is this something that can be implemented in the Duet web interface? Could it be implemented that every time you start a print, the web interface would send a M80, like when i manually press the ATX on button?

I n´know it may seem like a silly small thing, but it would just be a nayz feature i think..

dc42 · 27 Jan 2018, 13:35

I guess there could be a start.g macro run when you start printing a file from SD card.

DannerD3H · 27 Jan 2018, 15:59

Is this something that is already possible or ?

DannerD3H · 29 Jan 2018, 08:43

I finally got to make some prints this weekend. I think this could become a really good printer, but i still have a few issues..

This thread is covering my two biggest issues: https://www.duet3d.com/forum/thread.php?pid=37203#p37203

dc42 · 29 Jan 2018, 09:06

@DannerD3H:

Is this something that is already possible or ?

Not yet, but I will consider it for the next 1.21RC.

DannerD3H · 29 Jan 2018, 09:07

Cool!