Gscreen - a GTK / Glade / Python based screen

could you give the error.
could you post your HAL files. (or all config files)
Is this the default Gscreen or Industrial?

Thanks

Hi Chris,

I'm using the default Gscreen, here is a copy of what it says in my terminal when I try to start with gscreen, if you look in my Hal file I have all pins relating to gscreen #'ed out except for line 279, where the error occurs. If # that one out, gscreen starts, I can home my machine, and that's about it, because everything else goes thru my ladder. Also is my directory folder containing my configuration I'm trying to run.

cinci15cc@cinci15cc-desktop:~$ linuxcnc
LINUXCNC - 2.6.0~pre
Machine configuration directory is '/home/cinci15cc/linuxcnc/configs/15cc'
Machine configuration file is 'mygscreen.ini'
Starting LinuxCNC...
io started
halcmd loadusr io started
15ccgscreen.hal:279: Pin 'gscreen.change-tool' does not exist
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Cleanup done
LinuxCNC terminated with an error. You can find more information in the log:
/home/cinci15cc/linuxcnc_debug.txt
and
/home/cinci15cc/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal
cinci15cc@cinci15cc-desktop:~$

Thanks Again Chris,

Rick

this is the line at fault
15ccgscreen.hal:279: Pin 'gscreen.change-tool' does not exist

try moving the toolchanger parts to the end of the hal file or after hal is loaded as a post hal file etc

as the gui has not loaded at the time this line is reached then the change tool is not present
best to have your ladder etc loading last perhaps

Hallo Rick,

cncbasher is right,

all the gscreen pins will not be availibla before the GUI is loaded, so you must transfer the complete gscreen thinks to a postgui.hal file.
Do not forget to include the postgui.hal file in your INI, it must be named in the HALUI section.

Norbert

Hey Guys,

That did the trick, I moved everything related to gscreen to my post gui hal file and know we are flyin. Just started to get the operation figured out and it was quittin time. Hopefully tomorrow we can load some parts and make some things happen.

Thanks for the help,

Rick

glad you sorted it out ok

Everything is looking good so far, but I'm not sure how to perform a tool touch off, to start setting my tools. I brought my #1 tool up, faced the part and G92 z0.000 and turned a diameter of 1.422 so I G92 x1.422, indexed to tool 14 and touched off on the part, but now not sure how to get it into my tool table correctly?

Rick

Hallo Rick,
Even if this is off topic, I will try to answer:

why you use G92 for this?

Just turn your part to lets say 1,5 inch, set your axis to X 1.5
Now change the tool and touch off with the new tool, now we got i.e. X = 2,0
so there is a difference from 0.5 inch, that is the offset for tool 2 and that is the value you have to enter in the tool table.

Tool 1 is then your reference tool and has an offset from "0"

If you have set up all your tools, get back to tool 1.
And from now on you will have to get tool offset correction after each tool change with G43 and friends

Norbert

Hallo Chris,

Dave and myself found one thinks we would like to discuse to convince you to change.

If you are in a tool shop you won't use a mouse if possible. But if you try to enter the settings page you will be asked to enter the code.

Unfortunately it is not possible to enter the code with a keyboard, are you able and willing to change that?

And I found that the grid size from gremlin is set in inch , independent from the machine units, is this the same bug we discussed already related to the velocity label?

Norbert

yes you need to add a couple of things.
calc.set_editable(True)
calc.entry.connect("activate", lambda w : dialog.emit('response',gtk.RESPONSE_ACCEPT))

To the Gmocca's system_dialog function.
so the text entry can be typed in and so pressing enter also 'presses' ok button

I think I will do the same to Gscreen.

As for grid size - I do not know that was a fairly recent addition to the backplotter for foam cutter application. I would need to check the source code.

Chris M