ESP3D 3.0 Status

[luc-github]

migration from #239
What is the plan ? Do what was not done in 2.0/2.1 😉

1 - Nextion Screen support ((ESP3D + Nextion FW) (cancelled)
2 - M408 support according target FW support(On hold because dropped by Marlin)
3 - Reprap support (On hold)
4 - MKS complete support (done 👍 )
5 - ESP3D as Library as part of main board FW (eg Marlin) Code is emmbedded in Marlin ESP3DLib or GRBL_ESP32 firmware so will be a porting when 3.0 stand alone is done
_6 - UI improvement :

• Follow disconnection in authenticate page (WebUI + ESP3D) (done 👍 )
• add toshiba flash air support (WebUI) (done 👍 )

7 - Add ethernet support for ESP32 (like olimex)(done 👍 )
8 - Add optional translation file on flash FS for oled ESP3D message like (connected, update, etc...)(On hold)
9 - Monitor temperatures on Oled in autonomous way (no web browser connected)(moved to ESP3D-TFT : https://github.com/luc-github/ESP3D-TFT)
10 -Embedded Host support for ESP32 (on hold}
11 - New webUI :1:
12 - Fix issue with ESP8266 and Async Webserver and big Serial flow (on hold as 3.0 is planed to be sync only)(On hold)
13- Put all GCODE in preferences file for easier customization (WebUI)
14 - Heart beat generation to help UI to known if ESP3D is still connected or not (already implemented in GRBL-ESP32 and Marlin-ESP32 but disabled as buggy) (WebUI) (done 👍 )
15 - Fat FS support as option for SPIFFS for ESP32 , LittleFS as option for SPIFFS ESP8266 (done 👍 )
16 - Serial Bluetooth for ESP32 (done 👍 )
17 - Macro autostart (from FS done 👍 ) (from SD : TBD)
18 - Date Time on FS (SPIFFS / FAT / LittleFS) for ESP32 as ESP8266 (done 👍 )
19 - Add LittleFS support for ESP32 (done 👍)
20 - Buzzer support (done 👍)
21 - Push Notifications (Pushover / email) (done 👍)
22- Both way websocket communication (done 👍)
23 - Add auto notifications like #351 (done 👍)
24- USB host support using arduino usb host shield (https://github.com/felis/USB_Host_Shield_2.0) (on hold)
25 - Embedded camera support (done 👍)
26 - SD access with time support: Native (all) / SDFat (all) / SDIO (esp32 only) (done 👍)
⚠️ Note: this not Printer SD so printer has no access to it, it is for host feature, storage purpose or FW flash purpose.
27 - TFT touch (moved to ESP3D-TFT: https://github.com/luc-github/ESP3D-TFT)
28 - USB Disk support (using CH376s) (on hold)
29 - FTP Server (done 👍 )
30 - telegram notification support (done 👍 )
31 - BTT tft support (on going)
32 - WebDav server (done 👍 )

[luc-github]

About file upload, to clarify and avoid recurrent questions, here is what the 3.0 should support in beta, this is an under going and planned work, implementation should follow list order.

UPLOAD_DIRECT_SD (implemented)
the SD is directly connected to ESP board but printer has no access to it
e.g: ESPCAM32 board

UPLOAD_SHARED_SD (implemented)
the SD is shared between ESP and printer using hardware switch
e.g: Panucatt wifi back pack and other related devices

UPLOAD_SERIAL_SD (implemented in 2.1 but not available yet in 3.0)
the access to SD is done using M28/M29 protocol
e.g: Default 3D printer protocol

UPLOAD_FAST_SERIAL_SD (implemented for MKS)
the access to SD is done using an additional pin to let printer FW / TFT FW know this is an upload
e.g: MKS TFT / MKS Robin
Note: it is currently limited to MKS TFT and boards using Marlin as no one else implemented this protocol yet

UPLOAD_FAST_SERIAL_USB (implemented for MKS)
the access to USB TFT port is done using an additional pin to let TFT FW know this is an upload
e.g: MKS TFT
Note: it is currently limited to MKS TFT as no one else implemented this protocol yet

UPLOAD_DIRECT_USB (not started yet, and may be delayed to 3.1, waiting for hardware setup)
the access to direct USB port using CH376s chip
Note: CH376S support is not yet implemented but definitly planned

[MarSoft]

There is a mention here that UPLOAD_FAST_SERIAL_SD is implemented for MKS but should work on boards using Marlin. But I could not find anything related in Marlin's code or repo. Did I miss something, or is there a typo here? If marlin supports this feature then how to enable it?

[luc-github]

MKS Robin board , the code in Marlin is in
https://github.com/makerbase-mks/Mks-Robin-Nano-Marlin2.0-Firmware/blob/master/Marlin/src/lcd/extui/lib/mks_ui/wifi_module.cpp

it is also suported for mks tft with wifi module

[luc-github]

Shared SD and direct SD support now flash from SD for FW binary (esp3dfw.bin) and FS image (esp3dfs.bin)
also the file esp3dcnf.ini allows to configure ESP3D settings at start
Once processed all files are renamed .ok if success .bad if update failed

[luc-github]

I am currently reviewing the MKSWIFI FW (https://github.com/luc-github/MKS-WIFI/tree/debug) to understand it well and add support in ESP3D - once done - I will have a good understanding on how to had same fast upload protocol in ESP3D for other boards than MKS also

[luc-github]

MKS WIFI fast upload is now
implemented - need to fine tune some part but it is working : #523

[luc-github]

LittleFS for ESP32 is now implemented

[luc-github]

WebDav server is now implemented

[hyzx86]

Hi Luc，

Are there any plans to use ESP32 as a host computer?
It can reads the gcode file form the ESP32 SD card and sends instructions to the printer

[hyzx86]

[luc-github]

pronterface and repetier support it without virtual com

[gerthalberg]

I would say, the serial bridge is just the absolute lowest layer to just get the connection - after that the fun starts.

[hyzx86]

So, finally, I just want to make sure... Is there an easy way to remotely upload or print on ESP3D 3.0?😊

[luc-github]

print commands are visible when you list printer SD files
about upload files to printer - it is only implemented for Mks Boards and Wifi Backpack boards
status about upload is just few messages above this one
#540 (comment)

[luc-github]

Still busy with WebUI and now changing the CI from travis to github action
Next feature (with bug fixes) will be the #575 as this is a critical part I think
the SPI study of reprap implementation is also planed but standard serial support must be added first in webUi

[fkemps]

Hello,

Topic: ESP SD-card storage for webbrowser based printing.
I added SD-card to my ESP32 with 32GB per https://github.com/ardyesp/ESPWebDAV Instructions.

How can I check on ESP3D 3.0 (FW 3.0.0.a95, WebUI 3.0.0.85) that the storage is available?
I don't see any indication on "About ESP3D" page regarding the ESP32-SD-card storage.

Connection to http://<3d-printer>:8181/ give me "Not found, URI: / Method: GET".
MacOS Finder gives me authentication pop-up, where guest doesn't work.

I like to upload GCODE and print via WebInterface as I read there's limitation to print from 3Dprinter (Ender3 v2) which is no problem.

[luc-github]

the shared sd method of https://github.com/ardyesp/ESPWebDAV is not supported, it is same as #454

[luc-github]

GRBL_ESP32 requested to be able to have no radio mode as fall back option instead of AP mode if STA is failing to connect.
I will add a setting for selecting fallback option:
1 - OFF (No Radio)
2 -WIFI-AP (AP mode = default)
3 - BT (if BT is enabled)

[ESP104]<OFF / WIFI-AP / BT> will allow to select option

same in esp3dcnf.ini

#Station fallback mode BT, WIFI-AP, OFF
sta_fallback  = WIFI-AP

It will be implemented this week end I think

Edit: implemented with several fixes also

[luc-github]

About file upload, to clarify and avoid recurrent questions, here is what the 3.0 should support in beta, this is an under going and planned work, implementation should follow list order (the status has ben updated since last time)

UPLOAD_DIRECT_SD (implemented)
the SD is directly connected to ESP board but printer has no access to it
e.g: ESPCAM32 board

UPLOAD_SHARED_SD (implemented)
the SD is shared between ESP and printer using hardware switch
e.g: Panucatt wifi back pack and other related devices

UPLOAD_SERIAL_SD (implemented in 2.1 but not available yet in 3.0)
the access to SD is done using M28/M29 protocol
e.g: Default 3D printer protocol,
It is too slow and ask a lot work depending FW, also now this upload is almost always corrupted when using Serial TFT so it is pretty useless for most of people, so I won't implemented it.
I prefer to spend dev time on #575 instead, to have real benefit, and no more data corruption due to external queries

UPLOAD_FAST_SERIAL_SD (implemented for MKS)
the access to SD is done using an additional pin to let printer FW / TFT FW know this is an upload
e.g: MKS TFT / MKS Robin
Note: it is currently limited to MKS TFT and boards using Marlin as no one else implemented this protocol yet

UPLOAD_FAST_SERIAL_USB (implemented for MKS)
the access to USB TFT port is done using an additional pin to let TFT FW know this is an upload
e.g: MKS TFT
Note: it is currently limited to MKS TFT as no one else implemented this protocol yet

UPLOAD_DIRECT_USB (not started yet, and may be delayed to 3.1, waiting for hardware setup)
the access to direct USB port using CH376s chip
Note: CH376S support is not yet implemented but definitly planned

[luc-github]

Some update as I did not for a while and got request to give some visibility :
I am still working on ESP3D V3 I got some delay due to my moving and personnal issue in November
I am currently on porting ESP3DLib using ESP3D V3 code https://github.com/luc-github/ESP3DLib/tree/2-0
Doing that I actually improve also ESP3D V3 code which I will update once porting is done, I recently worked on refactoring of the shared SD part which lead me to a lot of change that will also affect webUI 3.0

Because it will be difficult to manage ESP3D V3 alpha code with Webui V3 and several change ESP3D code used by ESP3DLib that will be merged back to ESP3D V3 - I will use the rewrite of webui 3.0 as base code for the change of ESP3DLib and new ESP3D V3

Indeed all [ESPXXX] are rewriten to send plain text response and JSON format using json=YES and also I am trying to refactoring the FS listing to have listing code in one location instead of several

Which will make the output more consistent

To sum up:

• ESP3D V2.x use WebUI v2.x
• ESP3DLib V1 use WebUI v2.x
• ESP3D V3 use WebUI V3
• ESP3DLib V2/3 use WebUI rewrite (https://github.com/luc-github/ESP3D-WEBUI/tree/3.0-rewrite)

once ESPLib V2/3 will be done code will be merged to ESP3D V3 and so the rewrite of WebUI V3 will be merged to current WebUI V3

It looks messy for the moment I appologize but it is the easy way to keep current existing code working until update is ready - thank you for your patience ^_^

[luc-github]

Webdav is now working as expected with ESP3D V3, the screen is made on ESP3DLib but it is same in ESP3D and shared/direct SD connection

Still need to implement same kind of code update for FTP server and it should be good

[luc-github]

FTP server code is now updated to support new SD access API and so globalFS

Note: number of connection is still limited to 1

[luc-github]

The lastest esp32 core bring some change and I need to update display libraries - so I will take opportunity to rewrite the display module to reorganize the code and simplify the initial configuration

[luc-github]

I just did release of alpha2 which is the refactoring version and the new code base

[luc-github]

@Sawurai80 this is a status thread- if you have any issue please open a new ticket

[luc-github]

Clarification on SD Support (again)

• UPLOAD_DIRECT_SD (implemented)
  the SD is directly connected to ESP board but printer has no access to it
  e.g: ESPCAM32 board

• UPLOAD_SHARED_SD (implemented)
  the SD is shared between ESP and printer using hardware switch
  e.g: Panucatt wifi back pack and other related devices

• UPLOAD_SERIAL_SD (implemented in 2.1 but not more available in 3.0)
  M28/M29 protocol is too slow and buggy with external queries

• UPLOAD_FAST_SERIAL_SD (implemented for MKS)
  the access to SD is done using an additional pin to let printer FW / TFT FW know this is an upload
  e.g: MKS TFT / MKS Robin
  Note: it is currently limited to MKS TFT and boards using Marlin as no one else implemented this protocol yet

• UPLOAD_FAST_SERIAL_USB (implemented for MKS)
  the access to USB TFT port is done using an additional pin to let TFT FW know this is an upload
  e.g: MKS TFT
  Note: it is currently limited to MKS TFT as no one else implemented this protocol yet

• UPLOAD_DIRECT_USB (not started yet, and may be delayed to 3.1, waiting for hardware setup)
  the access to direct USB port using CH376s chip
  Note: CH376S support is not yet implemented but definitly planned

• Possible enhancement for Shared SD
  Some board (BTT Octopus ) share SD pins with ESP => I need to check if sharing protocol could be used on them => No

[luc-github]

Serveral bugs have been fixed for the SD Pro WiFi card thanks @y2kdread

I have refactoring the Time module and totaly rewrote the Webdav Module based on code I did for ESP3D-TFT.
This version of Webdav server is more oriented for ESP3D needs instead of beeing a general Webdav support.

For example it does not support PROPFIND with depth as infinity, but just do a max of Depth = 1
Also it is announcing itself as Dav 1 protocol, because we do not need LOCK/UNLOCK feature, neither really the PROPATCH feature.

Unfortunaly Microsoft Windows does not respect Webdav RFC and use it own properties and do not care about Dav=1, neither of allowed methods list announced, and still try to use LOCK/UNLOCK/PROPATCH feature just for uploading a file...
So even ESP3D webdav server do not announce it allows these method, it simulate them enough to allow a file upload from Microsoft Windows.

I will continue the porting from ESP3D-TFT code of at least 3 things:

1 - Refactorization of setting validation - the ESP3D-TFT has an API for that and I will add it to ESP3D (no visible impact but consistency in code across project and also some code simplification / readibility I think)

2 - Add the sticky authentication feature like in ESP3D-TFT for commands: when you use the pwd=in one command, the following won't need it anymore, same if you change to user level, that should apply to serial / telnet / websocket => TBC

3 - Streaming service from ESP3D- TFT (ongoing work)

I am also reviewing the [ESPXXX] docs by doing a document for each one - that one take time because I do not like to write docs orz... and there are many ~100, the doc https://github.com/luc-github/ESP3D/blob/3.0/docs/espXXX.md once done will be splitted and uploaded to esp3d.io

[luc-github]

Refactorization of setting validation is now done 😺

Working now on point 2 and preparing for point 3:

When ESP3D-TFT use internal message class to transfert data that contain the orgin (client which send the message) and target (destination of this message) allowing easy filtering and message transportation.

ESP3D currently only define and use target client. and has instead an hack in process function that allow to define only in the function: to only target the client X and to ignore client Y, and this is not following the message itself once function is passed.

process(uint8_t* sbuf, size_t len, ESP3DOutput* output, level_authenticate_type auth = LEVEL_GUEST, ESP3DOutput* outputonly = nullptr, uint8_t outputignore = 0);

So I will rewrite the ESP3DOutput class to ESP3DMessage to include origin and target, and also review all the dispatching process according these 2 elements.
Hopefuly it should simplify the dispatching of messages and make the dispatch ready for Streaming service, because it should know these 2 elements to process answers / response properly

The implementation will be different than ESP3D-TFT because of ESP8266 and to avoid to break everything - but the concept should be same

[luc-github]

Small update but huge impact:
After reviewing code of ESP3D internal messaging (aka ESP3DOutput) I realize the ESP3D-TFT API is really better and simpler, no need to have each client be a Print base object with many read / write functions that are just translators and not actually used.

So actually I am now breaking everything and simplify the whole system => TBC, but it will stay sync system unlike ESP3D-TFT.
Also no worry about current code, that is in devt branch which will only merged when validated, and replicate same as current behavior without any regression issue,
So I will definitly need some weeks to make all robust as expected and hopefuly simplify code a lot

[luc-github]

The messaging rewrite is ongoing - the painful task is currently to review each ESP command one by one to use new API which is currently only implemented on Serial, once all commands are updated I will update each clients and finally review the authentication part
The rewrite completion should need less than 2 weeks depending of my free time, but new API simplify a lot and seems beeing faster on ESP32 =>TBC I need also to see the end to test on ESP8266 but so far so good 😺

[luc-github]

All ESP command have been reviewed and new API messaging have been implemented on all clients
The code simplification is important and it also decrease the final footprint of 14 KB using default configuration.h which is not bad

Now I will review the authentication part and do test on 3 configs

• standard ESP32
• standard ESP8266
• ES8266 for MKS Robin

If ok I will do the porting of ESP3DLib using the new code and latest release of Marlin at this moment

[luc-github]

Sticky authentication is now implemented and due to rewrite of internal messaging the credential for each feature and command have been simplified to make the porting faster
I have wrote a quick doc to sum up authentication: https://github.com/luc-github/ESP3D/blob/Refactoring-internal-clients/docs/authentication.md that will be added to http://esp3d.io

So currently user and admin have same level, I need to update that part.

Here the scope of right for each authentication level:

Feature	not authenticated	guest	user	admin
Web Interface	No	No	Yes	Yes
Telnet	No	No	Yes	Yes
WebSocket	No	No	Yes	Yes
WebDav	No	No	Yes	Yes
Bluetooth	No	No	Yes	Yes
ESP0	Yes	Yes	Yes	Yes
ESP100	No	No	Get/Set	Get/Set
ESP101	No	No	Set	Set
ESP102	No	No	Get/Set	Get/Set
ESP103	No	No	Get/Set	Get/Set
ESP104	No	No	Get/Set	Get/Set
ESP105	No	No	Get/Set	Get/Set
ESP106	No	No	Set	Set
ESP107	No	No	Get/Set	Get/Set
ESP108	No	No	Get/Set	Get/Set
ESP110	No	No	Get/Set	Get/Set
ESP111	No	No	Get	Get
ESP112	No	No	Get/Set	Get/Set
ESP114	No	No	Get/Set	Get/Set
ESP115	No	No	Get/Set	Get/Set
ESP120	No	No	Get/Set	Get/Set
ESP121	No	No	Get/Set	Get/Set
ESP130	No	No	Get/Set	Get/Set
ESP131	No	No	Get/Set	Get/Set
ESP140	No	No	Get/Set	Get/Set
ESP150	No	No	Get/Set	Get/Set
ESP160	No	No	Get/Set	Get/Set
ESP161	No	No	Get/Set	Get/Set
ESP170	No	No	Get/Set	Get/Set
ESP171	No	No	Get	Get
ESP180	No	No	Get/Set	Get/Set
ESP181	No	No	Get/Set	Get/Set
ESP190	No	No	Get/Set	Get/Set
ESP191	No	No	Get/Set	Get/Set
ESP200	No	No	Get/Set	Get/Set
ESP201	No	No	Get/Set	Get/Set
ESP202	No	No	Get/Set	Get/Set
ESP210	No	No	Get/Set	Get/Set
ESP214	No	No	Set	Set
ESP215	No	No	Set	Set
ESP220	No	No	Get	Get
ESP250	No	No	Set	Set
ESP290	No	No	Set	Set
ESP400	No	No	Get	Get
ESP401	No	No	Set	Set
ESP402	No	No	Get/Set	Get/Set
ESP410	No	No	Get	Get
ESP420	No	No	Get	Get
ESP444	No	No	Set	Set
ESP450	No	No	Get	Get
ESP500	Get/Set	Get/Set	Get/Set	Get/Set
ESP510	No	No	Get/Set	Get/Set
ESP550	No	No	No	Get/Set
ESP555	No	No	Get/Set	Get/Set
ESP600	No	No	Set	Set
ESP610	No	No	Get/Set	Get/Set
ESP620	No	No	Set	Set
ESP700	No	No	Set	Set
ESP701	No	No	Get/Set	Get/Set
ESP710	No	No	Set	Set
ESP715	No	No	Set	Set
ESP720	No	No	Get	Get
ESP730	No	No	Get/Set	Get/Set
ESP740	No	No	Get	Get
ESP750	No	No	Get/Set	Get/Set
ESP780	No	No	Get	Get
ESP790	No	No	Get/Set	Get/Set
ESP800	No	No	Get/Set	Get/Set
ESP900	No	No	Get/Set	Get/Set
ESP901	No	No	Get/Set	Get/Set
ESP910	No	No	Get/Set	Get/Set
ESP930	No	No	Get/Set	Get/Set
ESP931	No	No	Get/Set	Get/Set
ESP999	No	No	Set	Set

Initially user can only read (get) settings but not change them, can use any feature without be able to change any configuration,
admin can change any settings
I plan to apply same

Any feedback / suggestions for changes on above table ?

[luc-github]

implemented as follow:

Feature	not authenticated	guest	user	admin
Web Interface	No	No	Yes	Yes
Telnet	No	No	Yes	Yes
WebSocket	No	No	Yes	Yes
WebDav	No	No	Yes	Yes
Bluetooth	No	No	Yes	Yes
Upload	No	No	Yes	Yes
Update	No	No	No	Yes
ESP0	Yes	Yes	Yes	Yes
ESP100	No	No	Get	Get/Set
ESP101	No	No	No	Set
ESP102	No	No	Get	Get/Set
ESP103	No	No	Get	Get/Set
ESP104	No	No	Get	Get/Set
ESP105	No	No	Get	Get/Set
ESP106	No	No	Set	Set
ESP107	No	No	Get	Get/Set
ESP108	No	No	Get	Get/Set
ESP110	No	No	Get	Get/Set
ESP111	No	No	Get	Get
ESP112	No	No	Get	Get/Set
ESP114	No	No	Get	Get/Set
ESP115	No	No	Get	Get/Set
ESP120	No	No	Get	Get/Set
ESP121	No	No	Get	Get/Set
ESP130	No	No	Get	Get/Set
ESP131	No	No	Get	Get/Set
ESP140	No	No	Get	Get/Set
ESP150	No	No	Get	Get/Set
ESP160	No	No	Get	Get/Set
ESP161	No	No	Get	Get/Set
ESP170	No	No	Get/Set	Get/Set
ESP171	No	No	Get	Get
ESP180	No	No	Get	Get/Set
ESP181	No	No	Get	Get/Set
ESP190	No	No	Get	Get/Set
ESP191	No	No	Get	Get/Set
ESP200	No	No	Get/Set	Get/Set
ESP201	No	No	Get/Set	Get/Set
ESP202	No	No	Get	Get/Set
ESP210	No	No	Get	Get/Set
ESP214	No	No	Set	Set
ESP215	No	No	No	Set
ESP220	No	No	Get	Get
ESP250	No	No	Set	Set
ESP290	No	No	Set	Set
ESP400	No	No	Get	Get
ESP401	No	No	No	Set
ESP402	No	No	Get	Get/Set
ESP410	No	No	Get	Get
ESP420	No	No	Get	Get
ESP444	No	No	Set(only RESTART)	Set
ESP450	No	No	Get	Get
ESP500	Get/Set	Get/Set	Get/Set	Get/Set
ESP510	No	No	Get	Get/Set
ESP550	No	No	No	Get/Set
ESP555	No	No	Get/Set	Get/Set
ESP600	No	No	Set	Set
ESP610	No	No	Get	Get/Set
ESP620	No	No	Set	Set
ESP700	No	No	Set	Set
ESP701	No	No	Get/Set	Get/Set
ESP710	No	No	No	Set
ESP715	No	No	No	Set
ESP720	No	No	Get	Get
ESP730	No	No	Get/Set	Get/Set
ESP740	No	No	Get	Get
ESP750	No	No	Get/Set	Get/Set
ESP780	No	No	Get	Get
ESP790	No	No	Get/Set	Get/Set
ESP800	No	No	Get/Set	Get/Set
ESP900	No	No	Get/Set	Get/Set
ESP901	No	No	Get	Get/Set
ESP910	No	No	Get/Set	Get/Set
ESP930	No	No	Get	Get/Set
ESP931	No	No	Get	Get/Set
ESP999	No	No	No	Set

[luc-github]

everything is.now integrated and sync with ESP3D-TFT but gcode streaming, need to test MKS protocol has no regresssion issue then I will merge devt branch and update ESP3DLib 3.0 accordingly

[luc-github]

MKS robin tested and so far so good
Next step is testing porting for ESP3DLib V3 with latest MArlin, latest release is https://github.com/MarlinFirmware/Marlin/releases/tag/2.1.2.1 so I will use it as a base for my fork

[luc-github]

Refactoring is now pushed to in 3.0 branch for more tests - feel free to feedback

[luc-github]

In same spirit of ESP3D-TFT:https://esp3d.io/esp3d-tft/v1.x/hardware/index.html I have started to list all boards I have tested, this is an ongoing process, let me know if need more data, I am starting with 2.x and will also do 3.0 : https://esp3d.io/esp3d/v2.x/hardware/index.htm.
2.x should be limited to esp8266 and esp32 nodem chips where 3.0 will cover all chips / boards

[luc-github]

I have replaced the lua wrapper (https://github.com/luc-github/ESP8266-Arduino-Lua) by a new version developed from scratch by me (https://github.com/luc-github/EspLuaEngine) the module is also now integrated
Because I think this feature need to have independant task and I want to keep simple - the feature is limited to ESP32/S2/S3/C3/etc... in ESP3D, the library itself has no limitation
That increase the fw footprint of around 100KB, I will review the impact on partitions size, I plan to prepare optimized partitions:

Flash Size	Environment	App Partition Size	SPIFFS Size	Coredump Size
4 MB	Arduino	1.89 MB (0x1D0000)	250 KB (0x3E800)	64 KB (0x10000)
4 MB	ESP-IDF	1.94 MB (0x1E0000)	250 KB (0x3E800)	N/A
8 MB	Arduino	2.5 MB (0x280000)	2.88 MB (0x2E0000)	64 KB (0x10000)
8 MB	ESP-IDF	2.5 MB (0x280000)	2.94 MB (0x2F0000)	N/A
16 MB	Arduino	2.5 MB (0x280000)	10.88 MB (0xAE0000)	64 KB (0x10000)
16 MB	ESP-IDF	2.5 MB (0x280000)	10.94 MB (0xAF0000)	N/A
32 MB	Arduino	2.5 MB (0x280000)	26.88 MB (0x1AE0000)	64 KB (0x10000)
32 MB	ESP-IDF	2.5 MB (0x280000)	26.94 MB (0x1AF0000)	N/A

That said before finalize the partition size, I will work on moving to ESP32 3.0.3 core which is breaking code vs 2.X.

The platformio team stop support after 2.0.17 as a result of business discussions with Espressif - it has been months now and there is an
alternative thanks to community and active members : https://github.com/Jason2866/platform-espressif32
Give https://github.com/pioarduino/platform-espressif32

So I will use it a base and resume the ESP3D porting to support ESP32 arduino core 3.0.3 - which should also include some new features, but these will depend of the hardware I have in hand.
That will bring several code update and also toons of test,
Coming month will be busy,
TBC

[luc-github]

during the tests I have found some issues with lua and some glitches in messages API that seems not fully thread safe
I have fixed the issues on my side but did not pushed the fixes yet, should be done end of the week , it will be done on idf-5.x branch

[luc-github]

Lua Update done / Message API update done , time for tests orz....

Ok : ✅
Limited: ✴️
Not Ok: ❌
Under Test: 👀

Board	Arduino	PIO	Notes
ESP8266	✅ 3.0.4	✅51.03.04	SPI ✅
ESP32	✅ 3.0.4	✅ 51.03.04
ESP32+SD	✅ 3.0.4	✅51.03.04	Native ✅ / SDFat ✅
ESP32 + Cam	✅ 3.0.4	✅51.03.04	SDIO ✅
ESP32 + Oled	✅ 3.0.4	✅ 51.03.04	SPI 135x240 ST7789V IPS screen
ESP32 + Ethernet	✅ 3.0.4	✅51.03.04
ESP32 C3	✅ 3.0.4	✅51.03.04
ESP32 C6	✅ 3.0.4	✅51.03.04	WebSocket need a patch Links2004/arduinoWebSockets#907
ESP32 S2	✅ 3.0.4	✅51.03.04
ESP32 S3	✅ 3.0.4	✅51.03.04
ESP32 S3 + Cam	✅ 3.0.4	✅51.03.04	SDIO ✅ / SPI ✅

Note

The littleFs version is different and tend to crash and go to dead loop if it is not setup in clean partition, so before flashing do a full flash erase

[luc-github]

I have issue with SD support , looks ok with Native SD SPI ( I did not checked SDIO yet) but got WDT fired with SDFat2 when listing files, even with latest version 2.2.3, using 2.2.3 sample of listing directory there is no issue , so issue should be in ESP3D abstraction layer
Edit : Fixed by simplifying the getState

I all case WDT seems more sensitive in 3.0.4 , I have a couple of E (337) task_wdt: delete_entry(233): task not found that I need to investigate, C6 especially is firing WDT event having reset or at boot I get : E (337) task_wdt: delete_entry(233): task not found - need to investigate
Edit: C6 seems do not care about esp_task_wdt_reset() use vTaskDelay(1) instead to feed the WDT and it is ok

[luc-github]

Tests are now done - several fixes / some code simplifications / libraries updates

I need to update the configurator , update esp3d.io docs, to add ESP32-C6 support and documentation and also missing settings in platformio.ini

Once done I will push PR to integrate 5.1.4 in 3.0 branch

Should be done soon hopefully

[luc-github]

For reference this the typical boot of ESP32 which flash was erased before flashing

1 - boot after flash

Writing at 0x00173802... (100 %)
Wrote 1462080 bytes (937804 compressed) at 0x00010000 in 21.1 seconds (effective 553.5 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

Please build project in debug configuration to get more details about an exception.
See https://docs.platformio.org/page/projectconf/build_configurations.html


--- Terminal on COM7 | 115200 8-N-1
--- Available filters and text transformations: colorize, debug, default, direct, esp32_exception_decoder, hexlify, log2file, nocontrol, printable, send_on_enter, time
--- More details at https://bit.ly/pio-monitor-filters
--- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H
ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x1b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4604
ho 0 tail 12 room 4
load:0x40078000,len:15468
load:0x40080400,len:4
ho 8 tail 4 room 4
load:0x40080404,len:3180
entry 0x400805b8
ets Jun  8 2016 00:22:57

2 - Reset and reboot due to ESP3D reset EEPROM settings
The reset raise several esp_task_wdt_reset(763): task not found I am guessing it is due to formating

rst:0xc (SW_CPU_RESET),boot:0x1b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4604
ho 0 tail 12 room 4
load:0x40078000,len:15468
load:0x40080400,len:4
ho 8 tail 4 room 4
load:0x40080404,len:3180
entry 0x400805b8
E (10047) esp_littlefs: ./managed_components/joltwallet__littlefs/src/littlefs/lfs.c:1369:error: Corrupted dir pair at {0x0, 0x1}

E (10048) esp_littlefs: mount failed,  (-84)
E (10052) esp_littlefs: Failed to initialize LittleFS
E (20519) task_wdt: esp_task_wdt_reset(763): task not found
E (20541) task_wdt: esp_task_wdt_reset(763): task not found
E (20541) task_wdt: esp_task_wdt_reset(763): task not found
E (20542) task_wdt: esp_task_wdt_reset(763): task not found
E (20546) task_wdt: esp_task_wdt_reset(763): task not found
E (20551) task_wdt: esp_task_wdt_reset(763): task not found
E (20572) task_wdt: esp_task_wdt_reset(763): task not found
E (20573) task_wdt: esp_task_wdt_reset(763): task not found
E (20574) task_wdt: esp_task_wdt_reset(763): task not found
E (20578) task_wdt: esp_task_wdt_reset(763): task not found
E (20583) task_wdt: esp_task_wdt_reset(763): task not found
E (20588) task_wdt: esp_task_wdt_reset(763): task not found
M117 Setup wifi 
M117 AP SSID: 'ESP3D' is started and protected by password (setup mode) 
M117 192.168.0.1 
M117 192.168.0.1 

3 - After new restart all is ok

eׁ�]
!��:0�LB=]�RO�%UMQe,���i0xL,BA%�F�*�e1MH_��Q%
��˥��ip��bSPR��x�YC�,k�E��:0��b�}��v:��0,dߖ�i0x�b�����i0��bB�}�rv���0,w}��v:���C!닕�DI�      �o�-"�v:�H��+�i0�&֙00&bb�n����
끰���l�L&���� 4�!�+��0x4�7����l�K��46j
�+�i0x���4�bb�n�S�8 t�Z
���:��0�0�b╹i31�j
en���0x���bj
M117 Setup wifi 
M117 AP SSID: 'ESP3D' is started and protected by password (setup mode) 
M117 192.168.0.1 
M117 192.168.0.1 

[luc-github]

Doing test on ESP32 + ethernet I found there are some glitch and also ESP3D used same settings for WiFi Client as Ethernet Client, I think for consistency it is better to split the commands and setting between WiFi and Ethernet, I will spend a couple days on it and add changes to current PR

[luc-github]

#1046 done, esp3d.io updated, configurator also updated

[luc-github]

I have updated the installation doc to use 3.0.4 core version - now I will work on update https://github.com/luc-github/esp32-usb-serial for 3.0.4 if necessary and add USB OTG for ESPS3/S2 - Hope to finish next week

[luc-github]

Quick update : I am late... daily life keept me away from PC so I am 50% progression of usb-serial implementation, I hope be able to resume this week end ...

[luc-github]

USB-serial is implemented - and I am back home so will resume - on hold task
1 - new hardware support
2 - TBD

[luc-github]

ESP3D is now Ok to move to Beta state I guess - current opened issues are more feature request for new hardware support, only the streaming is partially implemented and I think it should not prevent from moving to beta, the new serial protocol feature is big project on itself and should not be a blocking point neither
If no major issue raised- I will enabled the beta state next week and do a release