BLTouch Config.

fcwilt

Please get in the habit of using the </> tag.

Your config.g file using </>

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Wed Dec 26 2018 13:31:24 GMT+0000 (Hora padrão da Europa Ocidental)

; 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

; Network
M550 P"Cr 10 - S" ; Set machine name
M552 S1 ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; 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 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z408.00 E820.00 ; Set steps per mm Z400
M566 X600.00 Y600.00 Z24.00 E1200.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X30000.00 Y30000.00 Z300.00 E1500.00 ; Set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z100.00 E10000.00 ; Set accelerations (mm/s^2)
M906 X750.00 Y1150.00 Z750.00 E1050.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S300 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y300 Z400 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 S1 ; Set active high endstops

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000 A5 S0.02 ; Set Z probe type to bltouch and the dive height + speeds
G31 P25 X-40 Y-10 Z1.20 ; Set Z probe trigger value, offset and trigger height
M557 X50:250 Y50:250 S50 ; Define mesh grid

; Heaters
M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4725 C7.060000e-8 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S290 ; Set temperature limit for heater 1 to 290C

; Fans
M106 P0 S0 I0 F30 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0.5 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S0 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

; 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

; Automatic power saving
M911 S22 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

; Custom settings are not configured
M912 P0 S-1 ; calibrate MCU Temp

; pressure advance
M572 D0 S0.3 ; pressure advance

Your homeall.g file using </>

; generated by RepRapFirmware Configuration Tool v2 on Wed Dec 26 2018 13:31:24 GMT+0000 (Hora padrão da Europa Ocidental)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
M98 Pdeployprobe.g ; deploy mechanical Z probe
G1 S1 X-305 Y-305 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X5 Y5 F6000 ; go back a few mm
G1 S1 X-305 Y-305 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X200 Y150 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

M98 Pretractprobe.g ; retract mechanical Z probe

I will look at them now.

Frederick

Hélder Rocha

Ok...Tks

Stephen6309

@Hélder-Rocha It's the 5th symbol from the right at the top of the reply dialog.

fcwilt

Hi,

You are using firmware that is very old.

The most recent v2 firmware is v2.05.1 but my memory may be faulty on that.

The most recent v3 firmware is v3.2.

I suggest you update to at least the most recent v2 firmware.

I cannot be sure about your files as I have no idea what those files should look like for v1.21

Frederick

Hélder Rocha

Well, Frederick, there´s a big problem right there. Let me see if a find out how is that done, because i am a complete noob on this stuff.

fcwilt

@Hélder-Rocha said in BLTouch Config.:

Well, Frederick, there´s a big problem right there. Let me see if a find out how is that done, because i am a complete noob on this stuff.

I cannot help you with firmware that old.

There are special steps that sometimes need to be taken when make a big jump in versions.

For example, when I wanted to go from 2.05.1 to 3.1.1 (the most recent v3 at the time) I had to first go to 3.0.0 before I could go to 3.1.1.

I'm sure somewhere here can advise you or point you to the need references.

Perhaps if you started a new topic regarding your firmware upgrade situation?

Frederick

Phaedrux

Can you send M122 and post the response here so we can see what firmware version is actually flashed?

Hélder Rocha

@fcwilt said in BLTouch Config.:

most recent v2 firmware

Well i have the V2 2.05.01 at the momment!

Hélder Rocha

but i ll send the M122 just to check it out

Phaedrux

Ok, so the config for the BLTouch looks fine for 2.05

What problems exactly are you having?

Does the Bltouch work to home the Z axis?
After homing, does sending the nozzle to Z0 lead to the nozzle just touching the bed surface?

If you've gone through the test and calibrate page to set your XYZ offsets, have you now tried running G29 to get a map of your bed surface?

https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation

Hélder Rocha

@Phaedrux HI... the problem i am having is that, after i calibrate the offset on G31, defining the 0.0 position etc etc, when i do the first probe, the nozzle gets agaist the bed! If i increase or decrease the z value on the G31, it goes allways agaist the bed! Also, i dont haveproperly constant values when i try to define the z offset! It changes constantly. I read that a anti-backlash nut could help. I dont know!

Hélder Rocha

@Phaedrux Oh, and yes, Bltouch work to home the Z axis.
After homing z, it stays on 5mm plus the z offset value above the bed.
I made all the steps that are on that link you sent and yes, i made also the map. Dont know hou to use it, but yes, i made it!

Veti

@Hélder-Rocha said in BLTouch Config.:

when i do the first probe, the nozzle gets agaist the bed

do you mean it does not stop when its triggerd.
or the nozzle hits the bed before its triggered?

Hélder Rocha

@Veti i beleave it stops when triggered, and goes up for 5mm. At this moment the Z offset is marked with 1,90. So, after it makes the probe, Z ascend 5mm, in the panel i can check z height is 6,90 (5mm+1,90)... all good, but if i down it 5mm, it stops on Z 1,90, but against the bed. After slice a test cube, just to see if it runs ok, the nozzle does not get the 0,02 mm height i nead for the fisrt layer, because its touching the bed!! But Veti, i starded to download the new versions of firmware, i all strt over. Lets forget this for now. Different issues just appear. Ill open a different topic. Tks a lot for your help.

Veti

@Hélder-Rocha said in BLTouch Config.:

check z height is 6,90 (5mm+1,90)... all good, but if i down it 5mm, it stops on Z 1,90, but against the bed.

this means that your trigger height is incorrect

shubharora734

I made all the steps that are on that link you sent and yes, i made also the map. Dont know hou to use it, but yes, i made it!

Veti

@shubharora734

but if i down it 5mm, it stops on Z 1,90,

so decrease your trigger height by 1,9

Hélder Rocha

@Veti so, you suggest i put my offset in 0.0? But look Veti, i just started to update my firmware to 3.0 and found my first problems. If you care to help me on other topic i created in "firmaware instalation categories", ill be thankfull. many tanks

Veti

@Hélder-Rocha said in BLTouch Config.:

i just started to update my firmware to 3.0 a

please update to 3.2 there is no point in staying on 3.0

Hélder Rocha

@Veti all the surch i made, no one advices to go from 2.05 to 3,2 directly! The sugestion is to go first to 3.0, and then update to 3.1 or 3.2! I dont know nothing about this, just following the masters