Scanning Z probe support in RRF 3.5

dc42

@DeadNewbie I can supply firmware binaries with scanning probe support for anyone who wants to try them. The support will be included in firmware 3.5.0-rc.1 which I hope to release 2 or 3 weeks from now.

samlogan87

@dc42 are you guys likely to release a toolboard with a i2c connector?

oliof

@samlogan87 dc42 wrote upstream

For the future, we are considering making a dedicated CAN-connected board to support the LDC1612 as well as tool board variants with this chip on board.

lparnell34

@dc42 I was trying to test z probe scanning but it seems the probe is reading wrong. It says 22768239 under z probe on dwc dashboard. When I run G29 K1 it scans the bed but the max deviation is 1256mm and after it's done scanning it keeps lowering the Z axis until it bottoms out and grinds.

dc42

@lparnell34 you may need to adjust the drive level of the sensor. Run M122 B# where # is the address of the tool board and look at the LDC1612 status at the end. It should report the drive level but it may also report "amplitude error". If you run M122 again it should report a new drive level and no error. After that the sensor should work properly. This is best done with the sensor as close to the bed as you expect it to get during scanning. I set a nominal Z height of 3mm as the trigger height in G31 and I don't expect more than 1mm of error, so I did this at 2mm Z height.

samlogan87

@oliof missed that. Thanks for pointing that out

JoergS5

This post is deleted!

gringo

Z-Probe scanning

Here is another sensor.

A Former User

This post is deleted!

droftarts

@Herve_Smith I should imagine the one @gringo linked is a clone of the Beacon probe. But it does seem to be permanently attached, and has a couple of interesting 'extras' in the video: fast manual bed levelling (just set the probe above the bed at a corner/leadscrew and adjust the bed to the probe) and adjusting the nozzle in real time during the print (though I guess this only works on the first few layers, and with a metal sheet bed). I don't know if Beacon has shown this functionality before?

Ian

dc42

I think the one that @gringo linked to may pre-date the Beacon. It claims to be supported by Marlin since August 2022 and its Github repo goes back to May 2022.

A Former User

This post is deleted!

droftarts

@Herve_Smith Link to doc should be: https://github.com/markniu/Bed_Distance_sensor/wiki/Data-Protocol

Ian

A Former User

This post is deleted!

droftarts

@Herve_Smith said in Scanning Z probe support in RRF 3.5:

I thought i already had linked to it.

You did, but the link didn't work. I posted the correct link. You have since edited your original post, with the correct link. You can see the post edit history by clicking on the small square icon next to the post date.

Ian

A Former User

This post is deleted!

martin7404

I am sorry to write on old tread but I have a lamer question is this going ot support duet 2 wifi

T3P3Tony

@martin7404 our implementation will use a CAN-FD based sensor board so only compatible with Duet 3.

flyscha

@dc42
Any chance you have an update to what these codes should be, with the production SZP?

I've tried using these codes and adjusting accordingly, but there seems to be a disconnect when it comes to at least calling out the C"xxxx" you used in the M558 line. I'm using the CAN1_L & CAN1_H pins, but when I try to call them out while using the CAN address assigned to the SZP, I'm getting an error of "expansion boards do not support Z probe output ports".

Also, I'm getting another error of "Invalid Z probe index" for the G31 line, but I'm not sure if it's a problem stemming from the M558 line.

Any help is appreciated.

Thanks!

dc42

@flyscha use C"120.i2c.ldc1612" assuming it is at the default CAN address 120.