-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
MRO Control Zero F7 enable UART7 #16605
Conversation
USART6 is not working correctly so enabling UART7 as TEL3 makes sense while disabling Console on the port.
The objective was to disable the Console (as UART7 is needed due to USART6 not available/working) but by omitting the Console line completely it stops the Control Zero from booting. Moving this to UART8 (which is Frsky Telemetry and likely used sparsely makes the most sense). Tested and works.
@ryanjAA did you test fly this? if so can you please post a flight log? I will make sure we get this in ASAP before the v1.12 release which we are getting ready to cut. |
I haven’t flown this one yet since there is an H7 (processor) and H7 oem variant we’re working on as well. We’ll get them all test flown and logs updated the same day. Just waiting on getting the h7 units operational. @dagar wanted to change a few things that were added to master and with that and once the H7 stuff is finalized I’ll get it uploaded. Hopefully before 1.12 is cut. |
Thanks for the update I'll keep a close eye on this one @ryanjAA |
Sorry @mrpollo this specific Pr I’ve flown and have logs. Let me track them down. I thought this was the pr on bringing up the the f7 oem board (responding from my phone in our strange Texas snow storm). |
@ryanjAA were you able to find the test logs? |
https://review.px4.io/plot_app?log=8ab2f628-da88-4760-8bbb-dedf448c50c1 Changes would have been on top of a6274bc5 |
@dagar what do you think? we good to go? |
From a continuity standpoint the other MRO Ctrl Zero boards implemented I did the UART mapping the same as this PR so this will be the one board different from the other 3 until this is merged in. |
Why is this one different? |
It's not that it is different per se, it's that the use case of serial ports makes more sense to have them this way so when doing the other boards, that's the way I routed them so this is the only one that is different since I didn't do the original board config. |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
I believe this is no longer relevant? |
F7 EOL so yes, not relevant. |
UART7 is currently set to Console but as USART6 is not available/working, this makes sense to enable as a serial port (Telemetry 3). I tried setting it as GPS 2 but for some reason that would not work. It would not enable when selecting gps 2 port for a mavlink instance in qgc.
Even if USART6 was working, setting UART7 to an available port makes sense on this board.
Console was moved to UART8 which is Frsky Telemetry, that is likely not used very much.
The objective was to disable the Console completely but by doing so the autopilot would not boot up.
Tested and works correctly.