Gscreen - a GTK / Glade / Python based screen

Well I'll defer to consensus about whether it should be allowed.

but if it popped a dialog (with 'override' title) it probably would have been more obvious yes?

Chris M

Hi Chris,

I have been quietly using Gscreen and so far the suggestions that you have incorporated have been great. I am especial thankful for the Velocity readout you have currently added.
The only thing I'm missing for my setup is a Jogspeed display but I will look at adding this once development slows a little, that is unless someone else adds it first ...

Thanks,

Jayson.

Jayson

Thanks for letting use know things are well while using Gscreen.

Jog speed display do you mean current jog rate or current velocity while jogging or something else.

Cause both of those are there.

Chris M

Well that's good to hear, I just need to look more closely
I have one of my dials linked to halui.jog-speed to set the speed the axis will move at when I hold down one of the physical jog buttons.
I think this will be useful on my machine to use it in manual mode for facing operations and such.

Thanks,

Jayson.

ahh that's what is going on. Gscreen can't get the jog rate from HALUI.
So Gscreen just report the jog rate that was set in the INI file or some default in Gscreen.

Funny i was just trying to remember this problem when talking to Chris Radek today...

cmorley wrote: Well I'll defer to consensus about whether it should be allowed.

but if it popped a dialog (with 'override' title) it probably would have been more obvious yes?

Yes that would have been fine.

A couple more questions about jog increments.
1. When set to continuous, gscreen.jog-increment.out is zero. This essentially disables the panel-mount jogwheel, because it uses the increment from gscreen. In our setup the MPG uses its own set of increments so it still works. How about if gscreen.jog-increment.out used the largest jog increment if continuous is set. I wonder if others would use a similar setup, and have any comments about this.
2. When touching off the work or a tool, we normally start with the largest jog increment and then go to lower increments as we get closer, winding up with a 0.0001" increment. It's a bit cumbersome to go into Set Override mode to change the increment and back out to change the axis.

Any thoughts?

Thanks.
Karl