firmware_Ender6_BLT_DW7.4.bin causes crashing into bed

[JCSWeb]

When testing this firmware, the probe extends but then crashes into the bed.

BL Touch is connected via the splash / breakout board provided with the Ender 6.

[JCSWeb]

So it seems using this firmware it expects the BL Touch to be wired as the Z endstop switch which the filename structure doesn't suggest. After rewiring to utilise the Z stop I managed to get the printer to home.

Mesh leveling now seems to fail though. When initially going onto the mesh process, it attempts to start, homes, then kicks back out and stops without any messages.

[InsanityAutomation]

I'm putting this machine back on the bench this morning, so hopefully it can get sorted quickly :)

[kathagor]

👍 Super. i think it is only the wrong pin mapped for the bltouch, because ender6 uses a dedicated pin for the bltouch. And the printer reacts to the z endstop like it Was the bltouch. InsanityAutomation ***@***.***> schrieb am Sa., 3. Juli 2021, 15:24:

…

I'm putting this machine back on the bench this morning, so hopefully it can get sorted quickly :) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#207 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC2LFDXGTWDZJBGPDDOBWGDTV4FQRANCNFSM47SQINNA> .

[InsanityAutomation]

Updated hex files have been uploaded! Please let me know if any issues persist.

[subhead]

Updated hex files have been uploaded! Please let me know if any issues persist.

Where can i find these updated hex files?

[JCSWeb]

Updated hex files have been uploaded! Please let me know if any issues persist.

Perfect, Will test when I can. On holiday right now (no, I wasn't allowed to bring the printer) so will try and report back when I can 👍

[subhead]

Alright nevermind. Found the branch with the hex files.

[subhead]

I updated my Ender 6 with the latest BLTouch version. Some issues i found so far:

• Auto Leveling can not toggled on. After pressing on it it still remains off.
• After pressing the Z +/- buttons the bed did not move closer or further away from the nozzle. Instead it only shows on the screen that the new z offset is written. With that no initial bed leveling is possible.

[InsanityAutomation]

I updated my Ender 6 with the latest BLTouch version. Some issues i found so far:

* Auto Leveling can not toggled on. After pressing on it it still remains off.

* After pressing the  Z +/- buttons the bed did not move closer or further away from the nozzle. Instead it only shows on the screen that the new z offset is written. With that no initial bed leveling is possible.

I didnt see that behavior earlier today, i have it set with the z offset over 2mm off so i can see the drastic move when testing that. Any chance you can get a serial log from that occurring? The leveling state wont turn on if the mesh isnt valid, but that should be reported in the log as well. I usually totally ignore the button for it personally, let start gcode call it on for a safety anyway.

[banpot]

I updated my Ender 6 with the latest BLTouch version. Some issues i found so far:

* Auto Leveling can not toggled on. After pressing on it it still remains off.

* After pressing the  Z +/- buttons the bed did not move closer or further away from the nozzle. Instead it only shows on the screen that the new z offset is written. With that no initial bed leveling is possible.

I didnt see that behavior earlier today, i have it set with the z offset over 2mm off so i can see the drastic move when testing that. Any chance you can get a serial log from that occurring? The leveling state wont turn on if the mesh isnt valid, but that should be reported in the log as well. I usually totally ignore the button for it personally, let start gcode call it on for a safety anyway.

I face the same trouble, when pressing measure icon, it's look freezing my ender6 for a few minutes, cannot press any button. After minutes of waiting, the mesh measurement continue to works like a charm.

Toggleing Auto Leveling has the same problem as @subhead mentioned. but after waiting for mesh measuring for few minutes, it automatically toggled to ON.

[InsanityAutomation]

@banpot Have the screen files been flashed? There should be a bed heating message after pressing measuring that indicates what its doing / waiting for. It will reject other tasks until the current task is complete.

[notfixingit3]

@InsanityAutomation

solved 1) The screen flashes for a second (does not show heating message and appears to freeze). After waiting (can see temp rise on octoprint) it does its thing.

solved 2) It never shows the z offset when adjusting and it does not seem to save it, also when exiting out of leveling and going back in, it slams the nozzle into the bed or when pressing home, same issue.--

3. Z offset buttons are backwards, up lowers the bed

Maybe I missed the screen flashing bit? Would that cause the above issues? (Stock Ender 6 Touch Screen)

edit, found screen firmware, will upgrade later today and update this post after a retest
So 1 and 2 are solved by the screen firmware, there wasn't a guide for the Ender 6, so I just missed this step. Sorry my bad.

As for 3, all Z arrows are backwards, maybe I should open that as it's own issue? At least I can confirm though that the heating message does appear

[InsanityAutomation]

The Z arrows were the source of some debate. Currently, the motion is consistent with the axis position being increased or decreased. Users from the older machines (Ender 5 Plus) or from CNC operations were expecting this operation. The ender 6, Creality swapped the 2 buttons from the screen side. Currently, the direction on those is by design, so not a bug though I do understand its different than how it was on this machine originally.

[notfixingit3]

Ah ok, that makes sense, thank you! I think just using the stock Ender 6 since I got it and not having experience with others, my brain just logically defaults to up is up and down is down. Nots sure if it's possible, but maybe an option to invert the controls (or maybe it's not worth it)? This makes me realize now why I had to invert Z in octoprint originally