

dramida wrote::) i won't be so shure
Thanks for catching it... will update the repo soon... but first I have to finish my cinestar 8 build... i suppose it will be the first MultiWii powered cinestar
Crashpilot1000 wrote:Thanks for catching it... will update the repo soon... but first I have to finish my cinestar 8 build... i suppose it will be the first MultiWii powered cinestar
Hi, Eos!
Why not, at least mwii is more relieable than most other platforms. You will have no fly-aways.
Right now I am doing some serious copy/paste action with your current mwii gps code (http://code.google.com/p/multiwii/sourc ... 321&r=1321) and the naze32/baseflight soft. By doing this i stumbled across a few things.
- The GPS_calc_nav_rate function now deals with unsigned int16 (before: GPS_calc_nav_rate(int16_t max_speed); now: GPS_calc_nav_rate(uint16_t max_speed)) but the "speed" variable in the main gps loop is still a signed int16. Is that correct or a possible source of problems?
- The naze could do "double" floats, do you have a part of your gps code in mind, wich could benefit from that?
Cheers
Kraut Rob
Code: Select all
...
#elif defined(INIT_MTK_GPS) // MTK GPS setup
...
#if defined(NMEA)
Serial.write(MTK_SET_NMEA_SENTENCES); // only GGA and RMC sentence
#endif
...
#endif
Code: Select all
...
lastframe_time = millis();
if ((i2c_dataset.status.gps3dfix == 1) && i2c_dataset.status.numsats >= 5) {
...
Code: Select all
////////////////////////////////////////////////////////////////////////////////////
// Get distance between two points in cm
// Get bearing from pos1 to pos2, returns an 1deg = 100 precision
void GPS_distance_cm_bearing(int32_t* lat1, int32_t* lon1, int32_t* lat2, int32_t* lon2,uint32_t* dist, int32_t* bearing) {
float dLat = *lat2 - *lat1; // difference of latitude in 1/10 000 000 degrees
float dLon = (float)(*lon2 - *lon1) * GPS_scaleLonDown;
*dist = sqrt(sq(dLat) + sq(dLon)) * 1.113195;
*bearing = 9000.0f + atan2(-dLat, dLon) * 5729.57795f; //Convert the output redians to 100xdeg
if (*bearing < 0) *bearing += 36000;
}
alexia wrote:i neeed you help
this thread is so big so it s difficult to find everything..
i have crius aio pro and crius v2 gps
i am going to upload latest dev
http://code.google.com/p/multiwii/downl ... p&can=2&q=
could you help me to comment the right thing for my gps
does i need to change my baud rate?
i hope you could help me
Code: Select all
#define GPS_LEAD_FILTER
crono wrote:I activate the GPS on quadricopter starts to oscillate as fast as ever on what value I have to fix? pid?
mahowik wrote:crono wrote:I activate the GPS on quadricopter starts to oscillate as fast as ever on what value I have to fix? pid?
Have the same issue with lead filter, i.e. when GPS_LEAD_FILTER define activated... When GPS_FILTERING activated, issue is gone..
KeesvR wrote:I have a Flytron Navigator V1 GPS.
I'm trying to get my GPS working with binary protocol, but it's not working.
I've flashed the gps with 1.9 firmware.
With Minigps set it to 115200 and 10hrz also tried 5hrz.
With NMEA protocol it's working fine, but with Binary protocol I see nothing in the GUI.
What am I doing wrong, or is it not possible with my GPS ?
What are the settings for I2C GPS Config.H and MultiWii Config.H ?
Thanks.
Kayle wrote:Hello,
i use i2c nav board mit the newest firmware and a PA6C Global Tec GPS. GPS is set to 115k2, 10Hz, NMEA. In GUI i get 3D FIX with 7 SATS. But ALT is shown as "113m". This can´t be correct. ALT is in my tests only 3m. Why shows multiwii 113m ? Can someone help me ?
Kayle
EOSBandi wrote:Kayle wrote:Hello,
i use i2c nav board mit the newest firmware and a PA6C Global Tec GPS. GPS is set to 115k2, 10Hz, NMEA. In GUI i get 3D FIX with 7 SATS. But ALT is shown as "113m". This can´t be correct. ALT is in my tests only 3m. Why shows multiwii 113m ? Can someone help me ?
Kayle
Are you live in Netherland ? GPS alt is MSL alt....
scrat wrote:Hi guys.
Is this still valid for uBlox GPS from rctimer v2?
from config.h file MWii v2.2 - UBLOX - U-Blox binary protocol, use the ublox config file (u-blox-config.ublox.txt) from the source tree
Thanks.
scrat wrote:scrat wrote:Hi guys.
Is this still valid for uBlox GPS from rctimer v2?
from config.h file MWii v2.2 - UBLOX - U-Blox binary protocol, use the ublox config file (u-blox-config.ublox.txt) from the source tree
Thanks.
EOSBandi neighbourpliz help me with this answer.
scrat wrote:Thanks for answer.
But I just want to know if I still need to upload this file to my GPS with MWii v2.2 or not because GPS on my quad works pretty good.
crashlander wrote:scrat wrote:Thanks for answer.
But I just want to know if I still need to upload this file to my GPS with MWii v2.2 or not because GPS on my quad works pretty good.
After 2.1 Eos and Alex implemented full NEO configuration directly into MWII (serial version at least). It means no additional configuration of NEO modules are necessary.
Regards
Andrej
snowzach wrote:scrat wrote:scrat wrote:Hi guys.
Is this still valid for uBlox GPS from rctimer v2?
from config.h file MWii v2.2 - UBLOX - U-Blox binary protocol, use the ublox config file (u-blox-config.ublox.txt) from the source tree
Thanks.
EOSBandi neighbourpliz help me with this answer.
Yes, that's probably still true. From within the uBlox control center there's an option where you can send a GPS config.
I know there is this one: http://code.google.com/p/i2c-gps-nav/source/browse/trunk/I2C_GPS_NAV/u-blox-config.ublox.txt
It basically tells the GPS to send at 115200, uBlox binary format.
alll wrote:I played for the first time with UBlox GPS rc-timer v1 (without eeprom). I uploaded the configuration file to it u-blox-config.ublox.txt
Is this one also valid?
http://diydrones.com/xn/detail/705844:Comment:1222521
Thanks,
manu
#define UBLOX
Code: Select all
#define GPS_BAUD 57600
felixrising wrote: recommendation was 10Hz for the uBlox NEO-6m stuff....