List of problems in Version2.2

This forum is dedicated to software development related to MultiWii.
It is not the right place to submit a setup problem.
Software download
Stars112
Posts: 36
Joined: Wed Jan 30, 2013 9:29 pm

List of problems in Version2.2

Post by Stars112 »

Hi, i found another problem in Version2.2.
Please fill this List with your problems too. So we can help Alex and the Team to change this in next Version.

It gives a problem with the GYROFAILSAVECALIBRATION. When i use a WMP the Gyros initial in endless loop.
Effect: no calibration end, Status LED blink everytime. Motor dont start.
When i deaktivate the Failsavecalibration it works to rule.
The FC works with a WMP, BMA020 and 328P Atmel.

Marc

Mis
Posts: 203
Joined: Fri Apr 01, 2011 12:23 am

Re: List of problems in Version2.2

Post by Mis »

Maybe gyro on WMP is too noisy ?
Change one line in sernors.ino from
if(abs(imu.gyroADC[axis] - previousGyroADC[axis]) > 8) tilt=1;
to
if(abs(imu.gyroADC[axis] - previousGyroADC[axis]) > 20) tilt=1;
And check result.
And remember put you model on stable surface after power on. In your hands the calibration never ends.

Stars112
Posts: 36
Joined: Wed Jan 30, 2013 9:29 pm

Re: List of problems in Version2.2

Post by Stars112 »

Ok, 16 is not working. 18 is working and 20 works fine too.
So we have fix the Problem.
In 2.3 we must take a "if define wmp...." or we change the value 8 up To 20.

Stars112
Posts: 36
Joined: Wed Jan 30, 2013 9:29 pm

Re: List of problems in Version2.2

Post by Stars112 »

Another Problems:
With the 32u4 it dosen't work a lcd3w with serial1.
With the 32u4 the crius OLED i2c Display starts after the Save and exit command via sticks every Time the LCD config Mode again.
So i can not exit the LCD config. I Thing ist is a issues with the Serialport. But i don't can solve this.

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: List of problems in Version2.2

Post by Hamburger »

Stars112 wrote:With the 32u4 the crius OLED i2c Display starts after the Save and exit command via sticks every Time the LCD config Mode again.
So i can not exit the LCD config. I Thing ist is a issues with the Serialport. But i don't can solve this.

works for me with nanowii FC and oled allright. To enter and to abort config.menu, both require only short stick input, else it gets interpreted twice.

Stars112
Posts: 36
Joined: Wed Jan 30, 2013 9:29 pm

Re: List of problems in Version2.2

Post by Stars112 »

I teste with the very shortest Stick input what i can do;-)
After aprox. 4-5 sec. after "Save and Exit" the LCD-Config restart again.
I have a Jeti PPM RX. Is it to fast?
Can anyone build a delay after signal to Save and exit? With a Tag, like a Button debouncing.

Stars112
Posts: 36
Joined: Wed Jan 30, 2013 9:29 pm

Re: List of problems in Version2.2

Post by Stars112 »

List of Problems:
-------------------
1. WMP with Gyrofailsavecalibration dosen't work.
FIX: In the Sensors.ino at "if(abs(imu.gyroADC[axis] - previousGyroADC[axis]) > 8) tilt=1;" we must have a "If define WMP..." Question or the Value goes from 8 up to 20.
2. With 32U4 the Serial3W LCD dosen't work with Serial1 from 32U4
FIX: open
3. With the OLED at 32U4 the Config-Menu restarts after Exit on some Systems.
FIX: open
4. The Command SEI() in RX bring the 32U4 to Stop with some PPM Receiver (Jeti RMK2, Spektrum).
FIX: Uncomment the SEI() command in RX. http://fpv-community.de/showthread.php? ... -da!/page3 (Post#101)
Last edited by Stars112 on Fri Apr 19, 2013 11:19 am, edited 1 time in total.

SergioC
Posts: 19
Joined: Sat Dec 22, 2012 11:33 pm

Re: List of problems in Version2.2

Post by SergioC »

Stars112 wrote:List of Problems:
4. The Command SEI() in RX bring the 32U4 to Stop with some PPM Receiver (Jeti RMK2, Spektrum).
FIX: Uncomment the SEI() command in RX.


is this fix confirmed?

I had two software freeze midflight with multiwiigui connected via USB http://www.multiwii.com/forum/viewtopic.php?f=8&t=3266&start=10#p34122.


Sergio.

Stars112
Posts: 36
Joined: Wed Jan 30, 2013 9:29 pm

Re: List of problems in Version2.2

Post by Stars112 »

By my self, the board won't start (boot) after connect the Lipo.
Sometimes boot, sometimes dosen't boot (1/5).

Without the SEI() the Board evertime boot up right.

The Thread out of the FPV-Forum Post#101:
http://fpv-community.de/showthread.php? ... -da!/page3

obor
Posts: 26
Joined: Sun Mar 17, 2013 11:58 pm

Re: List of problems in Version2.2

Post by obor »

Hi,
I found that constant GYRO_SCALE in the code is computed at each loop. It looks weird to rely on the computer to dothis optimisation.
What do you think ?

in IMU.ino

Code: Select all

#define GYRO_SCALE ((2279 * PI)/((32767.0f / 4.0f ) * 180.0f * 1000000.0f)) //(ITG3200 and MPU6050)
...
void getEstimatedAttitude(){
  ...  // some initialisations
  scale = (currentT - previousT) * GYRO_SCALE;

User avatar
EOSBandi
Posts: 802
Joined: Sun Jun 19, 2011 11:32 am
Location: Budapest, Hungary
Contact:

List of problems in Version2.2

Post by EOSBandi »

wrong,
constants are calculated at compile time.

User avatar
Crashpilot1000
Posts: 631
Joined: Tue Apr 03, 2012 7:38 pm

Re: List of problems in Version2.2

Post by Crashpilot1000 »

Hi!
I am currently not flying 2.2 but i see a possible minor problem with the GUI / GPS / PIDS. If you fly gps and see a parameter should be tuned you land and connect to the gui and change the parameter without re-powering and hit write. From what i see in the code "serial" MSP_EEPROM_WRITE is received and a "writeParams" is performed. But the actual gps pids have to be fed into their own floatpoint space before they become active ("GPS_set_pids()") - maybe some "GPS_reset_nav()" might be reasonable as well.
Perhaps the serial MSP_EEPROM_WRITE could look like this:

Code: Select all

...
   case MSP_EEPROM_WRITE:
     writeParams(0);
     headSerialReply(0);
     GPS_set_pids();
     GPS_reset_nav();
     break;
...


I didn't look at the LCD config part. Perhaps it is better to change the "writeParams" part instead of altering the serial part.

Code: Select all

void writeParams(uint8_t b) {
  #ifdef MULTIPLE_CONFIGURATION_PROFILES
    if(global_conf.currentSet>2) global_conf.currentSet=0;
  #else
    global_conf.currentSet=0;
  #endif
  conf.checksum = calculate_sum((uint8_t*)&conf, sizeof(conf));
  eeprom_write_block((const void*)&conf, (void*)(global_conf.currentSet * sizeof(conf) + sizeof(global_conf)), sizeof(conf));
  readEEPROM();
  if (b == 1) blinkLED(15,20,1);
  #if defined(BUZZER)
    alarmArray[7] = 1; //beep if loaded from gui or android
  #endif

  #if defined(GPS)
     GPS_set_pids();
     GPS_reset_nav();
  #endif

}


Without some of theses Options a "hot - alter - GPS pids" seems to be problematic. Otherwise you will always have to powercycle your FC to let the new GPS Pids take effect and some GPS need long for a fix....

Perhaps i am completely wrong, and i stand by to be corrected.
Cheers
Kraut Rob

P.s.: I didn't look at the I2C GPS part ......

Mis
Posts: 203
Joined: Fri Apr 01, 2011 12:23 am

Re: List of problems in Version2.2

Post by Mis »

Look at readEEPROM(); function called from "writeParams"...
....
#if GPS
if (f.I2C_INIT_DONE) GPS_set_pids();
#endif "
....
In this way the GPS pids are setted after writeParams.

User avatar
Crashpilot1000
Posts: 631
Joined: Tue Apr 03, 2012 7:38 pm

Re: List of problems in Version2.2

Post by Crashpilot1000 »

I see. Mis, thanks for the correction! So f.I2C_INIT_DONE is always true. At least this problem exists (existed) in my naze code :) :) ...
Another thing while looking at the gps.ino: Global "static int16_t rate_error[2];" is not necessary. A local int16_t rate_error would do it as well.
Cheers
Kraut Rob

Stars112
Posts: 36
Joined: Wed Jan 30, 2013 9:29 pm

Re: List of problems in Version2.2

Post by Stars112 »

List of Problems:
-------------------
1. WMP with Gyrofailsavecalibration dosen't work.
FIX: In the Sensors.ino at "if(abs(imu.gyroADC[axis] - previousGyroADC[axis]) > 8) tilt=1;" we must have a "If define WMP..." Question or the Value goes from 8 up to 20.
2. With 32U4 the Serial3W LCD dosen't work with Serial1 from 32U4
FIX: open
3. With the OLED at 32U4 the Config-Menu restarts after Exit on some Systems.
FIX: open
4. The Command SEI() in RX bring the 32U4 to Stop with some PPM Receiver (Jeti RMK2, Spektrum).
FIX: Uncomment the SEI() command in RX. http://fpv-community.de/showthread.php? ... -da!/page3 (Post#101)
5. Gyro_Scale for 32u4 is wrong: viewtopic.php?f=8&t=3480
Last edited by Stars112 on Sat May 04, 2013 10:53 am, edited 1 time in total.

albertoLG
Posts: 57
Joined: Fri Sep 07, 2012 8:14 am

Re: List of problems in Version2.2

Post by albertoLG »

I have a problem with the latest dev (1426). Engine start only after half throttle. Better explanation : if I load the firmware, calibrate the sensor, arm the fc, throttle works fine, if I change the value of a switch (assign level to any value for example) then i save the changes and arm again the fc, then the engine will start to run only after half throttle (you can see it in the GUI), it works fine with the 1393.

regards
Alberto

EDIT:
tested again with latest dev1429 and the problem is still there, after I write the eprom to save data the throttle start working after half stick. Crius AIO V1.0
Last edited by albertoLG on Mon May 06, 2013 7:16 am, edited 1 time in total.

Stars112
Posts: 36
Joined: Wed Jan 30, 2013 9:29 pm

Re: List of problems in Version2.2

Post by Stars112 »

List of Problems:
-------------------
1. WMP with Gyrofailsavecalibration dosen't work.
FIX: In the Sensors.ino at "if(abs(imu.gyroADC[axis] - previousGyroADC[axis]) > 8) tilt=1;" we must have a "If define WMP..." Question or the Value goes from 8 up to 20.
2. With 32U4 the Serial3W LCD dosen't work with Serial1 from 32U4
FIX: open
3. With the OLED at 32U4 the Config-Menu restarts after Exit on some Systems.
FIX: open
4. The Command SEI() in RX bring the 32U4 to Stop with some PPM Receiver (Jeti RMK2, Spektrum).
FIX: Uncomment the SEI() command in RX. http://fpv-community.de/showthread.php? ... -da!/page3 (Post#101)
5. Gyro_Scale for 32u4 is wrong: viewtopic.php?f=8&t=3480
6. in the GUI (Load/Save) Feature: Load: the Extension is not in the Filter as default. Save: the Extension must add by your self.

User avatar
bulesz
Posts: 71
Joined: Mon May 06, 2013 8:03 pm
Location: Hungary EU

Re: List of problems in Version2.2

Post by bulesz »

Guys, has the ARM config option bug (SkyNet awakening) issue fixed in the MW 2.2?

I mean this one:

"3. The "ARM" config option is in the GUI moved to the TOP of the config. Direct over the "ANGEL" Option. I startet the Copter in the last 30min. three times on the Table. Why? I clicked in the config on ARM-HIGH and then "WRITE". THE MOTOR STARTED!!!! Without calibrate the Gyros!!! But i dont wont to push the AMR-HIGH. I wont push the ANGEL-HIGH button! The ARM button is on the old ANGEL Position...."

Mentioned here by Stars112:
viewtopic.php?f=8&t=3212&start=20

??

albertoLG
Posts: 57
Joined: Fri Sep 07, 2012 8:14 am

Re: List of problems in Version2.2

Post by albertoLG »

albertoLG wrote:I have a problem with the latest dev (1426). Engine start only after half throttle. Better explanation : if I load the firmware, calibrate the sensor, arm the fc, throttle works fine, if I change the value of a switch (assign level to any value for example) then i save the changes and arm again the fc, then the engine will start to run only after half throttle (you can see it in the GUI), it works fine with the 1393.

regards
Alberto

EDIT:
tested again with latest dev1429 and the problem is still there, after I write the eprom to save data the throttle start working after half stick. Crius AIO V1.0



here is a video of the GUI

http://youtu.be/9RWCyZtAngg

Alexinparis
Posts: 1630
Joined: Wed Jan 19, 2011 9:07 pm

Re: List of problems in Version2.2

Post by Alexinparis »

Hi,

If you plan to use dev after r1391, the setting configuration also changed in GUI, and you must use the last GUI in _shared. (for instance MINCOMMAND config was added)
Otherwise, you could encounter such oddity due to parameter misalignment.



albertoLG wrote:
albertoLG wrote:I have a problem with the latest dev (1426). Engine start only after half throttle. Better explanation : if I load the firmware, calibrate the sensor, arm the fc, throttle works fine, if I change the value of a switch (assign level to any value for example) then i save the changes and arm again the fc, then the engine will start to run only after half throttle (you can see it in the GUI), it works fine with the 1393.

regards
Alberto

EDIT:
tested again with latest dev1429 and the problem is still there, after I write the eprom to save data the throttle start working after half stick. Crius AIO V1.0



here is a video of the GUI

http://youtu.be/9RWCyZtAngg

albertoLG
Posts: 57
Joined: Fri Sep 07, 2012 8:14 am

Re: List of problems in Version2.2

Post by albertoLG »

Alexinparis wrote:Hi,

If you plan to use dev after r1391, the setting configuration also changed in GUI, and you must use the last GUI in _shared. (for instance MINCOMMAND config was added)
Otherwise, you could encounter such oddity due to parameter misalignment.



albertoLG wrote:
albertoLG wrote:I have a problem with the latest dev (1426). Engine start only after half throttle. Better explanation : if I load the firmware, calibrate the sensor, arm the fc, throttle works fine, if I change the value of a switch (assign level to any value for example) then i save the changes and arm again the fc, then the engine will start to run only after half throttle (you can see it in the GUI), it works fine with the 1393.

regards
Alberto

EDIT:
tested again with latest dev1429 and the problem is still there, after I write the eprom to save data the throttle start working after half stick. Crius AIO V1.0



here is a video of the GUI

http://youtu.be/9RWCyZtAngg


thank you Alex... but I'm using the latest multiwiiconf from _trunk, I can't see where or how enable the parameter in the GUI, sorry again...

edit:
nevermind, solved it, thanks
Last edited by albertoLG on Wed May 08, 2013 3:06 pm, edited 1 time in total.

scrat
Posts: 925
Joined: Mon Oct 15, 2012 9:47 am
Location: Slovenia

Re: List of problems in Version2.2

Post by scrat »

Do I need to just download MultiWiiConf.pde from shared and paste it into MultiWiiConf folder and then I'll have the latest MWii GUI or not? I'm on Mac. Thanks.

Alexinparis
Posts: 1630
Joined: Wed Jan 19, 2011 9:07 pm

Re: List of problems in Version2.2

Post by Alexinparis »

No, because the GUI would be not compiled in this case.
The best way to have the last dev GUI is to download a compiled version of the _shared branch here:
https://code.google.com/p/multiwii/downloads/list

scrat
Posts: 925
Joined: Mon Oct 15, 2012 9:47 am
Location: Slovenia

Re: List of problems in Version2.2

Post by scrat »

Thank you. I need to learn how to compile GUI.

edit: I don't see where to set MINCOMMAND in last version of GUI...do I need to set something in config.h or not?

albertoLG
Posts: 57
Joined: Fri Sep 07, 2012 8:14 am

Re: List of problems in Version2.2

Post by albertoLG »

scrat wrote:Thank you. I need to learn how to compile GUI.

edit: I don't see where to set MINCOMMAND in last version of GUI...do I need to set something in config.h or not?


when connected to the FC, you will see 3 tabs
DEFAULT MWII - SETTINGS - MOTORS
in settings you can change the other parameters, if you don't see it you don't have latest Multiwiiconf version
Attachments
multiwii22.png

Phil S.
Posts: 32
Joined: Fri Apr 26, 2013 7:59 am

Re: List of problems in Version2.2

Post by Phil S. »

Alexinparis wrote:No, because the GUI would be not compiled in this case.
The best way to have the last dev GUI is to download a compiled version of the _shared branch here:
https://code.google.com/p/multiwii/downloads/list

Can´t find a _shared branch there, and uncompiled versions only under /svn/

Got another link for us?

Regards, Philipp

scrat
Posts: 925
Joined: Mon Oct 15, 2012 9:47 am
Location: Slovenia

Re: List of problems in Version2.2

Post by scrat »

albertoLG wrote:
scrat wrote:Thank you. I need to learn how to compile GUI.

edit: I don't see where to set MINCOMMAND in last version of GUI...do I need to set something in config.h or not?


when connected to the FC, you will see 3 tabs
DEFAULT MWII - SETTINGS - MOTORS
in settings you can change the other parameters, if you don't see it you don't have latest Multiwiiconf version


Thank you albertoLG.

felixrising
Posts: 244
Joined: Sat Mar 23, 2013 12:34 am
Location: Australia

Re: List of problems in Version2.2

Post by felixrising »

Phil S. wrote:Got another link for us?


This might help: http://www.multiwii.com/forum/viewtopic.php?f=18&t=190

Phil S.
Posts: 32
Joined: Fri Apr 26, 2013 7:59 am

Re: List of problems in Version2.2

Post by Phil S. »

Thank You! But I changed my mind in the meantime, decided to wait for 2.3 final instead of fumbling with the devs. I prefer biking and hanging around at the arfiled at the moment!

Stars112
Posts: 36
Joined: Wed Jan 30, 2013 9:29 pm

Re: List of problems in Version2.2

Post by Stars112 »

List of Problems:
-------------------
1. WMP with Gyrofailsavecalibration dosen't work.
FIX: In the Sensors.ino at "if(abs(imu.gyroADC[axis] - previousGyroADC[axis]) > 8) tilt=1;" we must have a "If define WMP..." Question or the Value goes from 8 up to 20.
2. With 32U4 the Serial3W LCD dosen't work with Serial1 from 32U4
FIX: open
3. With the OLED at 32U4 the Config-Menu restarts after Exit on some Systems.
FIX: open
4. The Command SEI() in RX bring the 32U4 to Stop with some PPM Receiver (Jeti RMK2, Spektrum).
FIX: Uncomment the SEI() command in RX. http://fpv-community.de/showthread.php? ... -da!/page3 (Post#101)
5. Gyro_Scale for 32u4 is wrong: viewtopic.php?f=8&t=3480
6. in the GUI (Load/Save) Feature: Load: the Extension is not in the Filter as default. Save: the Extension must add by your self.[/quote]
7. The Checkboxes to Arm the Motor in AUX1-4 section is to near to the rest checkboxes. So the motor start sometimes with a click to write (viewtopic.php?f=8&t=3212&start=20).

felixrising
Posts: 244
Joined: Sat Mar 23, 2013 12:34 am
Location: Australia

Re: List of problems in Version2.2

Post by felixrising »

Number 5 is incorrect, it is/was wrong for MPU60x0 and some other Gyros - not for any specific MCU. It's now fixed in _shared branch.
Last edited by felixrising on Fri May 17, 2013 1:42 am, edited 1 time in total.

-ralf-
Posts: 215
Joined: Mon Dec 03, 2012 7:08 pm

Re: List of problems in Version2.2

Post by -ralf- »

8. S.Bus is broken

and Felix ....

until there is no ServicePack fpr MultiWii_2.2 it has to stay in the list of bugs ;)

albertoLG
Posts: 57
Joined: Fri Sep 07, 2012 8:14 am

Re: List of problems in Version2.2

Post by albertoLG »

Multiwii 2.2 r1440
FC : Crius v1.1
GPS : u-Blox CN-06 GPS Receiver V2.0
after the boot the GPS Led doesn't flash, it remain always on (very often), checked with the GUI and there is no comunication between FC and GPS. Loaded again the version 2.1 and everything is fine...

regards

felixrising
Posts: 244
Joined: Sat Mar 23, 2013 12:34 am
Location: Australia

Re: List of problems in Version2.2

Post by felixrising »

Alberto, I have the same configuration, works well. Are you sure this is a 2.2 issue? why?

albertoLG
Posts: 57
Joined: Fri Sep 07, 2012 8:14 am

Re: List of problems in Version2.2

Post by albertoLG »

felixrising wrote:Alberto, I have the same configuration, works well. Are you sure this is a 2.2 issue? why?

because reinstalled the 2.1 and the gps works... 2.2 no way, config.h is fine, same parameters for both... I don't know why... I will make a video of my issue....

albertoLG
Posts: 57
Joined: Fri Sep 07, 2012 8:14 am

Re: List of problems in Version2.2

Post by albertoLG »

ok, here is the video

http://youtu.be/5SFqdg99lRA

as you can see the yellow led never flash... you can try maybe 10 times to reboot the FC and then it works... loaded the 2.1 and works fine...

Perry
Posts: 11
Joined: Mon Mar 19, 2012 10:09 pm

VBAT problem

Post by Perry »

Hi, battery monitor does not seem to work well (for me) with the latest versions:
I have:
uncommented
# buzzer

uncommented
# VBAT

made the usual mounting hardware with two resistors of 33 kOhm and 56 kOhm plugging in A3

connected to the LED D8 and ground

when the voltage drops below the first warning level: 10.7 V starts blinking short-long-pause of 2 sec and so on (ok) but...

it remains so blinking even falling below 9 V, without any other change in blinking mode !??

something wrong?

Perry

realpastaman
Posts: 93
Joined: Thu Jan 12, 2012 1:10 am

Re: List of problems in Version2.2

Post by realpastaman »

albertoLG wrote:ok, here is the video

http://youtu.be/5SFqdg99lRA

as you can see the yellow led never flash... you can try maybe 10 times to reboot the FC and then it works... loaded the 2.1 and works fine...


I am having the exact same problem and so maybe this is a bug in 2.2? Resetting the AIOP using the reset switch usually solves it but there seems to be a problem with the initialisation of the GPS? in 2.2?

scrat
Posts: 925
Joined: Mon Oct 15, 2012 9:47 am
Location: Slovenia

Re: List of problems in Version2.2

Post by scrat »

realpastaman wrote:
albertoLG wrote:ok, here is the video

http://youtu.be/5SFqdg99lRA

as you can see the yellow led never flash... you can try maybe 10 times to reboot the FC and then it works... loaded the 2.1 and works fine...


I am having the exact same problem and so maybe this is a bug in 2.2? Resetting the AIOP using the reset switch usually solves it but there seems to be a problem with the initialisation of the GPS? in 2.2?

I have the same setup and everything works fine.

albertoLG
Posts: 57
Joined: Fri Sep 07, 2012 8:14 am

Re: List of problems in Version2.2

Post by albertoLG »

scrat wrote:
realpastaman wrote:
albertoLG wrote:ok, here is the video

http://youtu.be/5SFqdg99lRA

as you can see the yellow led never flash... you can try maybe 10 times to reboot the FC and then it works... loaded the 2.1 and works fine...


I am having the exact same problem and so maybe this is a bug in 2.2? Resetting the AIOP using the reset switch usually solves it but there seems to be a problem with the initialisation of the GPS? in 2.2?

I have the same setup and everything works fine.


we know that it works with some users... the problems is : why doesn't work with me, realpastaman and somebody else? have you loaded some configuration to your gps or is stock? I haven't touched mine. Can you post your GPS section in config.h ? thanks

felixrising
Posts: 244
Joined: Sat Mar 23, 2013 12:34 am
Location: Australia

Re: List of problems in Version2.2

Post by felixrising »

I've always uploaded the config file mentioned here http://www.multiwii.com/forum/viewtopic.php?f=8&t=649&p=35623&hilit=gps+config+txt#p35623 so I can't confirm whether 2.2 is automagically configuring mine..

albertoLG
Posts: 57
Joined: Fri Sep 07, 2012 8:14 am

Re: List of problems in Version2.2

Post by albertoLG »

update:
loaded the config file to my GPS http://ardupilot-mega.googlecode.com/gi ... -Ublox.txt and now everything is ok, tried several times with the 2.2 and GPS initialization is fine... so realpastaman, send the config file to the gps as described here http://code.google.com/p/arducopter/wiki/UBlox

regards

realpastaman
Posts: 93
Joined: Thu Jan 12, 2012 1:10 am

Re: List of problems in Version2.2

Post by realpastaman »

albertoLG wrote:update:
loaded the config file to my GPS http://ardupilot-mega.googlecode.com/gi ... -Ublox.txt and now everything is ok, tried several times with the 2.2 and GPS initialization is fine... so realpastaman, send the config file to the gps as described here http://code.google.com/p/arducopter/wiki/UBlox

regards


albertoLG - Thanks you genius! I have just what you suggested and its all fine now! Thanks so much for your help :)

felixrising wrote:I've always uploaded the config file mentioned here http://www.multiwii.com/forum/viewtopic.php?f=8&t=649&p=35623&hilit=gps+config+txt#p35623 so I can't confirm whether 2.2 is automagically configuring mine..


felixrising - Thanks also - It seems 2.2 does not automagically configure well?

scrat
Posts: 925
Joined: Mon Oct 15, 2012 9:47 am
Location: Slovenia

Re: List of problems in Version2.2

Post by scrat »

@albertoLG: I didn't touched my gps. It is stock.

Stars112
Posts: 36
Joined: Wed Jan 30, 2013 9:29 pm

Re: List of problems in Version2.2

Post by Stars112 »

List of Problems:
-------------------
1. WMP with Gyrofailsavecalibration dosen't work.
FIX: In the Sensors.ino at "if(abs(imu.gyroADC[axis] - previousGyroADC[axis]) > 8) tilt=1;" we must have a "If define WMP..." Question or the Value goes from 8 up to 20.
2. With 32U4 the Serial3W LCD dosen't work with Serial1 from 32U4
FIX: open :oops:
3. With the OLED at 32U4 the Config-Menu restarts after Exit on some Systems.
FIX: open :oops:
4. The Command SEI() in RX bring the 32U4 to Stop with some PPM Receiver (Jeti RMK2, Spektrum).
FIX: Uncomment the SEI() command in RX. http://fpv-community.de/showthread.php? ... -da!/page3 (Post#101)
FIX: Current DEV ;)
5. Gyro_Scale for 32u4 is wrong: viewtopic.php?f=8&t=3480
FIX: Current DEV ;)
6. in the GUI (Load/Save) Feature: Load: the Extension is not in the Filter as default. Save: the Extension must add by your self.
FIX: open :oops:
7. The Checkboxes to Arm the Motor in AUX1-4 section is to near to the rest checkboxes. So the motor start sometimes with a click to write (viewtopic.php?f=8&t=3212&start=20).
FIX: open :oops:
8. S.Bus is broken (viewtopic.php?f=8&t=3580)
FIX: open :oops:
9. Vbat warning level 3 dosent work.
Fix: Current dev. ;)

scrat
Posts: 925
Joined: Mon Oct 15, 2012 9:47 am
Location: Slovenia

Re: List of problems in Version2.2

Post by scrat »

albertoLG wrote:update:
loaded the config file to my GPS http://ardupilot-mega.googlecode.com/gi ... -Ublox.txt and now everything is ok, tried several times with the 2.2 and GPS initialization is fine... so realpastaman, send the config file to the gps as described here http://code.google.com/p/arducopter/wiki/UBlox

regards


As far as I know ublox file made for arducopter sets baudrate to 38400 and not 115200?

albertoLG
Posts: 57
Joined: Fri Sep 07, 2012 8:14 am

Re: List of problems in Version2.2

Post by albertoLG »

scrat wrote:
albertoLG wrote:update:
loaded the config file to my GPS http://ardupilot-mega.googlecode.com/gi ... -Ublox.txt and now everything is ok, tried several times with the 2.2 and GPS initialization is fine... so realpastaman, send the config file to the gps as described here http://code.google.com/p/arducopter/wiki/UBlox

regards


As far as I know ublox file made for arducopter sets baudrate to 38400 and not 115200?


I never said it set at 115200, I said that now the GPS initialization with the MW2.2 is fine... the GPS default speed is at 38400 (I use 57600 in the config.ino) and the default protocol is UBLOX

scrat
Posts: 925
Joined: Mon Oct 15, 2012 9:47 am
Location: Slovenia

Re: List of problems in Version2.2

Post by scrat »

I know you neber said this. I'm just asking.

User avatar
bulesz
Posts: 71
Joined: Mon May 06, 2013 8:03 pm
Location: Hungary EU

Re: List of problems in Version2.2

Post by bulesz »

Guys, I have this NEO-6M GPS module and in the config.h using this settings (it was set by default):
#define GPS_BAUD 115200
It has locked satelites but the GPS HOME and GPS HOLD don't seem to be working. Could be because of improper the baud rate setting in my config.h?
Should I use the 57600 instead?
if yes should I change this " #define SERIAL2_COM_SPEED 115200 " too to 57600?

Many thanks,
B

zwiebacksaege
Posts: 27
Joined: Thu Mar 07, 2013 10:14 am

Re: List of problems in Version2.2

Post by zwiebacksaege »

I noticed, that my settings for the AUX definitions where not stored when saving the settings. Anyone else got this?

Post Reply