greyltc
(Grey LTC)
February 28, 2017, 2:44pm
1
It’s cool to see carbide3d keeping up with supporting new grbl versions (1.1).
Does carbide3d maintain a fork of grbl somewhere?
What needs to be changed from the stock, publicly available grbl source on GitHub ( https://github.com/grbl/grbl ) to build a .hex for my Shapeoko 3 like the one provided here: carbide3d.com/carbideupdater/ , ( http://carbide3d.com/dl/v4/grbl.hex )
Presumably we need to change
#define DEFAULTS_GENERIC
to
#define DEFAULTS_SHAPEOKO_3
and uncomment
\\ #define PARKING_ENABLE
in grbl/config.h
Anything else?
robgrz
(Rob Grzesek (Carbide 3D))
February 28, 2017, 3:45pm
2
We don’t modify anything but the config file, which I’ll attach here.
Note that we do not test CM with any builds except the ones we release. If you change any of the config, or if Sonny makes any protocol changes, it won’t work reliably with CM.
config.h (42.3 KB)
3 Likes
greyltc
(Grey LTC)
February 28, 2017, 3:51pm
4
@robgrz
Wow! I surprised to see you’re using
#define DEFAULTS_GENERIC
Instead of those for the various shapeokos listed in https://github.com/gnea/grbl/blob/master/grbl/defaults.h
Is that because carbide motion sets all those defaults so you don’t have to worry about doing it in firmware?
robgrz
(Rob Grzesek (Carbide 3D))
February 28, 2017, 4:20pm
5
We have three different machines that we support with one hex file so we use CM to set the correct values.