Z axis randomly diving

[Parkgrr]

(Also I'll try the new plugin and report back, when I downloaded UCCNC from the CNC drive website last year it came with many very outdated plugins including this one).

[dezsoe]

Of course, I didn't mean to say that this bug is not important because only a few people see it. I just wanted to say that it's very hard to find a bug which we don't see. Even you find it only once a week.

It's the same for the probing issue: we know that the problem exists, but we cannot reproduce it. Battwell could make a video, so we could see how it all happens.

[mickecarlsson]

I just installed 1.2114 in a separate folder on C: (C:\UCCNC-12114), then copied my profile (micke.pro) and Ger's Screenset 2017 and macros to the proper directories.
Started up UCCNC with the profile micke.pro, checked that all was OK. Homed all axis, jogged around with my numeric keyboard. Did an Auto initialize. All was good, it probed the mobile probe, then went to the fixed probe and probed. no problems.
I then enabled the UCR201 and restarted UCCNC. Did the same, homed all axis, jogged around with the UCR201, no problems. Did an Auto initialize. Got this error immediately:

Probe error with UCR201 enabled.

I then shut down UCCNC, disabled UCR201, repeated the procedure, Auto initialize was OK.
I then did a complete Windows Update (I am running LTSC of Windows 10, that is 1809 without any bloated MS software). I got some .NET updates and the 2021-10 update and the computer restarted.
I then run UCCNC1.2114 without UCR201, all was good.
Enabled UCR201, tried Auto initialize and Auto zero. None of them worked.

I am running MySensors with RFM69 radios, those use 868 MHz, the same as UCR201 if I am not misstaken, I don't know if that is an issue at all as UCR201 works perfectly with jogging, it is just when you call a macro to do Auto zero or Auto Initialize.
My suspicion is that something is blocking the macro's trigger functions when UCR201 is enable.

I have not tested the 2019 screenset (lack of time) but if there is an auto zero macro that I can test, I will do that. My CNC is not used to much for the next week or two so I can test whatever you want.
Or, if you have a test version with logging that you can send me, I can test that.

[mickecarlsson]

Just to make sure that it is not my RFM69 radios that is disturbing the UCR201 I switched region to US C1, it did not make any difference, same error.
I am now trying the default 2019 screenset, but I need to read up on the probing, I could not get the mobile probe to work.

[mickecarlsson]

This is thread is also related: http://www.forum.cncdrive.com/viewtopic.php?f=4&t=1751

[Parkgrr]

Update:
I brought in RF frequency analyzing equipment to see all the activity in my shop. I found that the channel I was operating in had some other activity on it so I found a channel that had absolutely no activity and switched to that. This made no difference. I was sent a new UCR201 by Balazs (thanks Balazs), this seems to have made some difference and may have reduced the occurrence slightly but the issue is not gone. Here us a video after all of these changes of the MOST MILD way that this issue shows up. In the video I jog X, let it 'go to sleep', then wake it. This is the most reproduceable way to get the error to fire, the error of course also happens outside of the immediate waking. As mentioned it ranges from a 2 inch or so movement like this to a much larger 6-8 inch rapid movement.

https://youtu.be/s0glx-4-8K8

[rajjinator]

I have the exact same issue with the UCR201 and involentary jogging when waking up the pendant. as per your youtube video!

I started my own thread here https://www.forum.cncdrive.com/viewtopic.php?f=3&t=3623 before I was pointed at this thread by another user!

I should add this issue seems to occur not just for the Z axis but for whatever axis was last selected in the UCR201 before it went to sleep (as evidenced in your YouTube video also).

[rajjinator]

I'm surprised there is no response from cncdrive on this. The UCR201's are not cheap bits of kit which can't be used currently for fear of snapping the tip off my haimer when jogging with the pendant. Seems to be a fairly widely seen and repeatable issue...

[cncdrive]

We already answered in another thread on the forum reporting the same issue that we working on resolving the problem.

[rajjinator]

We already answered in another thread on the forum reporting the same issue that we working on resolving the problem.

Apologies, I have not seen "the other thread". Do you have a rough sense of timescales for when this issue might be fixed?

Many THanks,