Beitian BE-182 GPS with openXsensor doesn´t work

[Blamer]

Hi there,

I bought the Beitian BE-182 GPS on aliexpress and tried to use it with openXsensor. Unfortunately I do not receive any GPS- signals on my transmitter. I checked the wiring on the Arduino Nano several times. The openXsensor works great with other sensors (e.g. VFAS). I also changed the standard setting from 38000 to 9600 bauds with u-center (see attached screenshot), as described in oXs_config.description.h, without any success.

Does anyone has experience in setting up the BE-182 GPS with openXsensor?


Link: https://de.aliexpress.com/item/10050053 ... pt=glo2deu

Frank

[Carbo]

Hi,
UBlox M10 should be supported with the latest master, earlier versions will not work.
https://github.com/openXsensor/openXsen ... master.zip

[Blamer]

Thanks a lot Carbo for the reply! You are right: I used an earlier version of the master from github. Iḿ going to give the new version a try within the next couple of days.

Frank

[Blamer]

Hi together, I have a follow up question: I studied the oXs_config_description.h file in the openXsensor-master.zip in Carboś link in detail. In order to activate UBlox M10 I have to uncomment the function //#define GPS_M10 in oXs_config_basic.h or oXs_config_advanced.h. But the parameter is not listed in both files! I used the the search function in Arduino and the parameter is not included in the entire master package.

Where can I find the parameter #define GPS_M10? Do I have to include it by myself in basic.h or advanced.h? If so, where do I have to insert it?

Thanks a lot for the reply!

Frank


**** 9 - GPS (optionnal) *********************************************************************************************
* oXs is configured with following parameters (in the oXs_config_basic.h and oXs_config_advanced.h files):
* - #define A_GPS_IS_CONNECTED NO : Replace NO by YES if a GPS is connected and has to transmit his data
* - #define GPS_M10 : uncomment this line if GPS module is using M9/M10 engine
* - #define GPS_SPEED_IN_KMH : uncomment this line if GPS speed has to be sent in km/h instead of knot/h
* - #define GPS_SPEED_3D : uncomment this line if GPS speed has to be the 3d speed instead of the 2d speed (note: 3d is probably less accurate - to test)
* - #define GPS_REFRESH_RATE 5 : rate at which GPS sent new data; select between 1, 5 or 10 (Hz). Default = 5 Hz; Ublox NEO6 does not support 10 hz
* - #define GPS_TRANSMIT_TIME : for sport only, transmit UTC time from GPS

[Carbo]

Seems the config files have not been modified yet. Most people includig me switched to RP2040. I would try to add the line into advanced.h like this:

Code: Select all

// --------- 9 - GPS ------------------------------------------------------------------------------------------------
//#define GPS_SPEED_IN_KMH  // uncomment this line if GPS speed has to be sent in km/h instead of knot/h (only for Frsky protocol)
#define GPS_SPEED_3D      // uncomment this line if GPS speed has to be the 3d speed instead of the 2d speed (note: 3d is probably less accurate - to test) 
#define GPS_M10 : uncomment this line if GPS module is using M9/M10 engine
#define GPS_REFRESH_RATE  5 

[Blamer]

Carbo, thanks a lot for your answer.

I just included the parameter #define GPS_M10 in advanced.h and tested it on two different BE-182 with 9600 baud and 38600 baud: It still doesn´t work. Looks like openXsensor will not be be further developed since many files haven´t been updated for many months or years, including the documentation in oXs_config_description.h. If everybody switched to RP2040 this would be a possible explanation.

Will BE-182 work with RP2040? I haven´t been able to figure out if this sensor accepts CASIC messages. If so, I will also switch to RP2040.

Thanks a lot for the reply!!
Frank