Ender-3 V3 SE: config settings to roll our own firmware please

I think i have all those changes I merged your version with the others into one, you can check your commits in my repo too.

About using one repo I don’t mind if you want to use yours I’m happy to make PRs there, mostly because I’m not looking a lot into my own github, we can discuss this later. In the meantime I’m going to change the progress percent to reflect layer progress instead of time of completion. And will work on the STL preview to check options to write into SD a small data or transmitting on the fly. This need to be tested with other gcode files too.

Hey @Mikey_Mike_Mik any progress so far into porting the changes to marlin 2.1? I’ve been trying to make it work on my printer but I’ve been unlucky so far. Biggest problem I’ve encountered is the LCD that simply refuses to work. Apparently the v3 uses a different LCD than other models and it’s not yet supported. I’ve been trying to understand what creality changed by comparing the creality repo with the same marlin version but creality seems to have messed a lot with the marlin core too. The v3 board is now officially supported by Marlin so we’re getting closer to have an official setup.

Yes the LCD that the E3V3SE uses is a non standar serial DWIN LCD, you can find the configuration of it in the creality firmware in the path: Marlin/src/lcd/dwin/ and to use it Creality enabled the validation with: #define DWIN_CREALITY_LCD in the Configuration.h at line 2693.

The serial port, baudrate and encoder settings must be enabled too, then across the code you will find validations like:

#if ENABLED(DWIN_CREALITY_LCD)
#include "../../lcd/dwin/e3v2/dwin.h"
#endif

@iroh3d I bit the bullet and installed your firmware. I would like to extend my appreciation for the great work you have done and are still doing.

I am so happy to get the lcd to display info from the print it ties Octo and the lcd up brilliantly.

I see what you mean the layer info is unpredictable. I have a print running and the layer info is not changing at all, but no doubt you will resolve this in due time. Everything else seems to work great like the time remaining and percentage, they seem to be in sync with Octo.

Again thank you for the work you are doing and I look forward to more releases from you.

Cheers

Hi @Bruce_Van_Essen, It was supposed to be fixed but lets see where is the issue. Could you please download this file, rename it to .gcode, remove your filament to not waste material and print it.

We are looking for the “M117 DASHBOARD_LAYER_INDICATOR” messages in the Octoprint serial terminal, this messages set the layer info. If the file works as expected can you share with me which Slicer are you using and which plugins do you have installed?

I guess the PrintTimeGenius and the DisplayerLayerProgress(even disabled) helps to show the messages correctly. And also let me know if you are using the latest versions of the E3V3SE modified firmware and the latest release of the Octoprint plugin.

Hi @Iroh3d

I have run the gcode file and the answers to all are below

I am running version FW1095_OctoPrintPageinLCD of your firmware dated 2 weeks ago.

I am using Orca slicer 2.2.0 (updated last week)

And these are the plugins I am running

Achievements Plugin
Announcement Plugin
Anonymous Usage Tracking
Application Keys Plugin
Backup & Restore
Classic Webcam
Core Wizard
Cost Estimation (3.5.0)
Discovery
DisplayLayerProgress Plugin (1.28.0)
Error Tracking
Event Manager
File Check (2024.11.4)
Firmware Check (2021.10.11)
GCode Viewer
Logging
OctoPrint-E3v3seprintjobdetails (0.0.7)
Pi Support Plugin (2023.10.10)
PrintTimeGenius Plugin (2.3.3)
Software Update
Themeify (1.2.2)
Virtual Printer
WiFi Status (1.9.0)

Ok I printed the test cube. I am not getting any M117 commands showing in the terminal.

Is there a chance to share the Octoprint.log and the serial terminal log when you try the cube file?

Hi @Bruce_Van_Essen

Thanks for the Info.
Did a complete debug and just realized that my plugin depends on 3 plugins.

Please to make it work correctly install the following plugins:

  • Dashboard
  • GcodeViewer
  • PrintTimeGenius

To see correctly the layer progress you must wait till GcodeViewer analyse the file, after that you can start the print.
PrintTime Genius Provides the Estimated Print Time.

Usualy I load the file and when I see the screen in the LCD I check if gcodeviewer finished and then I press print to start the job.

So after that, try to reprint the cube without filament and let me know if is fixed.

Going to add those instructions to the readme.

Hi @Iroh3d

You are a gentleman and a scholar. The plugin is now working perfectly. Thank you so much for helping resolve this. I am very impressed with your work and look forward to future updates.

The bonus is the Dashboard is actually a really good plugin.

Have a great weekend.

1 Like

This past weekend I installed all the required plugins and could not get things to work. After much research I found that PrintTimeGenius does not work if you have Octoprint installed as a docker container, which is my setup.

Looks like I may have to try and find the problem with PrintTimeGenius if I want things to work with your additions…

The PTG plugin is mostly used to have a better source of Time, since Octo uses th estimation based on File processing(hoy many bytes of the file has been processed). My plugin takes the
print time from system not directly from PTG, when you install PTG it overrides the system.

Having said that I guess my Plugin should work using default system time provider, the only “problem” will be the Progress, with not accurate source could be worst than is right now.

Maybe if worths I could add a setting parameter to show the progress based on the Time(which is how it works right now) or use the Layer to show it.

If you are a colour change type person layer number would be best. If you are someone like me who makes functional prints time would be best. I think you need a poll attached to this thread to see what be most popular.

Released the version with the option to choose between Time or Layer along some other fixes: Plugin version v0.1.1

Hi General Iroh.

First of all, I would like to give you thanks for the effort, time and resources you have spent for merging and compiling (from other compilers), basically most (if not all) the things an E3V3SE owner needs! Higher temps, larger auto-level bed grid, linear advance, OctoPrint to printer communication (to and fro), updated progress on the stock LCD screen, filament runout; perfection. So, you have my thanks!

However, if you don’t mind me asking for some feedback, I flashed my E3V3SE with it and it works! But, there are 2 things somehow is not working for me. If I send M117 command message to the printer via OctoPrint terminal, it does nothing at the LCD screen. And, the printing progress update on the LCD, well, upon printing, the screen receives the update but everything remains as 0. From start to finish, 0% progress, 00:00:00 time, 1 layer / 100 layers. Can you suggest where I should be looking into to troubleshoot this matter?

Oh, FYI, I have downloaded the Dashboard, GcodeViewer (enabled and built-in by default, I guess?) and PrintTimeGenius. I also installed your latest plugin, and chose the O9000 command and tested with both layer or time updates.

Thanks, Iroh.

Khai.

Hi there!
Can you please share the following:

  • Version of Plugin and Firmware.
    By your message I’m guessing both latest right? v1.0.9.7_3 for printer and v0.1.1 for octoprint,

  • Describe what happened.
    If I understood well the LCD renders everything but no updates on layer, time and %progress if not please correct me.

  • How the Gcode file was loaded.
    Using the normal Octo GUI or printing direct from slicer?

  • If your Gcode is not parsed correctly, attach your gcode file, currently only Orca and Cura files has been tested.

  • Which slicer used to generate the GCode.

If its possible to you, can you open an issue in the github page to keep this thread clean?

Hi Iroh.

Sure, I will open an issue on Github.

Thanks for your reply!

Hi , I tried to install the 1.0.7 code on by Creality Ender 3 V3 Se and something went wrong. So I tried to revert to the factory supplied 1.0.6 version, nothing happens. I put in the formatted SD card with the software and switch on, the display shows the wave pattern and nothing else happens. I left it overnight… I think the bootloader must be corrupt. Any advice on how to proceed? I have used both the Arduino IDE and VScode with PlatformIo although I would not claim to be a great expert in either. My printer has a CR4NS200320C13 board in it.

OK, cancel that. I tried again with yet another SD card and also retried the renaming trick and this time it all worked. So I got extra brave and tried again with the 1.0.7 and now I have a cool set of extra features in Octoprint.
Thanks to all above posters.

Mj

1 Like

I recently started using Octoprint.
My CR-6 Max and S1 work nicely with it.
My V3 SE has stock firmware and Im hating the fact that nothing displays on the printer UI when printing from OctoPrint….

Maybe its time to take the leap and load the custom firmware…….

First, thank for your work on this firmware, I’ve already installed it and it’s very good., butr i have a problem.
I tried to use the color change in the middle of printing, but whenever it asks to change the filament, the printer does not print again, it is always in pause mode, it pushes the filament when I click continue, but it always stays in pause mode

I don’t have Octoprint installed.
Can you test it ?
I’m using the Orca Slicer but it’s the same on Creality

Firmware - FW1093_M600-M117F-G5-LADV-HCMD.bin