Another huge failure tonight

[Parkgrr]

There is a known but yet unaddressed issue with involuntary movements when using the UCR201 pendant. Usually this manifests as short ~1in rapids on whatever axis is chosen to jog (a video is posted elsewhere) but once in a while it does an infinite rapid, meaning one axis will go until the servos fault when it is physically stopped by the bed, the tool piece, a body part, whatever. As mentioned before the 2nd huge movement made by this error was on Z and crushed my tool changer causing hundreds in repairs and a month of shop downtime. Tonight it did the 3rd large rapid movement which was to send the axis selected on the pendant, Y, to +infinity. I immediately hit E-stop on the pendant which did nothing, I ran to my PC and hit RESET which did nothing. Finally it hit and bent my metal end-stops 12 feet later. When I started breathing again I tried to jog and saw that the values would change on the DROs but the axis would not move. I checked the UC300ETH and saw that no output signals were being sent when I jogged. I saw that "offline mode" was active on screen which would explain why the software was unresponsive to E-Stop.

I am still in continual troubleshooting mode on my side, doing clean installs, trying a different PC etc, but have already spent the money I could on this machine after I chose UCCNC and cannot switch to another controller and software. This post is just to plead:
CNCDRIVE, PLEASE PLEASE PLEASE GIVE SOME ATTENTION TO THIS ISSUE.

[ger21]

Not the answer you are looking for, but I'd have stopped using the pendant after the first time it damaged the machine.

[cncdrive]

I wrote already in your other thread that we working on the issue.
If you will post this same matter more times will not help us to resolve the issue faster.
Sorry, but how fast the problem gets resolved does not depend on how many times you will post the problem, it will only depend on how fast my collegues can eliminate the issue.
They working on the issue (reproducing, debugging, fixing etc.), but it takes time, sorry.

[CT63]

You should stop using the UCR201 until a solution is found or buy another brand of pendant. I have two VistaCNC pendants never had a problem with either.

As far as machine safety... e-stops should be hard wired to kill power to the servos (or steppers). Never, never rely on e-stop safety via software for just the reasons you mentioned. I work with industrial PLC's and VFD's that have to be NFPA-70E and OSHA compliant. Machine e-stop safety is never allowed by software only.

[Parkgrr]

I'm a startup business owner, I have many equally pressing things like this that need addressing that I'm solving as I can, I don't think that not having possible available solutions is a prerequisite for asking for an issue to be fixed. I recognize you guys are aware of the issue, you'll forgive me for feeling that it's not high priority as up until very recently the response I've received is "There is something strange..., but we cannot find the problem... However, the most of the users never meet this behavior". Since I'm here posting again I'll repeat PLEASE PLEASE PLEASE ADDRESS THIS ISSUE

I'll hardwire an E-stop somewhere, that was terrifying. I'll check out VistaCNC

[Parkgrr]

link to earlier responses https://www.forum.cncdrive.com/viewtopic.php?f=2&t=3451#p25164

[cncdrive]

Look, I already promised you that we will try to address the issue, but you must understand that this is not like painting the wall when you know exactly how much time and effort is needed to be done, this kind of reproducing/debugging/fixing is not that type of job. It is unpredictable how much effort and time is exactly needed to reproduce/debug/fix it.
I remember a few bugs which took us a month of continous debugging and testing and coding to fix it.
Some bugs take minutes to find and fix, some others months.

So, what I can still tell you is that my collegues are working on resolving the problem and they working on this bug right now, so I don't really know what else to tell you.

[spillage]

I spend many hours here reading and learning, preparing for my implementation of UCCNC.
There’s one thing that stands out above all else… cncdrive and crew are VERY responsive.
They have answers, fixes, or temporary work arounds (until the fix is found) in relatively short order, most times.
Things that take longer they report back when solutions are found (unprompted).
So unlike many places, not getting a quick response doesn’t mean you’re being ignored… it means the answer hasn’t been found yet.

[CT63]

Hard wiring an e-stop is a pretty simple process and only the cost of a switch and relay. The easiest way is disconnect the power source to the servo drives via the E-stop switch or switch and relay depending on the application.

If using a relay make sure to wire the contacts normally open. By that I mean the relay has to be energized to close the contacts to supply power the servos. This provides a fail safe if the E-stop circuit wire breaks or E-stop switch fails... the machine stops. As I you found out never rely on software only for E-stop safety.

[Karnage]

There is a known but yet unaddressed issue with involuntary movements when using the UCR201 pendant. Usually this manifests as short ~1in rapids on whatever axis is chosen to jog (a video is posted elsewhere) but once in a while it does an infinite rapid, meaning one axis will go until the servos fault when it is physically stopped by the bed, the tool piece, a body part, whatever. As mentioned before the 2nd huge movement made by this error was on Z and crushed my tool changer causing hundreds in repairs and a month of shop downtime. Tonight it did the 3rd large rapid movement which was to send the axis selected on the pendant, Y, to +infinity. I immediately hit E-stop on the pendant which did nothing, I ran to my PC and hit RESET which did nothing. Finally it hit and bent my metal end-stops 12 feet later. When I started breathing again I tried to jog and saw that the values would change on the DROs but the axis would not move. I checked the UC300ETH and saw that no output signals were being sent when I jogged. I saw that "offline mode" was active on screen which would explain why the software was unresponsive to E-Stop.

I am still in continual troubleshooting mode on my side, doing clean installs, trying a different PC etc, but have already spent the money I could on this machine after I chose UCCNC and cannot switch to another controller and software. This post is just to plead:
CNCDRIVE, PLEASE PLEASE PLEASE GIVE SOME ATTENTION TO THIS ISSUE.

I'm struggling to understand why you would have a machine without basic safety features such as a hardwired E-Stop. Secondly if you know the issue is unresolved, it's foolish to think the crash is anyone's fault but your own. UCCNC are aware of the issue and have stated they are working on a solution, perhaps a little patience and using one of the many alternative input methods might serve you better than crashing you machine repeatedly?