So, I’m looking to clean up the configuration system of my fork; and I went looking at the various hardware options (both for the standard version of Grbl and Grbl-Mega), and I didn’t see any that actually could use the setup enabled by these:
“
#define DEFAULTS_GENERIC
#define CPUMAP2560_INITIAL
“
Did I miss something, or are these in fact unused in actual deployments of Grbl-Mega?
![[gnea/grbl-Mega Issue#1] $ command extentions](https://www.grblhal.com/wp-content/themes/gitphp/timthumb.php?src=https://www.grblhal.com/wp-content/themes/gitphp/assets/img/pic/9.jpg&h=110&w=185&q=90&zc=1&ct=1)
![[gnea/grbl-Mega Issue#3] ATMega16U2 virtual com port on ATMega2560](https://www.grblhal.com/wp-content/themes/gitphp/timthumb.php?src=https://www.grblhal.com/wp-content/themes/gitphp/assets/img/pic/11.jpg&h=110&w=185&q=90&zc=1&ct=1)
![[gnea/grbl-Mega Issue#4] Real-time adjustable feedrates](https://www.grblhal.com/wp-content/themes/gitphp/timthumb.php?src=https://www.grblhal.com/wp-content/themes/gitphp/assets/img/pic/7.jpg&h=110&w=185&q=90&zc=1&ct=1)
#1 – chamnit 于 2019-10-22
No. Generic defaults are intentionally extremely conservative so users can see it working without having to tune it. In most cases, it works for this purpose.