Afaik, no support for that in the firmware.
Not all of the codes supported by GRBL are implemented in Maslow firmware, but there has been much talk recently of acceleration planning (or maybe I’ve just been reading lately about it on the forum from past posts). Either way, that is something that has been desired to get more in line with GRBL cnc compatibility. With the Maslow M2 using the Arduino Due, based on GRBL 1.1 (I think, but may be wrong) this is likely included. There is a significant time and sweat equity investment required to get the maslow cnc firmware 1.26 for the mega up to that for the “rest of us,” but it would be desirable and would mostly do away with the “sled not keeping up” error except when something is truly wrong.
Edit: I’ll add that I’d love to be a part of it, but i struggled through dynamics in college. Statics: no problem, but this motor kinematics is an animal I’ve not yet tamed.
I think ideally someone could get grbl-mega to work with maslow so people wouldn’t have to replace their hardware, but it’s not the end of the world if it does require new hardware.
It is for me - I had to wait over a month for customs clearance for my MakerMade kit.
Ouch… is there a off-the-shelf arduino-like microcontroller that would be compatible with the existing motor shield that doesn’t have customs issues?
That’s not the issue. Here (in Timor-Leste) customs duties are a significant part of government revenue, so everything goes slow through customs, especially if it’s something they’ve never seen before. Doesn’t matter what it is.
I honestly think it’s unlikely to see maslow firmware getting acceleration planning added to it. I don’t know of anyone working on it and it’s not trivial to do. So our best bet is to take grbl and make it work for Maslow’s motors and kinematics. @ldocull did it for an Arduino due, but to not sure if that can be ported to work on a mega… he used due-timer library. But someone may be able to figure out how to do it.
Absolutely.
Hi,
where can i post feature requests? Would it be possibe to have the “send gcode” input window detachable and not closing after sending gcode?
Post it on the GitHub repository (issues)
The detachable aspect will be challenging, but there are some smart programmers that might know a way. It certainly can be done in a separate browser window or perhaps by the additional of a fixed console section of the main screen.
If the send gcode window didn’t exit, could you just open a new browser window
and keep it open there rather than needing it to be detachable?