Well… it seems that neither Creality print nor CURA can see the printer. I can ping it through command line no problem, so what the hell is hoing on here?
For thouse who may ask Im on Ehternet printer is on Wifi, but that should not make any difference.
Getting pretty fed up here.
Can you get to Fluidd that’s running on the K2 via a web browser? ip-address:4408
I’m not sure if 4408 is the standard port Fluidd normally runs on or not, but it’s what’s being used on the K2. I’m currently using Orca slicer, pointed at my K2’s IP at port 4408, and it connected it that way. When I initially used Creality Print, it didn’t stay connected (like you, computer on ethernet, printer on wifi). After the K2 finally performed a FW update, the connection was more stable.
I don’t know if the printer has a “sleep” like mode or not, but I had better luck initially connecting the the printer shortly after powering it on.
I had a similar problem lately. Creality Print was not able to detect the K2 even if my router and K2 showed a perfect WLAN connection. And also the Creality Cloud worked perfectly on the PC or App.
The solution: I connected the K2 via a 2.4GHz SSID of my access point and it worked right away.
Both printer and computer or phone have ti be on thd same network ti see each other. If yiu have several networks such as separated 2.4 and 5ghz bands make sure yiu use thd same one
1 Like