constant disconnects and wifi issue after 1.2.0 updatre

[ares0027]

My printer is not that old, it had 1.0.0 stock, then upgraded it to 1.1.1 extended and then an hour ago i upgraded it to 1.2.0 extended. since then i have huge spikes on connection.

Pinging 192.168.1.140 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.140: bytes=32 time=302ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.140: bytes=32 time=13ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=3ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=3ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=3ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=7ms TTL=64
Reply from 192.168.1.140: bytes=32 time=6ms TTL=64
Reply from 192.168.1.140: bytes=32 time=3ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=4ms TTL=64
Reply from 192.168.1.140: bytes=32 time=1436ms TTL=64
Reply from 192.168.1.140: bytes=32 time=20ms TTL=64
Reply from 192.168.1.140: bytes=32 time=4ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=41ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=5ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=6ms TTL=64
Reply from 192.168.1.140: bytes=32 time=10ms TTL=64
Reply from 192.168.1.140: bytes=32 time=9ms TTL=64
Reply from 192.168.1.140: bytes=32 time=5ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=899ms TTL=64
Reply from 192.168.1.140: bytes=32 time=8ms TTL=64
Reply from 192.168.1.140: bytes=32 time=1ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=1754ms TTL=64
Reply from 192.168.1.140: bytes=32 time=21ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=1969ms TTL=64
Reply from 192.168.1.140: bytes=32 time=40ms TTL=64
Reply from 192.168.1.140: bytes=32 time=144ms TTL=64
Reply from 192.168.1.140: bytes=32 time=1970ms TTL=64
Reply from 192.168.1.140: bytes=32 time=48ms TTL=64
Reply from 192.168.1.140: bytes=32 time=16ms TTL=64
Reply from 192.168.1.140: bytes=32 time=6ms TTL=64
Reply from 192.168.1.140: bytes=32 time=36ms TTL=64
Reply from 192.168.1.140: bytes=32 time=11ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=4ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=3ms TTL=64
Reply from 192.168.1.140: bytes=32 time=22ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=5ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Request timed out.
Reply from 192.168.1.140: bytes=32 time=889ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=35ms TTL=64
Reply from 192.168.1.140: bytes=32 time=1ms TTL=64
Reply from 192.168.1.140: bytes=32 time=8ms TTL=64
Request timed out.
Reply from 192.168.1.140: bytes=32 time=777ms TTL=64
Reply from 192.168.1.140: bytes=32 time=3ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=1814ms TTL=64
Reply from 192.168.1.140: bytes=32 time=65ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=3ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=5ms TTL=64
Reply from 192.168.1.140: bytes=32 time=15ms TTL=64
Reply from 192.168.1.140: bytes=32 time=7ms TTL=64
Request timed out.
Reply from 192.168.1.140: bytes=32 time=1780ms TTL=64
Reply from 192.168.1.140: bytes=32 time=8ms TTL=64
Reply from 192.168.1.140: bytes=32 time=7ms TTL=64
Request timed out.
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=20ms TTL=64
Request timed out.
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=3ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=3ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.140: bytes=32 time=3ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.140: bytes=32 time=131ms TTL=64
Reply from 192.168.1.140: bytes=32 time=1ms TTL=64
Reply from 192.168.1.140: bytes=32 time=2ms TTL=64
Reply from 192.168.1.140: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

i DID NOT try with stock 1.2.0 i can if that is what you need.

[paxx12]

yes, always confirm with stock first

[ares0027]

yes, always confirm with stock first

i have a print right now so i will try it when it is done but is this right? it says 1.1.1 https://i.imgur.com/Da98ea9.png when i am on 1.2.0 https://i.imgur.com/RCwiayA.png

[Mascot68]

I don't know if this might be helpful or not, but when I got my U1 I had a lot of wifi issues with stock 1.1.1. They vanished the moment I switched to 1.1.1-extended. I've not tested 1.2.0 yet, stock or otherwise.

[plastikman]

I was unable to use Wifi on my unit stock 1.1.1 and extended 1.2.0, until I made a split 2.4/5G network. I am using Orbi Pro 6 access points. try making a split 2.4/5G setup and see if it helps.

[Mascot68]

try making a split 2.4/5G setup and see if it helps.

If this was in response to me, then I've always had separate 2.4/5GHz networks. I guess I'll just have to temper my expectations of 1.2.0 and be prepared for the eventuality that I'll need to stick with 1.1.1.

[drzeller]

I stopped getting the errors by assigning an IP to the printer in my router. I was also using QIDI Studio (for the Q1 Pro) when getting most of the errors, so I can't conclusively state that the fixed IP resolved it, as I have not used QIDI much the past few days.

[physicsG]

I stopped getting the errors by assigning an IP to the printer in my router. I was also using QIDI Studio (for the Q1 Pro) when getting most of the errors, so I can't conclusively state that the fixed IP resolved it, as I have not used QIDI much the past few days.

I have a similar experience and my U1 now connects reliably to the 2.4 GHz network after assigning a fixed IP in the router.