ms5611 power up issue

Wene001 · Post by **Wene001** » Tue Apr 26, 2016 8:04 am

Hi

I have build an openxsensor.
Arduino pro mini clone 5v 16mhz
GY-63 ms5611
Openxsensor newest master version form github (v7)

Receiver is X8R wit EU LBT Firmware.

if i power the receiver and the OXS at the same time, then there is no Vario Data working (Voltage reading from A0, A1, A2 works)

if i power the X8R and plug in the OXS sensor in a second step, then all is ok

All ideas welcome

Thanks

BTW
@mstrens
If you want to correct this...
A3 & A4 should be divided by 10
5V shows up at 50V

kalle123 · Post by **kalle123** » Tue Apr 26, 2016 10:22 am

Using Vcc or Raw on pro mini?

Wene001 · Post by **Wene001** » Tue Apr 26, 2016 10:34 am

Input Voltage from s.port to arduino pro mini and ms5611 both hooked to raw pin
Both power leds solid (arduino and GY-63)

Testet with NiMh 5,95V

mstrens · Post by **mstrens** » Tue Apr 26, 2016 11:37 am

If you can, I suggest that you activate the "DEBUG" option available at the end of the oxs_config.h file.
When this option is activated and Arduino is powered on, it will send debug messages to the PC terminal via the FTDI.

Take care in this process to connect only 2 wires between the arduino and FTDI.
You should connect only ground signal and arduino Tx to FDTI Rx.
Do not connect the other pins of FTDI (in order to avoid having dubbel power supply and reset forced by FTDI)

If you can make this test, then please post here the messages that oXs will send to the pc when the receiver and oXs are powered up.

Note : perhaps I should add some code in oXs in order to force a reset of MS5611 when arduino start up but up to now it did not seem to be required.

Wene001 · Post by **Wene001** » Tue Apr 26, 2016 1:13 pm

hmmmmm suspect
in the serial window i see this
6^›.}—ñÓ‚ £ÓV‚—“'+)_À:YÌ’‚Ñ*ÒÜÿ@ãxM/ÿ¨Ö“Úš£rð0Sl¯Í—_ÀiA£ mÜ “Á&Á/d$
when powering up. Is my 2303 Serial Adapter bad??

But more strange....with the debug option set in config.h vario works like a charm ??confused??

My config.h....

// OpenXsensor https://github.com/openXsensor/
// started by Rainer Schlosshan

//******************************************************************************************************************************************************* //
// //
// ! IMPORTANT NOTE !!!!!!!!!! Another file in this project (see oXs_config_description.h) provides detailed explanations on how to set up this file. //
// //
//******************************************************************************************************************************************************* //
// Note: the oXs_config.h file present on the GitHub site is not always meaningful.
// It could be that the combination of active/non active parameters is not consistent.
// This is just the result of many updates and tests in this document.
// So take always care to set up the oXs_config.h file according to your needs and check carefully all options.
// You can also use the oXs configurator in order to generate automatically a valid file.

#ifndef OXS_CONFIG_h
#define OXS_CONFIG_h

// --------- 1 - Telemetry protocol ---------
#define PROTOCOL FRSKY_SPORT // select between FRSKY_SPORT , FRSKY_HUB , FRSKY_SPORT_HUB , MULTIPLEX , HOTT

// --------- 2 - Serial data pin choice ---------
#define PIN_SERIALTX 4 // The pin which transmits the serial data to the telemetry receiver, Usually pin 4

// --------- 3 - PPM settings ---------
//#define PIN_PPM 3 // default is 2 but my own device use 3
#define PPM_MIN_100 980 // default 1500 - 512 ; // pulse width (usec) when TX sends a channel = -100
#define PPM_PLUS_100 1990 // default 1500 + 512 ; // pulse width (usec) when TX sends a channel = +100

// --------- 4 - Vario settings ---------

// ***** 4.1 - Connecting 1 or 2 MS5611 barometric sensor *****
#define VARIO // set as comment if there is no vario
//#define SENSOR_IS_BMP180 // set as comment if baro sensor is MS5611
//#define VARIO2 // set as comment if there is no second vario

// ***** 4.2 - Sensitivity predefined by program *****
#define SENSITIVITY_MIN 50
#define SENSITIVITY_MAX 300
#define SENSITIVITY_MIN_AT 100
#define SENSITIVITY_MAX_AT 1000

// ***** 4.3 - Sensitivity adjusted from the TX *****
#define SENSITIVITY_MIN_AT_PPM 10 // sensitivity will be changed by OXS only when PPM signal is between the specified range enlarged by -5 / +5
#define SENSITIVITY_MAX_AT_PPM 40
#define SENSITIVITY_PPM_MIN 20 // common value for vario is 20
#define SENSITIVITY_PPM_MAX 100 // common value for vario is 100

// ***** 4.4 - Hysteresis parameter & Alt compensation based on sensor temp *****
#define VARIOHYSTERESIS 0
//#define ALT_TEMP_COMPENSATION 800

// ***** 4.5 - Vertical speeds calculations *****
#define VARIO_PRIMARY FIRST_BARO // select between FIRST_BARO, SECOND_BARO , AVERAGE_FIRST_SECOND, AIRSPEED_COMPENSATED , BARO_AND_IMU
#define VARIO_SECONDARY FIRST_BARO // select between FIRST_BARO, SECOND_BARO , AVERAGE_FIRST_SECOND, AIRSPEED_COMPENSATED , BARO_AND_IMU
#define SWITCH_VARIO_MIN_AT_PPM 10
#define SWITCH_VARIO_MAX_AT_PPM 90

// ***** 4.6 - Analog vertical speed *****
//#define PIN_ANALOG_VSPEED 3
#define ANALOG_VSPEED_MIN -3
#define ANALOG_VSPEED_MAX 3

// ***** 4.7 - Calculating glider ratio, average sink/climb rate ******************************
//#define GLIDER_RATIO_CALCULATED_AFTER_X_SEC 1 // value must be higher or equal to 1, set line as comment if no calculation must be performed
#define SPEED_TOLERANCE 5 // in % of speed
#define VSPEED_MIN_TOLERANCE -200 // out of tolerance when Vspeed is lower than this value (cm/sec)
#define VSPEED_MAX_TOLERANCE -10 // out of tolerance when Vspeed is upper than this value (cm/sec)

// --------- 5 - Airspeed settings ---------
//#define AIRSPEED MS4525
#define AIRSPEED_AT_SEA_LEVEL_AND_15C // if this line is commented, airspeed is calculated using baro pressure and temperature (so being "true" airspeed instead of normalised airspeed)
#define AIRSPEED_IN_KMH // uncomment this line if airspeed has to be in km/h instead of knot/h (openTx 2.0 expect knot/h while openTx 2.1 expect km/h)

#define AIRSPEED_RESET_AT_PPM 100

#define COMPENSATION_MIN_AT_PPM 60
#define COMPENSATION_MAX_AT_PPM 90
#define COMPENSATION_PPM_MIN 80
#define COMPENSATION_PPM_MAX 140

// --------- 6 - Voltages & Current sensor settings ---------

// ***** 6.1 - Voltage Reference to measure voltages and current *****
//#define USE_INTERNAL_REFERENCE // uncomment this line if you use 1.1 volt internal reference instead of Vcc
//#define USE_EXTERNAL_REFERENCE // uncomment this line if you use an external reference instead of Vcc
//#define REFERENCE_VOLTAGE 4970 // set value in milliVolt; if commented, oXs will use or 1100 (if internal ref is used) or 5000 (if internal ref is not used)

// ***** 6.2 - Voltage parameters *****
#define PIN_VOLTAGE 0 , 1 , 2 , 3 , 7 , 8 // set this line as comment if no one voltage have to be measured, set a value to 8 for the voltage(s) not to be measured.
#define RESISTOR_TO_GROUND 12 , 12 , 12 , 0 , 0 , 0 // set value to 0 when no divider is used for a voltage, can contains decimals
#define RESISTOR_TO_VOLTAGE 12 , 12 , 20 , 0 , 0 , 0 // set value to 0 when no divider is used for a voltage, can contains decimals
#define OFFSET_VOLTAGE 0 , 0 , 0 , 0 , 0 , 0 // optionnal, can be negative, must be integer
#define SCALE_VOLTAGE 0.1 , 0.1 , 1 , 1 , 1 , 1 // optionnal, can be negative, can have decimals

// ***** 6.3 - Max number of Lipo cells to measure (and transmit to Tx) *****
//#define NUMBEROFCELLS 3 // Put this line as comment or set value to 0 (zero) if you do not want to transmit cell voltages.

// ***** 6.4 - Current parameters *****
//#define PIN_CURRENTSENSOR 3
#define MVOLT_AT_ZERO_AMP 2500 // in millivolt
#define MVOLT_PER_AMP 60 // in milliVolt per Amp
#define RESISTOR_TO_GROUND_FOR_CURRENT 19.8 // put as comment or set to 0 if no divider is used
#define RESISTOR_TO_CURRENT_SENSOR 39 // put as comment or set to 0 if no divider is used

// --------- 7 - RPM (rotations per minute) settings ---------
//#define MEASURE_RPM

// --------- 8 - Persistent memory settings ---------
//#define SAVE_TO_EEPROM
//#define PIN_PUSHBUTTON 2 // default is 10 but my own device is 2

// --------- 9 - Data to transmit ---------
#define VSPEED_SOURCE FIRST_BARO // select between FIRST_BARO, SECOND_BARO , AVERAGE_FIRST_SECOND, AIRSPEED_COMPENSATED , BARO_AND_IMU or PPM_SELECTION
// ***** 9.1 - Frsky data *****
#define VFAS_SOURCE VOLT_3 // select between VOLT_1, VOLT_2, VOLT_3 , VOLT_4, VOLT_5 , VOLT_6
#define FUEL_SOURCE VOLT_4 // select between VOLT_1, VOLT_2, VOLT_3 , VOLT_4, VOLT_5 , VOLT_6
#define A3_SOURCE VOLT_1 // select between VOLT_1, VOLT_2, VOLT_3 , VOLT_4, VOLT_5 , VOLT_6
#define A4_SOURCE VOLT_2 // select between VOLT_1, VOLT_2, VOLT_3 , VOLT_4, VOLT_5 , VOLT_6
//#define ACCX_SOURCE VOLT_5 // select between TEST_1, TEST_2, TEST_3, GLIDER_RATIO , SECONDS_SINCE_T0 ,AVERAGE_VSPEED_SINCE_TO , VOLT_1, VOLT_2, VOLT_3, VOLT_4, VOLT_5, VOLT_6, PITCH, ROLL , YAW
//#define ACCY_SOURCE VOLT_6 // select between TEST_1, TEST_2, TEST_3, GLIDER_RATIO , SECONDS_SINCE_T0 ,AVERAGE_VSPEED_SINCE_TO , VOLT_1, VOLT_2, VOLT_3, VOLT_4, VOLT_5, VOLT_6, PITCH, ROLL , YAW
//#define ACCZ_SOURCE VOLT_3 // select between TEST_1, TEST_2, TEST_3, GLIDER_RATIO , SECONDS_SINCE_T0 ,AVERAGE_VSPEED_SINCE_TO , VOLT_1, VOLT_2, VOLT_3, VOLT_4, VOLT_5, VOLT_6, PITCH, ROLL , YAW
//#define T1_SOURCE VOLT_1 // select between TEST_1, TEST_2, TEST_3 , GLIDER_RATIO , SECONDS_SINCE_T0 ,AVERAGE_VSPEED_SINCE_TO , SENSITIVITY, PPM, VOLT_1, VOLT_2, VOLT_3, VOLT_4, VOLT_5, VOLT_6
//#define T2_SOURCE VOLT_1 // select between TEST_1, TEST_2, TEST_3, , GLIDER_RATIO, SECONDS_SINCE_T0 ,AVERAGE_VSPEED_SINCE_TO , SENSITIVITY, PPM, VOLT_1, VOLT_2, VOLT_3, VOLT_4, VOLT_5, VOLT_6

// ***** 9.2 - Hott data *****
//#define BATTERY_1_SOURCE VOLT_4 // select between VOLT_1, VOLT_2, VOLT_3, VOLT_4, VOLT_5, VOLT_6
//#define BATTERY_2_SOURCE VOLT_2 // select between VOLT_1, VOLT_2, VOLT_3, VOLT_4, VOLT_5, VOLT_6
//#define MAIN_BATTERY_SOURCE VOLT_5 // select between VOLT_1, VOLT_2, VOLT_3, VOLT_4, VOLT_5, VOLT_6
//#define TEMPERATURE_1_SOURCE TEST_1 // select between TEST_1, TEST_2, TEST_3 , GLIDER_RATIO , SENSITIVITY , PPM
//#define TEMPERATURE_2_SOURCE PPM // select between TEST_1, TEST_2, TEST_3 , GLIDER_RATIO , SENSITIVITY, PPM

// ***** 9.3 - Multiplex data *****
//#define SETUP_MULTIPLEX_DATA_TO_SEND \
3 , ALTIMETER , 1 , 1 , 0 , -16384 , 16383 , \
6 , VERTICAL_SPEED , 1 , 1 , 0, -500 , 500 , \
5 , REL_ALTIMETER , 1 , 1 , 0 , -16384 , 16383 , \
7 , CELL_TOT , 1 , 1 , 0 , -16384 , 16383 , \
8 , ALTIMETER_MAX , 1 , 1 , 0 , -16384 , 16383 , \
4 , VOLT_4 , 1 , 1 , 0 , -16384 , 16383 , \
9 , PPM , 1 , 1 , 0 , -16384 , 16383

// --------- 10 - Sequencer ---------
//#define SEQUENCE_OUTPUTS 0b100000
#define SEQUENCE_UNIT 100
#define SEQUENCE_m100 1 , 0b100000 , 1 , 0b000000 , 1 , 0b100000 , 1 , 0b000000
#define SEQUENCE_m75 1 , 0b100000 , 1 , 0b000000 , 2 , 0b100000 , 2 , 0b000000
#define SEQUENCE_m50 5 , 0b100000 , 5 , 0b000000
#define SEQUENCE_m25 5 , 0b100000 , 5 , 0b000000 , 0 , 0b100000
#define SEQUENCE_0 3 , 0b100000 , 1 , 0b000000
#define SEQUENCE_25 2 , 0b100000 , 2 , 0b000000
#define SEQUENCE_50 5 , 0b100000 , 5 , 0b000000
#define SEQUENCE_75 7 , 0b100000 , 7 , 0b000000
#define SEQUENCE_100 8 , 0b100000 , 8 , 0b000000
#define SEQUENCE_LOW 10 , 0b100000 ,10 , 0b000000 // sequence for Low voltage
//#define SEQUENCE_MIN_VOLT_6 4000 // sequence_100 will be activated if voltage 6 is lower that the value.
#define SEQUENCE_MIN_CELL 3000 // sequence_100 will be activated if lowest cell is lower that the value.

// --------- 11 - GPS ------------------------------------------------------------------------------------------------
//#define GPS_INSTALLED // uncomment this line if a GPS is connected
//#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)

// --------- 12 - IMU 6050 --- (accelerometer + gyro -----------------------------------------------------------------
//#define USE_6050 // uncomment this line if a IMU 6050 is connected
#define PIN_INT_6050 3 // Interrupt from 6050 has to be connected to Arduino pin 2 or pin 3 (do not use here the same pin as PPM)
#define ACC_OFFSET_X -160 // fill here the first value reported when DISPLAY_ACC_OFFSET is activated
#define ACC_OFFSET_Y -150 // fill here the second value reported when DISPLAY_ACC_OFFSET is activated
#define ACC_OFFSET_Z -1100 // fill here the third value reported when DISPLAY_ACC_OFFSET is activated
//#define DISPLAY_ACC_OFFSET // used ONLY in order to display the acceleration offset on pc terminal; KEEP AS COMMENT once offsets has been setup

// --------- xx - Reserved for developer. DEBUG must be activated here when we want to debug one or several functions in some other files. ---------
#define DEBUG
//#define DEBUG_BLINK // use by developper in order to blink the led without using uart for debugging

#define BASED_ON_AIRSPEED 0
#define BASED_ON_GPS_SPEED 1
#define AVERAGING_DELAY_MILLISEC AVERAGING_TOLERANCE * 100
#if defined( DISPLAY_ACC_OFFSET ) && defined( USE_6050 )
#define DEBUG
#endif

#define FIRST_BARO 1
#define SECOND_BARO 2
#define AVERAGE_FIRST_SECOND 4
#define AIRSPEED_COMPENSATED 3
#define BARO_AND_IMU 5
#define PPM_SELECTION 6

#include <Arduino.h>
struct ONE_MEASUREMENT {
uint8_t available ;
int32_t value ;
} ;

#define FRSKY_SPORT 1
#define FRSKY_HUB 2
#define FRSKY_SPORT_HUB 3
#define MULTIPLEX 4
#define HOTT 5

#define SECONDS_SINCE_T0 32
#define AVERAGE_VSPEED_SINCE_TO 33

#ifdef DEBUG
//#include "HardwareSerial.h"
#endif

#ifdef GPS_INSTALLED
//#include "HardwareSerial.h"

#endif // End define OXS_CONFIG_h

#endif

Wene001 · Post by **Wene001** » Tue Apr 26, 2016 1:29 pm

For now CSB Pin is connected to GND

mstrens · Post by **mstrens** » Tue Apr 26, 2016 1:49 pm

The strange characters that you get in debug mode are probably the result of a wrong baud rate in your PC terminal session.
When there is no GPS connected, baud rate must be 115200. This is defined in terminal session from Arduino IDE I think.

It is strange that it works in debug mode. Still it could be that in debug mode arduino performs more operations before trying to read the MS5611 because it sends first some messages to FTDI.
If this is the reason, you can try to deactivate the DEBUG mode and to add a delay in the "setup" function.
To test this, you can insert a new line in order to add folowing code in openXsensor.ino file at line 370 (so just after the definition of the setup() function.
delay(500) ;

This will force the arduino to wait msec before going further.

Wene001 · Post by **Wene001** » Tue Apr 26, 2016 4:18 pm

Delay(1500) doesnt help (Tried yestersday)
I ll test with the right baud rate later

Wene001 · Post by **Wene001** » Tue Apr 26, 2016 6:41 pm

Did some more testing

It has nothing to do with debug on or off.
If Arduino TX and Gnd are connected to USB2Serial Adapter, every boot is successfull. (message "Vario is up" on serial monitor@115200)

If Arduino TX and Gnd are not connected to USB2Serial Adapter, every first boot fails for the MS5611 (Voltagereading ok)
Disconnecting Power from Receiver or arduino for 0,5-1sec and reconnect solves the Problem and Vario is running fine.
Doesnt matter if debug is on or off.

Every short power disconnect is fine. longer power cycles >5sek and the vario is dead.

?????????????????

kalle123 · Post by **kalle123** » Wed Apr 27, 2016 5:50 am

Change the arduino pro mini, try another MS5611.

Same behavior with other FrSky RX?

Post by **jhsa** » Wed Apr 27, 2016 6:18 am

What happens if you don't recycle the power but just press the reset button?

João

mstrens · Post by **mstrens** » Wed Apr 27, 2016 6:57 am

I do not see what could be the reason.

Perhaps can you try oXs version 5. This version is still available on github. Take that the config in this version uses different parameters.

Wene001 · Post by **Wene001** » Wed Apr 27, 2016 8:06 am

I`ve tried already OXS 5, same behavior
I build a second one this morning, new (the same charge) arduino, and new GY-63
Works from the first second.

When my Arduino Uno arrives, ill disassemble the components and test the GY- 63 on the breadboard

Wene001 · Post by **Wene001** » Wed Apr 27, 2016 8:08 am

Thanks for help

@mstrens
Where do you think is the best place in code to implement the divider (10) for A3 and A4 ?

kalle123 · Post by **kalle123** » Wed Apr 27, 2016 11:00 am

Wene001 wrote: When my Arduino Uno arrives, ill disassemble the components and test the GY- 63 on the breadboard

I do it the other way around. Test with uno and THEN start the soldering iron .....

Post by **MikeB** » Wed Apr 27, 2016 11:14 am

Wene001 wrote:Where do you think is the best place in code to implement the divider (10) for A3 and A4 ?

What firmware are you using on the transmitter?

Mike.

Wene001 · Post by **Wene001** » Wed Apr 27, 2016 11:26 am

2.17

In The moment i`m using faktor 0.1 in config.h from openxsensor for A3 and A4

mstrens · Post by **mstrens** » Wed Apr 27, 2016 2:49 pm

Yes, using factor 0.1 in config.h is the easiest way to get A3 and A4 divided by 10.
This does not require extra code.
I would like to keep oXs unchanged because there is an easy solution and this avoid using more flash and ram memory.

Otherwise, I should have to create 2 new structures of type ONE_MEASUREMENT (one for A3 and one for A4).
In oxs_out_frsky.cpp:
- in function initMeasurement(), you should have to point to those structure (instead of pointing to something like oXs_Voltage.voltageData.mVolt[A4_SOURCE - VOLT_1]
- in function OXS_OUT::sendSportData(), you should have to fill the 2 variables from each structure. Member "value" should be filled with something like oXs_Voltage.voltageData.mVolt[A4_SOURCE - VOLT_1].value and member "available" should be filled with "true".

Wene001 · Post by **Wene001** » Wed Apr 27, 2016 7:01 pm

Did more testing with the strange Gy-86
mounted on a new arduino
@jhsa
Sometimes Vario is working from first second.
Reset Button helps every time....

@mstrens
is it hard to implement a reset of the ms5611 in void setup ?

edit:
ive build a third openxsensor with a GY-86 and sometimes the vario doesnt work at first boot, too ???
Eventually it has to do with my batch of arduinos ?!?

mstrens · Post by **mstrens** » Wed Apr 27, 2016 8:35 pm

I checked the code and there is already a reset of the ms5611 in the function void setup.
Perhaps can you try to add several reset commands (instead of only one).
This is quite easy.
In the file oxs_MS5611.cpp there is a function void OXS_MS5611::setup().
In line 94 you currently have
errorI2C = I2c.write( _addr,0x1e) ;

You can just repeat it several times replacing the line by:
errorI2C = I2c.write( _addr,0x1e) ; errorI2C = I2c.write( _addr,0x1e) ; errorI2C = I2c.write( _addr,0x1e) ;

It will send 3 reset commands instead of 1.

Can you already try this?

If it still does not work, it would be possible to check if the (last) reset command is accepted or not and this without using the DEBUG mode.
I can provide some code later on if required.

Wene001 · Post by **Wene001** » Sun May 01, 2016 3:44 pm

Tried again with delay.
delay(3000); in line 429 (openxsensor) solved all my problems.

Thanks to all for help

kalle123 · Post by **kalle123** » Thu May 19, 2016 4:10 pm

Did a first test with that equipment yesterday.

Two oXs ver.7.0 with oXs vario and gps and oXs lipo voltage and current.

Yesterdays log like this here (both oXs working at startup)

Today oXs current/voltage at startup and oXs vario/gps delayed

Will do some static test and add a "delay" in openXsensor.ino
Any suggestions? Don't like things working one day and not the next ....

br KH

openrcforums

ms5611 power up issue

ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue

Re: ms5611 power up issue