Filament track switch warning, but I don't have one installed

I haven’t installed a filament track switch, nor does one show up on my device info page in Bambu Studio. So where is this warning coming from and how do I get rid of it?

was this a downloaded 3mf file that maybe had one in the project?

Downloaded, yes. But wouldn’t that be an option I could disable somewhere? I’m not finding where it’s set.

I’ve got the same thing going on. Probably a firmware or studio preset bug.

You could try saving it as a generic 3mf which (from what I am told) should strip out some of the Bambu centric things that are saved in the “Bambu” 3mf.

I’m guessing you are using the latest version of BS since this is an X2D? I am wondering if there is an actual setting on the printer or in studio about the FTS that is enabled by default. Just making guesses here since I don’t have that printer to look at.

Does re-sliceing as the message suggests seem to do anything?

If @Qjo is haveing the same issue but on a different file it could just be a “rare” BS bug.

Edit, I see that Qjo was only setting up a PA test.

Edit 2. Is anything plugged into the 6 pin port that the FTS is supposed to plug into? I have seen it referenced as a “dedicated” port but don’t know if that is true.

probably of no help but there is this

“Tap the printer screen, enter the Filament page, tap the prompt in the lower-left corner, and perform AMS setup. Choose either Auto Mode or Manual Mode.”

Mentioned a little way past half-way (AMS setup) in

1 Like

no help but you are not alone

https://www.reddit.com/r/BambuLab/comments/1sme4a0/x2d_and_filament_track_switch_warning/

Maybe Bambu can start a support group? (Bad joke).

1 Like

At least I’m not alone. I’ll assume for now this is a software bug in BS. The printer itself is not reporting anything about having the track switch installed anyway. Maybe this is a sales tactic to make everyone go buy one to make the warning go away.

I’ve fully given up on “auto mode” on my X2D for the mean time. Doesn’t seem to know it’s “you know what” from a hole in the ground.

Could you please share more information about this problem?

If you can share the steps about how to reproduce the message, we will be able to look into it and offer a solution.

Thank you.

It’s any file. Restarted studio. Used Bambu, generic, and custom filament profiles. AMS-HT’s are setup per the ams menu.

I have the rear exhaust fan hooked into the left port on the buffer and an AMS-HT plugged into the right side port on the buffer. Then there’s a second AMS-HT daisy chained to the first one.

Maybe it thinks the AMS is the track switch?

@SupportAssistant theres no special steps to take. Every time you send a print that error message is there. Would entering a ticket with log files be of any assistance?

Same here, there are no special steps taken here. Just slice any file and hit ‘Print” and this message shows up (screenshots above) before sending it off to the X2D.

Same for me. Independent if it’s a download file from makerworld or own made. Everytime you send any print to the printer via Bambu Studio you get this warning.

Same here ! Let’s hope that Bambulab fix it soon

My X2D arrived yesterday and I have the same error. I have AMS on one buffer port and the fan on the other. I’m considering adding the AMS HT and the track switch. Am I the only one who thinks the track switch installation looks like a messy afterthought? It would be nice if was a replacement print buffer assembly. But I understand they have other printers to support. The X2D in general is messier on the back than my X1C. Like it was fully baked before they started slapping on more stuff. Maybe the better question is if you get more filament path issues with the track switch installed. Setting up the printer I found the weirdest thing was the bowden extruder installation. It was sort of the only reason I needed to even look at the quick start :wink: I’m not sure how I feel about a Teflon tube attachment that needs a wrench :open_mouth:

Well, the Teflon tube attachment is a good solution, I have seen non-wrenched connections failing on other printers.

The ‘messy back’ I agree, and it renders the X2D a bit more space consuming compared to the P2S. And, unfortunately, all that stuff on the back requires a sort of easy access to the rear of the printer, it is not very shelf friendly so to say. Especially since the FTS disables the functionality of using a single external spool outside the AMS universe, it is required to disconnect the FTS just to feed in some filament manually, although I fed it thru the FTS at the end anyway in order to avoid re-connecting all the tubes back and forth.

First print and the message showed up. The file was from Maker world. I have my two AMS 2 daisy chained in the right port on the buffer and the fan in the left port of the buffer.

Same here, tried everything (even deleting all other filaments except two colours, it keeps telling me I have a Track Switch!) but gave up: my X2D keeps giving AMS sync problems since the last update, including this one. And what’s worse: there is no way to make the auxiliary nozzle to work…loaded it manually, assigned it in every way possible: does not show up in Studio.

Because I could not solve it, and I had an urgent task, I stepped back to my old printer.

Definitely not happy with this out of the box problem, and that’s an understatement.

I’m new to Bambu. I’ve had my X2D for a few weeks now and made dozens of prints. Most from scratch using CAD. I get this same warning every single time I hit print plate. I spent so much time trying to figure out what I am doing wrong. Thankfully I found this thread so that I know that I am not doing anything wrong. Definitely a bug. Hopefully there is a fix for it soon. There also must be a bug in the X2D right fan as it seems to ignore all settings but I’ll look for another thread with that issue.

I’ve had my X2D for about a month, and not had this error until I ran a firmware update today, despite multiple prints.

Now it’s present no matter what I try.

I don’t have a filament track switcher installed.

I’m trying just ignoring it for a few low consequence prints to see what happens - fine so far

I presume it’s a bug that will be ironed out.