Jogging not working properly when not on preview tab

Hi,
I have an issue where jogging is very unstable when I'm not on the Preview tab.
The jog signal (examined cmd_vel using halscope) will go off-on-off-on-off-... multiple times every second, but only if I'm not in the preview tab.

I tried to disable all of my custom tabs, and then testing using DRO tab.
When all custom tabs (and galdevcp side panel) are disabled, the issue is almost gone, but I still get a few off/on ticks.

As soon as i add a custom tab (even with no python script except for get_handlers + __init__) this issue is very severe when not on the Preview tab, even for DRO tab.

LinuxCNC version is 2.9.0-pre0-3879-g9a26e69fe
 

Have you tried testing your set up in version 2.8? Are you jogging using an MPG? Are all wire connections tight ?
Some more information about your system would possibly help. What Computer, driver boards, ect,ect.
 

tommylight wrote:

First, try another keyboard.

oh yeah. I thought I had covered the basics. The key board didn't even occur to me.

Using keyboard. No MPG.
Tested with other keyboard. Same.
I took a screeenshot of the halscope. Signal is joint.0.vel-cmd, while continously pressing arrow on keyboard.
Same issue for all directions.
Never an issue when Preview tab is selected, only while other tabs are selected.

Tried upgrading to newest 2.9 (python 3) and although it seems a bit better, the issue is still there.
Downgrading to 2.8 is not a solution for me.

Motors are connected with EtherCAT.
Linux Mint 19
4.19.1-rt3 #1 SMP PREEMPT RT 

I unfortunately have never used version 2.9. So my help will be extremely limited. That said what has helped me in the past
is make a second profile with the absolute minimum you need to test. Then double check connections. While jogging
wiggle some wires and see if things change. its possible a poorly connecting pin can cause the problem . But I will
admit that screen shot doesn't look like a bad connection. It looks more like something is trying to PWM the output.
 

I think this is expected behaviour. To jog, you have to be in teleop mode which will only be enabled if the jog buttons on axis are displayed.

halui.mode.teleop pin allows you to select this mode.

I came across this years ago with Gmoccappy and ended up programming a button on my pendant to select this mode (which moved to the appropriate tab)

I might add that I have axis running on  V2.9 and Ethercat and did observe this behaviour. But I thought nothing of it based on my past experience.

I looked through the version 2.9 manual and found a spot that lists a known issue of keyboard jogging doing as you have described.
see section 4.7.18.1

2.9 manual

my1987toyota wrote:

I looked through the version 2.9 manual and found a spot that lists a known issue of keyboard jogging doing as you have described.
see section 4.7.18.1

2.9 manual

I wonder if that is specific to QTplasmac? Its not about Axis there.