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...
quadwalker wrote:HI Dramida
From my side, using 115200b and 10hz seems to be working.
Code: Select all
const unsigned long baudrates[5] = {9600U, 19200U, 38400U, 57600U};
...
for (uint8_t i=0; i<5; i++) {
Code: Select all
for (uint8_t i=0; i<sizeof(baudrates); i++) {
Code: Select all
#define GPS_BAUD 115200 //can be 57600 or 115200
#define GPS_RATE 100 //can be 100ms for 10Hz or 200ms for 5hz
brettwal wrote:Looks like it works for the Ublox LEA-6 module on the Crius Extend board as well.
Don't forget to change the SBAS setup in GPS.ino for you area of the world. Also remember, that altitude is set to centimeters, not meters in this version.
nhadrian wrote:EDIT.: I tested with my LEA-6H in my Crius ext. board, looks like it's not working... nothing serial from GPS. Changing back to 58600 it works.
For ALT hold sensitivity, change this value in config.h:
#define ALT_HOLD_THROTTLE_NEUTRAL_ZONE 20
I'm using my copter with 80 value instead of 20.....
quadwalker wrote:For those who would like to test using UBLOX Neo 6m at 115200/10hz, here the GPS.ino attachment file modified
As my Neo 6m gps seems supporting this rate, let's have a try from you side if you wish
The GPS.ino was modified to scan 115200 as well during the the GPS init phase to setup the binary mode if ever your GPS should be in that default speed
I think it is also fixing a bug in the scan loop to setup the binay mode. The loop is looking one element behind the end of the baudrates array. Only 4 elements in the array and then 0 to 4 is too much.Code: Select all
const unsigned long baudrates[5] = {9600U, 19200U, 38400U, 57600U};
...
for (uint8_t i=0; i<5; i++) {
If you prefer to keep using the actual GPS.ino, it will be better to replace 5 by 4 or again better by sizeof(baudrates)Code: Select all
for (uint8_t i=0; i<sizeof(baudrates); i++) {
Using the new GPS.ino, you will have to add a new define statement GPS_RATE in config.h in the GPS section.Code: Select all
#define GPS_BAUD 115200 //can be 57600 or 115200
#define GPS_RATE 100 //can be 100ms for 10Hz or 200ms for 5hz
Hope that wil help and will be working from your side
have fun
nhadrian wrote:you mean it mooves up-down too much when poshold is active not only alt hold?
Are you using this and have the ublox with the pins 13,14 and 15 soldered?
I changed the I2C sketch to perform the same and so far the only remaining issue is the damm GPS not starting at first try.
quadwalker wrote:Are you using this and have the ublox with the pins 13,14 and 15 soldered?
I changed the I2C sketch to perform the same and so far the only remaining issue is the damm GPS not starting at first try.
Hi iceWind.
I only have pins 13 & 14 soldered together. Pin 15 remains unchanged. My GPS is a Neo 6m from rctimer
dramida wrote:It seems that serial GPS is not so-well supported as I2C navi GPS.
Today i had hard times trying to make ublox gps neo 6m working. the leds were flashing but the GUI arrow did not flash.
I even tried MT3329 gps and this one worked sporadically as if it worked 1 second and then shutted off and after another 5 seconds worked again...and off again...
My last hope is to try I2C navi board, even it seems to be over my shoulder as i use a mega board with 3 spare serial ports.
nhadrian wrote:Hi quadwalker,
EDIT.: I tested with my LEA-6H in my Crius ext. board, looks like it's not working... nothing serial from GPS. Changing back to 58600 it works.
For ALT hold sensitivity, change this value in config.h:
#define ALT_HOLD_THROTTLE_NEUTRAL_ZONE 20
I'm using my copter with 80 value instead of 20.....
But be careful, once you'll reach the neutral zone with the stick, it'll became as sensitive as now!!! It's because of the current ALT hold code behaviour. I posted a solution in another topic for compensating angle in LEVEL/ALT hold. For better alt hold behaviour you should try if you would like.
BR
Adrian
PS.: GPS altitude is not used for any purposes in the MWI.
brettwal wrote:nhadrian wrote:Hi quadwalker,
EDIT.: I tested with my LEA-6H in my Crius ext. board, looks like it's not working... nothing serial from GPS. Changing back to 58600 it works.
For ALT hold sensitivity, change this value in config.h:
#define ALT_HOLD_THROTTLE_NEUTRAL_ZONE 20
I'm using my copter with 80 value instead of 20.....
But be careful, once you'll reach the neutral zone with the stick, it'll became as sensitive as now!!! It's because of the current ALT hold code behaviour. I posted a solution in another topic for compensating angle in LEVEL/ALT hold. For better alt hold behaviour you should try if you would like.
BR
Adrian
PS.: GPS altitude is not used for any purposes in the MWI.
I have the Crius AIO and extend board with LEA-6 and its working for me. 57,600 10Hz or 5Hz & 115,200 10Hz or 5Hz It does take a good 20 seconds or so from boot for data to show in the GUI
dramida wrote:What software version are you using in those working GPS Ublox setups? Right now are 3 software setups that claims they work in ublox GPS:
...
The only method i tried was 1-by Bandy and i had serious trouble: .
dramida wrote:I found that at first power up after a period of innactivity, Ublox neo 6M gps from Rctimer sends an error message instead of data and halts. This error message is related to low voltage of backup memory cell battery.
That's why it is better to power the board, wait for a couple of seconds, unplug and immediately plug the battery again. For me is working this method every time.
quadwalker wrote:Hello
When PosHold and AltHold are activated, do you have your position well kept?
In my case, my quad is flying slowly to the left, mostly 5 or 10m from the position I activivated then he is coming back to the position wanted but staring again going back to the left and backward as well. After 2/3, the way to come back to the wanted position is done more and more in an acrobatic way
Do you have the same behavior?
Did I miss to activate something? what are the falg I may want to enable for POSHold feature?????
thanks
dramida wrote:Have you used IMU data in position hold error function? In this way the copter would react even at the slightest lateral acceleration.(DJI does this way)
pm1 wrote:dramida wrote:Have you used IMU data in position hold error function? In this way the copter would react even at the slightest lateral acceleration.(DJI does this way)
No, it was not neccessary. I tried exactly this for altiude hold, but it didn`t work. With the integration I got so such an drift, that it was worse than before.
dramida wrote:What software version are you using in those working GPS Ublox setups? Right now are 3 software setups that claims they work in ublox GPS:
1-Alex made on R1014 the integration of Ublox neo 6M with binary 5Hz (you have to solder pins 13, 14, 15) viewtopic.php?f=8&t=2166&start=10#p20105
2-EosBandi did some code mods witch were not published in shared trunk.http://www.multiwii.com/forum/viewtopic.php?f=8&t=2166#p20097
3- Quadwalker did some straight forward coding and claims it works at 10Hz refresh http://www.multiwii.com/forum/viewtopic.php?f=8&t=2166&start=40#p20569
The only method i tried was 2-by Bandy and i had serious trouble: In NMEA mode with an MT3329 GPS- disaster struck! it works sporadicly. If Ublox neo6m used, it works sporadicly, also leds are flasking, the GUI dosen't show data. Also some time works, some times, it dosen't. And i presume the missing #endif statament from Bandi's code is after SerialOpen function.
Code: Select all
for (uint8_t i=0; i<5; i++) {
Code: Select all
for (uint8_t i=0; i<4; i++) {
Code: Select all
SerialOpen(GPS_SERIAL,57600);
Code: Select all
SerialOpen(GPS_SERIAL,GPS_BAUD);
Code: Select all
msg.measure_rate_ms = 200;
Code: Select all
msg.measure_rate_ms = GPS_RATE;
Code: Select all
#define GPS_BAUD 57600
#define GPS_RATE 200
Woppit wrote:Hi All, anyone seen this?
http://www.goodluckbuy.com/crius-cn-06-gps-receiver-v2-0-module.html
vpb wrote:
Still dont know why I cannot config my gps to work at 10hz/115200 with quadwalker's instruction, (solder pin 13&14&15, 13&14, de-solder all, solder & desolder battery ), maybe I'll try again sometimes. Thank EOSBandi & quadwalker!
vpb wrote:About POS HOLD with GPS, just one time I saw it's nearly locked to one position (with baro, ofcourse), all other tests showed that it went around about 1-4m. I intend to do POS HOLD PID tuning explained in EOSBandi document.
The RTH feature works great!
vpb wrote:Do you think the ublox should be covered against the sun light?
dramida wrote:RCTimer put an I2C EEPROM to GPS Ublox NEO 6M at 27$. In this way GPS configuration settings will be permanent.
http://www.rctimer.com/index.php?gOo=go ... oductname=
quadwalker wrote:I am going to have a try by doing the same protection on the baro
what Camera are you using? The image is not bad at all!
thanks a lot for the tips
EOSBandi wrote:OK, here is a first version : I dont commit it into shared yet, since it is based on a 2.1 Gps.ino and still uses classes.
Just replace the Gps.ino and add the follwing lines to config.h gps partCode: Select all
//#define NMEA
#define UBLOX
// #define MTK
#define GPS_LEAD_FILTER
//#define GPS_FILTERING
//#define NAV_SLEW_RATE 30
Plus add the initialisation to the multiwii.ino setup()Code: Select all
#if defined(GPS_SERIAL)
#if defined(UBLOX)
UBLOX_init();
delay(200);
#endif
#if defined(MTK)
MTK_init();
delay(200);
#endif
SerialOpen(GPS_SERIAL,GPS_BAUD);
For UBLOX and MTK the GPS_BAUD must be 57600