MultiWii

Posted: **Fri Dec 07, 2012 3:00 pm**

Just curious, it has been awhile since we had an official MWC release, will there be an Official 2.2 release soon?

Posted: **Fri Dec 07, 2012 4:40 pm**

no change in dev since nov 25th. is that normal?

Posted: **Fri Dec 07, 2012 5:08 pm**

I need some testers for vbat alarm via buzzer or pilot lamp.

Posted: **Fri Dec 07, 2012 5:27 pm**

I suppose that's the slow winter time ... hadn't had a chance to fly or look at code in the last 4 weeks.

And i hope FrSky telemetry support will be included in the next release

Posted: **Fri Dec 07, 2012 8:22 pm**

i am not hurry up

i prefer to have a good new ver with lots of improvement than a new ver each months

Posted: **Fri Dec 07, 2012 10:19 pm**

jevermeister wrote:I need some testers for vbat alarm via buzzer or pilot lamp.

I will test it for you as i am not satisfied with current vbat implementation.

Posted: **Sat Dec 08, 2012 4:56 pm**

jevermeister wrote:I need some testers for vbat alarm via buzzer or pilot lamp.

What happened / chamged?
I will be away for another 2 weeks.

Posted: **Sat Dec 08, 2012 6:55 pm**

I noticed some weird soouns withe battery level warnings and pilotlamp inflight...

nils

Posted: **Sat Dec 08, 2012 7:52 pm**

jevermeister wrote:I noticed some weird soouns withe battery level warnings and pilotlamp inflight...

nils

I have not flown recently, but I always rely on the pilot lamp low bat sound and it works fine for me. I fly it till I get the second level warning. I'll compare my code to the latest to see if there is any difference, I may have changed the beep length but I don't think I changed anything in the code logic. Last I checked, I think there was some added code for variometer, which I don't have.

Posted: **Sat Dec 08, 2012 7:55 pm**

Hi,
I transferred the pl code to my 2.1 branch.

The beeps get cut off for level 1 and two. very weird...

Posted: **Sat Dec 08, 2012 7:56 pm**

Hi,
I transferred the pl code to my 2.1 branch.

The beeps get cut off for level 1 and two. very weird...

Posted: **Sat Dec 08, 2012 8:01 pm**

Did it work fine before or is this the first time you are testing the low bat warning code? I think when I looked at your branch code the last time, that is the same code I have. You have all sensors right? Try disabling them one by one. Start with GPS.

Posted: **Sat Dec 08, 2012 8:05 pm**

Hi,
I use everything I have. I had trouble with the old PL code regaridng CPU load.

MEGA 2560, GPS ,baro, mag, gyro, acc...

I did not notice this behavior while motors are off, I tested it by switching amnually between vbat1,2,3,4 etc. and everything was ok...

Posted: **Fri Dec 14, 2012 7:06 am**

solved. had an error in the firszrun of the sequence
already fixed, tested and commited

nils

Posted: **Sat Dec 22, 2012 11:30 pm**

Any updates on when we might see a release?

Posted: **Sun Dec 23, 2012 12:22 am**

I see that development has slowed down.
Dev_r1240 is there for almost two months and it appears quite stable and with many new features that are not in the official 2.1.
If my vote counts, I would say yes for a new official release that's based on dev_r1240.

-- Itai

Posted: **Sun Dec 23, 2012 12:42 am**

I actually installed R1290 this morning.

Posted: **Sun Dec 23, 2012 1:06 am**

itain wrote:I see that development has slowed down.
Dev_r1240 is there for almost two months and it appears quite stable and with many new features that are not in the official 2.1.
If my vote counts, I would say yes for a new official release that's based on dev_r1240.

-- Itai

i think it s better to wait for more improvement.
for example osd is not finish apparently.
some features need more time to be finished

Posted: **Sun Dec 23, 2012 4:45 am**

It depends on Alex and others developers, some features are stable enough, they should be closed and packaged into a released version. Nothing should be waited. And the latest development version is always usable & stable. You can check the development log at http://code.google.com/p/multiwii/source/list, with some developer's description at each version.

I'm on 1284 with EOSbandi new MAG calibration.
The new 1292 has some GPS info displayed on OLED lcd, coded by Hamburger.

Posted: **Sun Dec 23, 2012 7:09 am**

@ Developers, the distance to home turns zero after 654m away from home and restarts from zero. Please look into this issue also. Thanks

Posted: **Fri Dec 28, 2012 7:27 am**

faraz wrote:@ Developers, the distance to home turns zero after 654m away from home and restarts from zero. Please look into this issue also. Thanks

Are you using I2C_GPS?
Here's how GPS_distanceToHome is received from I2C:

Code: Select all

varptr = (uint8_t *)&GPS_distanceToHome;
*varptr++ = i2c_readAck();
*varptr   = i2c_readNak();
GPS_distanceToHome = GPS_distanceToHome / 100;      //register is in CM, we need in meter

It's only using 16 bit unsigned. Max 65535cm or 655m.

Posted: **Sat Dec 29, 2012 12:13 am**

I think a 2.2 should be possible for the end of next month after a code stabilization delay.

Posted: **Sat Dec 29, 2012 12:20 am**

itain wrote:
faraz wrote:@ Developers, the distance to home turns zero after 654m away from home and restarts from zero. Please look into this issue also. Thanks

Are you using I2C_GPS?
Here's how GPS_distanceToHome is received from I2C:
Code: Select all
varptr = (uint8_t *)&GPS_distanceToHome;
*varptr++ = i2c_readAck();
*varptr   = i2c_readNak();
GPS_distanceToHome = GPS_distanceToHome / 100;      //register is in CM, we need in meter
It's only using 16 bit unsigned. Max 65535cm or 655m.

This is effectively a limitation of I2C GPS which is currently only able to handle a maximum of 65535cm.
I think a new 32 bit I2C GPS register for this purpose should solve the problem in a next I2C GPS version

There should be no problem (65km max) with the other option: direct SERIAL GPS device.

Posted: **Sat Dec 29, 2012 7:48 am**

Alexinparis wrote:
itain wrote:
faraz wrote:@ Developers, the distance to home turns zero after 654m away from home and restarts from zero. Please look into this issue also. Thanks

Are you using I2C_GPS?
Here's how GPS_distanceToHome is received from I2C:
Code: Select all
varptr = (uint8_t *)&GPS_distanceToHome;
*varptr++ = i2c_readAck();
*varptr   = i2c_readNak();
GPS_distanceToHome = GPS_distanceToHome / 100;      //register is in CM, we need in meter
It's only using 16 bit unsigned. Max 65535cm or 655m.
This is effectively a limitation of I2C GPS which is currently only able to handle a maximum of 65535cm.
I think a new 32 bit I2C GPS register for this purpose should solve the problem in a next I2C GPS version

There should be no problem (65km max) with the other option: direct SERIAL GPS device.

Thanks Alex and Itain

Posted: **Wed Feb 06, 2013 2:41 am**

any update on when we may see a release? Whats holding it up?

Posted: **Mon May 27, 2013 3:16 am**

For the max 655-meter distance-to-home stuff, instead of waiting for a fix/release you could easily follow these steps to convert the distance to home unit in transmission to meters.

1. Comment out (or remove) this line in MultiWii GPS.ino

Code: Select all

GPS_distanceToHome = GPS_distanceToHome / 100;      //register is in CM, we need in meter. max= 655 meters with this way

So the line looks like:

Code: Select all

// GPS_distanceToHome = GPS_distanceToHome / 100;      //register is in CM, we need in meter. max= 655 meters with this way

This way your flight controller will expect the distance to home data from I2C-GPS in meters instead of centimeters.
You MUST update your i2c-gps-nav unit as well, so continue reading:

2. Download and open i2c_gps_nac_v2.2.beta (r62) from the downloads section.

3. Open I2C_GPS_NAV_v2.2.ino, find the i2c_dataset.distance_to_home line which is line 1535 in the file:

Code: Select all

i2c_dataset.distance_to_home = GPS_distance_cm(GPS_latitude,GPS_longitude,i2c_dataset.gps_wp[0].position.lat,i2c_dataset.gps_wp[0].position.lon);

add a " / 100" just before the ; so the line looks like this:

Code: Select all

i2c_dataset.distance_to_home = GPS_distance_cm(GPS_latitude,GPS_longitude,i2c_dataset.gps_wp[0].position.lat,i2c_dataset.gps_wp[0].position.lon) / 100;

This way the I2C board will send the distance to home data in meters instead of centimeters.

4. Compile and upload the modified Multiwii to your FC board and I2C_GPS to your I2C-gps board. You will probably need an FTDI adapter (if you don't already have one) for this.

5. If you are using these boards with other aircraft (ie. you have more than one flight controller but just one i2c-gps, or more than one i2c-gps but one FC)
you have to update each and every board you use i2c gps with. Else RTH will fail if you mismatch any two modified and unmodified board.

If any of these steps fail, you MUST revert your changes to your flight controller and/or the i2c board and reflash.

Posted: **Tue May 28, 2013 10:57 pm**

I added a modified i2c-gps-nav fork to my github. It has DISTANCE_TO_HOME_IN_METERS as an option in config.h. (You still need to modify MultiWii for this to work)

I couldn't resist and also added FrSky telemetry, so if you don't have space for a FC in your fuselage you can still have the GPS-coordinates in your modified 9X radio or FrSky Telemetry Display. A output pin is required for this to work, and no TTL-inverter is needed. You just connect the right pin to the Rx sideport of your FrSky telemetry receiver. I used digital pin 4 (D4) I don't have a commercial i2c-gps board, I'm using a Arduino ProMini for this. You can set this up and also change the pin in the config.

Here is my branch: https://github.com/disq/i2c-gps-nav (based on v2.2beta1 / r62)

MultiWii

An Official 2.2 Release soon?

An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?

Re: An Official 2.2 Release soon?