Piezo Orion + RRF 3.... Problems
-
@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 yourG31report when you execute it?
did you run repeatability macro? -
-
@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
-
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
-
@arhi i prob @ 80 on bed and 130 on nozzle
-
@chop those temps should be ok, just increase the offset a bit (absolute increase, the value need to go more in the negative)
-
@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?
-
What thats mean?
-
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 -
@arhi what is z=0 Datum?
-
@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
-
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.
-
@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 -
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
-
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 -
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.
-
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?
-
@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.
-
i try to explain
i want to add,heat to bed and hotend to X celsius(shpuld be print temp), do a makro, prob the bed, start the print.
the printer should do this one ervery print. where i have to add this commands?
-
The slicer should be adding the temp commands that you set in the slicer settings.
