Brand new machine just got setup. I can move the machine all around with no issues and turn on/off the spindle in both directions from gSender. I thought I followed the videos correctly and the instructions, but no matter what size drawing I try to test with, I get alarm 10 immediately. I choose multiple xyz zeros just to see if it is a limit thing but same error. I was getting soft limit alarms and I now have those turned off.
I’m using Vcarve Pro 12 with the grbl mm post-processor. I believe I have the latest gSender (not the latest trial versions). I have my machine defined in Vcarve as 49x49. I tried creating a toolpath to drill holes in spoil board strip so I can attach them - error. I tried a smaller 12x12 inch work piece with a 6in diameter circle - error. Is there an article or video I may have missed?
is it possible an inductive sensor was triggered during the job to set off the hard limit alarm?
Either by the machine or something else going too close to the sensor?
I found this forum post about them activating randomly. They suggest de-activating hard limits…that was for a longmill though, not a good idea on an altmill in my opinion
I just finished putting together my Altmill this weekend and jumped all over designing stuff to route.
Every time I uploaded the file into gSender I got and error message telling me I was hitting hard limits.
When I went back to the Vetric software, I noticed that it always wanted to start my projects with an “offset” instead of starting at Zero/Zero. Once I started to remember to click on the zero offset checkbox, everything worked out fine going forward.
This wasn’t the complete solution but got me going in the right direction. When I went to the Firmware settings and looked at #10, all but 1 setting were off! I hit the reset for #10 and saved. I also did a $RST=$ in the console and that reset everything. Restarted everything and now all the alarms are gone, the “set Zero” buttons are now actually setting 0’s, and my simple program to cut a circle is working without error.
These posts also helped figure out what was going on …