You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During actual flight, the drone cannot take off, regardless of whether the motors are connected to M1-M4 or M5-M8. After troubleshooting, it was found that the issue was caused by setting the M8 motor pin to PD15. I tried the methods suggested at #10900 and #10835, adding #define USE_DSHOT_DMAR, but this did not work. When I changed PD15 to, for example: DEF_TIM(TIM3, CH3, PB0, TIM_USE_OUTPUT_AUTO, 0, 7), // S8
Although motor M8 could not work in this case, the drone was able to take off normally when connected to M1-M4. I also encountered this problem on another H743 flight control board, where the PD15 pin is also used for M8.
I am wondering whether using #define USE_DSHOT_DMAR can really solve this problem, and whether anyone has encountered the same problem as me.
You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:
maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.
maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x
If master is the correct target for this change, no action is needed.
This is an automated suggestion to help route contributions to the appropriate branch.
1 targets built. Find your board's .hex file by name on that page (e.g. MATEKF405SE.hex). Files are individually downloadable — no GitHub login required.
Development build for testing only. Use Full Chip Erase when flashing.
This file contains hidden or 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
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.
User description
Added ZEX_ATHENA_STD_PRO board.
Hardware Verification
Problem Description
During actual flight, the drone cannot take off, regardless of whether the motors are connected to M1-M4 or M5-M8. After troubleshooting, it was found that the issue was caused by setting the M8 motor pin to PD15. I tried the methods suggested at #10900 and #10835, adding
#define USE_DSHOT_DMAR, but this did not work. When I changedPD15to, for example:DEF_TIM(TIM3, CH3, PB0, TIM_USE_OUTPUT_AUTO, 0, 7), // S8Although motor M8 could not work in this case, the drone was able to take off normally when connected to M1-M4. I also encountered this problem on another H743 flight control board, where the PD15 pin is also used for M8.
I am wondering whether using
#define USE_DSHOT_DMARcan really solve this problem, and whether anyone has encountered the same problem as me.