Utorrent Settings To Increase Download Speed

0 views
Skip to first unread message

Algernon Alcala

unread,
Aug 3, 2024, 5:24:06 PM8/3/24
to neyfurdopprock

I am working on a personal project that required me to make a thin box that is just about 2 perimeters thick. The model is fine and it slices but I am trying to reduce the print time. Since it is a simple object I thought I could change a couple of settings prusa slicer. According to the the readout most of the box is considered an external perimeter. I should be able to change the speed settings and reduce the printing time. However no matter what settings I put in I don't see any changes in the printing time. See the images below. I even cranked the speed settings up to crazy high values but nothing seems to change.

I updated to the most recent build of prusa slicer and also tried a couple of different objects. Results stayed the same. It seems to update when I change other settings. For some reason its just the speed settings that I don't see any changes. I cranked everything up to 9000 just to see if there would be any updates but I got nothing. Has anyone else noticed this problem? Is it just the estimated time that is off?

Thanks for the reply. Im not sure about the output. I have definitely printed at higher speeds before but it was with larger objects. It could be that the size is too small and there isn't enough time to accelerate. I hadn't thought of that.

Unfortunately I have to keep the current layer height due to project requirements. I have experimented with most of the settings and shaved about 10 minutes off which is good. I have to print a fair number of these so I'll take any minute I can get.

The slicer has a speed limit for layers that take under X seconds. The default is 20 seconds; the slicer will slow print speed down towards the minimum 15 mm/s trying to make the layer take 20 seconds to print. Set the filament cool down timer to something like 2 seconds ... you should see the print speed jump to your expected values. The risk is mushed parts if multiple layers start getting too warm.

If your printer/filament is dialled in you could experiment with reducing retraction. I have 2 printers a mk3 and what used to be a bowden cr10s. I could slice the same models and the cr10 would always be slower to print. Even if i set the speeds and accelerations the same. The thing that was causing the difference was the retraction settings. When I modified the cr10 to be direct drive and set the same retraction value then the print times became almost the same. So it might be worth experimenting with lowering your retraction and z hop values a little and see what that gives you.

Just a quick update - the slow down setting definitely helped. For starters I set the time down to 5 seconds and it cut down the time by about 40 minutes. No loss of quality thus far! I will continue to experiment as needed but that seems to be the main culprit.

We increased our district speed last year from 100 Mbps to 1GB. I was just wondering if there is any setting in the Hive Manager or AP's that needs to be changed? We aren't getting very good speeds from our WIFI network. And some of the clients are wanting to connect to AP's far away instead of the one that's in their room.

If you can just email me the zip file I can go from there, my email is commun...@aerohive.com. For the Radio and Rates Settings, you'll want to go to Configuration> Open the Network Policy> Open the SSID> Expand Radio and Rates. I would recommend turning 1-9 to N/A for the 2.4GHz settings, and 6&9 to N/A for the 5GHz settings, leaving the MCS rates alone. Again, these settings will require that the client device meet a stronger minimum signal before it can connect to or roam away from an AP to a new AP. That should help with the clients connecting to distant APs rather than the ones closer to them.

You have to have at a minimum 1 data rate set as basic. The basic data rates are rates that must be supported by the client to associate/authenticate to the AP. The lowest of the basic rates (if multiple are set) is what the beacon frames are transmitted at (the SSIDs that you see in the air). So as you change that basic rate to a higher rate, the distance that SSID is able to be heard shrinks and by nature the serviceable area of the APs RF footprint. This is one way to keep devices off of distant APs.

So if you currently have 11 Mbps on the 2.4 GHz side and 12 Mbps on the 5 GHz side set as basic, you can set the next rate up. I actually would leave them at 12 Mbps and not go up any higher as a good rule of thumb and try to figure out why devices aren't roaming to nearby APs. The 6, 12, 24 Mbps data rates are by the 802.11 standard to be used as basic rates as they all support different modulation methods. Most all vendors allow setting any rate as basic/mandatory though, so it can and should still work, but back in the past, some devices didn't operate well if a non-standard (6,12,24) data rate was set as basic.

Roaming is a decision that is almost exclusively done by the client device. So if it joins a far away AP, it must have done it for a reason. Congestion, retries, errors, etc. on it's current AP are possible reasons. Unfortunately, determining this can be very challenging. The Aerohive events/alarms might shed some light as to why they moved. If you have load balancing enabled, that too can cause clients to get moved to possibly less than ideal APs.

Absolutely, the best settings to adjust for that would be to disable the lower data rates in the SSID settings. This will require a stronger connection between the AP and the client device, which means devices will be connecting to APs nearer to them with a stronger signal.

You can find the data rates by going to Configuration> Open the Network Policy> Open the SSID> Expand the Radio and Rates section below the Optional Settings section header. If all the rates currently say "Basic" or "Optional" I would start by turning 1-9 to N/A for the 2.4GHz settings, and 6&9 to N/A for the 5GHz settings, leaving the MCS rates alone. If some are already set to N/A, I'd recommend turning the next one or two rates to N/A, pushing out a configuration update, and then waiting about an hour to see if you see any improvements.

I have a question. I put the radio frequency settings that you recommended in one of our schools last year and things have been working pretty good. However, lately at one of our schools devices are grabbing from further away access points than they should causing them to have weak signals and kicking off eventually or just freezing or going really slow. Can I narrow down those setting a little more to help ensure that they grab the closest access point to them? Thank you!

It would be nice if when you paused the laser that you could change the speed/power without starting the job all over again. I realize that there is now an option to change the speed/power in the move tab but that does not reflect in the original file. Keeping track of changes made are difficult and making changes on the fly to get an idea of the settings needed for a particular material is difficult before fine tuning using a target. Unless someone has a better way that they would like to share I think this would be a good idea to include in the next version.

Many of the things that you can change in LightBurn, like the dither settings, DPI, etc, make very drastic changes to the content of the GCode, so they would not be at all simple to update on the fly.

What most people do is use a generator or a set of samples with different settings to run test swatches, and use those to get the initial starting point set before doing the fine tuning. This is a good one: Lightburn PowerScale Generators - O2 Creative

F2-F3 has worked well for me with small 325g batches roasted on the lighter side, up to near SC. I tried constant F4 for a while, with correspondingly higher power to compensate for increased cooling, and found it easier to achieve a smooth declining RoR but the flavors in the cup were flatter. When to switch to F3 is a good variable to fine tune for each bean.

My understanding of most roast systems is that a majority of the heat transfer to the coffee beans is by convection (hot air). Even in a direct-heat drum roaster such as the R1 where the hottest component is the drum, the hot air (environment) in the roaster is doing the majority of the work. On the Loring heat transfer skewed towards convection as it uses hot air to indirectly heat the environment and drum.

I do think that dropping the power and increasing the fan speed at the same time or close together will have a large effect on RoR and I would be inclined to do one or the other unless the RoR trend is rising substantially. Perhaps my approach to using fan speed to help regulate RoR is incorrect and I should just be focusing on using the charge temperature and power settings to establish, maintain and control momentum and RoR.

Finally, it could be that you only pay for a slow internet connection. Then paying more for a faster connection can be a solution. What do you pay for (in Mbps download and upload) en what is the fastest you can get at your home?

I would reach out to your internet provider. There are not many things that you can do to increase your data connection speed on your computer, if anything at all. Is it one internet site or multiple sites? How old is your computer?

Check your network settings: Make sure your iMac is connected to the correct network and that the network settings are properly configured. Check the network settings in the System Preferences and make sure they match the settings provided by your internet service provider.

Update your software: Make sure your iMac is running the latest version of macOS and that all software updates have been installed. Updates often include bug fixes and performance improvements that can help improve internet speed.

Thanks for signing up! Keep an eye out for a confirmation email from our team. To ensure any newsletters you subscribed to hit your inbox, make sure to add newsl...@nl.technologyadvice.com to your contacts list.

c80f0f1006
Reply all
Reply to author
Forward
0 new messages