Download Print this page

Qstarz GM-Q772 User Manual

Ultra low power, high sensitivity gps smart receiver

Advertisement

Quick Links

Ultra Low Power, High Sensitivity
GPS Smart Receiver
User' s Guide

Advertisement

loading

Summary of Contents for Qstarz GM-Q772

  • Page 1 Ultra Low Power, High Sensitivity GPS Smart Receiver User’ s Guide...
  • Page 2: Hardware Interface

    Only clear view of sky and certain power supply are necessary to the device. With its ultra low power consumption, the smart receiver tracks up to 16 satellites at a time, re-acquires satellite signals in 1 second (average) and updates position data every second.
  • Page 3 2.2 Hardware Interface The smart receiver includes a low noise, high gain active antenna in a unique style waterproof gadget. Simply connect PS-2 female connector to one of the optional accessories and link to either your notebook PC, PDA or other devices.
  • Page 4 The GPS Smart Receiver is also equipped with optional connectors. Pin Assignment of standard PS-2 Din Jack Accessories Mini Din Female and PS-2 male connector: Cable Length: To GPS-6010: 1 meter RS-232 to PS-2: 45 cm Mini Din Female connector function definition:...
  • Page 5 PS2 composite connector function definition (to PC): USB connector The function definition of the A Type USB connector is as follows: Signal +5VDC N.C. N.C. N.C. N.C. Signal +5VDC...
  • Page 6: Usb Driver Installation

    4. Warranty The GPS smart receiver is warranted to be free from defects in material and functions for 1 year from the date of purchase. Any failure of this product within this period under normal conditions will be replaced at no charge to...
  • Page 7 Appendix : Software Specification NMEA Protocol The software is capable of supporting the following NMEA message formats NMEA Message Prefix SGPGGA SGPGLL SGPGSA SGPGSV SGPRMC SGPVTG SGPZDA NMEA Extensions The software is capable of supporting the following NMEA extensions: NMEA Message Prefix $PNMRX100 $PNMRX101 $PNMRX103...
  • Page 8: General Nmea Format

    $PNMRX603 General NMEA Format The general NMEA format consists of an ASCII string commencing with a ‘$’ character and terminating with a <CR><LF> sequence. NMEA standard messages commence with ‘GP’ then a 3-letter message identifier. NemeriX specific messages commence with $PNMRX followed by a 3 digit number.
  • Page 9 Geoid Separation Units Char Age of Differential Corrections Diff Reference Corrections Checksum Message <CR> <LF> terminator $GPGLL This message transfers Geographic position, Latitude, Longitude, and time. The $GPGLL message structure is shown below: Field Format Message ID $GPGLL Latitude Float N/S Indicator Char Longitude...
  • Page 10 $GPGSA This message transfers DOP and active satellites information. The $GPGSA message structure is shown below: Field Format Message ID $GPGSA Mode Char Mode Satellites Used Satellites Used … Satellites Used PDOP Float HDOP Float VDOP Float Checksum Message terminator <CR>...
  • Page 11 $GPGSV This message transfers information about satellites in view. The $GPGSV message structure is shown below. Each record contains the information for up to 4 channels, allowing up to 12 satellites in view. In the final record of the sequence the unused channel fields are left blank with commas to indicate that a field has been omitted.
  • Page 12 $GPRMC This message transfers recommended minimum specific GNSS data. The $GPRMC message format is shown below. Field Format Message ID $GPRMC UTC Time hhmmss.sss Status char Latitude Float N/S Indicator Char Longitude Float E/W indicator Char Speed over ground Float Course over ground Float Date...
  • Page 13 $GPVTG This message transfers Velocity, course over ground, and ground speed. The $GPVTG message format is shown below. Field Format Message ID $GPVTG Course (true) Float Reference Char Course (magnetic) Float Reference Char Speed Float Units Char Speed Float units Char Mode Char...
  • Page 14 $GPZDA This message transfers UTC Time and Date. Since the latency of preparing and transferring the message is variable, and the time does not refer to a particular position fix, the seconds precision is reduced to 2 decimal places. The $GPZGA message format is shown below. Field Format Message ID...
  • Page 15 Signed ECEF z co-ordinate in meters (0) 1 Clock offset of GPS receiver, in [Hz x 100] wrt L1. This changes the clock bias stored in the settings not the actual clock bias used by the system. A cold start is necessary, in order to use this value.
  • Page 16 $PNMRX103, NMEA rate control This message is sent to enable or pause the output of an NMEA message and to determine its output rate. The sequence of the output sequence is determined by the $PNMRX107 message. The $PNMRX103 message format is shown below. The rate of each message can individually be set. If ‘0’...
  • Page 17 $PNMRX104, LLA navigation initialization This message enables the receiver to be initialized using LLA data to speed up satellite acquisition. The first 4 values defining the position (if used) must be all present in the message. Otherwise the whole massage is considered invalid.
  • Page 18 Once the datum has been changed it will be applied to all LLA data, including the LLA navigation initialization Data. This message enables the receiver to be configured to use map datum from an internal table, or datum supplied as part of the message.
  • Page 19 $PNMRX107, Messages rate control This message is sent to set the automatic update rate, and to configure which messages will be automatically output, it is also sent from the node to report which messages are currently configured for automatic transmission. The $PNMRX107 message format is shown below. This message can be used to enable and disable multiple messages by including up to 4 message codes and associated fields in each $PNMRX107 message.
  • Page 20 $PNMRX108, NMEA message sequence This message is used to set the sequence used to output the NMEA messages. All messages in the list are set to be output with a default output rate. The messages that are not included are disabled.
  • Page 21 $PNMRX110, Fix Settings This message is used to set various settings and masks which control how the software will behave in relationship to the satellites in view, for example a mask can be set for the minimum satellite elevation, minimum SNR etc. The message consists of a varying number of fields depending on the number of masks to be set.
  • Page 22 This message is used to reset the systems. If the message is sent without parameters the receiver reboots according to the fix procedure (hot, warm or cold) configured with the PNMRX101 or PNMRX104 messages. A second parameter can optionally be used to specify which actions are executed after the reset.
  • Page 23 This message is used to configure the operating modes of the receiver. Low power modes can be activated and configured. Low power mode starts to work only after the receiver has a complete and up to date almanac and it can produce the fix.
  • Page 24 $PNMRX300, Almanac Data Transfer This message format is used to transfer the almanac data between nodes, it uses a packed hexadecimal format to transfer almanac data for each of the available SV’ s. Since the Almanac data is large and can take time to transfer over a slow serial interface, the data is divided into individual messages for each of the SV’...
  • Page 25 $PNMRX301, Ephemeris Data Transfer This message format is used to transfer the ephemeris data between nodes, it uses a packed hexadecimal format to transfer ephemeris data for each of the available SV’ s. Since the Ephemeris data is large and can take time to transfer over a slow serial interface, the data is divided into individual messages for each of the SV’...
  • Page 26 PNMRX301 message 2 field list Field Format Message ID $PNMRX301 Satellite Vehicle Id Subframe Id Iode Motion difference Mean anomaly Root A Checksum Message terminator <CR> <LF> width scale units Meters Semi- circles/sec Semi- circles Radians Radians Meters seconds (0) 3 Notes PNMRX301 protocol header.
  • Page 27 PNMRX301 message 3 field list Field Format Message ID $PNMRX301 Satellite Vehicle Id Subframe Id Omega zero I Zero Perigree Omega dot Iode I dot Checksum Message terminator <CR> <LF> width scale units Radians Semi- circles radians Semi- circles Meters Semi- circles Semi-...
  • Page 28 $PNMRX302, Ionospheric correction Field Format Message ID $PNMRX302 Satellite Vehicle Id ß 0 ß 1 ß 2 ß 3 Checksum Message terminator <CR> <LF> $PNMRX303,UTC time Field Format Message ID $PNMRX303 Satellite Vehicle Id Data – A0 Data – A1 Delta t LS WNlsf Delta t LSF...
  • Page 29 <CR> <LF> terminator $PNMRX600, Report Software Version By sending the $PNMRX600*00 string to the receiver, the version of the software is output. $PNMRX601, Enter ISP mode By sending the $PNMRX601*00 string to the receiver, the receiver enters ISP mode. $PNMRX603, Settings report By sending the $PNMRX603*00 string to the receiver, the current value of the settings is output.
  • Page 30 PNMRX603 message 1 Field Format Message ID $PNMRX603 Message Nb Ionospheric Data A0 Ionospheric Data A1 Ionospheric Data A2 Ionospheric Data A3 Ionospheric Data B0 Ionospheric Data B1 Ionospheric Data B2 Ionospheric Data B3 Ionospheric Data Valid Num Blocks Time Offset (Local zone hours) Time Offset...
  • Page 31 NMRX603 message 2 Field Format Message ID $PNMRX603 Message Nb MaxPDOP Float MaxHDOP Float Invalid Sv Min CNO Float Min Elevation Float Max TM Max Sv for fix Checksum Message <CR> <LF> terminator Field Format Message ID $PNMRX603 Message Nb threshold 1 threshold 2 Noise floor...
  • Page 32 PNMRX603 message 4 Field Format Message ID $PNMRX603 Message Nb Correction Mode Map Datum Inverse flatness Major axis Checksum Message <CR> <LF> terminator Examples: $PNMRX603*xx : Display the content of the Settings stored in NVRam Min chars Max chars Notes PNMRX603 protocol header.