G29A Successfully Enabled UBL, But M420 S1 Says Mesh Is Invalid.

Trang chủ » G29 Vs M420 » G29A Successfully Enabled UBL, But M420 S1 Says Mesh Is Invalid.

Có thể bạn quan tâm

Skip to content Dismiss alert {{ message }} / Marlin Public

  • Uh oh!

    There was an error while loading. Please reload this page.

  • Notifications You must be signed in to change notification settings
  • Fork 19.7k
  • Star 17.3k
  • Code
  • Issues 699
  • Pull requests 105
  • Actions
  • Projects 2
  • Security
  • Insights
Additional navigation options G29A successfully enabled UBL, but M420 S1 says mesh is invalid. #17100New issueNew issueClosedClosedG29A successfully enabled UBL, but M420 S1 says mesh is invalid.#17100LabelsF: U.B.L.@RFBomb

Description

@RFBombRFBombopened on Mar 9, 2020

Bug Description

~Unsure if this is actually a bug or not, but my printer when performing "G29 P1" only hits 57/100 points then says it is done. ~

Edit Description: I believe I determined the initial cause for this -- I have to test it once I'm home this weekend. The parameter for probe-distance-from-edge in the configuration.h file for the probe is set default to 10. I think if I set it to 0 it will properly hit the edges that previous G29 P1 commands skipped over.

The real issue here I think is that 'G29 A' and 'M420 S1' are giving different results.

  • G29 A reports a 'success' when activating UBL
  • M420 S1 reports a failure to activate the mesh due to invalid mesh.

According to the documentation, these two commands seem to be identical, so I'm confused as to why the results are success vs failure.

My Configurations

I am using BL-Touch on an Ender 3 with a SKR1.3 board. The probe, is attached to Z_Max Pin (per the SKR default probe pin). I am also using a microswitch on Z_Min. Here are my configured offsets: M206 X0.00 Y0.00 Z-0.97 M851 X-44 Y-14 Z-0.7

MyConfig.zip

Steps to Reproduce

  1. G28
  2. G29 P1 -> it will probe 57/100 locations
  3. M500 4.1 G29 A >> Reports success 4.2 M420 S1 >> Reports failure

PronterFace_Console.txt attached above is the text i copied from the Pronterface console with everything I did.

Expected behavior: [What you expect to happen] According to the MarlinFW website, G29 A looks like it is just a shortcut for "M420 S1", so I would expect them to have the same output.

Actual behavior: [What actually happens]

G29 A says the UBL becomes active, but M420 S1 won't activate the mesh because its invalid

Additional Information

Excerpt from the Pronterface Console

M420 S1 L0 SENDING:M420 S1 L0 Mesh loaded from slot 0 Bed Topography Report: ( 1,234) (234,234) 0 1 2 3 4 5 6 7 8 9 9 | . . . . . . . . . . | 8 | . +2.090 +2.142 +2.252 +2.340 +2.410 +2.505 +2.555 . . | 7 | . +2.120 +2.177 +2.277 +2.357 +2.455 +2.530 +2.597 . . | 6 | . +2.112 +2.177 +2.247 +2.347 +2.440 +2.515 +2.570 . . | 5 | . +2.067 +2.145 +2.240 +2.337 +2.452 +2.552 +2.610 . . | 4 | . +2.097 +2.165 +2.260 +2.380 +2.482 +2.595 +2.640 . . | 3 | . +2.122 +2.197 +2.313 +2.412 +2.517 +2.625 +2.672 . . | 2 | . +2.140 +2.217 +2.330 +2.427 +2.537 +2.645 +2.705 . . | 1 | . +2.152 +2.235 +2.337 +2.427 +2.545 +2.650 +2.702 . . | 0 | . . . . . . . . . . 0 1 2 3 4 5 6 7 8 9 ( 1, 1) (234, 1) Mesh is invalid Storage slot: 0 echo:Invalid mesh. Error:Failed to enable Bed Leveling [ERROR] Error:Failed to enable Bed Leveling echo:Bed Leveling OFF echo:Fade Height OFF >>> M420 S1 SENDING:M420 S1 echo:Invalid mesh. Error:Failed to enable Bed Leveling [ERROR] Error:Failed to enable Bed Leveling echo:Bed Leveling OFF echo:Fade Height OFF >>> G29 A SENDING:G29 A Unified Bed Leveling System v1.01 active

Metadata

Metadata

Assignees

No one assigned

Labels

F: U.B.L.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

You can’t perform that action at this time.

Từ khóa » G29 Vs M420