You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some API routes are missing from the new API, I'm working on a project and have looked at the openapi files on how to control my Prusa Mini. The legacy API provided ways to move the printhead in the openapi legacy file but not in the current openapi file.
I am attempting to send API requests through python to move the printhead but, sending a request to the legacy API endpoint results with a 401 error, I fixed this with correct and tested Digest authentication. This new authentication results in a 404 error. I know it is possible to do this as I can via the Prusa connect control screen:
This is a half-working implementation that I made in python:
This approach works but has many issues, the biggest one being once the gcode file has finished "printing", it will park the print head which can get in the way. Any help with this issue or support about an API endpoint would be greatly appreciated!
EDIT
I have recently switched to the PrusaLinkPy module, this has helped improve efficiency, but still has issues such as the print head parking and the lack of the ability to move the printhead directly
The text was updated successfully, but these errors were encountered:
NovodoOfficial
changed the title
No way to move the printhead
API routes invalid for some things in the new API
Dec 4, 2024
Some API routes are missing from the new API, I'm working on a project and have looked at the openapi files on how to control my Prusa Mini. The legacy API provided ways to move the printhead in the openapi legacy file but not in the current openapi file.
I am attempting to send API requests through python to move the printhead but, sending a request to the legacy API endpoint results with a 401 error, I fixed this with correct and tested Digest authentication. This new authentication results in a 404 error. I know it is possible to do this as I can via the Prusa connect control screen:
This is a half-working implementation that I made in python:
This approach works but has many issues, the biggest one being once the gcode file has finished "printing", it will park the print head which can get in the way. Any help with this issue or support about an API endpoint would be greatly appreciated!
EDIT
I have recently switched to the PrusaLinkPy module, this has helped improve efficiency, but still has issues such as the print head parking and the lack of the ability to move the printhead directly
The text was updated successfully, but these errors were encountered: