Gscreen -usability development

cncbasher wrote:

Chris could this not be done by checking for M30 or say % marker at the end of gcode

Possibly.
Might have to look into that.

good idea.

Chris M

You could probably do something with the "halui.program.is-running, bit out" it is a status pin telling that a program is running, to check when the program has ended for your elasped run timer.

I actually use that output bit to operate a 24VDC Green Led on the machine control panel, as a In cycle light, then myself or the shop supervisor can see from across the shop wether or not the machine is running.


Just a thought


Rick

Was going to try it out but latest buildbot doesn't work.

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.5
LINUXCNC - 2.6.0-pre0-4683-g0e76abf
Machine configuration directory is '/home/sven/linuxcnc/configs/sim/gscreen'
Machine configuration file is 'gscreen_mm.ini'
INIFILE=/home/sven/linuxcnc/configs/sim/gscreen/gscreen_mm.ini
PARAMETER_FILE=sim_mm.var
TASK=milltask
HALUI=halui
DISPLAY=gscreen
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
io started
halcmd loadusr io started
Starting HAL User Interface program: halui
Starting TASK program: milltask
task pid=29271
Starting DISPLAY program: gscreen
emcTaskInit: using builtin interpreter
Shutting down and cleaning up LinuxCNC...
Killing task linuxcncsvr, PID=29232
Killing task milltask, PID=29271
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Cleanup done

Debug file information:
Can not find -sec MOT -var MOT -num 1
Can not find -sec IO -var IO -num 1
Can not find -sec LINUXCNC -var NML_FILE -num 1
Can not find -sec EMC -var NML_FILE -num 1
Traceback (most recent call last):
File "/usr/bin/gscreen", line 37, in <module>
import gladevcp.makepins
File "/usr/lib/pymodules/python2.7/gladevcp/__init__.py", line 1, in <module>
from hal_pythonplugin import *
File "/usr/lib/pymodules/python2.7/gladevcp/hal_pythonplugin.py", line 29, in <module>
from hal_sourceview import *
File "/usr/lib/pymodules/python2.7/gladevcp/hal_sourceview.py", line 27, in <module>
import gtksourceview2 as gtksourceview
ImportError: No module named gtksourceview2
29232
PID TTY STAT TIME COMMAND
29271
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components

Crossposting from the mailing list.
Sebastian Kuzminsky sorted it all out and now gscreen runs in sim mode.
Unfortunately gmoccapy has no icons at all at the moment. There's a bug added for that.
sourceforge.net/p/emc/bugs/330/

@Sven,

it is a known isue, what happen only if you run from buildbot version.

Pease see:

wiki.linuxcnc.org/cgi-bin/wiki.pl?Gmoccapy

Item 2: I wrote:

At the moment there is a problem with the buildbot-version, as it does not include needed sub-folders from the config folder. It is also never as up to date at git master.

May be your report will solve that.

Norbert

Yes, the missing Gmoccapy config is related to the bug report, but the missing libraries were another thing (fixed by Seb). Hopefully it will run with the bot soon, I have test machines where a manual build isn't a working solution.

Hello Guys,

Its been a little while on this thread,

Good thing I've got some questions/ideas

We just yesterday fired up my latest retrofit, a Cincinnati Milacron 10VC-1000C VMC, we made a program up with some simple lines, arcs, interpolations, and are still trying to figure out the exact verbage on the post processor side of things to get it to load cleanly, but we did see a few things, that the operators was wondering about.

1. When we perform a T6M6 tool change, is the control supposed to automatically do a G43 H6, or do we need to do that on our own?

2. With the G43, is there any way to get that added to the info line at the top, where the current tool, and coordinate system are displayed, maybe have it look something like this, " Tool 6 H6 G54 " That way if you see the " H6 " you would know that the g43 is in effect, and for which tool it is set for.

I'm sure I will have some more questions/comments,

Thanks

Rick

Unfortunately it seems there is no way to find out what offset (s) are active at any one time.
only the actual value of the offsets are available.
while getting the info from remapping is possible, it will display whatever tool the interpreter is looking at, which can be different
then what is currently active because of read ahead.

So showing the currently active H code seems not possible at the moment.

With remapping, adding the g43 automatically is possible as well as wear offsets.

Chris M