gmoccapy 2.1.0 has been released
Thanks, didn't notice your reply as it was an edit of of my post.
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.
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.8) 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
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.
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.
loadusr -W hal_input -KRAL F310
# Include your custom_postgui HAL commands here # This file will not be overwritten when you run PNCconf again loadrt or2 count=2 loadrt mux4 count=1 addf or2.0 servo-thread addf or2.1 servo-thread addf mux4.0 servo-thread setp mux4.0.in0 0 setp mux4.0.in1 25 setp mux4.0.in2 50 setp mux4.0.in3 1000 net remote-speed-slow or2.0.in0 input.0.btn-x net remote-speed-medium or2.1.in0 input.0.btn-a net remote-speed-fast or2.0.in1 or2.1.in1 input.0.btn-b net joy-speed-1 mux4.0.sel0 <= or2.0.out net joy-speed-2 mux4.0.sel1 <= or2.1.out net jog-speed <= mux4.0.out net jog-x-analog <= input.0.abs-y-position net jog-z-analog <= input.0.abs-x-position
A part from Turner.hal
# ---HALUI signals--- net joint-select-a halui.axis.x.select net x-is-homed halui.joint.0.is-homed net jog-x-pos halui.axis.x.plus net jog-x-neg halui.axis.x.minus net jog-x-analog halui.axis.x.analog net joint-select-b halui.axis.z.select net z-is-homed halui.joint.2.is-homed net jog-z-pos halui.axis.z.plus net jog-z-neg halui.axis.z.minus net jog-z-analog halui.axis.z.analog net jog-selected-pos halui.axis.selected.plus net jog-selected-neg halui.axis.selected.minus net spindle-manual-cw halui.spindle.forward net spindle-manual-ccw halui.spindle.reverse net spindle-manual-stop halui.spindle.stop net machine-is-on halui.machine.is-on net jog-speed halui.axis.jog-speed net MDI-mode halui.mode.is-mdi
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,
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:
net jog-x-plus gmoccapy.jog.axis.jog-x-plus <= "pin from your pendant"
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.
Just take a look at the documents.