-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiling help #9
Comments
Here you go. 3, 4 and 5 axis with planning buffer set to 1024. 30K limit does not exist in grblHAL. |
Thanks, I really appreciate it, any idea about the ioports.h error i would really like to understand why its not working for me, also if grblhal does not have step rate limits why is it still defined in the config file // Sets the maximum step rate allowed to be written as a Grbl setting. This option enables an error |
OK, forgot about that. Never had that enabled for any of my builds. Never any reason to do so - I can get to 400 kHz step rate on the teensy. I'm not sure why you are seeing the ioports error. could be a mix and match thing. I built with the master branch and keep it pure. If you download the test over the master branch (or the other way around) you might wind up with left over files. The arduino IDE by default will try to compile everything. |
Worked like a charm !!! the laser is up and running. |
I've been fighting with this for a few weeks, and wonder if you could just make a precompiled version of the 3axis for lasers. I need the buffer changed to 1024 so I can move faster I have a 60W laser so I can move a bit faster than the LED lasers. Ive tried everything to compile, Ive used your guide but ran into the same thing as others with different/missing folders. I tried compiling using the most current Grblhal build and instructions and get an error ( no IOport.h file) but can't find where or what is even calling for it. I just need a 3 axis with homing switches (No Z tho) and the buffer set to 1024 and the 30k step limit removed.
Thanks
The text was updated successfully, but these errors were encountered: