Merge branch 'kamp' into develop. Moved imports into osskc.cfg.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -12,7 +12,6 @@ A clear and concise description of what the bug is.
 
 **To Reproduce**
 Steps to reproduce the behavior:
-
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
@@ -24,39 +23,12 @@ A clear and concise description of what you expected to happen.
 **Screenshots**
 If applicable, add screenshots to help explain your problem.
 
-**What printer are you using?**
-
-- SV06, SV06 Plus, etc.
-
 **What kind of device are you using to host Klipper?**
-
  - OS: [e.g. old laptop, PC, Raspberry Pi]
  - Version: []
 
 **How did you install Klipper?**
-
  - Manual install, KIAUH, MainsailOS, FluiddPi, etc.
 
-**Is your local copy of this configuration up to date?**
-
-- This configuration changes all the time, when did you install it? Are you sure you're running the latest version?
-
-**What slicer are you using?**
-
-- [ ] PrusaSlicer
-- [ ] SuperSlicer
-- [ ] Cura
-- [ ] OrcaSlicer
-
-**Are you using the config bundles from this repo?**
-
-- [ ] Yes
-- [ ] No
-
-**Did you [Adjust your slicer](https://github.com/bassamanator/Sovol-SV06-firmware#adjust-your-slicer)**?
-
-- [ ] Yes
-- [ ] No
-
 **Additional context**
 Add any other context about the problem here.

.gitignore

@@ -1,6 +1,3 @@
 printer-*_*.cfg
 .moonraker.conf.bkp
 .directory
-.venv
-__pycache__
-crowsnest.conf.*

.vscode/settings.json

@@ -3,82 +3,34 @@
 	"editor.insertSpaces": true,
 	"editor.detectIndentation": false,
 	"git.mergeEditor": false,
+	"spellright.language": ["en-GB-10-1."],
+	"spellright.documentTypes": ["markdown", "plaintext"],
 	"cSpell.words": [
         "ADXL",
         "blanchas",
-		"Buildplate",
         "cfgs",
         "Fluidd",
         "Fluiddpi",
         "gcode",
         "githubstar",
         "hotend",
-		"KAMP",
         "KIAUH",
         "Klipper",
         "Klipperized",
         "lrwxrwxrwx",
-		"microsteps",
         "moonraker",
-		"normalsize",
         "octahedroflake",
-		"osskc",
-		"Painis",
         "PARKBED",
         "PARKCENTER",
         "PARKFRONT",
         "PARKFRONTLOW",
         "PARKREAR",
         "pico",
-		"Printables",
         "Prusa",
-		"reformats",
         "runout",
-		"scriptsize",
-		"Sovol",
-		"superslicer",
-		"textcolor",
-		"textit",
-		"texttt"
+        "Sovol"
     ],
 	"[markdown]": {
 		"editor.formatOnSave": false
-	},
-	"[jsonc]": {
-		"editor.insertSpaces": false
-	},
-	"workbench.colorCustomizations": {
-		"activityBar.activeBackground": "#7e4810",
-		"activityBar.background": "#7e4810",
-		"activityBar.foreground": "#e7e7e7",
-		"activityBar.inactiveForeground": "#e7e7e799",
-		"activityBarBadge.background": "#041c10",
-		"activityBarBadge.foreground": "#e7e7e7",
-		"commandCenter.border": "#e7e7e799",
-		"sash.hoverBorder": "#7e4810",
-		"statusBar.background": "#512e0a",
-		"statusBar.foreground": "#e7e7e7",
-		"statusBarItem.hoverBackground": "#7e4810",
-		"statusBarItem.remoteBackground": "#512e0a",
-		"statusBarItem.remoteForeground": "#e7e7e7",
-		"titleBar.activeBackground": "#512e0a",
-		"titleBar.activeForeground": "#e7e7e7",
-		"titleBar.inactiveBackground": "#512e0a99",
-		"titleBar.inactiveForeground": "#e7e7e799"
-	},
-	"peacock.color": "#512e0a"
-	// "[html][jinja][jinja-html]": {
-	// 	"editor.formatOnSave": false,
-	// 	"editor.defaultFormatter": "monosans.djlint",
-	// 	"editor.detectIndentation": true,
-	// 	"editor.linkedEditing": true,
-	// 	"editor.tabSize": 4,
-
-	// 	"djlint.enableLinting": true,
-	// 	"djlint.profile": "jinja"
-	// },
-	// "djlint.showInstallError": true,
-	// "djlint.useVenv": false,
-	// "djlint.pythonPath": "/home/bassam/.local/share/uv/tools",
-	// "djlint.formatLanguages": ["django-html", "jinja", "jinja-html"]
+	}
 }

CONTRIBUTING.md

@@ -1,14 +1,8 @@
 # Contribution Guidelines
 
-When contributing, please:
+When contributing, please ...
 - provide a clear and concise explanation of your pull request.
-- try to make small changes, ie, make many small pull requests as opposed to a single large pull request.
+- try to make small changes, ie, make many small pull requests as opposed to a single large pull request. This allows me to check your work more quickly, thus merge more quickly.
 - try to follow the patterns I've already established.
 
-Contributions to `README.md` should do some or all of the following:
-- add clarity
-- reduce complexity for the user
-- reduce verbosity
-- fix errors
-
 Thank you.

LICENSE

@@ -1,661 +0,0 @@
-                    GNU AFFERO GENERAL PUBLIC LICENSE
-                       Version 3, 19 November 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
-
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-our General Public Licenses are intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-  Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
-  A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate.  Many developers of free software are heartened and
-encouraged by the resulting cooperation.  However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
-  The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community.  It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server.  Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
-  An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals.  This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                       TERMS AND CONDITIONS
-
-  0. Definitions.
-
-  "This License" refers to version 3 of the GNU Affero General Public License.
-
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
-
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-  1. Source Code.
-
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
-
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-  The Corresponding Source for a work in source code form is that
-same work.
-
-  2. Basic Permissions.
-
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-  4. Conveying Verbatim Copies.
-
-  You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-  5. Conveying Modified Source Versions.
-
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-  6. Conveying Non-Source Forms.
-
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-  7. Additional Terms.
-
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-  8. Termination.
-
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-  9. Acceptance Not Required for Having Copies.
-
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-  10. Automatic Licensing of Downstream Recipients.
-
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-  11. Patents.
-
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-  12. No Surrender of Others' Freedom.
-
-  If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-  13. Remote Network Interaction; Use with the GNU General Public License.
-
-  Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users
-interacting with it remotely through a computer network (if your version
-supports such interaction) an opportunity to receive the Corresponding
-Source of your version by providing access to the Corresponding Source
-from a network server at no charge, through some standard or customary
-means of facilitating copying of software.  This Corresponding Source
-shall include the Corresponding Source for any work covered by version 3
-of the GNU General Public License that is incorporated pursuant to the
-following paragraph.
-
-  Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU General Public License into a single
-combined work, and to convey the resulting work.  The terms of this
-License will continue to apply to the part which is the covered work,
-but the work with which it is combined will remain governed by version
-3 of the GNU General Public License.
-
-  14. Revised Versions of this License.
-
-  The Free Software Foundation may publish revised and/or new versions of
-the GNU Affero General Public License from time to time.  Such new versions
-will be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-  Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU Affero General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation.  If the Program does not specify a version number of the
-GNU Affero General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-  If the Program specifies that a proxy can decide which future
-versions of the GNU Affero General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-  Later license versions may give you additional or different
-permissions.  However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-  15. Disclaimer of Warranty.
-
-  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. Limitation of Liability.
-
-  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-  17. Interpretation of Sections 15 and 16.
-
-  If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-                     END OF TERMS AND CONDITIONS
-
-            How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU Affero General Public License as published
-    by the Free Software Foundation, either version 3 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU Affero General Public License for more details.
-
-    You should have received a copy of the GNU Affero General Public License
-    along with this program.  If not, see <https://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-  If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source.  For example, if your program is a web application, its
-interface could display a "Source" link that leads users to an archive
-of the code.  There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
-
-  You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
-<https://www.gnu.org/licenses/>.

README.md

@@ -1,23 +1,15 @@
-<p align="center">
-Please consider
-<a href="https://ko-fi.com/bassamanator" target="_blank">donating</a> to
-support my open source work ❤️
-</p>
+# 🚨 _One-Stop-Shop_ Klipper Configuration
 
-# One-Stop-Shop Klipper Configuration
+This branch contains the Klipper configuration and firmware for the **Sovol SV06** 3D printer.
 
 | Printer                     | Branch                                                                                    |
-| ------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
-| ${\normalsize{\textcolor{darkturquoise}{\text{Sovol SV06}}}}$ | ⚡ ${\scriptsize{\textcolor{darkturquoise}{\text{YOU ARE HERE}}}}$ ⚡                     |
-| Sovol SV06 SKR-Mini-E3-V3.0                                   | [skr-mini-e3-v3](https://github.com/bassamanator/Sovol-SV06-firmware/tree/skr-mini-e3-v3) |
-| Sovol SV06 Fly-E3-Pro-V3                                      | [fly-e3-pro-v3](https://github.com/ElPainis/Fly-E3-Pro-v3) \*\*                           |
+| --------------------------- | ----------------------------------------------------------------------------------------- |
+| Sovol SV06                  | ✨**You are here**✨                                                                      |
+| Sovol SV06 Skr-Mini-E3-V3.0 | [skr-mini-e3-v3](https://github.com/bassamanator/Sovol-SV06-firmware/tree/skr-mini-e3-v3) |
 | Sovol SV06 Plus             | [sv06-plus](https://github.com/bassamanator/Sovol-SV06-firmware/tree/sv06-plus)           |
 | All other printers          | [any-printer](https://github.com/bassamanator/Sovol-SV06-firmware/tree/any-printer)       |
 
-${\small{\textit{** Maintained by ElPainis}}}$
-
-> [!WARNING]
-> I am creating these files for my personal use and cannot be held responsible for what it might do to your printer. Use at your own risk.
+I am creating these files for my personal use and cannot be held responsible for what it might do to your printer. Use at your own risk.
 
 ## Outline
 
@@ -32,9 +24,8 @@ ${\small{\textit{** Maintained by ElPainis}}}$
   1. [Adjust Configuration with MCU Path](#adjust-configuration-with-mcu-path)
   2. [Configure Your Printer](#configure-your-printer)
 - [Adjust Your Slicer](#adjust-your-slicer)
-- [Support Me](#support-me)
 - [Directory Structure](#directory-structure)
-- [Special Considerations](#special-considerations)
+- [Support Me](#support-me)
 - [FAQ](#faq)
 - [Useful Resources](#useful-resources)
 - [Sovol Official Links](#sovol-official-links)
@@ -43,85 +34,53 @@ ${\small{\textit{** Maintained by ElPainis}}}$
 ## Features
 
 - 💥 This Klipper configuration is an _endpoint_, meaning that it contains **everything** that you could possibly need in order to have an excellent Klipper experience! 💥
-- Filament runout sensor usage implemented.
-- Minimum configuration settings for `Mainsail` and `Fluidd`.
-- Pre-configured configuration bundles based on the [Ellis SuperSlicer Print Profiles](https://github.com/AndrewEllis93/Ellis-SuperSlicer-Profiles):
-  - SuperSlicer
-  - PrusaSlicer
-  - 🚀 OrcaSlicer 🚀
-  - Printer profiles: `SV06/Plus`; `SV07/Plus`
+- <img src="./images/party_blob.gif" width="20" alt=''/> Filament runout sensor usage implemented. <img src="./images/party_blob.gif" width="20" alt=''/>
+- Minimum configuration settings for Mainsail/Fluiddpi to work.
+- SuperSlicer config bundle that contains the printer configuration, as well as what are considered by many to be the best print settings available for any FDM printer ([Ellis' SuperSlicer Profiles](https://github.com/AndrewEllis93/Ellis-SuperSlicer-Profiles)). Find the differences between the different print setting profiles [here](https://github.com/AndrewEllis93/Ellis-SuperSlicer-Profiles/tree/master/SuperSlicer). But basically, the 45 degree profile places the seam at the back.
 - Bed model and texture to use in SuperSlicer/PrusaSlicer.
-- Macros:
+- Macros
   - **Improved** mechanical gantry calibration/`G34` macro that provides the user audio feedback, and time to check the calibration.
   - Misc macros: `PRINT_START`, `CANCEL_PRINT`, `PRINT_END`, `PAUSE`, `RESUME`.
   - Parking macros (parks the printhead at various locations): `PARKFRONT`, `PARKFRONTLOW`, `PARKREAR`, `PARKCENTER`, `PARKBED`.
   - Load/unload filament macros.
-  - `PURGE_LINE` macro.
-  - `TEST_SPEED` macro. Find instructions [here](#how-do-i-use-the-test_speed-macro).
-- Klipper Adaptive Meshing & Purging (KAMP) integrated. Read about it [here](#what-do-i-need-to-know-about-kamp).
-
-[🔼 Back to top](#outline)
+  - Purge line macro.
 
 ## Stay Up-to-Date
 
-${\normalsize{\textcolor{goldenrod}{\texttt{Star ⭐ this project.}}}}$
+Watch for releases and updates.
 
-Watch for [updates](https://github.com/bassamanator/Sovol-SV06-firmware/discussions/37).
-
-<img src="./misc/images/githubstar.gif" width="500" alt='github star'/>
-
-[🔼 Back to top](#outline)
+<img src="./images/githubstar.gif" width="500" alt='Raspberry Pi'/>
 
 ## Preface
 
-Although I've made switching over to Klipper as easy as is possible, it can still be a challenge for some, especially considering that most of you have likely never used GNU+Linux. Save yourself the frustration, and fully read this documentation. Also note that Klipper is not a _must_, and is not for everyone. You can stick with Marlin, and have a fine 3D printing experience.
-
-In many ways, this entire repository can be considered _my opinion_ on the `3D printing experience` and this has been _my attempt_ to share that experience. Some factors, such as _accuracy_ and _testing_, have been at the forefront of my thoughts during this process. I hope you find this repository suitable. Cheers.
-
-[🔼 Back to top](#outline)
+Although I've made switching over to Klipper as easy as is possible, it can still be a challenge for some, especially considering that most of you have likely never used GNU+Linux. Save yourself the frustration, and fully read all documentation found on this page. Also note that Klipper is not a _must_, and is not for everyone. You can stick with Marlin, and have a fine 3D printing experience.
 
 ## Before You Begin
 
-- This entire page is a **9 minute read**. Save yourself _hours of troubleshooting_ and read this documentation fully.
-- Follow the steps in order. If an error was reported at a step, do no proceed to the next step.
-- It is assumed that you are connected to your host Raspberry Pi (or other host device) via SSH, and that your printer motherboard is connected to the host via a _data_ USB cable.
-- It is also assumed that the username on the host device is `pi`. If that is not the case, edit `moonraker.conf` and `cfgs/misc-macros.cfg` to change any mentions of `/home/pi` to `/home/yourUserName`.
-- Klipper _must_ be installed on the host beforehand. Easiest is to use [MainsailOS](https://github.com/mainsail-crew/mainsail/releases/latest). [KIAUH](https://github.com/th33xitus/kiauh) is another option.
-- Klipper _must_ be up to date.
-  - In `Fluidd`, you can do this from `Settings` > `Software Updates`.
-  - In `Mainsail`, you can do this from `Machine` > `Update Manager`.
+- Read this documentation _fully!_
+- Make sure your printer is in good physical condition, because print and travel speeds will be _a lot faster_ than they were before. Consider yourself warned.
+- Follow the steps in order.
+- If an error was reported at a step, do no proceed to the next step.
+- It is assumed that you are connected to your host Raspberry Pi (or other host device) via SSH, and that your printer motherboard is connected to the host via a data USB cable. Note that most of the micro USB cables that you find at home are _unlikely_ to be data cables, and it's not possible to tell just by looking.
+- It is also assumed that the username on the host device is `pi`. If that is not the case, you will have to manually edit `moonraker.conf` and `cfgs/misc-macros.cfg` and change any mentions of `/home/pi` to `/home/yourUserName`.
+- Klipper _must_ be installed on the host Raspberry Pi for everything to work. Easiest is to use a [~~FluiddPI~~](https://docs.fluidd.xyz/installation/fluiddpi#download) (⚠️ `FluiddPI` is not under active maintenance) or [MainsailOS](https://github.com/mainsail-crew/mainsail/releases/latest) image. Alternatively, you can install `Fluidd` or `Mainsail` via [KIAUH](https://github.com/th33xitus/kiauh).
 - Robert Redford's performance in _Spy Game (2001)_ was superb!
-- It is assumed that there is one instance of Klipper installed. If that is not the case, the steps in this guide will not work _perfectly_ for you.
+- It is assumed that there is one instance of Klipper installed. If you have multiple instances of Klipper installed, via `KIAUH` for example, then this guide is not for you. You can still use all the configs of course, but the steps in this guide will likely not work for you.
 - Your question has probably been answered already, but if it hasn't, please post in the [Discussion](https://github.com/bassamanator/Sovol-SV06-firmware/discussions) section.
-- I would recommend searching for the word `NOTE` in this configuration. There are roughly half a dozen short points amongst the various files that you should be aware of.
-- Consider [these](https://github.com/bassamanator/everything-sovol-sv06/blob/main/parts/README.md#printed-upgrades) printable parts, and also see my [Printables](https://www.printables.com/@bassamanator) page.
-
-> [!TIP]
-> Most of the micro USB cables that you find at home are _unlikely_ to be data cables, and it is not possible to tell just by looking.
-
-> [!CAUTION]
-> Make sure your printer is in good physical condition, because print and travel speeds will be _a lot faster_. Beginners would be wise to run through [these steps](https://github.com/bassamanator/everything-sovol-sv06/blob/main/initialsteps.md).
-
-> [!CAUTION]
-> [Disable](https://github.com/bassamanator/everything-sovol-sv06/blob/main/howto.md#disable-usb-cable-5v-pin) the USB cable's 5V pin.
-
-[🔼 Back to top](#outline)
+- I would recommend searching for the word `NOTE` in this repository. There are roughly half a dozen short points amongst the various files that you should be aware of if you're using this configuration.
 
 ## Klipper Installation
 
 ### Flash Firmware
 
-💡 If you flashed Klipper onto your motherboard in the past, you can skip this step.
+💡 _If you have already flashed klipper onto your motherboard in the past, you can skip this step._
 
 Please note:
 
-- For the sake of simplicity, I will refer to the firmware file as `klipper.bin` even though the actual filename is something along the lines of `klipper-v0.11.0-148-g52f4e20c.bin`.
+- For the sake of simplicity, I will refer to the klipper firmware file as `klipper.bin` even though the actual filename is something along the lines of `klipper-v0.11.0-148-g52f4e20c.bin`.
 - The firmware file is located in the `misc` folder.
 - Flashing will only work if current firmware filename is _different from previous flashing procedure_. The `.bin` is also important.
-- You may find this [video](https://youtu.be/p6l253OJa34) useful.
-
-> [!WARNING]
-> Many users have reported having issues flashing Klipper using the Sovol microSD card.
+- Many users have reported having issues flashing Klipper using the Sovol microSD card.
 
 #### 1. Prepare the microSD Card for Flashing with These Parameters
 
@@ -139,23 +98,18 @@ Please note:
 5. Turn on the printer and wait a minute (usually takes 10 seconds).
 6. Turn off the printer and remove the microSD.
 
-> [!IMPORTANT]
-> ⏲️ At this point, it's not possible to tell with certainty whether your flash was successful, continue on with the guide.
-
-[🔼 Back to top](#outline)
+You may find this [video](https://youtu.be/p6l253OJa34) useful.
 
 ### Download OSS Klipper Configuration
 
+You can choose _either_ of the 2 following methods.
+
 #### Method 1: Clone the Repository
 
-💡 Make sure `git` is installed (`sudo apt update && sudo apt install git`).
-
-1. `ssh` into the Klipper host.
-2. `cd ~/printer_data/config`
-3. Empty entire `~/printer_data/config` folder.
+1. `cd ~/printer_data/config`
+2. Empty entire `~/printer_data/config` folder.
    - In linux, you can delete files via `rm fileName` and directories via `rmdir directoryName`.
-   - In linux, you can list files and folders via `ls -lah`.
-4. `git clone -b master --single-branch https://github.com/bassamanator/Sovol-SV06-firmware.git .` ⚠️ Don't miss the period!
+3. `git clone -b master --single-branch https://github.com/bassamanator/Sovol-SV06-firmware.git .` ⚠️ Don't miss the period!
 
 #### Method 2: Download the ZIP
 
@@ -164,36 +118,27 @@ Please note:
 3. The parent folder in the `ZIP` is `Sovol-SV06-firmware-master`. This is relevant in the next step.
 4. Extract **only** the _contents_ of the parent folder into `~/printer_data/config`.
 
-[🔼 Back to top](#outline)
-
 ## Initial Steps
 
 ### Adjust Configuration with MCU Path
 
-💡 Make sure the host and printer are connected via USB.
-
-1. Find what port the `mcu` (printer motherboard) is connected to via _one_ of the following commands:
-
-   - `ls /dev/serial/by-id/*`
-   - `ls /dev/serial/by-path/*`
-
+1. Find what port the `mcu` (printer motherboard) is connected to via `ls -l /dev/serial/by-id/` or `ls -l /dev/serial/by-path/`.
    1. The output will be something along the lines of
-      - `/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0`
-
+      `lrwxrwxrwx 13 root root  22 Apr 11:10  usb-1a86_USB2.0-Serial-if00-port0 -> ../../ttyUSB0`.
+   2. `usb-1a86_USB2.0-Serial-if00-port0` is the relevant part.
+   3. Therefore, the full path to your `mcu` is either `/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0` or `/dev/serial/by-path/usb-1a86_USB2.0-Serial-if00-port0`, depending on the command you used to find the `mcu`.
 2. Adjust the `[mcu]` section in `printer.cfg` accordingly.
+   This is just an _example_ `mcu` section:
 
-   ```yaml
-   # 📝 This is just an example
+   ```
    [mcu]
    serial: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
    restart_method: command
    ```
 
-3. Do a `FIRMWARE_RESTART` in the Klipper console.
+3. Do a `FIRMWARE_RESTART`.
 
-If the Klipper flash that you did earlier was successful, and you've done everything else correctly, you should see no errors or warnings in the `Mainsail`/`Fluidd` dashboard. 🎉 **Your printer has been Klipperized!** 🎉
-
-[🔼 Back to top](#outline)
+If you've done everything correctly, you should see no errors or warnings in your Mainsail/Fluidd dashboard.
 
 ### Configure Your Printer
 
@@ -201,14 +146,11 @@ If the Klipper flash that you did earlier was successful, and you've done everyt
 
 ❗☠️ **Power off if there is a collision/problem** ☠️❗
 
-💡 The ${\small{\textcolor{red}{\texttt{EMERGENCY STOP}}}}$ button in your dashboard works faster than hitting the power switch.
-
-💡 Do a practice emergency stop.
-
 💡 I recommend no filament be loaded for any of these steps.
 
-> [!NOTE]
-> You will be pasting/typing these commands into the `Mainsail`/`Fluidd` console.
+💡 Find explanations for gcode commands at [https://marlinfw.org/](https://marlinfw.org/) and [https://www.klipper3d.org/](https://www.klipper3d.org/G-Codes.html).
+
+You will be pasting/typing these commands into the Mainsail/Fluidd console.
 
 1. Check to see if `X` and `Y` max positions can be reached, and adjust `position_max`, if necessary. You might be able to go further, which is great, but I recommend leaving a 2mm gap for safety.
    1. `G28`
@@ -225,136 +167,89 @@ If the Klipper flash that you did earlier was successful, and you've done everyt
    2. `SAVE_CONFIG` (once completed)
 5. Adjust `z_offset`. Make sure your nozzle if very clean. Do the [Paper test](https://www.klipper3d.org/Bed_Level.html?h=probe_calibrate#the-paper-test).
    1. `DO_PROBE_CALIBRATE`
-   2. Follow `z_offset` setup in `Mainsail`/`Fluidd`.
+   2. Follow `z_offset` setup in Mainsail/Fluidd.
    3. `SAVE_CONFIG` (once completed)
 6. Create a bed mesh.
    1. `DO_CREATE_MESH`
    2. `SAVE_CONFIG` (once completed)
 
-🏁 If you've made it here, then your Klipperized printer is ready to print! 🏁
+If you've made it here, then your printer has been Klipperized, and is ready to print!
 
-_But first_, adjust your slicer.
-
-[🔼 Back to top](#outline)
+But first, adjust your slicer.
 
 ## Adjust Your Slicer
 
-> [!NOTE]
-> If you are using the slicer bundles found on this repo, you can skip this section.
+You need to adjust the start and end gcode in your slicer. The relevant macros are `PRINT_START` and `PRINT_END`. Find instructions [here](https://ellis3dp.com/Print-Tuning-Guide/articles/passing_slicer_variables.html#slicer-start-g-code).
 
-### Start G-Code
-
-It varies depending on your slicer. Find instructions [here](https://ellis3dp.com/Print-Tuning-Guide/articles/passing_slicer_variables.html#slicer-start-g-code).
-
-### End G-Code
+If you would like to print a purge line before your print starts, at the end of your start gcode, on a new line add `PURGE_LINE`. Here's an example:
 
 ```
-PRINT_END
-```
-
-### Line Purge
-
-If you would like to print a purge line before your print starts, at the end of your start gcode, on a new line, add one of the following:
-
-- `PURGE_LINE`; prints a standard purge line.
-- `LINE_PURGE`; prints KAMP's purge line.
-
-> [!WARNING]
-> Do not attempt to use `LINE_PURGE` without reading [this section](#what-do-i-need-to-know-about-kamp).
-
-```yaml
-# 📝 This is just an example Start G-Code
-PRINT_START ...
+PRINT_START BED=[first_layer_bed_temperature] HOTEND={first_layer_temperature[initial_extruder]+extruder_temperature_offset[initial_extruder]} CHAMBER=[chamber_temperature]
 PURGE_LINE
 ```
 
-[🔼 Back to top](#outline)
-
-## Support Me
-
-Please ⭐ star this repository!
-
-Support [open source](https://en.wikipedia.org/wiki/Open_source), and buy me a [<img src="./misc/images/logo_white_stroke.png" height="20" alt='Ko-fi'/>](https://ko-fi.com/bassamanator).
-
-[🔼 Back to top](#outline)
-
 ## Directory Structure
 
 This repository contains many files and folders. Some are _necessary_ for this Klipper configuration to work, others are not.
 
 - **Necessary** items are marked with a ✅.
-- Items that can _optionally_ be deleted are marked with a 💠.
-<!-- tree -a -C -I '.directory' -L 1 -F -->
+- Items that can _optionally_ be deleted are marked with a ❌.
 
-```sh
-/home/pi/printer_data/config
-├── cfgs/ ✅
-├── CODE_OF_CONDUCT.md 💠
-├── CONTRIBUTING.md 💠
-├── .git/ ✅❔
-├── .github/ 💠
-├── .gitignore ✅❔
-├── LICENSE 💠
-├── misc/ 💠
+```
+├── cfgs ✅
+│   ├── adxl-direct.cfg
+│   ├── adxl-rp2040.cfg
+│   ├── adxl-rpi-pico-2x.cfg
+│   ├── MECHANICAL_GANTRY_CALIBRATION.cfg
+│   ├── misc-macros.cfg
+│   ├── PARKING.cfg
+│   └── TEST_SPEED.cfg
+├── CODE_OF_CONDUCT.md ❌
+├── CONTRIBUTING.md ❌
+├── .github ❌
+│   ├── FUNDING.yml
+│   └── ISSUE_TEMPLATE
+│       ├── bug_report.md
+│       └── feature_request.md
+├── .gitignore ❌
+├── images ❌
+│   ├── cup-border.png
+│   ├── githubstar.gif
+│   ├── heart.gif
+│   ├── logo_white_stroke.png
+│   └── party_blob.gif
+├── misc ❌
+│   ├── klipper-v0.11.0-148-g52f4e20c.bin
+│   ├── M503-output.yml
+│   ├── marlin-SV06V2.0.0A_2.24.bin
+│   ├── SuperSlicer_config_bundle.ini
+│   ├── sv06-buildPlate.png
+│   ├── SV06-buildPlate.stl
+│   └── SV06-texture.svg
 ├── moonraker.conf ✅
-├── osskc.cfg ✅
 ├── printer.cfg ✅
-├── README.md 💠
-├── SECURITY.md 💠
-└── .vscode/ 💠
+├── README.md ❌
+└── .vscode ❌
+    └── settings.json
 ```
 
-[🔼 Back to top](#outline)
+## Support Me
 
-## Special Considerations
+Please ⭐ star ⭐ this repository!
 
-### Sequential printing
-
-If enabled, cancelling, or resuming a print from pause, could lead to collisions with previously printed objects. In order to prevent collisions, in your slicer, ensure that objects are printed from the back of the build plate to the front.
-
-In PrusaSlicer, please see Printer Settings > Notes, for extruder clearances.
-
-### Renamed GCODE Commands
-
-#### BED_MESH_CALIBRATE
-
-Renamed to `_BED_MESH_CALIBRATE`.
-
-### Errors
-
-#### MCU 'mcu' shutdown: Timer too close
-
-This error often occurs when the `mcu` is unable to generate the required `microsteps`. Lower power Klipper hosts might be especially susceptible. Reducing `microsteps` to `64`, or even `32` can resolve the issue.
-
-[🔼 Back to top](#outline)
+If you found my work useful, please consider buying me a [<img src="./images/logo_white_stroke.png" height="20" alt='Ko-fi'/>](https://ko-fi.com/bassamanator).
 
 ## FAQ
 
-### What are some settings that I can change?
+##### How do I import a SuperSlicer configuration bundle (`SuperSlicer_config_bundle.ini`) into SuperSlicer?
 
-Edit the relevant file according to your needs.
+Please see [this discussion](https://github.com/bassamanator/Sovol-SV06-firmware/discussions/13).
 
-| File                   | Section                  |
-| ---------------------- | ------------------------ |
-| `cfgs/misc-macros.cfg` | `[gcode_macro _globals]` |
+##### How do I print using SuperSlicer?
 
-| Variable                           | Disable       | Enable         | Notes                                          |
-| ---------------------------------- | ------------- | -------------- | ---------------------------------------------- |
-| `variable_beeping_enabled`         | `0`           | `1` (default)  |
-| `variable_filament_sensor_enabled` | `0` (default) | `1`            |
-| `variable_kamp_enable`             | `0` (default) | `1`            | See [here](#what-do-i-need-to-know-about-kamp) |
-| `variable_bed_temp_over`           | `0`           | `10` (default) | Speeds up print start                          |
-| `variable_bed_temp_not_exact`      | `0`           | `1` (default)  | Speeds up print start                          |
+Please see [this discussion](https://github.com/bassamanator/Sovol-SV06-firmware/discussions/14).
 
-### How do I import a configuration bundle into SuperSlicer/PrusaSlicer?
-
-Please see this [discussion](https://github.com/bassamanator/Sovol-SV06-firmware/discussions/13).
-
-### How do I print using SuperSlicer/PrusaSlicer?
-
-Please see this [discussion](https://github.com/bassamanator/Sovol-SV06-firmware/discussions/14).
-
-### When does beeping occur?
+##### When does beeping occur?
 
 The printer will beep upon:
 
@@ -363,35 +258,54 @@ The printer will beep upon:
 - Upon `PRINT_END`.
 - `MECHANICAL_GANTRY_CALIBRATION`/`G34`.
 
-### I want to use a filament sensor. How do I set it up?
+##### How do I disable beeping?
+
+Make the following changes according to your needs. All beeping will be disabled _except_ during gantry calibration.
+
+| File            | `cfgs/misc-macros.cfg`     |
+| --------------- | -------------------------- |
+| Section         | `[gcode_macro _globals]`   |
+| Variable        | `variable_beeping_enabled` |
+| Disable beeping | `0`                        |
+| Enable beeping  | `1`                        |
+
+##### I want to use a filament sensor. How do I set it up?
 
 You can find information about the physical setup [here](https://github.com/bassamanator/everything-sovol-sv06#filament-sensor).
 
-You can test the sensor via `QUERY_FILAMENT_SENSOR SENSOR=filament_sensor`.
+##### I have a simple filament sensor connected. How do I enable/disable it?
 
-### My filament runout sensor works, but I just started a print without any filament loaded. What gives?
+Make the following changes according to your needs.
+
+| File           | `cfgs/misc-macros.cfg`             |
+| -------------- | ---------------------------------- |
+| Section        | `[gcode_macro _globals]`           |
+| Variable       | `variable_filament_sensor_enabled` |
+| Disable sensor | `0`                                |
+| Enable sensor  | `1`                                |
+
+##### My filament runout sensor works, but I just started a print without any filament loaded. What gives?
 
 A simple runout sensor can only detect a change in state. So, if you start a print without filament loaded, the printer will not know that there is no filament loaded. You should test your sensor by having filament loaded, starting a print, then cutting the filament. The expected behaviour is that the print will pause, and as long as you have beeping enabled, you will hear 3 annoying beeps.
 
-### What happens when I put in `M600`/colour change at a certain layer?
+##### What happens when I put in `M600`/colour change at a certain layer?
 
 1. The printer will beep 3 times (not annoyingly).
 2. Printing will stop.
 3. The printhead will park itself front center.
 4. The hotend will turn off, but the bed will remain hot.
 
-### What happens when I pause a print?
+##### What happens when I pause a print?
 
 Same behaviour as `M600`/colour change _except_ there won't be any beeping.
 
-### What happens when filament runs out?
+##### What happens when filament runs out?
 
 _If_ you have a working filament sensor, the same behaviour as `M600`/colour change will occur _except_ the beeps will be fairly annoying.
 
-### How do I resume a print after a colour change or filament runout?
+##### How do I resume a print after a colour change or filament runout?
 
-> [!WARNING]
-> Do not disable the stepper motors during this process!
+⚠️ _Do not disable the stepper motors during this process!_
 
 The printhead is now parked front center waiting for you to insert filament. You will:
 
@@ -402,43 +316,6 @@ The printhead is now parked front center waiting for you to insert filament. You
    - OR, you can push some filament by hand _making sure to first disengage the extruder's spring loaded arm_.
 3. Hit resume in your Klipper dashboard.
 
-### What do I need to know about KAMP?
-
-> [!WARNING]
-> No KAMP functionality can be used on low-powered devices such as the Raspberry Pi Zero.
-
-> [!WARNING]
-> If KAMP is disabled, and there is no `default` mesh, `PRINT_START` will crash.
-
-> [!IMPORTANT]
-> The [Label objects setting](https://docs.mainsail.xyz/overview/features/exclude-objects#enable-the-label-objects-setting-in-your-slicer) in your slicer must be enabled for KAMP to work.
-
-> [!NOTE]
-> `LINE_PURGE` is useable _on appropriate devices_ even if KAMP is disabled.
-
-This repo contains all the code from the KAMP repository, however, only the `adaptive meshing` and `LINE_PURGE` functionality of KAMP has been configured and tested for use. To enable other functionality, adjust `/cfgs/kamp/KAMP_Settings.cfg`.
-
-Read [KAMP official docs](https://github.com/kyleisah/Klipper-Adaptive-Meshing-Purging) to learn more.
-
-### How do I use the `TEST_SPEED` macro?
-
-> [!WARNING]
-> This is for advanced users only, with well oiled machines. You can cause serious damage to your printer if you're not careful.
-
-Find full instructions [here](https://ellis3dp.com/Print-Tuning-Guide/articles/determining_max_speeds_accels.html).
-
-Some tips:
-
-- Before running with `ITERATIONS=40` with an untested speed/accel value, run with `ITERATIONS=1`.
-- Pay close attention throughout the run, so that you can click ${\small{\textcolor{red}{\texttt{EMERGENCY STOP}}}}$ at a moment's notice.
-- This macro will simply help you determine the maximum speed your printhead and bed can reliably move at, not necessarily print at. The bottleneck for my SV06, for example, is the 15mm/s^2 that the hotend maxes out at (well under 200mm/s actual print speed).
-
-### How do I compile my own firmware?
-
-Please see this [discussion](https://github.com/bassamanator/Sovol-SV06-firmware/discussions/111).
-
-[🔼 Back to top](#outline)
-
 ## Useful Resources
 
 - [Everything Sovol SV06](https://github.com/bassamanator/everything-sovol-sv06)
@@ -446,27 +323,20 @@ Please see this [discussion](https://github.com/bassamanator/Sovol-SV06-firmware
 - ⭐⭐⭐⭐⭐ [Ellis' Print Tuning Guide](https://ellis3dp.com/Print-Tuning-Guide)
 - [Simplify3D Print Quality Troubleshooting Guide](https://www.simplify3d.com/resources/print-quality-troubleshooting/)
 
-[🔼 Back to top](#outline)
-
 ## Sovol Official Links
 
 - [SV06 Marlin Source Code](https://github.com/Sovol3d/Sv06-Source-Code)
 - [SV06 Models](https://github.com/Sovol3d/SV06-Fully-Open-Source)
 - [SV06 Plus Marlin Source Code and Models](https://github.com/Sovol3d/SV06-PLUS)
 
-[🔼 Back to top](#outline)
-
 ## Sources
 
-- [https://www.klipper3d.org](https://www.klipper3d.org)
-- [Ellis' Print Tuning Guide](https://ellis3dp.com/Print-Tuning-Guide)
-- [Mechanical Gantry Calibration Macro](https://github.com/strayr/strayr-k-macros)
-- [SV06 printer.cfg](https://github.com/spinixguy/Sovol-SV06-firmware)
-- [SV06 Buildplate and Texture](https://www.printables.com/model/378915-sovol-sv06-buildplate-texture-and-model-for-prusas)
-- [Ellis' SuperSlicer Profiles](https://github.com/AndrewEllis93/Ellis-SuperSlicer-Profiles)
-- [Klipper Adaptive Meshing & Purging](https://github.com/kyleisah/Klipper-Adaptive-Meshing-Purging)
-- [PrusaSlicer Print Settings](https://github.com/mjonuschat/PrusaSlicer-Profiles)
+- https://www.klipper3d.org
+- https://ellis3dp.com/Print-Tuning-Guide
+- https://github.com/strayr/strayr-k-macros
+- https://docs.vorondesign.com/build/software/miniE3_v20_klipper.html
+- https://github.com/spinixguy/Sovol-SV06-firmware
+- https://www.printables.com/model/378915-sovol-sv06-buildplate-texture-and-model-for-prusas
+- https://github.com/AndrewEllis93/Ellis-SuperSlicer-Profiles
 
 [![ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/H2H0HIHTH)
-
-[🔼 Back to top](#outline)

SECURITY.md

@@ -1,9 +0,0 @@
-# Security Policy
-
-## Reporting a Vulnerability
-
-If you see any piece of code on this repository that could be a security issue, please create an [Issue](https://github.com/bassamanator/Sovol-SV06-firmware/issues/new/choose) at your earliest continence. I keep a close eye on this repository, so you should get an update from me fairly quickly.
-
-You can also message me on [Reddit](https://www.reddit.com/user/bassamanator/) privately.
-
-If your reported vulnerability is confirmed, you can rest assured that dealing with it will be a top priority.

cfgs/CALIBRATION.cfg

@@ -22,7 +22,6 @@ gcode:
     G1 X{max_x/2} Y{max_y/2} Z10 F6000
     M106 S64
     PID_CALIBRATE HEATER=extruder TARGET={TARGETTEMP}
-    M107 ; Turn off print cooling fan
 
 # TODO test this
 [gcode_macro PID_TEST_ALL]

cfgs/MECHANICAL_GANTRY_CALIBRATION.cfg

@@ -72,16 +72,16 @@ gcode:
         SET_TMC_CURRENT STEPPER=stepper_z1 CURRENT={my_current} ; drop current
     {% endif %}
 
-    CONDITIONAL_BEEP I=1
+    BEEP I=1
     G4 P200 ; Probably not necessary, it is here just for sure
 
     SET_KINEMATIC_POSITION Z={z_max - 25} ; Trick printer into beleiving the gantry is 25mm lower than it is ; CHANGED
 
     G1 Z{z_max} F{6 * 60} ; based on above figures, there will be 20mm worth of grinding ; CHANGED
-    CONDITIONAL_BEEP I=2
+    BEEP I=2
     G4 P10000 ; wait 10 seconds
     G1 Z{z_max -6} F{6 * 60} ; move 4mm down
-    CONDITIONAL_BEEP I=3
+    BEEP I=3
     G4 P200 ; same as the first one
     
     SET_TMC_CURRENT STEPPER=stepper_z CURRENT={oldcurrent} HOLDCURRENT={oldhold}

cfgs/TEST_SPEED.cfg

@@ -1,12 +1,10 @@
-# NOTE Find how to use instructions here: https://ellis3dp.com/Print-Tuning-Guide/articles/determining_max_speeds_accels.html
-[gcode_macro TEST_SPEED]
+# NOTE This macro is not ready for use. ☠️☠️☠️
 # Home, get position, throw around toolhead, home again.
 # If MCU stepper positions (first line in GET_POSITION) are greater than a full step different (your number of microsteps), then skipping occured.
 # We only measure to a full step to accomodate for endstop variance.
 # Example: TEST_SPEED SPEED=300 ACCEL=5000 ITERATIONS=10
 
-description: Test for max speed and acceleration parameters for the printer. Procedure: Home -> ReadPositionFromMCU -> MovesToolhead@Vel&Accel -> Home -> ReadPositionfromMCU
-
+[gcode_macro TEST_SPEED]
 gcode:
     # Speed
     {% set speed  = params.SPEED|default(printer.configfile.settings.printer.max_velocity)|int %}
@@ -14,8 +12,6 @@ gcode:
     {% set iterations = params.ITERATIONS|default(5)|int %}
     # Acceleration
     {% set accel  = params.ACCEL|default(printer.configfile.settings.printer.max_accel)|int %}
-    # Minimum Cruise Ratio
-    {% set min_cruise_ratio = params.MIN_CRUISE_RATIO|default(0.5)|float %}
     # Bounding inset for large pattern (helps prevent slamming the toolhead into the sides after small skips, and helps to account for machines with imperfectly set dimensions)
     {% set bound = params.BOUND|default(20)|int %}
     # Size for small pattern box
@@ -46,7 +42,6 @@ gcode:
     { action_respond_info("TEST_SPEED: starting %d iterations at speed %d, accel %d" % (iterations, speed, accel)) }
     
     # Home and get position for comparison later:
-        M400 # Finish moves - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/66
         G28
         # QGL if not already QGLd (only if QGL section exists in config)
         {% if printer.configfile.settings.quad_gantry_level %}
@@ -58,7 +53,6 @@ gcode:
         # Move 50mm away from max position and home again (to help with hall effect endstop accuracy - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/24)
         G90
         G1 X{printer.toolhead.axis_maximum.x-50} Y{printer.toolhead.axis_maximum.y-50} F{30*60}
-        M400 # Finish moves - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/66
         G28 X Y
         G0 X{printer.toolhead.axis_maximum.x-1} Y{printer.toolhead.axis_maximum.y-1} F{30*60}
         G4 P1000 
@@ -68,14 +62,11 @@ gcode:
     G0 X{x_min} Y{y_min} Z{bound + 10} F{speed*60}
 
     # Set new limits
-    {% if printer.configfile.settings.printer.minimum_cruise_ratio is defined %}
-        SET_VELOCITY_LIMIT VELOCITY={speed} ACCEL={accel} MINIMUM_CRUISE_RATIO={min_cruise_ratio}
-    {% else %}
     SET_VELOCITY_LIMIT VELOCITY={speed} ACCEL={accel} ACCEL_TO_DECEL={accel / 2}
-    {% endif %}
 
     {% for i in range(iterations) %}
-        # Large pattern diagonals
+        # Large pattern
+            # Diagonals
             G0 X{x_min} Y{y_min} F{speed*60}
             G0 X{x_max} Y{y_max} F{speed*60}
             G0 X{x_min} Y{y_min} F{speed*60}
@@ -83,13 +74,14 @@ gcode:
             G0 X{x_min} Y{y_max} F{speed*60}
             G0 X{x_max} Y{y_min} F{speed*60}
             
-        # Large pattern box
+            # Box
             G0 X{x_min} Y{y_min} F{speed*60}
             G0 X{x_min} Y{y_max} F{speed*60}
             G0 X{x_max} Y{y_max} F{speed*60}
             G0 X{x_max} Y{y_min} F{speed*60}
         
-        # Small pattern diagonals
+        # Small pattern
+            # Small diagonals 
             G0 X{x_center_min} Y{y_center_min} F{speed*60}
             G0 X{x_center_max} Y{y_center_max} F{speed*60}
             G0 X{x_center_min} Y{y_center_min} F{speed*60}
@@ -97,7 +89,7 @@ gcode:
             G0 X{x_center_min} Y{y_center_max} F{speed*60}
             G0 X{x_center_max} Y{y_center_min} F{speed*60}
             
-        # Small pattern box
+            # Small box
             G0 X{x_center_min} Y{y_center_min} F{speed*60}
             G0 X{x_center_min} Y{y_center_max} F{speed*60}
             G0 X{x_center_max} Y{y_center_max} F{speed*60}
@@ -105,15 +97,10 @@ gcode:
     {% endfor %}
 
     # Restore max speed/accel/accel_to_decel to their configured values
-    {% if printer.configfile.settings.printer.minimum_cruise_ratio is defined %}
-        SET_VELOCITY_LIMIT VELOCITY={printer.configfile.settings.printer.max_velocity} ACCEL={printer.configfile.settings.printer.max_accel} MINIMUM_CRUISE_RATIO={printer.configfile.settings.printer.minimum_cruise_ratio} 
-    {% else %}
     SET_VELOCITY_LIMIT VELOCITY={printer.configfile.settings.printer.max_velocity} ACCEL={printer.configfile.settings.printer.max_accel} ACCEL_TO_DECEL={printer.configfile.settings.printer.max_accel_to_decel} 
-    {% endif %}
 
     # Re-home and get position again for comparison:
-        M400 # Finish moves - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/66
-        G28 # This is a full G28 to fix an issue with CoreXZ - https://github.com/AndrewEllis93/Print-Tuning-Guide/issues/12
+        G28
         # Go to XY home positions (in case your homing override leaves it elsewhere)
         G90
         G0 X{printer.toolhead.axis_maximum.x-1} Y{printer.toolhead.axis_maximum.y-1} F{30*60}
@@ -122,4 +109,3 @@ gcode:
 
     # Restore previous gcode state (absolute/relative, etc)
     RESTORE_GCODE_STATE NAME=TEST_SPEED
-    

cfgs/kamp/Adaptive_Meshing.cfg

@@ -13,13 +13,9 @@ gcode:
     {% set bed_mesh_min = printer.configfile.settings.bed_mesh.mesh_min %}                                                          # Get bed mesh min from printer.cfg
     {% set bed_mesh_max = printer.configfile.settings.bed_mesh.mesh_max %}                                                          # Get bed mesh max from printer.cfg
     {% set probe_count = printer.configfile.settings.bed_mesh.probe_count %}                                                        # Get probe count from printer.cfg
-    {% set kamp_settings = printer["gcode_macro _KAMP_Settings"] %}                                                                 # Pull variables from _KAMP_Settings
-    {% set verbose_enable = kamp_settings.verbose_enable | abs %}                                                                   # Pull verbose setting from _KAMP_Settings
-    {% set probe_dock_enable = kamp_settings.probe_dock_enable | abs %}                                                             # Pull probe dockable probe settings from _KAMP_Settings
-    {% set attach_macro = kamp_settings.attach_macro | string %}                                                                    # Pull attach probe command from _KAMP_Settings
-    {% set detach_macro = kamp_settings.detach_macro | string %}                                                                    # Pull detach probe command from _KAMP_Settings
-    {% set mesh_margin = kamp_settings.mesh_margin | float %}                                                                       # Pull mesh margin setting from _KAMP_Settings
-    {% set fuzz_amount = kamp_settings.fuzz_amount | float %}                                                                       # Pull fuzz amount setting from _KAMP_Settings
+    {% set verbose_enable = printer["gcode_macro _KAMP_Settings"].verbose_enable | abs %}                                           # Pull verbose setting from _KAMP_Settings
+    {% set mesh_margin = printer["gcode_macro _KAMP_Settings"].mesh_margin | float %}                                               # Pull mesh margin setting from _KAMP_Settings
+    {% set fuzz_amount = printer["gcode_macro _KAMP_Settings"].fuzz_amount | float %}                                               # Pull fuzz amount setting from _KAMP_Settings
     {% set probe_count = probe_count if probe_count|length > 1 else probe_count * 2  %}                                             # If probe count is only a single number, convert it to 2. E.g. probe_count:7 = 7,7
     {% set max_probe_point_distance_x = ( bed_mesh_max[0] - bed_mesh_min[0] ) / (probe_count[0] - 1)  %}                            # Determine max probe point distance
     {% set max_probe_point_distance_y = ( bed_mesh_max[1] - bed_mesh_min[1] ) / (probe_count[1] - 1)  %}                            # Determine max probe point distance
@@ -29,15 +25,10 @@ gcode:
     {% set y_max = all_points | map(attribute=1) | max | default(bed_mesh_max[1]) %}                                                # Set y_max from largest object y point
 
     {% set fuzz_range = range((0) | int, (fuzz_amount * 100) | int + 1) %}                                                          # Set fuzz_range between 0 and fuzz_amount
-    {% set adapted_x_min = x_min - mesh_margin - (fuzz_range | random / 100.0) %}                                                   # Adapt x_min to margin and fuzz constraints
-    {% set adapted_y_min = y_min - mesh_margin - (fuzz_range | random / 100.0) %}                                                   # Adapt y_min to margin and fuzz constraints
-    {% set adapted_x_max = x_max + mesh_margin + (fuzz_range | random / 100.0) %}                                                   # Adapt x_max to margin and fuzz constraints
-    {% set adapted_y_max = y_max + mesh_margin + (fuzz_range | random / 100.0) %}                                                   # Adapt y_max to margin and fuzz constraints
-
-    {% set adapted_x_min = [adapted_x_min , bed_mesh_min[0]] | max %}                                                               # Compare adjustments to defaults and choose max
-    {% set adapted_y_min = [adapted_y_min , bed_mesh_min[1]] | max %}                                                               # Compare adjustments to defaults and choose max
-    {% set adapted_x_max = [adapted_x_max , bed_mesh_max[0]] | min %}                                                               # Compare adjustments to defaults and choose min
-    {% set adapted_y_max = [adapted_y_max , bed_mesh_max[1]] | min %}                                                               # Compare adjustments to defaults and choose min
+    {% set adapted_x_min = (bed_mesh_min[0] + fuzz_amount - mesh_margin, x_min) | max - (fuzz_range | random / 100.0) %}            # Adapt x_min to margin and fuzz constraints
+    {% set adapted_y_min = (bed_mesh_min[1] + fuzz_amount - mesh_margin, y_min) | max - (fuzz_range | random / 100.0) %}            # Adapt y_min to margin and fuzz constraints
+    {% set adapted_x_max = (bed_mesh_max[0] - fuzz_amount + mesh_margin, x_max) | min + (fuzz_range | random / 100.0) %}            # Adapt x_max to margin and fuzz constraints
+    {% set adapted_y_max = (bed_mesh_max[1] - fuzz_amount + mesh_margin, y_max) | min + (fuzz_range | random / 100.0) %}            # Adapt y_max to margin and fuzz constraints
 
     {% set points_x = (((adapted_x_max - adapted_x_min) / max_probe_point_distance_x) | round(method='ceil') | int) + 1 %}          # Define probe_count's x point count and round up
     {% set points_y = (((adapted_y_max - adapted_y_min) / max_probe_point_distance_y) | round(method='ceil') | int) + 1 %}          # Define probe_count's y point count and round up
@@ -56,7 +47,6 @@ gcode:
     {% set points_y = [points_y, probe_count[1]]|min %}
 
     {% if verbose_enable == True %}                                                                                                 # If verbose is enabled, print information about KAMP's calculations
-        {% if printer.exclude_object.objects != [] %}
 
         { action_respond_info( "Algorithm: {}.".format(                                                                              
             (algorithm),                                                                                                            
@@ -101,12 +91,6 @@ gcode:
 
         {action_respond_info("KAMP adjustments successful. Happy KAMPing!")}
 
-        {% else %}
-
-            {action_respond_info("No objects detected! Check your gcode and make sure that EXCLUDE_OBJECT_DEFINE is happening before BED_MESH_CALIBRATE is called. Defaulting to regular meshing.")}
-            G4 P5000                                                                                                                # Wait 5 seconds to make error more visible
-        {% endif %}
-
     {% endif %}
 
     {% if probe_dock_enable == True %}

cfgs/kamp/KAMP_Settings.cfg

@@ -1,10 +1,7 @@
 # Below you can include specific configuration files depending on what you want KAMP to do:
 
-# NOTE bassamanator: uncomment the functionality that you want to use from KAMP
 [include ./Adaptive_Meshing.cfg]       # Include to enable adaptive meshing configuration.
-[include ./Line_Purge.cfg]             # Include to enable adaptive line purging configuration.
-# [include ./Voron_Purge.cfg]            # Include to enable adaptive Voron logo purging configuration.
-# [include ./Smart_Park.cfg]             # Include to enable the Smart Park function, which parks the printhead near the print area for final heating.
+# [include ./KAMP/Line_Purge.cfg]             # Include to enable adaptive line purging configuration.
 
 [gcode_macro _KAMP_Settings]
 description: This macro contains all adjustable settings for KAMP 
@@ -29,9 +26,6 @@ variable_purge_margin: 10                   # Distance the purge will be in fron
 variable_purge_amount: 30                   # Amount of filament to be purged prior to printing.
 variable_flow_rate: 12                      # Flow rate of purge in mm3/s. Default is 12.
 
-# The following variables are for adjusting the Smart Park feature for KAMP, which will park the printhead near the print area at a specified height.
-variable_smart_park_height: 10              # Z position for Smart Park, default is 10.
-
 gcode: # Gcode section left intentionally blank. Do not disturb.
 
     {action_respond_info(" Running the KAMP_Settings macro does nothing, it is only used for storing KAMP settings. ")}

cfgs/kamp/Line_Purge.cfg

@@ -37,11 +37,11 @@ gcode:
     {% set purge_y_origin = ([purge_y_min - purge_margin, 0] | max) %}                                  # Add margin to y min, compare to 0, and choose the larger
 
     # Calculate purge speed
-    {% set purge_move_speed = (flow_rate / 5.0) * 60 | float %}
+    {% set purge_move_speed = (flow_rate / cross_section) * 60 | float %}
 
-    {% if cross_section < 5 %}
+    {% if cross_section != 5 %}
 
-        {action_respond_info("[Extruder] max_extrude_cross_section is insufficient for purge, please set it to 5 or greater. Purge skipped.")}
+        {action_respond_info("[Extruder] max_extrude_cross_section is not configured correctly, please set it to 5. Purge skipped.")}
 
     {% else %}
 
@@ -60,7 +60,7 @@ gcode:
 
         {% if purge_y_origin > 0 %}
         
-            {action_respond_info("KAMP purge starting at {}, {} and purging {}mm of filament, requested flow rate is {}mm3/s.".format(                                                                 
+            {action_respond_info("KAMP purge starting at {}, {} and purging {}mm of filament, requested flow rate is {}mm/s3.".format(                                                                 
                 (purge_x_center),
                 (purge_y_origin),
                 (purge_amount),
@@ -69,7 +69,7 @@ gcode:
     
         {% else %}
     
-            {action_respond_info("KAMP purge starting at {}, {} and purging {}mm of filament, requested flow rate is {}mm3/s.".format(                                                                 
+            {action_respond_info("KAMP purge starting at {}, {} and purging {}mm of filament, requested flow rate is {}mm/s3.".format(                                                                 
                 (purge_x_origin),
                 (purge_y_center),
                 (purge_amount),
@@ -78,8 +78,6 @@ gcode:
 
         {% endif %}
 
-        SAVE_GCODE_STATE NAME=Prepurge_State                                                    # Create gcode state
-
         {% if purge_y_origin > 0 %}                                                             # If there's room on Y, purge along X axis in front of print area
 
             G92 E0                                                                              # Reset extruder
@@ -91,7 +89,6 @@ gcode:
             G1 E{tip_distance} F{purge_move_speed}                                              # Move filament tip
             G1 X{purge_x_center + purge_amount} E{purge_amount} F{purge_move_speed}             # Purge line
             {RETRACT}                                                                           # Retract
-            G0 X{purge_x_center + purge_amount + 10} F{travel_speed}                            # Rapid move to break string
             G92 E0                                                                              # Reset extruder distance
             M82                                                                                 # Absolute extrusion mode
             G0 Z{purge_height * 2} F{travel_speed}                                              # Z hop
@@ -107,13 +104,10 @@ gcode:
             G1 E{tip_distance} F{purge_move_speed}                                              # Move filament tip
             G1 Y{purge_y_center + purge_amount} E{purge_amount} F{purge_move_speed}             # Purge line
             {RETRACT}                                                                           # Retract
-            G0 Y{purge_y_center + purge_amount + 10} F{travel_speed}                            # Rapid move to break string
             G92 E0                                                                              # Reset extruder distance
             M82                                                                                 # Absolute extrusion mode
             G0 Z{purge_height * 2} F{travel_speed}                                              # Z hop
 
         {% endif %}
     
-        RESTORE_GCODE_STATE NAME=Prepurge_State                                                 # Restore gcode state
-    
     {% endif %}

cfgs/kamp/Smart_Park.cfg

@@ -1,38 +0,0 @@
-[gcode_macro SMART_PARK]
-description: Parks your printhead near the print area for pre-print hotend heating.
-gcode:
-
-    {% set kamp_settings = printer["gcode_macro _KAMP_Settings"] %}                                                                 # Pull all variables from _KAMP_Settings
-    {% set z_height = kamp_settings.smart_park_height | float %}                                                                    # Set Z height variable
-    {% set purge_margin = kamp_settings.purge_margin | float %}                                                                     # Set purge margin variable
-    {% set verbose_enable = kamp_settings.verbose_enable | abs %}                                                                   # Set verbosity
-    {% set center_x = printer.toolhead.axis_maximum.x / 2 | float %}                                                                # Create center point of x for fallback
-    {% set center_y = printer.toolhead.axis_maximum.y / 2 | float %}                                                                # Create center point of y for fallback
-    {% set axis_minimum_x = printer.toolhead.axis_minimum.x | float %}
-    {% set axis_minimum_y = printer.toolhead.axis_minimum.y | float %}
-    {% set all_points = printer.exclude_object.objects | map(attribute='polygon') | sum(start=[]) %}                                # Gather all object points
-    {% set x_min = all_points | map(attribute=0) | min | default(center_x) %}                                                       # Set x_min from smallest object x point
-    {% set y_min = all_points | map(attribute=1) | min | default(center_y) %}                                                       # Set y_min from smallest object y point
-    {% set travel_speed = (printer.toolhead.max_velocity) * 60 | float %}                                                           # Set travel speed from config
-
-    {% if purge_margin > 0 and x_min != center_x and y_min != center_y %}                                                           # If objects are detected and purge margin 
-        {% set x_min = [ x_min - purge_margin , x_min ] | min %}                                                                    # value is greater than 0, move
-        {% set y_min = [ y_min - purge_margin , y_min ] | min %}                                                                    # to purge location + margin
-        {% set x_min = [ x_min , axis_minimum_x ] | max %}
-        {% set y_min = [ y_min , axis_minimum_y ] | max %}
-    {% endif %}
-
-    {% if verbose_enable == True %}                                                                                                 # Verbose park location
-
-    { action_respond_info("Smart Park location: {},{}.".format(
-        (x_min),
-        (y_min),
-    )) }
-
-    {% endif %}
-
-    {% if printer.toolhead.position.z < z_height %}
-        G0 Z{z_height}                                                                                                              # Move Z to park height if current Z position is lower than z_height
-    {% endif %}
-    G0 X{x_min} Y{y_min} F{travel_speed}                                                                                            # Move near object area
-    G0 Z{z_height}                                                                                                                  # Move Z to park height 

cfgs/kamp/Voron_Purge.cfg

@@ -1,91 +0,0 @@
-[gcode_macro VORON_PURGE]
-description: A purge macro that adapts to be near your actual printed objects
-gcode:
-    # Get relevant printer params
-    {% set travel_speed = (printer.toolhead.max_velocity) * 60 | float %}
-    {% set cross_section = printer.configfile.settings.extruder.max_extrude_cross_section | float %}
-    
-    # Use firmware retraction if it is defined
-    {% if printer.firmware_retraction is defined %}
-        {% set RETRACT = G10 | string %}
-        {% set UNRETRACT = G11 | string %}
-    {% else %}
-        {% set RETRACT = 'G1 E-.5 F2100' | string %}
-        {% set UNRETRACT = 'G1 E.5 F2100' | string %}
-    {% endif %}
-
-    # Get purge settings from _Kamp_Settings
-    {% set kamp_settings = printer["gcode_macro _KAMP_Settings"] %}
-    {% set verbose_enable = kamp_settings.verbose_enable | abs %}
-    {% set purge_height = kamp_settings.purge_height | float %}
-    {% set tip_distance = kamp_settings.tip_distance | float %}
-    {% set purge_margin = kamp_settings.purge_margin | float %}
-    {% set purge_amount = kamp_settings.purge_amount | float %}
-    {% set flow_rate = kamp_settings.flow_rate | float %}
-    {% set size = 10 | float %}
-
-    # Calculate purge origins and centers from objects
-    {% set all_points = printer.exclude_object.objects | map(attribute='polygon') | sum(start=[]) %}    # Get all object points
-    {% set purge_x_min = (all_points | map(attribute=0) | min | default(0)) %}                          # Object x min
-    {% set purge_x_max = (all_points | map(attribute=0) | max | default(0)) %}                          # Object x max
-    {% set purge_y_min = (all_points | map(attribute=1) | min | default(0)) %}                          # Object y min
-    {% set purge_y_max = (all_points | map(attribute=1) | max | default(0)) %}                          # Object y max
-
-    {% set purge_x_center = ([((purge_x_max + purge_x_min) / 2) - (purge_amount / 2), 0] | max) %}      # Create center point of purge line relative to print on X axis
-    {% set purge_y_center = ([((purge_y_max + purge_y_min) / 2) - (purge_amount / 2), 0] | max) %}      # Create center point of purge line relative to print on Y axis
-
-    {% set purge_x_origin = ([purge_x_min - purge_margin, 0] | max) %}                                  # Add margin to x min, compare to 0, and choose the larger
-    {% set purge_y_origin = ([purge_y_min - purge_margin, 0] | max) %}                                  # Add margin to y min, compare to 0, and choose the larger
-
-    # Calculate purge speed
-    {% set purge_move_speed = (flow_rate / 5.0) * 60 | float %}
-
-    {% if cross_section < 5 %}
-
-        {action_respond_info("[Extruder] max_extrude_cross_section is insufficient for purge, please set it to 5 or greater. Purge skipped.")}
-
-    {% else %}
-
-        {% if verbose_enable == True %}
-
-        {action_respond_info("Moving filament tip {}mms".format(                                                                 
-            (tip_distance),                                                                                      
-        )) }
-        {% endif %}
-
-        {% if printer.firmware_retraction is defined %}
-            {action_respond_info("KAMP purge is using firmware retraction.")}
-        {% else %}
-            {action_respond_info("KAMP purge is not using firmware retraction, it is recommended to configure it.")}
-        {% endif %}
-
-            SAVE_GCODE_STATE NAME=Prepurge_State                                                            # Create gcode state
-
-            G92 E0                                                                                          # Reset extruder
-            G0 F{travel_speed}                                                                              # Set travel speed
-            G90                                                                                             # Absolute positioning
-            G0 X{purge_x_origin} Y{purge_y_origin+size/2}                                                   # Move to purge position
-            G0 Z{purge_height}                                                                              # Move to purge Z height
-            M83                                                                                             # Relative extrusion mode
-            G1 E{tip_distance} F{purge_move_speed}                                                          # Move tip of filament to nozzle
-            G1 X{purge_x_origin+size*0.289} Y{purge_y_origin+size} E{purge_amount/4} F{purge_move_speed}    # Purge first line of logo
-            {RETRACT}                                                                                       # Retract
-            G0 Z{purge_height*2}                                                                            # Z hop
-            G0 X{purge_x_origin+size*0.789} Y{purge_y_origin+size}                                          # Move to second purge line origin
-            G0 Z{purge_height}                                                                              # Move to purge Z height
-            {UNRETRACT}                                                                                     # Recover
-            G1 X{purge_x_origin+size*0.211} Y{purge_y_origin} E{purge_amount/2} F{purge_move_speed}         # Purge second line of logo
-            {RETRACT}                                                                                       # Retract
-            G0 Z{purge_height*2}                                                                            # Z hop
-            G0 X{purge_x_origin+size*0.711} Y{purge_y_origin}                                               # Move to third purge line origin
-            G0 Z{purge_height}                                                                              # Move to purge Z height
-            {UNRETRACT}                                                                                     # Recover
-            G1 X{purge_x_origin+size} Y{purge_y_origin+size/2}  E{purge_amount/4} F{purge_move_speed}       # Purge third line of logo
-            {RETRACT}                                                                                       # Retract
-            G92 E0                                                                                          # Reset extruder distance
-            M82                                                                                             # Absolute extrusion mode
-            G0 Z{purge_height*2} F{travel_speed}                                                            # Z hop
-
-            RESTORE_GCODE_STATE NAME=Prepurge_State                                                         # Restore gcode state
-
-    {% endif %}

cfgs/misc-macros.cfg

@@ -1,6 +1,3 @@
-[idle_timeout]
-timeout: 600
-
 [force_move]
 enable_force_move: True
 
@@ -29,12 +26,10 @@ gcode:
     SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=0
 
 [gcode_macro _globals]
-# NOTE 0 = false; 1 = true
 variable_filament_sensor_enabled: 0 # NOTE Enable(1) or disable(0) the filament sensor, if one is connected
 variable_beeping_enabled: 1 # NOTE Enable(1) or disable(0) beeping everywhere except during gantry calibration
-variable_bed_temp_over: 10 # NOTE Start print if bed temperature is over by this amount. Set to 0 to disable, meaning, wait for temperature to drop
-variable_bed_temp_not_exact: 1 # NOTE Start print if bed temperature is `target temperature - 1` (but continue to heat until target is reached)
-variable_kamp_enable: 0 # NOTE Enable(1) or disable(0) KAMP (adaptive mesh)
+variable_bed_temp_over: 10 # NOTE Start print if bed temperature is over by this amount, otherwise wait for temperature drop
+variable_kamp_enable: 1 # NOTE Enable(1) or disable(0) KAMP (adaptive mesh)
 variable_pre_purge_prime_length: 1.40
 gcode:
     # Don't delete this section
@@ -77,20 +72,12 @@ gcode:
 [gcode_macro M190]
 rename_existing: M99190
 gcode:
-    # Global variables/settings
-    {% set bedtempNotExact = printer["gcode_macro _globals"].bed_temp_not_exact|default(1)|int %}
-
     #Parameters
     {% set s = params.S|float %}
 
     M140 {% for p in params %}{'%s%s' % (p, params[p])}{% endfor %}   ; Set bed temp
     {% if s != 0 %}
-        {% if bedtempNotExact == 1 %}
-            TEMPERATURE_WAIT SENSOR=heater_bed MINIMUM={s-1} MAXIMUM={s+1}  ; set & wait for bed temp (within -1 or +1 degree)
-            M140 {% for p in params %}{'%s%s' % (p, params[p])}{% endfor %} ; set & don't wait for bed temp
-        {% else %}
-            TEMPERATURE_WAIT SENSOR=heater_bed MINIMUM={s} MAXIMUM={s+1}    ; Wait for bed temp (within +1 degree)
-        {% endif %}
+        TEMPERATURE_WAIT SENSOR=heater_bed MINIMUM={s} MAXIMUM={s+1}  ; Wait for bed temp (within 1 degree)
     {% endif %}
 
 [gcode_macro PURGE_LINE]

misc/compile-how-to.md

@@ -1,45 +0,0 @@
-${\small{\textcolor{green}{\texttt{2 minute read}}}}$
-
-#### Do I need to re-flash the motherboard?
-
-You will _almost never_ need to re-flash `klipper.bin`. When this is needed, your dashboard will explicitly tell you that you need to re-flash.
-
-#### Where does Klipper live?
-
-1. On the motherboard.
-2. On the host device (Raspberry Pi, etc.).
-
-🗒️ These 2 versions of klipper can rightly differ.
-
-#### Should I update Klipper, moonraker, etc.?
-
-I always update everything on the host device via the dashboard. I don't want to miss out on improvements, especially those that improve safety. What this means is that on some occasions, there will be breaking changes: you will need to change a few things in your config **before you can print**. I would suggest that if you absolutely have to get something printed immediately and there's an update, perhaps wait till after the print completes to do the update.
-
-Others will argue that 'if it ain't broke, don't fix it'.
-
-You have to decide what camp you want to be apart off.
-
-#### How-To
-
-##### Update Klipper repo first
-
-\*\* _For those coming from the_ ${\small{\textcolor{WildStrawberry}{\texttt{Before You B.egin}}}}$ _section (installing Klipper for the first time), complete_ **only** _this section_. No need to compile the firmware, etc.
-
-It's always best to update the Klipper repository that lives on the host before compiling. This ensures that your `klipper.bin` will be as 'fresh' as possible.
-
-- In `Fluidd`, you can do this from `Settings` > `Software Updates`.
-- In `Mainsail`, you can do this from `Machine` > `Update Manager`.
-
-##### Compile `klipper.bin`
-
-🗒️ The `compilation settings` you see in the image below apply only the the `SV06/Plus` boards, but the steps for compilation apply to any board.
-
-1. `ssh` into the Klipper host (i.e., RPi, OrangePi, etc.).
-2. `cd ~/klipper`
-3. `make menuconfig`
-4. Set things up to look as follows:
-   ![make-menuconfig](https://github.com/bassamanator/Sovol-SV06-firmware/assets/61985779/22298d47-2604-4231-ad10-7d6793be7904)
-5. `make clean`
-   - Clears `~/klipper/out/`
-6. `make`
-   - Compiles `klipper.bin` and puts it in `~/klipper/out/`

misc/how-to-update.md

@@ -1,73 +0,0 @@
-\*\* _Flashing the firmware is not required for any method_
-
-## Should You Update?
-
-I treat this config like software, and like any piece of modern software, it will require periodic updates to fix issues, add features, improve functionality, etc. So, if you want to have the latest and greatest, I recommend you periodically pull the changes from this repo.
-
-### What Changes Should You Be Concerned With
-
-The only changes you need to be concerned with relate to the `.cfg` and `.conf` files; all changes to `.md` files (these are markdown files, the text that you see when you visit this repo) can be ignored.
-
-### Git Users
-
-If you do a `git diff origin/master --name-only` and it shows you that a `.cfg` file has changed, you might want to pull in those changes (but you don't have to).
-
-### Non-Git Users
-
-Unfortunately, there's no simple way for you to ascertain whether there have been changes. I simply recommend that you update your config via the instructions below from time to time.
-
-## How to Update
-
-There are three methods to accomplish this:
-
-1. The correct method, using `git`.
-2. The mostly acceptable method, without using `git`.
-3. The start-from-scratch method. _Recommended for non-git users and those who haven't made many changes to their configuration._
-
-### The `git` method.
-
-⚠️ This method is only intended for those who already know how to use `git`.
-
-📝 In this example, I'm using the `master` branch which applies to SV06 users only. Be sure to use the appropriate branch for your printer.
-
-📝 The assumption is that you didn't change branches after the initial setup, so you are in `master`, and there are many untracked changes.
-
-1. `ssh` into your Klipper host.
-2. `cd ~/printer_data/config`
-3. `git checkout -b my-settings`
-4. `git add .`
-5. `git commit -m "Saving my settings."`
-6. `git checkout master`
-7. `git pull`
-8. `git checkout my-settings`
-9. `git merge master --no-ff --no-commit`
-10. Deal with comparing and pulling in incoming changes from `master` using your favourite code editor. You can also do this from the command line via `git commit --interactive`, however, only advanced `git` users should attempt this, though it is easy enough.
-11. Add all welcomed changes to the staging area, and discard all other changes.
-12. `git commit -m "Update with upstream."`
-
-You should push your branch to your own fork of this repo.
-
-For any future updates, you can run through the same process again, however, you cannot re-create the `my-settings` branch as you did in `step 3`, because it already exists. Simply omit the `-b` flag in `step 3` next time you update.
-
-### The mostly acceptable method.
-
-This method has shortcomings, because it relies on the user's memory, and requires more manual edits. Perfectly functional method, however.
-
-1. Read all the documentation.
-2. Backup your current configuration, essentially everything inside `~/printer_data/config`.
-3. Repeat steps in [Download OSS Klipper Configuration](https://github.com/bassamanator/Sovol-SV06-firmware#download-oss-klipper-configuration), and [Adjust Configuration with MCU Path](https://github.com/bassamanator/Sovol-SV06-firmware#adjust-configuration-with-mcu-path).
-4. Copy everything from `#*# <---------------------- SAVE_CONFIG ---------------------->` onward and paste into new `printer.cfg`, inclusive.
-5. Copy any other changes you might have made into the new configuration. Maybe you had adjusted the size of your printer (`position_max`), or other such changes.
-
-### The start-from-scratch method.
-
-1. Delete the folder `~/printer_data/config`.
-2. Recreate the folder `~/printer_data/config` via `mkdir ~/printer_data/config`.
-3. Start the Klipper installation process starting from `Download OSS Klipper Configuration` in the appropriate branch.
-
-## Linux Tips
-
-- In linux, you can delete files via `rm fileName` and directories via `rmdir directoryName`.
-- In linux, you can list files and folders via `ls -lah`.
-
-You are now up-to-date with this repo, and have added your personal settings on top.

misc/orcaslicer-bundles/how-to-generate/README.md

@@ -1,15 +0,0 @@
-## Converting PrusaSlicer/SuperSlicer config bundles to OrcaSlicer
-
-OrcaSlicer configs can be converted from PrusaSlicer using [SuperSlicer_to_Orca_scripts](https://github.com/apparle/SuperSlicer_to_Orca_scripts). It is a fork of theophile's script with some enhancements which haven't been merged yet ([theophile/SuperSlicer_to_Orca_scripts#43](https://github.com/theophile/SuperSlicer_to_Orca_scripts/pull/43)). It does require a few perl modules which can be installed using `cpanminus` (or your favorite perl module manager).
-
-Most of the script is automated, with the exception of `printer_model` field which must be manually specified with a `json`. This attribute is used by OrcaSlicer to load the appropriate build plate images & STLs.
-
-```
-perl SuperSlicer_to_Orca_scripts/superslicer_to_orca.pl --input PrusaSlicer_config_bundle-2.9.2.ini --nozzle-size 0.4 --compatible_printers_condition KEEP --skip-link-system-printer --printer-models-json printer_models_conversion_mapping.json --output-config-bundle OrcaSlicer_config_bundle-2.9.2-DEV.zip
-```
-
-## How to use OrcaSlicer bundle:
-
-This config bundle can be imported into OrcaSlicer : `File > Import > Import configs...`
-
-Note, OrcaSlicer reformats the `json` and adds some default attributes, so the imported files cannot be directly compared with the contents of the zipped bundle. But you can use json comparison tools like [https://www.jsondiff.com/](https://www.jsondiff.com/) to analyze the differences if needed.

misc/orcaslicer-bundles/how-to-generate/printer_models_conversion_mapping.json

@@ -1,12 +0,0 @@
-{
-	"SV06 0.4 nozzle": "Sovol SV06",
-	"SV06 0.6 nozzle": "Sovol SV06",
-	"SV06 ACE 0.4 nozzle": "Sovol SV06 ACE",
-	"SV06 ACE 0.6 nozzle": "Sovol SV06 ACE",
-	"SV06 Plus 0.4 nozzle": "Sovol SV06 Plus",
-	"SV06 Plus 0.6 nozzle": "Sovol SV06 Plus",
-	"SV07 0.4 nozzle": "Sovol SV07",
-	"SV07 0.6 nozzle": "Sovol SV07",
-	"SV07 Plus 0.4 nozzle": "Sovol SV07 Plus",
-	"SV07 Plus 0.6 nozzle": "Sovol SV07 Plus"
-}

misc/update-hot-to.md

@@ -1,73 +0,0 @@
-\*\* _Flashing the firmware is not required for any method_
-
-## Should You Update?
-
-I treat this config like software, and like any piece of modern software, it will require periodic updates to fix issues, add features, improve functionality, etc. So, if you want to have the latest and greatest, I recommend you periodically pull the changes from this repo.
-
-### What Changes Should You Be Concerned With
-
-The only changes you need to be concerned with relate to the `.cfg` and `.conf` files; all changes to `.md` files (these are markdown files, the text that you see when you visit this repo) can be ignored.
-
-### Git Users
-
-If you do a `git diff origin/master --name-only` and it shows you that a `.cfg` file has changed, you might want to pull in those changes (but you don't have to).
-
-### Non-Git Users
-
-Unfortunately, there's no simple way for you to ascertain whether there have been changes. I simply recommend that you update your config via the instructions below from time to time.
-
-## Hot to Update
-
-There are three methods to accomplish this:
-
-1. The correct method, using `git`.
-2. The mostly acceptable method, without using `git`.
-3. The start-from-scratch method. _Recommended for non-git users and those who haven't made many changes to their configuration._
-
-### The `git` method.
-
-⚠️ This method is only intended for those who already know how to use `git`.
-
-🗒️ In this example, I'm using the `master` branch which applies to SV06 users only. Be sure to use the appropriate branch for your printer.
-
-🗒️ The assumption is that you didn't change branches after the initial setup, so you are in `master`, and there are many untracked changes.
-
-1. `ssh` into your Klipper host.
-2. `cd ~/printer_data/config`
-3. `git checkout -b my-settings`
-4. `git add .`
-5. `git commit -m "Saving my settings."`
-6. `git checkout master`
-7. `git pull`
-8. `git checkout my-settings`
-9. `git merge master --no-ff --no-commit`
-10. Deal with comparing and pulling in incoming changes from `master` using your favourite code editor. You can also do this from the command line via `git commit --interactive`, however, only advanced `git` users should attempt this, though it is easy enough.
-11. Add all welcomed changes to the staging area, and discard all other changes.
-12. `git commit -m "Update with upstream."`
-
-You should push your branch to your own fork of this repo.
-
-For any future updates, you can run through the same process again, however, you cannot re-create the `my-settings` branch as you did in `step 3`, because it already exists. Simply omit the `-b` flag in `step 3` next time you update.
-
-### The mostly acceptable method.
-
-This method has shortcomings, because it relies on the user's memory, and requires more manual edits. Perfectly functional method, however.
-
-1. Read all the documentation.
-2. Backup your current configuration, essentially everything inside `~/printer_data/config`.
-3. Repeat steps in [Download OSS Klipper Configuration](https://github.com/bassamanator/Sovol-SV06-firmware#download-oss-klipper-configuration), and [Adjust Configuration with MCU Path](https://github.com/bassamanator/Sovol-SV06-firmware#adjust-configuration-with-mcu-path).
-4. Copy everything from `#*# <---------------------- SAVE_CONFIG ---------------------->` onward and paste into new `printer.cfg`, inclusive.
-5. Copy any other changes you might have made into the new configuration. Maybe you had adjusted the size of your printer (`position_max`), or other such changes.
-
-### The start-from-scratch method.
-
-1. Delete the folder `~/printer_data/config`.
-2. Recreate the folder `~/printer_data/config` via `mkdir ~/printer_data/config`.
-3. Start the Klipper installation process starting from `Download OSS Klipper Configuration` in the appropriate branch.
-
-## Linux Tips
-
-- In linux, you can delete files via `rm fileName` and directories via `rmdir directoryName`.
-- In linux, you can list files and folders via `ls -lah`.
-
-You are now up-to-date with this repo, and have added your personal settings on top.

osskc.cfg

@@ -3,7 +3,6 @@
 [include ./cfgs/MECHANICAL_GANTRY_CALIBRATION.cfg]
 [include ./cfgs/CALIBRATION.cfg]
 [include ./cfgs/kamp/KAMP_Settings.cfg]
-[include ./cfgs/TEST_SPEED.cfg]
 
 # NOTE Uncomment the ONE of the following lines if you're using an adxl345
 # [include ./cfgs/adxl-rp2040.cfg]

printer.cfg

@@ -96,7 +96,7 @@ step_pin: PB4
 dir_pin: !PB3
 enable_pin: !PC3
 microsteps: 128
-rotation_distance: 4.65 # NOTE Calibrate e-steps https://www.klipper3d.org/Rotation_Distance.html#calibrating-rotation_distance-on-extruders, https://github.com/bassamanator/everything-sovol-sv06/blob/main/howto.md#calibrate-esteps
+rotation_distance: 4.65 # NOTE Calibrate e-steps and adjust https://www.klipper3d.org/Rotation_Distance.html
 nozzle_diameter: 0.400
 filament_diameter: 1.750
 heater_pin: PA1
@@ -109,7 +109,6 @@ pid_ki: 1.326
 min_temp: 0
 max_temp: 300
 max_extrude_only_distance: 150.0
-max_extrude_cross_section: 5 # NOTE Needed for KAMP purge
 
 [tmc2209 extruder]
 uart_pin: PC14
@@ -156,19 +155,14 @@ z_hop_speed: 15
 
 [bed_mesh]
 speed: 175
-mesh_min: 27, 6 # probe as close to origin as possible while remaining fully on the bed
-mesh_max: 222, 203 # (x.position_max - 1), (y.position_max - abs(y_offset)) ; probe as far as possible from the origin while remaining fully on the bed
+mesh_min: 27, 5
+mesh_max: 222, 203
 probe_count: 5,5
 algorithm: bicubic
 fade_start: 1
 fade_end: 10
 fade_target: 0
 
-[axis_twist_compensation]
-calibrate_start_x: 27 # probe x coor at furthest left ; abs(x_offset)
-calibrate_end_x: 195 # probe x coor at furthest right ; (x.position_max - abs(x_offset) - 1)
-calibrate_y: 115
-
 #####################################################################
 #   Fans
 #####################################################################