gmoccapy tool change issue after apply

Hello....
i was trying to change the tool by changing tool to selected one after applying new offests to tool using tool edit ......but it show me an error that tool is not found in tool table however tool is present in tool table.

Thanx in advance
Kaushik

What version of linuxcnc are you using...there was a fix for the tooloffset widget for this issue (or at least it sounds the same)

Chris M

Hi Kaushik,

did you change the offsets within gmoccapy or with external editor?

If within gmoccapy, please report gmoccapy version?
Step by step description to be able to check here for errors.

Norbert

Hii....
i am using 2.7.3



I am changing the offsets using tool edit option in gmoccapy
wen I searched further...I got to knw dat in interp_find.cc file it is assign -1 to every tool number and thats why its not getting tool but when i open tool file each and every tool is present and its is getting updated also...

I am not able to reproduce that.

Please add you tool file and give a step by step description how I can reproduce the error.

Norbert

Hii

My issue was
1.When I change offsets of tool inside gmoccapy and then i apply those changes to reflect it to tool.tbl file
2.Then I change tool to recently updated tool then it use to give me error "Tool number X not found in tool table"

But,
my problem got solved by downloading and using latest master

But for my curiosity can you plz tell me the issue ie what you changed to get the bug solved

Thanx Norbert and Chris M

Hi,

it wasn't me, it was Chris,
he pushed on 15. Sept. 2014 the following patch:

gladevcp -tooledit, flush tool file to disk

hopefully fix an occasional bug that would make linuxcnc
tell you that the tool was missing from file when it was obviously there.
It seems maybe the file was not written to disk before linuxcnc was
told to read it. why it would be _blank_ I don't know.
I could cause this reliable when testing without linuxcnc, probably
because of the big pause as it tried to talk to non-existant linuxcnc..

Signed-off-by: Chris ....

python and the operating system typically cache data that are to be written to disc, for efficiency reasons.
So we would write the toolfile out to disc and tell linuxcnc to re-read it.
The data was (apparently) cached instead of written right away.
so linuxcnc would read the file then a small time later the file was actually written to disc.
Strangely (but luckily) the file would be blank when linuxcnc re-read it.
And that caused the error.

Now I added a command to force the file to be written immediately

Chris M

Okay.....
Thank you Chris M for explaining the issue....


Kaushik

cmorley wrote:

python and the operating system typically cache data that are to be written to disc, for efficiency reasons.
So we would write the toolfile out to disc and tell linuxcnc to re-read it.
The data was (apparently) cached instead of written right away.
so linuxcnc would read the file then a small time later the file was actually written to disc.
Strangely (but luckily) the file would be blank when linuxcnc re-read it.
And that caused the error.

Now I added a command to force the file to be written immediately

Chris M

And it has worked perfectly since you made this update.

Thanks Again Chris


Rick