My DeltaD3H (DIY Delta printer)
-
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). -
Any ideas?
-
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 -
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.. -
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… -
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.
-
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.
-
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..
-
I guess there could be a start.g macro run when you start printing a file from SD card.
-
Is this something that is already possible or ?
-
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
-
Is this something that is already possible or ?
Not yet, but I will consider it for the next 1.21RC.
-
Cool!