-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mks-Robin TFT LCD V1.0 ILI9328 Support. Is it possible? #15871
Conversation
[1.1.x] Extra insurance against endstop false positives
Fix message to long for 12864 display
The registers within the Max7219 can get corrupted a number of ways. This allows the Max7219 to be reset and fully initialized. And... it also allows the user to see the initialization pattern.
According to #9917 (comment)
* Fix planner/stepper race condition Co-Authored-By: ejtagle <[email protected]> Co-Authored-By: AnHardt <[email protected]> * Fix stepper pulse timing Co-Authored-By: ejtagle <[email protected]>
Fixed for cycle used to initialize default values
Co-Authored-By: gloomyandy <[email protected]>
Co-Authored-By: ejtagle <[email protected]>
Co-Authored-By: ejtagle <[email protected]>
- Allow planner to alter the deceleration phase of the currently executing block. - Remove BUSY flag, as it is NON ATOMIC to set bits in the Stepper ISR and Planner at the same time. Co-Authored-By: ejtagle <[email protected]>
To allow for the case where a Z endstop (e.g., hall effect) is higher than the probe trigger point, don't check the Z min endstop during probe moves. See #11134
V3 of the BLTouch has an [Alarm Release & Touch mode](https://docs.wixstatic.com/ugd/f5a1c8_77037f55e5d542309d9fc178165c9f3f.pdf) to activate after the probe is deployed. If this mode isn't activated, the BLTouch keeps deploying, ends up detecting a collision and gets itself in error mode. Tested on a Creality Ender-3.
Counterpart to #13595 Co-Authored-By: swilkens <[email protected]>
Co-Authored-By: InsanityAutomation <[email protected]>
see PR #14857 for details
This reverts commit 73f4027.
Co-Authored-By: thisiskeithb <[email protected]>
Make the configs zip file requirement more prominent
|
Unless I’m doing something wrong. Or the board v2.1 is a bit different ( don’t have the pin out from MKS) Thank you all again!!! |
Please close this PR... tx The FSMC connector to drive the LCD is the same for all boards |
Closing PR as requested. In this case will I need to open bug report to report, right? |
https://drive.google.com/file/d/19zjFjk2XoG93TN7go9lv5q_XIunrDD6u/view?usp=sharing I know its the v2.4 but the FSMC pins are dedicated on the STM chip... and its a 9328... not 9238 |
You are right! No, mine does not work yet. :-( |
re-open my request. would it be possible to add codings for the ILI9328 TFT controller? really thank you for your time.... |
You might be able to do what you want. But before we can review your PR you will need to start over and try again. Be sure to start with an up-to-date See http://marlinfw.org/docs/development/getting_started_pull_requests.html for full instructions. |
Understood SCOTT.
Thank you very much.
Will do it again.
The last download was Nov 11 2019
Will re download it tonight.
…On Tue, Nov 12, 2019 at 20:26 Scott Lahteine ***@***.***> wrote:
You might be able to do what you want. But before we can review your PR
you will need to start over and try again. Be sure to start with an
up-to-date bugfix-2.0.x before making your changes, and be sure to target
bugfix-2.0.x when creating your PR.
See
http://marlinfw.org/docs/development/getting_started_pull_requests.html
for full instructions.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#15871?email_source=notifications&email_token=AFYWWXIJJMQRR722JGVYV4TQTNXXXA5CNFSM4JLQZGMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED4X55Y#issuecomment-553221879>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFYWWXNLY3R2ZZZIB3SLUSDQTNXXXANCNFSM4JLQZGMA>
.
|
Just wanted to cross post the solution provided by Jmz52 in the below post. |
(Sorry, not sure why the pull request is saying merge request...If not correspond, Pls delete or close)
Description
The Marlin bugfix - 2.0 contain 2 supported TFT LCD ILI9413 and st7789v.
it is noted in the comment section that the ILI9328 is not supported.
Would it be possible to support the ILI9328?
In the early stage of the development, jmz52's branch had these two ILI9328 and st7789v supported and the coded for.
after the merge, not sure why the ILI9328 was left out and not been supported.
Benefits
It would enable owners of such STM32's Mian board combo kit to be able to use Marlin 2.
Related Issues
here is jmz52's repository of his code. tested o my MksRobin V2.1 TFT 1.0 and it works.
When using the nowadays' (Nov-10-19) it will compile correctly but I get "booting" on the screen.
I'm able to connect via ponterface and access eeprom's data by M503.
I'm not a programmer, so I'm not able to write codes.
hopping the team could help me out if possible and time allow.
Thanks
https://github.com/jmz52/Marlin/tree/MKS-Robin-Touch-POC
partial code from : Marlin\src\lcd\dogm\u8g_dev_tft_320x240_upscale_from_128x64.cpp
static const uint16_t ili9328_init[] = {
ESC_REG(0x0001), 0x0100,
ESC_REG(0x0002), 0x0400,
ESC_REG(0x0003), 0x1038,
ESC_REG(0x0004), 0x0000,
ESC_REG(0x0008), 0x0202,
ESC_REG(0x0009), 0x0000,
ESC_REG(0x000A), 0x0000,
ESC_REG(0x000C), 0x0000,
ESC_REG(0x000D), 0x0000,
ESC_REG(0x000F), 0x0000,
ESC_REG(0x0010), 0x0000,
ESC_REG(0x0011), 0x0007,
ESC_REG(0x0012), 0x0000,
ESC_REG(0x0013), 0x0000,
ESC_REG(0x0007), 0x0001,
ESC_DELAY(200),
ESC_REG(0x0010), 0x1690,
ESC_REG(0x0011), 0x0227,
ESC_DELAY(50),
ESC_REG(0x0012), 0x008C,
ESC_DELAY(50),
ESC_REG(0x0013), 0x1500,
ESC_REG(0x0029), 0x0004,
ESC_REG(0x002B), 0x000D,
ESC_DELAY(50),
ESC_REG(0x0050), 0x0000,
ESC_REG(0x0051), 0x00EF,
ESC_REG(0x0052), 0x0000,
ESC_REG(0x0053), 0x013F,
ESC_REG(0x0020), 0x0000,
ESC_REG(0x0021), 0x0000,
ESC_REG(0x0060), 0x2700,
ESC_REG(0x0061), 0x0001,
ESC_REG(0x006A), 0x0000,
ESC_REG(0x0080), 0x0000,
ESC_REG(0x0081), 0x0000,
ESC_REG(0x0082), 0x0000,
ESC_REG(0x0083), 0x0000,
ESC_REG(0x0084), 0x0000,
ESC_REG(0x0085), 0x0000,
ESC_REG(0x0090), 0x0010,
ESC_REG(0x0092), 0x0600,
ESC_REG(0x0007), 0x0133,
ESC_REG(0x0022),
ESC_END