Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Betaflight won't detect BN 220 GPS
#1
Hello, I have recently hooked up a BN220 GPS module to my JB F4 flight controller.  I am using UART 4 for connect the TX and RX.  I have made sure to connect GPS RX -> Flight Controller TX and GPS TX -> Flight Controller RX.  When my lipo battery is plugged in the GPS light is solid blue (I believe it's supposed to flash red when it is receiving data from the Flight Controller, but it's not doing that.  I've followed everything in this article but I don't get the GPS icon on top of betaflight to turn on so I can't continue forward.  https://oscarliang.com/gps-mini-quad/

Does anyone have any idea what could be wrong? 

Below is my settings dump for what it's worth 

defaults nosave


# version
# Betaflight / CLRACINGF4 (CLR4) 3.3.1 Apr  3 2018 / 09:28:24 (4b7eaf79d) MSP API: 1.37

# reset configuration to default settings
defaults nosave

# name

# resources

# mixer

# servo

# servo mix


# feature
feature GPS

# beeper

# map

# serial
serial 3 2 115200 57600 0 115200
serial 5 64 115200 57600 0 115200

# led

# color

# mode_color

# aux
aux 0 0 0 1700 2100 0
aux 1 1 2 1700 2100 0
aux 2 2 1 1700 2100 0
aux 3 10 3 1700 2100 0

# adjrange

# rxrange

# vtx

# rxfail

# master
set serialrx_provider = IBUS
set motor_pwm_protocol = DSHOT600
set gps_provider = UBLOX
set pid_process_denom = 2
set osd_vbat_pos = 2405
set osd_current_pos = 2417

# profile
profile 0


# profile
profile 1


# profile
profile 2


# restore original profile selection
profile 0

# rateprofile
rateprofile 0


# rateprofile
rateprofile 1


# rateprofile
rateprofile 2


# rateprofile
rateprofile 3


# rateprofile
rateprofile 4


# rateprofile
rateprofile 5


# restore original rateprofile selection
rateprofile 0

# save configuration
Reply
Login to remove this ad | Register Here
#2
There are several clones and versions of the BN220. So unless you have a spare working GPS its hard to guess. Unless you hook it up to an Arduino development board to test it. Or trying to use a FTDI serial adapter and test via U-Center software.

I do not see anything wrong with your diff.

Did you try another UART?

Did you check for shorts on the GPS wiring using a multimeter?
Reply
#3
(22-Oct-2022, 05:11 AM)kafie1980 Wrote: There are several clones and versions of the BN220. So unless you have a spare working GPS its hard to guess. Unless you hook it up to an Arduino development board to test it. Or trying to use a FTDI serial adapter and test via U-Center software.

I do not see anything wrong with your diff.

Did you try another UART?

Did you check for shorts on the GPS wiring using a multimeter?

I checked for continuity between the pads on the flight controller and the wires on the GPS and they all seem to connect correctly.  No shorts either.  I think I'm going to try to switch them to UART 6 (which my receiver is currently on.  Hopefully that will work on UART 4 where my GPS is currently on).  Also my power for the GPS is hooked up to BUZZ+ and BUZZ-.  I read somewhere not to use BUZZ- even though I think that's can also be used as a generic ground.  Plus my GPS seems to be getting power, just not a data signal, so I don't think that will help my problem.   I unfortunately don't have a spare GPS lying around or Arduino to test it on another board. 

I just hope it's not a software problem.  I'm running the latest betaflight on my computer, and I'm running an old version on my flight controller(3.3.1).  Not sure if that's going to be a problem.
Reply
#4
I can’t comment on the older version of the firmware and that’s fairly old.

What FC is this?

Edit: Just noticed you have a JB F4 which should suppose newer Betaflight firmware. Why not try the latest firmware?
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  EByte E108 GN02D GPS BaconFPV 3 79 14-Apr-2024, 03:43 PM
Last Post: BaconFPV
  GEPRC GPS M1025 series hawk01 0 68 13-Apr-2024, 12:54 AM
Last Post: hawk01
  BetaFlight Connection Issues..... Coleon 17 587 02-Apr-2024, 12:26 PM
Last Post: iFly4rotors
  Betaflight 4.4.3 on Speedybee F4V4 Ladu 4 219 14-Mar-2024, 04:45 PM
Last Post: Ladu
  Solved SPI V3 ELRS won't bind nicetomeetyou 5 385 23-Feb-2024, 05:22 PM
Last Post: nicetomeetyou


Login to remove this ad | Register Here