The Jupiter 20 GPS receiver module is a very small surface mount receiver that is intended
as a component for OEM (Original Equipment Manufacturer) products. The module provides
a 12‑channel receiver that continuously tracks all satellites in view and provides accurate
positioning data.
2.0 Technical description
The highly integrated digital receiver incorporates and enhances the established technology
of the SiRFstarIIe/LP chipset. It is designed to meet the needs of the most demanding
applications, such as vehicle tracking in dense urban environments. The interface conguration
allows incorporation into many existing devices and legacy designs.
The Jupiter 20 receiver decodes and processes signals from all visible GPS satellites. These
satellites, in various orbits around the Earth, broadcast RF (radio frequency) ranging codes,
timing information, and navigation data messages. The receiver uses all available signals to
produce a highly accurate navigation solution. The 12‑channel architecture provides rapid TTFF
(Time To First Fix) under all start‑up conditions. Acquisition is guaranteed under all initialisation
conditions as long as visible satellites are not obscured.
The Jupiter 20 is available in three congurations:
• Jupiter 20S (high sensitivity) – with XTrac navigation software
• Jupiter 20D (Dead Reckoning) – with SiRFDRive software and gyro interface
Protocols supported are selected NMEA (National Marine Electronics Association) data
messages and SiRF binary.
2.1 Product applications
The module is designed for high performance and maximum exibility in a wide range of OEM
congurations including hand‑helds, sensors, and in‑vehicle automotive products.
2.2 Receiver architecture
The functional architecture of the Jupiter 20 receiver is shown in Figure 2‑1.
controls the down conversion process for the RFIC block. Stability in this frequency is required
to achieve a fast TTFF.
Baseband processor: The SiRFstarII GSP 2e/LP processor is the main engine of the GPS
receiver. It runs all GPS signal measurement code, navigation code, and other ancillary routines,
such as power saving modes. The normal I/O of this processor is via the two serial ports.
Flash memory: The Flash memory stores software and also some long term data.
RTC (Real Time Clock) crystal: The 32 kHz crystal operates in conjunction with the RTC inside
the baseband processor. It provides an accurate clock function when main power has been
removed, if the battery backup is connected.
Reset generator: There are two voltage threshold reset generators in the Jupiter 20. The rst
provides a reset to the baseband block if the main power drops below a low limit threshold.
The second shuts off the supply to the RTC in case the backup battery drops below a lower
threshold. This is used to compensate for a slow SiRF rise‑time backup voltage.
Regulators: The regulators provide a clean and stable voltage supply to the components in the
receiver.
DR (Dead Reckoning) components: The Jupiter 20D has additional components allowing direct
connection to a turn rate gyro. The gyro input takes the form of a high resolution ADC (Analogue
to Digital Converter), where the analogue signal is digitised and prepared for use by the
SiRFDRive DR software running in the baseband processor.
2.4 Physical characteristics
The Jupiter 20 receiver is packaged on a miniature printed circuit board with a metallic RF
enclosure on one side. The standard or DR conguration must be selected at the time of
ordering and is not available for eld retrotting.
A lead‑free RoHS compliant product has been available since the end of 2005.
2.5 Mechanical specication
The physical dimensions of the Jupiter 20 are as follows:
length: 25.4 mm ± 0.1 mm
width: 25.4 mm ± 0.1 mm
thickness: 3.0 mm max
weight: 4.0 g max
Refer to Figure 8‑1 for the Jupiter 20 mechanical drawing.
2.6 External antenna surface mount pads
The RF surface mount pad for the external antenna has a characteristic impedance of 50 ohms.
2.7 I/O and power connections
The I/O (Input Output) and power connections use surface mount pads with edge plating around
the edge of the module.
The environmental operating conditions of the Jupiter 20 are as follows:
temperature: –40ºC to +85ºC
humidity: up to 95% non‑condensing or a wet bulb temperature of +35ºC
altitude: –304 m to 18 000 m
vibration: random vibration IEC 68‑2‑64
max. vehicle dynamics: 500 m/s
shock (non‑operating): 18 G peak, 5 ms
2.9 Compliances
The Jupiter 20 complies with the following:
Directive 2002/95/EC on the restriction of the use of certain hazardous substances in
•
electrical and electronic equipment (RoHS)
CISPR22 and FCC: Part 15, Class B for radiated emissions
•
Automotive standard TS 16949
•
•
Manufactured in an ISO 9000 : 2000 accredited facility
2.10 Marking/Serialisation
The Jupiter 20 supports a code 128 barcode indicating the unit serial number. The Navman
13‑character serial number convention is:
characters 1 and 2: year of manufacture (e.g. 06 = 2006, 07 = 2007)
characters 3 and 4: week of manufacture (1 to 52, starting rst week in January)
character 5: manufacturer code
characters 6 and 7: product and type
character 8: product revision
characters 9-13: sequential serial number
3.0 Performance characteristics
3.1 TTFF (Time To First Fix)
TTFF is the actual time required by a GPS receiver to achieve a position solution. This
specication will vary with the operating state of the receiver, the length of time since the last
position x, the location of the last x, and the specic receiver design.
3.1.1 Hot start
A hot start results from a software reset after a period of continuous navigation, or a return
from a short idle period (i.e. a few minutes) that was preceded by a period of continuous
navigation. In this state, all of the critical data (position, velocity, time, and satellite
ephemeris) is valid to the specied accuracy and available in SRAM (Static Random Access
Memory). Battery backup of the SRAM and RTC during loss of power is required to achieve a
hot start.
3.1.2 Warm start
A warm start typically results from user‑supplied position and time initialisation data or
continuous RTC operation with an accurate last known position available in memory. In this
state, position and time data are present and valid but ephemeris data validity has expired.
3.1.3 Cold start
A cold start acquisition results when either position or time data is unknown. Almanac
information is used to identify previously healthy satellites.