-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Add new target ORBITF435 #10578
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
Add new target ORBITF435 #10578
Conversation
|
Hello @orbittechnologyx, please have a look at https://github.com/iNavFlight/inav/blob/master/docs/policies/NEW_HARDWARE_POLICY.md Your PR is a great first step, but we also need samples to validate it works as expected. Please reach out to me over on INAV's Discord and I can help organize the process. |
|
Test results:
|
|
Almost everything tested seems to be working well. UART 4 does not seem to be working correctly, in my testing. It appears that the pad labeled TX4 is actually RX4. |
|
Probing with a meter confirms the pad labeled TX4 is connected to PH2, UART4_RX. |
|
Thank you very much for these tests. Unfortunately, we typed the R4 and T4 labels incorrectly. For this series, for now, we will make a note that R4 should be T4 instead of R4 and T4 should be R4, and if possible, we will even try to make corrections directly on the board. |
…ITF435 Add new target ORBITF435
Hello,
This target is already supported in official Betaflight firmware (Betaflight Wiki) . Also I want to add in official Inav firmware. Could you please review the configuration?
Here is the specs: