Hello all,
First of all, I apologize if this isn't the right place to post about this issue; I'm new to these forums.
I'm using a Melzi 2.0 board from TRONXY on a Prusa i3 clone (Monoprice Maker Select v2). The firmware is just Marlin 2.0.x configured to my printer, where I have "ZONESTAR_LCD" selected as the character LCD.
The problem I'm experiencing is with my 2004 keypad LCD (aka Zonestar LCD, Anet, etc.), the kind with 5 analog buttons. The screen lights up and displays characters/changes the screen when I push buttons, but the only characters it displays are question marks, left arrows, black rectangles, and the occasional Japanese character.
What I think the problem is is something to do with how Marlin sends characters to my LCD.
I am 98% certain I have the pin configurations correct, which are as follows, as written in pins_MELZI_TRONXY.h:
What I think I've ruled out so far is the pin configuration. The screen displays "some characters", and it changes during boot and when buttons are pushed. I've also tested my exact setup with basic Arduino sketch using the liquidcrystal library, which seems to be what Marlin uses as well. I can post the sketch if you think that might help, but it really is just a generic liquidcrystal test sketch with the pin configuration above. One bit of behavior I don't really understand is that the M117 GCode command doesn't seem to do anything, even though the printer responds to most other GCode fine.
I don't think the keypad pin (ADC_KEYPAD_PIN) has anything to do with this problem, since it responds to button presses. I personally haven't set it to anything, but it appears that Marlin sets it to 1 (that is, analog pin A1) somewhere, which is what I was going to do anyway.
What all of this indicates to me is that the problem is somewhere within Marlin itself, since I've been able to confirm that almost everything else about this works independently.
If anyone has any advice or can point me in the right direction, that would be hugely appreciated!!
First of all, I apologize if this isn't the right place to post about this issue; I'm new to these forums.
I'm using a Melzi 2.0 board from TRONXY on a Prusa i3 clone (Monoprice Maker Select v2). The firmware is just Marlin 2.0.x configured to my printer, where I have "ZONESTAR_LCD" selected as the character LCD.
The problem I'm experiencing is with my 2004 keypad LCD (aka Zonestar LCD, Anet, etc.), the kind with 5 analog buttons. The screen lights up and displays characters/changes the screen when I push buttons, but the only characters it displays are question marks, left arrows, black rectangles, and the occasional Japanese character.
What I think the problem is is something to do with how Marlin sends characters to my LCD.
I am 98% certain I have the pin configurations correct, which are as follows, as written in pins_MELZI_TRONXY.h:
#define LCD_PINS_RS 28 //RS 28 #define LCD_PINS_ENABLE 29 //EN 29 #define LCD_PINS_D4 10 //D4 -> RX1 -> 10 //new settings #define LCD_PINS_D5 11 //D5 -> TX1 -> 11 //these pins have been CONFIRMED to work via an Arduino sketch with liquidcrystal.h #define LCD_PINS_D6 16 //D6 -> SCL -> 16 #define LCD_PINS_D7 17 //D7 -> SDA -> 17
What I think I've ruled out so far is the pin configuration. The screen displays "some characters", and it changes during boot and when buttons are pushed. I've also tested my exact setup with basic Arduino sketch using the liquidcrystal library, which seems to be what Marlin uses as well. I can post the sketch if you think that might help, but it really is just a generic liquidcrystal test sketch with the pin configuration above. One bit of behavior I don't really understand is that the M117 GCode command doesn't seem to do anything, even though the printer responds to most other GCode fine.
I don't think the keypad pin (ADC_KEYPAD_PIN) has anything to do with this problem, since it responds to button presses. I personally haven't set it to anything, but it appears that Marlin sets it to 1 (that is, analog pin A1) somewhere, which is what I was going to do anyway.
What all of this indicates to me is that the problem is somewhere within Marlin itself, since I've been able to confirm that almost everything else about this works independently.
If anyone has any advice or can point me in the right direction, that would be hugely appreciated!!