Hello again! I'm not so good making intros, so imagine you just read a long and well redacted introduction of why uBlox (the best GPS ever) is so difficult to find and interface with (Specially the SparkFun version). So let's go to the point. ;-)If you are beginner please don't try to make this.Fallow this pictures in order to make the wiring (hurry!):
And this is an example of how to connect it to ArduShield, but you must configure the unit first! So continue reading for instructions.
You will need to configure uBlox module using U-center, only have to do it once, the settings will remain in the EEPROM forever. Download U-center from here and install it:http://www.ublox.com/en/evaluation-kits/u-center/u-center.htmlMake sure you supply the unit with 3.3V and interface it using the FTDI cable. When you are able to see real time data with U-center, you are ready to proceed. Click here for a u-Center user guide.Now UBX has 8 Message Class, we only use "Class 0x01" called "NAV":
Each class has "Messages ID's", we only need 3 ID's of "Class 0x01", the ones marked with blue:
If you need more information about uBlox protocols please download this uBlox_Protocol_Specification.pdf.Everything else must be disabled. Now that you know what we are trying to do, lets go with a more detailed instructions:Go to Message View by pressing F9 (menu View->messages view):
(I'm using Paparazzi instructions but modified).1. Right Click on the NMEA Text on top of the tree and choose disable child messages2. Choose UBX->CFG->NAV5(Navigation 5) - set it to use Airborne 8 <4G. This tells the Kalman filter to expect significant changes in direction.Note that this setting is only good for faster moving airplanes. For a fixed position hovering heli, 'pedestrian' setting is better3. UBX->CFG->PRT - set USART1 to 57600bps4. Change the baudrate of U-Center to 57600bps if the connection is lost at this point5. UBX->CFG->RATE(Rates) - change the Measurement Period to 250ms This gives a 4 Hz position update since 4 x 250ms is one second.6. UBX->CFG->SBAS : Disable (SBAS appears to cause occasional severe altitude calcuation errors)7. UBX->NAV (not UBX->CFG->NAV): double click on POSLLH, STATUS, VELNED. They should change from grey to black.8. UBX->CFG->CFG : save current config, click "send" in the lower left corner to permanently save these settings to the receiver.You are done!! Now plug the GPS to your ArduPilot and fly like a PRO ;-)[UPDATE:]Another great way to do it:
Be sure you ground D7 (just in case). Then supply the shield with 5 volts and connect the 3.3V and GND to the ublox. Then when you have ublox powered use hyper terminal to see if the GPS is sending data. Try to connenct one signal wire from ublox and check if you get any data, if not try with the other one. When you start to see incoming data change the baud rate to 9600, or 4800 until you see the normal NMEA strings. After that you can go to Ucenter and configure it!
Jordi, I am having trouble connecting to my uBlox,
please describe in more detail method to connect FTDI & power,
With shield not connected to ArduPilot
I connected 5v power to 5v GPS port on shield, power led is on
and FTDI to its port on shield, status led flash,
u-Center see port 5 and baud rate=57000, but data is not what I expected, comm status is grey, but should be green, any help is appreciated. I don't think the uBlox is bad?
I will admit that it is not nearly as small as the SPK one mentioned in this thread, but I feel uneasy about connecting the wires to unintended contact points :)
About the antenna analyzer, I looked into that and it appears that is used for active (powered) antennas. You are getting that reading because the paparazzi design uses a passive ceramic patch antenna. So it seems that your hardware is working. I plan on wiring one up as soon as my board comes in.
Yes you can use it perfectly, but is to bulky :S. I have one... And the antenna is not working properly i guess. If you look into ucenter and you look for the antenna "analyzer" (something like that), mention something about been in short circuit. I don't know maybe i'm wrong.
I guess because is the first GPS that fully supports Galileo Satellites (and right now is flying one), you can see it in U-center if you are in Europe. This module will become more accurate, that means is a good investment for the future. For R/C 4, 5 hz is more than enough. We are not flying missiles. ;-)
Jordi, I'm wondering if it is possible to interface this with the paparazzi 4-layer GPS board (http://paparazzi.enac.fr/wiki/GPS#Paparazzi_Stand-alone_GPS_Receivers). It takes a 5V input. The SPK board is tiny and looks promising, but that connector is just too flimsy for my comfort.
Two things. First, you're right that your pattern is probably too tight for the EM406. Unless you're flying really slow in low wind, I think 100m between waypoints is the minimum. A faster GPS would indeed allow tighter control.
Second, we can't confirm the 2 second delay in computation that Howard describes. That would mean missing two update cycles, and we don't see that in practice. (We do see a one-second delay, however, which is just lagging one update cycle)
Comments
Be sure you ground D7 (just in case). Then supply the shield with 5 volts and connect the 3.3V and GND to the ublox. Then when you have ublox powered use hyper terminal to see if the GPS is sending data. Try to connenct one signal wire from ublox and check if you get any data, if not try with the other one. When you start to see incoming data change the baud rate to 9600, or 4800 until you see the normal NMEA strings. After that you can go to Ucenter and configure it!
please describe in more detail method to connect FTDI & power,
With shield not connected to ArduPilot
I connected 5v power to 5v GPS port on shield, power led is on
and FTDI to its port on shield, status led flash,
u-Center see port 5 and baud rate=57000, but data is not what I expected, comm status is grey, but should be green, any help is appreciated. I don't think the uBlox is bad?
No offenses (Came on!). In my way is working good. But your way is better and i will do it like that. Thanks for the advice!
I will admit that it is not nearly as small as the SPK one mentioned in this thread, but I feel uneasy about connecting the wires to unintended contact points :)
About the antenna analyzer, I looked into that and it appears that is used for active (powered) antennas. You are getting that reading because the paparazzi design uses a passive ceramic patch antenna. So it seems that your hardware is working. I plan on wiring one up as soon as my board comes in.
Yes you can use it perfectly, but is to bulky :S. I have one... And the antenna is not working properly i guess. If you look into ucenter and you look for the antenna "analyzer" (something like that), mention something about been in short circuit. I don't know maybe i'm wrong.
I guess because is the first GPS that fully supports Galileo Satellites (and right now is flying one), you can see it in U-center if you are in Europe. This module will become more accurate, that means is a good investment for the future. For R/C 4, 5 hz is more than enough. We are not flying missiles. ;-)
www.rfdesign.co.za
I'm so,so glad the code will be implimented... I've been bugging chris and Jordi about it :) Rather a while ago..
Keep up the great work!
Two things. First, you're right that your pattern is probably too tight for the EM406. Unless you're flying really slow in low wind, I think 100m between waypoints is the minimum. A faster GPS would indeed allow tighter control.
Second, we can't confirm the 2 second delay in computation that Howard describes. That would mean missing two update cycles, and we don't see that in practice. (We do see a one-second delay, however, which is just lagging one update cycle)
-
1
-
2
-
3
-
4
-
5
of 5 Next