Piezo Orion + RRF 3.... Problems

chop

@arhi said in Piezo Orion + RRF 3.... Problems:

@chop now you need to manually figure out the Z offset of the probe and put it in the config.

super important is that you heat up your bed and nozzle before you home Z with the orion

super important that you clean a nozzle before you probe (so heat up, wipe, retract, wipe is what I do, visually inspect when nozzle is sitting above center of the bed that nozzle is clean)

after you home Z, you then need to find the "offset"

this offset is normally in the range of 0 to -0.1mm depending on how sensitive your orion is and how fast you probe so it's basically the travel your bed does during a trigger delay. how to setup this offset ... ppl have different preferences, what I do is I'd leave nozzle in the center of the bed (homing position) and do

G0Z1

this should have your nozzle close to the bed but not touching it

disable soft limits

M564 S0 H0

now I put piece of paper between nozzle and bed and start reducing this value

G0Z0.5

G0Z0.3
G0Z0.2
...
G0Z-0.2
...

till I get to point that paper is being grabbed by the nozzle

this position need to be your Z0 so see how far you are from it (you know what Z value you gave it), change the sign of that value and put in the config of the probe (G31, the Z value):
e.g.:

G31 X0 Y0 Z-0.1 P250

hope this helps

btw, do this while everything is HOT and nozzle is clean. Otherwise not much point in using orion, as if you probe cold those are not real value during print.... this is why I like the durable print surfaces like printbite as if you have those soft print surfaces they can dislike the hot nozzle so then you might want to work hot but heat up the bed to your print temperature but heat up the nozzle to lower temp like 100-120C enough for it to "get bigger" but not hot enough to damage the print board if you mess something up

useful read: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

Make sure the dynamic test is successful (Z probe stops when it senses the bed) before doing this.
Cancel any currently active mesh compensation with M561
Use the X and Y jog buttons to position the nozzle over the centre of the bed
Jog the nozzle down until it is just touching the bed or just gripping a sheet of paper. If the firmware doesn't let you jog it down far enough, send M564 S0 to disable axis limits.
Once you have the nozzle touching the bed, send command G92 Z0 to tell the firmware that the head is at Z=0
Jog the head up by 5 to 10mm
Send command G30 S-1. The nozzle will descend or the bed rise until the probe triggers and the Z height at which the probe stopped will be reported. If you are using a nozzle-contact Z probe, the trigger height will be slightly negative. For any other type of Z probe where the probe triggers before the nozzle contacts the bed, it will be positive.
Repeat from step 5 two or three times to make sure that the trigger height is consistent.
In Duet Web Control, go to Settings -> System Editor and edit the config.g file. Set the Z parameter in the G31 command to the trigger height that was reported. Save the file.
Open config-override.g and check that there are no G31 commands in it. If you find any, delete those lines and save the file.
To apply the new trigger height, restart the Duet by sending M999 or pressing Emergency Stop.

Thats what i do...print starts mid air

arhi

testing the repeatability - very important with piezo

G28
M401
G30 P0 X151 Y161 Z-9999
G30 P1 X151 Y161 Z-9999
G30 P2 X151 Y161 Z-9999
G30 P3 X151 Y161 Z-9999
G30 P4 X151 Y161 Z-9999
G30 P5 X151 Y161 Z-9999
G30 P6 X151 Y161 Z-9999
G30 P7 X151 Y161 Z-9999
G30 P8 X151 Y161 Z-9999
G30 P9 X151 Y161 Z-9999 S-1
M402

change X and Y values to be in the center of your bed
more details here: https://forum.duet3d.com/topic/6962/m48-measure-z-probe-repeatability-and-print-to-serial-output/4

arhi

@chop said in Piezo Orion + RRF 3.... Problems:

Thats what i do...print starts mid air

what is your G31 config line now?
what does your G31 report when you execute it?
did you run repeatability macro?

chop

@arhi alt text

arhi

@chop that is nicely repeatable, you have it working good I'd say

you need to change your G31, if you are printing in the air you need to lower the value more into negative... zo try Z-0.1 or Z-0.15 or even more Z-0.2 till you get satisfying first layer. I never seen it need more then -0.15 for ppiezo but .. if I didn't see it, it does not mean it does not exist

arhi

also - did you probe with heated nozzle?! if you are not probing with nozzle and bed at printing temperature that can account for a wrong (too high) required offset

chop

@arhi i prob @ 80 on bed and 130 on nozzle

arhi

@chop those temps should be ok, just increase the offset a bit (absolute increase, the value need to go more in the negative)

chop

@arhi if my bed isnt good levelt. i have to make a grid? with my current z0? and the orion knows where the bes is + or -? or i need g29 s1?

chop

alt text

What thats mean?

arhi

means that your config is not ok

you need to first setup G31 with proper offset
then you need to home
then you need to G29

chop

@arhi what is z=0 Datum?

arhi

@chop it compares the middle height of probed points with homed Z, the error is over 1.3mm .. this usually happens when you home, have wrong offset change offset and then do G29 without homing again ... I suggest you change config, reset board, home, g29, again change config, reset board, home, g29 ... until you are happy ... you can run g29 multiple times but any time you change config / execute G31 you reboot board, home, then g29

Phaedrux

That z datum error message usually means you've loaded a heightmap before you've used G30 to set Z0 first. Or you've used an endstop to set z0 rather than the probe.

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

chop

@Phaedrux i User the probe as endstop.

Is this Configuration correct? :

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y300 Z250 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M558 P5 C"^!zprobe.in" H5 F300 T15000 ; set Z probe type to switch and the dive height + speeds
G31 X0 Y0 Z-0.05 P250 ; set Z probe trigger value, offset and trigger height
M557 X5:300 Y5:300 S20 ; define mesh grid

Phaedrux

That looks fine, but you must be using G30 in your homeall.g. Also make sure you do NOT have G29 S1 in your config.g

chop

@Phaedrux

homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Oct 17 2020 17:51:59 GMT+0200 (Mitteleuropäische Sommerzeit)
G91 ; relative positioning
G1 H2 Z5 F15000 ; lift Z relative to current position
G1 H1 X-305 Y-300 F6000 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-305 ; home X axis
G1 H1 Y-300 ; home Y axis
G1 X5 Y5 F15000 ; go back a few mm
G1 H1 X-305 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-300 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X5 Y5 F15000 ; 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 Z5 F250 ; lift Z relative to current position
;G90 ; absolute positioning

Phaedrux

That looks correct. Now just make sure you have homed the z axis with G28 before creating a heightmap with G29 and the datum error message should go away.

chop

@Phaedrux @arhi @engikeneer

So .. everything works now and it prints well. Thank you all. Now my last question, as I am new to the RRF. How do I start a print now so that a macro is run, the orion tests the bed and then it prints? I don't know which one. g that's coming. or does it have to be in the slicer start g code? if so, how can I tell that he should use a macro?

Phaedrux

@chop said in Piezo Orion + RRF 3.... Problems:

How do I start a print now so that a macro is run, the orion tests the bed and then it prints? I don't know which one. g that's coming. or does it have to be in the slicer start g code? if so, how can I tell that he should use a macro?

I'm not really sure what you're asking.

But usually the slicer start gcode would contain at least a T0 to select the first tool, G28 to home all axis, and a G29 S1 to load the mesh. The slicer would also add the bed and hotend temps.

If you wanted to add something to run before any of that, you can add those commands to start.g in the /sys folder which gets run automatically before the sliced gcode file.