Open CodeWorksCZ opened 2 months ago
Hello CodeWorksCZ,
Here is my "full house" configuration. Everything works , no problems. I think your RP2040 board have a power problem or you have a sensor or wiring problem. You must set TLM= for Telemetrie and PRI= for SBUS, with your configuration the RP2040 can`t work correctly. Primary channels input = 255 (PRI = 5, 9, 21, 25) Secondary channels input = 255 (SEC = 1, 13, 17, 29) Telemetry . . . . . . . . = 255 (TLM = 0, 1, 2, ..., 29)
BeiTian BE-250 SBUS_out Decoder RMILEC V3 2xADS1115 GY-86 MS4225 Testet with FrSky X20S and TD-R10
Function GPIO Change entering XXX=yyy (yyy=255 to disable)
Primary channels input = 21 (PRI = 5, 9, 21, 25) Secondary channels input = 255 (SEC = 1, 13, 17, 29) Telemetry . . . . . . . . = 255 (TLM = 0, 1, 2, ..., 29) GPS Rx . . . . . . . . . = 12 (GPS_RX = 0, 1, 2, ..., 29) GPS Tx . . . . . . . . . = 13 (GPS_TX = 0, 1, 2, ..., 29) Sbus OUT . . . . . . . . = 2 (SBUS_OUT= 0, 1, 2, ..., 29) RPM . . . . . . . . . . = 4 (RPM = 0, 1, 2, ..., 29) SDA (I2C sensors) . . . . = 14 (SDA = 2, 6, 10, 14, 18, 22, 26) SCL (I2C sensors) . . . . = 15 (SCL = 3, 7, 11, 15, 19, 23, 27) PWM Channels 1, 2, 3 ,4 = 255 255 255 255 (C1 / C16= 0, 1, 2, ..., 15) PWM Channels 5, 6, 7 ,8 = 255 255 7 255 PWM Channels 9,10,11,12 = 255 255 255 255 PWM Channels 13,14,15,16 = 255 255 255 255 Voltage 1, 2, 3, 4 = 26 27 28 29 (V1 / V4 = 26, 27, 28, 29) RGB led . . . . . . . . . = 18 (RGB = 0, 1, 2, ..., 29) Logger . . . . . . . . . = 0 (LOG = 0, 1, 2, ..., 29) ESC . . . . . . . . . . . = 1 (ESC_PIN= 0, 1, 2, ..., 29) Locator CS . . . . . . . = 255 (SPI_CS = 0, 1, 2, ..., 29) SCK . . . . . . . = 255 (SPI_SCK= 10, 14, 26) MOSI . . . . . . = 255 (SPI_MOSI=11, 15, 27) MISO . . . . . . = 255 (SPI_MISO=8, 12, 24, 28) Output level High . . . . = 255 (HIGH = 0, 1, 2, ..., 29) Output level Low . . . . = 255 (LOW = 0, 1, 2, ..., 29)
Esc type is HW4 (Hobbywing V4)
Protocol is Fbus(Frsky) CRSF baudrate = 420000 Logger baudrate = 115200 PWM is generated at = 50 Hz Voltage parameters: Scales : 8.830600 , 1.000000 , 1.000000 , 1.000000 Offsets: 0.000000 , 0.000000 , 0.000000 , 0.000000 No temperature sensors are connected on V3 and V4 RPM multiplier = 1.000000 Baro sensor is detected using MS5611 at I2c adress 77 Sensitivity min = 100 (at 100) , max = 300 (at 1000) Hysteresis = 5 Aispeed sensor is detected using MS4525 Vspeed compensation channel = 7 First analog to digital sensor is detected using ads1115 Measurement setup: 4 , 5 , 6 ,7 Gains: 1 , 1 , 1 ,1 Rates: 5 , 5 , 5 ,5 Offsets: 0.000000 , 0.000000 , 0.000000 ,0.000000 Scales: 1.000000 , 1.000000 , 1.000000 ,1.000000 Averaged on: 10 , 10 , 10 ,10 Second analog to digital sensor is detected using ads1115 Measurement setup: 4 , 5 , 6 ,7 Gains: 1 , 1 , 1 ,1 Rates: 5 , 5 , 5 ,5 Offsets: 0.000000 , 0.000000 , 0.000000 ,0.000000 Scales: 1.000000 , 1.000000 , 1.000000 ,1.000000 Averaged on: 10 , 10 , 10 ,10 Foreseen GPS type is Ublox (configured by oXs) :GPS is detected and has a fix Led color is normal (not inverted) Failsafe uses predefined values Chan 1...4 = 1500 1500 1500 1500 Chan 5...8 = 1500 1500 1500 1500 Chan 9...12 = 1500 1500 1500 1500 Chan 13...16= 1500 1500 1500 1500 Acc/Gyro is detected using MP6050 Acceleration param: ACC= 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 Gyro offsets X, Y, Z = 0 , -19 , -24 Orientation Horizontal is UP(Z+) Vertical is FRONT(X+)
Gyro is not configured
No sequencers are defined
Config parameters are OK Press ? + Enter to get help about the commands processing cmd
Cmd to execute: FV
GPS Latitude = XX.1225696 degree GPS Longitude = X.7173136 degree GPS Groundspeed = 10 cm/s GPS Heading = 175.040000 degree GPS Altitude = 3887 cm GPS Num sat. = 121 GPS Date J M A = 27 8 24 GPS Time H M S = 12 21 18 GPS Pdop = 115 GPS Home bearing = 227 degree GPS Home distance = 0 m Volt 1 = 5865 mVolt Current (Volt 2) = 678 mA Volt 3 = 707 mVolt Volt 4 = 257 mVolt Capacity (using current) = 2 mAh Vspeed = 2 cm/s Baro Rel altitude = 7 cm Pitch = -1.000000 degree Roll = 1.000000 degree RPM = 994 Hertz Ads 1 1 = 118 mVolt Ads 1 2 = 118 mVolt Ads 1 3 = 118 mVolt Ads 1 4 = 118 mVolt Ads 2 1 = 118 mVolt Ads 2 2 = 118 mVolt Ads 2 3 = 118 mVolt Ads 2 4 = 118 mVolt Airspeed = -182 cm/s Compensated Vspeed = -1 cm/s Gps cumulative distance = 0 Acc X = -0.018000g Acc Y = 0.020000g Acc Z = 0.832000g Reserve 5 = -111 Vspeed compensation = 1.10 pwmTop= 20000
best regards, Torsten
Thanks Torsten for your answer. I need to dig deeper. I have also ordered another GPS module to see if the one I have is not faulty.
THis is a custom PCB i designed and this time I added MPU6050 but not as a GY board module but as on board components.
Previous version worked but did not have MPU and XGZP module.
I am glad that your "full house" works. At least I know that I have look at the hardware aspect.
Michal
My suspect looking to your hardware (the oxs stack) is that you rely too much on the LDO of the raspberry, The raspberry ldo only supports very low input voltage (5.5V) and very low current. Your stack may ask too much. I suggest you to add an additional LDO like AMS1117-3.3 to supply enough current not regarding INPUT voltage.
Thanks @romoloman. I though about that as well and I even tried to power up the GPS directly from 3.3V bread board and no luck.
I made a small test rig using POGO pins to test both PCB before soldering them together. I am sure I will crack it soon or later. In the future version I might add this LDO if i find some space on the board
Michal
I also have designed my own board to host some sensor but I have choose a different approach from your: I do not have cell measuring but I have optical RPM sensor, current (using a WCS1500) and temperature, plus onboard variometer (MS5611) and GPS, but if you look to the board there is the LDO The board is designed to be used with different protocols. (that's why the solder jumper for sbus2) With this design i have no problem in powering up gps, sensors etc etc (AMS1117-3.3 can supply up to 800mA)
For the GPS i use this one: https://aliexpress.com/item/1005006460489847.html It's rated for 5V but works at 3.3v without troubles. It comes programmed at 115200 so need a reconfiguration in u-center to slow down to 38400.
Hello, I have got a small PCB board which has GPS(BN220) connected and it works fine
There are also sensors connected to it BME280, MPU6050, XGZP, ADS1115.
They also work but as soon as I connect BN220 and power on oXs , serial monitor is clogged by these messages:
Write error for BMP280: -1 Write error ads1115 Write error for MPU6050 Write error for BMP280: -1 Write error ads1115Write error for MPU6050
It only happens when all sendors and gps are connected o oXs
My susspision falls on GPS handling which somehow breaks i2c bus
Have anyone encountered this behaviour?
[Parameters inc. debug without GPS connected]