Topics created by alexic

@Phaedrux It says that in the Gcode dictionary, I had to look it up!

@alexic said in IR sensor Z probe on RRF3 config issues:

@droftarts I am not using that comand, it was there from a configuration file example.

I was explaining the error message. But be careful when using someone else’s config, it won’t always suit your machine, and may cause problems. Make sure you understand every command, and use the Gcode dictionary to help you.

Ian

I ran the script at probing speeds from 30 to 500, dive height of 5mm - here is the results. My normal probing speed is 50.

; Probe repeatability testing ; Directory "0:/macros/probe-results/" must exist to save results ; Upon completion, download zip file of the results directory, make a file listing of the directory in the form of a text file, save that file ; as a .csv file, import into spreadsheet - setting "-" as the deliminator. G32 ; Home and level G1 Z5 ; Move Z to 5mm height G1 X100 Y100 F2000 ; Move to center of bed M558 F30 A1 ; Set probing speed while iterations <=19 ; Perform 20 passes G30 Z-99999 S-1 ; Execute Z Probe echo "" ^ move.axes[2].machinePosition ^ ",F30," ^ iterations ; Echo the probe result and iteration number to console M28 {"0:/macros/probe-results/"^ move.axes[2].machinePosition ^"-F30-"^iterations} ; Create a file, named as the probe result and iteration number in the ; 0:/macro/probe-results/ directory. M29 ; Close file G1 Z5 ; Move Z to 5mm height M400 ; Wait for current moves to finish

blt31-results-run1.png

From dive height of 15mm (50 samples per probing-speed group)

; Probe repeatability testing ; Directory "0:/macros/probe-results/" must exist to save results ; Upon completion, download zip file of the results directory, make a file listing of the directory in the form of a text file, save that file ; as a .csv file, import into spreadsheet - setting "-" as the deliminator. G32 ; Home and level G1 Z15 ; Move Z to 15mm height G1 X100 Y100 F2000 ; Move to center of bed M558 F30 A1 ; Set probing speed while iterations <=49 ; Perform 50 passes G30 Z-99999 S-1 ; Execute Z Probe echo "" ^ move.axes[2].machinePosition ^ ",F30," ^ iterations ; Echo the probe result and iteration number to console M28 {"0:/macros/probe-results/"^ move.axes[2].machinePosition ^"-F30-"^iterations} ; Create a file, named as the probe result and iteration number in the ; 0:/macro/probe-results/ directory. M29 ; Close file G1 Z15 ; Move Z to 15mm height M400 ; Wait for current moves to finish

blt31-results-run2.png

Raw probing values - results.csv

Sorry for crossposting, actual info for Duet2 + Ender 3 LCD here: https://forum.duet3d.com/post/207704

@alexic said in Z height issue:

@Phaedrux Yes it is a clone, that's the name, 3D Touch. Everytime I wonder if the probe is not the issue, and I'm not sure, I plan to replace it with a IR-probe to clarify this unknown variable.

Before I understood the difference my first two BLTouch were actually clones.

They did not work.

Then I got two genuine v3.0 units and they worked without issue.

Frederick