bigtreetech / BIGTREETECH-TouchScreenFirmware

support TFT35 V1.0/V1.1/V1.2/V2.0/V3.0, TFT28, TFT24 V1.1, TFT43, TFT50, TFT70
GNU General Public License v3.0
1.31k stars 1.65k forks source link

THT35v3E3 can`t activate mesh leveling menu on touch mode #1281

Closed FoxtrottPL closed 3 years ago

FoxtrottPL commented 3 years ago

SKRmini e3v2 with TFT 35 v3e3 1.board firmware prepare to use mesh bed leveling with 6x6 grid 2 after factory reset of motherboard then prepare to upload TFT firmware 3 I used 3 firmwares Unified , "normal" ,Red
a.on unified - missing few bmp and wrong keyword mesh_min_color mesh_max_color b.on normal wrong keywords mesh_min_color and mesh_max_color c.Red - bltouch menu present (without blt connected )

  1. When I switch to Merlin mode - mesh leveling present and used to calibrate bed . Stored to eeprom, activate eeprom. 5.Switching back to touch mode - mesh leveling menu not present , mesh grid not present. off course always factory reset , reset eeprom etc.
oldman4U commented 3 years ago

In case your firmware under Menu - Settings - Info is from September, please read this and see if it solves your problem:

https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/issues/1282

Thank you

oldman4U commented 3 years ago

Any news?

oldman4U commented 3 years ago

Please help the community and close the ticket once you do not need it anymore. Thank you

Codel1417 commented 3 years ago

Similar issue here. MArlin 2.0.7.2, TFT December 26 master except the mesh is created in touch mode and shows up on the mesh edit screen but cant be activated due to invalid mesh

Codel1417 commented 3 years ago
switch (key_num)
    {
      case KEY_ICON_0:
      case KEY_ICON_1:
      case KEY_ICON_2:
      case KEY_ICON_3:
        ublSlot = key_num;

        setDialogText(UBLSaveLoadItems.title.index, LABEL_CONFIRMATION, LABEL_CONFIRM, LABEL_CANCEL);
        showDialog(DIALOG_TYPE_QUESTION, ublSaveloadConfirm, NULL, NULL);
        break;

This looks valid but it could be the issue. Every other piece of gcode checks out so i wonder if the correct slot is being used. I need to debug over serial to confirm

Codel1417 commented 3 years ago
  1. G29 P1 // initial Level
  2. G29 P3 // fill in some gaps
  3. M118 A1 UBL Complete
  4. G29 S0 // save to slot 0
  5. M500 // save to eeprom
  6. M420 S1 //enable ubl

Send: M420 S1 Recv: echo:Invalid mesh. Recv: Error:Failed to enable Bed Leveling Recv: echo:Bed Leveling OFF

Only 57/100 points were filled using this command setup, which is what is currently used. all 100 must be filled in.

Codel1417 commented 3 years ago

@FoxtrottPL have you tried any of the newer binaries?

Codel1417 commented 3 years ago

Sorry for solving another issue within this one. kinda got carried away. Still would have fit under the same title though.

oldman4U commented 3 years ago

Hi. I add @digant73. He developed this and is very likely not watching this 1y old ticket.

digant73 commented 3 years ago

I have also Marlin 2.0.7.2 and with a 10x10 grid a didn't have that problem (with 57 of 100 points probed). Also in the Marlin home page, I didn't read any need to use multiple G29 P3 to fill in the grid. However, it seems that the solution works for you

Codel1417 commented 3 years ago

@digant73 its specific to Unified Bed Leveling. Marlin requires all points to be filled. in their demo gcode they indicate to rerun g29 p3 as many times as needed

digant73 commented 3 years ago

@foxtrottpl if you don‘t see bl and mesh editor menu, verify all the marlin options reported at the beginning of config.ini are enabled in marlin fw

Nascire commented 3 years ago

I had the same problem (Invalid Mesh / Cannot activate bed leveling) - through this issue I tried G29 P3 (as some spots where empty) and now it´s working. Manually activating in LCD-Mode was no problem however.

github-actions[bot] commented 6 months ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.