TEVO Little Monster + DuetWifi + BLTouch

yeoman91

Hello community,

I have encountered a problem that i simply can not get my head around. I have tried multiple solutions and the step by step guide; https://betrue3d.dk/bltouch-on-duet-wifi-duetreprapfirmware/.
The BLTouch i acting strange. I can perform a G29, a probe-test; M280 P3 S120 I1 and the BLT works as intended. However, when I want to print a part, with the following start g-code (after successfully doing the Auto Delta Calibration);

G28 ; Home
G29 S1 ; Load mesh from previous

I does not work. The effector moves towards the bed followed by a BLTouch that "clicks" (needle touches the bed). The probe does not retract and ends up going into alarm mode. I have checked the wiring twice and everything is fine. I do not know what is wrong i have tried different modes (Mode/Type of probe) P3, P5 and P9. White the same problem.
I have cleaned the pin in the BLT.

I have attached the following settings:

Config:

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P1 ; Set firmware compatibility to look like RepRapFirmare
M665 R157 L397.1073 B175 H517.82 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; Put your endstop adjustments here, or let auto calibration find them
M208 Z0 S1 ; Set minimum Z

; Endstops
M574 X2 Y2 Z2 S1 ; Define active high microswitches
M558 P1 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
M557 R130 S20 ; Define mesh grid

; BL-Touch
M307 H3 A-1 C-1 D-1 ; reserve pin 21 for M42 or servo use
M558 P9 X0 Y20 Z0 H5 F100 R0.2 T6000
G31 P25 X0 Y0 Z0.733; Set Z probe trigger value, offset and trigger height

; Drives
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
M350 E16 I1 ; Configure microstepping without interpolation
M350 X16 Y16 Z16 I1 ; Configure microstepping with interpolation
M92 X160 Y160 Z160 E892 ; Set steps per mm
M566 X1500 Y1500 Z1500 E1500 ; Set maximum instantaneous speed changes (mm/min)
M203 X39960 Y39960 Z39960 E3000 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 E1500 ; Set accelerations (mm/s^2)
M906 X1100 Y1100 Z1100 E1100 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Heaters
M143 S298 ; Set maximum heater temperature to 285C
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B4607 C8.950070e-8 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4725 C7.06e-8 R4700 ; Set thermistor + ADC parameters for heater 1

; Tools
M563 P0 D0 H1 F0:2 ; 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

; Network
M550 PTEVO LM ; Set machine name
M552 S1
M540 PBE:EF:DE:AD:FE:ED ; Set MAC address
M552 P192.168.1.149 S1 ; Enable network and acquire dynamic address via DHCP
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Fans
M106 P0 S0 I0 F255 H-1; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F255 H1 T60; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S0 I0 F255 H-1; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
; Custom settings are not configured

; Miscellaneous
M501 ; Load saved parameters from non-volatile memory

bed.g

; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool on Sat Jul 07 2018 15:37:48 GMT-0700 (Pacific Daylight Time)
M561 ; clear any bed transform
G28 ; home all towers
M401 ; deploy mechanical Z probe
; Probe the bed at 6 peripheral and 6 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y132.28 H0 Z-99999
G30 P1 X121 Y69.86 H0 Z-99999
G30 P2 X129.9 Y-75 H0 Z-99999
G30 P3 X0 Y-150 H0 Z-99999
G30 P4 X-129.9 Y-75 H0 Z-99999
G30 P5 X-121 Y69.86 H0 Z-99999
G30 P6 X0 Y59.15 H0 Z-99999
G30 P7 X56.09 Y32.38 H0 Z-99999
G30 P8 X64.95 Y-37.5 H0 Z-99999
G30 P9 X0 Y-75 H0 Z-99999
G30 P10 X-64.95 Y-37.5 H0 Z-99999
G30 P11 X-56.09 Y32.38 H0 Z-99999
G30 P12 X0 Y0 H0 Z-99999 S6
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)
M402 ; retract mechanical Z probe
G29

deployprobe.g
M280 P3 S160 I1
M280 P3 S10 I1

retractprobe.g
M280 P3 S90 I1

homedelta.g
; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool on Mon May 22 2017 22:56:20 GMT-0400 (Eastern Daylight Time)

; Use relative positioning
G91

; Move all towers to the high end stopping at the endstops (first pass)
G1 X550 Y550 Z550 F4800 S1

; Go down a few mm
G1 X-5 Y-5 Z-5 F1800 S2

; Move all towers up once more (second pass)
G1 X10 Y10 Z10 F360 S1

; Move down a few mm so that the nozzle can be centred
G1 Z-5 F6000

; Switch back to absolute positioning and go to the centre
G90
G1 X0 Y0 F6000

M280 P3 S10 I1

Thanks for reading

dc42

@yeoman91 said in TEVO Little Monster + DuetWifi + BLTouch:

G28 ; Home
G29 S1 ; Load mesh from previous

Do those commands work without deploying the BLTouch if you run them by themselves?
Delete the M401 and M402 commands from your bed.g file. They are not needed when using BLTouch and they could be causing probems.

yeoman91

@dc42 said in TEVO Little Monster + DuetWifi + BLTouch:

G29 S1

I have tested G28 and G29 S1 in the G-code console individually without problems.
I have now deleted the M401 and M402, setting the probe to mode P9, however the problemt stays the same.

I have tried a new Auto Delta Calibration, followed by a new print with the start g-code G28 and G29 S1, resulting in the same issue.

bed.g

; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool on Sat Jul 07 2018 15:37:48 GMT-0700 (Pacific Daylight Time)
M561 ; clear any bed transform
G28 ; home all towers
; Probe the bed at 6 peripheral and 6 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y132.28 H0 Z-99999
G30 P1 X121 Y69.86 H0 Z-99999
G30 P2 X129.9 Y-75 H0 Z-99999
G30 P3 X0 Y-150 H0 Z-99999
G30 P4 X-129.9 Y-75 H0 Z-99999
G30 P5 X-121 Y69.86 H0 Z-99999
G30 P6 X0 Y59.15 H0 Z-99999
G30 P7 X56.09 Y32.38 H0 Z-99999
G30 P8 X64.95 Y-37.5 H0 Z-99999
G30 P9 X0 Y-75 H0 Z-99999
G30 P10 X-64.95 Y-37.5 H0 Z-99999
G30 P11 X-56.09 Y32.38 H0 Z-99999
G30 P12 X0 Y0 H0 Z-99999 S6
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights andight only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)
G29

dc42

Please post the first 50 or so lines (excluding any comment lines at the start) of the file you are trying to print. I think something else in that file must be commanding the BLTouch to deploy.

Phaedrux

@yeoman91 said in TEVO Little Monster + DuetWifi + BLTouch:

M558 P9 X0 Y20 Z0 H5 F100 R0.2 T6000
G31 P25 X0 Y0 Z0.733; Set Z probe trigger value, offset and trigger height

Remove the X0 Y20 Z0 from M558, it doesn't belong there.
And your G31 doesn't have an X and Y offset. That's probably where the Y20 belongs.

@yeoman91 said in TEVO Little Monster + DuetWifi + BLTouch:

M280 P3 S10 I1

You've got a deploy probe command at the end of your homedelta.g. I don't think it should be there?

@yeoman91 said in TEVO Little Monster + DuetWifi + BLTouch:

deployprobe.g
M280 P3 S160 I1
M280 P3 S10 I1

You may need to add a brief dwell command between the two servo commands, but really you shouldn't need to clear an error before deploying the probe when things are working correctly, so maybe try removing the S160 command. If you want to ensure error states are cleared first, add that S160 command to your config.g for startup, and the start of the homing files.

yeoman91

@dc42

;FLAVOR:RepRap
;TIME:1290
;Filament used: 2.18283m
;Layer height: 0.3236
;Generated with Cura_SteamEngine 3.6.0
T0
M190 S80
M104 S200
M109 S200
M82 ;absolute extrusion mode
G28 ; Home
G29 S1 ; Load mesh from previous

M83 ;relative extrusion mode
G1 F2700 E-0.2
;LAYER_COUNT:56
;LAYER:0
M107
G0 F2520 X17.823 Y-12.036 Z0.324
;TYPE:SKIRT
G1 F600 E0.2
G1 F1470 X18.095 Y-11.757 E0.02992
G1 X18.611 Y-11.173 E0.05984
G1 X19.598 Y-9.945 E0.12097

...

G1 F1470 X13.387 Y7.825 E0.08014
;TIME_ELAPSED:1290.290412
G1 F2700 E-0.2
M140 S0
M82 ;absolute extrusion mode
M107
G92 E0 ; Set EXT to zero
G1 E-12 F9000 ; Retract x mm filament
M104 S0 ; turn off extruder
M140 S0 ; turn off bed
G28 ; home all axes
M83 ;relative extrusion mode
M104 S0
;End of Gcode
;SETTING_3 {"extruder_quality": ["[general]\nversion = 4\nname = 0.3236 - TLM
;SETTING_3 \ndefinition = fdmprinter\n\n[metadata]\nposition = 0\nsetting_ve
;SETTING_3 rsion = 5\nquality_type = normal\ntype = quality_changes\n\n[valu
;SETTING_3 es]\ncool_fan_speed = 30\nmaterial_flow = 95\nretraction_amount =
;SETTING_3 0.2\nretraction_retract_speed = 45\nspeed_print = 35\nspeed_travel
;SETTING_3 = 60\n\n"], "global_quality": "[general]\nversion = 4\nname = 0.
;SETTING_3 3236 - TLM\ndefinition = fdmprinter\n\n[metadata]\nsetting_versio
;SETTING_3 n = 5\nquality_type = normal\ntype = quality_changes\n\n[values]
;SETTING_3 \nlayer_height = 0.3236\nlayer_height_0 = 0.3236\nmaterial_bed_temp
;SETTING_3 erature = 80\n\n"}

@Phaedrux

I have cleanet my M558, G31 and deployprobe.

Furthermore, I changed the M558 F100 to F120 and G31 P25 to P500.

I have finally got it to work! Thank you both, what a struggle.

Phaedrux

@yeoman91 said in TEVO Little Monster + DuetWifi + BLTouch:

G31 P25 to P500

G31 P25 should work and provide quicker response time to a trigger, but if it works, it works. Glad it's sorted.