Gscreen - a GTK / Glade / Python based screen

I wonder if this is because you are trying to use data.estopped before the periodic is turned on?

you could check the task state directly through

self.gscreen.emc_status.emcstat.poll()
estop = self.gscreen.emc_status.task_state == self.gscreen.emc_status..emc.STATE_ESTOP

Hope I got that code right...
There may be other ways - I just don't have time to check sorry.

Hallo Chris,

I found ot that it must be:

to get the correct value.

But I am asking myself, when will periodic begin to run?
I checked the state of self.data.estopped now on_window1.realize() and do get the wrong value. If I get it directly with the code you gave me, I get the correct value.

Should this be corrected in the feature? By running the first periodic from gscreen bevor starting the gui?

Norbert

Norbert

newbynobi wrote:

I wonder if this is because you are trying to use data.estopped before the periodic is turned on?

you could check the task state directly through

self.gscreen.emc_status.emcstat.poll()
estop = self.gscreen.emc_status.task_state == self.gscreen.emc_status..emc.STATE_ESTOP

Hope I got that code right...
There may be other ways - I just don't have time to check sorry.

Hallo Chris,

I found ot that it must be:

Code:

self.gscreen.status.emcstat.poll() estop = self.gscreen.status.emcstat.task_state == self.gscreen.status.emc.STATE_ESTOP

to get the correct value.

But I am asking myself, when will periodic begin to run?
I checked the state of self.data.estopped now on_window1.realize() and do get the wrong value. If I get it directly with the code you gave me, I get the correct value.

Should this be corrected in the feature? By running the first periodic from gscreen bevor starting the gui?

Norbert

Norbert

The periodic is run after all the initialization is done.
It's the very last thing done before Gscreen just listens for signals.
It has to be or else the screen is updated before you initialize how you want it displayed.

It may be possible to call the method that updates the linuxcnc stuff into our self.data model once, earlier on in the process.
try adding
self.status.periodic()
just after line 444:
self.emc = emc_interface.emc_control(linuxcnc)

let me know if that fixes things for you.

I am working away for 3 weeks so updates and replays will be sporadic....

Hello Chris,

Which file in gscreen dictates the color of your gcode in auto mode, and the highlight color of the current line being run?

My shop supervisor asked if I could change those colors, he has a hard time reading the lines being that it is bright red and dark red while during a running program.

Hopefully next week I can try to do some personalizing regarding the pointers you have given me.

Thanks

Rick

I lightened the color of the highlight, it is not currently user configurable.

changing Gcode colors is a more involved:

superuser.com/questions/353391/custom-ge...lighting-for-dummies

Thanks Chris,

I hope I am not being too picky, Gscreen is one hell of a build, the guys are just used to the old ways, and are hard to adapt to change. SRT , our shop manager and myself all embrace change and really like the way things are going using the linux systems,( especially now with Gscreen) I am just trying to make the transition as easy as possible.

I knows its going to take time, but hopefully in the near future I will be able handle all of these thoughts by myself instead of bothering you guys.

Thanks Again

Rick

I hoped that Gscreen could help bridge the gaps between the old ways and the new.
It was not picky - it was hard to read

Chris M