Comments (6)
I ended up using SET_GCODE_OFFSET Z_ADJUST=-0.2
in my CALIBRATE_Z
macro override, at the end. Turns out I wasn't verifying with GET_POSITION
for the gcode_base
variable, which did show SET_GCODE_OFFSET Z_ADJUST
working.
I think the solution here would be to allow for switch_offset
to allow NEGATIVE numbers.
As for skipping the switch probe, I had to edit the z_calibrate.py
to:
# switch_zero = self._probe_on_z_endstop(self.helper.probe_switch_site)
switch_zero = nozzle_zero
I wonder if this could submit this as a Pull Request? The possibility of skipping the Switch Probing step by having it set to the same as the Z endstop?
I'm thinking it could be a simple boolean, defaulting to False to always probe the switch surface. True would skip it / force it to be set to the same as the Z endstop.
from klipper_z_calibration.
I'm not sure why or how you use this extension. If you have a load cell at your nozzle, then this extension would be pointless since you already have a direct nozzle-probe 🤔
So, this flex means that you need to over travel by 0.2 until the sensor reacts? Is this a fixed or varying value?
from klipper_z_calibration.
I'm not sure why or how you use this extension. If you have a load cell at your nozzle, then this extension would be pointless since you already have a direct nozzle-probe thinking
ah, i didn't mention that in all of that text above. The CR6SE comes with two z-endstops. One on the load cell/probe itself.
But, there's also an Optical sensor - that no one uses! Well, I want to use it!
I use this plugin for the optical Z for ultra fast Z homing (50mm/s now) as a FIXED offset of something like 0.875 - based on the probe's exact measurements. Then the load cell at much slower speed (@ 4mm/s) for precise offset to take away from this 0.875 number for a precise offset.
Minus, the negative -0.02 that I need to offset the probe, because of the "Bend" of the load cell (see below).
So, this flex means that you need to over travel by 0.2 until the sensor reacts? Is this a fixed or varying value?
It's fixed via an adjustable POT on the circuit board. but yes, once it is set, it remains roughly at that -0.02, or at least that's what I tuned it for for the best non-false-positives.
from klipper_z_calibration.
so basically, i'm cheating... i;m using this plugin to take two measurements, and then the negative -0.02 to account for the load cell.
I got around all of that by commenting out the line above. And I suggested making a PR to add that as a new variable in the ocnfig, that can be flipped on/off (defaulting to False, so it's backwards compatible).
My entire homing, including Z-homing, is extremely fast. Been needing to make a video about it as it's really impressive with the high-speed and and low-speed.
from klipper_z_calibration.
This is a nice creative solution!
But, since you misuse this plugin, I will not introduce an option to disable the probing on the switch. This step is essential for the intended purpose.
The core function is just the probing on the endstop. Maybe Klipper could be more flexible on this point. Then a little macro would be enough to achieve this 🤔
from klipper_z_calibration.
Aiight, if no option to set or override switch_zero
, then I'll close the issue. Thanks again for looking!
from klipper_z_calibration.
Related Issues (20)
- Code issue in clearance variable HOT 4
- calibrate_z crashes printhead into bed HOT 1
- If no Bed Mesh, it uses Z endstop height as Zero Position HOT 1
- Is it possible to have a dedicated Z Switch pin instead of just using the Probe Pin? HOT 10
- Automatic detection of the offset between nozzles of different tools. HOT 1
- At end of calibration i get a "unknown command" HOT 2
- [FR] Support for IDM Scanner HOT 7
- Perform Auto Z at KAMP Center HOT 1
- Move from clearance to safe_z_home when no [probe] section defined HOT 2
- Potential issues with oldham couplers HOT 1
- Z always off HOT 1
- Disable "Save Z Endstop" and "Save Z Probe" when print completes. HOT 1
- Klipper warning max_deviation HOT 1
- AttributeError: 'PrinterProbe' object has no attribute 'sample_count' HOT 14
- Klipper change leading to inaccessability of probe.
- After update no longer getting nozzle position from safe_Z_home HOT 4
- Using possible z_endstop position value HOT 6
- Not seeing the zero_reference_position in bed_mesh section HOT 3
- Offset is always outside the configured range HOT 1
- Error HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from klipper_z_calibration.