Navman GPS Receiver LA000508 User Manual

Jupiter 20

GPS receiver module

Data Sheet

Related documents

• Jupiter 20 Integrator’s manual LA000508

• Jupiter 20 Product brief LA000509

• Jupiter Series development kit guide

LA000645

• SiRF Binary protocol reference manual

• Navman NMEA reference manual

MN000315

• Jupiter 20 DR application note LA000433

• Low Power Operating Modes application

note LA000513

5.0 Software interface .......................................................................................... 13

5 .1 N MEA output messages ..............................................................................................13

5.2 SiRF binary .................................................................................................................13

5.3 Software functions and capabilities .............................................................................13

6.0 Dead Reckoning input speciﬁcation s ........................................................... 14

6 .1 G yro input speciﬁcatio n ...............................................................................................14

6.2 Wheel tick rate ............................................................................................................14

6.3 Fwd/Rev input sense ...................................................................................................14

7.0 Jupiter 20 development ki t ............................................................................. 15

8.0 Jupiter 20 mechanical drawing...................................................................... 15

9.0 Product handling............................................................................................. 16

9.1 Packaging and delivery ...............................................................................................16

9.2 Moisture sensitivity ......................................................................................................16

9.3 ESD sensitivity ............................................................................................................16

9.4 Safety ..........................................................................................................................16

9.5 RoHS compliance .......................................................................................................16

9.6 Disposal .......................................................................................................................16

10.0 Ordering informatio n .................................................................................... 17

11.0 Glossary and acronyms................................................................................ 17

Figures

Figure 2‑1: Jupiter 20 module architectur e ......................................................................... 4

Figure 8‑1: Jupiter 20 mechanical layout ...........................................................................15

Tables

Table 3‑1: TTFF acquisition time s ...................................................................................... 7

Table 3‑2: Software processing performanc e .................................................................... 8

Table 3‑3: GPS receiver performance ............................................................................... 8

Table 3‑4: Position and velocity accuracy .......................................................................... 9

Table 4‑1: Operating power for the Jupiter 2 0 .................................................................... 9

Table 4‑2: Typical jamming performance ..........................................................................10

Table 4‑3: Interface voltage levels ....................................................................................11

Table 4‑4: J20D receiver pad functions ............................................................................11

Table 4‑5: J20/J20S receiver pad function s ......................................................................12

Table 5‑1: Jupiter 20 default baud rate s ............................................................................13

Table 5‑2: Default NMEA message s .................................................................................13

Table 5‑3: Jupiter 20 software capability ...........................................................................14

Table 6‑1: Gyro input speciﬁcations ..................................................................................14

Table 10‑1: Jupiter 20 ordering information .......................................................................17

1.0 Introduction

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 conﬁguration

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 conﬁgurations:

• Jupiter 20 (standard) – GSW2.3 navigation software

• 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

conﬁgurations 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.

Module architecture

DR Modules only

GYRO IN

wheel

ticks

forward/

reverse

PWRIN

active or passive antenna

ADC

UART

ports

controls/

GPIO

TCXO

RFIC

bias T

baseband

processor

bandpass

ﬁlter

LNA

RFIN

V_ANT

input

RTC crystal

1.8V

2.8V

regulator

AD [0‑18]

D [0‑15]

CTRL

PWRIN

Flash memory

brown out

detector

ORing

circuit

PWRIN

VBATT

Figure 2-1: Jupiter 20 module architecture

ꢀ

2.3 Major components of the Jupiter 20

LNA (Low Noise Ampliﬁer): This ampliﬁes the GPS signal and provides enough gain for the

receiver to use a passive antenna. A very low noise design is utilised to provide maximum

sensitivity.

Bandpass ﬁlter (1.575GHz): This ﬁlters the GPS signal and removes unwanted signals caused by

external inﬂuences that would corrupt the operation of the receiver.

RFIC (Radio Frequency Integrated Circuit): The RFIC (SiRFstarII GRF 2i/LP) and related

components convert the GPS signal into an intermediate frequency and then digitise it for use by

the baseband processor.

TCXO (Temperature Compensated Crystal Oscillator): This highly stable 24.5535MHz oscillator

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 32kHz 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 conﬁguration must be selected at the time of

ordering and is not available for ﬁeld retroﬁtting.

A lead‑free RoHS compliant product has been available since the end of 2005.

2.5 Mechanical speciﬁcation

The physical dimensions of the Jupiter 20 are as follows:

length:

width:

25.4mm ± 0.1mm

thickness: 3.0mm max

weight: 4.0g 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 50ohms.

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.

ꢁ

2.8 Environmental

The environmental operating conditions of the Jupiter 20 are as follows:

temperature: –40ºC to +85ºC

humidity:

altitude:

up to 95% non‑condensing or a wet bulb temperature of +35ºC

–304m to 18000m

vibration:

random vibration IEC 68‑2‑64

max. vehicle dynamics:500m/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

speciﬁcation 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 speciﬁc 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 speciﬁed 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.

ꢂ

3.2 Acquisition times

Table 3‑1 shows the corresponding TTFF times for each of the acquisition modes.

J20

J20S

90%

J20D

90%

Mode

Typ

90%

Typ

TTFF hot

12s

40s

56s

12s

40s

70s

(valid almanac, position, time & ephemeris)

TTFF warm

(valid almanac, position & time)

38s

42s

55s

38s

35s

52s

TTFF cold

(valid almanac)

44s

45s

re‑acquisition

(<10s obstruction with valid almanac,

position, time & ephemeris)

100ms 100ms 100ms 100ms 100ms 100ms

Table 3-1: TTFF acquisition times

3.3 Timing 1PPS output

The 1PPS (Pulse Per Second) output of the Jupiter 20 receiver is <1µs, typical ±300ns in

reference to UTC (Coordinated Universal Time). This feature is currently only available on the

Jupiter 20 standard module.

3.4 Battery backup (SRAM/RTC backup)

During powered down conditions, the SRAM and RTC may be kept operating by supplying

power from the VBATT as shown in Table 4‑1. The Jupiter 20 can accept slow VBATT supply

rise time (unlike many other SiRFstarII based receivers) due to an on‑board voltage detector.

3.5 TricklePower mode

During normal mode of operation the Jupiter 20 is continuously running, providing a navigation

solution at the maximum rate of once per second. This continuous mode provides no power

saving.

The TricklePower mode of operation can be enabled to reduce the average power consumption.

The main power is supplied to the module continuously. An internal timer wakes the processor

from sleep mode. The module computes a navigation position ﬁx, after which the processor

reverts to sleep mode. The duty cycle is controlled by a user‑conﬁgurable parameter.

If ephemeris data becomes outdated, the TricklePower mode will attempt to refresh the data set

within every 30‑minute period, or for every new satellite that comes into view.

With TricklePower set to a 20% duty cycle, a power saving of 50% can easily be achieved with

minimal degradation in navigation performance.

3.5.1 Adaptive TricklePowermode

In Adaptive TricklePower mode, the processor automatically returns to full power when signal

levels are below the level at which they can be tracked in TricklePower mode. This is the

default behaviour when TricklePower is active.

3.5.2 Push-To-Fix mode

Unlike TricklePower, the operation in this mode is not cyclic. This mode always forces the

GPS software to revert to a continuous sleep mode after a navigation position ﬁx. It will stay

in sleep mode until woken by activation of the reset input, and compute a fresh position.

If the ephemeris data becomes invalid, the RTC has the ability to self activate and refresh the

data, thus keeping the restart TTFF very short.

This mode yields the lowest power consumption of the module, and is ideal where a battery

powered application requires very few position ﬁxes.

For further information on the TricklePower and Push‑To‑Fix modes refer to the Low Power

Operating Modes application note (LA000513).

ꢃ

3.6 Differential aiding

3.6.1 Differential GPS (DGPS)

DGPS speciﬁcation improves the Jupiter 20 horizontal position accuracy to <4m 2dRMS.

3.6.2 Satellite Based Augmentation Systems (SBAS) including WAAS and EGNOS

SBAS improves horizontal position accuracy by correcting GPS signal errors caused by

ionospheric disturbances, timing and satellite orbit errors. The Jupiter 20 is capable of

receiving WAAS and EGNOS differential corrections. Both SBAS and DGPS should improve

position accuracy. However, other factors can affect accuracy, such as GDOP (Geometric

Dilution of Precision), multipath, distance from DGPS reference station and latency of

corrections. Note also that XTrac does not support differential aiding.

3.7 Navigation modes

The Jupiter 20 GPS receiver supports 3D (three‑dimensional) and 2D (two‑dimensional) modes

of navigation.

3D navigation: The receiver defaults to 3D navigation when at least four GPS satellites are being

tracked. In 3D navigation, the receiver computes latitude, longitude, altitude, and time from

satellite measurements.

2D navigation: When less than four GPS satellite signals are available, or when a ﬁxed altitude

value can be used to produce an acceptable navigation solution, the receiver will enter 2D

navigation mode using a ﬁxed value of altitude determined by the host. Forced operation in 2D

mode can be commanded by the host.

In 2D navigation, the navigational accuracy is primarily determined by the relationship of the

ﬁxed altitude value to the true altitude of the antenna. If the ﬁxed value is correct, the speciﬁed

horizontal accuracies apply. Otherwise, the horizontal accuracies will degrade as a function of

the error in the ﬁxed altitude.

3.8 Core processor performance

The standard Jupiter 20 with GSW2 software runs at a CPU clock speed of 12.28MHz. Using

XTrac software (Jupiter 20S), the clock speed increases to 24.5MHz. An SDK (Software

Development Kit) is available from SiRF to customise the Jupiter 20 ﬁrmware. Using the SiRF

SDK the clock speed can be increased up to 49MHz.

The processing power used by the navigation software is shown in Table 3‑2.

Parameter

J20/J20D

2‑3 MIPS

6‑7 MIPS

J20S

typical performance

peak performance

4‑5 MIPS

8‑9 MIPS

Table 3-2: Software processing performance

3.9 Sensitivity

The GPS receiver performance of the Jupiter 20 is shown in Table 3‑3.

Parameter

J20/J20D

J20S

–135dBm

acquisition sensitivity

navigation sensitivity

tracking sensitivity

–135dBm

33dBHz

28dBHz

26dBHz

33dBHz

17dBHz

15dBHz

–141dBm

–143dBm

–152dBm

–154dBm

Table 3-3: GPS receiver performance

ꢄ

3.10 Dynamic constraints

The Jupiter 20 receiver is programmed to deliberately lose track if any of the following limits are

exceeded:

Velocity:

500m/s max

Acceleration: 4G (39.2m/s²) max

Vehicle jerk: 5m/s³max

Altitude:

18000m max (referenced to MSL)

3.11 Position and velocity accuracy

The position and velocity accuracy of the Jupiter 20 are shown in Table 3‑4, assuming full

accuracy C/A code (Clear/Acquisition). These values are the same in normal operation and

when TricklePower is active.

Parameter

horizontal CEP

J20/J20D

2.1m

J20S

2.2m

horizontal (2dRMS)

vertical VEP

5.2m

5.5m

2.5m

velocity 2D (2 sigma)*

*at a velocity greater than ꢁkm/h

0.1m/s

0.15m/s

Table 3-4: Position and velocity accuracy

4.0 Electrical requirements

4.1 Power supply

4.1.1 Primary power

The Jupiter 20 GPS receiver is designed to operate from a single supply voltage, meeting the

requirements shown in Table 4‑1.

Parameter

input voltage

J20

2.9 to 3.6VDC

75mA

J20S

2.9 to 3.6VDC

85mA

J20D

2.9 to 3.6VDC

80mA

current (typ) at full power (3.3V)

current (max)

100mA

current (typ) at 20% TricklePower^TM

battery backup voltage

battery backup current

maximum rise time

35mA

60mA

35mA

2.4V to 3.6V

<10µA typ at 25°C

unlimited

ripple

not to exceed 50mV peak to peak

Table 4-1: Operating power for the Jupiter 20

4.1.2 Low supply voltage detector

The module will enter a reset mode if the main supply drops below 2.8V.

4.1.3 VCC_RF power supply

The VCC_RF (pad 20) provides a regulated 2.8V power source. The speciﬁcations for this

supply are as follows:

voltage: 2.8V ± 2%

current max: 25mA for J20/J20S; 5mA for J20D

ꢅ

4.1.4 External antenna voltage

DC power is supplied to the external antenna through the antenna power input pad (VANT).

The receiver does not use this supply. The DC supply to the RF connection does not current

limit in the event of a short circuit. Reference designs for antenna current limit are available in

the Jupiter 20 Integrator’s manual (LA000508).

The external antenna characteristics are as follows:

voltage (typ): 3.3V

voltage max: 12V

current max: 100mA

Warning: if the antenna or its cable develops a short circuit and the external antenna

current is not limited, the GPS receiver will experience permanent damage.

4.1.5 RF (Radio Frequency) input

RF input is 1575.42MHz (L1 Band) at a level between –135dBm and –152dBm into a 50ohm

impedance. This input may have a DC voltage impressed upon it to supply power to an active

antenna. The maximum input return loss is –9 dB.

4.1.6 Antenna gain

The receiver will operate with a passive antenna of unity gain. However, GPS performance

will be optimum when an active antenna is used. The gain of this antenna should be in the

range of 20dB to 30dB.

4.1.7 Burnout protection

The receiver accepts without risk of damage a signal of +10dBm from 0 to 2GHz carrier

frequency, except in band 1560 to 1590 MHz where the maximum level will be –10dBm.

4.1.8 Jamming performance

The typical jamming performance of the receiver based upon a 3dB degradation in C/N₀

(Carrier to Noise power ratio) performance is shown in Table 4‑2. This is with reference to the

external antenna.

Jamming signal

Frequency MHz

power dBm

1400

1425.42

1530

–19

–16

–27

–69

–114

–33

–19

1555

1575.42

1625.42

1725.42

Table 4-2: Typical jamming performance

4.1.9 Flash upgradability

The ﬁrmware programmed in the Flash memory may be upgraded via the serial port. The

user can control this by pulling the Serial BOOT pad (3) high at startup, then downloading the

code from a PC with suitable software (e.g. SiRFFlash). In normal operation this pad should

be left ﬂoating for minimal current drain. It is recommended that in the user’s application, the

BOOT pad is connected to a test pad for use in future software upgrades.

4.1.10 Reset input

This active low input (pad 22) allows the user to restart the software from an external signal.

It is also used to initiate a ‘push‑to‑ﬁx’ navigation cycle. In normal operation this pad should

be left ﬂoating or activated by an open drain driver. Active pull‑up is not recommended.

4.2 Data input output speciﬁcations

All communications between the Jupiter 20 receiver and external devices are through the I/O

surface mount pads. These provide the contacts for power, ground, serial I/O and control. Power

requirements are discussed in Section 4.1.

4.2.1 Voltage levels

The I/O connector voltage levels measured at PWR_IN = 3V are shown in Table 4‑3.

Signal

Parameter

V_IH(min)

Value

2.0V

V_IH(max)

PWR_IN +0.1V

0.1V

V_IL(min)

TXD & RXD

GPIOs

SPI bus

V_IL(max)

0.8V

2.0V

V_OH(min) at I_OH2mA

V_OH(max)

PWR_IN

V_OL(min)

1.0V

V_OL(max) at I_OL–2mA

max capacitance Cmax

input current max

pulse time min

100pF

–600μA

200μs

Reset input*

*Reset input should not be driven high by external circuits. It

is recommended that this input is driven low by an open drain

interface.

Table 4-3: Interface voltage levels

4.2.2 I/O surface mount pads

Details of the surface mount pad functions are shown in Table 4‑4 and 4‑5.

Pad

No.

Name

Type

Description

gyro input (analogue 0–5V)

GYRO_IN

FWD/REV

27*

28*

fwd/rev input (low=forward, high=reverse)

wheel tick input

WHEEL_TICKS

* See also Table ꢀ‑ꢁ for J20/J20S pad functions

Table 4-4: J20D receiver pad functions

Pad

No.

Name

Type

Description

main power input (3.3V)

PWRIN

GND

ground

serial boot (high for serial boot, low or open circuit for

normal operation)

BOOT

RXA

TXA

TXB

RXB

CMOS level asynchronous input for UART A

CMOS level asynchronous output for UART A

CMOS level asynchronous output for UART B

CMOS level asynchronous input for UART B

GPIO3/

ADC_CONV/

NANT_SC

general purpose IO/

output for external A/D converter control/

antenna short circuit sensor input (active low)

output to indicate whether the RF section is enabled

(active high)

RF_ON

GND

ground

GND

ground

GND

ground

GND

ground

GND

ground

GND

ground

RF_IN

antenna signal input

GND

ground

V_ANT

external power supply for active antenna

RF Power (+2.8V) supply output

backup battery input

VCC_RF

V_BATT

RESET

GPIO10/GPS_FIX

GPIO6/SDO

GPIO5/SDI

GPIO7/SCK

master reset (active low)

general purpose IO or GPS ﬁx indication (active low)

general purpose IO or SPI serial data out

general purpose IO or SPI serial data in

general purpose IO or SPI serial clock

GPIO15/

ANT_OC

general purpose IO/

antenna open circuit sensor input (active high)

27*

28*

GPIO1/

ANT_CTRL

general purpose IO/

antenna DC power control output (ON=high)

GPIO9/1PPS

GND

general purpose IO or 1 pulse per second output

ground

* See also Table ꢀ‑ꢀ for J20D pad functions

Table 4-5: J20/J20S receiver pad functions

5.0 Software interface

The host serial I/O port of the receiver’s serial data interface supports full duplex communication

between the receiver and the user. The default serial modes are shown in Table 5‑1.

J20

(GSW2.3)

J20S

(XTrac)

J20D

(SiRFDRive 1.0)

Port

Port A

Port B

NMEA, 9600

RTCM, 9600

NMEA, 9600

RTCM, 9600

SiRF binary, 38400

Table 5-1: Jupiter 20 default baud rates

5.1 NMEA output messages

The output NMEA (0183 v2.2) messages and intervals for the receiver are listed in Table 5‑2.

A complete description of each NMEA message is contained in the Navman NMEA reference

manual (MN000315).

NMEA message

GGA

J20

N/A

J20S

J20D

GSA

GSV

RMC

VTG

GLL

ZDA

N/A

PTTK, DR

N/A=not available

Table 5-2: Default NMEA messages

5.2 SiRF binary

A complete description of each binary message is contained in the SiRF Binary Protocol

reference manual.

5.3 Software functions and capabilities

The Jupiter 20 has additional capabilities to the standard SiRF GPS software:

• GPS ﬁx output – GPIO10 Low for 2D or 3D ﬁx

• GPIO command control via serial commands – for use by customer

• Gyro, wheel‑tick and forward reverse inputs (DR only)

• Antenna power monitor messages and power control O/P (non DR only)

• PTTK, DR – DR status messages in NMEA protocol format

Refer to the Jupiter 20 Integrator’s manual (LA000508) for further information.

Table 5‑3 shows the software features available with the Jupiter 20 conﬁgurations.

Feature

Description

J20

GSW2.3

J20S

XTrac

J20D

SiRFDrive

Improves position accuracy by using freely available

SBAS capability satellite‑based correction services called SBAS (Satellite

Based Augmentation System)

DGPS ready

TricklePower

Accepts DGPS corrections in the RTCM SC‑104 format

Improves battery life using this enhanced power management

mode

Adaptive

TricklePower

Intelligently switches between TricklePower and full power

depending on the current GPS signal level (when TricklePower

is enabled)

yes

Advanced power Improves battery life using a software‑based power

management

Push‑to‑Fix

Provides an on‑demand position ﬁx mode designed to further

improve battery life

Almanac to

Flash

Improves cold start times by storing the most recent almanac to

ﬂash memory

yes

Low signal

acquisition

Acquires satellites and continues tracking in extremely low

signal environments

yes

Low signal

navigation

Continues navigating in extremely low signal environments

1 PPS

A timing signal generated every second on the second

yes=always enabled A=available E=enabled by default in production units

Table 5-3: Jupiter 20 software capability

6.0 Dead Reckoning input speciﬁcations

6.1 Gyro input speciﬁcation

The speciﬁcations shown in Table 6‑1 apply to the Jupiter 20D only.

Characteristics

input max voltage range

input resistance nominal

nominal bias at zero angular velocity

nominal scale factor

Value

max +5, min 0

18.2

Unit

VDC

kΩ

2.5

VDC

22.2

mV per degrees/s

linearity

±0.5 max

0.055

angular resolution

degrees/s

max gyro angular rate

±80

Note that clockwise rotation should cause the input to rise

Table 6‑1: Gyro input speciﬁcations

At the time of publication, recommended manufacturers of gyros are as follows:

Murata ENV series

Panasonic EWTS series

(Navman takes no responsibility for the use of these gyros in an application.)

6.2 Wheel tick rate

The wheel tick rate is 4kHz maximum, 1Hz minimum.

6.3 Fwd/Rev input sense

The fwd/rev input sense is: LOW=forward, HIGH=reverse. External pull down is required if this

input is not used.

1ꢀ

7.0 Jupiter 20 development kit

The Jupiter 20 Development kit series assists in the integration of the Jupiter 20 module

in custom applications. The Development kit contains all of the necessary hardware and

software to carry out a thorough evaluation of the Jupiter 20 module. Refer to the Jupiter Series

Development kit guide (LA000645) for further details.

The following development kits are available for Jupiter 20 products:

• TU10‑D057‑400 Jupiter 20 Development kit RoHS

• TU10‑D057‑401 Jupiter 20 S Development kit RoHS

• TU10‑D057‑402 Jupiter 20 DR Development kit RoHS

8.0 Jupiter 20 mechanical drawing

25.4 ± 0.1

top view

3.0 max

side view

3.0 max

R0.4

side view

detail A

1.0

23.4

scale 6:1

bottom view

all dimensions are in mm

Figure 8-1: Jupiter 20 mechanical layout

1ꢁ

9.0 Product handling

9.1 Packaging and delivery

Jupiter 20 modules are shipped in Tape and Reel form. The reeled modules are shipped with

250 units per 300x44mm (DxW) reel with a pitch of 32mm. Each reel is ‘dry’ packaged and

vacuum sealed in an MMB (Moisture Barrier Bag) with two silica gel packs and placed in a

carton.

The MOQ (Minimum Order Quantity) for shipping is 250 units.

All packaging is ESD protective lined. Please follow the MSD and ESD handling instructions on

the labels of the MMB and exterior carton (refer to sections 9.2 and 9.3).

9.2 Moisture sensitivity

The Jupiter 20 GPS receiver is an MSD (Moisture Sensitive Device). Precautionary measures

are required in handling, storing and using such devices to avoid damage from moisture

absorption. If localised heating is required to rework or repair the device, precautionary methods

are required to avoid exposure to solder reﬂow temperatures that can result in performance

degradation.

Further information can be obtained from the IPC/JEDEC standard J‑STD‑033: Handling,

Packing, Shipping and Use of Moisture/Reﬂow Sensitive Surface Mount Devices.

9.3 ESD sensitivity

The Jupiter 20 GPS receiver contains class 1 devices and is ESDS (ElectroStatic Discharge

Sensitive). Navman recommends the two basic principles of protecting ESDS devices from

damage:

• Only handle sensitive components in an ESD Protected Area (EPA) under protected and

controlled conditions

• Protect sensitive devices outside the EPA using ESD protective packaging

All personnel handling ESDS devices have the responsibility to be aware of the ESD threat to

reliability of electronic products.

Further information can be obtained from the IEC Technical Report IEC61340‑5‑1 & 2:

Protection of electronic devices from electrostatic phenomena.

9.4 Safety

Improper handling and use of the Jupiter GPS receiver can cause permanent damage to the

receiver and may even result in personal injury.

9.5 RoHS compliance

This product complies with Directive 2002/95/EC on the restriction of the use of certain

hazardous substances in electrical and electronic equipment.

9.6 Disposal

We recommend that this product should not be treated as household waste. For

more detailed information about recycling of this product, please contact your local

waste management authority or the reseller from who you purchased the product.

1ꢂ

10.0 Ordering information

The part numbers of the Jupiter 20 variants are shown in Table 10‑1.

Part Number

TU20‑D411‑001

TU20‑D411‑101

TU20‑D421‑201

TU20‑D101‑001

TU10‑D007‑400

TU10‑D007‑401

TU10‑D007‑402

Description

Jupiter 20 (standard)

Jupiter 20S (with XTrac)

Jupiter 20D (with Dead Reckoning)

Jupiter 20 std adapter

Jupiter 20 std development kit

Jupiter 20S development kit

Jupiter 20D development kit

Table 10-1: Jupiter 20 ordering information

11.0 Glossary and acronyms

2dRMS: twice distance Root Mean Square

ADC: Analogue to Digital Converter

Almanac: A set of orbital parameters that allows calculation of approximate GPS satellite

positions and velocities. The almanac is used by a GPS receiver to determine satellite visibility

and as an aid during acquisition of GPS satellite signals. The almanac is a subset of satellite

ephemeris data and is updated weekly by GPS Control.

C/A code: Coarse Acquisition code

A spread spectrum direct sequence code that is used primarily by commercial GPS receivers to

determine the range to the transmitting GPS satellite.

DGPS: Differential GPS

A technique to improve GPS accuracy that uses pseudo‑range errors recorded at a known

location to improve the measurements made by other GPS receivers within the same general

geographic area.

GDOP: Geometric Dilution of Precision

A factor used to describe the effect of the satellite geometry on the position and time accuracy

of the GPS receiver solution. The lower the value of the GDOP parameter, the less the error in

the position solution. Related indicators include PDOP, HDOP, TDOP and VDOP.

EGNOS: European Geostationary Navigation Overlay Service

The system of geostationary satellites and ground stations developed in Europe to improve the

position and time calculation performed by the GPS receiver.

Ephemeris

A set of satellite orbital parameters that is used by a GPS receiver to calculate precise GPS

satellite positions and velocities. The ephemeris is used to determine the navigation solution and

is updated frequently to maintain the accuracy of GPS receivers.

GPS: Global Positioning System

A space‑based radio positioning system that provides accurate position, velocity, and time data.

OEM: Original Equipment Manufacturer

Re-acquisition

The time taken for a position to be obtained after all satellites have been made invisible to the

receiver.

SBAS: Satellite Based Augmentation System

Any system using a network of geostationary satellites and ground stations to improve the

performance of a Global Navigation Satellite System (GNSS), e.g. EGNOS and WAAS.

SRAM: Static Random Access Memory

WAAS: Wide Area Augmentation System

System of satellites and ground stations developed by the FAA (Federal Aviation Administration)

providing GPS signal corrections. (Currently available for North America only.)

1ꢃ

SiRF and SiRF logo are registered trademarks of SiRF Technology, Inc. SiRFstar, Push‑to‑Fix, and TricklePower are

trademarks of SiRF Technology, Inc. All other trademarks mentioned in this document are property of their respective

owners.

Information in this document is provided in connection with Navman New Zealand (‘Navman’) products. These materials

are provided by Navman as a service to its customers and may be used for informational purposes only. Navman

assumes no responsibility for errors or omissions in these materials. Navman may make changes to speciﬁcations and

product descriptions at any time, without notice. Navman makes no commitment to update the information and shall have

no responsibility whatsoever for conﬂicts or incompatibilities arising from future changes to its speciﬁcations and product

descriptions. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by

this document. Except as provided in Navman’s Terms and Conditions of Sale for such products, Navman assumes no

liability whatsoever.

THESE MATERIALS ARE PROVIDED ‘AS IS’ WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR

IMPLIED, RELATING TO SALE AND/OR USE OF NAVMAN PRODUCTS INCLUDING LIABILITY OR WARRANTIES

RELATING TO FITNESS FOR A PARTICULAR PURPOSE, CONSEQUENTIAL OR INCIDENTAL DAMAGES,

MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY

RIGHT. NAVMAN FURTHER DOES NOT WARRANT THE ACCURACY OR COMPLETENESS OF THE INFORMATION,

TEXT, GRAPHICS OR OTHER ITEMS CONTAINED WITHIN THESE MATERIALS. NAVMAN SHALL NOT BE

LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT

LIMITATION, LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS.

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. Product names or services listed in this publication are for

identiﬁcation purposes only, and may be trademarks of third parties. Third‑party brands and names are the property

of their respective owners. Additional information, posted at www.navman.com, is incorporated by reference. Reader

response: Navman strives to produce quality documentation and welcomes your feedback. Please send comments

and suggestions to [email protected]. For technical questions, contact your local Navman sales ofﬁce or ﬁeld

applications engineer.

1ꢄ

Miller Electric Bicycle Accessories Digital Elitet User Manual
Musical Fidelity Stereo Amplifier X A50 User Manual
National Geographic Digital Photo Frame NG1050 User Manual
Navman GPS Receiver M Nav 650 User Manual
Niles Audio Speaker CM963 User Manual
Nokia Network Router A032 User Manual
Omron Healthcare Scale HBF 516 User Manual
Onkyo Radio T 4555P User Manual
Panasonic VCR AJ PD950 User Manual
Parasound TV Converter Box D A C 1500 User Manual