Gscreen - a GTK / Glade / Python based screen

More
13 years 9 months ago #28479 by BigJohnT
Replied by BigJohnT on topic Gscreen - a GTK / Glade / Python based screen

cmorley wrote: I recently noticed that linuxcnc has two reference types of 'touch-off' (origin offset in Gscreen speak):
touchoff to fixture or touch off to workpiece
Can't say what the difference really is but I assume i need a button to select - where should that button be and where should the indicator be?


If you have say a turret or other means to preset tools you can touch off each one to a fixture then you use one tool to touch off to the work piece and that sets the Z for all the tools in your tool table. Before you had to change to an unused coordinate system to touch off tools to the fixture or you got a nasty surprise... oh wait here is a tutorial.

John

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

More
13 years 9 months ago #28486 by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
Thanks John.

So to summarise touch off :
to fixture - offsets just the current tool
to workpiece - offsets all the tools

so really:
to fixture - is tool setting
and to workpiece - is origin setting

Is this accurate?

Chris M

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

More
13 years 9 months ago #28496 by tjamscad
Replied by tjamscad on topic Gscreen - a GTK / Glade / Python based screen

cmorley wrote: tjamscad

Hiding the debug tab can by done many ways. eg
1) require you to change some text in the files to show it - down side is you would need to close and restart the screen. so slow to change
2) use an HAL input pin to control it via a physical switch - down side is it uses up an IO pin, upside can be done anytime and quickly
2) use a special key combination while clicking a button or tab - trouble is this is completely un-discoverable and unintuitive so I can't really publish this as a sample config though could show you how to add it to your personal screen.
3) find some place for a button that brings up a password dialog any idea where and what to call it?

The alarm history could get very long - do the controls get turned off regularly ? oh wait do you want it saved when turned off?
I suppose we could limit it to say the last 50 entries. A time stamp would be useful too.

Are you saying the buttons on the tabs are not sufficient if made a little larger?
There is a technical reason why I don't just add the tabs - though I may have thought of a work around....

estop - sorry I thought I turned them black but I see I turned them dark - not quite the same...

Left bar - yes I did some work on that and didn't figure out what was causing it - will work on it some more.

I recently noticed that linuxcnc has two reference types of 'touch-off' (origin offset in Gscreen speak):
touchoff to fixture or touch off to workpiece
Can't say what the difference really is but I assume i need a button to select - where should that button be and where should the indicator be?

I will be very proud if the machinists prefer this screen - thank you and everyone else for the critiques.
Chris M


Alarm history, yes this can be very long sometimes. From a maientance point it is so nice when an operator is complaining about an issue and can go to the alarm history and see what has been going on. Most machines reset the history at machine power down, and some can save the history out to a text file.

Is it possible when selecting the debug tab that it bring up a password dialog box. That would be just the thing.

The SET-up, MDI, and Run are all in a single tabthat contains all three tabs. Can they be seperated to all three single tabs?

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

More
13 years 9 months ago #28497 by BigJohnT
Replied by BigJohnT on topic Gscreen - a GTK / Glade / Python based screen

cmorley wrote: Thanks John.

So to summarise touch off :
to fixture - offsets just the current tool
to workpiece - offsets all the tools

so really:
to fixture - is tool setting
and to workpiece - is origin setting

Is this accurate?

Chris M


I'd say that it pretty accurate. I have button that runs a mdi command for touch off to material as I always use the same method. It takes 2 buttons for me to touch off to fixture as it seems the G43 must be done after the G10 to load the tool.

John

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

More
13 years 9 months ago #28507 by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen
My attempt to add separate tabs has failed, so for now seems buttons is what you get.

Where would you like the show-debug-tab button and what to call it?

I'll try building an alarm history page.

An offsets page was talked about too...

Always more to do :)

Chris M

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

More
13 years 9 months ago - 13 years 9 months ago #28519 by tjamscad
Replied by tjamscad on topic Gscreen - a GTK / Glade / Python based screen

cmorley wrote: My attempt to add separate tabs has failed, so for now seems buttons is what you get.

Where would you like the show-debug-tab button and what to call it?

I'll try building an alarm history page.

An offsets page was talked about too...

Always more to do :)

Chris M


Debug can be where it is and could be called "SYSTEM" and then the Maintence tab could be renamed back to debug.
Alarm history page, great :)
I think an offsets page embeded just like your tool editor page would be great also.
Last edit: 13 years 9 months ago by tjamscad.

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

Time to create page: 0.295 seconds
Powered by Kunena Forum