Raspberry Pi 4

I did, did a rebuild, can't see any diff.
kernel and debs of linuxcnc are available at the link in my sig, add
lathe-stf/linuxcnc4rpi4 to the address above. Kernel is huge, already built, just install it. debs are of 2.9.0-pre0 about a week older than master.

jtheath wrote: Here you go. First with ini DEBUG=0 then DEBUG=7 on 2nd. In both cases I powered up then attempted to jog.

File Attachment:

File Name: console.txt
File Size:8.46 KB

There is nothing there suggesting a problem with PyVCP.
I my have misunderstood the original problem description. I thought you were saying that the PyVCP panel didn't load, not that it didn't do its job.

I suspect that the problem is due to the joints-axes changes, you now need to set up external jog buttons to jog joints in joint mode and axes in world mode.

If I am correct then I would expect the PyVCP jogging to work after the machine is homed. Can you test that?

Can you attach your PyVCP HAL file so that we can check (and correct) it?

Hello Andy,

You are correct. The PyVCP jog works after homing. The machine is screw-driven and normally doesn't rack so homing is not usually required.

My PyVCP hal entries (custom_postgui.hal) are the vanilla ones found in the documentation:
net remote-rapid-home halui.mdi-command-00 <= pyvcp.rapid-home
net remote-rapid-z-zero halui.mdi-command-01 <= pyvcp.rapid-z-zero
net remote-o100 halui.mdi-command-02 <= pyvcp.o100
net remote-move-clear halui.mdi-command-03 <= pyvcp.move-clear
net remote-zero-x halui.mdi-command-04 <= pyvcp.zero-x
net remote-zero-y halui.mdi-command-05 <= pyvcp.zero-y
net remote-zero-z halui.mdi-command-06 <= pyvcp.zero-z

# connect the X PyVCP buttons
net my-jogxminus halui.axis.x.minus <= pyvcp.x-minus
net my-jogxplus halui.axis.x.plus <= pyvcp.x-plus
# connect the Y PyVCP buttons
net my-jogyminus halui.axis.y.minus <= pyvcp.y-minus
net my-jogyplus halui.axis.y.plus <= pyvcp.y-plus
# connect the Z PyVCP buttons
net my-jogzminus halui.axis.z.minus <= pyvcp.z-minus
net my-jogzplus halui.axis.z.plus <= pyvcp.z-plus
# connect the PyVCP jog speed slider
net my-jogspeed halui.axis.jog-speed <= pyvcp.jog-speed-f

How do I map the jog control buttons to get behavior identical to the Axis keyboard operations, {up, down, left, right, PgUp, PgDn}?

jtheath wrote: # connect the X PyVCP buttons
net my-jogxminus halui.axis.x.minus <= pyvcp.x-minus
net my-jogxplus halui.axis.x.plus <= pyvcp.x-plus

How do I map the jog control buttons to get behavior identical to the Axis keyboard operations, {up, down, left, right, PgUp, PgDn}?

You need to add a some more halui pins to each axis above.

linuxcnc.org/docs/2.8/html/man/man1/halui.1.html

For X:
net my-jogxminus halui.axis.x.minus halui.joint.0.minus <= pyvcp.x-minus
net my-jogxplus halui.axis.x.plus halui.joint.0.plus <= pyvcp.x-plus

Thank you. I can do that.

Since I am running a dual X gantry should the X jog hit two joints simultaneously?

jtheath wrote: Since I am running a dual X gantry should the X jog hit two joints simultaneously?

Yes, that would probably be best.

Though if there are home switches it might be better to actually completely disable un-homed jogging.