Summary of the content on the page No. 1
TRISTAR25 GPS Receiver Module
User’s Guide
1
Summary of the content on the page No. 2
Manual Revision History Revision Date Update Summary Issue A December 2002 Initial release Issue B February 2003 Add pins electrical characteristics Deluo Electronics http://www.deluo.com 2
Summary of the content on the page No. 3
1 INTRODUCTION ............................................................................................... 5 1.1 OVERVIEW............................................................................................................. 5 1.2 FEATURES .............................................................................................................. 5 2 RECEIVER OPERATION............................................................................... 6 3 HARDWARE INTERFACE.......
Summary of the content on the page No. 4
4.2.2 Binary Output Messages.................................................................................. 25 4.2.2.1 EverMore Binary Output Message 0x02: Navigation Data ................................... 25 4.2.2.2 EverMore Binary Output Message 0x04: DOP Data ........................................... 26 4.2.2.3 EverMore Binary Output Message 0x06: Channel Status..................................... 27 4.2.2.4 EverMore Binary Output Message 0x08: Measurement Data..............
Summary of the content on the page No. 5
1 Introduction 1.1 Overview The TISTAR25 GPS Receiver is intended for use in a wide range of applications. The receiver simultaneously tracks up to twelve satellites, provides accurate satellite positioning data with fast time-to-first-fix (TTFF) and low power consumption. It is designed for high performance and maximum flexibility in a wide range of applications including mobile asset tracking, in-vehicle automotive guidance, location sensing, telematics and so on. The highly in
Summary of the content on the page No. 6
2 Receiver Operation Upon power up, after initial self-test has completed, the TISTAR25 will begin satellite acquisition and tracking process. Under normal open-sky condition, position-fix can be achieved within approximately 45 seconds (within 15 seconds if valid ephemeris data is already collected from recent use). After receiver position has been calculated, valid position, velocity and time information are transmitted through the on board serial interface. The receiver uses the
Summary of the content on the page No. 7
3 Hardware Interface 3.1 RF Connector The RF connector is a 50 ohm straight MCX snap-on coaxial RF jack receptacle. 3.2 Interface Connector There are three interface connectors, the first is a 10-pin Molex connector, the second is a 16-pin golden finger, and the third is a 16-pin header. Deluo Electronics http:
Summary of the content on the page No. 8
3.3 Mechanical Dimensions and Interface Connector Unit: mil 1780 734 100 40 100 1225 985 78.74 50 150 RF
Summary of the content on the page No. 9
3.4 Interface Connector Pin Out 3.4.1 Molex Connector JP3 1 JP3 pin-1 1 10-pin Molex connector Figure 2 Pin Function Input/Output Level Pin Function Input/Output Level 1 TXD0 Output LVTTL 2 RXD0 Input LVTTL 3 PWR_IN Input 3.3V 4 GND Ground 0V 5 LED0 In/Out LVTTL 6 1PPS Output LVTTL 7 TXD1 Output LVTTL 8 RXD1 Input LVTTL 9 VBAT Input 3.3V 10 ANT PWR Input The following is a functional description of the pins on the 10-pin interface connector. Pin 1. TXD0: Serial port o
Summary of the content on the page No. 10
3.4.2 Pin Header Connector JP2 JP2 16-Pin Header 16-Pin Golden Finger RF SRAM Flash Antenna Connector Pin1 Pin 1 Pin header parallel golden finger Figure 3 Pin Function Input/Output Level Pin Function Input/Output Level 1 PIO1 In
Summary of the content on the page No. 11
3.5 One-Pulse-Per-Second Output The one-pulse-per-second output is provided for applications requiring precise timing measurements. The output pulse is 1usec in duration. The rising edge of the output pulse is accurate to +/-1usec with respect to the start of each GPS second. The accuracy of the one-pulse-per-second output is maintained only when the receiver has valid position fix. 3.6 RTCM Differential Data By using differential GPS (DGPS) correction data in RTCM SC-104 form
Summary of the content on the page No. 12
4 SOFTWARE INTERFACE This section describes the details of the serial port commands through which the TISTAR25 is controlled and monitored. The serial port commands allow users to set the receiver parameters, configure output message type, and retrieve status information. The baud rate and protocol of the host COM port must match the baud rate and protocol of the GPS receiver serial port for commands and data to be successfully transmitted and received. The default receiver proto
Summary of the content on the page No. 13
4.1.2 GGA – Global Positioning System Fix Data Purpose Output time, position and position-fix related data. Format $GPGGA,hhmmss.sss,ddmm.mmmm,a,dddmm.mmmm,a,x,xx,xx.x,xxxxx.x,M,xx.x,M,xxx,xxxx *CS Example $GPGGA,083604.883,2446.5254,N,12100.1399,E,1,09,01.0,00155.7,M,16.3,M,,*6E Output Rate Programmable using EverMore Binary Message 0x8E and 0x8F. Field Name Example Unit Description 1 Message ID $GPGGA GGA protocol header 2 UTC Time 083604.883 hhmmss.sss hour, minute
Summary of the content on the page No. 14
4.1.3 GLL – Geographic Position – Latitude / Longitude Purpose Output latitude and longitude of current position, time, and status. Format $GPGLL,ddmm.mmmm,a,dddmm.mmmm,a,hhmmss.sss,x*CS Example $GPGLL,2446.5311,N,12100.1377,E,110519.259,A*35 Output Rate Programmable using EverMore Binary Message 0x8E and 0x8F. Field Name Example Unit Description 1 Message ID $GPGLL GLL protocol header 2 Latitude 2446.5311 ddmm.mmmm degree, minute & decimal minute Leading zeros trans
Summary of the content on the page No. 15
4.1.4 GSA – GNSS DOP and Active Satellites Purpose Output operating mode, satellites used for navigation, and DOP values. Format $GPGSA,x,x,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx.x,xx.x,xx.x*CS Example $GPGSA,A,3,27,31,08,20,13,28,03,01,02,11,22,,01.3,00.8,01.0*0C Output Rate Programmable using EverMore Binary Message 0x8E and 0x8F. Field Name Example Unit Description 1 Message ID $GPGSA GSA protocol header 2 Manual or A x Automatic Mode A=automatic, allowed to switch
Summary of the content on the page No. 16
4.1.5 GSV – GNSS Satellites in View Purpose Output number of SVs in view, PRN numbers, elevation, azimuth and SNR values. Four satellites maximum per transmission, additional satellite data sent in the second or the third sentence. Format $GPGSV,x,x,xx,xx,xx,xxx,xx … xx,xx,xxx,xx*CS Example $GPGSV,3,1,11,27,59,276,44,31,50,046,44,08,38,309,44,20,07,165,39*70 $GPGSV,3,2,11,13,10,223,41,28,13,304,38,03,14,054,41,01,13,186,40*73 $GPGSV,3,3,11,02,06,303,43,11,73,165,43,22,06,11
Summary of the content on the page No. 17
4.1.6 RMC – Recommended Minimum Specific GNSS Data Purpose Output time, date, position, course and speed data. Format $GPRMC,hhmmss.sss,x,ddmm.mmmm,a,dddmm.mmmm,a,xxx.x,xxx.x,ddmmyy,xxx.x,a*CS Example $GPRMC,083604.883,A,2446.5254,N,12100.1399,E,000.0,000.0,300502,003.3,W*76 Output Rate Programmable using EverMore Binary Message 0x8E and 0x8F. Field Name Example Unit Description 1 Message ID $GPRMC RMC protocol header 2 UTC time 083604.883 hhmmss.sss hour, minute, se
Summary of the content on the page No. 18
4.1.7 VTG – Course Over Ground and Ground Speed Purpose Outputs actual track made good and speed relative to the ground. Format $GPVTG,xxx.x,T,xxx.x,M,xxx.x,N,xxxx.x,K*CS Example $GPVTG,000.0,T,003.3,M,000.0,N,0000.0,K*7E Output Rate Programmable using EverMore Binary Message 0x8E and 0x8F. Field Name Example Unit Description 1 Message ID $GPVTG VTG protocol header 2 Heading 000.0 degree xxx.x Heading of the receiver when moving Leading zeros transmitted 3 True T In
Summary of the content on the page No. 19
4.2 EVERMORE BINARY MESSAGE SPECIFICATION The EverMore binary message protocol consists of 3 parts: message header, message body, and message footer. Message Header Message Body Message Footer Start Sequence Length of Message Body Message Checksum End Sequence 0x10 0x02 1 or 2 bytes Up to 253 bytes 1 or 2 bytes 0x10 0x03 Message Header The Message Header consists of 3 or 4 bytes: Byte #1 - DLE = 0x10 Byte #2 - STX = 0x02 Byte #3 - Length of Message Body + 2 Byte #4 - when
Summary of the content on the page No. 20
Message Footer: The Message Footer consists of 3 or 4 bytes: Byte #1 - checksum of the Message Body (it is calculated by summing all bytes in the Message Body and taking the sum modulo 256) Byte #2 - when Byte #1 equals DLE (0x10), DLE (0x10) is sent out as the 2nd byte of the message footer; otherwise it is not sent. Byte #3 - DLE (0x10). If checksum is not 0x10, this DLE character becomes Byte #2 Byte #4 - ETX (0x03). If checksum is not 0x10, this ETX character becomes Byte #3
