Gscreen - a GTK / Glade / Python based screen

tjamscad wrote: Chris,

Ignore limits should be hidden until a limit switch is made.

When starting gscreen G54 or the last correndante system is automatically set active. The machinists i am working with feels this is not correct. The coordinate system should only be activated by an MDI or program command.

Can you add a machine position to the display?

Tool set should not use the correnate system (G54-G59) it should be using the machine position.

I probably could hide the ignore limits button and it only needs to be on the setup page.
You cannot pick the machine coordinate system. It is mostly hidden from the user. There is always one user system active.
If you leave the offsets at zero for a user system then this would be equivalent to the machine coordinate system.

'Absolute' position IS the machine coordinates

Tool set uses G10 L10 ,other option is to do G10 L11

G10 L10 from the manual:
"G10 L10 changes the tool table entry for tool P so that if the tool offset is reloaded, with the machine in its current position and with the current G5x and G92 offsets active, the current coordinates for the given axes will become the given values. The axes that are not specified in the G10 L10 command will not be changed."

G10 L11:
"G10 L11 is just like G10 L10 except that instead of setting the entry according to the current offsets, it is set so that the current coordinates would become the given value if the new tool offset is reloaded and the machine is placed in the G59.3 coordinate system without any G92 offset active.

This allows the user to set the G59.3 coordinate system according to a fixed point on the machine, and then use that fixture to measure tools without regard to other currently-active offsets."

Since you can't use machine coordinates, G10 L10 is probably what you want.
If not you'll have to explain in more detail. I am not up to speed on tool set procedures.

Chris M

Hey Chris,

I no more than pressed submit this morning on that post and both operators came to me within 20 minutes of each other, and both machines were telling me that " Requested tool XX not found in tool table". They had done nothing at all except performed an MDI tool call and it tells them that. I shut linux down, restarted, homed the machine and did a tool call and it still gave me that fault. The only way that I found to resolve this is to delete and re-add each tool back into the tool table. I even went to the actual tool.tbl file, copied the contents, made another file with a different name, changed my INI file to reflect it and it still faulted.

Any thoughts?

What would be of help on my end to try to diagnose this?

Rick

Can you send me the original screwed up tooltable file?

Chris M

Chris,

This is a quick tool seting link from a fanuc control. The button might not be the same but the princple is for almost macines.

www.wisc-online.com/objects/ViewObject.aspx?ID=MTL17302

cmorley wrote: Can you send me the original screwed up tooltable file?

I think this is probably nothing to do with Gscreen. I think I have heard of this before, it is something to do with a blank line either present where it shouldn't be or absent where it should be in the tool table file.

(I really need to get back to the task of replacing this bug with newer ones)

andypugh wrote:

cmorley wrote: Can you send me the original screwed up tooltable file?

I think this is probably nothing to do with Gscreen. I think I have heard of this before, it is something to do with a blank line either present where it shouldn't be or absent where it should be in the tool table file.

(I really need to get back to the task of replacing this bug with newer ones)

Are you possibly refering to the semicolon on the first line? I see this mentioned in the Tool Table Wiki. What is the purpose of this and if it was missing would this possibly give me this fault?

Rick