Hi,
Is there a list of (significant) changes between these 2 versions of the smart effector? I just bought one and it's 1.3 and I wanted to know if I was going to be missing out on anything important?
The only difference I (think I) can see from the documentation are that the position of the thermistor connector moved and that a micro-fit connector was added for the hotend.
Thanks!
Chris
That was my problem. Switched it to 5v and I am now happily printing.
@Phaedrux thanks, but not a huge deal. It was just a Creality motor and I've replaced it with a slightly better Tevo motor from the scrap pile and it works better than ever now!
@SpeedyDad said in Revo Voron PZ Probe firmware configuration?:
Your wire connections look correct. The PZ PCB is reading the piezo probe correctly. But the firmware is not correctly reading the triggered value. That would most likely be a bad crimp or a misconfiguration. I think it's the misconfiguration because you have:
M558 P8 C"!^io1.in" A5 R1 H5 F400 T24000
which would be the io1.in pin on the main board. The toolboard would be xxx.io1.in where "xxx" is the canbus address of the board. From the comments around the zprobe and previous posts you've made, I'm guess that it should be:
M558 P8 C"!^121.io1.in" A5 R1 H5 F400 T24000
@SpeedyDad I just changed from a klicky probe to a PZ Probe on another printer this morning. The only config changes I had to make were to change:
M558 P5 C"^io1.in" H5 F200 T24000
G31 X0 Y22 Z3.625 P25
to
M558 P8 C"!^io1.in" A5 R1 H5 F400 T24000
G31 X0 Y0 Z0 P100
@SpeedyDad Two of the machines are running the latest stable (3.5.4?) and the idex printer is running 3.6.0-rc2+2 (for a bug fix needed to calibrate the tool offsets).
it sounds like you're not getting anywhere. I would suggest that you do the following:
If one of those things don't work, that's the first problem you need to fix.
if all that works, then I would manually (or via a G92 Z0 G1 Zxx) make sure that you have a large space between your nozzle and your print bed and then run G30 S-1. Let the probe run a for a couple of seconds to make sure it isn't false triggering and then tap the nozzle. If it doesn't stop, hit emergency stop.
If you want to try those steps and report back along with your full config.g, I (or someone else) may have a suggestion.
@SpeedyDad Yes, I have a PZ Probe connected to a (regular, not roto) Toolboard, two running on an IDEX printer with a 3HCL expansion board (I use them to calibrate the tool offsets when starting a multi-material/colour print) and one on another printer just plugged into the regular control board. All of them are working great and I have plans to install more of them.
@SpeedyDad I wasn't suggesting that you change the input pin (it depends on where you have the pz probe connected). Your original M558 was:
M558 P8 C"121.io0.in" H10 F700 T16000
and I was suggesting that you could change it to something like:
M558 K0 P8 C"^!121.io0.in" H10 F700 T16000
M558 K0 P8 C"^!121.io0.in" R0.5 H5 F400 A2 T24000
M558 K0 P8 C"^!121.io0.in" R1.0 H5 F400 A5 T24000
E3D is also suggesting that you turn off the heaters (the B1) but I don't do that and it has been working well for me.
All that said, if you have the correct pin in the M558 command with ^! and it shows not triggered when idle but when you tap the hotend the www interface doesn't show the z probe triggered then you have a problem. You can post your config.g and maybe I (or someone) can suggest a problem. Also, are you sure your crimps are good?
The "commands section" is for non-standard usage of the probe or to reprogram the settings. You can ignore that until you find you want to do one of those things.
@SpeedyDad Your M558 looks like the problem. Mine (just wired to the mini 5+ board on this printer) is:
M558 K0 P8 C"^!io1.in" R1.0 H5 F400 A5 T24000
Note the "^!" to both enable the pullup register and invert the signal direction.
I believe E3D recommends R0.5 and A3 and the T (travel speed) is printer dependent. I gave it a slightly high R (rest before probing) because at least one of my printers generates a lot of vibrations in the toolhead at 24,000 mm/min and I figured it wouldn't hurt. I increased A when I first starting using it to make sure it was giving me valid readings and never changed back because it was working fine. You can choose to values that work for you.
Mine are connected to 3.3V (not 5V) but that shouldn't be a problem. I have setting #4 (filtering enabled) which gives ME the most consistent triggering. YMMV.
@dc42 Again, thanks! I can confirm that this fixes my probing issue.
@dc42 Wow, that was a fast fix! Thanks!
@droftarts I tried all 4 combinations of U vs. X and specifying T0 vs. T1's probe to see if I could make any sense of it. I couldn't. I really don't want to run any strange combination of moving a tool and triggering a different endstop!
What I really want to run is "G38.2 X150 Kx " and have it move whichever tool is active toward 150 until probe #x is triggered. To confirm the behaviour I reported, I just ran the following sequence of commands:
G28
T0
G1 X150 F24000
T1
G1 X150 F24000
G1 X0
G38.2 X150 K1
G38.2 U150 K1
The G1 commands are to be 100% sure that the axes move as expected (T0 moves to 150 for the first G1 and then T1 moves to 150 for the second G1). The first G38.2 command moves both T0 and T1 until probe 1 is triggered. The second G38.2 command moves only T0 (T1 doesn't move even though it is both active and the tool driven by the U axis).
@dwuk3d Thanks for looking. I'm afraid it's a bug but I wanted to reach out here to see if anyone had experience doing something similar.
Unfortunately, I don't think I can use G1 H4 as I need to move X/Y until a probe is triggered, not the moving axis' endstop.