Replies to This Discussion

Permalink Reply by Theodoros Bakoyiannis on January 23, 2012 at 7:02am

I have to say that the GPS is in 38400 baud by default.

Permalink Reply by jalves on January 23, 2012 at 7:28am

Teo,

What are you trying to do with the Ap?

Permalink Reply by Theodoros Bakoyiannis on January 23, 2012 at 7:38am

Nothing that has not been done.

I want to use it in a FPV plane for Stabilization and Return To Launch.

I made a flight with it and the Stabilization is working just fine.

The problem is that i can't get a Sat Lock so as to use the RTL feature.

Permalink Reply by jalves on January 23, 2012 at 9:05am

I am not using the shield, only the bare alone Ap board, and it is working well 90% of the time (RTL...).

But I remember to read something in the past that the shield has some problem related to the gps fix.

Try to do a search or else remove the shield and connect the gps directly to the Ap board.

Permalink Reply by Theodoros Bakoyiannis on January 23, 2012 at 9:53am

I have already done that.
I removed the Shield but without luck.
Still the same thing.
No Sat Lock.
I was wondering if there is something in the code that needs to be changed that is not mentioned in the tutorial of the link that i have posted on the top.

Permalink Reply by jalves on January 23, 2012 at 11:08am

Are you using #define GPS_PROTOCOL 0 in Ap_Config.h   ?

I notice you wrote above GCS_PROTOCOL , and this the define telemetry data to ground station

Permalink Reply by Theodoros Bakoyiannis on January 23, 2012 at 11:51am

GPS_PROTOCOL is set to 0 (NMEA)

Something strange is that when

GCS_PROTOCOL is set to 0 the SAT LOCK led is not blinking at all!!!!!!!!

But when

GCS_PROTOCOL is set -1 then the SAT LOCK led is blinking but never get a LOCK!!.

Can't find anything about such a problem.

Permalink Reply by jalves on January 23, 2012 at 3:50pm

Teo,

Check the gps connection to the Ap board.

Upload a different sketch (try 1. basics --> blink) and see the Ap led blink, if it does, then the mcu is ok (IIRC this was a check method I use in the past...)

 

Connect the locosys to the PC through a serial usb and check if the gps is working (NMEA sentences and if it fixes in the same place you are trying to fix the Ap)

Do a Y connector and connect the gps output to the Ap AND to the PC and see what the gps is feeding to the Ap (check baud rate, etc)

upload a 2.1 sofware version and see if this solve the problem.

Download fresh software from the repository and start from the beginning, follow the DIYdrones instructions and report back.

 

GSC_PROTOCOL shouldn't have any influence over the gps data treatment by the Ap, only have to do with the Ap output to the GS (I personally use -1 to cut all because I don't use it).

I am using MTK gps with mine, it works with 2.7 NMEA and binary mode.

Permalink Reply by Theodoros Bakoyiannis on January 23, 2012 at 3:55pm

I have checked the GPS module and it uses 38400 baud and i have also plugged it in a FY21-AP and it got a lock in 20-30 seconds.

So you say i should go back to 2.1 firmware?

Still if i change the GCS_PROTOCOL (from -1) the sat led stop blinking!!!!

When left outside working the Blue Led will blink and every minute or so will stay solid for few seconds and start blinking again!!!!

Permalink Reply by jalves on January 23, 2012 at 4:14pm

Hypothesis: The behaviour of the led may mean the software isn't understand fully the gps sentences, thus the intermittent behaviour.

Try an older version to see if the situation improves.

I think it's time to do some detective work...

Do you have another Ap board to try?

Permalink Reply by Theodoros Bakoyiannis on January 23, 2012 at 5:30pm

Probably i have to do that. I will start with 2.4 then and see from there.

Thank you

Permalink Reply by Theodoros Bakoyiannis on January 24, 2012 at 7:47am

Tried all firmwares from 2.4 to 2.7.1 which i think is the latest and nothing.

Actually in 2.7.1 everytime i select the NMEA in the GPS_PROTOCOL i get no flashing blue led at all anymore.

If i choose any onter protocol the led flashes.

Why my board is not accepting NMEA at all.

I rechecked the GPS module on a different autopilot (FY21ap) and it locks in 30 seconds.

The GPS is working and i have it connected in the vertical pins in front of the uBlox connector GND to -, 3V to Vc and IN to Tx.

I even used another GPS module of the same company also NMEA and nothing.

ANY help?

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