-
-
Notifications
You must be signed in to change notification settings - Fork 392
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* fix: replace tab characters by spaces Signed-off-by: Dominik Willner <[email protected]> * fix: replace tab characters by spaces Signed-off-by: Dominik Willner <[email protected]> * feature: add lockable sliders Signed-off-by: Dominik Willner <[email protected]> * feat: add lockable sliders feat: add auto-lock sliders Signed-off-by: Dominik Willner <[email protected]> * locale: add EN locale for LockSlider and AutoLockSlider features. Signed-off-by: Dominik Willner <[email protected]> * chore: rename autoLockSliders to lockSliders refactor: include startLockTimer method in sendCmd method Signed-off-by: Dominik Willner <[email protected]> * refactor: refactor startLockTimer method Signed-off-by: Dominik Willner <[email protected]> * refactor: lockSlidersChanged Watcher Signed-off-by: Dominik Willner <[email protected]> * refactor: remove helper, use new isTouchDevice BaseMixin method instead Signed-off-by: Dominik Willner <[email protected]> * feat: add lockable sliders to miscellaneous sliders Signed-off-by: Dominik Willner <[email protected]> * fix: every interaction with the slider resets timeout correctly Signed-off-by: Dominik Willner <[email protected]> * fix: fix typo Signed-off-by: Dominik Willner <[email protected]> * chore: remove unused import Signed-off-by: Dominik Willner <[email protected]> * chore: remove unused import Signed-off-by: Dominik Willner <[email protected]> * chore: replace tabs with spaces Signed-off-by: Dominik Willner <[email protected]> * chore: replace tabs with spaces / remove trailing newlines Signed-off-by: Dominik Willner <[email protected]> * refactor: rename name/value pairs to a more appropriate name Signed-off-by: Dominik Willner <[email protected]> * refactor(locale): update EN locale file Signed-off-by: Dominik Willner <[email protected]> * fix: get/set correct store name Signed-off-by: Dominik Willner <[email protected]> * refactor: use "Delay" instead of "Timeout" Signed-off-by: Dominik Willner <[email protected]> * refactor(locale): update EN locale file Signed-off-by: Dominik Willner <[email protected]> * refactor(locale): update DE locale file Signed-off-by: Dominik Willner <[email protected]> * refactor: rename menuStyle to navigationStyle Signed-off-by: Dominik Willner <[email protected]>
- Loading branch information
Showing
17 changed files
with
3,580 additions
and
3,199 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,48 +1,48 @@ | ||
--- | ||
layout: default | ||
title: Command format mismatch | ||
parent: Klipper Errors | ||
grand_parent: FAQ | ||
nav_order: 10 | ||
has_children: false | ||
permalink: /faq/klipper_errors/command_format_mismatch | ||
has_toc: false | ||
description: >- | ||
You have updated Klipper and now you get this cryptic error message? We would like to help... | ||
--- | ||
|
||
# Klipper Error - Command format mismatch | ||
|
||
You have updated Klipper and now you get this cryptic error message? | ||
|
||
![Command format mismatch](../../assets/img/faq/errors/mcu_error.png) | ||
|
||
This is an error and needs to be fixed to make Mainsail and Klipper work again. | ||
{: .info} | ||
|
||
## TL;DR | ||
|
||
Klipper on your host and on your MCU have different versions. | ||
Recompile and flash your MCUs and it will work again. Please also pay attention to the "Linux MCU", if you had e.g. an adxl345 in use. | ||
|
||
The following links should help you to solve the problem: | ||
[Klipper SD-Card Updates](https://www.klipper3d.org/SDCard_Updates.html){:target="_blank"} | ||
[Klipper Building and flashing the micro-controller](https://www.klipper3d.org/Installation.html#building-and-flashing-the-micro-controller){:target="_blank"} | ||
|
||
## More detailed | ||
|
||
Klipper consists of two parts: | ||
The software on your host (e.g. Raspberry Pi) and the firmware on your microcontroller (MCU). | ||
|
||
Under normal circumstances, Klipper (on your host) can simply be updated from Mainsail without any problems and everything will work as expected. | ||
|
||
From time to time it happens that there are changes in Klipper that make it necessary to update all your MCUs. Assuming you have run a Klipper update and Klipper on your host now supports commands that your MCUs does not understand. Then you will get the above error message. | ||
|
||
Fortunately, these kind of updates don't happen very often, but now it has happened to you. ;-) | ||
|
||
In order to solve the problem, you need to update all your MCUs. We are talking about multiple MCUs here, as people tend to forget that they have multiple microcontrollers in use. One of these candidates is the "Linux MCU" that many people install on their Raspberry Pi to measure resonances with an adxl345. | ||
|
||
Detailed information on how to update the firmware can be found in the Klipper Documentation linked above (under TL;DR). | ||
|
||
As far as we know, work is in progress to let Klipper update the firmware on its own. | ||
--- | ||
layout: default | ||
title: Command format mismatch | ||
parent: Klipper Errors | ||
grand_parent: FAQ | ||
nav_order: 10 | ||
has_children: false | ||
permalink: /faq/klipper_errors/command_format_mismatch | ||
has_toc: false | ||
description: >- | ||
You have updated Klipper and now you get this cryptic error message? We would like to help... | ||
--- | ||
|
||
# Klipper Error - Command format mismatch | ||
|
||
You have updated Klipper and now you get this cryptic error message? | ||
|
||
![Command format mismatch](../../assets/img/faq/errors/mcu_error.png) | ||
|
||
This is an error and needs to be fixed to make Mainsail and Klipper work again. | ||
{: .info} | ||
|
||
## TL;DR | ||
|
||
Klipper on your host and on your MCU have different versions. | ||
Recompile and flash your MCUs and it will work again. Please also pay attention to the "Linux MCU", if you had e.g. an adxl345 in use. | ||
|
||
The following links should help you to solve the problem: | ||
[Klipper SD-Card Updates](https://www.klipper3d.org/SDCard_Updates.html){:target="_blank"} | ||
[Klipper Building and flashing the micro-controller](https://www.klipper3d.org/Installation.html#building-and-flashing-the-micro-controller){:target="_blank"} | ||
|
||
## More detailed | ||
|
||
Klipper consists of two parts: | ||
The software on your host (e.g. Raspberry Pi) and the firmware on your microcontroller (MCU). | ||
|
||
Under normal circumstances, Klipper (on your host) can simply be updated from Mainsail without any problems and everything will work as expected. | ||
|
||
From time to time it happens that there are changes in Klipper that make it necessary to update all your MCUs. Assuming you have run a Klipper update and Klipper on your host now supports commands that your MCUs does not understand. Then you will get the above error message. | ||
|
||
Fortunately, these kind of updates don't happen very often, but now it has happened to you. ;-) | ||
|
||
In order to solve the problem, you need to update all your MCUs. We are talking about multiple MCUs here, as people tend to forget that they have multiple microcontrollers in use. One of these candidates is the "Linux MCU" that many people install on their Raspberry Pi to measure resonances with an adxl345. | ||
|
||
Detailed information on how to update the firmware can be found in the Klipper Documentation linked above (under TL;DR). | ||
|
||
As far as we know, work is in progress to let Klipper update the firmware on its own. | ||
{: .info} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.