gmoccapy 2.1.0 has been released

Please try with configs/sim/gmoccapy/gmoccapy_lathe.ini

Excuse me, I tried configs/sim/gmoccapy/gmoccapy_lathe.ini .
There is correct

OK, than it is for sure your config.

Norbert

tarasko wrote: Well ok. You even didn't compile it correctly.

First you need to launch configure script with additional parameter as been sain in error message:

./configure --enable-non-distributable=yes

Then continue with compilation as instruction says.

After successful compilation you need to launch linuxcnc script:
~/linuxcnc-dev/scripts/linuxcnc ~/<some_location>/<your_configuration_ini_file>

After I changed this parameter in the config I was able to get it to work. Now time to play with the 2.1

A bit old for this thread maybe. Anyway.

I have a nagging issue when using a joypad for jogging on the lathe.
It worked fine in 1.x and in general it works fine also in the latest 2.1.
However, if I for example touch off, enter a value and then try to jog
with the joypad keys it won't work. I need to manually press one of the
X-/X+/Z-/Z+ buttons in gmoccapy with the mouse. Just a press
seems enough. Then the jogging with the joypad keys works again.
Until a new user input on the gmoccapy screen is needed.

The joypad is controlled by
loadusr -W hal_input -KRAL F310

Do you have an idea of what this can be?
Thanks.

That is strange,

What version do you use?
I just pushed release 2.2.0.2

I have not seen such a behavior with my two "handwheels" but I use MPG for jogging, not button.

If you update and start from terminal, you would see printed the mode changes.
Setting a value is done in MDI mode, while jogging is allowed only in manual mode.
Depending on your config, there might be a race conflict in mode changes.

Norbert

I tested now with the latest 2.2.0.2 I think.

I too use a MPG in my milling machine and that works as it should

I looked at the mode change debug output and that seems to happen at the right time.
What I also get is
The "wrong motion mode" message come when I press X+/X-/Z+/Z- in gmoccapy after using the joypad.
After that the jogging with the joypad works.

The wrong motion mode comes from joint axis handling
What hal pin do you use for jogging?
Please post your config.

Norbert

Quick question.....will this version work with 2.7.8? Was going to download all the required files and do a re-make of the source to get V2+ if it does.

No!
It will not!

If you want to use v2+ with 2.7, you will need to change some code. The main difference is that I changed gmoccapy to support the new Joint/Axis changes from 2.8

If you just want to use the new slider Widgets, that can be done with a reasonable amount of gode modifications.

Because I do support at the moment 3 release versions (gmoccapy in 2.6, gmoccapy in 2.7 and gmoccapy in 2. I have not many time to make special wishes come True

I will announce very soon, that gmoccapy in 2.6 will not be supported any more, as users should update to 2.7

Norbert

@Hakan,

I still need to know what hal pin you use for jogging to solve that issue!

Norbert

Of course.
I first want to go through my configuration to see if I can find anything myself.
I will come back with info during the weekend.
/Hakan