September 23, 2019 at 8:15 am #115108
Need some help troubleshooting if I have a shitty board.
Attached a pic of what the screen looks like during use.
As far as my build goes, I’m super satisfied: printed the parts, bought the kit from V1, built a nice little bed, everything is wired and initial tests show me it’s working great… however, this faulty display issue makes the machine hard to manage and move on to carving stuff up!
Side note: when I bought my Lowrider kit, I accidentally had two of these LCD monitors in my cart. Ended up coming in handy though since I have used both screens to test and verify they both display weird, leading me to think it’s my board. I used the pre-configured firmware as recommended.
Thanks in advance to anyone willing to chime in and take the time to help a brother out!
Attachments:September 23, 2019 at 8:25 am #115111
Is the language set to klingon?
I’ve seen this before, but I can’t remember when… Maybe on my melzi board from a few years ago…
I’m assuming you flashed the board yourself, with your firmware? If the controller’s firmware was really messed up, it could be having an effect like this, but the processor on that board is the same as on any ramps or rambo.
Maybe it’s noise affecting the serial lines from the controller to the lcd?
I can’t see a good way this could be caused by the hardware of your controller board unless there was a missing component meant to reduce noise on those lines.September 23, 2019 at 8:27 am #115112
I just watched the video, clearly it’s got Ryan’s firmware on it. And it definitely looks like noise to me.September 23, 2019 at 8:45 am #115113
TimParticipantSeptember 23, 2019 at 8:54 am #115115
Assuming pixels are loade line-by-line and left to right it looks like the clock line for the display is picking up extra transitions from noise which is shifting portions of the lines to the right. Could be as simple as a missing pull-up/down resistor on the CLK pin, but more data would be needed.
You have an oscilloscope laying around by any chance?September 23, 2019 at 1:04 pm #115142
I had this issue with a bad LCD cable. Replaced the cables and the problem went away.
You must be logged in to reply to this topic.