Navman Jupiter 110 User manual

LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
Related documents
• Jupiter 110 Product brief LA000511
• Low Power Operating Modes application
note LA000513
• Navman NMEA reference manual
MN000315
• SiRF Binary protocol reference manual
Jupiter 110
Integrated GPS Sensor
Module
Data Sheet/
Integrator’s Manual
Downloaded from Arrow.com.

LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
Contents
Related documents................................................................................................. 1
1.0 Introduction ....................................................................................................... 4
2.0 Technical description ....................................................................................... 4
2.1 Receiver architecture.................................................................................................... 4
2.2 Major components of the Jupiter 110 ........................................................................... 5
2.3 Product applications..................................................................................................... 5
2.4 Physical characteristics................................................................................................ 5
2.5 Mechanical specication .............................................................................................. 5
2.6 Environmental .............................................................................................................. 5
2.7 Compliances................................................................................................................. 6
2.8 Marking/serialisation .................................................................................................... 6
3.0 Performance characteristics ........................................................................... 7
3.1 TTFF (Time To First Fix)............................................................................................... 7
3.1.1 Hot start ................................................................................................................ 7
3.1.2 Warm start............................................................................................................ 7
3.1.3 Cold start .............................................................................................................. 7
3.2 Acquisition times .......................................................................................................... 7
3.3 Battery backup ............................................................................................................. 7
3.4 Power management ..................................................................................................... 7
3.4.1 TricklePower mode ............................................................................................... 7
3.5 Differential aiding WAAS/EGNOS................................................................................ 8
3.6 Navigation modes......................................................................................................... 8
3.7 Core processor performance ....................................................................................... 8
3.8 Dynamic constraints..................................................................................................... 8
3.9 Position and velocity accuracy ..................................................................................... 8
4.0 Electrical requirements .................................................................................... 9
4.1 Power supply ................................................................................................................ 9
4.2 RF sensitivity................................................................................................................ 9
4.2.1 Internal patch antenna.......................................................................................... 9
4.2.2 External RF connector ......................................................................................... 9
4.3 Data input/output levels...............................................................................................10
5.0 Interfaces......................................................................................................... 10
5.1 External antenna connector ........................................................................................10
5.1.1 External antenna voltage .....................................................................................10
5.2 External I/O connector ................................................................................................11
5.2.1 I/O connector signals...........................................................................................11
5.2.2 I/O connector description....................................................................................11
6.0 Software protocol ........................................................................................... 12
6.1 NMEA output ...............................................................................................................12
6.2 Navman NMEA low power mode messages...............................................................12
6.2.1 Low power conguration .....................................................................................12
6.2.2 Low power acquisition conguration...................................................................13
6.3 Navman NMEA active antenna status message.........................................................13
6.4 SiRF binary output ......................................................................................................13
Downloaded from Arrow.com.Downloaded from Arrow.com.

LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
Tables
Table 3-1: Acquisition times................................................................................................ 7
Table 3-2: Jupiter 110 processor performance................................................................... 8
Table 3-3: Position and velocity accuracy.......................................................................... 8
Table 4-1: Operating power for the Jupiter 110 .................................................................. 9
Table 4-2: RF sensitivity at patch antenna ......................................................................... 9
Table 4-3: RF sensitivity at external RF connector ............................................................ 9
Table 4-4: Input/output voltage levels ...............................................................................10
Table 5-1: External antenna characteristics ......................................................................10
Table 5-2: Module I/O pinouts ...........................................................................................11
Table 5-3: I/O connector part numbers .............................................................................11
Table 6-1: NMEA default settings......................................................................................12
Table 6-2: Low power modes message values .................................................................12
Table 6-3: Low power acquisition input values..................................................................13
Table 6-4: Antenna status output message values ...........................................................13
Table 10-1: Jupiter 110 ordering information .....................................................................16
Figures
Figure 2-1: Jupiter 110 architecture .................................................................................... 4
Figure 2-2: Application example......................................................................................... 6
Figure 5-1: Pinout I/O connector .......................................................................................11
Figure 9-1: Jupiter 110 mechanical layout .........................................................................15
7.0 Mounting option .............................................................................................. 14
8.0 Product handling............................................................................................. 14
8.1 Packaging and delivery ...............................................................................................14
8.2 ESD sensitivity ............................................................................................................14
8.3 Safety ..........................................................................................................................14
8.4 RoHS compliance .......................................................................................................14
8.5 Disposal ......................................................................................................................14
9.0 Jupiter 110 mechanical layout ....................................................................... 15
10.0 Ordering information .................................................................................... 16
11.0 Glossary and acronyms................................................................................ 16
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

LNA
patch
antenna
RTC crystal
serial data in
serial data out
+ power in
GND
RTC backup
battery
backup
RFIC
TCXO
bandpass
lter
2.8 V
regulator
baseband
processor
Flash
memory
1.8 V
regulator
voltage
detector
BOOT CMOS serial IO
external
antenna
sense
external
antenna
input
reset
voltage
detector
antenna
switch
4
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
1.0 Introduction
The Jupiter 110 sensor module is based on the SiRFstarIIe/LP navigation engine and provides
OEMs with an ideal integrated solution for cost effective GPS based navigation and tracking
systems.
The module continuously tracks all satellites in view and uses enhanced ltering to provide
fast and accurate positioning information, even in dense urban environments. The sensor
combines advanced performance, compact form factor and very low current consumption in an
economically priced package.
2.0 Technical description
The Jupiter 110 module provides a 12-channel GPS receiver and patch antenna in an open
board design that is compact, versatile and easy to adopt. The Jupiter 110 is available in four
congurations:
• Jupiter 110 (standard) – GSW2 navigation software
• Jupiter 110R – supports an external RF antenna
• Jupiter 110S (high sensitivity) – XTrac positioning software
• Jupiter 110RS – XTrac positioning software and external RF antenna support
The Jupiter 110 variants can be mounted externally or internal to a wide variety of devices,
including PDAs, smartphones, hand-held radios and data terminals.
Protocols supported are selected NMEA (National Marine Electronics Association) data
messages and SiRF binary. The default setting is NMEA-0183 (v2.2).
2.1 Receiver architecture
The functional architecture of the module receiver is shown in Figure 2-1.
Figure 2-1: Jupiter 110 architecture
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

5
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
2.2 Major components of the Jupiter 110
Antenna: The antenna receives the GPS signals.
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.575 GHz): 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): The highly stable 24.5535 MHz
temperature compensated crystal oscillator is required as the reference for the local oscillator.
Stability in this frequency is required to achieve a fast TTFF (Time To First Fix).
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 serial port.
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 block, and provides an accurate clock function when main power has been
removed.
Regulators: The regulators provide a clean and stable voltage supply to the components in the
receiver.
2.3 Product applications
The module is suitable for a wide range of integrated OEM GPS design applications such as:
PDAs and smartphones with integrated navigation
custom navigation and tracking equipment
on-board equipment for eet management
Figure 2-2 shows an example of a personal navigation system based on a Pocket PC, with the
integrated sensor module housed inside a custom ip-up enclosure.
2.4 Physical characteristics
The Jupiter 110 is an open frame structure on a single PCB, with patch antenna mounted on the
upper surface and the GPS receiver components housed on the lower surface.
2.5 Mechanical specication
The physical dimensions of the Jupiter 110 are as follows:
length: 39.0 mm
width: 34.0 mm
thickness (without external RF connector): 6.8 mm
thickness (with external RF connector): 8.3 mm
weight: 11 g
2.6 Environmental
The environmental operating conditions of the Jupiter 110 are as follows:
temperature: –40ºC to +85º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
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

6
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
2.7 Compliances
The Jupiter 110 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.8 Marking/serialisation
The Jupiter 110 supports a 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
•
•
•
•
Figure 2-2: Application example
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

7
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
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 TTFF 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, time and satellite ephemeris) is valid
to the specied accuracy and available in SRAM.
3.1.2 Warm start
A warm TTFF typically results from user-supplied position and time initialisation data or
continuous RTC operation with an accurate last known position available. In this state,
position and time data are present and valid but ephemeris data validity has expired.
3.1.3 Cold start
A cold TTFF acquisition state results when position or time data is unknown. Almanac
information stored in Flash memory 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.
Mode
J110/J110R J110S/J110RS
Typ 90% Typ 90%
TTFF hot (valid almanac, position, time & ephemeris) 8 s 12 s 8 s 12 s
TTFF warm (valid almanac, position & time) 38 s 42 s 38 s 40 s
TTFF cold (valid almanac) 44 s 55 s 45 s 56 s
re-acquisition (<10 s obstruction with valid almanac,
position, time & ephemeris) 100 ms 100 ms 100 ms 100 ms
Table 3-1: Acquisition times
3.3 Battery backup
The battery backup input line powers the RTC section of the baseband receiver. Supplying
power to this pin is required for normal operation and ensures that the RTC continues to operate
even when the main power is interrupted. Refer to Table 4-1 for the Jupiter 110 battery backup
supply voltages.
3.4 Power management
During normal operating mode the Jupiter 110 runs continuously, providing a navigation solution
at a maximum rate of once per second. This continuous mode provides no power saving. For
power saving, TricklePower mode can be set using NMEA or SiRF Binary messages.
3.4.1 TricklePower mode
The TricklePower mode can be enabled to reduce 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 become 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.
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.
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

8
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
If the ephemeris data become invalid, the RTC has the ability to self activate and refresh the
data, thus keeping the restart TTFF very short.
For further information about TricklePower refer to the Low Power Operating Modes
application note (LA000513).
3.5 Differential aiding WAAS/EGNOS
The Jupiter 110 is capable of receiving WAAS and EGNOS differential corrections. WAAS/
EGNOS improves horizontal position accuracy to <6 m 2 dRMS by correcting GPS signal errors
caused by ionospheric disturbances, timing and satellite orbit errors.
3.6 Navigation modes
The Jupiter 110 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
information 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 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.7 Core processor performance
The standard Jupiter 110 with GSW2 software runs at a CPU clock speed of 12.28 MHz. Using
XTrac software (Jupiter 110S and 110RS), the clock speed increases to 24.5 MHz. An SDK
(Software Development Kit) is available from SiRF to customise the Jupiter 110 rmware. Using
the SiRF SDK the clock speed can be increased up to 49 MHz.
The processor performance of the Jupiter 110 is shown in Table 3-2.
Parameter J110/J110R J110S/J110RS
typical performance 2-3 MIPS 4-5 MIPS
peak performance 6-7 MIPS 8-9 MIPS
Table 3-2: Jupiter 110 processor performance
3.8 Dynamic constraints
The Jupiter 110 is programmed to lose track if any of the following limits is exceeded:
Velocity: 500 m/s max
Acceleration: 4 G (39.2 m/s/s) max
Altitude: 18 000 m
3.9 Position and velocity accuracy
Position and velocity accuracy of the Jupiter 110 are shown in Table 3-3, assuming full accuracy
C/A code. These values are the same in normal operation and when TricklePower is active.
Parameter J110/J110R J110S/J110RS
horizontal CEP 2.2 m 3.0 m
horizontal (2 dRMS) 5.5 m 6.0 m
vertical VEP 2.5 m 5.0 m
3D SEP 5.0 m 5.0 m
velocity 3D (2 sigma) 0.1 m/s 0.1 m/s
Table 3-3: Position and velocity accuracy
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

9
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
4.0 Electrical requirements
4.1 Power supply
The module is designed to operate using the supply voltages shown in Table 4-1. These values
do not include external antenna current on the J110R and J110RS.
Parameter J110/J110R J110S/J110RS
input voltage 3.0 to 3.6 VDC 3.0 to 3.6 VDC
current (typ) at full power (3.3 VDC) 75 mA 85 mA
current (max) 100 mA 100 mA
current (typ) at 20% TricklePower 35 mA 60 mA
battery backup voltage 2.0 to 3.6 VDC 2.0 to 3.6 VDC
battery backup current (non-operating) <10 µA at 25ºC <10 µA at 25ºC
battery backup current (operating mode) 18 µA typ, 50 µA max 18 µA typ, 50 µA max
Table 4-1: Operating power for the Jupiter 110
4.2 RF sensitivity
4.2.1 Internal patch antenna
The RF sensitivity measured at the internal patch antenna is shown in Table 4-2.
Parameter J110 J110S
acquisition sensitivity 33 dBHz 30 dBHz
tracking sensitivity 25 dBHz 14 dBHz
navigation sensitivity 28 dBHz 17 dBHz
Table 4-2: RF sensitivity at patch antenna
4.2.2 External RF connector
The RF sensitivity measured at the external RF connector using a 21 dB gain amplier is
shown in Table 4-3.
Parameter J110R J110RS
acquisition sensitivity –135 dBm –138 dBm
tracking sensitivity –144 dBm –155 dBm
navigation sensitivity –141 dBm –154 dBm
Table 4-3: RF sensitivity at external RF connector
Note: The external antenna input requires additional signal gain in the external antenna.
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

10
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
4.3 Data input/output levels
All communication between the Jupiter 110 and external devices is through the I/O (input/output)
connector. The I/O data is CMOS serial.
The I/O connector voltage levels measured at PWR_IN = 3 V are shown in Table 4-4.
Signals Parameter Value
TXD, RXD
& BOOT
VIH (min) 2.0 V
VIH (max) PWR_IN +0.1
VIL (min) 0.1 V
VIL (max) 0.8 V
VOH (min) at IOH 0.5 mA 2.0 V
VOH (max) PWR_IN
VOL (min) 0
VOL (max) at IOL –0.5 mA 1.0 V
Table 4-4: Input/output voltage levels
5.0 Interfaces
5.1 External antenna connector
The RF connector for the external antenna is an MMCX type jack straight connector. This
connector is available on the Jupiter 110R and the Jupiter 110RS.
5.1.1 External antenna voltage
DC power is supplied to the external antenna from the main power supply via the internal
antenna selection switch.
The external antenna characteristics are shown in Table 5-1.
Parameter External
antenna current Notes
internal patch antenna to external
antenna switchover threshold 5 mA
external antenna to internal patch
antenna switchover threshold 1 mA
reducing the external antenna current
from 5 to 1 mA will result in switchback
to the internal patch antenna
external antenna over current
latch threshold 80 mA
external antenna over current
reset threshold 200 µA
reducing the current from 80 mA to
200 µA, or no load, will result in the
DC supply being made available to the
internal patch antenna. To reset the
‘over current’ trip, remove power from
the unit for >3 s.
Table 5-1: External antenna characteristics
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

11
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
5.2 External I/O connector
The input/output connector is a 6-pin header, organised in a single row. Figure 5-1 shows the
layout of the connector, viewed looking into the pins.
1 2 3 4 5 6
PCB
Figure 5-1: Pinout I/O connector
5.2.1 I/O connector signals
Table 5-2 shows the name and function of each connector pin.
Pin no. Name Description
1 PWR_IN primary VDC power input (DC)
2 VBATT battery backup voltage (DC)
3 TXD serial data output port 1
4RXD serial data input port 1
5 BOOT boot pin (active high)
6 GND ground
Table 5-2: Module I/O pinouts
Pin 2: VBATT Voltage
This pin provides the battery backup power to run the RTC. This voltage must be supplied
during normal mode of operation even when battery backup is not required.
Pin 3: Host port serial data output (TXD)
The host port consists of a full-duplex asynchronous serial data interface. Both binary and
NMEA initialisation and conguration data messages are transmitted and received across
this port. Port Idle is a CMOS logic high level.
Pin 4: Host port serial data input 1 (RXD)
This is the data input to the module.
Pin 5: BOOT
Pull this pin high during start-up to reprogram the Flash memory.
5.2.2 I/O connector description
The part numbers relating to the I/O connector are shown in Table 5-3.
Part description Part number Manufacturer
Jupiter 110 connector JST-SM06B-SRSS-TB JST
Suggested mating connector 06SR-3S JST
Table 5-3: I/O connector part numbers
Refer to the JST website for further details (www.jst.com). A mating connector and cable
assembly (Navman part number CB000222D) can be supplied optionally by Navman.
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

12
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
6.0 Software protocol
The following sections describe the software protocol, including the default NMEA-0183 (v2.2)
protocol.
6.1 NMEA output
The Jupiter 110 has a default data transmission speed of 9 600 Baud. The update rate is once
per second.
The conguration parameters set via the NMEA command sentences are stored in battery
backed memory and will be used at power up. If the battery backup is unavailable, the default
settings shown in Table 6-1 will be used.
Refer to the Navman NMEA reference manual (MN000315) for a full list of the NMEA
commands.
NMEA sentence Factory default
GGA – global positioning system x data on
GLL – geographic position - latitude/longitude off
GSA – DOP and active satellites on
GSV – satellites in view on
RMC – recommended minimum specic GNSS data on
VTG – course over ground and ground speed on
ZDA – time & date (J110 and J110R only) off
Table 6-1: NMEA default settings
6.2 Navman NMEA low power mode messages
Navman has added proprietary NMEA input messages to congure the TricklePower mode.
6.2.1 Low power conguration
The following message sets the receiver to low power mode:
$PSRF151,a,bbbb,cccc*CS
where:
Field Description
aPush-To-Fix = 0 (always off)*
bTricklePower duty cycle (parts per
thousand)
c TricklePower on time (milliseconds)
* Push-to-x is not supported.
Table 6-2: Low power modes message values
This message is the NMEA equivalent of the SiRF Binary input message ID 151. For
compatibility with ublox products, an identical input message is used with 107 substituted for
151 in the header:
$PSRF107,a,bbbb,cccc*CS
System response:
$PTTK,LPSET,a,bbbb,cccc*CS
The updated values returned by the system are as described in Table 6-2.
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

13
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
6.2.2 Low power acquisition conguration
The following message sets the acquisition parameters of the low power mode:
$PSRF167,aaaa,bbbb,cccc,d[*CS]
where:
Field Description
amaximum off time (milliseconds)
b maximum search time (milliseconds)
cPush-To-Fix period (seconds)
dadaptive TricklePower (1=on, 0=off)
Table 6-3: Low power acquisition input values
This message is the NMEA equivalent of the SiRF Binary input message ID 167.
System response:
$PTTK,LPACQ,aaaa,bbbb,cccc,d*CS
The updated values returned by the system are as described in Table 6-3.
6.3 Navman NMEA active antenna status message
The Jupiter 110 software includes an antenna monitor message driven by the state of the
antenna monitor inputs. The pins GPIO6 (overcurrent detect) and GPIO5 (internal antenna
detect) are congured as inputs (both active high). Note that these pins are not connected to the
input/output connector.
The antenna status output message is an NMEA message in the form:
$PTTK,ANT,d*CS
Where d represents any of the following numbers:
d Description
0using external antenna
1 using internal (patch) antenna
2external antenna short circuit
Table 6-4: Antenna status output message values
The antenna status message is output automatically in the event of an external antenna being
connected or disconnected, or of a short circuit on the external antenna.
In addition, this message is output on the receipt of the NMEA input message:
$PSRF199[*CS]
The antenna status is also output as the SiRF binary message with message ID 99. It contains
one byte of data, being the appropriate value from Table 6-4. This gives a payload length of 2
bytes, since the message ID is considered part of the payload.
The antenna status message is output automatically in the event of an external antenna being
connected or disconnected, or of a short circuit on the external antenna.
In addition, this message is output on the receipt of the SiRF binary message with message ID
199. The output rate of this message is also under the normal control of the SiRF Binary Query/
Rate Control input message, however this message is not output at a regular rate by default.
6.4 SiRF binary output
The NMEA command format to change the data protocol to SiRF binary can be found in the
Navman NMEA reference manual. For a full list of the SiRF binary commands, refer to the SiRF
Binary Protocol reference manual.
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

14
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
7.0 Mounting option
The module is designed for mounting inside a non-metallic enclosure. The recommended
fastening style is with side clips designed into the OEM’s enclosure.
An example of a custom ‘ip-up’ style enclosure is shown in Figure 2-2. Other mounting options
are available on request.
8.0 Product handling
8.1 Packaging and delivery
The Jupiter 110 is packaged individually in sealed anti-static bags in a partitioned box containing
75 modules. The bag is labelled with an ESD Caution (see section 8.2).
The MOQ (Minimum Order Quantity) for shipping is 75 units.
8.2 ESD sensitivity
The Jupiter 110 module 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.
8.3 Safety
Improper handling and use of the Jupiter GPS sensor module can cause permanent damage to
the module and may even result in personal injury.
8.4 RoHS compliance
This product will comply with Directive 2002/95/EC on the restriction of the use of certain
hazardous substances in electrical and electronic equipment from April 2006.
8.5 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 whom you purchased the product.
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

Unless otherwise stated all dimensions are in mm.
Tolerances: 0 ± 0.2 – 0.0 ± 0.1
Note: when tting to housing or enclosure, ensure
there is a minimum air gap of 3.0 mm between any
point on the patch antenna and the plastic housing
components view
side view
patch antenna view
Ø 3.5
RF connector
MMCX Jack
Straight
15.6
3.8
39.0 ± 0.25
34.0 ± 0.25
8.0 8.5
JST connector
JST-SM06B-SRSS-TB
4.3
3.5
4.5
2.5 MAX
0.8
3.0
6.8
15
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
Figure 9-1: Jupiter 110 mechanical layout
9.0 Jupiter 110 mechanical layout
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

16
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
10.0 Ordering information
The part numbers of the Jupiter 110 variants are shown in Table 10-1.
Part Number Description
AA004260 Jupiter 110 (standard)
AA004261 Jupiter 110S (with XTrac software)
AA004250 Jupiter 110R (with external RF antenna support)
AA004263 Jupiter 110RS (with external RF antenna support and XTrac)
Table 10-1: Jupiter 110 ordering information
11.0 Glossary and acronyms
2dRMS: twice-distance Root Mean Square
A horizontal measure of accuracy representing the radius of a circle within which the true value
lies at least 95% of the time.
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.
CEP: Circular Error Probable
The radius of a circle, centred at the user’s true location, that contains 50% or the individual
position measurements made using a particular navigation system.
EGNOS: Euro 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.
I/O: Input/output
MIPS: Millions of Instructions Per Second
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.
SEP: Spherical Error Probable
The radius of a sphere, centred at the user’s true location, that contains 50% of the individual
three-dimensional position measurements made using a particular navigation system.
SRAM: Static Random Access Memory
WAAS: Wide Area Augmentation System
The system of satellites and ground stations developed by the FAA (Federal Aviation
Administration) that provides GPS signal corrections. WAAS satellite coverage is currently only
available in North America.
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.

17
LA000504D © 2006 Navman New Zealand. All rights reserved. Proprietary information and specications subject to change without notice.
TricklePower is a registered trademark of SiRF Technologies
© 2006 Navman New Zealand. All Rights Reserved.
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 tech.
[email protected]. For technical questions, contact your local Navman sales ofce or eld applications engineer.
Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.Downloaded from Arrow.com.