$I
: [VER:1.1e.20161208:]
: [OPT:VZ]
@Arion_McCartney Thanks! I can see what’s wrong. You are running at 40kHz. Grbl supports up to 30kHz step frequencies. It can go slightly faster, depending on the job, but it can become unstable and produce weird results. Unfortunately, this is a hard limit of the 328p processor capabilities.
If you can adjust your micro stepping to be 40-80 steps/mm, you can run fast (or faster) and still have very good step resolution. If you can’t, reduce your maximum rates to get yourself around that 30kHz threshold.
@Arion_McCartney I can confirm this weirdness. And someone else just posted a similar issue. I’m working on this now to see I can isolate the cause. It doesn’t seem to be performance related, so your settings may be have been just fine.
@Sonny_Jeon , thank you for your response. I am a bit glad I am not the only one this is happening to. I thought I was going crazy for a while there! +Peter van der Walt, my apologies for using this forum for my issues that are clearly not LW issues. Again, I appreciate everyone’s help here.
+Peter van der Walt Lol. I wish you lived closer. I’d love to have a beer or three with you.
@Arion_McCartney Should have a fix in a few hours. Looks like I messed up some of the alarm reporting and flag clearing. Going to check a few times before pushing. Basically you’ll need to increase the pull-off distance and homing debounce delay. This was the error you were getting, but it wasn’t showing the right code.
+Peter van der Walt, Interesting to say the least! @Sonny_Jeon Awesome thank you for looking into this! I installed a new Uno and did decrease the pull off distance(10mm) and changed the parameters I mentioned earlier and all is working still. Anyways, because it is working I was able to cut some seasonal snowflakes with LW. Thank you all!
Thanks. Had to do 5 passes for 3mm plywood but it worked great.
@Arion_McCartney Looks great!
So, I just pushed a bug fix and made a new release. It should report the problem correctly and not enter an infinite loop.
Also, I would still lower your step/mm setting, if possible. Anything you do to lower the step frequency below 30kHz, will greatly improve Grbl performance. Particularly at high speeds and raster jobs.
@Sonny_Jeon , I will try to lower the steps/mm. I had to use 200 for 1/32 microsteps and 16 teeth timing pulley with gt2 belt. Only way I know how to lower the steps/mm is to lower the microsteps and/or change the teeth count on the timing gear pulley. Unless you know another way? Thanks!
What would be an adequate microstep? I just went for the max, haha!
1/8 micro steps should be fine. This will give you 50 steps/mm. Or 20 microns per step. More than enough precision. You’ll also likely to be go faster overall since you’ll have both more motor torque and Grbl will have extra cycles to execute gcode.
OK. Seems I can get my steps/mm down to 100 with 1/16 microsteps. @Sonny_Jeon , how do you calculate the 30kHz step frequency and rates to make sure I’m not running my machine too fast for the steps/mm I choose to run at?
@Sonny_Jeon , OK I’ll try the 1/8 microstep tomorrow. Thank you guys for your input. I’m learning and that’s awesome.
Try both. It really depends on the machine and if there is a resonance issue.
Step frequency = (max mm/min) * (step/mm) * (1/60 min/sec)