Resume print
-
I don't see anything unusual in there, unless you've got something in the homing files or start gcode?
-
@Phaedrux I really dont think its the start code haha... but for safety sake here it is:
G28
G92 E0 ;Reset Extruder
G1 Z2.0 F3000 ;Move Z Axis up
G1 X10.1 Y20 Z0.28 F5000.0 ;Move to start position
G1 X10.1 Y200.0 Z0.28 F1500.0 E15 ;Draw the first line
G1 X10.4 Y200.0 Z0.28 F5000.0 ;Move to side a little
G1 X10.4 Y20 Z0.28 F1500.0 E30 ;Draw the second line
G92 E0 ;Reset Extruder
G1 Z2.0 F3000 ;Move Z Axis up -
@Phaedrux @dc42
Sorry guys I thought maybe a video to show this is the easiest.As you can see, when you hit resume, the nozzle drops from the correct height to resume, to x0 y0 z0 and then starts moving to go back to the resume point. This almost always knocks the print off the bed... How do I correct that?
G1 R1 X0 Y0 Z5 F6000 ; go to 5mm above position of the last print move
G1 R1 X0 Y0 Z0 ; go back to the last print move
M83 ; relative extruder moves
G1 E2 F3600 ; extrude 2mm of filament -
@GT1Za Is the video supposed to be only 3 seconds long? Though it looks like it's moving at a diagonal.
Again, I ask what firmware version are you using? Send M115.
-
@Phaedrux sorry I missed you asking for the firmware.
The video was only 3 seconds because the forum will only allow a 4mb upload.Firmware is 2.02RC5
-
@GT1Za said in Resume print:
Firmware is 2.02RC5
I would suggest updating your firmware first. There were some issues in that time frame for resuming.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
Download this zip file, and in DWC, upload it to the system tab. Don't extract it first.
-
@Phaedrux the reason I havent done this is because, well as you can see im not the greatest at firmware. My understanding is that most of the code for the config etc has changed? If I upload this wont it break my existing?
-
No, 2.05 won't require changes to your config. RRF3 would require changes.
-
@Phaedrux Firmware Version: 2.05.1 (2020-02-09b1)
haha fingers crossed! Thanks for the help, Ill report back as soon as I get a chance to test
-
@Phaedrux thanks I can confirm updating the firmware fixed the issue
