halui.joint.*.plus do not work

Been trying to get this working again in qtDragon, it works in gmoccapy and it seems to work in qtDragon before homing (although no real movement, just warnings about not being homed). After homing nothing happens.

The pins do function after homing, watching the halui.joint.*.minus/plus pins I can see that the values change when I use the switches. There seems to be a blockage from halui to qtDragon?

What am I doing wrong here?

Code:

[code]  net Jog-Z-Plus       <= halui.joint.2.plus        <= input.0.btn-base5   net Jog-Z-Minus      <= halui.joint.2.minus       <= input.0.btn-base6   net Jog-X-Plus       <= halui.joint.0.plus        <= input.0.abs-x-is-pos   net Jog-X-Minus      <= halui.joint.0.minus       <= input.0.abs-x-is-neg   net Jog-Y-Plus       <= halui.joint.1.plus        <= input.0.abs-y-is-neg   net Jog-Y-Minus      <= halui.joint.1.minus       <= input.0.abs-y-is-pos  

[/code]

Code:

[code][code]command (EMC_JOG_STOP) cannot be executed until the machine is out of E-stop and turned on command (EMC_JOG_STOP) cannot be executed until the machine is out of E-stop and turned on command (EMC_JOG_STOP) cannot be executed until the machine is out of E-stop and turned on command (EMC_JOG_STOP) cannot be executed until the machine is out of E-stop and turned on command (EMC_JOG_STOP) cannot be executed until the machine is out of E-stop and turned on command (EMC_JOG_STOP) cannot be executed until the machine is out of E-stop and turned on command (EMC_JOG_STOP) cannot be executed until the machine is out of E-stop and turned on command (EMC_JOG_STOP) cannot be executed until the machine is out of E-stop and turned on Cannot jog joint 2 because home_sequence is synchronized (-1) Cannot jog joint 2 because home_sequence is synchronized (-1) Cannot jog joint 2 because home_sequence is synchronized (-1) Cannot jog joint 2 because home_sequence is synchronized (-1) Cannot jog joint 2 because home_sequence is synchronized (-1) Cannot jog joint 2 because home_sequence is synchronized (-1) [QTvcp.QTVCP.QT_ACTION][INFO]  Homing Joint: -1 (qt_action.py:99)  

[/code][/code]

Doesn't work in qtDragon git version github.com/persei802/QtDragon_hd

Before homing (if allowed) you jog joints.

after homing you must jog axes.
linuxcnc.org/docs/devel/html/gui/halui.html#_axis

cmorley wrote:

Before homing (if allowed) you jog joints.

after homing you must jog axes.
linuxcnc.org/docs/devel/html/gui/halui.html#_axis

 

I read and reread the above but it doesn't make sense. What are you trying to say? I am a mechanic, not a programmer.

The signal pins do function after homing, watching the halui.joint.*.minus/plus pins I can see that the values change when I use the switches. There seems to be a blockage from halui to qtDragon?

Before homing the motors are jogged  as joints
After homing the motors are moved as axes.

In a typical xyz machine they are the same thing. But linuxcnc treats them differently anyways.

But if you think of a tandem motor axis..each motor is a joint but together they move an axis.


Bottom line is before homing you jog joints after homing you jog axes and that means you must use the right halo pins

Same for mpg jogging.

 

Bottom line is before homing you jog joints after homing you jog axes and that means you must use the right halo pins

Same for mpg jogging.

 

would it be terribly difficult to just name the right signals?


I am tired, please forgive me.

I changed the names to

net jog-z-plus <= halui.axis.z.plus <= input.0.btn-base5
net jog-z-minus <= halui.axis.z.minus <= input.0.btn-base6
net Jog-X-Plus <= halui.axis.x.plus <= input.0.abs-x-is-pos
net Jog-X-Minus <= halui.axis.x.minus <= input.0.abs-x-is-neg
net Jog-Y-Plus <= halui.axis.y.plus <= input.0.abs-y-is-neg
net Jog-Y-Minus <= halui.axis.y.minus <= input.0.abs-y-is-pos

But doing that clashes with the same names in qt.hal So not a step further. I commented out the declarations in the qt.hal file, and I can see the halui.axis.*.minus switching, but there is no movement at all from the machine.

strange thing is that when I watch axis.x.kb-jog-active I can see it change if I use one of the on-screen buttons and it changes when I use the joystick. So why does the machine move when using the on-screen qtDragon button, and does not move when using a hardware button?

  

Ok you got alot going on in your zipped file - I quickly looked in it.

Looks like some of it is from 2.7? code (or 2.7 examples).
That was before joints and axes were separated in linuxcnc.
At that time you set a jogsped in halui and jogged an axis no matter the homing status.

Now you must set a joint.jog-speed and jog a joint (before homing)
after homing you must set a axis.jog-sped and jog an axis.

i see in both the custom_postgui and joystick files you have commented out:
 #setp halui.jog-speed 2000
Probably because it errored, because that is not right for version 2.8/master

You could set it directly by adding these lines
or you could use QtDragon's setting from the slider (must be in postgui file):
Hope that gets you closer.

It might help to understand that halui is an entity all on it's own.
It has nothing to do with any other screen unless you connect it to the screen with pins.
It really is a like a qtdragon/gmoccapy/AXIS without the screen.

Meaning it has it's own idea about jogging speeds jogging axes, etc.
This is why kb jogging works (because that is handled in Qtdragon) but not in HALUI.

Linuxcnc has no internal (global?) concept of jog settings - every screen has their own.

Thank you very much. This is the kinda help that gets people moving forward, you are very kind to look at my specific case.

I started years ago with Axis, then gmoccapy and now qtDragon. So yes, there might be some old settings in the ini and hal files. Nice of you to notice. You might have noticed my frustration at not being able to get things working and trying examples from all over the Internet.

So what you are basically saying is that the way the axis are moved changed totally from the previous LinuxCNC version? No wonder then that all the examples I could find do not work at all. Yesterday I read the Hal documentation and it sort of dawned on me that there might have been massive changes. Thanks for confirming that.

Yesterday I started to edit and update the documentation with missing stuff and examples that is available for qtDragon ( is there a reason btw why the 'old' name (silverdragon) is still used in the file?). I will do a pr pretty soon. Examples will be marked with the version of LinuxCNC they are supposed to work with.

Thanks once again. You gave me the incentive and courage to try again, this time with a little more knowledge. Will post my findings here, if and when I get it all working again.

Code:

or you could use QtDragon's setting from the slider (must be in postgui file): [code][code]net linear-jog-speed     qtdragon_hd.slider_jog_linear    halui.joint.jog-speed    halui.axis.jog-speed

[/code][/code]

[/code][/code]