Resume print
-
@Phaedrux here is the config. Left out the networking part
; Drives
M569 P0 S0 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2:4 E3 ; two Z motors connected to driver outputs Z and E1
M671 X-20:220 Y0:0 S0.5 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis
M208 X-5:205 Y0:200 ; X carriage moves from -5 to 205, Y bed goes from 0 to 200
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E408 ; set steps per mm
M566 X500.00 Y500.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z300.00 E3600.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z900 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y-22.5 Z-2.5 S1 ; set axis minima
M208 X500 Y500 Z500 S0 ; set axis maxima; Endstops
M574 X1 Y1 S1 ; set active high endstops
M574 Z1 S2 ; set endstops controlled by probe; Z-Probe
M558 P9 H5 F120 T6000 A2 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-30.8 Y0 Z2.55 ; set Z probe trigger value, offset and trigger height
M557 X15:445 Y15:445 S20 ; define mesh grid; Heaters
M305 P0 T100000 B4138 R2200 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R2200 ; set thermistor + ADC parameters for heater 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C; Fans
M106 P0 S1 I0 F500 H1 T30 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C -
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
