Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CR-10S Pro with BTL and UBL issue #210

Open
cactixxx opened this issue Jul 7, 2021 · 1 comment
Open

CR-10S Pro with BTL and UBL issue #210

cactixxx opened this issue Jul 7, 2021 · 1 comment

Comments

@cactixxx
Copy link

cactixxx commented Jul 7, 2021

Description

I upgraded my CR-10S Pro with a BLTouch to 7.4 using 10SPro_BLT_UBL_DW7.4.hex and TM3D_DWINCombinedScreens_V4.7z

When auto leveling the probe does not probe in sequence and the position of the probe does not match the screen. The machine only probes 16 points although it should probe 36 points according to the screen. It stops and saves the results once it reaches position 17/36. The screen only has 25 positions available.

Steps to Reproduce

  1. Click on Settings -> Leveling
  2. The printer head will Auto Home and move to the center of the board (as expected).
  3. Click on Measuring. After the bed heats. The head will auto home and measuring will start (as expected)
  4. The probe will probe the 16 middle positions in a non sequence way - the position on the screen will not match the position probed. The first position probed is one position to the right of center. The screen will change the top left value.
  5. Once the probe reaches position 17/36 it will stop and center in the middle. The extruder will heat up and finally a message will be displayed "Settings Saved".

Expected behavior

The system should probe in sequence. The probe position should match the position on screen. The screen should be extended to show 36 values or the probe points should be reduces to a 5x5 grid. The entire bord should be probed and not only the 16 inner positions. I want to be able to fine tune the probed values using UBL, but it's impossible to know which value on the screen matches the probed value.

@InsanityAutomation
Copy link
Owner

UBL is a little different... It creates mesh points where the probe cannot physically reach. At the moment that is the expected behavior, but it definitely needs more work to be presented in a smooth fashion. The mesh area must cover the full movement area as UBL does not handle off mesh movements well and this causes some of the oddities.

Some change upstream awhile back caused the UBL numbering on reporting to occur differently. I intend to track down why at some point, but the UBL userbase is fairly small so there continue to be higher priority items elsewhere. On the next power cycle, all mesh points are recalled and displayed at the proper positions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants