Differences

This shows you the differences between two versions of the page.

--- guides:falcom_fsa03 [2010/09/09 09:04] – changed type int to unsigned long for startTime variable. Int causes timing errors because millis() returns unsigned long. mixio
+++ guides:falcom_fsa03 [2012/06/03 14:42] (current) – upu
@@ Line 4: / Line 4: @@
 The [[http://www.falcom.de/products/gps-modules/fsa03/|Falcom FSA03]] is an inexpensive Ublox 5 ([[http://www.u-blox.com/en/gps-chips/stand-alone-gps-chips/u-blox-5-chipset-ubx-g5010.html|UBX-G5010]]) GPS module with a small footprint which featuring the Sarantel quadrifilar helix antenna.
+Although still available this unit is end of life.
 Ublox modules are capable of operating above 60,000 feet, provided they are configured and placed in airborne mode. The FSA03 does not include any EEPROM or Flash memory, and as such is unable to retain settings unless its RAM is buffered by backup battery. The module should be programmed with UBX whenever power has been lost to place it in airborne mode.
 Some FSA03 modules have been found to have a default baud rate of 9600, whilst others have a default baud rate of 38400, which may be difficult to parse if not using a UART (ie software serial).
@@ Line 20: / Line 23: @@
 The module draws around 40mA typically, though upto 100mA when acquiring lock.
-The antenna on this module appears to be slightly wobbly and this may be one of the causes of the module not getting a lock for long periods of time. Its recommended that you secure it (perhaps with glue) in a position that works.
+The antenna on this module appears to be slightly wobbly and this may be one of the causes of the module not getting a lock for long periods of time. It's recommended that you secure it (perhaps with glue) in a position that works.
 ===== Configuration =====
 The FSA03 is primarily configured through Ublox's binary protocol (UBX), though some parameters can be altered using NMEA sentences. The [[http://www.u-blox.com/images/downloads/Product_Docs/u-blox5_Protocol_Specifications%28GPS.G5-X-07036%29.pdf|UBX protocol specification]] covers configuring the module.
@@ Line 32: / Line 36: @@
 ====== CONFIG NAV MODE (Airbone < 1g) + (Auto 2D/3D) ======
-:37:25  SEND  B5 62 06 24 24 00 FF FF 06 03 00 00 00 00 10 27  // Set Navigation Engine Settings
+:37:25  SEND   B5 62 06 24 24 00 FF FF 06 03 00 00 00 00 10 27  // Set Navigation Engine Settings
 	  SEND   00 00 05 00 FA 00 FA 00 64 00 2C 01 00 00 00 00
 	  SEND   00 00 00 00 00 00 00 00 00 00 16 DC
@@ Line 131: / Line 135: @@
 :31:57  RECV  B5 62 05 01 02 00 06 06 14 3D  		// Message Acknowledged
+===== Baud rate to 4800 =====
+:33:45  SEND  B5 62 06 00 14 00 01 00 00 00 D0 08 00 00 C0 12  // Set 4800
+          SEND  00 00 03 00 03 00 00 00 00 00 CB C4
+:33:45  RECV  B5 62 05 01 02 00 06 00 25 8D                    // Message Acknowledged
 </code>
@@ Line 141: / Line 150: @@
 #include <NewSoftSerial.h>
-NewSoftSerial nss(3, 2);
+NewSoftSerial nss(2, 3);
+// GPS Tx output is connected to Arduino input on pin 2
+// GPS Rx input is connected to Arduino output on pin 3
+byte navmode = 99;
 void setup() {
@@ Line 267: / Line 281: @@
 	}
 }
+//Function to poll the NAV5 status of a Ublox GPS module (5/6)
+//Sends a UBX command (requires the function sendUBX()) and waits 3 seconds
+// for a reply from the module. The then isolates the byte which contains
+// the information regarding the NAV5 mode,
+// 0 = Pedestrian mode (default, will not work above 12km)
+// 6 = Airborne 1G (works up to 50km altitude)
+//Adapted by jcoxon from getUBX_ACK() from the example code on UKHAS wiki
+// http://wiki.ukhas.org.uk/guides:falcom_fsa03
+boolean checkNAV(){
+  uint8_t b, bytePos = 0;
+  uint8_t getNAV5[] = { 0xB5, 0x62, 0x06, 0x24, 0x00, 0x00, 0x2A, 0x84 }; //Poll NAV5 status
+  nss.flush();
+  unsigned long startTime = millis();
+  sendUBX(getNAV5, sizeof(getNAV5)/sizeof(uint8_t));
+  while (1) {
+    // Make sure data is available to read
+    if (nss.available()) {
+      b = nss.read();
+      if(bytePos == 8){
+        navmode = b;
+        return true;
+      }
+      bytePos++;
+    }
+    // Timeout if no valid response in 3 seconds
+    if (millis() - startTime > 3000) {
+      navmode = 0;
+      return false;
+    }
+  }
+}
 </code>
 ==== NMEA ====
@@ Line 316: / Line 364: @@
 |0|$PUBX|string|$PUBX|-|Message ID, UBX protocol header, proprietary sentence|
 |1|00|numeric|ID|-|Propietary message identifier: 00|
-|2|081350.00|hhmmss.sss|hhmmss.ss|-|UTC Time, Current time|
+|2|081350.00|hhmmss.ss|hhmmss.ss|-|UTC Time, Current time|
 |3|4717.113210|ddmm.mmmm|Latitude|-|Latitude, Degrees + minutes, see Format description|
 |4|N|character|N|-|N/S Indicator, N=north or S=south|
@@ Line 322: / Line 370: @@
 |6|E|character|E|-|E/W indicator, E=east or W=west|
 |7|546.589|numeric|AltRef|m|Altitude above user datum ellipsoid.|
-|8|G3|string|NavStat|-|Navigation Status, See Table below|
+|8|G3|string|NavStat|-|Navigation Status - Example: G3 =Stand alone 3D solution, NF =No Fix|
 |9|2.1|numeric|Hacc|m|Horizontal accuracy estimate.|
 |10|2.0|numeric|Vacc|m|Vertical accuracy estimate.|