Hi I upgraded from 2.1 to 2.3.
Same comment on config and deifne.h
Seems to fly ok but I have a lot of i2c errors in 2.3 .
Any idea?
I am using a 10 dof from cgs eu instead a 9 dof and I have to change the ime settings in def accordingly
Those are the changes I made in the code.
CONFIG
#define QUADX
#define MINTHROTTLE 1300 // (*)
#define MAXTHROTTLE 1950
#define MINCOMMAND 900
#define I2C_SPEED 400000L
#define ALLINONE
#define GPS_SERIAL 2 // should be 2 for flyduino v2. It's the serial port number on arduino MEGA
//#define GPS_BAUD 57600
#define GPS_BAUD 115200
#define NMEA
DEF.H
#if defined(ALLINONE)
#define ITG3200
#define BMA180
#define MS561101BA <---- I changed this from BMP085
#define HMC5883
#define ACC_ORIENTATION(X, Y, Z) {imu.accADC[ROLL] = -X; imu.accADC[PITCH] = -Y; imu.accADC[YAW] = Z;}
#define GYRO_ORIENTATION(X, Y, Z) {imu.gyroADC[ROLL] = Y; imu.gyroADC[PITCH] = -X; imu.gyroADC[YAW] = -Z;}
#define MAG_ORIENTATION(X, Y, Z) {imu.magADC[ROLL] = X; imu.magADC[PITCH] = Y; imu.magADC[YAW] = -Z;}
#define BMA180_ADDRESS 0x41
#endif
From 2.1 to 2.3 i2c errors!!
-
- Posts: 1
- Joined: Mon Jan 13, 2014 8:40 am
Re: From 2.1 to 2.3 i2c errors!!
I have the same issue, I have a CRIUS SE V2.0 with CN-06 GPS on I2C with Nav board and KV OSD on my Serial port. After upgrading from 2.1 to 2.3 I get 36 I2C errors in MW Config., Not only am I getting I2C errors, The attitude indicator rolls right when I tilt the quad left, All other indications report left roll. I thought it was a GPS Baud issue so I slowed it down to 57600 and still the same issue. I comment out the I2C bus and disconnect my GPS and the I2C errors go away. I have played with interleave times, Baud rates and port configs, Nothing!!!. I tried it on my CRIUS AIO pro, Same thing. I even tried using Ardruino 1.0.3 to load the sketches, I would like to say something good about MW but as of yet, I won't trust it!.
Re: From 2.1 to 2.3 i2c errors!!
Claustro
Is i2c error count constantly rising or only during boot and init?
In latter case it was annoying but nothing to worry about.
Is i2c error count constantly rising or only during boot and init?
In latter case it was annoying but nothing to worry about.