Updating to 2.1 configuration issue
Error message is advising Pin PF2 used multiple times in the configuration.
Attached is my previous overides secition and the error message, the error message and the configuration options I selected
![No description](https://cdn.answeroverflow.com/1262903000721260564/Useroverides_2024-07-17_090412.png)
![No description](https://cdn.answeroverflow.com/1262903000972656720/Screenshot_2024-07-17_103939.png)
![No description](https://cdn.answeroverflow.com/1262903001266520125/install_config_2024-07-17_102659.png)
31 Replies
make a text search for PF2 in ratos.cfg and printer.cfg
Nothing in printer.cfg
Appears twice in ratos.cfg
![No description](https://cdn.answeroverflow.com/1262906001468817469/image.png)
I am not sure how to correct this. I am using and SKR Pro 1.2
yeah, this is likely a bug @miklschmidt
you can outcomment the aliases, they are only there for backwards compatibility, you dont need them
then it should work
Thanks. I am not sure how to do that?
jsut put a
#
in front on one of these two appearancesLike this?
![No description](https://cdn.answeroverflow.com/1262907150129172540/image.png)
yes
you ened to redo this once you update ratos or change something in the config bc the file will be regenerated
but im sure mikl will fix it soon
Hmmm....still get this after saving changes and restarting.
![No description](https://cdn.answeroverflow.com/1262907367868071957/image.png)
restartklipper
and double check for more appearances
Still got issues and yes there are more appearances. I am updating RatOS configurator and other options before going further.
Will re run configuration in a couple of minutes...
Updating got rid of the multiple appearances...and that error message.
Now I can move on to calibration stuff,
Thanks for your help.
oh wait is this a new V2.1 install?
if yes, then you shoul dhave made all updates before configuring
to make sure you use the latest version of the configurator
so this bug is likely fixed already
Have you updated? Because this is an old bug that was fixed several weeks ago
Oh.. 😂