Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Adding 3d Probe wizard in addition to toolsetter #559

Open
Doriangaensslen opened this issue Oct 7, 2024 · 2 comments
Open
Labels
feature New feature or request

Comments

@Doriangaensslen
Copy link

I love how gSender works and shows everything in a very pleasant and beginner-friendly manner. I would love to see a nice wizard, where I could use my 3d Probe (https://de.aliexpress.com/item/1005005786040317.html?spm=a2g0o.order_list.order_list_main.47.61f05c5fbElHdX&gatewayAdapt=glo2deu) to detect z0 y0 x0. This is the only thing, that keeps me from gSender right now with my printNC.

Here an Example how the GUI in ioSender looks like.
image

@JohnOCFII
Copy link

While I'd also love to see the probing wizard enhanced to support the 3D Touch probe, here is a link to a note with some macros that work for probing with the 3D Touch probe. https://forum.sienci.com/t/macros-for-3d-probing/13806/18?u=johnocfii

@walidkayhan walidkayhan added the feature New feature or request label Nov 5, 2024
@axg20202
Copy link

axg20202 commented Nov 28, 2024

Just posting here to second this feature request.

My current workflow (in iosender) is to use a 3D probe to probe a fixed toolsetter switch. This initiates setting up the job WCS and tool length offset. I then jog over to the corner of my workpiece, use an edge and Z finder function in my sender (op's image above) to auto probe for the workpiece origin and auto update G54 wcs. I then remove the probe and load Tool 1 in the spindle, issue an M6 T1 command which sends it off to the toolsetter for tool length offset and return to workpiece origin. Hit job start. Subsequent M6 tool changes in the gcode send the spindle to my park location for bit change, a single click sends it off to the toolsetter for length measurement and then machine continues with T2 operation.

I'd really like to have a similar workflow in gSender using built in 'status aware' tools rather than relying on macros, given how costly probe crashes can be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants