Lpc-tmc22xx. Please add support for TMC2209 sensorless homing and stall detection. Also add TMC2209 option to LPC configuration tool. #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 30 commits
July 25, 2018 21:22
* Added config for MKS Sbase and AZSMZ * Updated configs to use TimerPWM where needed * Added Boost Preprocessor library to generate tables for TimerPWM and External Interrupts
# Conflicts: # src/RepRapFirmware.h # src/Tasks.cpp
# Conflicts: # src/Tasks.cpp
This adds support for TMC22XX drivers when using LPC based systems. It uses the LPC Repetitive Interrupt Timer (RIT) to drive a custom software UART implemetation. This allows the use of standard GPIO pins to talk to UART based TMC devices. A single pin is used per device and the UART operates in half duplex mode. To minimise system impact the UART operates at a slow speed (9600 baud) and uses a single interrupt per bit. When the UART is not operating the timer is disabled. The interrupt handler takes approximately 1uS to execute on an LPC1768 (plus standard interrupt overhead). Potential issues When enabled all active drivers must be TMC22XX devices. The software UART is sensitive to timing issues. If other parts of the system delay the RIT interrupt handler then errors will occur. To improve detection of these errors full CRC checking of responses has been enabled. Currently no errors are seen when the system is idle, but during test print jobs an error rate of 0.5% is seen. If there is an error the operation will be retried. Currently RepRap firmware polls the drivers constantly to obtain status information. So far when testing no error has created a false status report. But this is possible if errors are not detected by the CRC code. It may make sense to change things so that this polling is optional (can probably be done using the current M569 R option), the UART interface would then in effect only be used for configuration.
|
Hi I'm going to close this pull request (as it does not contain any code), if you would like to discus feature requests etc. it is probably best to do that over on the RepRap forum thread. I'd be happy to discus further over there. |
|
OK, understood. I was not really sure the best way to request a feature.Thanks for all of your work on this so far.Cheers - BillT
On Tuesday, May 5, 2020, 04:13:47 PM EDT, Andy Shaw <notifications@github.com> wrote:
Hi I'm going to close this pull request (as it does not contain any code), if you would like to discus feature requests etc. it is probably best to do that over on the RepRap forum thread. I'd be happy to discus further over there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorry, I am unable to help with the code. I do have an SKR V1.3 and TMC2209 drivers and would be glad to test/confirm updates.
Thanks! Bill Trondsen