gmoccapy 2.1.0 has been released

racedirector wrote: 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

Thanks, didn't notice your reply as it was an edit of of my post.

I tried 2.8 but it messed up my ini file to the point of not working so I went back to 2.7. One day I'll try 2.8 again.

Had a look at the config files for my lathe but can't find anything obviously wrong.
Switched to Axis and the hick-up wasn't there.
Repeat by jogging, then touch off and enter a number.
After that a mouse-press on the X+/X-/Z+/Z- key buttons is required for further jogging with the joypad.
Commented out ALL joypad settings and the message still comes.
Startup gmoccapy, e-stop off, power on and then press X+/X-/Z+/Z- and it says
"wrong motion mode, change to the correct one". I go and home the axis and again when I
press X+/X-/Z+/Z- and it says "wrong motion mode, change to the correct one"
Perhaps it has something to do with the homing?
At least your comment in gmoccapy.py suggests that.
I have tried to set up with no homing switches. Intention is that I press "home X"
the axis should home immediately without moving.

But perhaps it is not the homing, it may be the joypad.
Couldn't test that when joypad was uncommented of course.

custom.hal
custom_postgui.hal
A part from Turner.hal

Hi,
tested some today. I could get it to work actually,
When I press "Home all" then the joypad works as expected.
But I usually press "Home X" and then "Home Z", don't know why I do it that way really,
and then the X+/X-/Z+/Z- mouse press is needed.

So I will just press "Home all". Easy,

As already commented out, I am not able to test on real hardware at the moment.
But I think it may be related to the halui pin. Why are you using that pin and not the gmoccapy ones?

Just connect like so:
Please try and report.

Norbert

No success, the pin is a float and the is a bit so got an error message at startup. The abs-y-position is analog between -1 and 1.

But I think in principle it works using halui, it is just that joint.1 will not get homed when pressing "Home X" and "Home Z". It will get homed when pressing "Home all". Even if the Y axis is not used it is there in the background. That is the difference as far as I can see.

If you want to use that pin, you should take a look at:

gmoccapy.jog.jog-velocity.direct-value
and
gmoccapy.jog.jog-velocity.analog-enable

etc.

Just take a look at the documents.

linuxcnc.org/docs/devel/html/gui/gmoccapy.html#_hal_pins