search

bdring / Grbl_Esp32

A port of Grbl CNC Firmware for ESP32
GNU General Public License v3.0
1.69k stars 529 forks source link

Errors with Arduino-ESP32 ver 2.0-... #1244

Open slresour opened 2 years ago

slresour commented 2 years ago

Errors with Arduino-ESP32 ver 2.0-... "arduinoWebSockets\src\WebSockets.cpp:42:10: fatal error: hwcrypto/sha.h: No such file or directory" "Grbl_Esp32-main\Grbl_Esp32\src\I2SOut.cpp:54:10: fatal error: FreeRTOS.h: No such file or directory"

With Arduino-ESP32 ver 1.8.6 no problems.

MitchBradley commented 2 years ago

We are no longer supporting Grbl_Esp32. The developers are now working exclusively on its replacement FluidNC. We had to made a lot of modifications on FluidNC to migrate to the new Arduino framework. There were several subtle problems to solve that resulted from deep changes in both the Arduino framework, the ESP-IDF core, and the xtensa compiler toolchain. We have no plans to backport those changes to Grbl_ESP32.

There are some tools to help you migrate your Grbl_ESP32 configurations to FluidNC.

Prior to making those changes, we also found a tricky bug in the core stepping code that causes random crashes while running GCode programs. That bug affected both Grbl_ESP32 and FluidNC. We fixed it in FluidNC but did not backport the fix to Grbl_ESP32. That is another reason to migrate.

slresour commented 2 years ago

In my opinion FluidNC is worse than Grbl-ESP32. For example: $$ $10=1 Ok. Is that all? How do I change the parameters by bluetuth?

Avataar120 commented 2 years ago

FluidNC is using YAML configuration file Everything is explained in the very detailed wiki https://github.com/bdring/FluidNC/wiki/FluidNC-Config-File-Overview

MitchBradley commented 2 years ago

FluidNC is much more configurable than Grbl_Esp32. The configuration is now in a hierarchical tree-structured file, whose parameters have descriptive names and human-readable values instead of meaningless number "names" and numerical-only values. Aspects of Grbl_Esp32 that required recompilation to change can now be configured with a text file, so that few users need to set up and maintain a compilation environment. Releases can be used as-is, with a one-click installation process that preserves the user's configuration.

To upload a YAML configuration file over Bluetooth, you can use FluidTerm - included in the release package - to connect via Bluetooth, then use FluidTerm's CTRL-U upload command to put your configuration file into the ESP32 FLASH filesystem.

Existing Grbl_Esp32 compile-time configurations (the Machine.h file) can be auto-converted to FluidNC YAML files by submitting a Grbl_Esp32 issue using the "Translate Machine.h File to FluidNC".