Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A new Klipper webinterface #2

Closed
mbgroot opened this issue Jul 29, 2020 · 5 comments
Closed

A new Klipper webinterface #2

mbgroot opened this issue Jul 29, 2020 · 5 comments
Labels
Type: Feature Request New feature or request

Comments

@mbgroot
Copy link

mbgroot commented Jul 29, 2020

Maybe you would like to add Mainsail webui to the script ?
https://github.com/meteyou/mainsail

@lixxbox
Copy link

lixxbox commented Jul 29, 2020

Checkout his dev-2.0 branch 😋

https://github.com/th33xitus/kiauh/tree/dev-2.0

@dw-0 dw-0 added >>> fixed! Type: Feature Request New feature or request labels Jul 29, 2020
@dw-0
Copy link
Owner

dw-0 commented Jul 29, 2020

Like lixxbox said, this feature is already available in the dev-2.0 branch.
I haven't merged, or rather made it to the new master yet but i will probably do in the next few days.

@mbgroot
Copy link
Author

mbgroot commented Jul 29, 2020

It's not working yet. - Klipper3d/klipper#3026 (comment)

@dw-0
Copy link
Owner

dw-0 commented Jul 29, 2020

It is working. But there is a restriction on Mainsail/Moonraker side.
Currently that webinterface only works with a special fork of klipper made by Arksine:
https://github.com/Arksine/klipper/tree/dev-moonraker-testing
You have to have this version of Klipper active before you can use Mainsail.

My script actually won't allow you to install Mainsail without being on the correct Klipper Version.
Please use KIAUH for changing the Klipper version, because it will add the remote with a specified name. That's the only way the script can tell if you are on the right version or not, and therefore either decline or allow installation.

As long as all the important parts of dev-moonraker-testing are not merged into the mainline, we have to use the corresponding Klipper fork.

Same goes for people currently using the s-curve smoothing or shaping branch of dmbutyugins fork of Klipper. There will be no way they can use Mainsail as long as the important bits and pieces which are needed for Moonraker are not merged into their forks.

Im sorry, that is nothing i can fix or help with. Thats the way it is for now.... we just need to give the Klipper Devs a little bit more time until they fully implement the Moonraker support. For the meantime there is still the option to use DWC2 or OctoPrint.

@mbgroot
Copy link
Author

mbgroot commented Jul 29, 2020

Sorry, didn't give the right address in trusted_clients.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Request New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants