rrozestw / ESP32

grblHAL driver for ESP32

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

ESP32GrblDriver

A GrblHAL driver for the ESP32 processor. *** Preview version ***

How to build using ESP-IDF v4.3:

While this manual briefly describes basic build process on Linux OS, you can find more details as well as differences for building on other OS at this webpage:

https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/index.html#step-2-get-esp-idf

First you have to prepare esp-idf v4.3:

#Create directory and clone esp-idf into it:
mkdir -p ~/esp
cd ~/esp
git clone -b release/v4.3 --recursive --shallow-submodules https://github.com/espressif/esp-idf.git

#Prepare build environment and toolchain:
cd ~/esp/esp-idf
./install.sh
. ~/esp/esp-idf/export.sh

Then get the grblHAL driver code:

git clone -recursive git://github.com/grblHAL/ESP32
git pull --recurse-submodules
git submodule update --remote

Once you have ESP-IDF prepared, go back to grblHAL directory and copy grbl/* to drivers/ESP32/grbl/ in grblHAL repo as well as desired plugins into the respective folders. eg. plugins/spindle/* to drivers/ESP32/spindle/ and so on...

Modify settings in grbl/config.h and CMakeLists.txt as needed. Pin assignments and board specific config is in *_map.h files for each individual board.

Go into the drivers/ESP32/ directory and run idf.py build. This will build the firmware image which can be later flashed into ESP32 device.

Note that idf.py command is only available in terminal window which was previously configured using the . ~/esp/esp-idf/export.sh command.

After build is completed you will be instructed on how to flash firmware into the device. Typicaly you can use command similar to this: idf.py -p /dev/ttyUSB0 flash

Once flashing is complete, your CNC controller is ready to be configured and used.

Using Docker

If you're familiar with Docker, you can use it to build grblHAL in a self-contained environment without installing the complete toolchain on your system:

  • prepare and configure the codebase as described above
  • build with docker run -it --rm -v $(pwd):/grbl -w /grbl/drivers/ESP32 espressif/idf:release-v4.3 idf.py build
  • flash with docker run -it --rm -v $(pwd):/grbl --privileged -v /dev:/dev -w /grbl/drivers/ESP32 espressif/idf:release-v4.3 idf.py -p /dev/ttyUSB0 flash

Changelog/Notes:


NOTE: grbl/config.h or CMakeLists.txt may need modification before compilation. If needed an #error (with instructions) will be generated when compiling.


Update 2020-02-06: Added option for secondary serial input stream with input pin for switching on/off, indended for external MPGs. For verification!



Update 2020-02-02: Added board mapping files for Bart's v3.5 and v4 ESP32 boards. v4 is now the default mapping. For verification!


Update 2019-11-25: Added basic support for Luc's ESP3D-WEBUI with a backend written from scratch utilizing GrblHALs function pointer based API.

Currently missing is authentication and notification support, and possibly something else that I have overlooked. All GrblHAL settings are available from the GRBL configuration page, however the extended settings provided by GrblHAL does not show any help text. The ESP3D Settings page does not show settings not supported by this backend implementation.

This addon has not yet been tested connected to a machine - I challenge some brave souls to do that and report back by posting issues!

NOTE: Configuration has been simplified a bit, primarily change options in CMakeLists.txt to enable/disable. Enabled plugin code still has to be copied from the plugins folder though.


Update 2019-11-16: Added initial (and rather crude) UI for captive portal when WiFi is configured in APSTA mode. Ajax-based, no postbacks for updates. It works with Firefox on my laptop...


Update 2019-11-15: Added AP and APSTA WiFi options. Initial webserver support for reading/setting $-settings via JSON-messages. In APSTA WiFi mode webserver supports querying for available access points and connecting to selected, again via JSON messages. No UI for this yet though...

NOTE: IDF version 3.2 or later required for compilation if webserver is to be enabled.

IMPORTANT: Network setting-id's are changed and many are added. Any previous network settings will be lost if upgrading.


Update 2019-08-01: Now uses code for keypad and SD card options from common plugins. Added support for Trinamic TMC2130 plugin (currently via SPI <> I2C bridge).

NOTE: If plugins are to be used driver.h and CMakeLists.txt has to be updated. Details can be found in these files.

Update 2018-12-14: Prototype CNC BoosterPack "motherboard" up and running.

The board has an 8-bit I2C IO-expander and a micro SD card socket on board. Option to use EEPROM on BoosterPack for settings.

I have reorganized the HAL structure a bit so all drivers and the core grbl code must be published simultaneously. To aid this work I am contemplating making similar CNC BoosterPack "motherboards" for Arduino MKRZERO and Cypress CY8CKIT-059 (PSoC 5).

Complemented with the Trinamic TMC2130 version of the CNC BoosterPack silent stepping is within reach for all these processors...


Update 2018-11-08: I2C keypad interface done, usable for jogging and overrides.

Driver code published (still for preview), but not yet the changed core Grbl code required for compilation. No more work will be done on this driver until I receive dev kits and IO-expanders ordered from China.


Update 2018-11-07: RMT seems to be usable - pulse delay jitter is in the region of 100-200nS, pulse length jitter none. Pulse inversion ok as is pulse delay and length configurations. Running jobs from SD card ok, with M6 support for manual tool change (allows jogging).

One worry remains about ESP32 - what happens when there is a cache miss and code needs to be loaded from (serial) flash? CPUs suspended? It may take a long time (I've seen 300uS mentioned), but I have not found any documentation regarding this. Espressif documentation is not in the same class as for the other MCUs I am accustomed to...

Next step is to get I2C working, first for a keypad - then for an 8-bit IO-expander I have in order.

Updated code will be published later, changes in the core Grbl code related to reporting/streaming has to be verified first.


Work in progress, I do not currently have access to the hardware I need for complete testing so this is just a code preview. Parts of the code is commented out as I only have a TTGO WROOM module with less GPIO pins available than the target board(s).

I am hopeful that the RMT feature for autonomous step pulse generation will work out ok, I have seen postings on the net that suggest it should. Timing and jitter must be checked out with a scope. Does it work out then step pulse delay and inversion is supported, this with no CPU overhead.

Input signal debouncing and millisecond delay is implemented with the help of FreeRTOS timer tasks, and the previous delay in the stepper ISR for disabling the steppers at the end of a job is done with a callback from the millisecond timer. Also, I have added an option for ramped spindle speed changes.

Since an I2C bus is free I am tinkering with making a "motherboard" for my CNC BoosterPack, this has EEPROM on board for storing the settings - to avoid wearing out the flash. I am also considering adding support for a 4-bit I2C IO-expander to that (for coolant and spindle control), thus freeing up enough GPIO pins to allow a SD card and keypad to be added without losing any of the standard Grbl I/O.

Some time ago I started writing code for controlling Trinamic drivers - via a homemade I2C <> SPI bridge (MSP430) - maybe I will add that too...

Please note that this driver is not made using the Arduino IDE/framework, I am using Eclipse and CMake.


Credits:

index.htm.gz is Copyright (c) 2019 Luc Lebosse - from his ESP3D-WEBUI, I may have pulled a few lines from his backend code too.

dns_server.c is Copyright (c) 2019 Tony Pottier - from his ESP32 WiFi Manager

Snippets of code is extracted from Espressif ESP-IDF examples which are public domain.


2020-02-10

About

grblHAL driver for ESP32


Languages

Language:C 97.0%Language:CMake 1.9%Language:HTML 1.1%