gmoccapy tool change issue after apply

More
11 years 9 months ago #55249 by newbynobi
Replied by newbynobi on topic gmoccapy tool change issue after apply
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
11 years 9 months ago #55259 by cmorley
Replied by cmorley on topic gmoccapy tool change issue after apply
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
11 years 9 months ago #55289 by Kaushik
Replied by Kaushik on topic gmoccapy tool change issue after apply
Okay.....
Thank you Chris M for explaining the issue.... :)


Kaushik

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

More
11 years 8 months ago #56335 by LAIR82
Replied by LAIR82 on topic gmoccapy tool change issue after apply

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.

More
10 years 9 months ago - 10 years 9 months ago #69348 by 10K
Replied by 10K on topic gmoccapy tool change issue after apply
I'm having a similar issue.

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
Last edit: 10 years 9 months ago by 10K. Reason: typo
The following user(s) said Thank You: newbynobi

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

More
10 years 8 months ago #69372 by newbynobi
Replied by newbynobi on topic gmoccapy tool change issue after apply
Let me check on this, it works in 1.5.5.4 with 2.6.12 but show the described behavior on 1.5.6, but I did not make any change to that part of gmoccapy.

I will check on that.

Norbert
The following user(s) said Thank You: 10K

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

Moderators: newbynobi, HansU
Time to create page: 1.004 seconds
Powered by Kunena Forum