Tool offset patch

Thanks guys, I got it working by doing as andypugh said. I also did this command...

sudo make install

I tried it first without that command and it didn't work. I tried it again with it and now its working as it should.

Thanks guys, I got it working by doing as andypugh said. I also did this command...

sudo make install

I tried it first without that command and it didn't work. I tried it again with it and now its working as it should.

jlviloria wrote:

Chris, there is one detail, I notice now add the value of the compensation to 1000n, and Tn is the wear.

but assumes wear backwards. digit 1 in Z and the display shows -1

sorry is my mistake

thanks

Jorge Viloria

Jorge

To be clear, did you find a problem?

Chris M

Chris,

Sometimes the alarm goes, Tn not found tool table.

when it happens I have go to back to the tool table and give "apply" and solve the problem.

He had thought that he had not pressed "apply" but it happens with any number of tools.

no matter that this editing the number 1, LinuxCNC not find any tools.

Thanks,

Chris, I have a doubt.

I'm doing the following test:

1.0) compensated the tools 5, 6 and 8.

2.0) No. 8 position tool, apply Z = 5mm wear

3.0) and also apply 5mm, tools 5 and 6.

4.0) but the tools 5 and 6 assume no wear.

5.0) I have to call each and apply the wear, with the tool in position.

assume all commercial controls wear without the tool is in position.

Thanks,

Jorge Viloria

Jorge

Yes this patch needs work.
There are a couple this not right with it
You sre chaging wear offsets with the tool table or using MDI?
I realize now that wear compensation is fundamentally different from geometry offsets.

More work to do - Thanks for report - sorry for results

Chris M

Even with the problems we have exploited with the patch it is still better than no patch. Please keep up the good work and Thank you Chris and D Rogge for starting the development work in this area. We are running two Large lathes on this patch and even with the issues we are making it happen. I wish I could write the code myself but no where near that level of understanding, we will however gladly do real testing on this. Looking forward to jog while paused too......Just a plug for what we need.


Again Thank you for your efforts.

It's true what they say SRT, a change of sky to ground. You helped to improve the work of Rogge.

My lathe is producing with your patch.

I found a solution, is to select the tools that I will change, if swap then apply them before I applied one by one. and if it works ..!

Friend my apology stolen a space this post.

How do I get my monitor I assume the rotation, said "rotation not supported".
I'm working on a GUI, from GScreen, but will not let me rotate the monitor.

Thanks,

Jorge Viloria

cmorley wrote:

hmm I didn't do anything to that patch other then update it so it applied cleanly.
Should be no different from the original.

If your interested in trying a experimental patch I have one available that switches to an INI switch and fixes the G10 problem.
(tool setting changes the wrong offset entry)

File Attachment:

File Name: lathe_styl...atch.zip
File Size:2 KB

Remember experimental - it has minimum testing.
If anyone tries it please let me know.

Chris M

Hello Chris,

This experimental patch, is all that changes is that the values would be put in the opposite fields, wear in 01 and geometry in 10001?

Along with the INI switch?


Rick

We are still having issues with the machine, at random points, telling us that " Requested tool XX not found in tool table", and we have not really noticed any pattern of activity that is making this happen.

We tried moving the "Wear" values to the "Geometry" section of the table and the "Geometry" to the " Wear" section and noticed that now if the fault appears you usually only need to go back to the tool edit page, select the tool and hit apply, instead of having to delete the information and re-add the very same data to get it to recognize the tool.

I just don't know what else I should try to do in regards to troubleshooting this problem.

Thanks

Rick