Discussion
Modifying FileZilla to Workaround Bambu 3D Printer's FTP Issue
whalesalad: Somewhat related I am thinking of picking up a Bambu A1 as my first foray into 3d printing ... seems to be a really solid move can anyone comment?
bb88: Go for it, don't spend a lot of money though on the first one. If you enjoy it then figure out the next one to spend the money on.The big issue for me right now is that a lot of the smaller bed printers can't really do some of the larger projects I want to do like wall hanging systems or drawer organization systems.Also Bambu the company mostly is fine, but there's some worry that they'll eventually lock people into using only their filament, but doesn't seem to have happened yet. So buyer beware.
xoxxala: > Also Bambu the company mostly is fine, but there's some worry that they'll eventually lock people into using only their filament, but doesn't seem to have happened yet. So buyer beware.I'm not sure how Bambu could actually do that. They use RFID tags to identify their filament type/color. I taped a tag from a used roll to some prusa filament and the printer couldn't tell the difference.Just in case, my Bambus are LAN only and don't get updated. I use Orca Slicer instead of the Bambu slicer.
pawelduda: Good choice, keep in mind that you'll probably spend more on filament rolls if you get hooked
kiproping: Instead of recompiling the source and installing it again, is there a way to monkey patch the already existing package? It seems like a few lines of code.
Pay08: That would be incredibly complicated and crash-prone to do.
lexicality: > I use Linux daily and don't want to switch to Windows just to connect to the printer's FTP serviceI wonder if the author tried using their file manager to connect? I haven't needed any kind of external file management system since switching to Linux, Dolphin just handles everything (sftp, ftp, samba, etc) for me natively in the same window.
prmoustache: That was my first thought as well, there is special client needed on all major desktops.
whalesalad: you can recompile and not install it anywhere, just run the binary you compiled yourself.
hxbddbj: The A1 mini has FTP O_o that's actually great to hear
pavel_lishin: I upgraded from my buggy, annoying Ender 3 Pro to a Bambu A1, and it's been pretty wonderful so far. I haven't had any need to "babysit" it, and I can trust it to just start a print, and finish it when I get back. It self-levels the bed, etc.I got the most basic model - a single feed for filament, etc. I recommend it.People are right that you shouldn't spend too much money, but don't spend too little, either. If you think to yourself, "Well, $300 is a lot for a 3D printer, I'll just get an Ender 3 for $200, or a used Ender 3 for $100", you'll end up getting significantly more frustrated if all you want to do is 3D print things.
jacquesm: For $300 you can get an A1 mini and it's a pretty solidly engineered printer. We're running them until they break. But they don't break...
xrd: I second this. Occasionally the head will jam, but it is easy to clean them out. But, the A1 mini is the first device that really just works. It's so much fun.Do not be an idiot like I was and try to print in an outdoor atrium to avoid fumes. That's really not an issue these days and humidity will kill your filament. For many reasons related to humidity control, it is useful to invest in a humidity monitoring filament holder.
progbits: I'm guessing bambu implementation returns the server socket's listen address, and they bind to 0.0.0.0. (Typography pet peeve, how do I disambiguate that dot?)What's surprising is how this got shipped. Do the devs use some other client that has the WinSCP setting on by default, or is that feature only used by their slicer and their SDK does it by default?One theory I have is they bound the server to the printer's address originally and it behaved properly, but then changed to 0.0.0.0 later.
wqweto: Too bad FileZilla can’t be forced to use EPSV which might just work with this buggy server.
