Hobby V2.4 about a year old probably has ~40 hrs on it. Recently updated klipper firmware with a bit of heartburn but got through it. Printed a thing or two, then the printer sat for a month or so. Powered on a few days ago to do a job and no joy. Cant connect to mainsail/pi on wifi via pi’s ip address, have not tried ethernet. SSH will not connect as well. Checked the sd card on the pi and wifi info is correct as is the ip address. Router shows that pi is connected to wifi. Still fairly new to this wondering what the best path forward is for diagnosis? I have some fairly recent cfg backups, maybe need to reinstall mainsail? Reinstall os on the pi?(btt cb1 in my case) Any additional questions please ask! TIA
#mainsail/pi issue
14 messages · Page 1 of 1 (latest)
if it has an ip address, and you still can't even ssh in, that sounds more likely to be an overall issue with your network, than an issue with the printer...
what is the ip address?
what is the ip of the machine you're coming from?
can you ping from one to the other?
Thank you @silent hollow for the response! FWIW nothing has changed to my knowledge with regard to our home network. Also, from the list of connected devices to the router, none possess the same address as the printer. Now to answer your questions,
Ip of the printer is 192.168.68.110
Ip of computer is 192.168.1.154
Ping results from pc to printer is timed out x 4, 4 sent 0 rec’d
Pings to other devices give the same failed results… seems it may very well be a network issue as you say… could it have something to do with the pc’s assigned ip? All the other devices on the network mimic the printer with the suffix .103, .104 etc
so... 192.168.68.* is almost certainly a different network than 192.168.1.*
maybe wired devices are being separated from wireless or something?
maybe something (the printer) has accidentally been moved to an isolated IOT/guest/something network?
Wireless mesh perhaps but the pc and printer should be on the same hub, perhaps i should try to force them onto one particular hub
worth a shot. mesh device might be running a separate network rather than a proper mesh
I'm pretty sure the problem is something of that kind though
whether it's related to the mesh device, or something else. when you get the printer to pull a 192.168.1.* address, I think that's when you know its fixed, at any rate
Will do, thank you again for your help!