- Posts: 186
- Thank you received: 0
Gscreen - a GTK / Glade / Python based screen
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
Please Log in to join the conversation.
It was not picky - it was hard to read
Chris M
Please Log in to join the conversation.
The way it looks, I will be starting our third retrofit in about 2 weeks, and it usually takes about 9-10 weeks to rewire and program these big lathes. So in about 3 months we will have 3 big turning centers all on Linux using the Gscreen interface.
Then we are going to our first mill to convert over.
Thanks
Rick
Please Log in to join the conversation.
using "Industrial GScreen"
In advance thank you very much,
Jorge Viloria
Please Log in to join the conversation.
at about line 290 change to this:
Please Log in to join the conversation.
searching a bug in gmoccapy I realized that the bug is not in my code.
Please do the following in industrial:
- turn on machine and reference all axis
- switch on the spindle, witch will run with the rpm set in preferences, in my case 450 rpm
- change do MDI mode and enter S2500
The spindle stops instead of speeding up to the S value.
IMHO it is a bug, spindle works well after you give an M3 command in MDI.
Norbert
Please Log in to join the conversation.
This is Linuxcnc setting the outputs according to the active G/M codes when setting the S speed.
Since M3 or 4 is not set, it stops the spindle.
Some might say the spindle should stop when you switch from manual to MDI.
If you feel strongly about it file a bug report or discuss it on the dev mail list.
Chris M
Please Log in to join the conversation.
I'm testing GScreen-industrial successfully on my lathe.
I have some doubts.
1) When starting I get the measurement in inches, but what I have in mm, in the "DRO" of gremlin out in mm, touch him twice click the button mm / inch units.
2) Do not I have all this physical buttons on my screen. is very hard for me to jog change going forward one by one. any help at this point would be very helped, I've thought about hal_scale in vcp_box, but I could not connect to LinuxCNC.
Attachment not found
thanks in advance.
Jorge Viloria.
Please Log in to join the conversation.
jlviloria wrote: Chris,
I'm testing GScreen-industrial successfully on my lathe.
I have some doubts.
1) When starting I get the measurement in inches, but what I have in mm, in the "DRO" of gremlin out in mm, touch him twice click the button mm / inch units.
2) Do not I have all this physical buttons on my screen. is very hard for me to jog change going forward one by one. any help at this point would be very helped, I've thought about hal_scale in vcp_box, but I could not connect to LinuxCNC.
thanks in advance.
Jorge Viloria.
Glad you got it working.
If you wish to start in mm all the time, select the 'metric' button in the system / preference page.
adding a jog rate slider using HAL connections is probably not going to work satisfactory.
Doing it by using a custom handler file would integrate better.
a Jog slider is not going to be nice if you use a touch screen I think.
I am still working out of town so can not offer code examples yet.
Chris M
Please Log in to join the conversation.
you can check the code of gmoccapy for the slider acting as jog velocity.
Norbert
Please Log in to join the conversation.
