Precision Piezo Orion: Errors when probing
bLiTzJoN last edited by bLiTzJoN
Using 2.02RC3 (and 2.01) on a DuetWifi equipped Delta; I can't get a reading when I auto-calib - every point errors and I can see the effector flexing. It's wired to the zprobe connector. I adjusted the sensitivity accordingly. Set the right z-height (using a manual method). When I tap the hotend I can see the P0 turn to P1000 which to me means it's registering on the board, but not sure why it's not seeing the tap when it probes. In the config.g I have the following:
M558 P8 I1 H2 A2 R0.6 F300 T6000
G31 X0 Y0 Z-0.1 P100
To make sure it wasn't the Orion board, I swapped it out with another and still experience the same results.
Is this a new problem? Have you recently upgraded to 2.02RC3?
What's the recommended probing speed for the Orion? 300mm/min sounds rather slow to me.
This is a new install.
As for the F value, "Probing speed F parameter (in mm/min). A value from 300-420 is recommended. Slower can give more accuracy but too slow may not trigger, as the probe generates a signal on a change (compression or flexing in the piezo disc."
I've messed with the settings for several hours and the best I can come up with is using the following settings:
M558 P5 I1 R1 F380 X0 Y0 Z0 H2 ;
G31 X0 Y0 Z-0.05 P100 ;
Unfortunately, the reading is very inconsistent and on some points will either not move or slams into the bed. I have a video but can't post it (spam).
@moriquendi I started with 2.02RC3, downgraded to 2.01 and then returned back to 2.02RC3 as it didn't seem to matter.
Firstly I'd suggest changing from mode 5 to mode 8 ( change P5 to P8 in your M558 ), this works better in most cases. Secondly, change from P100 to P500, the output of the Orion is digital, having a low trigger value makes it more likely to be triggered by noise on the signal wire.
Can you give some more details of your printer and mechanical set up? Are you using parts you designed/printed yourself or parts supplied by me? What are your acceleration and jerk values?
Another thing that often helps in situations like this is to loosen the four assembly screws slightly, start with 0.5 turns and test, repeat if necessary.
peirof last edited by
I am having similar issue, I have instaled PPO, with this config... M558 P5 I1 R0.4 F300 H5 X0 Y0 Z0 T2400, until yesterday works fine... But now its very inconsistent.
When I Command duet do autocalibration, In aprox. 70% of probed points I have a Hard tap... And when finish calibration the mean error its aprox 5x before error.
When I push the nozzle with a object, smooth, PPO, detects the tap, and Led change color to blue...
What can i try? Downgrade?
Actual firmware... 2.02RC2(RTOS)
Did you see any improvement adjusting the assembly screws?
@peirof, what machine are you using?
peirof last edited by peirof
@blitzjon Tevo Little Monster...you only( ) have 6....
So, my issue was the top mount I designed was too rigid causing noise. I've since modified the design and have it working on two of my machines now. Here's the writeup: https://www.thingiverse.com/thing:3192818
CaiJonas last edited by
Hi guys, I had the same issue. The solution is to change the diameter of the part above the pcb. It should be around 17.5mm. My expirience is, that a bigger diameter makes it much worser.