Absolutely. I know exactly what's going on. The ArduPilot, ArduIMU and APM protocols all are missing data. They have no variable for GPS lock, nor satellite count, nor HDOP, nor GPS time. It also depends upon the version of the MediaTek you're using. If you flashed it with 1.6 then I can't say for sure that the GPS parsing is working 100% on the APM yet. I would take a look at the serial data coming across in the Serial Data window.
Drift of lat and long is not a function of my GPS...I just display what I'm getting. Knowing how many sats you're connected to would be very helpful...but at the moment they are not included in any ArduPilot data stream to the best of my knowledge. The bigger issue is the lack of GPS data coming out of the telemetry port when there is no GPS lock. I am lobbying for a fundamental change in the way this works as any loss of GPS lock will mean the GCS user is in the dark.
If you want the number of satellites now add the following to GSC_Ardupilot tab then under the void print_position
I add it just before the following line
Working on Fix at the moment
I've got this program working with my Ardupilot with the exception of the battery voltage. It reads over 100,000 volts. Voltage reads fine with the original Ardupilot GCS. Is this a setup/configuration problem?
There must have been a change to the ArduPilot GCS output at some point. Are you using the "Legacy" output? Where it's !!!LAT:XXXXX, etc or are you using a binary output?
If it's legacy, take a look at the output .pde file (it's been renamed several times) and look at the BTV: output. Make sure it's sending a non-scaled value. So 12.41 = 12.41. You might have something *1000 so the output is scaled way up.
Irvin, please email it to firstname.lastname@example.org
I'm planning on re-vamping the mission load/save function. I just edited the code to get by for now...my plan is to make a universal file format that I can use on my GCS to load and save in just my GCS or output in a file type for a specific auto pilot..