GithubHelp home page GithubHelp logo

digant73 / artillery-sidewinder-x1_releases_tft Goto Github PK

View Code? Open in Web Editor NEW
8.0 8.0 5.0 55.85 MB

releases_tft

C 98.54% C++ 0.01% HTML 0.83% Python 0.05% Dockerfile 0.01% SourcePawn 0.09% Pawn 0.05% Assembly 0.45%

artillery-sidewinder-x1_releases_tft's People

Contributors

digant73 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

artillery-sidewinder-x1_releases_tft's Issues

Mesh Bed level editing misbehavour

Hi @digant73 first of all thanks for your firmware releases! :)

I am having an issue when editing my mesh bed level.
So lets say I have a mesh bed level point adjusted to 0.13mm already, but I want to edit that spot. I click on the spot to edit it and the print head jumps to the correct location and z height right?
Unfortunately the software wrongly calculates the z height, meaning it calculates 0.13mm on top of the already present 0.13mm offset in the printer. So to really go to the height that we want to adjust we need to go down from 0.13mm to 0! But when we do that the printer software shows every point in the mesh bed as 0 (if we adjust all points)!

I dont know if this is understandable, so here is how to reproduce:

  1. Set initial mesh bed leveling with MBL wizard and save to marlin firmware
  2. Edit a mesh bed leveling point of your choice
  3. Notice that the nozzle is not at the correct height while editing. Basically it is at offset + offset.
  4. Set your offset to zero and notice that now your nozzle is at the height you have previously defined
  5. Save that new setting and notice that now this point is shown as 0 offset value in the menu... which is wrong!

It is at zero offset from the saved value yes, because the software does not calculate that the firmware already compensated the offset.

Now imagine you actually want to edit a value, than you would end up with smth like 0.1mm, which would actually mean 0.13mm + 0.1mm. So it's a total mess!

Sounds confusing but I hope I explained it well enough! Posting this here as I did not know if it's an upstream or downstream issue, but I think it is a pretty major bug for mesh bed leveling.

EDIT: I have no experience in hw programming, but I noticed that when doing "bed leveling" (not mesh bed leveling), the software jumps to the "real" z height ignoring mesh bed leveling values. I assume this is on purpose, but Im mentioning it in case it contains useful code to fix this bug :)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.