When i upload the code, a have to connect the jumper (d6 and d7) and then the blue led starts to blink. When the GPS doesn´t have signal (like indoor) the blinks remains forever. When it get´s signal, the blue led stops blinking but the Mux led powers On and the Blue Led is Off.
If when the Blue led is blinking i remove the jumper, and after a couple of seconds i reset the Ardupilot, the blue led powers On (without blinking), and the GPS works like a charm.
Even if i disconect the batery and after a couple of seconds i conect the batery, the GPS remains working.
I test with the FTDI cable, and without the Ftdi Cable, the result is the same.
With the 2.1 software, the blue LED blinking means that it's waiting for GPS lock. For the first time using a GPS in an area that can take as much as 15 minutes. I'd leave it outside for that long and see if the GPS locks and the blue LED goes solid. I
I bought the Ardupilot from the sparkfun, with GPS and the FTDI cable. When i first powered on the Ardupilot, the threee Leds blinks in sequential (i think it's the "firmware" factory). In the page of the Ardupilot, we have to plug first the GPS, then disconect and then upload the Ardupilot firmware. I didn´t do that, i upload the ardupilot (with the GPS disconected) and then plug in the GPS.
But now, the blue led doesn't blink. I tried to upload with the Ardupilot 2.1 firmware, and plug the jumper in D6 and D7. Now the blue leds, starts to blinks but it remains blinking.
My question is, the firmware from sparkfun, configures the GPS? Why my GPS isn't getting lock what i'm doing wrong?
Comments
When i upload the code, a have to connect the jumper (d6 and d7) and then the blue led starts to blink. When the GPS doesn´t have signal (like indoor) the blinks remains forever. When it get´s signal, the blue led stops blinking but the Mux led powers On and the Blue Led is Off.
If when the Blue led is blinking i remove the jumper, and after a couple of seconds i reset the Ardupilot, the blue led powers On (without blinking), and the GPS works like a charm.
Even if i disconect the batery and after a couple of seconds i conect the batery, the GPS remains working.
I test with the FTDI cable, and without the Ftdi Cable, the result is the same.
Is this strange, or not really?
Many thanks
With the 2.1 software, the blue LED blinking means that it's waiting for GPS lock. For the first time using a GPS in an area that can take as much as 15 minutes. I'd leave it outside for that long and see if the GPS locks and the blue LED goes solid. I
Well that's happens to me, if i don't remove the FTDI cable.... Or something is obstruction the serial communication.
Unless you fuselage is carbon fiber or aluminum/titanium you can leave it inside...
I bought the Ardupilot from the sparkfun, with GPS and the FTDI cable. When i first powered on the Ardupilot, the threee Leds blinks in sequential (i think it's the "firmware" factory). In the page of the Ardupilot, we have to plug first the GPS, then disconect and then upload the Ardupilot firmware. I didn´t do that, i upload the ardupilot (with the GPS disconected) and then plug in the GPS.
But now, the blue led doesn't blink. I tried to upload with the Ardupilot 2.1 firmware, and plug the jumper in D6 and D7. Now the blue leds, starts to blinks but it remains blinking.
My question is, the firmware from sparkfun, configures the GPS? Why my GPS isn't getting lock what i'm doing wrong?
Many thanks
I didn´t connect the GPS with the firmware fom factory. I upload the code directly, but now i can get the lock in the GPS.The blue led doesn´t blink.
The firmware from factory,configures the GPS? if so what can i do now?
Many thanks
-
40
-
41
-
42
-
43
-
44
of 62 Next