Pendant delay after zeroing an axis in PP 2.12

I have not yet reverted to PP 2.10 to see if the problem goes away but every since the initial release of 2.12 I have noticed that jogging any axis after zeroing any axis results in delayed movement lasting a couple of seconds. At first I thought this was related to having a large program loaded and PP needing to recalculate the graphics, but I have since confirmed that it also happens with no program loaded.

To recreate the behavior:
Position the machine anywhere
Zero any axis
Attemp to jog the machine using the pendant

Following these steps, the machine will move but it hesitates and then jumps. After a few seconds it’s back to normal. If I wait a few seconds after zeroing and then jog, it works normally. In either case, what is shown on the DRO corresponds to the actual location so there is no loss of position, it’s more of an annoyance than a problem.

Some possibly noteworthy items:
I am using a MadeWithCNC pendant as I don’t have an operator’s console. This pendant has been working properly for a couple years now, prior to 2.12.
I have not reverted to 2.10 but all versions of 2.12 have exhibited this behavior, including 2.12.4
I have not attempted to jog with the keyboard (broken too many haimer tips that way)
I have not checked for the same behavior with the jog shuttle (been in the drawer ever since I got the pendant)
I do not have a pendant on my 440 so I’m not sure if the same thing happens on that machine or just the 1100MX
The behavior persist after replacing the USB hub that the pendant is connected to

I’ve had this for a couple versions. It’s usually programs with over 150,000 lines. As the machine is refreshing it pauses (and buffers) any moves then executes them all as soon as the refresh finishes. Be very careful turning the jog wheel because you crank it1 click and it doesn’t move then crank it 5 inches to see if it’s working and it storing all that. Hit the stop or it’s gonna move as soon as it refreshes. You can tell it’s refreshing because the program counter will stop, if you’re running a program. The clock also stops, I’m running a 20mb program and it talked about 3 minutes to load and refresh.

1 Like

Personally, I cant have the jog puck plugged into a usb hub on any of my machines. For me the puck has to be plugged into a usb port on the computer.
Even then I get usb hub “noise i call it” if there is even one usb cable strain “pulling” on the hub. making keyboard, mouse…act flakey at times.

I am aware this is a thing but as I mentioned, the same effect occurs with no program loaded. The buffering of large programs to update the graphics I can understand and has been around for as long as I’ve had the machine and probably since the first iteration of the software. Hesitation with no program loaded and therefore, minimal graphics to update, seems to be a new issue as of 2.12

@Lane_Burkhart while this would make some sense given the tendency of usb hubs to fail regularly on these machines, the consistency of the issue suggests that it’s not related. I’ve experienced the occaisional connection issue between my keyboard, touchscreen, and pendant, during which time, none of them respond. This is random both frequency and duration. The issue I’m describing occurs every time I zero an axis, with no exceptions, and while I have not timed the duration of the issue, that seems very consistent as well.

Seems it’s time for a bit more diagnosis and testing on my part, then I’ll put in a support ticket.

@Ian_Vivero

I wasn’t positive if you meant the jog shuttle or the console pendant, I tried both on an 1100MX and 1500MX with 2.12.3 and didn’t see any noticeable lag. Please open a support ticket with a video and logdata taken right after attempting to jog so we can look into your issue.

Thank you,
Norman

1 Like

Neither actually, I am using a MadeWithCNC pendant. I haven’t gotten back to the machine since posting so I’m going to do a bit more testing on my end to see if the jog shuttle and/or keyboard behaves the same way. I’m also curious if the pendant will cause the same behavior on my 440 which has not seemed to have the same hesitation but I am usually slower to move that machine after zeroing an axis due to how it’s setup in my shop so I might be slower than the hesitation period.