Gscreen - a GTK / Glade / Python based screen

When in set override mode, changing jog speed using the + and - seems to work. Set at changes to 5.1 IPM Zero seems to work. Am I useing the "Set at" wrong?

I added all 9 possible axis to Gscreen simulator and the text height is different after x,y,z.

Also the readout information is not center on the selection box. Can that be changed?

newbynobi wrote:
Hallo Chris,

you are right, that Max_velocity is not shown in your screen, but it is on mine.
I thing max_Velocity should be on the screen, and I will try to explain why.

I write most of my programs offline, many times using CAD/CAM. So feed rates are set automatically and the rapid moves also.
So, ngc.file to the server and then get it with the real machine.

On the first run, I reduce the max_velocity to a quite slow velocity, so every quick move (G0) will be done with slower velocity than the max_velocity.
My machine runs at 10000 mm/min each axis, running at such speed, you will not be able to react, if you see a fixture collision or other errors.

On one off my machines max_velocity can be modified with an jog wheel, but I believe most users don't have this option.
I think this security feature should be integrated.

Second thing I noticed:
On my computer when using gscreen, I am not able to jog the machine using the keyboard buttons.
sometimes it is realy helpfull to use just the arrows to move arroud.
It would be nice to get the axis keyboard shortcuts also in gscreen.

Regards Norbert

Norbert

Norbert.
Velocity Override is exactly for what you are doing - to limit the maximum speed the machine will go.
The difference is VO is a percentage rather then an absolute value.
VO can be changed with a dial or on-screen buttons. How do you set your max_velocity?

Your right, I have not added keyboard shortcuts to Gscreen. I am not a big fan of keyboards for machine control.
That being said, I am not completely against it just has a low priority.
If I do it I would like it so a user can change them - which of course is more work for me and also require the development to slow down.

Chris M

tjamscad wrote:

cmorley wrote: tjamscad

re F0 S0 and V0

I was thinking you were talking of the overrides in the status window.
Maybe you were speaking of the Gcodes active window?

You are correct, Feed and Spindle override normal but the "VO" is for velocity override correct? Wich in turn makes it Rapid Feed Override?

Sort of - VO limits the maximum speed of ALL moves. So if you turn down VO below a feedmove speed it limits feed moves too.
I am not sure this is how industrial machines work, but there is little I can do about it - that's how linuxcnc does it.
My only reference was the Okuma lathe I ran - it turned both feeds and rapids down at the same, so at 50% the feed was at 50% and the rapid was at 50%.

Anyways that's why I chose VO rather then RFO or RO - I could change it to RO if you think that's fine.

Chris M

tjamscad wrote:
1. Please add machine off
1a. homed would be nice also.
4. Yes, save and save as I woul like to show when in edit mode. Pressing Edit to Exit doesn't make sense. Can Edit change to Exit when in edit mode and provide a popup for save or save as?
If a machinest needs to write a program from scratch it is usually 5-15 lines long and seems to never be the same.

1) K I did and 'Estop reset' I'll look at 'all homed' anything else? I would think you would like it as sparse as practical - can be quite a list in a day.
Do you guys leave the machines on over night usually?

4) If fact I will have edit mode have it's own set of lower buttons. There are some editing options that can be added fairly easily I think, like undo/redo.
so I need button real estate anyways. I could put the save and saveas there too.
Is the pop up really required? Pop ups can be annoying if you do a lot of editing. hmm maybe it is required,,, right now it is fairly easy to edit something and not save it, so then the screen and liuxcnc are out of sync....
Yes I can have the edit button change text.

Oh and I think I have Gscreen changing joint 0 to Axis X reliably - I already pushed the change. We will see if it catches them all.

Chris M

tjamscad wrote: When in set override mode, changing jog speed using the + and - seems to work. Set at changes to 5.1 IPM Zero seems to work. Am I useing the "Set at" wrong?

well if the upper right entry widget said 5.1 (or more likely 5.125 I limited the jog rate to 1 decimal) then it worked right.
But it would probably be better to have a pop up number entry. - I may in fact be able to get rid of that entry widget if I did that for all entry points.