Yet another WiFi issues post

U1 Toolchanger
1

Hi! I recently got myself a SnapMaker U1 and have overall been quite satisfied with it. The firmware installed when it arrived was 1.3.x, which I upgraded to U1_1.4.1.6_20260608141446_upgrade. The device is configured to connect to a (hidden) 2.4 Ghz network and is in LAN mode.

The device does not have internet access, it being in LAN mode, this shouldn’t be a problem. I also did not witness any connections outgoing from the printer to the internet.

The klipper UI works just fine. Pointing my browser to the UI of the printer works flawlessly and snappy, but the snapmaker orcaslicer does not. Upon an initial connection with the printer, the slicer gives me a green status icon and is happy, but within a few seconds (up to 30 seconds) the status icon turns orange and a message appears “Network unstable. Partial operation may failed” A few seconds later (up to 30) the printer disconnects from the slicer with a popup message “The device is currently processing the offline state, please check the device and try again” This popup allows me to do a network check.

I can reconnect as many times as I want, the resulting pattern is always the same. The network signal of the device was not bad (-57db), but to ensure the best possible connection (no wired ethernet :angry: ) I got myself another 2.4Ghz access point and put it next to the printer. The connection gives me a signal of -47 now, but still, the same issue persists.

Output of the network test:
Fri Jul 03 14:09:26:
Fri Jul 03 14:09:26: ========================================
Fri Jul 03 14:09:26: test LAN Device start...
Fri Jul 03 14:09:26: [test LAN Device]: server=192.168.8.21, port=1884
Fri Jul 03 14:09:26:
Fri Jul 03 14:09:26: --- Step 1: Network Layer Test (ICMP Ping) ---
Fri Jul 03 14:09:26:
Fri Jul 03 14:09:26: Starting ping test to 192.168.8.21...
Fri Jul 03 14:09:26:
[FAIL] Ping command failed or timed out
No output from ping command
Fri Jul 03 14:09:26:
Fri Jul 03 14:09:26: --- Step 2: Transport Layer Test (TCP Connection) ---
Fri Jul 03 14:09:26: DNS resolve time: 0 ms
Fri Jul 03 14:09:26: test LAN Device connected
Fri Jul 03 14:09:26: [OK] TCP connection established in 1 ms
Fri Jul 03 14:09:26: Total test time: 1 ms
Fri Jul 03 14:09:26:
Fri Jul 03 14:09:26: --- Test Summary ---
Fri Jul 03 14:09:26: [OK] Network Layer: Ping test completed (see RTT above)
Fri Jul 03 14:09:26: [OK] Transport Layer: TCP port 1884 is open and accepting connections
Fri Jul 03 14:09:26: Connection Quality: [Level 1] Excellent (RTT: 1 ms)
Fri Jul 03 14:09:26: test LAN Device ok ([Level 1] - Excellent, RTT: 1 ms)
Fri Jul 03 14:09:26: ========================================
Fri Jul 03 14:09:26:
Fri Jul 03 14:12:05:
Fri Jul 03 14:12:05: ========================================
Fri Jul 03 14:12:05: test Snapmaker Orca(GitHub) start...
Fri Jul 03 14:12:05: [test Snapmaker Orca(GitHub)]: url=https://github.com/Snapmaker/OrcaSlicer
Fri Jul 03 14:12:05:
Fri Jul 03 14:12:06: test Snapmaker Orca(GitHub) ip resolved = 140.82.121.4
Fri Jul 03 14:12:06: test Snapmaker Orca(GitHub) ok
Fri Jul 03 14:12:06: ========================================
Fri Jul 03 14:12:06:
Fri Jul 03 14:12:08:
Fri Jul 03 14:12:08: ========================================
Fri Jul 03 14:12:08: test Bing start...
Fri Jul 03 14:12:08: [test Bing]: url=http://www.bing.com
Fri Jul 03 14:12:08:
Fri Jul 03 14:12:08: test Bing ip resolved = 2.16.241.210
Fri Jul 03 14:12:08: test Bing ok
Fri Jul 03 14:12:08: ========================================
Fri Jul 03 14:12:08:
Fri Jul 03 14:12:09:
Fri Jul 03 14:12:09: ========================================
Fri Jul 03 14:12:09: test Cloud Server start...
Fri Jul 03 14:12:09: [test Cloud Server]: ``server=a1pr8yczi3n0se-ats.iot.us-west-1.amazonaws.com``, port=8883
Fri Jul 03 14:12:09:
Fri Jul 03 14:12:09: --- Step 1: Network Layer Test (ICMP Ping) ---
Fri Jul 03 14:12:09:
Fri Jul 03 14:12:09: Starting ping test to ``a1pr8yczi3n0se-ats.iot.us-west-1.amazonaws.com``...
Fri Jul 03 14:12:09:
[FAIL] Ping command failed or timed out
No output from ping command
Fri Jul 03 14:12:09:
Fri Jul 03 14:12:09: --- Step 2: Transport Layer Test (TCP Connection) ---
Fri Jul 03 14:12:09: DNS resolve time: 296 ms
Fri Jul 03 14:12:09: test Cloud Server connected
Fri Jul 03 14:12:09: [OK] TCP connection established in 169 ms
Fri Jul 03 14:12:09: Total test time: 466 ms
Fri Jul 03 14:12:09:
Fri Jul 03 14:12:09: --- Test Summary ---
Fri Jul 03 14:12:09: [OK] Network Layer: Ping test completed (see RTT above)
Fri Jul 03 14:12:09: [OK] Transport Layer: TCP port 8883 is open and accepting connections
Fri Jul 03 14:12:09: Connection Quality: [Level 3] Fair (RTT: 169 ms)
Fri Jul 03 14:12:09: test Cloud Server ok ([Level 3] - Fair, RTT: 169 ms)
Fri Jul 03 14:12:09: ========================================
Fri Jul 03 14:12:09:
Fri Jul 03 14:12:11:
Fri Jul 03 14:12:11: ========================================
Fri Jul 03 14:12:11: test Login API start...
Fri Jul 03 14:12:11: [test Login API]: url=https://id.snapmaker.com
Fri Jul 03 14:12:11:
Fri Jul 03 14:12:11: test Login API ip resolved = 104.18.21.166
Fri Jul 03 14:12:11: test Login API ok
Fri Jul 03 14:12:11: ========================================
Fri Jul 03 14:12:11:
Fri Jul 03 14:12:16:
Fri Jul 03 14:12:16: ========================================
Fri Jul 03 14:12:16: test Upload API start...
Fri Jul 03 14:12:16: [test Upload API]: url=https://public.resource.snapmaker.com
Fri Jul 03 14:12:16:
Fri Jul 03 14:12:16: test Upload API ok (403 - access restricted, but server reachable)
Fri Jul 03 14:12:16: ========================================
Fri Jul 03 14:12:16:

I noticed the “ping command failed” message, so I attempted to run ping from my terminal (same system). This passed without issue:
> ping 192.168.8.21
PING 192.168.8.21 (192.168.8.21) 56(84) bytes of data.
64 bytes from 192.168.8.21: icmp_seq=1 ttl=63 time=3.68 ms
64 bytes from 192.168.8.21: icmp_seq=2 ttl=63 time=22.1 ms
64 bytes from 192.168.8.21: icmp_seq=3 ttl=63 time=2.27 ms
64 bytes from 192.168.8.21: icmp_seq=4 ttl=63 time=1.63 ms
64 bytes from 192.168.8.21: icmp_seq=5 ttl=63 time=1.81 ms
64 bytes from 192.168.8.21: icmp_seq=6 ttl=63 time=64.2 ms
^C
--- 192.168.8.21 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 1.630/15.946/64.225/22.768 ms

What could the issue still be?

2

Only for troubleshooting, does it work if you let it access the internet?

3

Hello @xchrisd , Thanks for helping to think about the issue.
I’ve added a firewall rule allowing any traffic coming from the printer, but the issue persists. I haven’t inspected the traffic yet as I’m a bit under time pressure today, but yesterday I found this promising github issue: U1 LAN connection flaps continuously — Home + Device MQTT sessions share one clientId and evict each other (0 heartbeats succeed on a 0% packet-loss LAN) · Issue #497 · Snapmaker/OrcaSlicer · GitHub

The problem description is not entirely the same, as the reporter describes the connection to be flapping (on/off/on/off), where my connection first “degrades” and then goes down.

I have now also attached an USB ethernet dongle. This results in the same behaviour. From this I can conclude it’s not a wifi/device issue, but most probably an issue with the slicer/device firmware.

4

Hi there. Thanks for posting this. I am having the exact same issue. You compelled me to sign up here while I was looking for solutions. I thought the USB dongle would solve this. I have some other suggestions I am going to try. I tried both LAN mode and cloud mode with the same issues. My firewall doesn’t block the printer at all. I have made a wifi network just for it. Another user suggested getting an AP with solely for the printer. I have one and will try that as well. By any chance do you use Unifi (Ubiquiti) Network gear? Thats what I have at home and I fear there could be some settings causing the issues. I will update what I find. This is a new printer I just opened yesterday.

5

Do you have the same issues if you use vanilla Orca? Just to see if there might be a bug in SnOrca?

6

I haven’t tried that. I will try that as well because I’m not confident my other plans will work. Thanks.

7

I wanted to update you guys. I solved the issue for my printer with some suggestions from here. Firt I made a seperate wifi network just for the U1. Its only 2.4ghz with some options for older devices. I have several access points in my network but I only gave this network access to the access point nearest the printer this way it does not have to roam between other access points. Its the only device on this network and I noticed improvements immediately. I was able to connect to the printer quickly and the “Unstable Network” messages have gone. Let me know if you have any questions.