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

Hi @Iroh3d

Thank you for your reply, my apologies on disturbing you. I sort of understand what you are saying but am struggling to find the right scripts for cancel, pause/resume and find myself getting in a mess so in due time do respectfully ask if you can assist a dummy like me.

Marlin 2.1 sounds like a plan

I look forward to your reply when you are back on board.

The scripts that I’m using are here(scroll down to the section):

But it doesn’t affect the M600 behavior. Although it will report the cancellation of the job at the end by sending the M117 CMD to the printer.

@Iroh3d

Thank you for your help

My scripts were different and maybe it wont help the purge side of it but at least cancelling will be reported.

The script you provided indeed now reports a job cancel. I am sure it worked before but at least now it is going again.

Again thank you so much for your help.

Hey all - just checking in post daughter’s wedding (it was wonderful, but here’s a hint: don’t dost a wedding in your backyard. It’s Hard enough being parent of the bride …).

Anyhoo: I’m so proud & jealous of all the good work being done here. Hopefully I get a break over after Christmas to install the latest & greatest & start printing again!

Happy Holidays, Merry Christmas, Hanukkah, Festivus, Kwanzaa, Diwali, Yule, etc …

2 Likes

Hi all, new release has been published v1.0.9.7_4

This release includes:

  • Fix for M600 Purge option from octoprint.
  • Fix for M600 resume print when printing standalone(without connection of Octoprint).
  • Fix for M600 purge when printing standalone.
  • Fix for Bed Level Save prompt from LCD menu, the M117 command now will not overlap the screen.
  • Enable flag when serial port is connected to Octoprint.
  • Added two firmwares for 128000(128kbps) and 115200(115kbps) for those using Octo4A.

Take note of this:

  • This firmware is heavily modified to be used with Octopint, So if you want to use the normal standalone I suggest to use another flavor from another user to avoid any other malfunction.
  • If you connect Octoprint M600 prompts MUST be acknowledge from OctoPrint and will ONLY work from Octopint. Here you can purge N times and then continue
  • If you do not connect Octoprint, M600 prompts MUST be acknowledge from LCD and will ONLY work from LCD. Here there is no option to purge, in the moment you hit the knob of the LCD it will purge once and continue the print job.
  • Once you connected Octoprint the LCD KNOB will not work anymore, This is because the way creality designed the firmware, there is no middle ground so I tried my best to give you the ability to use the knob if Octo is not connected, but if you connect it then you are tied to the host.
4 Likes

Thanks for your excelent work, will try tomorrow.

2 Likes

Hi @Iroh3d

I can confirm that the filament purge now works on the latest firmware release.

Thank you for your hard work.

I wish you and your family a Merry Christmas and Happy New Year.

Regards

Bruce

2 Likes

Hi @Iroh3d

Thank you for your hard work! Merry Christmas and a Happy New Year to you and your family!

I flashed your latest firmware and can confirm no issues with the M600 pause and resume, both via OctoPrint and/or the LCD knob. Great work!

However, I am not sure if this is firmware related, but I tested if a print pauses due to filament runout sensor flagged the print to pause, changing/adding the filament and resume printing via OctoPrint/OctoApp, will not resume the print, especially via the host (printer’s LCD knob). Cancelling will just hand and heater will timeout, reheat and timeout again until printer is reset (and print is ruined hahaha). Upon checking the terminal, it seems that the filament run-out sensor does not send a M600 command as follows:

Let me know what do you think of this. Happy holidays! :christmas_tree:

Regards,
Kai

So if I understood correctly the resume/continue button from Octoprint didn’t worked right after sensor paused the print? Knob from LCD will not work since Octoprint is already connected.

I don’t have a filament runout sensor to check; but I will try to check from code the flow to see if can be fixed.

I am so sorry to say that my darling wife bought me a Nebula Smart Kit.
So now I’m going to have to leave y’all in Marlin land as I move on to rooting it to explore Klipper!

Any hints?

I hope you all have/had a Merry Christmas/Happy Hanukkah/Kwanza/Festivus, and hope your nozzles never clog!

All the best for 2025!

Mikey & family.

Looks like there are a lot of issues related to nebula and some users wrote a guide to not suffer much. Here is one:

https://www.reddit.com/r/Ender3V3SE/s/S61eZYGhuN

Good luck and happy holidays.

1 Like

I concur with the stepper motor current, i had to do this for my Sonic pad assisted V3SE.

Thanks for the advice!

A side question: what can/should I do with my old V3SE display? I have a heavily modded OG Ender 3 (with Creality sprite hot end, runout sensor). Is there any way to “retrofit” it?

Is it the same as the display for the Ender 3 V2?

If si, I’m thinking I may have to do some Marlin codein’ & flashin’ a la:
https://www.reddit.com/r/ender3/comments/irivkf/swap_v2_screen_on_v1_ender_3_pro/

Waddya reckon?

Can you share the complete output of terminal log and octoprint log?
Looking at the code the runout sensor uses M600 command, so teorically it should work with the previous fix, but in your log Im missing some parts of the flow. I’ll need to check it to see where it breaks, since I dont see the resume flag.

Hi @darkclover92 I built a DIY runout sensor to test the firmware and it worked as expected. You can take a look:

In the bottom left when the led become red it simulate the runout of the filament and in the upper video of Octoprint page you can see the activity. I tested with Octoprint and with the printer knob, both worked as expected.

Buuut I’m not sure if the original sensor send the same voltage signal, I’m sending high 5V when it simulate the runout.

Maybe I can send you this version of the firmware that has debug information for the serial terminal and you can send me the log while using the real sensor?

I have the official Creality runout sensor on my SE and things work just like in your video on my printer.

1 Like

Thanks for confirming!

Afternoon, I have been testing this firmware along with some prints with Octolapse. one thing i have noticed when you run with the camera position set to centre and trigger snapshot every 5s the model fails to continue to extrude filament. I have returned to front left and classic every layer trigger without any other modifications to the sliced file and appears to be printing fine.

I will retry the a test print shortly and try grab some logs that can be debugged.

other then that so far this appears to be great awesome work…

Hey guys - New here and new to 3d printing! Thanks for this entire effort and soooo glad I found this thread.

i just installed the 1.0.9.7_4.b custom framework to my brand new SE. My device was (confusingly) running 1.0.7 already…

Anyway, maybe I misunderstood but I thought that one of the updates would be such that if a print is started via Octoprint, it would still show the “origin” progress information on the LCD screen still.

i plan to run from Octoprint, but would be nice if someone went to directly inspect the printer they could still see the original LCD output.

Hi, nope this firmware that I’m working with was edited with the goal of showing:

  • Time of the print. Calculated by Octoprint, or Print Time Genius or from M73 command. :white_check_mark:

  • Print Time left. Same as above. :white_check_mark:

  • Layer progress. :white_check_mark:

  • Percentage of progress. Based on Time elapsed, or Layer or M73 command.

  • The thumbnail of the GCODE. Since no documentation found I’m trying to brute force the access to the memory of LCD so for now we just see the Standard Creality superMan :x:

  • Fully integrated with Octoprint rather than standalone. This because I use heavily Octoprint. I would say the integration is working fine with the help of the plugin. Without the Octoprint plugin installed you will not see the updates in the LCD.

So the disposition of the LCD GUI went a little bit different but trying to keep the same layout and look and feel. The LCD is super tiny so can’t add much on it.