Giter Club home page Giter Club logo

klackender-probe's People

Contributors

dannidesign avatar delta0001 avatar farva42 avatar hawk16zz avatar kevinakasam avatar oldcrazyeye avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

klackender-probe's Issues

REV_2 Still Uses Z_MIN_PROBE pin in Marlin

On reviewing the Marlin code it appears to use the Z_MIN_PROBE pin for probing with little other options.

https://github.com/MarlinFirmware/Marlin/blob/bugfix-2.1.x/Marlin/src/module/probe.cpp#L611

In the REV_2 README I don't see you resetting the Z_MIN_PROBE to use the Z_STOP_PIN. It appears without doing this then REV_2 for Marlin would continue to use the Z_MIN_PROBE which is what REV_1 uses.

I think to change this some redefining in the Configuration.h would be needed, but the README doesn't mention it.

bed mesh macro

better macro for bed mesh:

[gcode_macro BED_MESH_CALIBRATE]
rename_existing: _BED_MESH_CALIBRATE
description: Perform Mesh Bed Leveling with klicky automount
gcode:
	G90
    PROBE_OUT

    _BED_MESH_CALIBRATE {% for p in params
           %}{'%s=%s ' % (p, params[p])}{%
          endfor %}

    PROBE_IN

it works with the original bed mesh button

Chamfer of 0.4mm not used on bottom edge of parts

Fillets are used on some parts, other parts don't have anything at all.

Chamfer @ 45º on the bottom edges of parts give enough room to prevent elephants footing. Fillets shouldn't be used due to them having too much overhang making the 2nd layer look very sloppy. Especially with plastics like ABS.

Example of how they parts should look:
image

You can see the difference in how they lay down in the slicer too. Fillet on the left, Chamfer on the right.
Much less gap fill used in the slicer on these smaller parts. Might be harder to see, but the overhang difference can be seen here too.
image

[QUESTION] Unklicky...possibly?

Hello. I would like to know if you are working on a version to support the superior Unklicky. It uses magnets instead of a micro switch which causes for better accuracy. I am going to be using this on my Voron, so I would like a shared ecosystem. Thank you in advance!

[Feature Request] Use klickyprobe macros

Instead of using the macros included that aren’t really written well, utilize the existing work of the Klicky Probe macros.

This would allow for a much better user experience.

The existing macros could be updated to be much better if the rename_existing: function was utilized.

Z_TILT_ADJUST issue

The Z_TILT_ADJUST macro needs to call _Z_TILT_ADJUST instead of Z_TILT_ADJUST otherwise it becomes a recursive call.

Also the example config should include a SCREWS_TILT_CALCULATE macro.

Missing a Critical Marlin Step In Readme (for CR/BL Touch users)

Critical for me at least! I migrated from a CR Touch, so I knew I had to comment out "BL Touch" but not having the change below really was a bummer!

(currently line 1280 in Configuration.h) #define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN

If you are coming from a Hall Effect sensor, or many other sensors.... you have this commented out.

I'd throw together the two changes and a heading in the instructions for those poor souls that die a little inside every time their rig crashes into the bed.

Otherwise, even though I had to customize some stuffs to accommodate a Sprite Pro, this thing works! Can't wait to get it really fine tuned!

Probe mount doesn't fit to Ender 3S1

Probe mount from STL folder doesn’t fit to Ender 3S1. Horizontal opening on probe mount which is included is 17.1mm and tab on 3S1 carriage is 19.6 mm wide and 3mm in height.
Can You include mount for Ender 3S1 to measures and include in 3S1 folder?

Wiring an Ender3 S1 Pro issue

I'm trying to wire the micro switch to the Ender3 S1 Pro and I'm not having any luck. I have been trying the "Z Limit Interface" but it's 3 prongs, so I've tried all the combos but none of them work.
How am I supposed to wire the Klack to the S1 Pro motherboard?

CREALITY-3D-Ender-3-S1-Ender3-S1-PRO-Silent-Motherboard-32-Bit-TMC2208-Mainboard-Silent-Printing jpg_80x80

relative_reference_index in the bed_mesh section is deprecated

Klipper deprecated the relative_reference_index option for the bed_mesh in the version 20230619, details on how to update the configuration are specified here.

After a quick read, my two cents is that we could replace it with the zero_reference_position pointing to one of the bed leveling screws.

"Probe triggered prior to movement" error randomly popped up when running AUTO_BED_MESH

Hi all,

I'm making this issue to share my experience troubleshooting error mentioned and the solution, in case anyone is experiencing the same issue.
Just managed to installed the parts and get the probe to smoothly goes in and out of its dock.
Absolutely no problem when homing Z.
Tested manually attaching probe to trigger the probe on bed, and raising the head(Z) +1 at a time, probe gets open at sometimes at +1, other times at +3. I.e ranging from Z 0 to Z 3
This causes issues during calibrating bed mesh, specifically when taking multiple sample as the probe get stuck in "Triggered" status and which give me a clue that it needs to move upwards(+Z) more.

Solution:
Go into printer.cfg and scroll down to the [probe] section. Increase the value of "sample_retract_dist".
For me, I made the value as the same as my "z_offset" value.

Hope this helps someone.

Probe_calibrate not working so well

i used this macro:

[gcode_macro calibrate_nozzle]
gcode:
  G28
  PROBE_OUT
  G0 X117 Y117 # the center of print bed
  Probe_calibrate
  PROBE_IN

it does good on G28 and on probe_out, when it get to probe calibrate it starts good but when it returns the probe it move to x0 y-8.
there is a reasen to move it to 0 0 on probe_in?

Please help Klackender Config issue

I just set up the klackender config and i got this error from klipper any suggestions?

Section 'menu __main' is not a valid config section

Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
Printer is halted

Code parsing errors

When I added the klackender config file, mainsail gave me this report:

Klipper reports: ERROR

Source contains parsing errors: '/home/biqu/printer_data/config/Klackender.cfg'
[line 134]: 'PROBE_OUT\n'
[line 135]: '_BED_MESH_CALIBRATE\n'
[line 136]: 'PROBE_IN\n'

Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
Printer is halted

Ender 5 support?

At the lab, we have an Ender 3, and Ender 3 Pro, and an Ender 5 Pro. Would be nice to be able to use this on all 3 printers :)

I imagine the part that goes on the toolhead would be identical, but the part that mounts to the frame would be a bit different, and probably the load/upload sequences would have to be tweaked too.

Marlin

Hello, this looks pretty genius. I especially like that you don't need to rewire the motherboard but can use the existing endstop cable (and possibly re-use the existing endstop switch?).

A kind user (Farva) on my Discord figured out how to configure Marlin for the Rev2. I had no time to test it yet. Feel free to join my server and test it out on your own. Once I tested it, I will upload detailed instruction here.

Is there any update on this? Could you post/link to that firmware configuration please?
Thanks, and keep up the great work.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.