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

New Probe tab to set workspace origin using probe #1879

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pavlot
Copy link

@pavlot pavlot commented Feb 15, 2024

This pull-request contains new Probe tab to quickly change workspace origin and detect tool diameter with probe

image

This tab has two tools to simplify origin definition.

Tool diameter

This part could be used to determinate tool diameter.
Idea is simple: probe width is known. So first touch left probe side, remember position. Next jump over probe, touch right side.
Tool diameter will be equal: right position - probe width - left position.

This tool allow to move gantry in 4 directions: NORTH (+Y), SOUTH(-Y), EAST(+X), WEST(-X).
No difference which one is selected, they can be selected by convenience reasons. Main prerequisite - probe should be touch not longer than 5mm from current position.

Parameters
Direction - where to move gantry to touch probe
Probe width - width of the probe. Gantry will be moved to this distance to find opposite side of probe
Probe height - Z distance required to jump over probe
Tool bounds - this parameter will add extra shift before go down on opposite side, to avoid wide tool touch probe top. It should be greater or equal than tool diameter

In situation when probe cannot be placed close to mill, gantry has to be moved close to probe.

Setting origin

After tool diameter is known, origin can be set for each axis. Tool just touch probe from any side, and this position +/- tool radius set as origin on that axis. +/- sign depends from which side probe was contacted. For Z axis: probe position + probe height

Parameters
Tool diameter - can be set manually, or automatically detected from previous step
Rapid move (X, Y, Z) - distance from current position, where gantry should be placed on given axis. Useful when new origin is far away from current position and moving with probe feed rate will take too long.
Probe move (X, Y, Z) - distance where probe is expected

This operation should be repeated for each axis

@Harvie
Copy link
Collaborator

Harvie commented Feb 16, 2024

NORTH (+Y), SOUTH(-Y), EAST(+X), WEST(-X).

Lets stick with Y+ Y- X+ X-, i've never heard machinist using geography terms.

detect tool diameter with probe

What is the use case for this? Do they sell milling bits with unknown diameters nowadays?

@pavlot
Copy link
Author

pavlot commented Feb 16, 2024

NORTH (+Y), SOUTH(-Y), EAST(+X), WEST(-X).

Lets stick with Y+ Y- X+ X-, i've never heard machinist using geography terms.

no problem, I can fix it.

detect tool diameter with probe

What is the use case for this? Do they sell milling bits with unknown diameters nowadays?

In my case - I have a box of china corn mills, it contains 3 and 3.175 mills which I use to cut pcb edge. This .175 mm hard to measure on corn surface, but it is enough to cutoff ground or narrow wire on pcb. So I measure it on running spindle, which give exact size of cutting width. I have graphite probe which is connected to end of spindles rotor, so it is possible to check it with running tool. This is on 3018

@Harvie
Copy link
Collaborator

Harvie commented Feb 16, 2024

It's rather hard to imagine spinning bit making electrical contact with graphite part without milling it away (therefore making the subsequent measurements useless).
Also why are your traces so close to the edge of PCB that slight variation in bit diameter makes such a big deal? does not seem as good design to me... Also... Maybe don't use roughing bits for final cuts of such precision parts?

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

Successfully merging this pull request may close these issues.

2 participants