search

KoenVanduffel / CR-6_Klipper

A repository for Klipper firmware details for the Creality CR-6 printers.
GNU General Public License v3.0
91 stars 14 forks source link

Proposing some changes to the README.MD file #4

Closed Thinkersbluff closed 2 years ago

Thinkersbluff commented 2 years ago

Thank you for building and maintaining this repo!

I have forked a copy for myself, and I am taking advantage of my current level of general ignorance on the topic of Klipper to scan through the README files for areas where a noob may have a lot of questions for us.

I was a Systems Engineer and a Proposal and Procedures writer in my working life, so I tend to enjoy refactoring documents for clarity. This PR is to offer some/all of my current editorial changes to you, in case you also find this of value.

Cheers, Thinkersbluff

Thinkersbluff commented 2 years ago

I continue to update my Editorials branch and it looks like those updates come here, too. Sorry for the lack of detail in the commit titles. I am having some troubles getting this tool installed. In particular, KlipperScreen would not launch and the troubleshooting instructions failed when the file 99-fbturbo.conf was actually named 99-fbturbo.~ on my pi and I could not rename it.

Today, I started my installation again, three times:

  1. Once with a FULL Raspberry OS install, hoping that whatever service may have been missing on the Lite version was now installed. Surprised to find that the automatic update of that OS ran for almost 3hrs, right after a "fresh" install. Then it ran like a snail.
  2. The second time installing the "recommended" 32-bit Pi OS. That ran almost as slowly as the FULL.
  3. Finally, I installed the latest MainsailOS. I may not try installing KlipperScreen again, until I have Mainsail working well.

I am now using KIUAH to do all the updates, to reduce the risk of finger-troubles at my end.

As I continue to research and learn, I am tweaking the ReadMe on my fork, in the hopes that others who follow may save themselves a bit of this trouble. It seems like Moonraker changed its "permissions" strategy in Jan2022, to require something called PolicyKit to be installed and configured. I don't know whether that impacts the steps you originally outlined in your ReadMe, but I think it may be something I did incorrectly, which might explain why KlipperScreen did not simply launch after the install/restart.

BTW - I will soon be receiving a Creality 1.1.0.3 board as a backup to my BTT SKR, since I started having problems getting the TMC Hybrid Threshold values to stay the value I entered. (e.g. entered 600, saved as 617) I am also leaning toward MainSail rather than Fluidd. That may mean we can validate your CR6.cfg and printer.cfg files on more configurations? Is there anything about either cfg file that is Fluidd-specific, other than the line [include fluidd.cfg] in the printer.cfg file? Could those files safely just include [include mainsail.cfg] as well, to make the repo assets ui agnostic?

Thinkersbluff commented 2 years ago

Looks like the cfg edits PR I followed this with has collected the same commits. I don't think GitHub would like two PRs making the same changes, so I will close this one. Guess I should have made the other branch from main instead of from Editorials.
Sorry, still learning.

So I still recommend these editorial changes, but will close this PR to avoid duplication