Duet WiFi with E3V6 dragging on plate

[dc42]

PS you have no M208 command in config.g so movement below where the firmware thinks Z=0 will not be allowed. As you are experimenting with negative trigger heights, you may need to allow small amounts of negative Z movement. For example, M208 S1 Z-1 would allow movement down to -1mm.

[thingismith]

So, I tried again with your suggestions dc, still no success. I commented out the G31 in bed.g (and included the M208 command in config.g), still dragging on the plate (I know what you're thinking, of course I changed the Z to -.4 in the G31 of config.g). I even tried replacing the M109 with the M116 in my GCode (the M104 was already there) in case I didn't upgrade the 1.20 firmware correctly or to check if it was still an issue, but it still dragged.

[Char'les Grey]

ok, I resolved my issue. First of all, I commented out initially m665 and m666, got everthing working and as soon as I ran m666 commented in, I started having issues, so I just run auto calibration before every print and call it good. I haven't updated the firmware yet.... but I have printed a few things out with "ok" success. But NO bed scraping or silly stuff like that, below is from my config.g

Code: Select all

; Configuration file for SeeMeCNC Rostock MAX V3

; Communication and general
M111 S0                             	; Debug off
M550 PSeeMeCNCRostockMAXV3		; Machine name and Netbios name (can be anything you like)
M551 Preprap                        	; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 XX	; MAC Address
;*** Wifi Networking
M552 S1					; Enable WiFi

M555 P2                           	; Set output to look like Marlin
M575 P1 B57600 S1			; Comms parameters for PanelDue

G21                                 	; Work in millimeters
G90                                	; Send absolute coordinates...
M83                                 	; ...but relative extruder moves

; Axis and motor configuration
M569 P0 S1				; Drive 0 goes forwards
M569 P1 S1				; Drive 1 goes forwards
M569 P2 S1				; Drive 2 goes forwards
M569 P3 S0				; Drive 3 goes forwards
M569 P4 S0				; Drive 4 goes forwards
M574 X2 Y2 Z2 S1			; set endstop configuration (all endstops at high end, active high)
;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
M665 R144.192 L291.06 B265 H386.163 X0.406 Y0.359 Z0		; set delta radius, diagonal rod length, printable radius and homed height
;M666 X-0.46 Y0.39 Z0.08				; put your endstop adjustments here, or let auto calibration find them
M350 X16 Y16 E16 I1    			; Set 16x microstepping with interpolation
M92 X80 Y80 Z80				; Set axis steps/mm
M906 X1000 Y1000 Z1000 E800 I60		; Set motor currents (mA) and increase idle current to 60%
M201 X1000 Y1000 Z1000 E1000		; Accelerations (mm/s^2)
M203 X20000 Y20000 Z20000 E3600		; Maximum speeds (mm/min)
M566 X1200 Y1200 Z1200 E1200		; Maximum instant speed changes mm/minute

; Thermistors
M305 P0 T100000 B3950 R4700 H30 L0	; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 B4725 C7.060000e-8
;M305 P1 T100000 B3974 R4700 H30 L0	; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
;M305 P2 T100000 B3974 R4700 H30 L0	; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
M570 S180				; Hot end may be a little slow to heat up so allow it 180 seconds

; Fans
M106 P1 H-1 				; disable thermostatic mode for fan 1

; Tool definitions
M563 P0 D0 H1                       	; Define tool 0
G10 P0 S0 R0                        	; Set tool 0 operating and standby temperatures
;*** If you have a single-nozzle build, comment the next 2 lines
;M563 P1 D1 H2                      	; Define tool 1
;G10 P1 S0 R0                       	; Set tool 1 operating and standby temperatures
M92 E456.7829376                       	; Set extruder steps per mm

; Z probe and compensation definition
M558 P4 X0 Y0 Z1 H5 F1200 T2400		 ; M558 P5 X0 Y0 Z1 H5 F1200 T2400	


; grid compensation
M557 R110 S15

M558 P4 X0 Y0 Z-0.22         ; Z probe is a switch and is not used for homing any axes -added

G31 X0 Y0 Z-0.5				; Set the zprobe offset and threshold (determine your printer's Z offset value). For a delta, use zero X and Y offset.

;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0                   	; Axis compensation here
M501					; added per forum
T0						; select first hot end

[geneb]

I do this myself - my start gcode includes a G32 right after the G28.

g.

[thingismith]

I noticed that 1.21 was out, so I decided to try installing that to see if it would fix the issue, but I'm still SOL.

Duet_Version.pdf

(10.91 KiB) Downloaded 198 times

I even tried Char'les solution of commenting out M666, but that didn't work either. What the heck is going on? How am I the only 1 with this issue? (btw, I've bumped the Z to -.6)

Also, is there a mailing list somewhere to be notified when a new Duet Firmware Version comes out?

[Char'les Grey]

I noticed that 1.21 was out, so I decided to try installing that to see if it would fix the issue, but I'm still SOL.
Duet_Version.pdf
I even tried Char'les solution of commenting out M666, but that didn't work either. What the heck is going on? How am I the only 1 with this issue? (btw, I've bumped the Z to -.6)

Also, is there a mailing list somewhere to be notified when a new Duet Firmware Version comes out?

What are you using to determine bed leveling? How did you get the M665 results? Copy and Paste from a tutorial, or determine them yourself?

[thingismith]

I got my config m665 and m666 from running the auto-calibration and inputting the results.

But it shouldn't matter, they get overridden by the m500 auto-calibration command. I just can't get the g31 z adjust to work. I can circumvent the issue by adjusting in my slicer, but I'd prefer it to work the right way.

[geneb]

M500 doesn't calibrate anything, it just writes changed things to config-override.g.

g.

[thingismith]

Thank you gene, how about this: "...overridden by the m500 auto-calibration [override] command."

You remind me of a kid in my high school who always wore sweatpants just so he'd never get caught with his fly down. That guy was a genius too.

[geneb]

Again, M500 doesn't have anything to do with calibration. All it does is output any differences between config.g and the in-ram configuration out to a file called config-override.g. This entry lists what exactly is stored when M500 is executed: https://duet3d.dozuki.com/Wiki/Gcode#Se ... parameters

Have you ever tried mesh compensation on your machine? I'm wondering if that might help you. If memory serves, G29 will kick off the routine. When it's done, it'll write a .csv file to your /sys directory. You can load that map file via "G29 S1".

You'll need "M557 R140 S30" in your config.g file - replace the 140 with whatever the radius of your bed is.

g.

[thingismith]

Well, I tried the mesh-bed compensation yesterday, that seemed to do the trick! I had never bothered before because it seemed unnecessary, just to get a visual heightmap of the bed. After playing with it, I realized that the g31 affects the mesh compensation results, which affects (after including G29 in the bed.g) the machine's calibration.

Does anyone run the mesh bed compensation G29 after the G32 probe every time before a print? At the moment I have G29 S1 in my bed.g file.

[geneb]

Unless you take your glass off or rotate it, there's usually no reason to re-run the map.

g.