Gscreen - a GTK / Glade / Python based screen

Hallo Chris,

I just took a look to your "Offset Page" Because I was thinking about that too.
I wonder, why you list the coordinate systems in rows and the coordinates in lines,
while in the tool editor tab it is viceversa.

I suggest to get an uniform layout for both.

And there is another think I cant understand, please make the following:

- Emergency off
- Machine on
- home all axis
- jog all axis around and then Zero Origin for all axis
- change to auto mode
- load examples spiral.ngc
- go back to manual mode
- jog to an other position, lets say go down 20 mm or 1 inch with Z
- Say cero origin
- go back to auto mode
- run the program

and then wonder where gremlin paints the tool path.

Regards Norbert

John,

Are you saying that gscreen could create a file when entering multiple lines of g-code or that you could create a seprate file and then run it?

Hallo Chris,

it's again me.
I just changed some thinks in moccapy and started it to check my changes.
It seems you have changed something within gscreen, because now the aux screen opends by himself.
I didn't change anything within my ini file, but the screen with the spindle indicator and the small gremlin opens.

I am speeking over gscreen2.glade window.

This is strange for me.

#########################################

I just managed this, I had to open gscreen and in preferences disable the aux screen, thats it.
So the preferences are taken in care even if I start from a different config folder.

This can confuse operators!


Regards Norbert

tjamscad wrote:

Chris,

1. The at speed indicator is still green before it is set, please make it black unless it is at speed.

2. In program mode the EDIT doesn't toggle to EXIT when edit is selected.

3. MDI can't have multiple lines of commands because of LinuxCNC right?

1) it IS at speed - the speed requested speed is zero so when the spindle is zero the LED goes green.
I'll have to figure out how to combine that with something else to make it black when turned off.

2) oh yes sorry forgot.

3) As far as I know.

Chris M

newbynobi wrote:

Hallo Chris,

I just managed this, I had to open gscreen and in preferences disable the aux screen, thats it.
So the preferences are taken in care even if I start from a different config folder.

This can confuse operators!


Regards Norbert

Yes the preference file is written to your home folder.
It is used by any/all Gscreen programs.

It could be possible to specify a preference filename in the INI.
so then you could have multiple screens on one computer.
I just wonder how often this is really necessary...?

cmorley wrote:

tjamscad wrote:

Chris,

1. The at speed indicator is still green before it is set, please make it black unless it is at speed.

1) it IS at speed - the speed requested speed is zero so when the spindle is zero the LED goes green.
I'll have to figure out how to combine that with something else to make it black when turned off.

Yes that makes sense, I just didnt think of "0" as speed.

newbynobi wrote:

Hallo Chris,

I just took a look to your "Offset Page" Because I was thinking about that too.
I wonder, why you list the coordinate systems in rows and the coordinates in lines,
while in the tool editor tab it is viceversa.

I suggest to get an uniform layout for both.

Ahh yes, You are surely right, I think maybe AXES should go left to right on both screens ??

And there is another think I cant understand, please make the following:

- Emergency off
- Machine on
- home all axis
- jog all axis around and then Zero Origin for all axis
- change to auto mode
- load examples spiral.ngc
- go back to manual mode
- jog to an other position, lets say go down 20 mm or 1 inch with Z
- Say cero origin
- go back to auto mode
- run the program

and then wonder where gremlin paints the tool path.

Regards Norbert

Yep that's a regression I missed. I need to tell gremlin to reload the plot after a coordinate offsets change.
I did this by using a button that was connected to hal_action_reload.
later I moved the button and remoced the connect to hal_action_reload.
I'll fix it by calling the action directly..

Thanks for pointing them out !

Chris M

Chris,

What file is the main file? I mean what calls all your extra files to come play? How is gscreen structured?

I also noticed that on the spindle section the "FWD" is shown as selected but I didnt select anything. It was just after turning it on.

The spindle direction buttons 'toogle' either fwd or reverse, so one will always be selected.
In this way when you push start, you will know what way it will turn.



gscreen.py is the Main file.
It has 'helper' files:
mdi.py
preference.py
emc_interface.py
and the stock screen file, gscreen,glade

These are found in /src/emc/usr_intf/gscreen in a compiled run-in-place linuxcnc.

Then there can be 'local' (local as in the users config with the HAL files) custom screen files.
These can be somename_hander,py and/or somename.glade

For instance the industrial screen is defined in these 'local' files. They must be put in every cofig folder that you want industrial in.
This is different from all other linuxcnc screens. There you just change the DISPLAY= name in the INI file and the new screen shows up.
This works with Gscreen too but you will always get the stock screen that way.

Chris M