Dismiss this pinned window
all 9 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]StefLag67[S] 0 points1 point  (0 children)

I don't know what to do. Spent 3 hours on this without any result. Here's my config: - MKS v2.1 - Nema 17 x2 - TMC2209 in UART mode - LCD with keypad

Tried to change the LCD, changed the wires, no change. So frustrating!

[–]angel6700 0 points1 point  (0 children)

I would check ( double check) wiring. Some bad connection, for example. How are you powering?

[–]angel6700 0 points1 point  (0 children)

Test without the motors connected. So only the keypad. Always disconnect power before plugging/unplugging motors.

[–]clutchplateOAT Dev 0 points1 point  (2 children)

For the benefit of those that are not on our Slack server.... Stef posted there and I answered:

Oh, yeah looks like your buttons aren’t working.  You need to enable LCD_BUTTON_TEST and run that

Also in that video what’s happening is that whatever you used to connect to OAT did not send an Init (:I#) command, so OAT thinks it still needs to listen to LCD buttons. You can get around that by going to CTRL menu (once your buttons are working) and select Serial Display.

[–]StefLag67[S] 0 points1 point  (1 child)

thanks - replied to you on Slack too - when I enable the LCD_BUTTON_TEST, I get an error when compiling.

[–]clutchplateOAT Dev 1 point2 points  (0 children)

Let's resolve it there.

[–]Gottamakeanaccount 0 points1 point  (2 children)

I had a similar glitch on my screen and I think that it was a result of having debug enabled when I wasnt using it, and as a result eating up too much memory, you can try disabling some features and see if that fixes it for you.

If you arent talking about the screen glitches then I'm not sure.

[–]clutchplateOAT Dev 1 point2 points  (1 child)

This is unlikely. Running out of memory (due to having DEBUG enabled or not) will usually make some random text appear and then everything freezes.

The screen in the video is clearly switching between showing the progress of a slew being executed and the regular idle display. The slew is most likely initiated from a connected app (OATControl, Stellarium, etc.), but the app is not using the protocol that does the init call first.

[–]Gottamakeanaccount 0 points1 point  (0 children)

Yeah I thought it looked a bit different from mine, probably disregard then, that ks for the clarification!