search

iNavFlight / inav

INAV: Navigation-enabled flight control software
https://inavflight.github.io
GNU General Public License v3.0
3.12k stars 1.47k forks source link

F405-Wing can't talk to any GPS's #3618

Closed Hyperious closed 6 years ago

Hyperious commented 6 years ago

Board and Version

Matek F405-wing INAV/MATEKF405SE 2.0.0 Jul 12 2018 / 11:30:25 (81ce75745)

Behavior

No GPS's work, on any UARTs. I've tried 3 different known-working Neo-M8N's on all the UART's, and none of them talk to the FC. I've made sure the ports tab is set correctly, and that wiring is correct for all of them. the GPS tab shows no packets sent or received either.

Any idea what's wrong?

Blackbox logs/Config (.ZIP) where problem occurs

current dump: CLI-Dump.txt

lichtl commented 6 years ago

Did you connected lipo to the FC? Some of the 5V rails only provide power when Lipo is connected

Hyperious commented 6 years ago

yup, tried both USB power only, and power from a Lipo. I've even hooked all the tested GPS units to a known-working 5v BEC. Still no dice

NNygren commented 6 years ago

I'm seeing the same thing. Using a MatekF405-mini board. iNav 1.9.1 picked up the GPS just fine and worked in 2 RC1, but I can't get get the GPS to be recognized in iNav 2 RC4.

Hyperious commented 6 years ago

I'm sure the software and hardware are the same between the two boards for gps processing, so it doesn't surprise me that other F405-X boards would be having the same problem. Shame though as I need to run 2rc4 since I've been having random disarms with 1.9.1.

I'll try jumping back to 2RC1 and will see if it talks to the gps, but at this point I think it's either batch hardware related, or there's an issue in inav's specific F405 release.

giacomo892 commented 6 years ago

I'm using MATEKF405SE and GPS is working fine on latest development. Must be an issue with your GPS hardware/configuration.

ghost commented 6 years ago

That's weird.

I am using a self compiled version of RC4 on a MATEK F405-WING (QUAD platform) and GPS is working perfectly. I have modified the code to put the motor outputs on S3 - S7 and an external baro on the I2C2 bus, but doubt if that would affect the GPS in any way.

Cosmic rays?

ghost commented 6 years ago

Sorry, can't count at this time in the morning. Motors on S3-S6.

Hyperious commented 6 years ago

I got in contact with Matek about it. While they didn't say it directly, I think they had a bad batch of F405-X's. The support member mentioned that a few other owners were experiencing the same issue, and that they'd warranty replace it for me. Hopefully that solves it once and for all.

akhanhk commented 6 years ago

@giacomo892 sorry for opening up an old thread, can you verify your FW version and the configurator version..

Target : F405SE I am using config 2.0 rc2 and f/w 1.9.1 - GPS works, no mixer switch to Config 2.0 rc2 and FW 2.0 rc4 - No GPS, yes mixer.. lol

giacomo892 commented 6 years ago

1.9.1 doesn't have custom mixer as 2.0.0 :) GPS works for me on 2.0rc3 configurator and 2.0.rc4 firmware

solmag commented 6 years ago

Hello, I just finished building a plane and everything works except the GPS. I'm using the Matek F405-WING. Is there a solution to this problem? I have tried 5 different GPS modules and none of them works with the F405 Wing FC, but they work on other FC. Does anyone know how to fix this issue? I am using Inav 2.0 stable firmware.

Hyperious commented 6 years ago

I heard they made a batch where the RX and TX pins were actually switched on accident. When I RMAed mine, that's probably why it was having problems.

Try switching your uart TX and RX pins to see if that works

solmag commented 6 years ago

I will try that. Thanks for the information.

Sent from my iPhone

On Aug 31, 2018, at 4:37 AM, Hyperious notifications@github.com wrote:

I heard they made a batch for the RX and TX pins were actually switched on accident. When I RMAed mine, that's probably why it was having problems.

Try switching your uart TX and RX pins to see if that works

On Fri, Aug 31, 2018, 12:02 AM solmag notifications@github.com wrote:

Hello, I just finished building a plane and everything works except the GPS. I'm using the Matek F405-WING. Is there a solution to this problem? I have tried 5 different GPS modules and none of them works with the F405 Wing FC, but they work on other FC. Does anyone know how to fix this issue? I am using Inav 2.0 stable firmware.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/3618#issuecomment-417572014, or mute the thread https://github.com/notifications/unsubscribe-auth/AmOUWZ0mz97CGXwCLLXKsWiJYQXdBmcvks5uWN9-gaJpZM4VTwZK .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

geoavia commented 6 years ago

Same problem here :( FC: Matek F405-Wing (ordered from getFPV) GPS: Holybro Micro M8N GPS Module (also ordered from getFPV) Configuator: 2.0.0 Firmware: MATEKF405SE 2.0.0

@Hyperious: swapping TX/RX does not work for me. But I kew it wont work, cause gpspassthrough command worked fine, uCenter conects get GPS lock, so GPS itself works perfectly well. So the pinout was correct in my case.

Just can't get GPS working in iNav, therefore compass recognized and working.

solmag commented 6 years ago

I was able to solve mine by swapping the UART. I contacted Matek and I was asked to change the UART and after I did it, it started working.

solmag commented 6 years ago

I was able to solve mine by swapping the UART. I contacted Matek and I was asked to change the UART and after I did it, it started working.

Sent from my iPhone

On Sep 28, 2018, at 7:20 AM, geoavia notifications@github.com wrote:

Same problem here :( FC: Matek F405-Wing (ordered from getFPV) GPS: Holybro Micro M8N GPS Module (also ordered from getFPV) Configuator: 2.0.0 Firmware: MATEKF405SE 2.0.0

@Hyperious: swapping TX/RX does not work for me. But I kew it wont work couse gpspassthrough command worked fine, uCenter conects get GPS lock, so GPS itself works perfectly well.

Just can't get GPS working in iNav, therefore compass recognized and working.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

geoavia commented 6 years ago

@solmag can you point me on which uart it worked? I have currently using uart 4, tend to try on 6 - cause it's just aside. . . . PROBLEM SOLVED! UART6 worked, Thank you @solmag!

Nice to have such a responsive community ;)

antidotez commented 5 years ago

I have the same problem on matek f405-wing and bn220 gps. Latest working version of inav is 2.0.1. I tried different ports, different baudrates, but no changes on inav >2.0.1.

geoavia commented 5 years ago

@antidotez did ypu check if it (GPS) works in uCenter, u must have gpspassthrough enabled though.

P.S. I have BN220 working fine but on different wing and FC (Matek F411Wing)

antidotez commented 5 years ago

Sorry, i forgot to say about it. Yes, it work through "gpspassthrough". After version 2.0.1 there were changes in the gps code, maybe this affected? Maybe gps module settings are not correct? Can you send me your bn220 settings?

geoavia commented 5 years ago

@antidotez sorry for delay... was out of reach of the wing. Forget that I replaced BN220 with Matek SAM-M8Q GPS module on that wing (no particular reason thogh). But, to be sure, today repinned (thanks to the fact that connector is same) and reconnected BN220 again for you as it worked before :)

as for settings (nothing special):

pix for reference (NMEA, 9600bps ) https://pasteboard.co/IxP6556.jpg (both leds were flashing) https://pasteboard.co/IxP6zNF.jpg

I'll post inav cli dump/diff if you wish later.