Marine6680
New member
I am in the process of building a Tridex.
While I am familiar enough with klipper that I can follow guides and even figure out some things on my own, and also Linux console command work, enough that I can follow guides without issues...
I am in no means proficient. I am great with mechanical things and electronics and electrical work. I am an Avionics Tech by profession... But code work is not a strong suit at all.
Currently I have the printer built and mostly running properly. Had a few hiccups with the Y axis homing after redoing the config. (The build is a kit provided by an enthusiast and the config files were included on a drive. I decided to switch to community sourced configs located at this git page https://github.com/joseph-greiner Some of the original included configs seemed off, even though things seemed to be working okay, hence the switch, but while transferring the pin info I got the Y switches mixed)
My three biggest questions currently.
Is there a way to have klipper automatically determine the Z offset between the two toolheads, by using two nozzle probes?
I have two PZ Probes from E3D, not the integrated Revo hotend version, but the standalone version.
If it can be setup in klipper, I would like to use them to make the Z offset automatic. Or at least partially automatic. Even a macro that would take a probe reading from T0 and then T1 and provide the offset amount for me to manually enter into config would be great. I am not very concerned with copy or mirror mode, so the doubletap setup isn't as appealing, but I could switch to it if the PZ probes don't work out.
Next, does anyone have any experience with the PZ Probe and how/well it works?
Edit: The bit about the PZ Probe may be solved now. At least the sensitivity. The accuracy, I needed to do some testing.
Currently I am having a frustrating time with the system being both too sensitive and not sensitive enough at the same time.
I often get false positive triggers during movement as the bed is coming up but not near the nozzle, and I also occasionally get delayed activation where the nozzle hits the bed but doesn't activate until the pressure builds to the point of flexing the mount.
I tried faster movement but lower motor torque, but that actually increased false triggers. Seems like the reduction in motor torque means they need to struggle more, which causes vibrations that then cause false triggering. (My hypothesis anyway) Decreasing sensitivity of the Probe always results in poor performance with delayed activation, but false triggers are reduced or eliminated. I am using default 7 most sensitive setting with vibration filtering. It is the only one that is somewhat consistently working.
Now I began the testing before putting on all the panels and securing the toolhead harnesses with support and chafe wrap with frustrating results. After putting on the rear panel and securing the harnesses false triggers seem reduced but still present. Still frustrating but at least progress.
Accuracy is also an issue, with my Probe consistency sometimes reaching 0.02 deviations.
I am going to attempt a lower motor torque and higher Probe speed again, to see if the panels have helped there.
Being the standalone probes, I am not sure my mounting is correct. I used a metal washer to sandwich the peizo element between the mount and heatsink, then tightened that down snug. It could be that less initial load pressure is required for the Probe to work well. E3D does not provide guidance, and I have found no pictures that show how the prebuilt probe heatsink is assembled in enough detail to gleam any insight.
Any guidance on the PZ Probe would be helpful.
Edit: I found this setting and have it corrected now.
Lastly... Safe Z home position for homing is not centered on the bed. Using the config files outlined above. I have searched through the files for a section that defines this position, but I have not found it. I perhaps overlooked it.
I uncommented all of the 250mm bed sections properly I believe, but a mistake there might possibly be an underlying cause?
Sorry for the wall of text and several questions.
Thanks in advance for any help.
While I am familiar enough with klipper that I can follow guides and even figure out some things on my own, and also Linux console command work, enough that I can follow guides without issues...
I am in no means proficient. I am great with mechanical things and electronics and electrical work. I am an Avionics Tech by profession... But code work is not a strong suit at all.
Currently I have the printer built and mostly running properly. Had a few hiccups with the Y axis homing after redoing the config. (The build is a kit provided by an enthusiast and the config files were included on a drive. I decided to switch to community sourced configs located at this git page https://github.com/joseph-greiner Some of the original included configs seemed off, even though things seemed to be working okay, hence the switch, but while transferring the pin info I got the Y switches mixed)
My three biggest questions currently.
Is there a way to have klipper automatically determine the Z offset between the two toolheads, by using two nozzle probes?
I have two PZ Probes from E3D, not the integrated Revo hotend version, but the standalone version.
If it can be setup in klipper, I would like to use them to make the Z offset automatic. Or at least partially automatic. Even a macro that would take a probe reading from T0 and then T1 and provide the offset amount for me to manually enter into config would be great. I am not very concerned with copy or mirror mode, so the doubletap setup isn't as appealing, but I could switch to it if the PZ probes don't work out.
Next, does anyone have any experience with the PZ Probe and how/well it works?
Edit: The bit about the PZ Probe may be solved now. At least the sensitivity. The accuracy, I needed to do some testing.
Currently I am having a frustrating time with the system being both too sensitive and not sensitive enough at the same time.
I often get false positive triggers during movement as the bed is coming up but not near the nozzle, and I also occasionally get delayed activation where the nozzle hits the bed but doesn't activate until the pressure builds to the point of flexing the mount.
I tried faster movement but lower motor torque, but that actually increased false triggers. Seems like the reduction in motor torque means they need to struggle more, which causes vibrations that then cause false triggering. (My hypothesis anyway) Decreasing sensitivity of the Probe always results in poor performance with delayed activation, but false triggers are reduced or eliminated. I am using default 7 most sensitive setting with vibration filtering. It is the only one that is somewhat consistently working.
Now I began the testing before putting on all the panels and securing the toolhead harnesses with support and chafe wrap with frustrating results. After putting on the rear panel and securing the harnesses false triggers seem reduced but still present. Still frustrating but at least progress.
Accuracy is also an issue, with my Probe consistency sometimes reaching 0.02 deviations.
I am going to attempt a lower motor torque and higher Probe speed again, to see if the panels have helped there.
Being the standalone probes, I am not sure my mounting is correct. I used a metal washer to sandwich the peizo element between the mount and heatsink, then tightened that down snug. It could be that less initial load pressure is required for the Probe to work well. E3D does not provide guidance, and I have found no pictures that show how the prebuilt probe heatsink is assembled in enough detail to gleam any insight.
Any guidance on the PZ Probe would be helpful.
Edit: I found this setting and have it corrected now.
Lastly... Safe Z home position for homing is not centered on the bed. Using the config files outlined above. I have searched through the files for a section that defines this position, but I have not found it. I perhaps overlooked it.
I uncommented all of the 250mm bed sections properly I believe, but a mistake there might possibly be an underlying cause?
Sorry for the wall of text and several questions.
Thanks in advance for any help.
Last edited: