- Posts: 1931
- Thank you received: 394
gmoccapy tool change issue after apply
- newbynobi
- Offline
- Moderator
-
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 ....
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
-
- Posts: 7368
- Thank you received: 2181
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
Please Log in or Create an account to join the conversation.
- Kaushik
- Offline
- New Member
-
- Posts: 7
- Thank you received: 0
Thank you Chris M for explaining the issue....
Kaushik
Please Log in or Create an account to join the conversation.
- LAIR82
- Offline
- Elite Member
-
- Posts: 197
- Thank you received: 3
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
Please Log in or Create an account to join the conversation.
- 10K
- Offline
- Premium Member
-
- Posts: 142
- Thank you received: 33
I input a new tool on a blank tool table screen on gmoccapy, and hit "apply". If I then look at the tool.tbl file, it's empty.
I've edited the tool.tbl file directly with Mousepad. When I go into the tool table screen on gmoccapy, it pulls up the data from the file. But if I hit "apply", the tool information disappears. And when I check the file, it's empty again.
I deleted the tool.tbl file. If I hit "apply", the file is recreated, but it's empty.
In no case have I ever been able to load the tool (tool not found), or set any offsets using the buttons.
Any ideas?
Versions:
Linux Jessie 32-bit
LinuxCNC 2.8.0-prel-1468-gl70bb5a
gmoccapy 1.5.6
Please Log in or Create an account to join the conversation.
- newbynobi
- Offline
- Moderator
-
- Posts: 1931
- Thank you received: 394
I will check on that.
Norbert
Please Log in or Create an account to join the conversation.