Gscreen - a GTK / Glade / Python based screen

Thanks for the report and the error pinpointing.
I pushed the fix.

Chris M

ok you can add 'continuous' to the DISPLAY INCREMENTS section in any order.

hopefully the DRO in industrial is a little more stable.

The restart dialog has a numerical entry and pops up with the last line number run. you can type directly into the dialog and move it.

industrial has home indicators and DTG. The indicators only pop up when all the axis are homed, that should be changed.

Chris M

I was trying to get Gscreen running just for simulation while I am preparing my lathe and I could not.

I have installed from the buildbot the sim version:

LINUXCNC - 2.6.0-pre0-3890-g5075862

I can run others simulations including axis, so I think I did not mess anything. Not sure if I am helping in reporting this, but here it goes.
All tests with all the possible configurations of gscreen returned an error:

LINUXCNC - 2.6.0-pre0-3890-g5075862
Machine configuration directory is '/home/me/linuxcnc/configs/sim/gscreen'
Machine configuration file is 'gscreen_lathe.ini'
Starting LinuxCNC...
redis server started as: 'redis-server ', logging to: /dev/null
io started
halcmd loadusr io started
Could not open command file 'core_sim.hal'
Shutting down and cleaning up LinuxCNC...
Cleanup done

and the debug file contains:

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
Can not find -sec REDIS -var DISABLE_SERVER -num 1
Can not find -sec REDIS -var SERVER_PATH -num 1
Can not find -sec REDIS -var SERVER_ARGS -num 1
Can not find -sec REDIS -var SERVER_LOG -num 1
16279
PID TTY STAT TIME COMMAND
16278
PID TTY STAT TIME COMMAND
16278 pts/0 Dl+ 0:00 redis-server
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components

sim/axis9 works?

can you look in configs/sim folder and see if
core_sim.hal
is there?

If it isn't then sim/axis shouldn't work either.

Chris M

I think this is a problem with the system links.
I only have worked with Gcsreen as a Run-in-place build.

by using buildbot it's an installed build which moves a few things around.

There are system-links (shortcuts) that are pointing to the wrong place.

Where ever sim/axis/core_sim.hal is pointing to
sim/gscreen/core_sim.hal must point to

There are probably a couple others too. hal_manual_toolchange.hal etc

Chris M

Or maybe the system links are missing when copied into your linuxcnc folder...

cmorley wrote:

ok you can add 'continuous' to the DISPLAY INCREMENTS section in any order.
Chris M

Chris,

Thanks for adding this.

As an exercise I tried putting in code to set the initial jog increment. I modified industrial_handler.py and in the __init__ function for HandlerClass I inserted the following:
self.gscreen.set_jog_increments(vector=1)
When run it gave this error:
File "/home/milluser/linuxcnc-dev/bin/gscreen", line 1886, in set_jog_increments
self.halcomp["jog-increment.out"] = distance
AttributeError: Pin 'jog-increment.out' does not exist

I assume jog-increment has not been set up at the point HandlerClass is being initialized. Is there a different place I could make a call to set_jog_increments, after everything is initialized, to set the initial jog increment?

Thanks.
Karl

That would need to go in the init_widgets section.

In Gscreen proper the order is:
parse handler file and call it's __init__
make basic Hal component
initialize_pins
connect_signals
initialize_widgets

any one or all of the last three can be in the handler_file and the order is the same.
try adding it to the initialize_widgets section
you'll see a couple of others there as well as a lot of calls to gscreen's individual initializing functions.

Chris M

cmorley wrote:

I think this is a problem with the system links.
I only have worked with Gcsreen as a Run-in-place build.

by using buildbot it's an installed build which moves a few things around.

There are system-links (shortcuts) that are pointing to the wrong place.

Where ever sim/axis/core_sim.hal is pointing to
sim/gscreen/core_sim.hal must point to

There are probably a couple others too. hal_manual_toolchange.hal etc

Chris M

Or maybe the system links are missing when copied into your linuxcnc folder...

I had to copy files from the axis sim directory and create empty files, named xxxx_postgui.hal, and it is working.

Chris,

gscreen-industrial has some new issues since the last push