Download  Print this page

Navman 12 Designer's Manual

Jupiter gps receiver module
Hide thumbs

Advertisement

Jupiter GPS receiver module
Designer's guide
(11/12/T/Pico/Pico T series)
MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice.
Related products
Jupiter 11 (low power)
• Development kit TU10-D007-051
Jupiter 11 (standard 5 V)
• Development kit TU10-D007-061
Jupiter 11 (dead-reckoning)
• Development kit TU10-D007-101
Jupiter 12 (standard)
• Development kit TU10-D007-351
Jupiter 12 (dead-reckoning)
• DR Development kit TU10-D007-352
Jupiter Pico (standard)
• Development kit TU10-D007-361
Jupiter Pico (timing)
• Development kit TU10-D007-363
Related documents
Jupiter T
• Product brief LA010039
• Data sheet LA010050
Jupiter 12
• Product brief LA010040
• Data sheet LA010065
Jupiter Pico (and Pico T)
• Product brief LA010041
• Data sheet LA010066
• Data sheet LA010093
Jupiter series (T/12/Pico/Pico T)
• Development kit: Quick start guide
LA010088
• Development kit: Guide LA010089
• DR receiver: Gyro application note
LA010090
1

Advertisement

Table of Contents
loading

  Related Manuals for Navman 12

  Summary of Contents for Navman 12

  • Page 1 Jupiter GPS receiver module Designer’s guide (11/12/T/Pico/Pico T series) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Related products Jupiter 11 (low power) • Development kit TU10-D007-051 Jupiter 11 (standard 5 V) •...
  • Page 2: Table Of Contents

    3.5.2.9 Message 1219 (user-entered altitude input)..38 3.5.2.10 Message 1220 (application platform control)..39 3.5.2.11 Message 1221 (nav configuration)..40 3.5.2.12 Message 1300 (perform built-in test command)..40 MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice.
  • Page 3 4.5 Satellite management ...61 4.5.1 Visible list generation..61 4.5.1.1 Dilution Of Precision (DOP) ...61 4.5.2 Acquisition modes ...62 4.5.2.1 Sequential acquisition ...62 MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice.
  • Page 4 Typical Specification for RG-316: ... 89 I. Electrical Characteristics: ... 89 II. Physical Characteristics: ... 89 measurement processor ...80 differential data processor ... 80 MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice.
  • Page 5: Features

    • ability to accept externally supplied initialisation data. • three-satellite navigation start-up from acquisition. • user selectable satellites. · user selectable visible satellite mask angle. MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice.
  • Page 6: Introduction

    However, the flexible MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Jupiter signal acquisition system takes advantage of all available information to provide a rapid TTFF.
  • Page 7 (optional) Figure 1-3 Possible Jupiter/OEM architecture MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. architecture that might be used to integrate a particular Jupiter receiver with an application processor that drives peripheral devices such as a display and keyboard.
  • Page 8: Hardware Interface

    8-bit representation. The Jupiter receiver software will pack/unpack the character data internally as needed. MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Each binary message consists of a header portion and a data portion, each with its own checksum.
  • Page 9: Binary Message Header

    The ACK/NAK control mechanism gives the user the ability to request either ACK or NAK, or both, MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. independently for each message request. The user...
  • Page 10: Message Header Word 5

    The data portion of a binary message, if it exists, can be variable in length, as specified by the MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. data word count found in the header. The data checksum follows the data and is not included in the data word count.
  • Page 11: Nmea Input Messages

    Hex value <CR> <LF> MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. The maximum number of characters in a sentence is 82, consisting of a maximum of 79 characters between the starting delimiter ‘$’ and the terminating <CR>...
  • Page 12 Note 3: All data fields are delimited by a comma (,). Note 4: Null fields are indicated by no data between two delimiters. MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Definition Special format fields...
  • Page 13 Flash boot status Error/status (*) Enable by default at power-up (**) Once at power-up/reset MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Message ID Input message name Geodetic position and velocity...
  • Page 14: Jupiter Binary Data Messages

    Number of measurements used in solution Table 3-5 (1 of 2) Message 1000 (geodetic position status output) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. 3.5.1.1 Message 1000 (geodetic position status output) This message outputs the receiver’s estimate of...
  • Page 15 Note 11: DR is running with calibration from stored values from prior operating session. Note 12: An uncertainty value of 0x7FFF indicates unknown heading. A message value 0x000D indicates Polar navigation equals true and heading uncertainty SD equals 0.06 (hex value 0x000C).
  • Page 16: Message 1002 (Channel Summary)

    Note 4: n = 0 to 11. Table 3-6 Message 1002 (channel summary) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. information on a per- channel basis. The contents of the ‘channel summary’ message are described...
  • Page 17: Message 1003 (Visible Satellites)

    Note 4: j = the number of visible satellites minus one when the number of visible satellites is greater than zero. Table 3-7 Message 1003 (visible satellites) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. from this visible list, are also provided. The contents of the ‘visible satellites’...
  • Page 18: Message 1005 (Dgps Status)

    Note 2: The sequence number is a count that indicates whether the data in a particular binary message has been updated or changed since the last message output. Note 3: Only the correction status words for the number of available corrections reported in word 12 of this message are valid. Note 4: The word number, j, ranges from 13 to 24.
  • Page 19: Message 1007 (Channel Measurement)

    Note 4: j = 0 to 11 Table 3-9 Message 1007 (channel measurement) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. 12 channels. The contents of the ‘channel measurement’ message are described in Table 3-9.
  • Page 20: Message 1009 (Reduced Ecef Position Status Output)

    Note 4: The data displayed by this field is not valid until the receiver is in navigation mode. Table 3-10 Message 1009 (ECEF position output) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. 12 channels. The contents of the ‘channel measurement’...
  • Page 21: Message 1011 (Receiver Id)

    1 minimises RAM usage bits 2-15 reserved MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. this message are also honoured. This message consists of five 20-byte (two characters per word), null-padded ASCII data fields.
  • Page 22: Message 1012 (User Settings Output)

    1 = SV2 status, bit 31 = SV32 status). Table 3-12 Message 1012 (user-settings output) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. The contents of the ‘user settings output’ message are described in Table 3-12.
  • Page 23: Message 1100 (Built-In Test Results )

    Therefore, the OEM’s BIT pass/fail should ignore words for components that are not in the system under test. Notice that the Dual Port RAM Failure test is currently not implemented. Therefore, word 12 will report a value of zero.
  • Page 24: Message 1108 (Utc Time Mark Pulse Output)

    Table 3-14 Message 1108 (UTC time mark pulse output) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. 400 milliseconds before the time mark pulse strobe signal.
  • Page 25: Message 1110 (Frequency Standard Parameters In Use)

    Table 3-15 Message 1110 (frequency standard parameters in use) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Note: Message 1110 is primarily used to output key parameters to GPS systems without non- volatile storage.
  • Page 26: Message 1117 (Power Management Duty Cycle In Use)

    Table 3-16 Message 1117 (power management duty cycle in use) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. ‘power management duty cycle in use’ message are described in Table 3-16.
  • Page 27: Message 1130 (Serial Port Communication Parameters In Use)

    Port 1 post-scale (Note 3) Table 3-17 (1 of 2) Message 1130 (serial port communication parameters in use) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. The contents of the ‘serial port communication parameters in use’...
  • Page 28 Note 3: When a custom bits-per-second (bps) rate is selected, the bps rate is equal to ‘CPU clock / (16 x pre-scale x 2post-scale)’. Table 3-17 (2 of 2) Message 1130 (serial port communication parameters in use message) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Type Port 2 communication parameters (12.0-14)
  • Page 29: Message 1135 (Eeprom Update)

    Note 4: This field is only valid when the data ID = 23 (Almanac). Table 3-18 Message 1135 (EEPROM update) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. configured for output on update (the default), as it will provide a notification of all stored configuration...
  • Page 30: Message 1136 (Eeprom Status)

    15 = user entered altitude 31 = data is being updated Table 3-19 Message 1136 (EEPROM status) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. in the status words indicate that those data blocks have been updated at least once in the EEPROM.
  • Page 31: Message 1160 (Frequency Standard Table Output Data)

    Table 3-20 Message 1160 (frequency standard table output data) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. message will be used in conjunction with Message 1360 to retrieve and restore this information for external storage.
  • Page 32: Message 1180 (Flash Boot Status)

    3 = executive error 4 = executive Service Routine error 5 = user error MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. 3.5.1.18 Message 1190 (error/status) This message provides diagnostic information if the receiver encounters an error during execution of its firmware.
  • Page 33: Binary Input Message Descriptions

    Table 3-23 Message 1200 (geodetic position and velocity initialisation) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. rate. The course may be either true or magnetic, as indicated by the magnetic course field.
  • Page 34: Message 1210 (User-Defined Datum)

    Note 2: Appendix B contains map datum codes from 0 to 188. Codes 300 to 304 are user-defined. Table 3-25 Message 1211 (map datum select) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. use’ for the navigation function. Also, any message 1210 that contains an undefined datum code is...
  • Page 35: Message 1212 (Satellite Elevation Mask Control)

    Table 3-27 Message 1213 (satellite candidate select) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. 3.5.2.5 Message 1213 (satellite candidate select). This message allows the user to construct the list of satellites which will be considered for selection by the receiver.
  • Page 36: Message 1214 (Dgps Control)

    Table 3-29 Message 1216 (cold start control) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. continues until either the receiver navigates or the timer is exceeded.
  • Page 37: Message 1217 (Solution Validity Input)

    Note 4: DR must NOT be used, even if available. Table 3-30 Message 1217 (solution validity input) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. status specified in the position output messages.
  • Page 38: Message 1219 (User-Entered Altitude Input)

    (RAM or EEPROM). Table 3-31 Message 1219 (user-entered altitude input) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. entry of mean-sea- level altitude. A standard deviation can be specified to indicate the...
  • Page 39: Message 1220 (Application Platform Control)

    Table 3-32 Message 1220 (application platform control) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. application in which the receiver is being used. Storage for the Platform parameter requires EEPROM.
  • Page 40: Message 1221 (Nav Configuration)

    Table 3-34 Message 1300 (perform built-in test command) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Ground track smoothing and position pinning are not used when DGPS corrections are in use. The contents of the ‘nav configuration’...
  • Page 41: Message 1303 (Restart Command)

    If cold start testing without time is desired, then the invalidate RTC bit (7.2) should also be set. Table 3-35 Message 1303 (restart command) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. The contents of the ‘restart command’ message are described in Table 3-35.
  • Page 42: Message 1310 (Frequency Standard Input Parameters)

    Table 3-36 Message 1310 (frequency standard input parameters) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Note: Message 1310 is primarily used to input key parameters from GPS systems without non-volatile storage.
  • Page 43: Message 1317 (Power Management Control)

    Table 3-37 Message 1317 (power management control) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Note: Message 1317 is primarily used to input key parameters from GPS systems without non-volatile storage.
  • Page 44: Message 1330 (Serial Port Communication Parameters)

    Note 2: Pre-scale/post-scale parameters are used to set custom bps rates (bps rate = ‘CPU clock/(16 x pre-scale x 2post-scale) Table 3-38 Message 1330 (serial port communication parameters) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. two serial ports. The contents of the ‘serial port communication parameters’...
  • Page 45: Message 1331 (Message Protocol Control)

    Table 3-40 Message 1350 (factory calibration input) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. ‘message protocol control’ message are described in Table 3-39.
  • Page 46: Message 1351 (Raw Dgps Rtcm Sc-104 Data)

    Table 3-41 Message 1351 (raw DGPS RTCM SC-104 data) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. compatibility with the earlier MicroTracker GPS receiver and may be used in lieu of the auxiliary port data.
  • Page 47: Message 1360 (Frequency Standard Table Input Data)

    Note: This message does not provide the sequence number as word 6. Table 3-43 Message 1380 (flash re-program) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. contents of the ‘frequency standard table input data’...
  • Page 48: Jupiter Nmea Data Messages

    <CR><LF> Sentence terminator Note 1: $ = NMEA message prefix. P = proprietary message indicator, RWI = Navman Systems Inc. mnemonic, BIT = BIT results message ID. Note 2: A value of zero indicates a test has passed. A non-zero value indicates a device failure. Missing devices are reported as failures.
  • Page 49: Navman Proprietary Error/Status (Err)

    Note 5: Time in seconds since the last SC1-04 Type 1 or Type 9 update; null field when DGPS is not used. Note 6: This field is null when DGPS is not used. MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. navigation solution passes all validity criteria (set using the binary ‘solution validity criteria’...
  • Page 50: Gps Satellites Active And Dop (Gsa)

    Note 2: Azimuth and elevation are null when the satellite is in track, but a visible list is not available. Table 3-49 GSV message (GPS satellites in view) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. and Signal-to-Noise Ratio (SNR) values. Each transmission identifies up to four satellites (max);...
  • Page 51: Navman Proprietary Receiver Id (Rid)

    ROM usage, bit 1 minimises RAM usage, bits 2-15 are reserved. Table 3-50. RID message (Navman proprietary receiver ID) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. serial input. The contents of the ‘RID’ message are described in Table 3-50.
  • Page 52: Recommended Minimum Specific Gps Data (Rmc)

    Note 2: Easterly variation (E) subtracts from true course. Westerly variation (W) adds to true course. Table 3-51. RMC message (recommended minimum specific GPS data) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. obtained. The contents of the ‘RMC’ message are described in Table 3-51.
  • Page 53: Course Over Ground And Ground Speed (Vtg)

    Note 1: Output of this message is temporarily suppressed while the receiver is in acquisition mode. Table 3-52. VTG message (course over ground and ground speed) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. described in Table 3-52.
  • Page 54: Navman Proprietary Jupiter Channel Status (Zch)

    Sentence terminator Note 1: Channel number (xx) is implied by position in message. Data for all 12 channels is always provided in this message. If a channel is unused, a value of 0 will appear for both channel fields. The status indication (hh__ is a one-digit, hexadecimal value which represents four bits as follows: <y.O>...
  • Page 55: Nmea Input Message Descriptions

    <CR><lF> Sentence terminator Note 1: $ = NMEA message prefix, P = proprietary message indicator, RWI = Navman Systems Inc. mnemonic, ILOG = log control message ID. Note 2: A special form of this field disables all output messages. Use ‘???’ as the message ID as in the following example: $PRWIILOG,???,V,,, Note 3: This field may be null to indicate that the previous setting should be left unchanged.
  • Page 56: Navman Proprietary Receiver Initialisation Message (Init)

    • UTC time and date must be provided together. Table 3-56 INIT message (Navman proprietary receiver initialisation) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. are described in Table 3-56.
  • Page 57: Navman Proprietary Protocol Message (Ipro)

    Note 1: The identifier of the device from which data is being requested (refer to paragraph 5.4.4 of this chapter) must be ‘GP’ (GPS device) for the ‘Jupiter’ receiver to recognise the message; otherwise, the message will be ignored. MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. 3.6.2.5 Standard query message (Q).
  • Page 58: Jupiter Gps Receiver Operation

    4.1.4 Read-Only Memory (ROM) On board ROM is only used as a data source if MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. SRAM and EEPROM are unavailable. Satellite almanac and frequency standard parameters can be obtained from ROM with limited usefulness.
  • Page 59: Configuration

    (*) solution validity criteria (**) after a ‘fully determined’ or successful transition to navigation MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. inputs. Over 180 pre-defined datums are available for user configuration.
  • Page 60: Differential Gps (Dgps) Control

    Note: These straps are only read once at MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. initialisation time, so a power cycle or hardware or software reset must be executed after any strap changes are made.
  • Page 61: Frozen Start

    MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. almanac or ephemeris data. In the case where DGPS corrections are used to establish list membership, a change in the set of satellites reflected in the corrections also causes a...
  • Page 62: Acquisition Modes

    4.5.2.4 Overall search process Figure 4-1 depicts the overall search process as MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. it interacts with the visible satellite list generation described in section 4.5.I. Sequential or parallel...
  • Page 63 Figure 4-1 Jupiter search process MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice.
  • Page 64: Navigation

    Department of Defense World Geodetic System 1984. MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. 4.6.1.1 User selection of geodetic datums The default datum is WGS-84 (defined as datum code zero for the receiver).
  • Page 65: Platform Class

    Once the receiver has been navigating and a velocity has been established by the Kalman filter, MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. it will be used to propagate the state forward in the...
  • Page 66: Ground Track Smoothing

    Ground-track smoothing can be disabled using the ‘nav configuration’ message (binary MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Message 1221). The configuration word is stored in EEPROM, so the setting for ground-track smoothing will be retained through power-off and reset cycles.
  • Page 67: Maximum Ehpe Validity Criterion

    4.6.6 Magnetic variation The magnetic variation model used in the receiver MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. is derived from the full International Geomagnetic Reference Field (IGRF) 95 magnetic model.
  • Page 68: The Auxiliary Port

    Table 4-2 Parameters and data maintained in EEPROM MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. update. The various parameters and data maintained in the Jupiter receiver’s EEPROM are listed in Table 4-2.
  • Page 69: The Rtcm Protocol

    RTCM standard are used by the receiver to form a DGPS position solution. Refer to the MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. standard for more detailed descriptions of these and other RTCM SC-104 messages.
  • Page 70: Disabling Dgps Operation

    However, after a DGPS reset all other DGPS MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. parameters will be set to their default values.
  • Page 71 If the count of bytes received with error is large, the interface may be defective or the port configuration may be incorrect. MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice.
  • Page 72: Appendix A: Acronyms, Abbreviations, And Glossary

    BIT: Built-In Test. Block I satellite: satellites designed and built to MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. support GPS development and testing. A total of 10 Block I satellites were successfully launched between February 1978 and October 1989.
  • Page 73 MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. GPS receiver solution. The lower the value of the GDOP parameter, the less the error in the position solution.
  • Page 74 The GPS receiver computes, when possible, an over-determined solution using MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. the measurements from all GPS satellites it can track, instead of the four necessary for a three- dimensional position solution.
  • Page 75 Navigation Mode. TOW: Time Of Week (see GPS time). MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. TTFF: Time-To-First-Fix. The actual time required by a GPS receiver to achieve a position solution.
  • Page 76: Appendix B: References

    55 degrees. This orientation normally provides a GPS user with a MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Figure C-1 NAVSTAR GPS operational satellite...
  • Page 77 = user clock bias Figure C-2 Range processing equations GPS system operation MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. by the speed of light to arrive at the apparent range measurement.
  • Page 78 DOPs relate to more accurate estimates. MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. The errors in the range measurements used to solve for position may be magnified by poor geometry.
  • Page 79 The oscillator that times the MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. satellite signal is free-running; the GPS ground...
  • Page 80: Measurement Processor

    Figure C-5 User equipment block diagram MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. is transmitted continuously or in bursts, or whether protocol overhead is added.
  • Page 81: Appendix D: Frequently Asked Questions (Faq)

    Accuracy with DGPS is primarily a function of the quality and latency of the corrections used. MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. 6. What is the difference between the two models...
  • Page 82: Appendix E: Reference Ellipsoids And Datum Tables For Jupiter And Navcore Receivers

    WGS 84 Bessel 1841 (Namibia) Everest 1956 Everest 1969 Everest (Sabah & Sarawak) SGS 85 MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. REFERENCE ELLIPSOIDS Semi-Major Axis 6377563.396000 6377340.189000 6378160.000000 6377397.155000...
  • Page 83 Bukit Rimpah Indonesia (Bangka & Belitung Islands) Camp Area Astro Antarctica (McMurdo Camp Area) Campo Inchauspe - Argentina MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. ROM Datums Name –166 –15...
  • Page 84 GUX 1 Astro - Guadalcanal Island Herat North - Afghanistan Hjorsey 1955 - Iceland Hong Kong 1963 - Hong Kong Hu-Tzu-Shan - Taiwan MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Name –375 –136 –292 –263...
  • Page 85 North American 1927 - Alaska North American 1927 Bahamas (Except San Salvador Island) North American 1927 Bahamas (San Salvador Island) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Name –122 –794 –298 –435...
  • Page 86 Provisional S. American 1956 - Bolivia Provisional S. American 1956 Chile (Northern, Near 19°S) Provisional S. American 1956 Chile (Southern, Near 43°S) MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Name –7 –9...
  • Page 87 Wake Island Astro 1952 - Wake Atoll WGS 1972 - Global Definition Yacare - Uruguay Zanderij - Suriname MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Name –282 –371 –278 –367...
  • Page 88 Liberia 1964 Luzon Mindanao Island Table E-1 NavCore datums, maintained and selectable through the LABMON development software MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice. Mahe 1971 Marco Astro Massawa...
  • Page 89: Appendix F: 2 X 10 Pin Field Connector Information

    Conductor diameter 0.020 inches nominal Core diameter 0.58 inches nominal Outside dimensions 0.96 inches nominal Applicable specifications MIL-C-17F (M17/113- RG316) *Teflon is a trademark of DuPont MN002000A © 2004 Navman NZ Ltd. All rights reserved. Proprietary information and specifications subject to change without notice.
  • Page 90 Navman products are not intended for use in medical, lifesaving or life sustaining applications. Navman customers using or selling Navman products for use in such applications do so at their own risk and agree to fully indemnify Navman for any damages resulting from such improper use or sale.