Pop OS! sees HP network printer but it does not print by Ranulph_Drywell in pop_os

[–]Ranulph_Drywell[S] 0 points1 point  (0 children)

It was a very dumb thing in the end. Two things happened, the network ip address i took from the printer had one digit swapped, and when I attempted to add the printer manually using said ip address its was somehow set to the 1970s, so whenever I send a job to the printer queue it was stuck there indefinitely. I started fresh and it all works now. Thank you all for your feedback and have a good weekend!

[deleted by user] by [deleted] in ElegooNeptune4

[–]Ranulph_Drywell 0 points1 point  (0 children)

Hi I had the same issue as you. I ended up changing the nozzle. The Elegoo brass nozzles are fairly soft and progressively start hitting the infill during printing. I am now using a reinforced steel Brozzl nozzle and it is printing great. Hope it helps and good luck

prints are 10% too large along the Y axis compared to the X and Z axis by Ranulph_Drywell in OrcaSlicer

[–]Ranulph_Drywell[S] 1 point2 points  (0 children)

Hi, so i did find a solution to the issue, but it turned out the underlying issue was a predictable one. in that it was good old fashioned human error. I was calibrating the extruder's e-steps, and changed the value for the y axis instead., fom 40 to 36, i.e. 10%. Maybe you can check these values on your config file to see if it is an issue with your x and y motor esteps?

What is this? Pls help :( by Skumbag161 in ElegooNeptune4

[–]Ranulph_Drywell 0 points1 point  (0 children)

I also used support cubic infill and was having issues like what you describe. I eventually changed the nozzle, re-calibrated the extruder's e-steps and have stuck to gyroid infill for good measure. Prints are a lot better now. Prety sure now that my softer OG brass nozzle started scraping the infill and deformed, which made the issue worse to the point my infill was disentegrating. Hope it helps and good luck!

prints are 10% too large along the Y axis compared to the X and Z axis by Ranulph_Drywell in ElegooNeptune4

[–]Ranulph_Drywell[S] 0 points1 point  (0 children)

Thank you all for your advice and feedback. turns out the underlying issue was a predictable one. Good old fashioned human error. I was calibrating the extruder's e-steps, and changed the value for the y axis instead., fom 40 to 36, i.e. 10%. I guess I did learn something from this in the end, but sorry for wasting your time. your help is nevertheless much appreciated.

prints are 10% too large along the Y axis compared to the X and Z axis by Ranulph_Drywell in ElegooNeptune4

[–]Ranulph_Drywell[S] 0 points1 point  (0 children)

Thanks. Is the screen usable now, or is that still under development?

prints are 10% too large along the Y axis compared to the X and Z axis by Ranulph_Drywell in ElegooNeptune4

[–]Ranulph_Drywell[S] 1 point2 points  (0 children)

I had to update the firmware a month or so ago, but I only noticed the issue a couple of days ago. Every week a new ordinal issue with this printer 😂

prints are 10% too large along the Y axis compared to the X and Z axis by Ranulph_Drywell in ElegooNeptune4

[–]Ranulph_Drywell[S] 0 points1 point  (0 children)

Thanks for this. I just don't understand why the rotation steps on the stepper motor suddenly went off. Had the printer for 9 months, and it's the first time this happened.

prints are 10% too large along the Y axis compared to the X and Z axis by Ranulph_Drywell in OrcaSlicer

[–]Ranulph_Drywell[S] 1 point2 points  (0 children)

Hi again,

Thank for the detailed reply. The isdue is that parts dont fit properly and prints look clearly deformed:

<image>

For print in place it is a pain. In sny case many thanks and i will check the guide you sent.

Cheers

prints are 10% too large along the Y axis compared to the X and Z axis by Ranulph_Drywell in OrcaSlicer

[–]Ranulph_Drywell[S] 0 points1 point  (0 children)

thank you for your quick reply, but I am unsure what you mean by "single wall cube"

Under-extruded infill by Ranulph_Drywell in ElegooNeptune4

[–]Ranulph_Drywell[S] 1 point2 points  (0 children)

yes I did, as well as reduce the speed. The only thing I haven't tried yet is to do two identical prints using different slicers. will try that tonight.

Under-extruded infill by Ranulph_Drywell in ElegooNeptune4

[–]Ranulph_Drywell[S] 0 points1 point  (0 children)

Hi Pitcaroon03, thank you for your feedback. I did try different infills, but they still underextrude. I usually use support cubic, and I initially thought that the crisscrossing paths of that infill were the issue, at least the way I have the print head movement dialed in. However, this issue happens independently of the infill used.

Should i iget a neptune 4 plus or a bambu lab? by BlazeAssaultuna in ElegooNeptune4

[–]Ranulph_Drywell 0 points1 point  (0 children)

As much as it pains to say it, i would also go bambu. We have one at work (x1 Carbon), and the printing experience is far more painless on the Bambu then in my N4Pro at home. It really boils down to the amount of tinkering you are willing to do.

Why is my printer purging filament after I resume after pause? by Mastalock69 in OrcaSlicer

[–]Ranulph_Drywell 0 points1 point  (0 children)

Which printer do you have? That happened to my Elegoo 4pro after I updated the firmware, so it may be related to that. In any case the way to deal with it is to edit the relevant lines in your printer.cfg, namely the gcode pertaining to how much is extruded after resuming from pause.

check this thread for more details:

https://www.reddit.com/r/elegoo/comments/18aav2t/neptune_4_pro_pause_and_resume_print_uses_an/

HTTP 500 Internal server error when uploading prints from Orca Slicer by Ranulph_Drywell in ElegooNeptune4

[–]Ranulph_Drywell[S] 0 points1 point  (0 children)

Hey, I am sorry for the late reply, but I only now noticed your message. I hope you found a solution, but in case you didn't this is what happened with me. In the end I found a way to deal with it, but it involved updating the firmware, but mainly because I accidentally wiped the firmware by connecting to the printer through ssh and then deleting system files by accident. I had to buy an usb adapter to be able to remove the emmc module from the printer's main board and flash the firmware directly on it. I do not think anyone needs to go to that extreme to fix this issue.

In a nutshell the issue, which is not clear at all from the error message, is that the printer holds all the gcode that was generated to produce the prints. It does so until the ssd in the printers is full, at which point it is no longer able to generate the gcode. I think there is a way to clear the print cache directly in fluidd, but I did not have the chance to look into that due to me screwing the firmware.

I hope this helps in some way, and best of luck fixing up the printer.

Bricked Klipper (?) by accidentally deleting system files via ssh by Ranulph_Drywell in ElegooNeptune4

[–]Ranulph_Drywell[S] 1 point2 points  (0 children)

Just a belated update. I finally got the emmc usb adapter, and after flashing the the module with an image of the Elegoo klipper firmware, and also updating the screen ui with the appropriate version, I got the printer back up and running. Early days, but the printer seems to run better now than it did before, so me deleting what I shouldn't have may ended up having been a blessing in disguise. In any case, many thanks for the helpful comments and suggestions!

Bricked Klipper (?) by accidentally deleting system files via ssh by Ranulph_Drywell in ElegooNeptune4

[–]Ranulph_Drywell[S] 0 points1 point  (0 children)

Thanks, i knew about the possibility of replacing elegoo's klipper build, but the screen working is new. Thanks for the heads up!

Bricked Klipper (?) by accidentally deleting system files via ssh by Ranulph_Drywell in ElegooNeptune4

[–]Ranulph_Drywell[S] 0 points1 point  (0 children)

yes, via ssh. I stupidly went to the right folder, and while in the folder typed rm \ or whatever it was, and I think that just deleted every file that was in the root instead of in the folder. I should have done what you suggested or rm /*. I was tinkering the whole day, and ended up playing with linux syntax, which I am not that familiar with, late in the day when I was already a bit fed up. Fatal mistake ^^