A and B axis jog very slow when angular velocity is specified in display section

A and B axis jog very slow when these are defined in display section... 
DEFAULT_ANGULAR_VELOCITY = 5.60
MIN_ANGULAR_VELOCITY = 0
MAX_ANGULAR_VELOCITY = 56.00

This affects A and B even when the joint is type linear 

If I change display to axis, the jog function is normal. If I remove the angular specification in gmoccapy the jog is normal. Jogging with pendant is normal in all cases, this is a gmoccapy display issue.

Thanks for taking the time to consider my problems!

 

Gmoccapy appears to define the max/min angular jog velocities in degrees/minute.

github.com/LinuxCNC/linuxcnc/blob/master...gmoccapy.glade#L1403

Which means a value of "56" will result in 56 degrees per minute - painfully slow.

If you want 56 degrees/second, try increasing by a factor of 60.  Same with the default velocity value.

Note that the same glade file appears to have a max limit of 3600.  This may need to be changed in a glade editor:

forum.linuxcnc.org/gmoccapy/38811-gmocca...ular-velocity#163532

It shouldn't affect Linear axis. Joint 3 and Joint 4 are both linear.

Sorry, misunderstood your config.

Try adding this to INI:
[AXIS_A]
TYPE = LINEAR

[AXIS_B]
TYPE = LINEAR

I had a similar problem just the other day with axis GUI.  The gui was programmed to interpret XYZUVW as linear axes unless specifically defined in [AXIS].  This meant my W rotary axis was clamped by the gui at linear units.

Gmoccapy may have the same or similar programming.

Thanks for the pointers. I have increased the angular velocity, maybe too much. Setting axis to linear didn't resolve the problem, A and B respond to angular settings in GUI whether linear or angular.

 

You may want to open a ticket on github for this.  If gmoccapy isn't responding as expected  - that is using the expected units & limits for an axis type - the devs should know about it.

Or clarify in the user manual how to set an axis, or there are arbitrary restrictions on linear axis names.