Summary of the content on the page No. 1
Jupiter 30 / 20
GPS receiver module
Integrator’s Manual
Related documents
•Jupiter Series Development kit guide
LA000645
• Navman NMEA reference manual
MN000315
• SiRF Binary Protocol reference manual
LA000577C © 2006 Navman New Zealand. All rights reserved. Proprietary information and specifications subject to change without notice.
Summary of the content on the page No. 2
Contents 1.0 Introduction .......................................................................................................4 2.0 Hardware application information...................................................................4 2.1 Electrical connections (SMT pad interface)................................................................... 4 2.2.Physical.dimensions...................................................................................................... 6 2.3 Manufacturing pr
Summary of the content on the page No. 3
Figures Figure 2-1: Lead-free and tin/lead reflow profile recommendation...................................... 6 Figure 2-2: Sample application circuit................................................................................. 8 Figure 2-3: Recommended application layout dimensions................................................. 9 Figure 2-4: Typical module layout......................................................................................10 Figure 2-5: Example PCB layout for ext
Summary of the content on the page No. 4
1.0 Introduction The Navman Jupiter 30 and Jupiter 20 series of GPS receiver modules are complete GPS receivers designed for surface mount assembly (SMT) integration. The modules provide a simple, cost effective GPS solution for application designers. Application integration will vary primarily with respect to antenna system design and EMI protective circuitry. The Jupiter 30 is the successor to the established Jupiter 20, sharing the same form factor (25.4 x 25.4 mm) and electrical compatib
Summary of the content on the page No. 5
Pin Name Type Description No. 1 PWRIN P main power input (3.3 V) 2 GND P ground serial boot (high for serial boot, low or open circuit 3 BOOT I for normal operation) 4 RXA I CMOS level asynchronous input for UART A 5 TXA O CMOS level asynchronous output for UART A 6 TXB O CMOS level asynchronous output for UART B 7 RXB I CMOS level asynchronous input for UART B 8 pin 8 multi-functional (see table 2-2) output to indicate whether the RF section is 9 RF_ON O enabled (active high) 10 GND P ground
Summary of the content on the page No. 6
Jupiter 30 Jupiter 20 Pin Standard & GPIO Name and Description GPIO DR function XTrac name 24 13 reserved 6 GPIO (SDO) not.connected 25 4 reserved 5 GPIO (SDI) ADC DOut WAKEUP. 26 – 7 GPIO (SCK) ADC Clk push-to-fix wakeup (active on +ve edge) FWD/REV. ANT_OC. fwd/rev input 27 15 antenna open circuit sensor input (active 15 ANT_OC (low=forward,. high) high=reverse) ANT_CTRL. WHEEL_TICKS. 28 1 1 ANT_CTRL active antenna control output wheel tick input NANT_SC. GYRO_IN. 8 14 antenna short circuit
Summary of the content on the page No. 7
2.3.3 Solder paste mask size This should be adjusted by experimentation according to the customer’s production process requirements. A 1:1 (paste mask:pad size) ratio has been found to be successful. 2.3.4 Solder paste type The module accepts all commonly used solder pastes. The solder paste can be lead based or lead-free. If a lead-free process is introduced, factors such as circuit board thickness, fabrication complexity, assembly process compatibility, and surface finish should be taken i
Summary of the content on the page No. 8
2.4.3 Decoupling The schematic in Figure 2-2 illustrates a suggested method of decoupling. These are capacitors C1 to C7. This level of decoupling may not be required in a particular application, in which case these capacitors could be omitted. Only the signal lines used in the application require decoupling. All capacitors are highly recommended if the module will experience substantial electromagnetic interference (EMI). All low value capacitors should be as close as possible to the modul
Summary of the content on the page No. 9
2.4.4 Serial RS232 data level shifter To connect the module to a PC comm. port, the serial data signals must be level shifted to RS232 levels. This has not been shown in the reference design, but many single chip RS232 level shifters are available, such as MAX3232. Note: It is highly recommended to provide test points on the serial data lines and ‘Boot’ signal (pad 3), even if the application circuit does not use these signals. This will allow the user to connect to these signals if a firmwa
Summary of the content on the page No. 10
Ground plane design. We reccomend a complete ground plane is used under the PCB with signal tracks on the same layer as the module. We also recommend having a ground plane on both sides of the PCB underneath the module. If the ground planes are very small, separate analogue and digital ground planes may not be required. The ground return for any signal should have a clear path back to its source and should not mix with other ground return signal paths. Hence the return path, which is the gr
Summary of the content on the page No. 11
Design of 50 ohm microstrip antenna connection. When designing the signal track from the antenna connection to the antenna input on the module, a controlled impedance microstrip with a characteristic impedance of 50 ohms must be used. The PCB parameters that affect impedance are as follows: 1. Track width (W) 2. PCB substrate thickness (H) 3. PCB substrate permittivity ( ε ) r 4. To a lesser extent, PCB copper thickness (T) and proximity of same layer ground plane. Figure 2-6 shows a represen
Summary of the content on the page No. 12
• be interfaced to a coaxial connector if an external antenna is used • have maximum clearance to ground on the same layer, or at least be half the substrate thickness • be routed away from noise sources such as: switching power supplies, digital signals, oscillators.and.transmitters The PCB track connection to the RF antenna input must NOT have: •.vias • sharp bends • components overlaying the track 2.6 Antenna system design choices 2.6.1 Antenna types There are two major types of GPS antenna
Summary of the content on the page No. 13
2.6.3 Passive antenna A passive antenna does not require any power because it has no amplifier. This is not the best choice if signal strength is a concern, however, it may be sufficient if the signal path is kept to a minimum (usually below 300 mm). An advantage to using a passive antenna is the ability to mount directly onto the application. For best performance, a passive patch antenna should have a metal ground plane (about 80 mm in diameter) placed directly under the antenna, and it is
Summary of the content on the page No. 14
2.6.5 DC supply protection for an active antenna Antenna DC supply current limit. When the Jupiter receiver is used with an external active antenna, the DC supply in the coax cable is vulnerable to over-current if a fault occurs in the antenna or its cable gets crushed, for.example.in.a.car.door. WARNING It is important to note that the module antenna power feed does not have internal current limiting. Damage can occur if unlimited current is permitted to flow through the module antenna pow
Summary of the content on the page No. 15
Antenna short/open sense inputs and control output. The Jupiter receiver has a digital input to provide signalling when an antenna fault has occurred. These functions are shared with the Jupiter 30 GPIO pads as shown in Table 2-7. Antenna sense Jupiter GPIO function functions ANT_CTRL GPIO1 (ON=High) ANT_OC GPIO15 (Active High) NANT_SC GPIO3 (Active Low) Table 2-7: Antenna sense and control functions The reference design shown in figure 2-11 is indicative of an open-circuit switchover thresho
Summary of the content on the page No. 16
2.7 Jupiter adapter printed circuit board The module supplied in the Development kit is mounted on a carrier PCB in a method typical of a customer application. This carrier PCB illustrates and implements many of the design considerations discussed in this document. The module is interfaced through two separate 20-pin data connectors with different header pitches. This is for development purposes and provides a simple way to evaluate the surface mount module. The RTC (Real-Time Clock) backu
Summary of the content on the page No. 17
Refer to Table 2-8 for a description of the connector interfaces. Jupiter J2 (2.54 mm J1 (2 mm pitch function pitch header) header) pin no. pin no. V_ANT 1 1 VCC_RF 2 – V_BATT 3 3 VDD 4 4 M_RST 5 5 GPIO/GYRO IN 6 6 GPIO/FR 7 7 BOOT 8 8 GPIO/W TICKS 9 9 RFON 10 – GND – 10 TXA 11 11 RXA 12 12 GPIO/SDI 13 – GND – 13 TXB 14 14 RXB 15 15 GPIO/SCK .16* – GND 17 16 GPIO/SDO 18 – GND – 17 GND – 18 1PPS 19 19 GPS_FIX/GPIO 20 – *Note: J2 Pin 1 on the adapter card is the wake-up line for push to fix mod
Summary of the content on the page No. 18
3.2.1 Adaptive TricklePower mode 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. Adaptive TricklePower is always enabled on the Jupiter 30 and Jupiter 20 S (XTrac), and selectable on the Jupiter 20 standard module. 3.2.2 Push-to-Fix mode Unlike TricklePower, the operation in this mode is not cyclic. This mode alwa
Summary of the content on the page No. 19
Unused messages Input messages where the message ID is not between 100 and 255, or where the message ID does not correspond to a specified function, result in the response: $PTTK,INVALID*CS Errors Errors in message receipt (other than checksum errors) result in the response: $PTTK,ERROR,xx*CS where.xx.is.a.hexadecimal.error.code. Magnetic Variation (Declination) The Jupiter 20 module calculates the magnetic variation (the Jupiter 30 does not). Magnetic Variation fields in $GPRMC The last two fi
Summary of the content on the page No. 20
3.4 Navman proprietary NMEA low power mode messages Navman has added a number of proprietary NMEA input messages to configure the TricklePower and Push-To-Fix modes. 3.4.1 Low power configuration The following message sets the receiver to low power mode: $PSRF151,a,bbbb,cccc[*CS] where: Field Description a Push-To-Fix* (1=on, 0=off) TricklePower duty cycle (parts per b thousand) c TricklePower on time (milliseconds) TM *Note that Push-To-Fix does not require fields b and c so they m
