Anyone experienced the issue that firing the laser interfered with the arduino that runs grbl? When i’m moving x/y axis and fire the laser it stops. This is most of the time because it seems to trigger reset or emergency stop. if i home or unlock i can move it again. And once it set the grbl settings to default.
Does anyone know a solution?
Common problem usually is grounding problems created by messy wiring, daisy chained PS grounds, LPS arcs etc…
Post a picture of your wiring…
its really messy at the moment. shall wire it up better soon and post a picture and results
I had the issue. I removed the LCD and all is well. I think there is a grounding issue on the LCD/Encoder
I had the same problem was driving me mad as everything worked fine with a mega running marlin but started doing as yours did with a UNO and GRBL. What I found was noise on the end-stop wiring triggering end-stop hits. My solution was to put some 6.8 uF caps on the X and Y end-stop wiring at the the UNO shield end. All good now, It is very strange that all is good with the Ramps/Mega setup but not with the UNO. Anybody with any reason this should happen
Just to add to that mine happened whenever I did an X/Y move without laser firing eg homing.
@tony_turner explaining noise in these systems especially those running at 3.3 vdc is not easy. Add a 20,000v, 20ma laser and/or high current stepper and you enter the realm of magic :). Long wires (like end stops) are susceptible to noise especially when these signals connect directly to the processor without any input conditioning like Schmidt triggers.
I am surprised that such high value caps (low frequency filter) worked for you. I have often found that even though the problem is fixed by input filtering the problem is actually a grounding problem, usually at power nodes. Folks like to daisy chain power and grounds and this creates very complex current flows and loops.
Different boards have different grounding schema and that can account for differences in noise susceptibility… sort of !