Gscreen - a GTK / Glade / Python based screen

pushed some new stuff:
-at speed indicator displays the commanded spindle speed
-Gscreen now honours the default jog speed in the INI file
- all the sample screens except gaxis have an alarm page now
- The alarm page records when the control was launched and whe the machine is estopped and machine turned on
- You can set the display cycle time in the INI file. A slower computer may work better with a larger cycle time. default is 100 milliseconds

Chris M

heck slow down Chris , before you burn out ... haha
looking good , great additions

cmorley wrote: pushed some new stuff:
-at speed indicator displays the commanded spindle speed
-Gscreen now honours the default jog speed in the INI file
- all the sample screens except gaxis have an alarm page now
- The alarm page records when the control was launched and whe the machine is estopped and machine turned on
- You can set the display cycle time in the INI file. A slower computer may work better with a larger cycle time. default is 100 milliseconds

Chris M

Chris,

This is really looking good!!! Some more comments from working on the mill:
1. When gscreen starts the jog speed now comes from the INI file, but when I select jog override and +/- buttons it jumps back to 60. I probably have some other setting in the INI file. Any idea what it is?
2. After cycling modes through manual->mdi->auto->manual, then select jogging mode and select an axis. The machine is still in MDI mode, so the joysticks and jogwheel don't work. Pressing the +/- buttons sets manual mode. It would be nice it it could put the machine in manual mode without having to press the +/- buttons.
3. When running a program, the Snnn in the active G codes doesn't change with programmed spindle speeds.
4. Is there somewhere that current machine velocity is shown when running a program?
5. When setting overrides with the +/- buttons, is is possible to detect the button held down, and continuously increment/decrement the value. What would be best is to still increment/decrement by the amount it currently does when the button is just tapped, but after it's held for more than 0.5s (or whatever) it increments/decrements continuously.
6. Connecting the cycle-start button works great in MDI mode. Thanks.
7. Could the actual spindle speed displayed as text in the bar graph be limited to 1 or 0 digits?

It's all really coming together nicely. Thank you!

Karl

cmorley wrote: In reference to a cycle start button:

I have to decide on behaviour for run-at-line.

Do we select the line with run-at-line dialog then use cycle start or
Do we select the line with run-at-line dialog and start the cycle from that dialog button?

We don't use run-at-line much. Mostly too scared that something won't be right.

But I'd favor your first option.

Karl

karlkec wrote: Chris,

This is really looking good!!! Some more comments from working on the mill:
1. When gscreen starts the jog speed now comes from the INI file, but when I select jog override and +/- buttons it jumps back to 60. I probably have some other setting in the INI file. Any idea what it is?
2. After cycling modes through manual->mdi->auto->manual, then select jogging mode and select an axis. The machine is still in MDI mode, so the joysticks and jogwheel don't work. Pressing the +/- buttons sets manual mode. It would be nice it it could put the machine in manual mode without having to press the +/- buttons.
3. When running a program, the Snnn in the active G codes doesn't change with programmed spindle speeds.
4. Is there somewhere that current machine velocity is shown when running a program?
5. When setting overrides with the +/- buttons, is is possible to detect the button held down, and continuously increment/decrement the value. What would be best is to still increment/decrement by the amount it currently does when the button is just tapped, but after it's held for more than 0.5s (or whatever) it increments/decrements continuously.
6. Connecting the cycle-start button works great in MDI mode. Thanks.
7. Could the actual spindle speed displayed as text in the bar graph be limited to 1 or 0 digits?

It's all really coming together nicely. Thank you!

Karl

Karl are you using the metric sample config?

1) i see in the metric example similar behaviour I don't see 60 but 15 as the velocity but the jog rate say 381mm
This is a conversion error that doesn't happen in imperial configs (so I missed it) I will see whats going on
2) You must be talking of external joystick and jogwheel. Gscreen has a jogging button that must be toggled on.
This is automatically toggled off when you change to MDI or AUTO mode. This button also changes linuxcnc to manual mode.
There is a jogging-enabled HAL pin that follows it.
I did this so if running a program or a MDI move you could go to manual or MDI page without causing an error.
Maybe this is unnecessary. And I could have linuxcnc's mode changed as you change Gscreens mode....
3) hmm I see the Snn change in auto or MDI mode. It always says 0?
4) double click the graphics screen makes it bigger and the readout show (with velocity)
I will add velocity to the status box though.
5) I will see if i can figure that out.
6)Ah good thanks for testing.
7) Yes I fixed that on the industrial screen - forgot to do the rest.

the feedback from every one really helps to flush out the bugs and needed improvements

I am gonna mention that fairly soon there is going to be HAL pin name changes and a INI name lookup change that will require
users to modify HAL and INI files a bit. So if you see these errors you know why.
The naming convention of the HAL pins varies some use . where - should be.

Chris M

karlkec wrote:

cmorley wrote: In reference to a cycle start button:

I have to decide on behaviour for run-at-line.

Do we select the line with run-at-line dialog then use cycle start or
Do we select the line with run-at-line dialog and start the cycle from that dialog button?

We don't use run-at-line much. Mostly too scared that something won't be right.

But I'd favor your first option.

Karl

Setting spindle on in manual or MDI then restarting at a rapid point would seem the safest.
i should talk to Mocca's Tom about exactly how he did run at line...

To use cycle start would require the user to press it with the run-at-line dialog showing.
I wonder it that is enough of an indicator. cycle start without dialog starts from beginning, cycle start from dialog starts at the requested line.

Chris M