Thomas Reitmayr

I opened this PR almost one month ago, and while I admittedly added more changes later on, there was no comment to the specific code changes or prospects for when...

> Uploading files from prusaslicer gets stuck on "RESOLVING ADDRESS". This is very likely an issue of PrusaSlicer and not of this PR or ancertctl in general, see https://github.com/prusa3d/PrusaSlicer/issues/10944 ....

This and other PRs are now incorporated in https://github.com/anselor/ankermake-m5-protocol/tree/exiles-1.1 . Unfortunately, I have to admit that the documentation is still not up to date and matching the now recommended way...

There usually seem to be two possible issues resulting in the above error: * The printer IP address is not configured. @revil-O it seems that this is your problem because...

This is also fixed in PR #145 in a way which supports both Ankermake M5 and M5C printers, see https://github.com/Ankermgmt/ankermake-m5-protocol/pull/145/commits/d9af57732b163ed81115dab0dea6386c3e564530 . You can try the fork at https://github.com/anselor/ankermake-m5-protocol/tree/exiles which integrates...

It looks like the IP address of your printer ist not set in ankerctl's configuration. You can confirm that by typing `python ankerctl.py config show` ~As we just discussed this...

I just opened PR #150 which will add the possibility to set and update the printer's IP address via CLI and web interface. This should make it easy to fix...

My understanding is that the gcode is sent directly to the printer, not via the AnkerMake cloud service. At least that is my experience with a missing printer IP address...

Updated the PR because I saw commit https://github.com/Ankermgmt/ankermake-m5-protocol/commit/2add2e60bb66f5ae369aefe7ed3f8cb9a087a255 and used its (proper) way of displaying the modal popup with varying messages instead of duplicating it.

Fixes #109, #152.