Summary of the content on the page No. 1
Jupiter GPS receiver module
Designer’s guide
(11/12/T/Pico/Pico T series)
Related products
Jupiter 11 (low power)
• Development kit TU10-D007-051
Jupiter 11 (standard 5 V)
• Development kit TU10-D007-061
Jupiter 11 (dead-reckoning)
• Development kit TU10-D007-101
Jupiter 12 (standard)
• Development kit TU10-D007-351
Jupiter 12 (dead-reckoning)
• DR Development kit TU10-D007-352
Jupiter Pico (standard)
• Development kit TU10-D007-361
Jupiter Pico (timing)
• Development kit TU10-D007-363
Related
Summary of the content on the page No. 2
Contents Features .................................................................................................................................5 1.0 Introduction ..................................................................................................6 1.1 Product overview ............................................................................................................6 1.1.1 Description ...................................................................................
Summary of the content on the page No. 3
3.5.2.13 Message 1303 (restart command). ..............................................................................41 3.5.2.14 Message 1310 (frequency standard input parameters). ..............................................42 3.5.2.15 Message 1317 (power management control). ..............................................................43 3.5.2.16 Message 1330 (serial port communication parameters). ............................................44 3.5.2.17 Message 1331 (message protocol
Summary of the content on the page No. 4
4.5.2.2 Parallel acquisition ..........................................................................................................62 4.5.2.3 Adaptive threshold-based signal detection .....................................................................62 4.5.2.4 Overall search process ...................................................................................................62 4.5.3 Data collection .....................................................................................
Summary of the content on the page No. 5
Features The Jupiter series of GPS receivers offers the following physical, operational, and support features: • OEM product development that is fully supported through application’s engineering. • compact GPS receiver footprint. • 12 parallel satellite tracking channels. • supports NMEA-0183 data protocol. • direct, differential RTCM SC-104 data capability for improved positioning accuracy (available in both Navman binary and NMEA host modes.) • static navigation enhancements to minimise wand
Summary of the content on the page No. 6
Jupiter signal acquisition system takes advantage 1.0 Introduction of all available information to provide a rapid TTFF. Acquisition is guaranteed under all initialisation This document provides technical information conditions as long as available satellites are not common to the entire Navman Jupiter series. obscured. Navman’s Jupiter series of Global Positioning To minimise TTFF following a power interruption, System (GPS) receivers are single-board, each of the Jupiter receivers ca
Summary of the content on the page No. 7
2. The Scorpio device, which contains an architecture that might be used to integrate a integral microprocessor and all GPS specific particular Jupiter receiver with an application signal processing hardware. processor that drives peripheral devices such as a display and keyboard. The interface between the In addition, memory and other supporting application’s processor and the Jupiter receiver is components configure the receiver into a complete through the serial data interface. navigati
Summary of the content on the page No. 8
Each binary message consists of a header 2.0 Hardware interface portion and a data portion, each with its own checksum. Each message will have a header, but Details of the specific Jupiter GPS receiver’s some messages may not have data. Message electrical interface are contained in the applicable acknowledgements are in the form of a header, data sheet for the receiver (the latest Jupiter series and message requests are also made using data sheets and product briefs can be downloaded he
Summary of the content on the page No. 9
independently for each message request. The user sets the request (R) bit and either the acknowledge (A) bit or negative acknowledge (N) bit, or both, to select the proper acknowledge behaviour. With this approach, the user can configure requests only to be NAKed, alerting the user when a problem arises without incurring the overhead necessary to continuously process ACKs. The lower six bits of the flags word can be used as an additional input identifier. This identifier is not explicitly
Summary of the content on the page No. 10
during the next output interval. Standard log data word count found in the header. The data requests will be accepted if the log (L) bit is set checksum follows the data and is not included in and if the required data parameters are present in the data word count. the data portion of the request message. The data checksum is a 16-bit word used to 3.2.5 Message header word 5 validate the data portion of the message. It is Word 5 of the message header is the data transmitted as the last word
Summary of the content on the page No. 11
RMC: recommended minimum specific GPS The maximum number of characters in a sentence data is 82, consisting of a maximum of 79 characters between the starting delimiter ‘$’ and the The Jupiter receiver also supports the following terminating and . Since the number of Navman proprietary output messages: data fields can vary from sentence to sentence, BIT: built-In test results it is important that the ‘listener’ (or application ERR: error/status software) locate fields by counting de
Summary of the content on the page No. 12
Field Type Symbol Definition Special format fields Single character field: Status A A = yes, data valid, warning flag clear V = no, data invalid, warning flag set Fixed/variable length field (degrees/minutes.decimal) two fixed digits of degrees, two fixed digits of minutes, and a variable number of digits for decimal-fraction of minutes Latitude 1111.11 Note: Leading zeros always included for degrees and minutes to maintain fixed length (the decimal point and associated decimal-fraction are optional i
Summary of the content on the page No. 13
Output message name Message ID Input message name Message ID Geodetic position and velocity Geodetic position status output (*) 1000 1200 initialisation Channel summary (*) 1002 User-defined datum definition 1210 Visible satellites (*) 1003 Map datum select 1211 Differential GPS status 1005 Satellite elevation mask control 1212 Channel measurement 1007 Satellite candidate select 1213 ECEF position output 1009 Differential GPS control 1214 Receiver I D (**) 1011 Cold start control 1216 User-settin
Summary of the content on the page No. 14
3.5.1.1 Message 1000 (geodetic position status 3.5 Jupiter binary data messages output) This section describes the binary data messages This message outputs the receiver’s estimate of of the Jupiter GPS receiver. All output and input position, ground speed, course over ground, climb binary messages are listed in Table 3-4 together rate, and map datum. A solution status indicates if with their corresponding message IDs. Power-up the solution is valid (based on the solution validity default
Summary of the content on the page No. 15
Word No Name Type Units Range Resolution Non-DR link: polar navigation DR navigation link: Bit 1 = true 13 Bit 0 = polar navigation degrees 0.01 Bit 15 to 1 = heading uncertainty standard Bit 1 = true deviation (Note 12) UI 0 to 300 14 GPS week number UI weeks 0 to 32 767 15-16 GPS seconds from epoch UDI s 0 to 604 799 17-18 GPS nanoseconds from epoch UDI ns 0 to 999 999 999 19 UTC day UI day 1 to 31 20 UTC month UI month 1 to 12 21 UTC year UI year 1980 to 2079 22 UTC hours UI h 0 to 23 23 U
Summary of the content on the page No. 16
3.5.1.2 Message 1002 (channel summary) information on a per- channel basis. The contents This message provides a summary form of the of the ‘channel summary’ message are described satellite range measurements and signal tracking in Table 3-6 Message ID: 1002 Rate: Variable; defaults to 1 Hz Message Length: 51 words Word No. Name Type Units Range 1-4 Message header 5 Header checksum 6-7 Set time (Note 1) UDI 10 ms ticks 0 to 4 294 967 295 8 Sequence number (Note 2) I 0 to 32 767 Satellite me
Summary of the content on the page No. 17
3.5.1.3 Message 1003 (visible satellites) from this visible list, are also provided. The This message outputs the list of satellites visible contents of the ‘visible satellites’ message are to the receiver and their corresponding elevations described in Table 3-7. and azimuths. The best possible DOPs, calculated Message ID: 1003 Rate: Variable; default on update Message Length: 51 words Word No. Name Type Units Range Resolution 1-4 Message header 5 Header checksum 0 to 6-7 Set time (Note
Summary of the content on the page No. 18
3.5.1.4 Message 1005 (DGPS Status) processed by the receiver. The contents of the This message contains DGPS status information ‘DGPS status’ message are described in Table derived from the last set of differential corrections 3-8. Message ID: 1005 Rate: Variable Message Length: 25 words Word No. Name Type Units Range 1-4 Message header 5 Header checksum 6-7 Set time (Note 1) UDI 10 ms ticks 0 to 4 294 967 295 8 Sequence number (Note 2) I 0 to 32 767 Status (9.0-9.15) 9.0 Station health Bit
Summary of the content on the page No. 19
3.5.1.5 Message 1007 (channel measurement) 12 channels. The contents of the ‘channel This message provides measurement and measurement’ message are described in associated data for each of the receiver’s Table 3-9. Message ID: 1007 Rate: Variable Message Length: 154 words Word No. Name Type Units Range Resolution 1-4 Message header 5 Header checksum 6-7 Set time (Note 1) UDI 10 ms ticks 0 to 4 294 967 295 8 Sequence number (Note 2) I 0 to 32 767 9 Satellite measurement sequence number (Note
Summary of the content on the page No. 20
3.5.1.6 Message 1009 (reduced ECEF position 12 channels. The contents of the ‘channel status output) measurement’ message are described in This message provides measurement and Table 3-10. associated data for each of the receiver’s Message ID: 1009 Rate: variable Message length: 22 words Word No. Name Type Units Range Resolution 1-4 Message header 5 Header checksum 6-7 Set time (Note 1) UDI 10 ms ticks 0 to 4 294 967 295 8 Sequence number (Note 2) I 0 to 32 767 Satellite measurement sequen
