I am getting intermittent and recurring 'Hard limit triggered' events when running a gcode that is nowhere near the limit switches. Is there a list of potential causes for the 'false' alarm that I can work through? Thanks!
Depends on what sort of limit switches you use. Normally open switches are particularly susceptible to EMI (interference). Normally closed switches can give false triggers if there is a dodgy wiring connection. Keep mains and spindle cables away from low voltage stuff, check your wiring. If you think it might be EMI (and you have your mains cables well away from other wiring) ferrite cores - especially near the controller - on switch wiring and usb cables will help. Alex.
Thanks, I am using an Acro 1510 with the OpenBuilds Xtension Limit Switch (normally open). Interestingly, the low voltage lines to come within a few inches of the power cable to the power supply so I've separated those and will see if I experience the problem again. Will post here how it goes.
Do let us know if that solves the problem - the Xtension Limit Switches are quite well protected but nothing is completely immune. Alex.
What tool head is on the acro? (laser, pen, etc?) is it something that does make any static or EMI? What's the exact setup, details count. Dust extractor hoses make awesome static electricity generators for example, while easy to overlook. Tell us what's around it and we'll help identify causes. Xtension switches are very resilient against EMI. Hf plasma or VFD might push it over the edge
The tool head is a Nema 17 linear actuator with lead screw controlling the Z axis. The lead screw is about 15cm long, and the gantry holds an acrylic pen. The Acro is mounted to an IKEA table (laminated wood table top supported by metal legs). It's powered on the standard EU 220 voltage and I have been using it without incident for over a month at least. I recently upped the speeds on the X and Z axes which may have been a contributing factor. The alarm was still triggered after moving the power cord further away from the low voltage cables and also after switching to a different USB cable. Running the same gcode file does not result in the alarm being generated at the same point. The alarm was not triggered after disconnecting the Xtension limit switches from the BlackBox Controller. My gcode files have about 40,000 to 60,000 instructions in them, so static electricity seems like it could be a cause, if there is a way to discharge that from the system I will try that out. I suppose I can also reconnect one limit switch at a time to see if it is associated with a specific one.
I suspect you need to run shielded wiring to your switches. If you do, make sure the ground/shield connection is at the controller. Honestly, I'd like to see OB come out with NC style limits switches rather than their current NO ones. I know there is disagreement on this point but NO switches are more susceptible to noise than NC switches. It also helps if there is filtering or optoisolation on the inputs at the controller. Not sure what BB has.
Blackbox has filter at the controller end; see https://openbuilds.com/attachments/brain-pdf.38327/ Alex.
Xtension switches has RC filters right onboard too (so doubled up with a Blackbox but even with lesser controllers Xtension Limits got you covered) I am doubting this IS EMI at all here. No big EMI sources nearby. Could be a faulty switch (mechanical side) that triggers from vibration. Xtension Limits run fine with unshielded wire next to Cut40 Hf plasma inverters (; We did a lot of testing and by adding active filtering, we solved the EMI issues, and still able to keep No wiring for all the advantages it lends (easier wiring, default config values, etc)
I encountered the same hard limit alarm error again today (multiple times) despite having the limit switches disconnected from the BlackBox. I'm mentioning this in case it narrows the search space of potential causes. It isn't really negatively impacting me, aside from being an annoyance. I may test out a different set of gcode files tomorrow to see if I hit the same issue.
What are your $20, $21 and $22 settings at the moment? Try setting them all to 0 and see if that helps. (disables homing, soft and hard limits). Also see if you can find any faults on the limit switches - can you get a connection between signal and ground with a tiny movement? Alex.
Yes, agree that's worth doing. Did you disconnect them at the switches or the BB? I'd also take a close look at both sides of the BB circuit board to see if there is anything obvious like metal debris or loose wires or ...
Switches were disconnected at both the BB side and the switch side, $20 was set to 0, $21 and $22 were set to 1 (when I was getting the alarms) I have set them all to 0 and haven't encountered the hard limit alarm since then. If there is anything else I should check just let me know. Thanks!
As @phil from seattle said, check both sides of the black box circuit board for any obvious faults - they are quite rigorously checked before despatch, but still worth checking.
Although that gets you running, it doesn't find the problem. Have you checked your switches to see if one of them is faulty? Use a multimeter to check for continuity between sig and gnd and see if a very small movement of the lever gives continuity. Also double check your wiring for any stray "whiskers" of wire that might be making intermittent contact. Alex.
After a full day of cutting, I'm suddenly experiencing this. I'm using BlackBox & Xtension switches. It seems to be from vibration... it's most often when the spindle is moving to the left, and isn't in the exact same spot. I'm going to disable switches one by one & see if I can narrow it down.I'll post what I find.
I disconnected the Z axis switch first & still got the issue. I reconnected the Z & disconnected both X axis switches & the issue went away. I reconnected the left X switch & the issue stayed away. I reconnected the right & it came back. I checked the right connector & wiring with a loupe; all looks good, so I swapped in a brand new switch. I'm back at 'real' work for a bit & will finish this later but I suspect that it was a faulty switch.
Not the switch! The issue occurred again with the new switch. I disconnected the new switch & repeated the test; it went away again, so the only thing left is the wiring. I disconnected the wiring between the X axis switches & inspected it. It's undamaged. Then I carefully reconnected it. I'm running a cut again and it's all working - all connected, no issues. So, weird. We'll see how things go.
...still might be more going on. today as I started running a program I noticed that my vacuum hose wasn't seated in the dust boot properly. I wiggled it in and just as I did it stopped with the same error. I have a ground wire in the hose & I don't know if had anything to do with the wire or just the static in the hose itself, but I reseated the hose, ensured there was some distance between it & the router mount (~1/2") and oriented it so the wire was on the opposite side of the hose. I haven't had an issue since. Once I'm done with the job I'll play with it & see if I can reproduce it.
I’ve also disconnected the limit switches from both sides (limit and bb), I’ve tried running the openbuilds control spoiler board surfacing job 5 times now and each time it fails showing that a hard limit was hit. How can it be detecting that a hard limit was hit if there’s no hard limit switches connected? This is on a stock lead 1515.
I have had this machine up and running for less than 24 hours lol, I’ll Google and see how to do that.
This is driving me nuts. I’ve run several jobs (hello world, a couple other jobs) that have run fine. I’m now trying to flatten the spoiler board using the openbuilds control wizard job. I keep getting a hard limit hit alarm - I’ll restart the job, and as soon as it gets to the spot where it’s cutting into material it trips for hard limit hit. I’ve ensured that there power cables are away from the black box, and I’ve tried unplugging all limits from the bb and the limits. This is a brand new machine with brand new wiring. Pulling out my hair lol.
Consider it a troubleshooting step. Soft limits will still protect the machine (as will common sense, most people dont bother with limits) You can revisit limits after spending a little time working with the machine first - get to making stuff so you feel better about it all. Then someday revisit your EMI issues. Disconnecting the switch won't make the EMI go away (the switch has pullups etc that keep the line high, you now removed that, making the signal line even more susceptible) - provided you have the good Xtension limits When it comes to EMI its better to address the source of the EMI than trying to shield everything around it. Badly earthed spindles, dust extractors without anti static hoses, that sort of thing. So disable Limits for now. Get some work hours under your belt, experience is a great teacher. Then in a couple weeks when you have a better feel for it all, revisit limits