search

Ankermgmt / ankermake-m5-protocol

Ankermake M5 protocol specifications and libraries *NOT AFFILIATED WITH ANKER*
GNU General Public License v3.0
161 stars 34 forks source link

everything is running now but i can't connect to the printer #49

Closed Jean0726 closed 1 year ago

Jean0726 commented 1 year ago

50 33 webserver test says ok but nothing arrives at the printer when I upload it with prusa

chrivers commented 1 year ago

This can typically happen, if the computer that runs ankerctl.py is not on the same wifi as the printer, or if you have some sort of firewall running, that is blocking the traffic.

The official AnkerMake Slicer supports relay mode (where the traffic is sent to AWS (Amazon Cloud) and back to the printer) if the printer cannot be contacted directly.

We don't support relay mode (yet), so this is a limitation for now.

Does that help?

austinrdennis commented 1 year ago

I get the same issue, but I'm definitely on the same wifi network. Does this not play nice with mesh clients?

chrivers commented 1 year ago

@austinrdennis can you do a wireshark capture while attempting this? Wireshark should be started before ankerctl, to ensure we see all traffic.

MEvansDCC commented 1 year ago

I am also having the same issue. I've connected my laptop (running the webserver) and the Anker to the same separate access point. And unfortunately the printer is not doing anything. I can however get a response from the command : "python .\ankerctl.py mqtt monitor" image

kivinen commented 1 year ago

This can also happen when the printers IP-address has changed, for example because the DHCP server decided to assign it different address than before. I think the current code still uses the ip-address it gets from the cloud and it can take days before the cloud backend gets up to date ip-address for the device.

So if you run config show and pppp lan-search and see if the ip-addresses are not same, if so then you need to manually edit the config file to fix the ip-address.

chrivers commented 1 year ago

Since this issue was originally opened, we have released version 1.0.0, which is a huge milestone for this project.

Countless improvements and bugfixes have been merged since this was last tested, so there's a chance that some of these issues are now fixed.

I'd encourage anybody who has seen this issue, to try the new version in web server mode.

It may just work - and if not, the three colored status icons in the web ui will paint a clearer picture of what the problem might be.

So if you have a chance, please try the new version, and report back what you see in the web ui (specifically, the red/yellow/green color for each status label)

MEvansDCC commented 1 year ago

Looks much better, but the webserver is not connecting over PPPP: image I must be missing something but not figured it out yet.

billyjbryant commented 1 year ago

This typically indicates that you have a communication problem with the printer. Either the printer is on a different network or your local firewall on your computer is preventing you from connecting.

MEvansDCC commented 1 year ago

Quite right! Failed at the first hurdle 😄 turned off firewall and it worked. So will need to make a rule.

chrivers commented 1 year ago

@MEvansDCC that's great to hear!

Unfortunately, the pppp protocol is tricky to firewall exactly. But at least, you can allow all UDP traffic, which covers all pppp, instead of allowing all protocols.

chrivers commented 1 year ago

I'm going to close this issue, since the original issue has been resolved for at least one of the reporters.

I encourage anyone who still has this problem, to try the new version 1.0.0, and see if that improves the situation.

If this problem surfaces with the new version, please open a new issue :)