Z end stop errors posted during auto bed compensation
-
Hi:
Cartesian FrameMechanical limit switches
HomeX works properly
HomeY works properly
HomeZ works properlyHomeAll works properly
When I run the auto bed compensation, I get error messages popping up that say that
"the Z probe was not triggered during probing move"
and the utility fails.
At each probe point, I see the light on the main board turn on for the Z end stop indicating that it has triggered.
Is there a way to see the gcode that is executing during the auto bed compensation run?
I don't understand why it is failing, or not registering the z end stop triggering except to observe that the z end stop light goes out between probe points which I think it should (and which matches the error message), or is the z end stop supposed to be triggered throughout the probing duration and how do I make that happen without editing the auto bed compensation code?
Thanks
Tim -
If you have recently updated, make sure deploy and retract probe folders have been deleted.
Then post your config and bed files.
-
Hi:
Deploy and retract have been deleted.
Bed
[c]
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool on Fri Sep 08 2017 10:03:01 GMT-0400 (Eastern Daylight Time); Clear any bed transform
M561; Home all axes
G28; Probe the bed at 5 points
G30 P0 X25 Y25 H0 Z-99999
G30 P1 X25 Y175 H0 Z-99999
G30 P2 X200 Y175 H0 Z-99999
G30 P3 X200 Y25 H0 Z-99999
G30 P4 X140 Y100 H0 Z-99999 S[/c]
Config
[c]
; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Fri Sep 08 2017 10:03:01 GMT-0400 (Eastern Daylight Time); General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X210 Y280 Z180 S0 ; Set axis maxima; Endstops
M574 X1 Y1 Z1 S0 ; Define active low and unused microswitches
M558 P0 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X25:175 Y25:175 S20 ; Define mesh grid; Drives
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X128 Y128 Z128 E16 I0 ; Configure microstepping without interpolation
M92 X640 Y640 Z3200 E100 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X12000 Y12000 Z1200 E3000 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z100 E5000 ; Set accelerations (mm/s^2)
M906 X855 Y855 Z855 E855 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Heaters
M143 S260 ; Set maximum heater temperature to 260C
M305 P0 T100000 B3988 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4725 C0 R4700 ; Set thermistor + ADC parameters for heater 1; Tools
M563 P1 D0 H1 ; Define tool 1
G10 P1 X0 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C; Network
M550 PTevo Tarantula ; Set machine name
M552 S1 ; Enable network
; Access point is configured manually via M587 by the user
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S1 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off; Custom settings are not configured
; Miscellaneous
T1 ; Select first tool
[/c]I think I am going to have to learn a lot more about G-Code
Thanks
Tim -
What are you using for a probe? You don't have anything in your M558 for it.
-
Well. that might be causing my issue. I don't have a probe. I had an SN04 from my Tevo Tarantula, but I didn't want to modify the Duet to use it on this board. I have ordered one of DC42s probes, but I don't have it yet. All I have is the Z limit switch which I had hoped would allow me to print while I was waiting for the probe to arrive.
I haven't managed to get my first print done yet.
Can I just comment out the M558 for now? Will it then use my z limit switch, or will it just fail?
Thanks
Tim -
Just don't run the bed compensation.
-
Ok, Thanks very much.
Now I can work setting up the 1st layer and so on.
