Probe panel for Axis GUI
01 May 2023 18:16 #270418
by Tilman
Probe panel for Axis GUI was created by Tilman
Hi,
some weeks ago we decided to write a simple probe add-in that works regardless of the LinuxCNC version you use. The panel itself is a simple PyVCP which calls the macros through the halui section of your ini file. In other words: It's not more than a few lines XML and some nc files.
We tried to keep it as simple as possible so there is not much more than the basic functions of a probe add-in. You can use up to three different probe tools which needs to be added to your tool table since the calibration will store the data in the tool table, too. As long as any of the probe tools is active, spindle-inhibit is true so there is no risk of spooling your probe wire by accidently pusing the wrong button while probing.
All hal components are loaded in a seperate hal file so als you need to edit at your running configuration are a few lines of your ini.
Download: github.com/hausen8/EasyProbe
Screenshot of the probe panel:
Repeat accuracy of probing the ring gauge after calibration:
Regards,
Tilman
some weeks ago we decided to write a simple probe add-in that works regardless of the LinuxCNC version you use. The panel itself is a simple PyVCP which calls the macros through the halui section of your ini file. In other words: It's not more than a few lines XML and some nc files.
We tried to keep it as simple as possible so there is not much more than the basic functions of a probe add-in. You can use up to three different probe tools which needs to be added to your tool table since the calibration will store the data in the tool table, too. As long as any of the probe tools is active, spindle-inhibit is true so there is no risk of spooling your probe wire by accidently pusing the wrong button while probing.
All hal components are loaded in a seperate hal file so als you need to edit at your running configuration are a few lines of your ini.
Download: github.com/hausen8/EasyProbe
Screenshot of the probe panel:
Repeat accuracy of probing the ring gauge after calibration:
Regards,
Tilman
Attachments:
Please Log in or Create an account to join the conversation.
02 May 2023 07:21 - 02 May 2023 07:25 #270453
by juliankoenig87
Replied by juliankoenig87 on topic Probe panel for Axis GUI
Hey Tilman,
hi everyone,
I would like to add some information. My part of this little project are/was to write the macros. We had some goals:
1) As Tilman mentioned. As easy as possible. On the one hand to implement and be sure that it will work in the future (no python). And on the other hand to be sure to be able to use it in the middle of the night
2) Put any relevant parameter into the ini. This is because any change of some parameters will change the probe results. There is no need to change for example the probing speeds on the fly.
3) Save every calibration data to a save place. So I experimented al lot. Use a file and include it to the ini. Use parameters and made them persistent. In the end the tooltable is the best place in my opinion. Ofsets and ranges (x/y). I borrowed the lathe parameter I and J for the ranges.
4) Make a real calibration. So all 4 triggerpoints got recognized by the calibration macro. No need for manual tuning the runout and compensation of the (normally 120 degree) mechanic of the probe. For this a 180 degree rotation in the calibration is necessary. But no worry. As long as your runout is smaller than 0.1 mm you just need to hit the angle by 10 degrees. Eyeballing is sufficient. Otherwise you need some kind a of a stop for the rotational position.
In the end I checked the normal available probe macros. So Probe screen V1/V2 and NG. And also probe basic. In the end I decided to use the probe basic macros as a starting point. But I changed a lot
So if you have questions feel free to ask here or in the github.
Regards
Julian
hi everyone,
I would like to add some information. My part of this little project are/was to write the macros. We had some goals:
1) As Tilman mentioned. As easy as possible. On the one hand to implement and be sure that it will work in the future (no python). And on the other hand to be sure to be able to use it in the middle of the night
2) Put any relevant parameter into the ini. This is because any change of some parameters will change the probe results. There is no need to change for example the probing speeds on the fly.
3) Save every calibration data to a save place. So I experimented al lot. Use a file and include it to the ini. Use parameters and made them persistent. In the end the tooltable is the best place in my opinion. Ofsets and ranges (x/y). I borrowed the lathe parameter I and J for the ranges
.4) Make a real calibration. So all 4 triggerpoints got recognized by the calibration macro. No need for manual tuning the runout and compensation of the (normally 120 degree) mechanic of the probe. For this a 180 degree rotation in the calibration is necessary. But no worry. As long as your runout is smaller than 0.1 mm you just need to hit the angle by 10 degrees. Eyeballing is sufficient. Otherwise you need some kind a of a stop for the rotational position.
In the end I checked the normal available probe macros. So Probe screen V1/V2 and NG. And also probe basic. In the end I decided to use the probe basic macros as a starting point. But I changed a lot
So if you have questions feel free to ask here or in the github.
Regards
Julian
Please Log in or Create an account to join the conversation.
Time to create page: 0.130 seconds