Probing G30 Help
-
Problem with G30 S1..
I home first then jog down to 5mm to 10mm above bed and in the web console i enter a G30 S1
It seems to probe 3 times and retract every time.
The probe doesn't stop at trigged height so i can't seem to get the correct Z offset value
the z after retract always seems to end up at around 7mm above bedIts a delta printer and a precision piezo probe..
seems to be triggering ok seems it hit and retract fine, no crashing into the bed...just doesn't stop at the trigged height..
this is my Z probe form config file
; Z-Probe M558 P3 C"zprobe.in" R2 H5 F1200:800 T3000 A3 S0.03 K0 G31 X0 Y0 Z2 P720 M557 R85 S20
my firmware installed
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3RC2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-05-11 14:55:01
-
@gorf26 you want
G30 S-1
notG30 S1
G30 S-1 ; Probe the bed at the current XY position. When the probe is triggered, do not adjust the Z coordinate, just report the machine height at which the probe was triggered.
https://duet3d.dozuki.com/Wiki/Gcode#Section_G30_Single_Z_Probe
-
Thanks a stupid mistake going blind in old age works now..
Have another question, is there anyway to put this code in the config. file
I have tried but doesn't seem to work.G31 P{sensors.probes[0].value[0] + 8}
i have it in a macro but would like not to have to run the macro if possible, if for some change i forget to run the macro and run the g30 i always get the message probe
already triggered..Thanks
-
@gorf26 said in Probing G30 Help:
G31 P{sensors.probes[0].value[0] + 8}
i have it in a macro but would like not to have to run the macro if possible, if for some change i forget to run the macro and run the g30 i always get the message probe
already triggered..I don't understand what you're trying to do with that.
-
I'm not much of a programmer, so not real sure why the code is needed but the piezo will not work without the macro being run before a probe move.
The probe is set in analog mode.
If i don't run the macro before any probe moves the probe shows as always being triggered.I am just looking to see if there is a way to have, G31 P{sensors.probes[0].value[0] + 8}, run at startup, like in config file or something along that approach. I think it will only need to be run once endless a reboot or estop happens..
make any more sense?
Thanks
-
I guess it could go in homeall at the start so that it gets run before probing.
I'm still not clear on what it's doing though other than adding 8 to whatever the current probe value is. I guess just setting the sensitivity above whatever the noise floor currently is.
Try it in homeall.
-
Thanks I will try adding in the homeall and see how that go's..
I think that is correct i think it changes the sensitivity level, but not sure and for me right now it's the only way the probe will work, without DWC thinking it is already triggered
When i first load DWC it shows red color in the probe value dro, when i run the macro it changes color and works..
Thanks
-
G31 X0 Y0 Z2 P720
Have you tried just raising the trigger level in config.g ?
Just change the P parameter until you don't get the triggered messagee.g.
G31 X0 Y0 Z2 P750
To test you can do it in the console first then check the state of the sensor
It should show in DWC whether it thinks it's triggered or not. -
Thanks i have tested from P720 to P800 was getting the same results.
I have added the G31 P{sensors.probes[0].value[0] + 8} to my homedelta and that is working fine.
The G32 was done with the bed at 60C and the hotend at 220CI did the G32 and heightmap looks ok I guess
![alt text] (image url)So Should i do a G32 every time before a print,?
And should I do a G29 once and load the map or do that before each print also.?Thanks
-
@gorf26 said in Probing G30 Help:
So Should i do a G32 every time before a print,?
And should I do a G29 once and load the map or do that before each print also.?See what you can get away with.