Hi all, hope someone can help please, final stages of my build and I have an unusual limit switch issue which I cant work my way around, hopefully it's just something simple i'm overlooking. - Machine is 3 axis, 2 NO limit switches on each axis. - All on shielded CY cable - To eradicated any interference the switches are connected to the Ramps board via optocouplers with each axis' switches in parallel. - Homing works perfectly BUT the limit switches do NOT create a stop scenario when they are triggered during a "jog" or running a job. - $21=1 Any help will be appreciated! Thanks in advance $0=10 $1=255 $2=0 $3=5 $4=1 $5=0 $6=0 $10=1 $11=0.020 $12=0.002 $13=0 $20=0 $21=1 $22=1 $23=1 $24=250.000 $25=1000.000 $26=250 $27=4.000 $30=24000 $31=1000 $32=0 $100=800.000 $101=800.000 $102=800.000 $110=1000.000 $111=1000.000 $112=1000.000 $120=50.000 $121=50.000 $122=50.000 $130=1000.000 $131=1500.000 $132=300.000 [VER:1.1g.20180813.Mega:] [OPT:VNM+,35,255]
Does anyone have any ideas? Tried reflashing and tried with a different computer to drive using BCNC not sure what to check next. Thanks
Have you tried flashing with OpenBuilds Control? Has great feedback interface can help you troubleshoot. Does soft limit work?
I've not looked into it, but will take a look tonight thanks. Not sure about soft limits, will try when I get home. Got a spare Arduino, may try flashing that with pure GRBL and running headless rather than the Mega 2560 version with Ramps Board.
Just to update, flashed a UNO with GRBL hooked up the pins and everything works fine. Tried a second Mega and Ramps with the Mega code same issue. Tried both on the bench, UNO works fine, Mega again fails. Not changed anything in the config files except define Ramps. Will probably just stick the UNO for now at least it works. Cheers
then you are asking in the wrong place (-: This points to a bug in the mega/ramps software so you need to create an issue report on github where you got it. That way the programmers will read about it, seems they do not read this forum >-:
Thanks I do agree but I had logged on the GitHub issue page before but nobody responded and with the sticky on here saying "as your GRBL Q's here" and that one the the lead dev's are monitoring and may respond thought it'd be the next best place to check. Either way, I'm now fully up and running just need to tidy a few bits up get the first cut on the go!
the RAMPS board is terrible (in terms of pin layout, very different to the optimized GRBL layout) and is not fully supported as an official GRBL target. The person who ported it is/was on github but if they are no longer watching then it is very hard to debug. Glad you got it going, I used my machine on and off all day yesterday, dunno how people live without one (-:
