its either a poor gps fix, or imagery in your area is realy out.
But the same SIFR II GPS positioning RIGHT in MegapirateNG,Maybe In APM2 settings something wrong...
MPNG 2.6 R5 uses different NMEA library due to GPS error in original lib.
This issue described at http://code.google.com/p/ardupilot-mega/issues/detail?id=416&q=gps
We uses latest Greg Nash's library version.
When I replace AP_GPS_NME.h and AP_GPS_NMEA.CCP in AP_GPS , flash the 2.6 firmware,an error :
ArduCopter:254: error: cannot declare variable 'g_gps_driver' to be of abstract type 'AP_GPS_NMEA'
C:\Users\Monchhichi\Documents\Arduino\libraries\AP_GPS/AP_GPS_NMEA.h:52: note: because the following virtual functions are pure within 'AP_GPS_NMEA':
C:\Users\Monchhichi\Documents\Arduino\libraries\AP_GPS/GPS.h:87: note: virtual void GPS::init(GPS::GPS_Engine_Setting)
How to solve?
Greg version is not ready for 2.6, Try my version from MPNG, www.siralex.info/files/AP_GPS.ZIP
Thank you very much, use your file to replace the the original file, and reflash arducopter 2.6 again , MAVLINK1.0 connect to Mission Planner 1.196, that the positioning normal .
But after update firmware,GPSHDOP this value reach 179X, is this normal?
HDOP reported by GPS and depends on Sat count and signal quality...
What is 179X ?
GPSHDOP=1790 OR 1794.....
Have you compared the position reported by the GPS with a real GPS? As Michael said, could just be the imagery in your area, but I've never seen anything that bad. Man, I thought 10m was a lot...
the only other thing i can think of is the nmea mode driver changed recently
The problem is that the same GPS in MegapirateNG any version of firmware positioning in Mission Planner are correct, but the GPS switch to APM2 arducopter 2.6 firmware on a positioning offset, I don't understand what's wrong.I have modify the GPS baudrate 4800 in 2.6 firmware at SYSYTEM.INO , do not know where also need to modify?