Great, thanks. You helped us confirming a bug.
Just reflashed my only printer not running and no error.
Just glad i can help!
1 Like
Error was on my LR3 not the printer. I homed the printer after getting the error on the LR3 and it had no error
Odd.
It has to be a leftover from flashing the wrong firmware first. If I am not mistaken you flashed the plain firmware before mine?
Just to drive that point home, here is how they flash fresh out of the box.
If I flash them again the background is black and right side up. Something must be getting left behind from different flashes.
On my LR3 this is the first and only flash i have done. Screen came from you when i ordered the build kit. I have homed in TFT mode on that machine before and dont remember ever getting the M420 message before but I cant be certain. Should i try and flash it again with the CNC firmware and see if i still get the message?
I just updated a TFT, and had to reset the baud rate. Not too bad.
What I’m sad about is now I can’t light the knob LED lights any more. The older firmware let me set the knob LEDs to different colours, but the new firmware does not.
Mine changes all kinds of colors. Lights up with the heat cycles as well. Dont remember if it did that before the update or not.
With the V2 that I put up today, or on a CNC?
It would not have that error on a printer. The printer understands M420. It has to be tested against the LR.
Definitely doesn’t happen there. I have homed it at least 5 times so far today. I have been cutting panels. That one is using the current release package as well.
WAIT!!! It happened!
Hmmmmm, okay. Now I can figure out how the heck to proceed.
Well, that was a mess. Now why is it happening. I tested it so many times. I flashed it again at some point yesterday. After that, I might have only used the headless mode (needed to get things cut). That is weird though because it does still flash messages on the TFT even though it is headless, and no errors.
So now what the heck do we submit to BTT? I will post a issue and see if Kisslorand jumps on it.
1 Like
We’re a little spread out now. But the suggestion to add it to the known echo would be a solid solution.
Alternatively, the section where it sends M420 in G28 could be gated on the bed level enabled flag.
I have no clue how long it will BTT take to fix the issue.
In the meantime our CNC users will download the new firmware and may raise questions here about the M420 message.
So I would propose to either fall back to the previous release or to apply the ‘knownEcho-fix’ (after some testing). Both until BTT have solved the issue.
2 Likes
BTT was pretty good about merging and closing the previous PR (with some nudging from Ryan). If someone makes the PR there, Ryan can encourage them to fix it.
1 Like
It is there, but Kisslorand added some other edits to it so it could take a while. Last time the edit we needed was also packaged in with a bunch of other edits and they asked for one issue per PR, looks like more outstanding PR’s are packages instead of one at a time.
1 Like
I‘ve seen the backlog of PRs on Github. However, it is save to apply the fix to your sources if you don‘t want to wait until the PR has been merged
1 Like
I’ll give it unit Monday Evening. It is an annoying error but not critical.
1 Like
The PR has just been merged!
2 Likes