BLTouch working
-
I am suggest that you create a resetalarm.g (your call on the name) file with M280 P3 S160 I1.
That way, you can cancel the alarm by usingM98 Presetalarm.g
instead of remembering the M280 P3 S160 I1 command or resetting your printer.
I have add it to my Default G-Codes (drop down menu).
-
Were you able to test your homez.g?
-
Were you able to test your homez.g?
Not yet, I'm working till late tonight. I'll post a feed back Around 9pm.
and yes I do have the files retract & deploy. I did add it to bed.g & homeall.g but forgot about homez.g.
But if I'm not wrong I believe it deploy and retract the probe automatically when i use G30. -
Were you able to test your homez.g?
I have tested it but it work just as my configuration without theM98 commands.
I also I'm using the correct resistor.
ever thing works "almost" fine if I use M558 P1 but the probe drops some time.
this is my configuration maybe I missed some thing;; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Tue Sep 19 2017 08:19:05 GMT+0100 (GMT 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 MarlinM667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X430 Y330 Z450 S0 ; Set axis maxima; Endstops
M574 X1 Y1 Z0 S0 ; Define active low and unused microswitches
M558 P1 X0 Y0 Z1 H5 F120 T9000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P10 X0 Y40 Z2 ; Set Z probe trigger value, offset and trigger height
M557 X15:415 Y15:315 S20 ; Define mesh grid; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M569 P5 S1 ; Drive 5 goes forwards
M350 X16 Y16 Z16 E16:16:16 I1 ; Configure microstepping with interpolation
M92 X100 Y100 Z400 E383:383:383 ; Set steps per mm
M566 X1200 Y1200 Z12 E240:240:240 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E3000:3000:3000 ; Set maximum speeds (mm/min)
M201 X500 Y20 Z250 E250:250:250 ; Set accelerations (mm/s^2)
M906 X1200 Y1200 Z1500 E800:800:800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Heaters
M143 S275 ; Set maximum heater temperature to 275C
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1; Tools
M563 P0 D0 H1 ; 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
M563 P1 D1 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
M563 P2 D2 H1 ; Define tool 2
G10 P2 X0 Y0 Z0 ; Set tool 2 axis offsets
G10 P2 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C; Network
M550 PUltima Bot ; 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
M307 H7 A-1 C-1 D-1 ;disable heater 7 on pmw5; Miscellaneous
T0 ; Select first toolBed.g
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool on Mon Sep 18 2017 19:18:06 GMT+0100 (GMT Daylight Time); Clear any bed transform
M561; Deploy the mechanical Z probe
M98 Pdeployprobe.g; Probe the bed at 5 points
G30 P0 X15 Y15 H0 Z-99999
G30 P1 X15 Y315 H0 Z-99999
G30 P2 X415 Y315 H0 Z-99999
G30 P3 X415 Y15 H0 Z-99999
G30 P4 X215 Y165 H0 Z-99999 S
; Retract the mechanical Z probe
M98 Pretractprobe.gHomeall.g
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Mon Sep 18 2017 19:21:01 GMT+0100 (GMT Daylight Time); Relative positioning
G91; Lift Z
G1 Z5 F9000; Deploy the mechanical Z probe
M98 Pdeployprobe.g; Course home X and Y
G1 X-435 Y-335 F3600 S1; Move away from the endstops
G1 X5 Y5 F9000; Fine home X and Y
G1 X-435 Y-335 F360 S1; Absolute positioning
G90; Go to first bed probe point and home Z
G1 X15 Y15 F9000
G30; Uncomment the following line to lift the nozzle after probing
;G1 Z10 F150; Retract the mechanical Z probe
M98 Pretractprobe.gHomez.g
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Tue Sep 19 2017 08:11:32 GMT+0100 (GMT Daylight Time); Lift Z relatively to current position
G91
G1 Z5 F9000; Back to absolute positioning
G90; Go to first bed probe point and home the Z axis
G1 X15 Y5 F9000
G30; Uncomment the following lines to lift Z after probing
G91
G1 Z5 F150
G90 -
What are your values in Z-Probe for triggered and deploy?
-
The shows 4 some times 5 when triggered and 0 when not triggered. (using M558 P1)
If I uses M558 P5 then it will always be 0. -
just run a mesh grid and this was the results :
share pics online
I'm Almost giving up on this … I have tried the DC42 IR Probe but because my heatbed is glass when I use tape or ABS juice on the surface the IR probe needs to be re-calibrated. -
I just noticed that in your HomeZ.g you do not deploy or retract.
-
I just noticed that in your HomeZ.g you do not deploy or retract.
it is not necessary because the firmware does it automatically when G30 is called. but I have tried it with the deploy and retract code but did not make any difference.
I have now just tried to do a mesh levelling using the DC42 IR Probe and this was the result;
I have a aluminium heat bed painted black and with a 6mm sheet of glass on top of it so it is 100% flat. I dont know why I keep get this results with the BLTouch and the IR Probe. any idea? -
just did a mesh grid using the BLTouch and another with the DC42 IR Probe. can anyone help with it?why both of then are giving bad results?
BLTouch
DC42 IR Probe
-
How is your bed mounted, is the movement smooth or staggered at low and fast speed
-
The IR probe results have one corner point much lower than the rest. There must be something in that corner to cause that, or perhaps you are probing too close to the edge.
-
It is a Modified D-Bot with 3 x T8 rods its pretty solid. and the heat bed is a 6mm sheet of glass over a aluminium plate painted black.
it is probing at least 50mm away from the edges.
I am doing some tests now with the DC42 IR Probe it seems to be more reliable than the BLTouch.
got this result doing a probing in just 1 point with this settingM558 P1 X0 Y0 Z1 H5 F120 T12000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P200 X0 Y0 Z1.4 ; Set Z probe trigger value, offset and trigger heightM98 P0:/macros/BLTouch 20 probing 1 point
Bed probe heights: -0.657 -0.660 -0.660 -0.655 -0.657 -0.657 -0.655 -0.660 -0.657 -0.657 -0.662 -0.662 -0.655 -0.657 -0.660 -0.655 -0.652 -0.662 -0.657 -0.657 -0.660, mean -0.658, deviation from mean 0.003Now I will do a G29 and see if it is consistent with this result.
-
Just did a G29 and got this with the IR Probe
-
Hello ALL !
I'm using DUET 0.6 and TLTouch sensor from aliexpress. It's clone of BLTouch.
While sensor is triggered with 240 ohm resistor, output value is 1.3 v. it's low level and not worked!
After i install 560 ohm resistor then output voltage becomes 2 v and it is a hi level and now work fine.
I wrote this information may be it's help anybody who use TLTouch sensor.Thank's for all, and bye!
-
The IR probe results have one corner point much lower than the rest. There must be something in that corner to cause that, or perhaps you are probing too close to the edge.
hey dc42. I have a bltouch smart and doing mesh bed compensation on duet wifi. Why is my z-axis not moving like in the video on the first page of this thread? Does mesh bed compensation and autobed compensation cause different z-axis behavior? I also have two steppers in the z-axis connected to ZA and ZB on the duet wifi board. lmk, thanks.
-
hey dc42. I have a bltouch smart and doing mesh bed compensation on duet wifi. Why is my z-axis not moving like in the video on the first page of this thread? Does mesh bed compensation and autobed compensation cause different z-axis behavior? I also have two steppers in the z-axis connected to ZA and ZB on the duet wifi board. lmk, thanks.
How is it behaving then?
-
hey dc42. I have a bltouch smart and doing mesh bed compensation on duet wifi. Why is my z-axis not moving like in the video on the first page of this thread? Does mesh bed compensation and autobed compensation cause different z-axis behavior? I also have two steppers in the z-axis connected to ZA and ZB on the duet wifi board. lmk, thanks.
How is it behaving then?
It stays stationary unless there is a layer change. What I noticed on the other video is that the z-axis steppers would move back and forth based on compensation needs. Does this mean my bed is just perfectly leveled (highly unlikely)?
-
I fear I may have messed up! I think I have had my BLTouch connected with a 10ohm resistor instead! Could I have damaged something? I have recently rebuilt the printer and when testing the BLTouch will not self test or fire. It does reset but nothing else? I am picking up some new (240ohm metal film) resistors tonight to replace the current (wrong) one.
Have I screwed my board?
-
It's unlikely that you have damaged the Duet.
