gmoccapy tool change issue after apply

More
14 Jan 2015 13:23 #54993 by Kaushik
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

Please Log in or Create an account to join the conversation.

More
14 Jan 2015 15:24 #54994 by cmorley
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
The following user(s) said Thank You: Kaushik

Please Log in or Create an account to join the conversation.

More
14 Jan 2015 19:24 #55001 by newbynobi
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
The following user(s) said Thank You: Kaushik

Please Log in or Create an account to join the conversation.

More
16 Jan 2015 23:18 - 17 Jan 2015 13:10 #55085 by Kaushik
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...
Last edit: 17 Jan 2015 13:10 by Kaushik.

Please Log in or Create an account to join the conversation.

More
18 Jan 2015 01:51 #55129 by newbynobi
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
The following user(s) said Thank You: Kaushik

Please Log in or Create an account to join the conversation.

More
21 Jan 2015 13:56 #55231 by Kaushik
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 :)

Please Log in or Create an account to join the conversation.

More
22 Jan 2015 02:35 #55249 by newbynobi
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 ....

The following user(s) said Thank You: Kaushik

Please Log in or Create an account to join the conversation.

More
22 Jan 2015 13:29 #55259 by cmorley
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
The following user(s) said Thank You: Kaushik

Please Log in or Create an account to join the conversation.

More
23 Jan 2015 16:00 #55289 by Kaushik
Okay.....
Thank you Chris M for explaining the issue.... :)


Kaushik

Please Log in or Create an account to join the conversation.

More
27 Feb 2015 23:40 #56335 by LAIR82

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

Please Log in or Create an account to join the conversation.

Moderators: newbynobiHansU
Time to create page: 0.125 seconds
Powered by Kunena Forum