[BUG] RADDS v1.5 LCD 2004 Initialization problem #18132
Comments
ShadowOfTheDamn
changed the title
|
Is anyone else able to reproduce this issue? |
|
Lack of Activity |
|
please open it again: |
|
today I check the new bugfix and the problem is still there. |
|
Please test the Also enable |
|
Thank you Scott, Used the latest Bugfix two days ago but unfortunately it wasn't fixed. Used M43 and all the pins were ok.
|
|
Hi @ShadowOfTheDamn. A change was merged a few days ago which fixed startup delays for some LCD screens. I do not know whether or not it impacts the character LCD you are using. Please test the bugfix-2.0.x branch to see where it stands. If the problem has been resolved then we can close this issue. If the issue isn't resolved yet, then we should investigate further. |
|
I tried the latest bugfix. the issue is still there with my character LCD. |
|
This issue has had no activity in the last 30 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 7 days. |
|
The issue is still there with todays bugfix, don't close the issue |
|
Stale Bot gives you a week to comment on the issue before it's closed after 30 days of inactivity, so please confirm that it's not resolved before then. |
|
This issue has had no activity in the last 30 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 7 days. |
|
I think this might be related to the issue i reported some time ago: #13555 I think if you check some unused pins with a volt meter before pressing the reset or connecting via usb, you will find that the pins are high (3.3v) indicating that marlin has not booted yet. I spent a long time not using my radds controller (or the printer it belongs to) and got back to troubleshooting it today. I'm using a home-made cable strictly following the schematic of the radds2lcd board, including the 1k resistors. I hadn't noticed before that the emergency stop (kill) button on the RRD full graphic is now a reset button. You didn't say whether you're using a radds2lcd board or used your own cable. I should note that the radds2lcd schematic leaves the "kill" wire floating since it has no obvious corresponding pin on the original radds lcd. So i am wondering if this is a hardware problem or what. Today i converted to a fysetc mini 12864 v1.2 (no rgb led) and it behaves exactly the same way. I'm using the same cable, just added another section to my pins file. |
|
I use a custom PCB. I will send the schematics. |
|
Followup to my previous comments. While digging around for clues with google i came across a post on the repetier forums about the same issue, where one of the repetier devs stated that it's usually a problem of a "wrong size capacitor" or something on clone Arduino DUE boards that doesn't seem to occur on the genuino made-in-italy boards. Something about the clone boards booting too quickly after initial power-up and then immediately crashing. So i acquired a genuine DUE. I no longer have to reset my RADDS to get it to boot up properly. Glancing at the boards, the clone board from china has some open pads that contain components on the genuino board.
|
|
I dont understand when I did not changed my HW what this could do with my issue. You mean the hardware become faulty? |
|
Adding info, the place you are showing is a place for freq generator not a cap. also the original board is completely different with clones. that is not relevant as I said before. with an original board the results are the same. |
|
RESONATOR_EPSON_FC_145 |
|
https://forum.arduino.cc/index.php?topic=256771.msg2512504#msg2512504 |
|
Very interesting. My chinese clone Due seems to be the earlier design. I Wonder what effect the missing crystal has. The other Due derivative i have here is a Udoo Quad and so far i haven't done anything with it except try to figure out which build of armbian has working network drivers for it. |
|
So has this turned out to be an issue with some DUE boards missing parts, and not an issue inside Marlin? |
|
nope, the issue is due to some ******** bootloader developers of DUE decided to change the bootloader globally regardless of their faulty HW and without considering any difference between the new and old HW revisions. And when you uploaded the marlin firmware the new bootloader is also flashed at that time hence the story you know. |
|
Added the SMD 0603 10Kohm resistor and now the system boots correctly in the first time you turn the machine on. no reboot required. |
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Bug Description
Dear experts
When the printer is turned on the 2004 LCD (rep-rap smart controller) seems to be late to initialize and draws 2 lines of blocks, but if you reset the printer it will initialize and every thing works ok.
My Configurations
Configuration.zip
Steps to Reproduce
Just turn on the printer.
If you reset the printer with the reset switch the screen will initialize.
but if you turn off the printer and turn it on again it wont help.
Expected behavior: I expect the LCD work correctly in the first boot.
Actual behavior: The printer need a reset so the LCD could get to work.
Additional Information
A video of the screen is provided:
Video.zip
Edit (23/06/2020) :
1-checked all the wiring and connectivity
2-checked cable length (20cm, 30cm, 60cm, 1m)
3-double checked the pin numbering in marlin
the issue is not solved.
I thought it is clear in the video that the LCD initialization lag behind the system.
If the motherboard lose power I need to reset to see the LCD but if I switch off the system for as short period of time, just before it lose the power completely (when LEDs are fading on the MB) I power on the system the LCD initialize. so this seems connected on how things get powered on and initialized (i Think). It is noteworthy again to add I didn't have the problem while using an older version of marlin before and got stock with this after upgrading, unfortunately does not have my old configuration nor the source so I cannot revert)
The text was updated successfully, but these errors were encountered: