Gmoccapy - A new screen for linuxcnc

Jorge

Did you do a "make clean" before building again after the pull?
And then do
./autogen
./configure

from the /src directory

Marius,



I make clean but still have problems

thanks

Jorge

I dont understand much of what I see in the file due to language barrier but I did see this line

there is a dot after the sim in the directory line "sim.gmoccapy" I dont know if that has anything to do with the problems but I suggest that you have a look at that.

How do you start the system?

Hola Jorge,

favor de hacer lo siguiente:

maneja a /linuxcnc-dev/src

make clean
./autogen.sh
./configure
make
sudo make setuid
cd ..
. ./scripts/rip-environment
linuxcnc

Saludos de Norbert

Hallo Jorge,

all the errors in you last attachment are normal, they are more likely informations from gmoccapy, I can not see, why linuxcnc closes at this time.

Have you tried any other GUI?

Norbert

@Marius

I have a request please. Is it possible to have a indicator to show if we are in Radius or Diameter mode. Especially in the touch off screen. Sometimes some gcode program can pit the machine into another mode than what you usually operate in and then when you touch off you enter the wrong offset.

This is already included.
Please watch the DRO.

If you are in G8 the D-DRO should be with gray background, in G7 the R-DRO is grayed out.

Just look there and you know the black one is the active one.

Norbert

Hi Norbert

I tested in sim and it seems to be as you say (not that it would be else wise ). I did not notice that on my lathe though. The motor is burned out now so I cannot run it to test.
The scenario happens when I run some of the pyngngui stuff. Sometimes the program is in Radius mode and sometimes not ( i have added some programs already). I will have to test to see how it happens. I am hoping to have a new motor and VFD soon.

newbynobi wrote:

@verser,

I just pushed 1.1.5.6 to master and 2.6, including new hal pin:

gmoccapy.program.length = S32, OUT (total number of program lines)
gmoccapy.program.current-line =S32, OUT (current executed line)
gmoccapy.program.progress = FLOAT, OUT (progress in %)

Now you are able to make your custom panel just with one hal progress bar and connect the gmoccapy hal pin to the progress bar.
...
Norbert

Thanks!

Guys,

I tried reading through the whole thread, but might have missed my answer.

Is there a screen in Gmoccapy that resembles this one yet?


That one is actually really very close to what I am desiring. Is there some location with many different Turning Center screens available right now, in LCNC?

Thank you.

The Gmoccapy screen in lathe mode has all the functions that you need on a lathe. And very similar to the sample you gave. I am using the Gmoccapy lathe screen and it does very well and is very practical.
Try it.

If you want a screen just like that you will have to create it yourself .