Neptune_3 VS Neptune_3_Pro_Plus_Max

Enable Hotbed PID. Default value: M304 P97.10 I1.41 D1675.16 Debug method: https://github.com/NARUTOfzr/Neptune_3/issues/39

Neptune_3 https://github.com/NARUTOfzr/Neptune_3

My first attempt with the M600 code did nothing, the M600 command was ignored. For my second attempt I tried using the M117 + M0 code, the head moved away from the print, but then started printing again right away. The print continuation was not quite aligned and the print failed (filament being deposited was not attached to the main print). I have some questions: a) The closest post I could find was, https://www.reddit.com/r/ElegooNeptune3/comments/10csnsj/filament_layer_change_what_is_the_current_best/ which suggested using M117 before M0. I used that in my M0 attempt. The screen indeed did change modality, but unclear if the M117 helped or not. Just using M117 and M0 was not enough to make things work for me. b) The first thing I did after assembling the printer was updating the firmware (both screen and board). The board firmware binary file path indicates version V1_1.0.5-Beta (latest version indicated at https://github.com/NARUTOfzr/Neptune_3) however after the "updating firmware" screen, the screen UI still indicates firmware 1.0.2; is this expected or I have not successfully updated the firmware? c) I am sending my prints to the printer via the Mintion BeagleCamera ( https://www.mintion.net/beaglecamera ) does this somehow affect the behaviour of the M0 command ? Should I only use the SD card when trying to have pauses in the print? Being able to introduce more than one color in a print would significantly expand the realm of possibilities. Help and suggestions most welcome.

Yes. You can find the firmware here. The beta firmware hasn’t given me any issues, so don’t hesitate to try it. Just remember, if you have any different e-steps, PID tune, etc they will be reset to original values.

You can find the firmware at https://github.com/NARUTOfzr/Neptune_3 , at the end of the page there is also a brief description about the update. In a lot of cases it's best to update screen and board firmware (screen first).

https://www.elegoo.com/blogs/3d-printing/elegoo-neptune-3-fdm-3d-printer-support-files or more specifically https://github.com/NARUTOfzr/Neptune_3 as i said i've never done this myself, but when scrolling to the bottom there's instructions for updating the screen firmware, and the motherboard firmware. do this at your own risk i know nothing either 😅

Please update the latest version of the firmware via the link below. https://github.com/NARUTOfzr/Neptune_3 You can refer to this tutorial when updating the firmware. https://youtu.be/m6vp1q083sI

Narutofzr GitHub for Neptune 3 Pro/Plus/Max Printers

Neptune_3_Pro https://github.com/NARUTOfzr/Neptune_3_Pro_Plus_Max

this bug is fixed by the newer firmware, you may refer to this link to update it: https://github.com/NARUTOfzr/Neptune_3_Pro_Plus_Max/blob/main/README-en.md

I've tried following the instructions here and here, but the updates don't seem to be taking.

NARUTOfzr/Neptune_3_Pro_Plus_Max: Firmware file (github.com)

Paper test to get a reasonable z offset, then adjust it during the first layer print, to get perfect. This value should be constant, since it's a reasonably fixed property of the sensor, so you should be able to run ABL, in the future, and use the same z offset. See: https://github.com/NARUTOfzr/Neptune_3_Pro_Plus_Max/issues/23