Gscreen - a GTK / Glade / Python based screen

Chris, you might take a look at the Gremlin example I finally got working with the help of Rogge that doesn't use the gladevcp widget to implement gremlin. It seems like a better solution to me at this point as you can handle the file load error as you like without a python error showing up.

John

cmorley wrote: 1) you can almost do this now by using halui override controls. The missing part is the on-screen enable controls.
I could create pins that are true only when one of the override buttons is selected and while not in jogging mode - is that sufficient?
2) it is possible to zoom in anyway you want with a little coding. Is the track ball used like a mouse? so track ball movement is the same as mouse movement?
3) Yes ideally the tool editor display will be more configurable. I hadn't decided how that should work at the time I built it.
4) tool changing requires the machine to be homed that is why I left it off the first screen. I know on my lathe we indexed tools manual fairly often.
I could add it, de-sensitized till homing is done. Could you llive with index next tool or would you need index to a particular tool?
As for tooleditor as a setup tab- I'm not sure what you mean exactly - are you saying you want to be able to set the origin while the tooleditor displays?
5) If tabs are easier to use yes an offset tab could be built.
6) Jogging is available without homing. Homing mode is set automatically when Gscreen is started as that is pretty standard. de-press the homing button on the right side and press the jogging button on the bottom left. If this is an option lots of people want I could add it as a preference.

Hi Chris,

1. I'll try it.
2. The track ball movement works just like a mouse. The advantage is it doesn't need a flat surface to work on.
4. I didn't think of the problem of doing tool changes prior to homing. That obviously can't work.
We often index tools out of order. This is not a production shop, and we leave some "standard" tools in the changer. A particular job might use some of those tools plus ones added in higher tool numbers just for that job.
What I was thinking about for a setup tab is to edit the tool table, set origins, and touch off tools. The setup process for us is like this: home the machine, load an edge finder tool, set X and Y origins, load a reference tool, set Z origin, then load and touch off each tool for the job, It is reassuring to see the Z offset in the tool table change after touching off a tool.
5. ok. I'll think about this.
6. I got it. Thanks.

Thanks a lot, Chris.

Karl

Well while that would fix the error code being thrown that would create a lot of work for me and then restrict users from customising Gscreen's graphics plot, which is one of Gscreen's objectives.
Also fixing the HAL_gremlin error seems a better thing for a developer to do then just stop using the widget.

I can suppress the error messages easily by overriding the method that prints them to standard error and changing it to a print statement.
This shows me that the error message is being written twice, which seems to indicate the loading of the program is being done twice.
Not sure why that causes an error rather then just printing twice though...
I'm sure someone who knew how to use a debugger could figure out why it's being called twice - I just don't know how to use a debugger.
I did a few print statement debugging and haven't found it yet - I wouldn't be surprised if it's a glade signal being called twice.

Chris M

Karl

trackball movement and having the offset and origin offset button in the tool table page are good candidates for custom screens.
These are things that I don't think I want to do to the default screen.

I will see about building a sample of those customizations if you like.
Are you using the default screen now or a custom one?
Are you using a touch screen as well as a track ball?

The tool change and offsets page sound like good default features so will look into them.

Chris M

Chris,

I'm using the default screen. I'll have a stab at doing a custom screen. I want to learn about that anyway.
We're using both the touch screen and track ball. The track ball isn't used much, mostly just the touch screen.

I couldn't get the override enables to work on my simulator. I enabled the machine, homed it, pressed Set Override, and pressed Feed Override. gscreen.f-override-enable-out is still False. Is there something else I need to do?

Karl

As long as your not in jog mode it should work. i just checked it again...