Skip to content
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

iomcu reset with bdshot on 6X #27171

Closed
tridge opened this issue May 27, 2024 · 1 comment · Fixed by #27201
Closed

iomcu reset with bdshot on 6X #27171

tridge opened this issue May 27, 2024 · 1 comment · Fixed by #27201
Assignees
Labels

Comments

@tridge
Copy link
Contributor

tridge commented May 27, 2024

With a CUAV 6X with Pixhawk6X-bdshot firmware, with 6 blheli32 ESCs connected on a hexacopter (4 ESCs on main, 2 on aux) I get a reproducible internal error 0x1000 for IOMCU reset after arming. The copter still flies fine, but we need to find the cause of this.
Logs here:
https://drive.google.com/drive/folders/1fveumuzs7zw7zCqw7jKLHqiaXxx3k5nC?usp=drive_link
ping @andyp1per

@burgeruser
Copy link
Contributor

burgeruser commented May 27, 2024

I encountered a similar issue earlier, and my solution was either to exclusively use D-shot outputs from the IOMCU or have the MAINMCU handle all D-shot outputs. I frequently ran into error code 0x1000 back then.

The interface resources tested for Ardupilot hardware controllers – 16 D-SHOT ports, and 2 CAN buses – are ample to cater to consumer-grade drones, vehicles, boats, and even underwater vehicles. If ever faced with insufficient connectivity, expansion would likely rely on CAN interfaces as a modular solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 4.5.5-beta1
Development

Successfully merging a pull request may close this issue.

3 participants