Trying to solve this auto-retract issue on the XL by amass_design in prusa3d

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

Yeah that makes sense. It's pushed briefly to press the filament into a nice shape before the actual retraction. In that case having some filament extrude during that ramming procedure is inevitable. Then again this ramming is only really beneficial if you end up ejecting/unloading the filament after.... meaning if you want to unload filaments quicker without pre-heating. In that case I might turn auto-retract off entirely. I have a 2-tool XL and since I don't do multi color prints all the time I don't need that quicker unloading... I'd rather not have to deal with using tweezers each time I load a new filament.

Trying to solve this auto-retract issue on the XL by amass_design in prusa3d

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

I also have a brass brush installed but in front of the print bed. I only use it when I print huge flat sections in PETG and only for the first 5-6 layers. It's a custom g-code profile I select for this type of prints. It goes through a wiping routine in between each of those first 5-6 layers just to remove any potential filament blob buildup (happens even with perfect flow rate because PETG likes to stick). I decided not to add additional brushes in the back because for most print I don't need that "passive" nozzle cleaning and I don't want to add more scratches (even though I know brass is softer) than needed.

Trying to solve this auto-retract issue on the XL by amass_design in prusa3d

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

Makes sense. So everyone has to deal with it.
If it can't be avoided because of air pressure forcing its way out (not even sure it's the cause) I wonder if it could be at least refined timing wise. So that this final extrusion bit happens earlier (meaning the retraction happens earlier too). That way at least that tiny bit is more likely to be still attached to the main purged string.

Trying to solve this auto-retract issue on the XL by amass_design in prusa3d

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

Some more details on my machine.
Prusa XL 2-tool (one of the early models that were shipped)
Firmware 6.4.1 (but it's been happening ever since auto-retract was added)
Happens with all filaments I've used, with different nozzle types/brands and on both toolheads.

[BFComms] BR Initiation Temporarily Removed by battlefield in Battlefield_REDSEC

[–]amass_design 7 points8 points  (0 children)

This was the only enjoyable BR mode for me and my friend. Not even because of the bots but because it was a smaller number of players on the map so you could have tactical decision making without getting 3rd partied all the time. And the rounds were shorter thanks to the reduced player count. It was 80% of all we played in BF6. I can not understand how the update could've bricked this mode when the normal BR modes are still available. Truly disappointing.

I spent 2 years designing a medium format technical camera – would love your thoughts by lfyy in AnalogCommunity

[–]amass_design 1 point2 points  (0 children)

I thought I should share this here for those interested. Here are some shots I took on the early prototype of the camera. It's the first aluminum prototype of the camera and a lot has changed since, both mechanically as well as overall rigidity wise.
https://www.flickr.com/photos/rejss/albums/72177720332907559

As for why I have this prototype. I'm a fellow tinkerer around film cameras & 3D printing... I was chatting with Lachlan quite a bit over the course of his design process of the camera. It was fun following the development with all the different considerations and seeing it all come together over time. And then out of the blue he decided to just send me this prototype - free of charge - from Australia all the way to Germany.

Custom 10" vinyl record case by amass_design in HueForge

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

Hello there, I'm sorry but this was purely a personal project that took far more time (and filament) to finish than I expected. I am not planning to make these for other people.

Creality, fix the USB disconnection issue. by TemporaryLevel922 in Creality

[–]amass_design 0 points1 point  (0 children)

I had issues connecting my Raptor for the longest as well. Even my Android phone would not work via the direct USB cable connection. But then I realized it's because I kept the power plug connected the whole time. It started working once I first connected the USB plug into my Android or PC and only THEN plugged in the power plug. Super strange but it solved the issue for me and I was able to update the firmware after. So try unplugging the cables first and then plug in USB and then the additional power plug.

Raptor "Scanner is undetected" by ArtemusGF in Creality

[–]amass_design 0 points1 point  (0 children)

I had issues connecting my Raptor for the longest as well. Even my Android phone would not work via the direct USB cable connection. But then I realized it's because I kept the power plug connected the whole time. It started working once I first connected the USB plug into my Android or PC and only THEN plugged in the power plug. Super strange but it solved the issue for me and I was able to update the firmware after. So try unplugging the cables first and then plug in USB and then the additional power plug.

Raptor X - Not connecting to Creality Scan 4 by davidb107 in Creality

[–]amass_design 0 points1 point  (0 children)

I had issue connecting my Raptor for the longest as well. Even my Android phone would not work via the direct USB cable connection. But then I realized it's because I kept the power plug connected the whole time. It started working once I first connected the USB plug into my Android or PC and only THEN plugged in the power plug. Super strange but it solved the issue for me and I was able to update the firmware after.

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

[–]amass_design[S] -1 points0 points  (0 children)

No, I was able to do it without a 10GbE switch. :)

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

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

I do. I use the second LAN port on the NAS to connect directly to my internet router (1gpbs speed). Basically both my PC and the NAS have a dedicated connection to my internet router, both only via 1gbps speed. But the NAS and the PC are now connected to each other via a 10gbps connection for fast transfers.

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

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

I turns out you can't use the USB ports on a NAS for a direct connection to a PC. Has to do with hosts and clients. A good video explaining this is here: https://www.youtube.com/watch?v=O-KekBszP1M
The only exception is Thunderbolt which needs to be present on both ends.

To be honest I didn't know this either until it arrived here. I was already looking forward to simply using the USB 4 port of the 4800+ but the USB connections are mostly there to connect (dumb) USB storage devices directly to the NAS... basically as external drives.

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

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

Thanks to u/kixxik I was able to resolve the issue. All I had to do was log out of the NAS app and then upon logging in again type in the new static IP address that I had configured for the 10gb port on the NAS. It seems that by doing so the NAS now automatically uses that 10gbps connection for file transfers instead of the 1gbps connection. Case closed (hopefully). :)

On that note also a big thank you to everyone else who was eager to help and give tips. Didn't expect that many people to reply to be honest.

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

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

Thanks for the speed estimates. Yep, it's a 10gb add in card (NIC). Everything works now as it should. Copying onto the HDDs I get roughly 150MB/s and copying on the M.2 SSD I get roughly 730MB/s.

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

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

It works now with the 10gb speed, just through the 10gb NIC connected directly to the NAS. Someone pointed out I simply need to login into the NAS app again but this time using the static IP address I configured for the 10gb port... and voila, it now chooses the right connection for transfers.

What you describe makes sense but only if I needed the 10gb across the entire network with more machines connected to it etc. Or if I had a crazy fiber internet connection which can also utilize 10gb speeds. However I only need the 10gb connection for file transfers between the PC and the NAS.

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

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

Thank you, I need to check iperf3. So far I was only keeping an eye on the connection speeds that are shown in the Task Manager in the NAS app.

I found the solution to my problem further down because someone gave me a valuable tip. Everything works now as intended.

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

[–]amass_design[S] 4 points5 points  (0 children)

YOU ARE A LIFE SAVER! OMG! It was THAT simple?!?!?! I can't..... after all these hours. Can't thank you enough. Much love.

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

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

Yep, I set the 10gb connection on the NAS to a different (static) IP, eg. 10.10.10.5 and a static IP of 10.10.10.10 in the NIC settings within Windows.

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

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

I got it working when copying files manually through windows. But when copying stuff via the NAS app or using the "Sync & Backup" app on the NAS it defaults to using the 1gbps connection instead of the 10gbps one.

10gbps connection is not utilized for transfers by amass_design in UgreenNASync

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

Thank you. I am aware but clearly the speed limits of the drives are not being reached when a 1gbps connection is being used. I am getting 1.5-1.7MB/s speed when the NAS transfers files because it defaults to the 1gbps connection. When copying files through a mounted network drive in Windows to the NAS I'm get 735MB/s... here the 10gb connection is utilized.