Replies to This Discussion

Permalink Reply by Bertrand Duchiron on May 24, 2011 at 2:55pm

Usually I use a TP 5000mAh 3S (the same I put on my plane) when I test the whole system with all servos connected  but I also tested with a Lifesource 1300mAh 6.6V  without any servos (only APM, Magnetometer,Telemetry, GPS, Pitot and RX or BEC).

When I used 4.8V, the GPS light was somtetimes dim and the APM seem to be mad, the Artifiical horizon was turning all around even if the APM was sitting on a flat table and no GPS lock even after 10min  First I thought a hardware problem but when I used the USB to check all was normal so I connect my 'big' LIPO+ESC+RX to the APM and all went good, good GPS, no more madness. This is why I didn't use any more 4.8V battery.

 

Did you try to put a toroid ring around the GPS cable? maybe there is EMI with the 2.4Ghz

 

• ▶ Reply

Permalink Reply by Nikos Gerarchakis on May 26, 2011 at 1:15pm

Hi Happy K and Bertrant ,  today i decide to test old versions of HK GCS .

So after many test , finaly i setup the version 1.2.39. and observe the followings

1. When i start up with the auto mode enable , the GCS ( with 4 sats) display the cordinates .
2. When I switch to manual mode, and restart the program ( without to turn off the APM) the readings are normal.
3. The flight instruments has normal display.

Finally i test the Qground Control , with the same sequence ( auto and then manual mode) and the readings and GPS was Normal.

The battery for both tests was a   4.8 V Nimh fully charged.

I try again with latest version of HK GCS , but nothing happened

I want to use the Happy Ks GCS, because is light and simple to use

Any more help would be much appreciated.

Attachments:

• hp_gcs_v1-2-39.jpg, 246 KB
• qgroundcontrol.jpg, 225 KB

• ▶ Reply

ModeratorPermalink Reply by Paul Mather on May 26, 2011 at 1:44pm

The trouble is the GPS Fix value. If you look in the serial window, you'll see Fix=0. This means according to MAVlink, you do not have GPS fix. I'm actually getting a 1 from MAVlink since internally nFix = MAVlink's variable -1 so a value of 1 = 0 internally....which means no fix.

 

If you look at GPS_RAW #32 here http://pixhawk.ethz.ch/wiki/mavlink/ you'll see that a 0 or 1 for fix type = no fix. I was probably handling it wrong in 1.2.39 and have since corrrected it to match the correct protocol spec. Your GPS is acting as I would expect since GPS lock does not happen until Satellites = 5. You're showing 4 so that is not GPS lock. You may be getting valid GPS data but the GPS unit itself has not reported the GPS lock signal and the blue light on your MediaTek board will still be flashing at this point. You must wait until the blue light is solid before you have GPS lock.

• ▶ Reply

• ‹ Previous
• 1
• 2
• Next ›
• Page