I’m running into a very frustrating issue where my X2D keeps freezing at the end of the first layer of the prime tower on multi material prints (using both nozzles). The printer is currently in Lan only mode and is on firmware 01.01.00.00.
The first layer will print, but then just freeze up. No warnings or errors popping up, just frozen. I end up needing to turn off power on the back to reboot it.
This did not happen on the firmware the printer shipped with, so I am thinking it is something in the 01.01.00.00 update. I’ve reloaded the firmware (from a USB stick), but that has not fixed the issue. Unfortunately, it doesn’t seem to be possible to revert to the original firmware, as it is not published anywhere that I can find. Factory reset does not appear to revert it back either.
I found one other instance of someone having what appeared to be the same issue online. They said they were able to fix the problem by reloading 01.01.00.00, which I am trying again currently. Just wondering if anyone else has run into this issue.
https://www.reddit.com/r/BambuLab/comments/1teasxm/x2d_freezingunresponsive_with_nozzle_on_prints/
Try changing the earlier file name to something greater than the current name e.g. 01.01.00.10
1 Like
Honestly, I’m not comfortable manually altering anything about the firmware. Right now this is a Bambu issue, but if I brick the printer by uploading modified firmware, that becomes a me issue.
Adding a bit more information. I updated the firmware today to the newest version, just released. Unfortunately, the problem persists. Prints fail just as they start to print the second layer on the prime tower.
I did confirm that the pre-loaded panda files prints fine, including the prime tower. But, that is the only file I’ve every been able to print successfully on the printer. Multiple other files sliced on my computer have failed, both sent via lan only mode as well as with a usb stick.
Don’t have this issue since I updated the firmware. Does the issue also occur when you are printing a single color from either nozzle’s?
Try using the bare stock defaults in the slicer for all components? Machine,filament,process. Your one nozzle is 245. What’s loaded in it? Try using both nozzle pla while debugging.
I have exactly the same issue. Having the same temp for both nozzles seems to be fixing the issue. I’m on the latest firmware too.
1 Like
I am using Polymaker Panchroma matte in the hotter nozzle, using the profile for the X2D I downloaded from the Polymaker website.
I will try printing using regular PLA in both nozzles. It will be interesting to see if that impacts the issue. Even if it does though, my use case for purchasing the printer was different materials in each nozzle, so it will still need to be addressed by Bambu. But, it would at least give another clue towards the issue.
I am currently on the latest firmware that released yesterday, still getting the same issue. I have not printed any single nozzle prints yet, but my coworker did successfully print one.
Interesting, I’m running a test now. The culprit might be the Polymaker profiles because I’ve done the same thing and the profile shows N/A for bowden max volumetric speed.
I’ve changed it to 8 and will give it a try and update here.
I am currently printing a two color benchy using elegoo PLA in both nozzles, and the generic PLA setting for each. It has gotten passed the second layer and is showing no signs of stopping. I am also suspecting the Polymaker profile.
It is highly probable that this issue is caused by Polymaker profile having N/A in bowden profile’s max volume setting. Can you try to confirm?
I have successfully printed with the profile fixed now!
However this is still a bug because the tooltip clearly states that if user (Polymaker in our case) enters an unacceptable number it will be ignored. Yet it is not ignored. Or it can throw an error instead of freezing.
1 Like
Just to confirm, to fix the profile you entered a value for the max volume setting in the bowden profile? I just did that as well, updating both the high flow direct drive and bowden settings to 8, from N/A, to match the standard direct drive setting. I also did the same for the Polymaker ESD-safe PETG filament I had downloaded but hadn’t tested yet.
Hopefully this is the issue and is an easy fix until Polymaker corrects their profiles, and Bambu adds a check and error notification if this field is missing.
I am going to test out the updated Panchroma Matte profile as soon as the current benchy test finishes printing. 
1 Like
Slicer should probably reject the slice if there’s 0 flow, dont need to send it to the printer for it to find out. Maybe worthy of a bug report if you have something recreatable.
I always use filament profiles derived off the “Generic $material” presets, and so far, things have been ok w/ aux and main although you do have to mentally keep it straight. In case you want to get working right now and not wait for some corpo to update a json file
Yeah I did simply edited the profile. Specifically for the Bowden.
24 would be too high I believe so I went for 8 for now.
There is an issue on github already.
I wanted to get the best profile from the makers and edit from there generally. But it seems like due to the bug and bad profile it’s been the bane of my existence for the past few days
I can confirm this was the issue. I set the flow max to 8 across the board and it is not printing the 3rd layer of my model with the Panchroma material. Thank you Kontinyu for your help.
I will pass this along to Bambu via the support ticket I opened. Even though the issue ultimately was with the 3rd party profile, there still is an issue in their firmware if it doesn’t look for this problem and throw an error.
I think you meant it is “now” printing!
Happy to help, and yes they should look into it. Slicer should give an error or ignore the setting etc. instead of freezing midprint.
Yes, typo. Now printing! Actually, done now, came out great!
