Anyone with a 3d printer that can run vanilla Marlin AND using automatic bed

3D Printing
, , , ,
1

Anyone with a 3d printer that can run vanilla Marlin AND using automatic bed compensation want to test my fork?

I’ve submitted a pull request for these changes (just changing AUTO_BED_LEVELING to AUTO_BED_COMPENSATION basically) but since I’m using the Printrbot fork of Marlin I can’t test it. If anyone can and wants to, I’d be most appreciative of any feedback or confirmation of functionality.

And take it easy on me. This is the first time I’ve tried to use Github for anything but comments and certainly the first time I’ve tried to fork anything. Thanks!

2

Can you tell what you did? Not sure bed compensation gives enough information to understand what are the improvements/changes.

3

@Brad_Hopper ​ It is only a change of the name of the feature AUTO_BED_LEVELING to AUTO_BED_COMPENSATION.

4

Don’t quite understand the point of just changing the name only. What would be the reason to try and what sort of feedback are you looking for?

5

@Brad_Hopper ​ Several of us have been lobbying to do away with the term “level” altogether when talking about 3d printer platform adjustment/alignment.

https://plus.google.com/105535247347788377245/posts/JgA8zRGs47a

Arguably “AUTO_BED_LEVELING” is even more incorrect because it implies that the alignment of the bed is being manipulated when in fact its misalignment is being compensated for. More critically, because of the popularity of Marlin firmware, as long as Marlin contniues to call it AUTO_BED_LEVELING, we don’t have much hope of ever expunging those (misleading) terms from the community lexicon. That’s all this change is about. Fingers crossed.

The only feedback I’d be looking for is “did I break anything?”. I attempted to merely change “level” and “leveling” in every relevant instance to “compensation”. If I found every instance (there were dozens of instances across a handful of different files) and didn’t make any typos, etc. I don’t think anything should be broken, but those are some sizeable ifs so it seems prudent to test for basic functionality of the firmware and that specific feature if possible.