-
Notifications
You must be signed in to change notification settings - Fork 320
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
MATEK F405 v1 #2141
Comments
You wrote "my rx is wired to UART4". |
Hello,
It may be connected to UART 4. The writing on the board is very small. Assuming it's connected to UART 2, it's still not recognizing the RX. Any suggestions?
…________________________________
From: Sensei ***@***.***>
Sent: Sunday, July 7, 2024 11:11 PM
To: iNavFlight/inav-configurator ***@***.***>
Cc: MBR595 ***@***.***>; Author ***@***.***>
Subject: Re: [iNavFlight/inav-configurator] MATEK F405 v1 (Issue #2141)
You wrote "my rx is wired to UART4".
Your screenshot shows it's configured for rx on UART2.
—
Reply to this email directly, view it on GitHub<#2141 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEMX4UWZ45Q25PSW3LDZNSDZLH7OXAVCNFSM6AAAAABKPV4D46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJSHEYDAMBWGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
In your shoes, the first thing I would do is use some good lighting and take a close-up picture with my phone. Then zoom in on that pic to a) verify which user it is on and b) check for any stray wire strands, solder whiskers, etc. If it's not connected to the same uart that is configured, that would be the problem. So I would start there. |
Good Afternoon,
I inspected the board again. The RX is plugged in to UART4 and the GPS is plugged into UART 2. What should I do?
…________________________________
From: Sensei ***@***.***>
Sent: Monday, July 8, 2024 1:30 PM
To: iNavFlight/inav-configurator ***@***.***>
Cc: MBR595 ***@***.***>; Author ***@***.***>
Subject: Re: [iNavFlight/inav-configurator] MATEK F405 v1 (Issue #2141)
In your shoes, the first thing I would do is use some good lighting and take a close-up picture with my phone. Then zoom in on that pic to a) verify which user it is on and b) check for any stray wire strands, solder whiskers, etc.
If it's not connected to the same uart that is configured, that would be the problem. So I would start there.
—
Reply to this email directly, view it on GitHub<#2141 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEMX4UQAFSLEIJGIFHLYXFTZLLECZAVCNFSM6AAAAABKPV4D46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJUG44DEMZUGI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hello,
I recently changed controllers. Currently using a FRSKY TARANIS X-LITE PRO with the TBS module and receiver. I'm using a Matke F405 V1 board and INAV Configurator 7.1.1. FW is 7.1.0 MATEKF450SE. My RX is wired to UART4 but it's not being recognized in the configurator when I turn it on, save and reboot. Any advice you can offer is greatly appreciated.
The text was updated successfully, but these errors were encountered: