Duet3 BLTOUCH3.1 Probe deploys but doesn't trigger on Z Home

Veti

yes.

i said that is what is generated by default if you configure bltouch in the duet configurator.

vistalert

Thanks for confirming

No change in behaviour with the following in config.g
M558 P9 C"^io7.in" H5 F100 T2000

Home Z, bed continues to move when contact with probe has ocurred.

Veti

can you post your homeall.g ?

vistalert

@Veti I haven't yet got a reliable homeall.g as I haven't commissioned the BLTOUCH.

I have Home X and Home Y, which are sensorless (pending delivery of endstops)

So what I'm trying for test purposes is this:

Execute M401 - probe deploys - touch the end of the probe briefly enough to make the BLT light red. It must be released in < 650ms is my understanding, else it errors. At no time during repeated touches does the Z sensor in DWC show anything other than 0.
I use a macro to drop the bed 10mm. I execute HOME Z - with my hand on the power button, because every time I test this, the bed is going to hit the nozzle.

For what it's worth, this is the homeall.g I've built from copy / paste / learning about sensorless homing:

My objectives here, home to front left using sensorless. Then move to centre of bed and probe there for Z home. Welcome your comments recommendations, as always.

M400 					; wait til stuff stops

M574 X1 Y1 S3 			; use stall guard for endstops

M201 X2000 Y2000 		; reduce acceleration on X/Y to stop false triggers

M915 P0:1 S3 R0 F0 H400	; both motors because corexy; Sensitivity 4, don’t take action, don’t filter, 400steps/sec

G91 					; relative Positioning

G1 H2 Z5 F1200			; lower the bed


M913 X44 Y44  			; drop motor currents
G1 H1 X-500 F5000 		; move until the motor stalls - COARSE HOME

M400 					; wait til stuff stops
M913 X100 Y100  		; motor currents back to 100%
G1 H2 X30 Y0 F1200		; move away from end 
M400 					; wait til stuff stops


M913 X32 Y32  			; drop motor currents
G1 H1 Y-500 F4000 		; move until the motor stalls - COARSE HOME

M400 					; wait til stuff stops
M913 X100 Y100  		; motor currents back to 100%
G1 H2 X0 Y10 F1200		; move away from end 

M400 					; wait til stuff stops

G90 					; back to absolute positioning
M913 X100 Y100  		; motor currents back to 100%
M201 X3000 Y3000 		; accel back to original

M400 					; wait til stuff stops
G90 					; absolute positioning

G1 X250 Y250 F13000 	; Move x and Y axis over to bed center so probe is on top of bed
M558 A1 F400 			; Set single probing at faster feed rate
G30 					; Do a single probe to home our Z axis
M558 A3 F100 			; Set tripple probing at slower feed rate
G30 					; Probe again to get a more accurate position

G28 X Y

Veti

@vistalert said in Duet3 BLTOUCH3.1 Probe deploys but doesn't trigger on Z Home:

At no time during repeated touches does the Z sensor in DWC show anything other than 0.

the bltouch pulse is so fast that you will not see it go to 1000.

have you run the bltouch self test? its
M280 P0 S120

(edits it S120)

vistalert

I will try. But that runs on power up no?

At power on, I see the pin bounce twice then the BLT tests with solid red LED.

Veti

@vistalert said in Duet3 BLTOUCH3.1 Probe deploys but doesn't trigger on Z Home:

I will try. But that runs on power up no?

no the self test will retract and deploy the pin 10 times

Veti

what firmware version are you on (i hope the latest 3.1.1)

vistalert

@Veti understood

M280 P0 S120 - Don't get any activity from BLT

My firmware is:
RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later

Veti

@vistalert said in Duet3 BLTOUCH3.1 Probe deploys but doesn't trigger on Z Home:

3.01-RC9

please update to 3.1.1 there were some versions with bltouch problems

vistalert

Sure thing

vistalert

@Veti Completed all the upgrades to 3.1.1

Confirming that the BLTOUCH 3.1 self-test does now execute after the upgrade to 3.1.1.
M401/402 deploys and retracts.

Home Z does not stop the bed raising when probe touches the bed.
Lightly touching the probe doesn't register on DWC Z sensor, the value stays at 0.

A reminder, that as the bed doesn't retract within 650ms, the BLT goes into error.
If I manually push the pin up, then issue the BLT reset command, it does reset ready for next test cycle.

So, some progress

Bear in mind I still have questionable bed.g, homez.g - almost all of my config stuff is copy /paste from elsewhere.

Not sure if Z endstop setting is needed in config,g as it is put there by the configurator, but then people say it's not needed, and others say it is.

Please advise next steps and many thanks for the patient support so far.

Veti

@vistalert said in Duet3 BLTOUCH3.1 Probe deploys but doesn't trigger on Z Home:

Bear in mind I still have questionable bed.g, homez.g - almost all of my config stuff is copy /paste from elsewhere.

i would suggest you create them using the configurator. this will give you clean files with bltouch support. select bltouch there and the generated files should be good.

A reminder, that as the bed doesn't retract within 650ms, the BLT goes into error.

this is not normal, try again with the clean config

vistalert

Got the clean configs.
Do I need to set the Z screw locations AND do something to bed.g in relation to probing close to the screws?

Veti

@vistalert

for now focus on the bltouch problem

vistalert

The BLT and bed are intrinsically linked for Z probing, so don't we need to ensure bed.g and homez.g are in alignment?

What steps do you want me to take now that I have the clean files? These files are initially not suitable without editing (which as a newbie is challenging). For example, the Z was travelling way too fast. There's no support in the configurator for triple steppers.

What specific steps do you want me to take with what specific actions from the UI, or GCODE from the console?

I think we need a less generic approach, and I need to be told: do this, expect this.

We spent all day yesterday circling around my wiring, to find we should have started with the firmware version. Today you're telling me to use the configurator and without specific knowledge of the stepper setup, the bed almost shot off the top of the screws at high speed.

Veti

@vistalert said in Duet3 BLTOUCH3.1 Probe deploys but doesn't trigger on Z Home:

The BLT and bed are intrinsically linked for Z probing, so don't we need to ensure bed.g and homez.g are in alignment?

the bed.g is used for leveling the bed using independent z motors. this required a working probe.
the homez from the configurator should be correct. please post it to verify.

https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help/11

@vistalert said in Duet3 BLTOUCH3.1 Probe deploys but doesn't trigger on Z Home:

What steps do you want me to take now that I have the clean files? These files are initially not suitable without editing (which as a newbie is challenging). For example, the Z was travelling way too fast. There's no support in the configurator for triple steppers.

i wanted to rule out any problem in your config file. if the files from the configurator with selected bltouch do not work, we can rule out a config problem.
for the 3 z motor just add the motors back to M584.
to change the speed of z change it in https://configtool.reprapfirmware.org/Motors Max. Speed (mm/s). the default is 3mm/s. is that too fast?

We spent all day yesterday circling around my wiring, to find we should have started with the firmware version. Today you're telling me to use the configurator and without specific knowledge of the stepper setup, the bed almost shot off the top of the screws at high speed.

remote debugging is hard. and you did not provide all the information specified in the guide on how to ask for help https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help/11

so post the new config files that you generated.

I think we need a less generic approach, and I need to be told: do this, expect this.

see if the bltouch is now working. next maybe the port is bad.
so switch to a different port in the configurator and move the wiring.

but to be honest, i think the bltouch is broken.

Phaedrux

Please post your new files for 3.1.1 config.g, homing files, bed.g and a thorough description of your printer hardware and we can work from there.

vistalert

Thank you @Phaedrux - I will certainly do that. Also, I'd like to apologise to @Veti for the tone of my previous post. I was a little shaken by what happened with the bed raising, but no excuses. I didn't mean to be rude.

Phaedrux

Any time testing motor movement on a new printer it's wise to reduce motor currents in case of a crash. And always have a hand near the power switch. This is true of any printer/board/firmware.