Gscreen - a GTK / Glade / Python based screen

This has the tool turret in the back.
so looking at the end on the lathe looking at the chuck the tool turret is on the right side.

linuxcnc displays it on the left side looking as above or front if standing in the usual place.

There is some work arounds and work going on to fix this.

tjamscad wrote: Chris,

The first comments I recived for gscreen-indrustrial.

1. Why are the buttons on the bottom row? Can the bottom row be moved to the top and shift everything down.

2. When opening a program it shows the Ubuntu bars on the top and bottom. Can you make something that will stay inside gscreen? I am running gscreen as full screen because I dont want machinest/operators doing anything outside that.

3. The demo programs dont run gives error about exceding limits. Can you make the needed changes so it will run? I have a pc hooked to a touch screen no keyboard, no ouse.

1) it's surprising to me that that is important - but can be changed.
When I do this I will send you a separate GLADE file, I'm not sure I want to release it that way we will see.

2) I noticed that and I'm not sure, I will look into that.

3) you need to set the user coordinate system G54 in the Z axis down aways.
(I assume you are trying the penguin example) it rapids UP for clearance.
If you have not set the Z axis to something else it is zero at the top of it's travel ( so can not travel any higher )
This is common on most of the examples.

This was a discussion Norbert and I were have just so others may gice their opinion:

> Could you add a function to gscreen to launch also hal-scope?
> I believe this is the only hal-tool, you didn't include.
>

And I forget why I didn't - but will look again

> Within axis there is also a menu item to set the debug Level of linuxcnc,
> do you see a need to include this in the settings page?
>

I have never used this feature. So I'm not sure of the need. If it becomes desirable I can add it.

> Is it possible to redirect/copy all messages to std-out also to the
> alarm history?
> Otherwise we miss information, if the application is not started through
> a terminal.

I have _alot_ of temporary debugging prints, that will be removed when we are ready to release.
I can have all the messages wrapped in dbg() sent to the alarm history if the -d switch is on.
Is there some particular info you would like there - remembering this is really for the integrator to debug
machine/operator problems not for developing/bugs.

>
> And a setting to log the alarm history to a file would be great. I am
> thinking in an application for gscreen, just as workpiece handling
> system. This will run not only with good personal, but also with not
> well qualified personal. Many times people play around with settings or
> other thinks and then I get a reclamation, that the machine is not
> working any more. At the moment I am using a windows system, and I log
> every click, so I am able to check exactly what happened.
>
Logging - I assume you mean saving the history to a file - probably would be
a good thing to be able to turn on and off, maybe from the preference page?
How should if decide when to save? Just by time ? like every 4 hours save everything
and start a new fiile?
And what do you want logged? everything for instance I currently print messages
for most button presses (for development) do you want that level of logging?
One thing if users find bugs it would help me pin point the problem!

> Or should I comment all these thinks in the forum?
general questions like most of thee would be great on the forum so we get
the broadest / most experience opinions.

cmorley wrote: This was a discussion Norbert and I were have just so others may gice their opinion:

> Could you add a function to gscreen to launch also hal-scope?
> I believe this is the only hal-tool, you didn't include.
>

And I forget why I didn't - but will look again

> Within axis there is also a menu item to set the debug Level of linuxcnc,
> do you see a need to include this in the settings page?
>

I have never used this feature. So I'm not sure of the need. If it becomes desirable I can add it.

> Is it possible to redirect/copy all messages to std-out also to the
> alarm history?
> Otherwise we miss information, if the application is not started through
> a terminal.

I have _alot_ of temporary debugging prints, that will be removed when we are ready to release.
I can have all the messages wrapped in dbg() sent to the alarm history if the -d switch is on.
Is there some particular info you would like there - remembering this is really for the integrator to debug
machine/operator problems not for developing/bugs.

>
> And a setting to log the alarm history to a file would be great. I am
> thinking in an application for gscreen, just as workpiece handling
> system. This will run not only with good personal, but also with not
> well qualified personal. Many times people play around with settings or
> other thinks and then I get a reclamation, that the machine is not
> working any more. At the moment I am using a windows system, and I log
> every click, so I am able to check exactly what happened.
>
Logging - I assume you mean saving the history to a file - probably would be
a good thing to be able to turn on and off, maybe from the preference page?
How should if decide when to save? Just by time ? like every 4 hours save everything
and start a new fiile?
And what do you want logged? everything for instance I currently print messages
for most button presses (for development) do you want that level of logging?
One thing if users find bugs it would help me pin point the problem!

> Or should I comment all these thinks in the forum?
general questions like most of thee would be great on the forum so we get
the broadest / most experience opinions.

Halscope would be nice.

I like the extra logging options but the way it is now looks pretty good to me. so anything extra wiould be bonus.

cmorley wrote:

tjamscad wrote: Chris,

The first comments I recived for gscreen-indrustrial.

1. Why are the buttons on the bottom row? Can the bottom row be moved to the top and shift everything down.

2. When opening a program it shows the Ubuntu bars on the top and bottom. Can you make something that will stay inside gscreen? I am running gscreen as full screen because I dont want machinest/operators doing anything outside that.

3. The demo programs dont run gives error about exceding limits. Can you make the needed changes so it will run? I have a pc hooked to a touch screen no keyboard, no ouse.

1) it's surprising to me that that is important - but can be changed.
When I do this I will send you a separate GLADE file, I'm not sure I want to release it that way we will see.

2) I noticed that and I'm not sure, I will look into that.

3) you need to set the user coordinate system G54 in the Z axis down aways.
(I assume you are trying the penguin example) it rapids UP for clearance.
If you have not set the Z axis to something else it is zero at the top of it's travel ( so can not travel any higher )
This is common on most of the examples.

1. I thought it stange too. He said something about looking down being some sort of social thing. Another guy said that with the tabs at the top the button needed to be at the top so everything is in one place. Which make sense, all the CAD and programing applications have there tools at the top.

3. I cant seem to set the offset on the offset page. What am I doing wrong?

4. I noticed that there is a status section and a popup widget for alarms. The popup got to be quite difficult as it is distracting to use. Can you remove the popup since there is already a status section/

cmorley wrote:
3) you need to set the user coordinate system G54 in the Z axis down aways.
(I assume you are trying the penguin example) it rapids UP for clearance.
If you have not set the Z axis to something else it is zero at the top of it's travel ( so can not travel any higher )
This is common on most of the examples.

soapbox = on
This is the most frustrating thing about the examples they just don't run! Well the ngcgui examples run out of the box. I've always thought it is ridiculous to make a sample program that doesn't run. There you are green as a gourd and you can't make a sample program run... what do you do? I put instructions in the splash code but no one can see them so it just appears to be broken... what a great first impression we make.
soapbox = off

John