[grbl Issue#44] Grbl seems to grind to a halt with F commands >= 150 About GRBL HAL

Issue #44 | 状态: 已关闭 | 作者: jasin | 创建时间: 2011-12-20

Grbl seems to grind to a halt with F commands >= 150. I can re-create this issue as of right now 100% of the time. I am not sure if this is an issue with max stepping frequency or what. My lack of exactly how this works is limited.

Does this sound like another issue that you are aware of or should I try to narrow down the issue more and report back? What kind of problems will I run into if I just change all my F commands >= 150 to something smaller?

I should add that I am using an arduino uno 328p and grbl 0.6b.

#1 – chamnit 于 2012-01-04

Hi jasin. It seems that Simen has taken a hiatus and I’ve been continuing the development of grbl. Give my fork a try and see if this problem goes away. Use v0.7, which is stable. (v0.8 edge is alpha status) There have been many bug fixes since the last time Simen has worked on grbl, so there’s a good chance that the problem could have been fixed. Also, more often than not, the user interface seems to be more a cause for bugs than grbl itself. Try out the Python streaming script in my fork, rather than the Ruby one (we discovered that it has many problems as well recently.)

#2 – jasin 于 2012-01-04

Yes, thanks for replying. I did actually checkout your 0.7V and it solved all the issues I was having. I should have posted back but I got busy and forgot I even submitted a bug report.

I will now close this bug and let you continue your great work.

原始Issue: https://github.com/grbl/grbl/issues/44

评论 (2)