Report Your Snapmaker U1 Connectivity Issues and Help Us Improve — $30 Gift Card for Useful Reports

[Zoe_M]

Hi everyone,

If you’ve run into connectivity problems with your Snapmaker U1, we want to hear about your experience and better understand these cases.

We’re running a focused effort to track down U1 connectivity issues, and submitted reports will help our software and firmware engineers analyze different scenarios. These issues can involve multiple factors, including device status, firmware versions, network environments, and system configurations.

If you have experienced issues such as:

• Device cannot be discovered or connected
• Device frequently goes offline or disconnects
• Print tasks fail or get stuck during transmission
• Snapmaker Orca-related issues (such as connection, loading, or display problems)
• Connection problems after firmware/software updates
• Other connection-related issues

please share your experience through the survey.

The survey covers:

• Device information and software/firmware versions
• Network and connection environment
• Steps to reproduce the issue
• Screenshots, videos, or logs (if available)

The survey may take around 20 minutes to complete, depending on your situation and the information you can provide. More detailed information will help our team analyze the issue more efficiently.

Survey link:

https://snapmaker.formcrafts.com/snapmaker_connectivity_issue_en

As a thank-you for your support, submissions that provide actionable details and are confirmed useful for software team analysis may receive a $30 gift card after review.

Thank you for helping us improve the Snapmaker U1 connectivity experience. Your detailed reports will help our team better understand real-world usage scenarios and make future improvements.

[Trip]

Hello Zoe,

I was trying to go through the survey, but since I wasn’t encountering any issues, I couldn’t follow the survey steps. Therefore, I’m replying here because I wanted to provide feedback anyway.

I bought my machine from Microcenter on May 30, and it connected to my network without any problems. I have an Eero Pro 7 router sitting near it so that may be why I had no issues. Initial setup went well, except for an issue with Toolhead 4 during the initial filament loading, however, it worked after a couple of tries.

I’m using Linux (CachyOS) and tried installing Snapmaker Orca using the native package but the application had issues launching. It was crashing and had some UI inconsistencies, mainly my account was not being stored, forcing me to re-enter my credentials every time I opened the application, which was time-consuming and annoying. I then switched to using the AppImage and it started working just fine. I noticed, however, that intermittently the upload process to send gcode to the printer would hang and/or take too long to complete. Canceling and re-trying fixed the issue.

I tried connecting the app, and it worked but since I’m not used to using apps for my 3D printers, I stopped using it. I don’t have much feedback other than that the features appeared to be very basic.

I then switched the firmware to Paxx12 1.4.2 and I’m using it so far. Paxx12 firmware offers 2 main functionalities missing from the main firmware: an improved camera and remote access to the printer screen. If you could make this a baseline feature, that would be great as I don’t need the other Paxx12 features.

I then switched to LAN mode to keep my printer information local and also switched to regular Orca 2.4. Both are working flawlessly so far. Since using Paxx12 firmware and Orca 2.4 the intermittent hangs while sending gcode to the printer haven’t happened anymore. Even in the few times I still use Snapmaker Orca, I haven’t noticed any hangs anymore.

I know that this is not exactly what you guys were looking for, but I wanted to provide this feedback anyway. I hope it helps.

Best Regards.

Wilson Laizo Filho

[brawlspecials]

Thanks for putting this survey together and actively gathering data on this issue!

I’ve been running into [insert issue: e.g., frequent Wi-Fi disconnections in Cloud Mode / failure to discover the printer on Snapmaker Orca in LAN mode]. My printer usually loses connection right around [insert timing: e.g., starting a print / after coming out of sleep mode]. - Nulls Brawl Mods

I just completed the survey with my log files, router specs, and firmware details attached. Hope this helps the engineering team squash these bugs soon!

[xchrisd]

Great step forward to get a more stable, improved and userfriendlier machine! Congrats to this step.

[RogerT]

When I try to connect to my U1 I get an error message that says “The device communications failed, please check whether the device is normal and unresponsive.” I checked while the device was printing a file. How do I check if the device is normal and unresponsive? When I check at my printer it shows it is on line to my network.

Thanks for your help.

Ever Grateful

Roger T

rtrant@telus.net

[tinkerbarn]

Hi @Zoe_M,

Unfortunately, the survey form has too many mandatory fields that don’t fit all use cases. For example, being forced to enter the App Version even when the app isn’t used at all.

Generally, I had major issues with the mesh network in my house. The U1 is located about 2 meters away from an AVM Fritzbox, which is part of a mesh network consisting of another Fritzbox and two repeaters.

After about 2–3 days of operation, the U1 suddenly connected to a repeater located about 30 meters away, with two stone walls in between. As a result, the signal quality was extremely poor. Even after restarting the U1, it immediately reconnected to that same repeater, despite the router being only 2 meters away.

The WLAN configuration should display the strongest router and offer the option to configure a BSSID, so that the printer’s WLAN connects exclusively to that router, even if other routers/repeaters are detected.

I solved this for myself by using a USB-to-Ethernet adapter and connecting the U1 to the router via a LAN cable. The U1 is configured for local network only, with no cloud connection.

I suspect that other users will also have problems with mesh networks.

Best regards,

Tinkerbarn

[MAGNAC]

Onward to a machine that will become increasingly stable and functional! Bravo to the entire Snapamker staff for their dedication!

[Zoe_M]

Hi, is the printer set to “LAN mode”?

If yes, you can find the IP address on the U1, then try to ping irs IP address to check the connection stability:

If it in cloud mode, you can refer to this link to check cloud server status:https://wiki.snapmaker.com/en/snapmaker_orca/unstable_connection

[Zoe_M]

Yeah, mesh networks are pretty common in home setups now. I don’t think the U1 supports fast roaming, and it probably won’t switch between nodes automatically.
Is the U1 the only device connected to the farthest mesh node?
I was wondering if the nearest node had too many 2.4 GHz devices, causing the router to spread the load around.

[BoCu]

I’m cancelling my order for my second U1. If I can’t send a print to the machine it is worthless. To sit there and click PRINT and have the software completely ignore you is UNACCEPTABLE. No error message. Just ignore the user.

[BoCu]

Agreed. As soon as I got to serial number I backed out. You don’t need my serial number to know that this product has MAJOR ISSUES.

[tinkerbarn]

Sorry for the late reply.

No, it’s not just the U1 that connects to the remote router/repeater. It also includes several RFID remote readers based on the ESP32 that I developed myself.

I’ve since solved this by displaying the three strongest Wi-Fi sources in the area and defining which source is used as primary and which as secondary via BSSID. Since then, these devices are no longer reassigned by the FRITZ!Box.

I don’t believe it’s exclusively an issue with the U1. However, one could allow users to assign the U1 to a specific Wi-Fi router/repeater via an extended menu and reconnect it if it’s no longer connected to that target.

[tinkerbarn]

The serial number can indeed be interesting for narrowing down the error. Manufacturers often use different revisions of, for example, mainboards or other hardware components during production. This is because feedback may already be incorporated into the design/firmware, or a supplier may no longer be able to deliver the originally specified hardware component and thus installs an alternative.

Based on the feedback, it can then be narrowed down that perhaps only Batch 1 with Revision X is affected.

However, the further questions in the form were unfortunately often mandatory and did not always fit, making it difficult to describe the individual problem.

[Zoe_M]

I agree. This would be really helpful for the Mesh network. I’ll forward it to the firmware team.
You might also want to post a feature request here (Feature Request - Snapmaker: where creation happens), so other users facing similar situations can upvote it.

[tinkerbarn]

Done

Preferred Wi-Fi Access Point (BSSID) Selection for Mesh Networks

Feature Request, Preferred Wi-Fi Access Point (BSSID) Selection for Mesh Networks. Many U1 users experience unstable Wi-Fi in mesh environments because the printer sometimes roams to a distant access point with the same Wi-Fi name. A BSSID is the unique hardware address of a single access point— think of it like choosing a specific entrance to a building, rather than just the building name. Please add an Advanced Wi-Fi option that shows the 3 to 4 strongest BSSIDs for the selected network and le…

[V1nce_78]

I had a connection issue today, that was way more intrusivve then the other ones (I usually have a few times each week). Today SnOrca and the Android app both said they couldn’t connect. But I could pring it without a problem. Also the U1 itself says on its display it is conencted (and shows a green marker). The webinterface could also be used.

Restarting SnOrca didn’t change anything. I tried turning off and on again the WiFi on the U1, that didn’t change anything. Snorca and the app still couldn’t connect. What i found strange, is that when I open the Android App, it gave the option to reconfirm the bind with the U1. That part DID work. On the U1 there was a pop-up that asked ‘request connection’ on which I pressed OK.

But that changed nothing. The app could connect. Restating SnOrca again on te pc, no succes.

On the webinterface i tried a host restart. That didn’t do anything. I tried a Host shutdown, that also didn’t do anything. (The U1 didn’t go down).

But(!) when I clicked in the U1 webinterface restart klipper (on the system tab). it said after clicking, klippy is not connected. (and on the webinterface nothing looked different.

Also nothing changed on the snapmaker display (I was still ont the same menu item (network).

But pinging the U1 missed 1 ping. (I was pringing the U1 for over 20 minuties now, it had missed not 1 singe ping, untin now, 1 missed 1, only 1.

But right after that 1 missed ping, the U1 could be reached again.

And when I tried clicking connect in SnOrca this time it did connect succesfully!. I could activate the camera, and everything worked again.

-

Don’t know if this situation will help, but I made many screenshots and pictures of the U1 display during this situation. And I could provide the logfiles if wanted.

I will also fill in the survey.

[xchrisd]

Did you open a ticket about?

U1 Troubleshooting Request

Nevermind, i Just found your thread about.