Gmoccapy - A new screen for linuxcnc

Chris,
Will we have a way to do NGCGUI type stuff with Gscreen or gmoccapy? Thinks like wizards or code to do repetitive tasks like circular bolt patterns and the like. You know, all the nice things for a mill or lathe.

I have no plans to build such things.
I will try to incorporate anything that someone comes up with.
I too think it's an important feature - just beyond my skills or time.

Chris M

It does not have to be integrated. Maybe we could have a way to call another program that will generate the gcode directly into the gmoccapy window or even just so that the file could be loaded.
The reason that I am asking about this kind of feature is that I will be using gscreen and gmoccapy with a touch screen controller that has no keyboard at all. That's why maybe a way to call another program could also work. There are a lot of pythons scripts on the wiki already that does this kind of thing.

generators such as these:
wiki.linuxcnc.org/cgi-bin/wiki.pl?Simple...NC_G-Code_Generators
will work with Gscreen/Gmoccapy.

Just open the scripts as if you were loading a Gcode program.

Maybe NGCGUI can be run standalone and then load the program from Gmoccapy.
Incorporated would be much nicer.

Chris M

Chris
I just tested some of those generators and they work just fine. I suppose that will be good enough for now. I will look at the ngcgui at a later stage but I think my requirements will be met with the gcode generators. I can attempt some of my own as well.

I am really looking forward to put my packaged controller together. I will use gmoccapy with a touch screen running linuxcnc on an industrial atom motherboard. The interface will be either Mesa 5i25 with 7i76 for steppers or 5i23 with 7i33 for servos. The whole lot will be packaged in one panel mounted unit with custom buttons and MPG. No more keyboard

I tried what Jorge suggested and now I get a whole lot of errors. I changed the setting back to what it was but still the errors appear.

There are two more that are similar - all to do with scale_xxx_overide

EDIT: In the debug trace I found this. Don't know if it will help any.