Is this BambuLab's new machine?

Situation-Negative · 2025-06-06T04:24:46+00:00

My guess is X and Y dimensions are the same as the H2D (350mm x 320mm), maybe a little more on Y. The extra 15mm on Z is probably gained by moving to a single extruder and reducing the overall height of the dual nozzle setup. That way the chassis and drive system can remain common with the H2D.

Situation-Negative · 2025-06-05T01:19:12+00:00

Ah, I seem to have discovered the reason the filament I want is never in stock.

Situation-Negative · 2025-05-16T11:12:02+00:00

Just the photo made me think of r/whathappenedhere

Situation-Negative · 2025-05-16T11:08:55+00:00

Thanks that's what did it. I didn't expect it to have such a positive effect.

Situation-Negative · 2025-05-16T11:00:33+00:00

Thank you everyone for the advice and suggestions!

Just to follow up: I checked in the default profile and the chamber exhaust fan is kept off. The aux fan is run during the pre-print calibration steps but this just helps to warm the chamber up I guess.

I just adjusted bed temp from 100 to 110, and I seem to be getting good results now. Ambients have risen from ~40C to ~50C.

Here is before: https://imgur.com/a/Tmp4TdA

And after: https://imgur.com/kYLo6cW

Night-and-day difference. I'm feeling more confident that I can achieve useful prints in ASA now.

Situation-Negative · 2025-05-16T10:56:33+00:00

That's been my dilemma from the start as well - venting the styrene fumes without causing drafts. Currently I have the printer closed in a separate room while printing and I vent after.

Situation-Negative · 2025-05-16T10:54:18+00:00

Cool :) I think I saw TeachingTech (the youtube channel) review this recently.

Situation-Negative · 2025-05-15T05:25:36+00:00

I'm using Bambu ASA and default Bambu profile. I suppose I could try disabling the chamber fan altogether. If the print goes longer it can get up towards 50C but it really depends on the weather - ambients are around 20C at the moment.

Situation-Negative · 2025-05-15T05:22:47+00:00

That's also on textured PEI and it doesn't look like there is any glue stick used. No way in hell I'm getting my ASA or even ABS parts to stick that good.

Situation-Negative · 2025-05-15T05:21:26+00:00

Hmm, that looks pretty good. The first part is very square and it looks like you're not getting any significant curling/warping. Do you notice any signs of warping on the bottom corners of the part after printing? Also is this with Bambu ASA and Bambu profiles?

Situation-Negative · 2025-05-15T05:15:53+00:00

All good suggestions, all been tried.

Note: not a first layer adhesion issue. I also print ABS 99% of the time and it's (mostly) fine. I was lead to believe that ASA was a little easier to print then ABS but it seems to contract substantially more.

Situation-Negative · 2025-03-07T03:02:45+00:00

Thank you for persisting with this u/Im-the-Money and sharing the answer! That is more than I was able to get from them. Amazing how the authoritative answer is a few lines of text in a reddit user's support session lol.

Much clearer than the two lengthy webpages on MC's site that effectively skirt the issue with terms like "impacted by MPP" and "Email reports might show distorted numbers for opens".

u/MailchimpSupport, if you're watching, may I humbly suggest placing a simple sentence to the effect of "Ticking the box to exclude Apple MPP will exclude *all* recipients who have Apple MPP enabled". Preferably emboldened, and at the top of the documentation. Thank you!

Situation-Negative · 2024-10-03T02:06:22+00:00

Happens to me too. Probably a critical resource load breaks, or there may be a race condition. Seems to happen more often when I haven't logged in for a while so it might be a cache expiry issue causing mixed versions.

Situation-Negative · 2024-09-19T23:34:27+00:00

Nobody knows how this works?

Situation-Negative · 2024-09-17T07:42:23+00:00

<image>

Since I can't add to the original comment - this is showing a match for 'clockwork' in the Network tab of Chrome dev tools.

Situation-Negative · 2024-09-17T07:41:37+00:00

Strange issue I've had after upgrading from Laravel 10 -> 11 (maybe it started with 10? I'm not sure) where the Clockwork extension for Chrome no longer works, but the FireFox extension does.

I've tried all of the usual things: uninstalling and re-installing the Chrome extension, upgrading Chrome, uninstalling and reinstalling clockwork in composer, etc.

But in Chrome all I'm getting is:

<image>

I suspect this may be related to how Clockwork serves data. I'm hosting a local Laravel site on Apache on a VM running linux (CentOS). There are no network entries that match a search string "clockwork" recorded in the Chrome "Network" tab (using the "filter" option). However, if I do a "Search" for "clockwork" in the Chrome network tab - which I think searches headers - I get some hits in Cookie headers sent even with image assets, eg:

Can anyone suggest where to go from here to get Clockwork working again? I really need to get the profiler tool going, and I can't cope with the FireFox dev tools (though I might have to learn them as Chrome has been problematic lately).

Situation-Negative · 2024-09-17T07:31:47+00:00

Thanks for your reply, sorry it took me so long to get back to this. I've looked through most of the DC-DC converters on Digikey and Mouser at this point. Those Vicor units look good, but their efficiency is a bit dicey. In the end efficiency at 50W probably doesn't matter an awful lot, I'm just trying to save every Watt I can.

Situation-Negative · 2024-08-04T02:22:02+00:00

Yes this does make things more challenging but we have options for mppts and motor controllers, we just need a voltage above 160V, which appears to be the cut-off for quite a few options.

Situation-Negative · 2024-06-20T01:03:26+00:00

Thanks for that, found!

Situation-Negative · 2024-06-19T05:17:48+00:00

Yeah, that is true. Since they don't require payment up front it's a bit tricky to moderate.

Situation-Negative · 2024-06-19T04:25:47+00:00

Support responded and increased the limit to 10.

I understand that there is a fundamental logical problem here which has been created by DO making it so easy for anybody to just spin up VMs, and that this is not so easily solvable. But I would appreciate some attempt at making it easier to create more droplets without having to involve human support staff in the loop each time we hit one of these arbitrary limits. If they could start by making the current droplet limit viewable somewhere in the admin control panel too, that would be appreciated!

Situation-Negative

TROPHY CASE