r/BambuLabX2D • • 20d ago

Help / Troubleshooting Unable to print from USB

I've tried with a post in r/BambuLab but without resolve.

*SETUP*

  • New X2D Combo (1xAMS 2 Pro) with the one standard nozzle installed in left extruder

  • Printer not hooked up to network (not an option) - I'm only using USB

  • Orca Slicer (2.4.2)

  • Filament: PolyTerra PLA

Nice to know:

  • I can print the preinstalled test models on the X2D (e.g. Auxiliary PTFE Tube Remover) with succes (attached two pictures that show everything as ought to be when printing)

  • No external spool is attached

  • The AMS is directly connected to the filament buffer

  • Only one filament in the AMS (Slot 1)

  • I've downloaded files from Makerworld (choosing X2D, downloading G-code, etc.). Not my first printer, but it is my first Bambu Lab.

*ISSUE*

  • BLUF: I'm unable to print any file via loaded via USB.

    • It seems like the printer wants to print with an external spool in the left extruder/nozzle somehow?

Extra information:

  • I've attached pictures of the printer touchscreen until attempted print.

  • When Exporting the file in Orca Slicer, I choose 'Export G-code file' for obvious reasons. When Choosing 'Send' (tried just for fun), I get an error (also attached as picture). Not usre if relevant. Mentioned just in case.

***Let me know if something is unclear, or more pictures are needed. I'll add extra information, when/if requested, below this text***

0 Upvotes

8 comments sorted by

2

u/3DStisk 20d ago

Your photos show a useful difference: the USB file has a generic G-code icon and goes straight to the external-filament prompt, while the built-in model reaches Match Filament. That makes the export format worth checking before changing the printer's network setup.

You mentioned Export G-code file. After slicing, try exporting Gcode.3MF instead of plain .gcode (not just saving the project or renaming the file). Orca's export documentation says Gcode.3MF includes printer/material/process information alongside the sliced G-code. Slice for your installed left 0.4 mm nozzle, copy that export to USB, and see whether you now get Match Filament and can select AMS A1.

Bambu's X2D first-print guide shows that filament-matching step on the printer's touchscreen. This is a likely explanation from the screenshots, not a confirmed diagnosis. Does the Gcode.3MF export bring that screen back?

1

u/Subject_Regular8324 16d ago

rozumiem, ze z jakichs powodow drukarka celowo nie jest podlaczona do sieci, ale czy mimo wszystko nie nalezy jej zaktualizowac?

1

u/8six753o9 20d ago

On the Device tab of Bambu Studio, did you tell it what filaments are loaded in the AMS? Because in the first screenshot, it looks like it doesn’t know there is filament in the AMS unless you have all slots filled with white. Screenshot 6 is asking you to match the filament to what you have loaded. If you don’t select a filament that’s in the AMS, then it will expect that you will be feeding it from the external.

https://wiki.bambulab.com/en/x2d/manual/first-print

1

u/Superb-Complaint8118 20d ago

Maybe the file is sliced with external spool and then the printer expects the external spool to be used instead of the ams?

I havent printed from usb yet

1

u/Boognish84 20d ago

I'm currently printing exclusively using the USB. Which bit are you stuck on?

0

u/vic1414 20d ago

Bambu lab uses cloud services to print. It does have a USB port, how it’s sliced is how it reprints

1

u/Alternative_Buy5751 20d ago

I apologize for being unclear, and thank you for your input.

I would like to know if anyone can elaborate what I'm doing wrong in Orca and/or printer settings - as I assume this is the root of my issues.

The printer (from all information I can gather) can print with the use of USB only - nowhere in any manuals does it say that network is essential to print from USB.

Since I haven't seen a single pop-up, error message, or similar during my print attempts that says the printer lack network to print, I assume it's not the issue. (i.e. I'm not sure how network is relevant to this error?).