Hi everyone,
I’m experiencing an issue connecting my Bambu Lab X1E to a standalone PC (that’s disconnected from the internet). The X1E is connected directly to the PC via an Ethernet cable.
The Bambu Studio successfully recognizes the X1E.
However, when attempting to connect, the process starts but then fails to complete.
Has anyone encountered this problem before, or have any ideas on what might be missing in the configuration?
Any help would be greatly appreciated!
Until you find a solution (or someone else help find it), you may want to print your files from your SD card.
At the very least, a direct Ethernet connection (no router), will require manually assigned IP addresses and subnet masks for both the X1E and the Ethernet adapter on the PC.
Section 3 here should help with the X1E.
I did this, and it allowed the printer to be recognized by the computer and software, but it still fails to connect to the printer.
Same issue. Standalone pc and not able to connect. Has anyone actually ever connected to an X1E? These threads seem to never get an answer. Is this real life?
If you’re expecting an answer from BL on this forum, then you’ve had to high hopes. You may open a ticket with them, requesting for an answer, but then again wouldn’t recommend making to many hopes either…
Have you tried contacting the reseller you bought the printer from? That should be your first contact.
@JonRaymond is correct. It should be noted that when Bambu released the X1E, the dramatic difference, unlike their other products, is that it would be “solely” supported by their channel partners. This is noteworthy because it is almost an about-face from their direct-to-market business model for the rest of their product line. It is also for this reason, as well as the fact that far fewer X1Es were shipped, that this forum doesn’t have many resources to address the X1E.
However, sometimes the simple things are what matters…like, using a standard EN cable without reversing transmit and receive pairs on one end…Did you check? are you seeing the EN lights blink on both ends, the printer and the PC? connecting transmit to transmit and receive to receive won’t work.
It’s 2024. Everything has Auto-MDX capability. Crossover Ethernet cables are not necessary.
You are correct, MDI-X since 1998, been awhile I was in IT.
Whoops, MDX is an Acura automobile. This alphabet soup of initialisms and acronyms, who can keep up?
lol, I guess that for the US-based guys this 3-letter (or more) acronym thing comes easier, as they are already accustomed with; NSA, FBI, CIA, DMV, FEMA, etc…
For the test of us, I guess we’re going to need acronym dictionaries to keep up.
