Gmoccapy - A new screen for linuxcnc

This is interesting (And a little surprising as gmoccapy is a German GUI

Can you try one of the sim/axis configs and see if the same problem exists there? I think it probably will as both use the same preview widget (hal_gremlin)

If it does, then I think it is something for the bug tracker:
github.com/LinuxCNC/linuxcnc/issues

This German is surprised too
Axis is actually fine with de_DE.utf8, as I said in my P.S. It seems to be an issue of gmoccapy only. Actually, gmoccapy shows a period as the decimal separator everywhere inspite of the de_DE locale setting (and even complains about G0 X10,5), but the G5X page shows commas and gets confused with a period.

A quick fix is of course to set LC_NUMERIC=en_US.utf8 or LC_NUMERIC=C and leave the rest of the locale settings as is.

Maybe the german author of gmoccapy can chime in sometime.

My Weiler Lathe with Sinumerik 810t I have to go too G0 X5.0 Z-1.0 nix shows commas

This German is surprised too
Axis is actually fine with de_DE.utf8, as I said in my P.S. It seems to be an issue of gmoccapy only. Actually, gmoccapy shows a period as the decimal separator everywhere inspite of the de_DE locale setting (and even complains about G0 X10,5), but the G5X page shows commas and gets confused with a period.

Hallo,

That is the first hint to go on searching the offset in the preview. If that is really a "komma" bug, it should be possible to find. Could you please test if the offset also happen with gscreen?

IMHO Axis uses a slightly different preview but gscreen and gmoccapy do share the same code.

Unfortunately I must tell you, that I will not invest too much time in this, as actually I am building gmoccapy to support 9 axis and at the same time, I am separating GUI and handling code. This will result in gmoccapy 3.0 or even "minos" (the future replacement).

You may ask why to change all the code? Because after this it is much easier to change the GUI part and replace also the underlaying widget base, i.e. from glade to Qt.

Norbert

Hallo Norbert,
I just checked that gscreen has the same offset issue with de_DE.utf8 as gmoccapy. There is really no need to put much work into this as setting LC_NUMERIC differently is not a problem at all, at least for my application. Exciting news that you are working on a new version and going from glade to Qt. I am looking forward to that!
Cheers,
Karl

hi
does anybody know how I can connect the DRO input to a different pin other than the default Z axis?

What are you trying to do?
All can be done in the gmoccapy python file,

but without more details no one will be able to help.

What gmoccapy release?
What config?
What distro?
What purpose?

Norbert

HI
Happy new year to all.

I have created a kind of stand-alone THC component for plasma.

forum.linuxcnc.org/plasma-laser/32555-do...nent?start=20#103768

This component does not work with the motion controller.
However, I really like to show the step generator feedback on the DRO & Plot

I'm working on the master branch with the debian distro.

thanks...

I just looked in the sample INI you referenced too.
It is an axis config, so may your comment is in the wrong thread?

Norbert

Well, I have a very limited knowledge of the Gmocaapy GUI.
As I see in a normal configuration the feedback from step generator should be connected to
joint.x.motor-post-fb

net x-pos-fb <= hm2_5i25.0.stepgen.00.position-fb
net x-pos-fb => joint.0.motor-pos-fb

however, I don't want to connect mine to a joint, I want to connect directly to DRO

thanks..