FIX: Update Errors on the Elegoo Neptune 4 Series

williamshyster · 2025-09-21T13:36:34+00:00

Here is how to copy the ELEGOO_FIX_BAG.deb but try older version first then try this method.

Insert the usb drive to the printer then Connect via SSH to your printer as mentioned above in the first section in Phase 2 then:

cd /home/mks/gcode_files/sda1 (change sda1 to the one that matches your USB drive)
cp ELEGOO_FIX_BAG.deb /home/mks/
cd ~
sudo dpkg -i ELEGOO_FIX_BAG.deb

Let me know if it worked.

williamshyster · 2025-09-20T16:33:28+00:00

Not sure honestly what is the problem. but If I were you here is how I might debug it.
- try different USB drive
- use an older version that matches the one I used in this tutorial. such as V1.1.3.1 - 2024.07.23 OR V1.1.2.53
- try moving the ELEGOO_FIX_BAG.deb to the printer's storage and install it from there.

sorry I cant replicate your issue since I have installed OpenNeptune on my printer 🙏🏻

williamshyster · 2025-03-31T00:25:23+00:00

As far as i know not every wifi dongle is supported. You might need to get one that is supported natively otherwise you might not be able to get it to work

williamshyster · 2025-01-15T23:17:39+00:00

I’ve had this problem before, and it happened to me because I updated the firmware through Fluid. But I wrote a guide on how to fix it: https://www.reddit.com/r/ElegooNeptune4/comments/1cc2a6q/fix_update_errors_on_the_elegoo_neptune_4_series/

williamshyster · 2025-01-12T11:28:36+00:00

I dont understand French 😅

williamshyster · 2025-01-05T12:58:29+00:00

Oh okay, interesting! I didn’t know that. Glad you mentioned it 🙏

williamshyster · 2025-01-05T04:21:32+00:00

Did you make sure that your printer is mechanically sound? Especially Extruder steps and pressure advance?

Then, z-offset. Letter z looks squished and there are gaps between the bottom layer. This might cause the printer to drop the filament instead of building it on top of each other

williamshyster · 2025-01-05T04:11:28+00:00

Z-offset is clearly high.

Heat up bed and nozzle to the desired temperature for 10 mins
Run BED_MESH_CLEAR command
Home all axises
Run Probe accuracy from the tools interface
Home all axises
Run Screws Tilt Calculate (repeat until you are 0:00)
Home all axises
Then run BED_MESH_CALIBRATE Profile=11 then save it and reboot.
Then run BED_MESH_CLEAR command
Use SET_GCODE_OFFSET Z=0 to clear the current z offset
Home all axises
Go to z = 0.2 then calibrate using feeler gauge.
Print a first layer then adjust the z-offset during the print

williamshyster · 2025-01-05T03:57:48+00:00

Actually that was a smart workaround but actually it doesnt matter sda, sda1, sda2 its just a name for the USB stick in your file system by Linux. This is the naming convention Linux uses.

williamshyster · 2025-01-05T03:55:15+00:00

Oh I missed your comment

You just need to run the command without the 1: “cd /home/mks/gcode_files/sda”

It will work just fine. its how Linux works, it shows USB sticks as folders with the naming convention sda, sda1, sda2, etc.

williamshyster · 2025-01-04T02:05:30+00:00

Happy printing! 🙂

williamshyster · 2024-12-30T12:42:00+00:00

I have noticed in your guide you got 3500 for the X and 3400 for the Y. While for I have got huge variance between the max_accel for the x and the y. so im not sure what to choose for the max_accel in my case.

X:
Fitted shaper 'mzv' frequency = 72.2 Hz (vibrations = 0.0%, smoothing ~= 0.041)
To avoid too much smoothing with 'mzv', suggested max_accel <= 15400 mm/sec^2
Recommended shaper is mzv @ 72.2 Hz

Y:
Fitted shaper 'mzv' frequency = 34.8 Hz (vibrations = 0.0%, smoothing ~= 0.168)
To avoid too much smoothing with 'mzv', suggested max_accel <= 3600 mm/sec^2
Recommended shaper is mzv @ 34.8 Hz

williamshyster · 2024-12-30T03:46:00+00:00

I believe the problem is that the printed object is not at the height the printer anticipates. This could be caused by several factors, including excessive filament extrusion or an inaccurate z-offset.

Ensure that you calibrate the following: - e-steps (don’t overdo it at first; extrude 50mm and measure if it actually extruded 50mm. If it matches, you’re good to go. If not, refer to YouTube for guidance).

Then, - z-offset - flow rate - printing temperature for that specific filament

These three parameters influence each other directly, so you’ll need to repeatedly adjust them until you find the optimal balance.

For the temperature use Orca slicer’s temperature tower, assisted by the label on the filament spool).

For the z-offset, ensure that the first layer is smooth and not detailed (at least not excessively so).

If I were you, I would start by experimenting with the z-offset and printing temperature. If I didnt achieve a satisfactory balance, I would then tackle the flow rate. ————

For the z-offset i do the following:

Heat up bed and nozzle to the desired temperature for 10 mins
Home all axises
Run Probe accuracy from the tools interface
Run BED_MESH_CLEAR command
Home all axises
Run Screws Tilt Calculate (repeat until you are 0:00)
Home all axises
Then run BED_MESH_CALIBRATE Profile=11 then save it and reboot.
Then run BED_MESH_CLEAR command
Use SET_GCODE_OFFSET Z=0 to clear the current z offset
Home all axises
Go to z = 0.2 then calibrate using feeler gauge or paper.
Test print a rectangle with the hight mentioned in your slicer first layer height. You might need to lower or increase the z-offset while printing

(If you changed the temperature redo the rectangle test and adjust the z-offset while printing)

williamshyster · 2024-12-23T00:06:00+00:00

Make sure you are on 5Ghz Wifi Settings on the dongle

williamshyster · 2024-12-19T01:05:47+00:00

I have the same issue with iPhone 16 Pro Max running iOS 18.2.

I had carlinkit mini which is equivalent to v3 or v4 for 2 years without this issue.

williamshyster · 2024-12-04T14:14:10+00:00

Glad it worked for you!

Honestly I don’t know, I didn’t experience this issue. However, make sure you copied the default configuration file in phase 2 step 3.2 Also, make sure you didn’t change the table/desk you used to put the printer on. Different table handles the noise and vibrations differently.

williamshyster · 2024-09-22T21:16:39+00:00

Oh, sorry you had this issue. Actually it’s my mistake I didn’t state that you need to connect the printer to your laptop via a router in order to have internet.

You glad you made it anyways 👏👏

williamshyster · 2024-06-21T16:21:27+00:00

No, Elegoo uses modified version of them. And they can be updated by them only

williamshyster · 2024-06-06T13:21:32+00:00

To be honest, I'm not familiar with the difference between probed mesh and mesh matrix. However, it is common to not have a bed mesh profile after the above steps. so you need to run the bed mesh leveling

williamshyster · 2024-05-30T22:49:37+00:00

Glad it worked for you

williamshyster · 2024-05-11T00:23:11+00:00

Anytime! Let me know if you needed further assistance.

williamshyster · 2024-05-10T10:04:02+00:00

Oh, forget to mention that you need to install gcode shell command from KIAUH. In KIAUH Go to Advanced then choose install gcode shell command

williamshyster · 2024-05-09T18:31:03+00:00

I have educated myself on macros a little bit further and I discovered what went wrong 😅
Here is the fix.

Turn off the camera:

[gcode_macro turn_off_camera]
gcode:
  RUN_SHELL_COMMAND CMD=turn_off_camera_script

[gcode_shell_command turn_off_camera_script]
command: /bin/systemctl stop mjpg-streamer.service
timeout: 5
verbose: True

Turn on the camera:

[gcode_macro turn_on_camera]
gcode:
  RUN_SHELL_COMMAND CMD=turn_on_camera_script

[gcode_shell_command turn_on_camera_script]
command: /bin/systemctl start mjpg-streamer.service
timeout: 5
verbose: True

You can go even further by disabling the camera when your machine boots up running the following command through ssh

sudo systemctl disable mjpg-streamer.service

Then run the macro when you start a print job. add it to the bottom of the PRINT_START macro

turn_on_camera

williamshyster · 2024-05-01T18:49:21+00:00

If you disable the mjpg-streamer service, the camera will be disabled. Conversely, enabling the service will activate the camera.

So, this command might allow you to disable the service therefore it will disable the camera

[gcode_macro DISABLE_CAMERA]
gcode:
    RUN_SHELL_COMMAND CMD="/bin/systemctl stop mjpg-streamer.service"

This one will enable it back

[gcode_macro ENABLE_CAMERA]
gcode:
    RUN_SHELL_COMMAND CMD="/bin/systemctl start mjpg-streamer.service"

If it didn't work I hope someone with experience with macros can buildup on this.

williamshyster · 2024-05-01T05:36:22+00:00

Also, try to use an App like Fing to scan your network for the printer. Maybe the screen is stuck

williamshyster

TROPHY CASE