MultiWii

pm1

ublox CN-06 connected to I2C nav module is anyone else finding that the UBLOX GPS needs to be powered off an on again to start sending its data to the I2C module? I have tried mofiying EOSBandi's code to get the IC2 Nav module to send a warmboot to the ublox (3 seconds after sending all the baud ra...

pm1

Is the file to download? I2c gps nav v2.1 rc2 (Wire lib issue fixed) from here: m Yes Then does the patch go in? I2C_GPS_NAV.ino Yes, function setup I see another Patch: m Which is best? My one is better -> configures to 115200 baud with ublox binary protocol and 10 Hz. If xou try the other one, be...

pm1

CokeViper wrote:Is it already possible to just define a gps coordinate and let the quadrocopter fly to this position?

No, the code has already definitions for 16 WPs, but there is no code to switch to them...

pm1

I am looking to optimize PH for me. If I switch to PH, (*not* RTH), the reaction is totally different, if the *nav* PIDs are zero or not, when I use the sticks to bring the copter by force away from the correct position (to test the reaction). I seem to be blind somehow, but I don't find the piece o...

pm1

I have bought from RCTimer the Crius MultiWii SE V1.0 (with I2C header) + I2C GPS nav module + Crius CN-06 UBlox GPS module I have shorted pins 13 & 14 on the CN-06, connected it via FTDI head to USB and connected in U-Centre, this shows the GPS position and works fine. Plugged together on FC b...

pm1

That was my guess, too. But I did put in a delay before calibration, -> no success...

pm1

Ok, one step further... It seems to be, that the chip is not correctly initialized somehow. On my boards the reaction was even different after power on or reset. The result is, the first configuration, you send to the chip does not work correctly. I now send a dummy configuration at first. After tha...

pm1

I tried now : i2c_rep_start(MAG_ADDRESS<<1); // I2C write direction i2c_write(0); // register selection i2c_write(0x71); // value to write in register i2c_write(0x60); // value to write in register i2c_write(0x01); // value to write in register i2c_stop(); It does not work. I looked again into the d...

pm1

I'm not sure delay between register writes is valid. I think, it's not a question of valid. I agree, there is no reason according to the datasheet why the registers should not be written at once, but I find no reason, why there shouldn't be a delay between them. Reality is, if there is only a small...

pm1

I try to understand: according to your code, configuring register B must be configured before register A otherwise is doesn't work as expected ? No, but after configuring Register B, there must be a delay Here's the relevant bit from the datasheet: ... The datasheet says, you`ll have to have a dela...

pm1

The calibration with the internal test mode of HMC5883 works (at least with my 2 different boards) not as expected: #if defined(HMC5883) magCal[ROLL] = 1160.0 / abs(magADC[ROLL]); magCal[PITCH] = 1160.0 / abs(magADC[PITCH]); magCal[YAW] = 1080.0 / abs(magADC[YAW]); magADC for the different axis shou...

pm1

It's not neccessary, you are right. But that was my first try: running at 38400 and ublox binary at 5 Hz. The only reason, why it might be neccesary is, that some people claimed, that the neo6-m often doesn't initialize correctly without the short of pin13+14. Nevertheless, too much effort to remove...

pm1

I have the Neo-6m running at 115200 baud and 10 Hz. The steps I had to do (rctimer gps+i2c board): 1. Solder pin 13+14 of neo6-m together -> (baudrate to 38400) 2. use arduino 1.0 + eosbandi's path for twi.c and twi.h (1.01 didn't work for me for some reason, if twi patch applied or not) 3. activate...

pm1

quadwalker wrote:HI Dramida
From my side, using 115200b and 10hz seems to be working.

I can confirm that. I have measured the time between consecutive reading and put that to a debug variable, it's about 100 ms...

pm1

Hi, here a new version of the STM32 port based on r181 of the afrodevices svn repository. Download Differences: - main loop fixed to 5 ms - changed altitude hold I made the main loop at fixed intervalls, because I and D-Term are dependent of the loop time in the code today. I found the default loop ...

pm1

@dongs Just compiling the head revision of your stm32 port. I am using codesourcery g++. I am breaking now the flash, the binary size is > 64 k. Your hex file seems to be 30 % smaller than mine. Any hint? Compiler options: -mcpu=cortex-m3 -mthumb -auxbase-strip src/gps.o -Os -Wall -version -fmessage...

pm1

Make the PID calculations at a constant interval. There are now faster processors using the software. The loop time at my 328P is about 3 ms. With an STM32 you have less than 1.5 ms. So the D term has half and I term double effect. I am just testing, what loop time make sense here. Maybe 10ms is eno...

pm1

Hi all, I'm getting better ACC results/less minor twitch by using MAG style LPF instead of current ACC_LPF code... accSmooth[axis] = (accSmooth[axis] * (ACC_LPF_FACTOR - 1) + accADC[axis]) / ACC_LPF_FACTOR; // LPF for Accelerometer values instead of... accTemp[axis] = (accTemp[axis] - (accTemp[axis...

pm1

when compiling latest code r700 out of MultiWii_shared, I get the following warnings: .. t+= inBuf[indRX++]<<8; Could not this be rewritten in a compiler-clean way? Should be like this (sry, not tested...): t+= ((uint16_t)inBuf[indRX++])<<8; t+= ((uint32_t)inBuf[indRX++])<<16; t+= ((uint32_t)inBuf[...

pm1

Hamburger wrote:so we continue to develop in the _shared branch...
anyone willing to do the hard work and synchronize _shared with Alex' non-shared tree?

Maybe not too hard. At the first look there seems to be not much features beside LCD.pde in the shared branch, which didn't found the way into non-shared...

pm1

Cronalex wrote:hi, i have a multiwii crius se i have charged multiwii relase 2.0 but i have a problem
when start my quadcopter and give power to motor the quad do a flip forward but if i charge 1.9 version it's ok have you an idea for my problem?

If you are using level mode, calibrate ACC before use!

pm1

...and i cannot use it because of the toilet bow effect with ACC on and BMA020... Looks like if have to get other sensors..... Maybe a bit of debugging and fixing the problem is an option too One yaw rotation in 20 seconds is not much. Did you already try to compensate with trim? Does the level fun...

pm1

Is it normal that Baro shows negative results in GUI in pre4 That depends on the height above sea-level where you are living. The calculated height is based on an atmospheric pressure of 1013 hPa. At the the moment, we have a pressure of about 1030 hPa here. The calculated height is therefore about...

pm1

... but I think it was a way to introduce more samples in the moving average vector. marbalon said, he had more *unique* samples now. But that isn't true, since now are even less samples taken -> The internal averaging is a bit faster and you'll save the time for the temperature sampling. With 8 ti...

pm1

The BMP085 needs roughly about 3-4.5 milliseconds for one sample. Either the chip averages up to to 8 samples internally (faster), or you read every sample yourself and make an average in code. Since the pressure calculation is relatively complex, your can save a lot of CPU time (at least for the 8 ...

pm1

BMP085 and OSS=2 The oversampling setting was reduced from 8 to 4 samples. The reason was to get more unique samples. But in my opinion now the processor does exactly the same what the BMP085 does internally. Unless there is a bug in the internal oversampling, this is only a waste of CPU time. I hav...

pm1

Hi,
in IMU.pde
void getEstimatedAltitude()
...
if (abs(temp32) < 10 && BaroPID < 10) BaroPID = 0;

I think, intended was this:
if (abs(temp32) < 10 && abs(BaroPID) < 10) BaroPID = 0;

Best regards
Peter

pm1

Hi, I found the following: IMU.pde getEstimatedAltitude () static int16_t BaroHistTab -> should be int32_t, Alt is cm and I am am living at 650 m MSL BaroLow+=BaroHistTab[(BaroHistIdx + temp32 + BARO_TAB_SIZE)%BARO_TAB_SIZE]; should be BaroLow+=BaroHistTab[(BaroHistIdx + temp32 + 1)%BARO_TAB_SIZE]; ...

pm1

Hi,
maybe I am wrong, but please check the follwing code:

void getEstimatedAltitude(){
...
BaroLow+=BaroHistTab[(BaroHistIdx + temp32 + 1 + BARO_TAB_SIZE)%BARO_TAB_SIZE]; //sum older samples

I think the existing code has the latest value in the older samples.

Best regards
Peter

pm1

I am using the BMP085. I have now observed the output in different conditions for a while. - The output is quite noisy - It has reaction times of 0.5 to 2 seconds (I don't know why, but sometimes it is faster, other times slower) - Sometimes the altitude jumps 2m for a couple of seconds, the jumps b...

pm1

@Hamburger But for me this leads to an unwanted increase of memory usage (what we wanted to cure in the first place) from before (with PROGMEM) I didn't check this. Interesting, that it leads to an increase of code and data section. But I read the posts in the posted link. I will try the suggestion ...

pm1

@dongs I dunno if this has been mentioned yet, but the temperature sensor on BMP085 is pretty noisy. That's a new info for me. If I assume, that the sensor is normally surrounded by foam and perhaps a housing, making a temperature average of 1-5s+ seems to be absolutely reasonable: I will try that o...

pm1

@ziss_dm You also can increase BW of sensor (currently it takes 2 samples per second, as I remember) Is currentTime not microsends? Then I would get about 20 samples per second, as far as I see in the code (BMP085). @Magnetron I have implemented a moving avarage algorithm for gyros, accs, baro and s...

pm1

Hi, I tested the altidude with the 1.9 version and the new dev release. I am not very happy at the moment with the results. The only thing which works more or less predictable for me is a low altitude P term. My findings at the moment are: - If I do not average the BaroAlt, I get ridiculous velocity...

pm1

Your patch file seems to contain some stuff twice?

...not only some stuff. For some reason the patch file was appended instead of overwritten. File should be ok now.

pm1

Hi, I have looked into the warning, and I think, I can fix them. As far as I see, there are only 2 warnings, which may lead to wrong code (the rest seems to be more or less cosmetic): GPS.pde:36: warning: operation on 'd' may be undefined -> The usage of a decrement operator twice in a line is not a...

MultiWii

Search found 136 matches

Re: GPS integration

Re: RCTimer MWC SE V1.0 + I2C nav + CN-06

Re: GPS integration

Re: GPS integration

Re: RCTimer MWC SE V1.0 + I2C nav + CN-06

Re: Possible bug in HMC5883 code

Re: Possible bug in HMC5883 code

Re: Possible bug in HMC5883 code

Re: Possible bug in HMC5883 code

Re: Possible bug in HMC5883 code

Possible bug in HMC5883 code

Re: Crius GPS and I2C_GPS_NAV

Re: Crius GPS and I2C_GPS_NAV

Re: New RCtimer GPS Ublox Neo 6M fails to perform on Mega bo

Re: Multiwii port to STM32 and place to ask stupid questions

Re: Multiwii port to STM32 and place to ask stupid questions

Re: wishlist for v2.1

Re: ACC LPF alternative

Re: MultiWii 2.0 bug report

Re: mwc 2.0 ++

Re: MultiWii 2.0 is coming

Re: MultiWii 2.0 is coming

Re: MultiWii 2.0 is coming

Re: MultiWii 2.0 is coming

Re: MultiWii 2.0 is coming

Re: MultiWii 2.0 is coming

Re: MultiWii 2.0 is coming

Possible bugs in MultiWii_dev_20120225

Re: dev20120219 and new features... info?

Re: Alt. Hold Ideas and discussion

Re: cpp and compiler warnings defaced

Re: Improving Altitude Hold Performance

Re: Improving Altitude Hold Performance

Re: Improving Altitude Hold Performance

Re: cpp and compiler warnings defaced

Re: cpp and compiler warnings defaced