ADD ADDITIONAL CONFIGS

ADD .drone.yml

Update .gitignore
Update MK3 Mesh Definitions

Fixes #1
MK3 BMG Z_MAX_POS 210
* Only MK3S FW needs to have 205/204 as MK3 Printer type is set to MK3 for BMG MK3, so the default 210 should work fine.

USE GOLD BUILD

* Uses the python script from https://github.com/nato2k/Skelestruder_Firmware_Patch

…ild.sh builds instead (Travis job will still run the other builds)

Skelestruder Build is for 16 Microsteps

Add Bear Gearbox 16MS Variant

Changes for Gearbox 16 MS

Rename to match convention

Update Display Name for Gearbox Variant

Update Gearbox Configs

Thanks for the wonderful work and making all the variants explicit, this was really helpful!
I had a concern with respect to Bondtech BMG and MK3S firmware, and the way Prusa fixed it and how for a bondtech it reduces Z_MAX_POS.

Basically, instead of increasing Z_MAX_POS for the MK3S by 6, Prusa decided to leave it as is,
and... to extend the travel down when calibrating XYZ by 7.
As a result, Prusa's "S" firmware does not work for a taller extruder, like the Bondtech for the "S" variant.

What Prusa _should_ have done is INCREASE Z_MAX_POS in their variant by 6 for the "S" extruder and
leave the "travel down mechanism"for XYZ calibration as it was.
Then we could have kept the Z_MAX_POS to 210 for BMG variants and all would be fine.

Now, we have a smaller Z_MAX_POS as necessary, if we want to use the "S" firmware.

I implemented it - in my opinion - correctly in the branch, by introducing a new variable to work exactly "where it hurts":
during Z calibration: see the pull request.

In particular, look at Marlin_main.cpp at line 2121 and the "S" variants, that now set the offset correctly (basically to 9 for "S" extruders and 2 elsewhere..)
There is also an unclear thing in the Prusa file, in that they test for "MK3", (the alternative being MK3S), but the should have tested on MK3S and MK2.5S and then have all the others as alternative.
My variant puts that test "out of order" and sets the desired XYZ calibration travel to the correct value for each extruder.

I issued a pull request to Prusa, but have little hope that they would do it correctly, or even better: set Z_MAX_POS for their "S" variants to 217 and leave the algorithm in Marlin_main.cpp like how it was before, then Prusa owners would "enjoy" higher Z....

To summarize: the change is easy: only one file (marlin_main.cpp) and a new constant in each variant. I just went through the many variant files to set it.

I hope it is clear (and I believe it to be cleaner).
Added #define for Z_MAX_POS_XYZ_CALIBRATION_CORRECTION in order to configure XYZ calibration for a Bondtech and Bear extruder for the MK3S.
Gearbox: Use Z_MAX_POS_XYZ_CALIBRATION_CORRECTION

MMU2S More Load Patch

Add 32 and 8 Microstepping Skelestruder Builds

Rename MK25S-BMG Variants

Remove all geared 1/32 micostep options / Add 1/8 microstep for BMG

Add Watchdog Support

* Creates unique FW file names

Remove git reset to retain epoch build number for skele

* Microstepping can now be set via M350 for EINSY

* Update fsensor.cpp

M600 Z_MAX_POS

* Update Marlin_main.cpp

M600 Z_MAX_POS

Creates scripts based on base script so that updates from Prusa can be more easily merged into variant configs.

* Remove Gearbox
* Remove load more patch
* Rename BMG to Bondtech (Bondtech Prusa Extruder)
* Add 320Z Variants
* Add MK25 Variants

Update create_variant.sh script
* Create Slice Thermistor Variants

Add Bondtech Slice Thermistor Variants

Rename Slice Thermistor Variants

Fix MK2S SliceHT

Enable Cutter
Update Variants 


Update Variants


Update Variants
* ADD Silver PSU for Bondtech-16-SliceHT

* Source Zaribo FW Fork (3d-gussner)

* Enable OLED in all Variants

* Bondtech Updates

Move hardcoded TMC2130 parameters to Variants for MK3 and MK3S and split X and Y to independant microstep settings

Add MK3S variant for 0.9 deg steppers motors on X and Y using TMC2130 settings from GuyKuo.

Run create_variants.sh to propogate TMC2130 parameters to all variants files.

Removed BMG related configurations not specifically generated by create_variants.sh