Hypercube Piezo Orion - I dont understand...

gtj0

Which version of RRF?
Which version of the Orion? Does it have the two rows of pins, one for analog and one for digital or just one row for digital? If you're connected to the digital pins on the Orion, you should use P8 for M558. If the analog pins, use P1. Also if analog, use I0.

You have M574 Z0 and that needs to be Z1.

soreloser

Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.0 (2020-01-03b3)
Its the newer version of the sensor, i have tried both sets of pins, right now using P8 on the M558. I will change the M574 to Z1 and see. thanks!

soreloser

Same;
i rechecked the wire connectivity and that it is properly oriented in the z probe port of the duet, all good (oh ya, and its wired to the digital part portion of the Piezo).
I turned down the sensitivity to see if it might be triggered prematurely, same. When i send the M558 code i receive 'Z probe 0 not found' , what should it be returning?

Phaedrux

Can you post your m558 command as it is now?

soreloser

M574 X1 Y1 Z1 S0
M558 P8 I1 R0.4 F300 X0 Y0 Z0

soreloser

Should i see some reference to the sensor in the status panel of GUI?

Phaedrux

You are missing a few parameters like the dive height, travel speed. X0 Y0 Z0 is no longer used, so remove those. Also in RRF3 the inversion is done in the pin definition and not the M558, so remove the I1.

Try this M558 P8 H5 F300 T6000 R0.4 C"!zprobe.in"

C"!zprobe.in"` this must reflect the pin you're actually connect to. Are you using the Z endstop pin or the z probe pin? How are you wired?

Delete your M574 X1 Y1 Z1 S0 and use the RRF3 syntax:

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

You don't need a definition for Z here since you're using a probe.

I think this should get you going with RRF3.

gtj0

Once you get to the point of seeing the probe, I'd actually use it in analog mode because you don't have to fiddle with that tiny pot. When it's connected properly, you should see a constant reading of about 525-575 and touching the nozzle should cause the reading to jump then come back again. It happens too fast for the web console to keep up sometimes though. You can then set your G31 trigger threshold to around 10 + whatever the stable reading is. Of course, test that it stops the Z movement with your finger before you let Z home on its own.

soreloser

@Phaedrux
I am using the z probe input. Thank you, I will try your suggestions when i am in front of the machine tomorrow

soreloser

@gtj0 Ok, cool - makes sense!

soreloser

@Phaedrux WOW! Awesome! it works. Thank you for your assistance, I learned a lot. I have much more to do but this portion now works. My configuration portion looks like this;

; 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 '

; Z-Probe
M558 P8 H5 F300 T6000 R0.4 C"!zprobe.in" ;DIGITAL mode, NO/NC, delay, speed, used as axis endstop
G31 X0 Y0 Z-0.1 P600 ;X, Y, Z offsets, sensitivity/threshold

For now it stays digital until final tuning and try analog, thank you everyone.