# Document Metadata **Format:** PDF 1.7 **Author:** user **Creator:** Microsoft® Word 2016 **Producer:** Microsoft® Word 2016 **Creation Date:** D:20240312171445+08'00' **Mod Date:** D:20240312171445+08'00' --- ## Page 1 1 RYS352x 18-DEC-2023 56312E39 PAIR Command Guide ![Image 1 from page 1](pdf-image://page_1_img_1) ![Image 2 from page 1](pdf-image://page_1_img_2) ## Page 2 2 Contents 1 Introduction ................................................................................................................................................ 6 2 NMEA Protocol ......................................................................................................................................... 7 2.1. Structure of NMEA Protocol Messages .............................................................................................. 7 2.2. Standard Messages ........................................................................................................................... 9 2.2.2. GGA ...................................................................................................................................... 11 2.2.3. GSV ....................................................................................................................................... 13 2.2.4. GSA ....................................................................................................................................... 14 2.2.5. VTG ....................................................................................................................................... 16 2.2.6. GLL ........................................................................................................................................ 17 2.2.7. ZDA ....................................................................................................................................... 19 2.2.8. GNS ...................................................................................................................................... 10 2.2.9. GST ....................................................................................................................................... 13 2.2.10. GRS ....................................................................................................................................... 14 2.2.11. RLM ...................................................................................................................................... 15 2.3. PAIR Messages ................................................................................................................................ 17 2.3.1. Packet Type: 001 PAIR\_ACK .................................................................................................. 17 2.3.2. Packet Type: 002 PAIR\_GNSS\_SUBSYS\_POWER\_ON ............................................................. 17 2.3.3. Packet Type: 003 PAIR\_GNSS\_SUBSYS\_POWER\_OFF ............................................................ 18 2.3.4. Packet Type: 004 PAIR\_GNSS\_SUBSYS\_HOT\_START ............................................................. 19 2.3.5. Packet Type: 005 PAIR\_GNSS\_SUBSYS\_WARM\_START ......................................................... 19 2.3.6. Packet Type: 006 PAIR\_GNSS\_SUBSYS\_COLD\_START ........................................................... 20 2.3.7. Packet Type: 007 PAIR\_GNSS\_SUBSYS\_FULL\_COLD\_START .................................................. 20 2.3.8. Packet Type: 010 PAIR\_REQUEST\_AIDING ............................................................................ 21 2.3.9. Packet Type: 050 PAIR\_COMMON\_SET\_FIX\_RATE ................................................................ 21 2.3.10. Packet Type: 051 PAIR\_COMMON\_GET\_FIX\_RATE ................................................................ 22 2.3.11. Packet Type: 058 PAIR\_COMMON\_SET\_MIN\_SNR................................................................ 23 2.3.12. Packet Type: 062 PAIR\_COMMON\_SET\_NMEA\_OUTPUT\_RATE ............................................ 23 2.3.13. Packet Type: 059 PAIR\_COMMON\_GET\_MIN\_SNR ............................................................... 24 2.3.14. Packet Type: 063 PAIR\_COMMON\_GET\_NMEA\_OUTPUT\_RATE ........................................... 25 2.3.15. Packet Type: 066 PAIR\_COMMON\_SET\_GNSS\_SEARCH\_MODE ........................................... 26 2.3.16. Packet Type: 067 PAIR\_COMMON\_GET\_GNSS\_SEARCH\_MODE ........................................... 27 2.3.17. Packet Type: 070 PAIR\_COMMON\_SET\_STATIC\_THRESHOLD .............................................. 28 2.3.18. Packet Type: 071 PAIR\_COMMON\_GET\_STATIC\_THRESHOLD ............................................. 28 2.3.19. Packet Type: 072 PAIR\_COMMON\_SET\_ELEV\_MASK ............................................................ 29 2.3.20. Packet Type: 073 PAIR\_COMMON\_GET\_ELEV\_MASK ........................................................... 40 2.3.21. Packet Type: 074 PAIR\_COMMON\_SET\_AIC\_ENABLE ........................................................... 30 2.3.22. Packet Type: 075 PAIR\_COMMON\_GET\_AIC\_STATUS ........................................................... 31 2.3.23. Packet Type: 080 PAIR\_COMMON\_SET\_NAVIGATION\_MODE ............................................. 42 ## Page 3 3 2.3.24. Packet Type: 081 PAIR\_COMMON\_GET\_NAVIGATION\_MODE ............................................. 34 2.3.25. Packet Type: 086 PAIR\_COMMON\_SET\_DEBUGLOG\_OUTPUT ............................................. 34 2.3.26. Packet Type: 087 PAIR\_COMMON\_GET\_DEBUGLOG\_OUTPUT ............................................. 34 2.3.27. Packet Type: 154 PAIR\_COMMON\_SET\_RLM\_OUTPUT\_ENABLE .......................................... 36 2.3.28. Packet Type: 155 PAIR\_COMMON\_GET\_RLM\_OUTPUT\_STATUS .......................................... 36 2.3.29. Packet Type: 158 PAIR\_COMMON\_SET\_B1C\_ENABLE .......................................................... 36 2.3.30. Packet Type: 382 PAIR\_TEST\_LOCK\_SYSTEM\_SLEEP ............................................................. 38 2.3.31. Packet Type: 400 PAIR\_DGPS\_SET\_MODE ............................................................................ 39 2.3.32. Packet Type: 401 PAIR\_DGPS\_GET\_MODE ............................................................................ 39 2.3.33. Packet Type: 410 PAIR\_SBAS\_ENABLE .................................................................................. 40 2.3.34. Packet Type: 411 PAIR\_SBAS\_GET\_STATUS .......................................................................... 41 2.3.35. Packet Type: 432 PAIR\_RTCM\_SET\_OUTPUT\_MODE ............................................................. 42 2.3.36. Packet Type: 433 PAIR\_RTCM\_GET\_OUTPUT\_MODE ............................................................ 42 2.3.37. Packet Type: 434 PAIR\_RTCM\_SET\_OUTPUT\_ANT\_PNT ........................................................ 43 2.3.38. Packet Type: 435 PAIR\_RTCM\_GET\_OUTPUT\_ANT\_PNT ....................................................... 43 2.3.39. Packet Type: 436 PAIR\_RTCM\_SET\_OUTPUT\_EPHEMERIS ..................................................... 44 2.3.40. Packet Type: 437 PAIR\_RTCM\_GET\_OUTPUT\_EPHEMERIS .................................................... 45 2.3.41. Packet Type: 490 PAIR\_EASY\_ENABLE .................................................................................. 45 2.3.42. Packet Type: 491 PAIR\_EASY\_GET\_STATUS ........................................................................... 46 2.3.43. Packet Type: 511 PAIR\_NVRAM\_SAVE\_NAVIGATION\_DATA ................................................ 47 2.3.44. Packet Type: 513 PAIR\_NVRAM\_SAVE\_SETTING ................................................................... 48 2.3.45. Packet Type: 650 PAIR\_LOW\_POWER\_ENTRY\_RTC\_MODE ................................................... 48 2.3.46. Packet Type: 680 PAIR\_GLP\_ENABLE .................................................................................... 49 2.3.47. Packet Type: 681 PAIR\_GLP\_GET\_STATUS............................................................................. 50 2.3.48. Packet Type: 690 PAIR\_PERIODIC\_SET\_MODE ...................................................................... 50 2.3.49. Packet Type: 691 PAIR\_PERIODIC\_GET\_MODE ..................................................................... 51 2.3.50. Packet Type: 730 PAIR\_FLP\_ENABLE ..................................................................................... 52 2.3.51. Packet Type: 731 PAIR\_FLP\_GET\_STATUS ............................................................................. 53 2.3.52. Packet Type: 732 PAIR\_FLP\_ENABLE ..................................................................................... 53 2.3.53. Packet Type: 733 PAIR\_ALP\_GET\_STATUS ............................................................................. 54 2.3.54. Packet Type: 752 PAIR\_PPS\_SET\_CONFIG\_CMD ................................................................... 55 2.3.55. Packet Type: 900 PAIR\_LOCUS\_ENABLE ............................................................................... 55 2.3.56. Packet Type: 901 PAIR\_LOCUS\_GET\_STATUS ........................................................................ 57 2.3.57. Packet Type: 902 PAIR\_LOCUS\_SET\_MODE .......................................................................... 57 2.3.58. Packet Type: 903 PAIR\_LOCUS\_GET\_MODE .......................................................................... 58 2.3.59. Packet Type: 904 PAIR\_LOCUS\_SET\_THRESHOLD ................................................................. 59 2.3.60. Packet Type: 905 PAIR\_LOCUS\_GET\_THRESHOLD ................................................................ 69 2.3.61. Packet Type: 906 PAIR\_LOCUS\_CLEAR .................................................................................. 69 2.3.62. Packet Type: 907 PAIR\_LOCUS\_LOG\_NOW ........................................................................... 70 2.3.63. Packet Type: 908 PAIR\_LOCUS\_GET\_DATA ........................................................................... 70 ## Page 4 4 2.3.64. Packet Type: 909 PAIR\_LOCUS\_GET\_RECORD\_NUM ............................................................ 73 3 RTCM Protocol .......................................................................................................................................... 74 4 Appendix A – References ......................................................................................................................... 77 5 Appendix B - GNSS Satellites (NEMA) Numbering ............................................................................... 78 6 Appendix C – Special characters ............................................................................................................. 79 ## Page 5 5 Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Table Index Table 1: Applicable Modules and Variants .................................................................................................................... 6 Table 2: Supported Protocols ................................................................................................................................. …...6 Table 3: Structure of NMEA Protocol Messages ......................................................................................................... ..7 Table 4: NMEA Talker ID ..................................................................................................................................................... ..8 Table 5: Supported RTCM3 Messages ...................................................................................................................... …74 Table 6: Terms and Abbreviations .................................................................................................................................. …75 Table 7: GNSS Satellites (NEMA) Numbering ........................................................................................................... …78 Table 8: Special Characters ...................................................................................................................................... …79 ## Page 6 RYS352x PAIR Command Guide 1 Introduction RYS3520 GNSS modules support GPS, GLONASS, Galileo, BDS and QZSS constellations. Concurrent tracking of multi-frequency bands provides fast and accurate acquisition and makes these modules ideal solutions for positioning and navigation in various vertical markets. This document describes the software commands that are used to control and modify the module configuration. The software commands are NMEA proprietary commands defined by REYAX. To report GNSS information, the modules support outputting messages in NMEA 0183 protocol format and RTCM protocol format. Table 1: Applicable Variants and Supported Frequency Bands Module Variant Frequency Band RYS352x RYS3520 GPS L1 C/A + GLONASS L1 + Galileo E1 + BDS B1I + QZSS L1 C/A ,,, Table 2: Supported Protocols Protocol Type RYS352x Output, ASCII, standard Input/output, ASCII, proprietary RTCM 10403.3 Output, binary, proprietary 6 ![Image 1 from page 6](pdf-image://page_6_img_1) ![Image 2 from page 6](pdf-image://page_6_img_2) ## Page 7 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. 2 NMEA Protocol 2.1. Structure of NMEA Protocol Messages Start of sentence character. Always ‘$’ Start with a ‘\*’, 8-bit checksum value converted to two ASCII characters Address field - contains talker identifier and sentence formatter Data field(s), delimited by ‘,’ End of sentence. Always $
() [,] \* Range for checksum calculation Field Description $ Start of the sentence (Hex 0x24).
In Standard Messages: In NMEA standard messages, this field consists of a two-character talker identifier (TalkerID) and a three-character sentence formatter (SentenceFormatter). The talker identifier identifies the data type of talker. For more information on the TalkerID, see Table 4: NMEA Talker ID. The sentence formatter identifies the data type and the string format of the successive fields. In Proprietary Messages: In NMEA proprietary messages, this field consists of the proprietary character P followed by a three-character Manufacturer's Mnemonic Code, used to identify the TALKER issuing a proprietary sentence, and any additional characters as required Data fields, delimited by data field delimiter ‘,’. Variable length (depends on the NMEA message type). Checksum field follows the checksum delimiter character \*. Checksum is the 8-bit exclusive OR of all characters in the sentence, including the ‘,’ field delimiter, between but not including the ‘$’ and the ‘\*’ delimiters. End of the sentence (Hex 0x0D 0x0A). Figure 1: Structure of NMEA Protocol Messages Table 3: Structure of NMEA Protocol Messages 7 ![Image 1 from page 7](pdf-image://page_7_img_1) ![Image 2 from page 7](pdf-image://page_7_img_2) ![Image 3 from page 7](pdf-image://page_7_img_3) ![Image 4 from page 7](pdf-image://page_7_img_4) ## Page 8 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Table 4: NMEA Talker ID GNSS Constellation Configuration TalkerID (NMEA V4.10) GPS GP GLONASS GL Galileo GA BDS GB QZSS GP Combination of Multiple Satellite Systems GN Sample Code for NMEA Checksum: // pData is the data array whose checksum needs to be calculated: unsigned char Ql\_Check\_XOR(const unsigned char \*pData, unsigned int Length) { unsigned char result = 0; unsigned int i = 0; if((NULL == pData) || (Length < 1)) { return 0; } for(i = 0; i < Length; i++) { result ^= \*(pData + i); } return result; } 8 ![Image 1 from page 8](pdf-image://page_8_img_1) ![Image 2 from page 8](pdf-image://page_8_img_2) ## Page 9 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. 2.2. Standard Messages This chapter explains the NMEA 0183 V4.10 standard messages supported by the modules. 2.2.1. RMC Message RMC Description Recommended Minimum Specific GNSS Data. Time, date, position, course, and speed data provided by a GNSS receiver Type Output Message Structure: Example: $GNRMC,040143.000,A,3149.334166,N,11706.941670,E,0.01,0.00,010522,,,D,V\*0E Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters GN Talker identifier. See Table 4: NMEA Talker ID RMC String, 3 characters RMC Recommended Minimum Specific GNSS Data. hhmmss.sss 040143.000 GNSS Data. Position fix UTC. hh: Hours (00–23) mm: Minutes (00–59) ss: Seconds (00–59) sss: Decimal fraction of seconds Character A Positioning system status. A = Data valid V = Navigation receiver warning ddmm.mmmmmm 3149.334166 Latitude. dd. Degrees (00–90) mm. Minutes (00–59) mmmmmm: Decimal fraction of minutes Note that this field is empty in case of an invalid value. $RMC,,,,,,,,,,, ,,\* 9 ![Image 1 from page 9](pdf-image://page_9_img_1) ![Image 2 from page 9](pdf-image://page_9_img_2) ## Page 10 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description Character N North-south direction. N = North S = South Note that this field is empty in case of an invalid value. dddmm.mmmmmm 11706.941670 Longitude. ddd: Degrees (000–180) mm: Minutes (00–59) mmmmmm: Decimal fraction of minutes. Note that this field is empty in case of an invalid value. Character E East-west direction. E = East W = West Note that this field is empty in case of an invalid value. Numeric Knot 0.01 Speed over ground. Variable length. Note that this field is empty in case of an invalid value. Numeric Degree 0.00 Course over ground. Variable length. Maximum value: 359.99. Note that this field is empty in case of an invalid value. ddmmyy 010522 Date. dd: Day of month mm: Month yy: Year Magnetic variation. Not supported. Direction of magnetic variation. Not supported. 10 ![Image 1 from page 10](pdf-image://page_10_img_1) ![Image 2 from page 10](pdf-image://page_10_img_2) ## Page 11 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description Character D Mode indicator. A = Autonomous mode. Satellite system used in non-differential mode for position fixing. D = Differential mode. Satellite system used in differential mode for position fixing. Corrections from ground stations or Satellite Based Augmentation System (SBAS). E = Estimated (dead reckoning) mode F = Float RTK. Satellite system used in RTK mode with floating integers. M = Manual input mode N = No fix. Satellite system not used for position fixing, or fix not valid. R = Real Time Kinematic (RTK). Satellite system used in RTK mode with fixed integers Character V Navigational status indication. Note that this parameter is only available in messages in line with NMEA0183 V4.10 and later versions. Hexadecimal \*0E Checksum. Character Carriage return and line feed. 2.2.2. GGA Message GGA Description Global Positioning System Fix Data. Time, position, and fix-related data for a GNSS receiver Type Output Message Structure: Example: Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters GN Talker identifier. See Table 4: NMEA Talker ID $GGA,,,,,,,,,,M, ,M,,\* $GNRMC,040143.000,A,3149.334166,N,11706.941670,E,0.01,0.00,010522,,,D,V\*0E 11 ![Image 1 from page 11](pdf-image://page_11_img_1) ![Image 2 from page 11](pdf-image://page_11_img_2) ## Page 12 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description GGA String, 3 characters GGA Global Positioning System Fix Data. hhmmss.sss 040143.000 GNSS Data. Position fix UTC. hh: Hours (00–23) mm: Minutes (00–59) ss: Seconds (00–59) sss: Decimal fraction of seconds ddmm.mmmmmm 3149.334166 Latitude. dd. Degrees (00–90) mm. Minutes (00–59) mmmmmm: Decimal fraction of minutes Note that this field is empty in case of an invalid value. Character N North-south direction. N = North S = South Note that this field is empty in case of an invalid value. dddmm.mmmmmm 11706.941670 Longitude. ddd: Degrees (000–180) mm: Minutes (00–59) mmmmmm: Decimal fraction of minutes. Note that this field is empty in case of an invalid value. Character E East-west direction. E = East W = West Note that this field is empty in case of an invalid value. Numeric, 1 digit 2 GPS quality indicator. 0 = Fix not available or invalid 1 = GPS SPS Mode, fix valid 2 = Differential GPS, SPS Mode, or Satellite Based Augmentation. System (SBAS), fix valid 3 = GPS PPS Mode, fix valid 4 = Real Time Kinematic (RTK) System used in RTK mode with fixed integers 5 = Float RTK. Satellite system used in RTK mode, floating integers 6 = Estimated (dead reckoning) mode 1) Numeric, 2 digits 36 Number of satellites in use. Numeric 0.48 Horizontal dilution of precision. Note that this field is empty in case of an invalid value. 12 ![Image 1 from page 12](pdf-image://page_12_img_1) ![Image 2 from page 12](pdf-image://page_12_img_2) ## Page 13 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description Numeric Meter 61.496 Altitude above mean-sea-level (geoid). Note that this field is empty in case of an invalid value. M Character M Unit of . “M” = Meter. Differential GPS data age. Not supported. Differential reference station ID. Not supported. Hexadecimal \*58 Checksum. Character Carriage return and line feed. Note: 1. The NMEA 0183 specification indicates that GGA messages are GPS specific. However, when the receiver is configured for multi-constellations, the content of GGA messages will be generated from the multi-constellation solution. 2.2.3. GSV Message GSV Description GNSS Satellites in View. The GSV sentence provides the number of satellites in view (SV), satellite ID numbers, elevation, azimuth, and SNR value, and it contains maximum four satellites per transmission. Therefore, it may take several sentences to get complete information. The total number of sentences being transmitted and the sentence number are indicated in the first two data fields. Type Output Message Structure: Example: $GSV,,,{,,,,},\* $GPGSV,3,1,12,195,72,076,42,01,69,158,45,194,66,111,29,21,61,060,44,1\*6D $GPGSV,3,2,12,07,61,233,42,30,52,284,44,199,51,162,37,08,39,045,42,1\*59 $GPGSV,3,3,12,14,29,312,29,196,20,148,36,17,18,258,36,27,07,061,36,1\*53 $GLGSV,2,1,05,79,80,068,47,82,62,248,44,81,56,014,38,78,31,137,24,1\*7F $GLGSV,2,2,05,88,07,034,29,1\*46 $GAGSV,2,1,06,26,80,095,42,01,69,353,13,21,49,106,26,33,42,207,41,7\*72 $GAGSV,2,2,06,13,28,040,34,31,19,313,34,7\*72 $GBGSV,4,1,16,46,81,194,38,07,68,349,31,40,61,016,40,30,60,259,43,1\*71 $GBGSV,4,2,16,10,59,321,,03,51,192,36,36,41,314,38,02,37,229,32,1\*71 $GBGSV,4,3,16,09,31,219,26,08,27,175,31,37,25,146,29,06,23,202,29,1\*78 $GBGSV,4,4,16,16,20,199,31,13,17,186,26,39,12,192,29,28,09,048,30,1\*7C 13 ![Image 1 from page 13](pdf-image://page_13_img_1) ![Image 2 from page 13](pdf-image://page_13_img_2) ## Page 14 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters GP Talker identifier. See Table 4: NMEA Talker ID GSV String, 3 characters GSV GNSS Satellites in view Numeric 3 Total number of sentences. Range: 1–9. Numeric 1 Sentence number. Range: 1–. Numeric 12 Total number of satellites in view. Start of repeat block. Repeat times: 1–4. Numeric 195 Satellite ID. See Table 8: GNSS Satellites (NEMA) Numbering. Numeric Degree 72 Satellite elevation. Range: 00–90. Numeric Degree 076 Satellite azimuth, with true north as the reference plane. Range: 000–359. Numeric dB-Hz 42 Satellite C/N0. Range 00–99. Null when not tracking. Numeric 1 GNSS signal ID. See Table 8: GNSS Satellites (NEMA) Numbering. Note that this parameter is only available in messages in line with NMEA 0183 V4.10 and later versions. Hexadecimal \*58 Checksum. Character Carriage return and line feed. Note: 1. GN cannot be used for GSV sentences. If satellites of multiple constellations are in view, use separate GSV sentences with the corresponding talker ID for each constellation. 2.2.4. GSA Message GSA Description GNSS DOP and Active Satellites. GNSS receiver operating mode, satellites used in the navigation solution reported by the GGA sentence, and DOP values. Type Output 14 ![Image 1 from page 14](pdf-image://page_14_img_1) ![Image 2 from page 14](pdf-image://page_14_img_2) ## Page 15 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Message Structure: Example: Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters GN Talker identifier. See Table 4: NMEA Talker ID GSA String, 3 characters GSA GNSS DOP and Active Satellites. Character A Selection of 2D or 3D fix. M = Manual, forced to operate in 2D or 3D Mode A= Automatic, allowed to automatically switch to 2D/3D Numeric - 3 Fix mode. 1 = Fix not available 2 = 2D 3 = 3D Start of repeat block. Repeat times: 12. Numeric 195 ID numbers of satellites used in solution. See Table 8: GNSS Satellites (NEMA) Numbering. Note that this field is empty in case of an invalid value. End of repeat block. Numeric 0.71 Position dilution of precision. Maximum value: 99.00. Note that this field is empty in case of an invalid value. Numeric 0.48 Horizontal dilution of precision. Maximum value: 99.00. Note that this field is empty in case of an invalid value. Numeric 0.52 Vertical dilution of precision. Maximum value: 99.00. Note that this field is empty in case of an invalid value $GSA,,{,},,,\* $GNGSA,A,3,195,01,194,21,07,30,199,08,14,17,27,,0.71,0.48,0.52,1\*34 $GNGSA,A,3,79,82,81,78,88,,,,,,,,0.71,0.48,0.52,2\*0D $GNGSA,A,3,26,21,33,13,31,,,,,,,,0.71,0.48,0.52,3\*09 $GNGSA,A,3,46,07,40,30,03,36,02,09,08,37,06,16,0.71,0.48,0.52,4\*0B $GNGSA,A,3,13,39,28,,,,,,,,,,0.71,0.48,0.52,4\*0B 15 ![Image 1 from page 15](pdf-image://page_15_img_1) ![Image 2 from page 15](pdf-image://page_15_img_2) ## Page 16 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description Numeric 0.48 Horizontal dilution of precision. Maximum value: 99.00. Note that this field is empty in case of an invalid value. Numeric 0.52 Vertical dilution of precision. Maximum value: 99.00. Note that this field is empty in case of an invalid value Numeric 1 GNSS system ID. See Table 8: GNSS Satellites (NEMA) Numbering Hexadecimal \*34 Checksum Character Carriage return and line feed. Note: 1. If less than 12 satellites are used for navigation, the remaining fields are left empty. If more than 12 satellites are used for navigation, only the IDs of the first 12 are output 2.2.5. VTG Message VTG Description Course Over Ground & Ground Speed. The actual course and speed relative to the ground. Type Output Message Structure: Example: Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters GN Talker identifier. See Table 4: NMEA Talker ID VTG String, 3 characters GSA Course Over Ground & Ground Speed. Numeric Degrees 0.00 Course over ground, in true north course direction. Note that this field is empty in case of an invalid value. $VTG,,T,,M,,N,,K,\* $GNVTG,0.00,T,,M,0.01,N,0.02,K,D\*25 16 ![Image 1 from page 16](pdf-image://page_16_img_1) ![Image 2 from page 16](pdf-image://page_16_img_2) ## Page 17 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description T Character T Fixed field: true. Numeric Degrees M Course over ground (magnetic). Not supported. M Character Fixed field: magnetic. Numeric Knots 0.01 Speed over ground in knots. Note that this field is empty in case of an invalid value. N Character N Fixed field: knot. Numeric km/h 0.02 Speed over ground in kilometers per hour. Note that this field is empty in case of an invalid value0 K Character K Fixed field: kilometers per hour. Character D Mode indicator. A = Autonomous mode D = Differential mode E = Estimated (dead reckoning) mode F = Float RTK. Satellite system used in real time kinematic mode with floating integers M = Manual input mode N = No fix. Satellite system not used for position fixing, or fix not valid R = Real Time Kinematic. Satellite system used in RTK mode with fixed integers Hexadecimal \*25 Checksum Character Carriage return and line feed. 2.2.6. GLL Message GLL Description Geographic Position – Latitude/Longitude. Latitude and longitude of the GNSS receiver position, the time of position fix and status Type Output Message Structure: Example: $GLL,,,,,,,\* $GNGLL,3149.334166,N,11706.941670,E,040143.000,A,D\*46 17 ![Image 1 from page 17](pdf-image://page_17_img_1) ![Image 2 from page 17](pdf-image://page_17_img_2) ## Page 18 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters GN Talker identifier. See Table 4: NMEA Talker ID GLL String, 3 characters GLL Geographic Position – Latitude/Longitude. ddmm.mmmmmm - 3149.334166 Latitude. dd: Degrees (00–90) mm: Minutes (00–59) mmmmmm: Decimal fraction of minutes Note that this field is empty in case of an invalid value. Character N North-south direction. N = North S = South Note that this field is empty in case of an invalid value. dddmm.mmmmmm 11706.941670 Latitude. dd: Degrees (000–180) mm: Minutes (00–59) mmmmmm: Decimal fraction of minutes Note that this field is empty in case of an invalid value. Character E East-west direction. E = East W = West Note that this field is empty in case of an invalid value hhmmss.sss 040143.000 Position UTC. hh: Hours (00–23) mm: Minutes (00–59) ss: Seconds (00–59) sss: Decimal fraction of seconds Character A Positioning system status. A = Data valid V = Invalid data 18 ![Image 1 from page 18](pdf-image://page_18_img_1) ![Image 2 from page 18](pdf-image://page_18_img_2) ## Page 19 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description Character GN Mode indicator. A = Autonomous mode D = Differential mode E = Estimated (dead reckoning) mode F = Float RTK. Satellite system used in real time kinematic mode with floating integers M = Manual input mode N = No fix. Satellite system not used for position fixing, or fix not valid R = Real Time Kinematic. Satellite system used in RTK mode with fixed integers. Hexadecimal \*46 Checksum Character Carriage return and line feed. 2.2.7. ZDA Message ZDA Description Time and date. UTC, day, month, year and local time zone. Type Output Message Structure: Example: Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters GN Talker identifier. See Table 4: NMEA Talker ID ZDA String, 3 characters ZDA Time&Date. UTC, day, month, year and local time zone. $ZDA,,,,,,\* $GNZDA,055054.000,19,09,2022,,\*4A 19 ![Image 1 from page 19](pdf-image://page_19_img_1) ![Image 2 from page 19](pdf-image://page_19_img_2) ## Page 20 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description hhmmss.sss 055054.000 Position fix UTC. hh: Hours (00–23) mm: Minutes (00–59) ss: Seconds (00–59) sss: Decimal fraction of seconds Numeric 19 Day of month. Range: 01–31. Numeric 09 Month. Range: 01–12. Numeric 2022 Year. Numeric Local zone hours, 00 to ±13 hours. Not supported. Numeric Local zone minutes, 00 to +59 minutes. Not supported. Hexadecimal \*4A Checksum Character Carriage return and line feed. 2.2.8. GNS Message GNS Description GNSS fix data. Fix data for single or combined satellite navigation systems (GNSS). Type Output Message Structure: Example: Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters Talker identifier. See Table 4: NMEA Talker ID GNS String, 3 characters GNS GNSS Fix Data. $GNS,,,,,,,,,, M,,M,,,\* $GNGNS,053106.000,3149.334190,N,11706.948654,E,DANN,16,0.63,51.287,M,-0.335,M,,,V\*05 20 ![Image 1 from page 20](pdf-image://page_20_img_1) ![Image 2 from page 20](pdf-image://page_20_img_2) ## Page 21 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description hhmmss.sss 053106.000 North-south direction. N = North S = South Note that this field is empty in case of an invalid value. ddmm.mmmmmm 3149.334190 Longitude. ddd: Degrees (00–90) mm: Minutes (00–59) mmmmmm: Decimal fraction of minutes Note that this field is empty in case of an invalid value. Character N East-west direction. E = East W = West Note that this field is empty in case of an invalid value. dddmm.mmmmmm 11706.948654 Longitude. ddd: Degrees (000–180) mm: Minutes (00–59) mmmmmm: Decimal fraction of minutes Note that this field is empty in case of an invalid value. Character E East-west direction. E = East W = West Note that this field is empty in case of an invalid value. < ModeInd>1) Character DANN Mode indicator. A = Autonomous mode. Satellite system used in non-differential mode for position fixing D = Differential mode. Satellite system used in differential mode for position fixing. Corrections from ground stations or Satellite Based Augmentation System (SBAS) E = Estimated (dead reckoning) mode F = Float RTK. Satellite system used in RTK mode with floating integers M = Manual input mode N = No fix. Satellite system not used for position fixing, or fix not valid R = Real Time Kinematic (RTK). Satellite system used in RTK mode with fixed integers. 21 ![Image 1 from page 21](pdf-image://page_21_img_1) ![Image 2 from page 21](pdf-image://page_21_img_2) ## Page 22 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description Numeric 16 Total number of satellites in use. Range: 0–99. Numeric 0.63 Horizontal dilution of precision. Maximum value: 99.00. Note that this field is empty in case of an invalid value. Numeric Meter 51.287 Antenna altitude above the meansea- level (geoid). Note that this field is empty in case of an invalid value. M Character M Unit of . “M” = Meter. Numeric Meter -0.335 Geoid separation (the difference between the earth ellipsoid surface and the mean-sea-level (geoid) surface defined by the reference datum used in the position solution). Note that this field is empty in case of an invalid value. M Character M Unit of . “M” = Meter. Differential GPS data age. Not supported. Differential reference station ID. Not supported. Character V Navigational status indicator. Always “V” (Navigational status not valid). Hexadecimal \*05 Checksum Character Carriage return and line feed. Note: 1. 1) is a variable length field. The first character indicates the use of GPS satellites, the second character indicates the use of GLONASS satellites, and the third character indicates the use of Galileo satellites. The fourth character indicates the use of BDS satellites, the fifth character indicates the use of QZSS satellites, and the sixth character indicates the use of NavIC (IRNSS) satellites. . 22 ![Image 1 from page 22](pdf-image://page_22_img_1) ![Image 2 from page 22](pdf-image://page_22_img_2) ## Page 23 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. 2.2.9. GST Message GST Description GNSS Psuedorange Error Statistics. This sentence supports Receiver Autonomous Integrity Monitoring (RAIM). Pseudorange measurement error statistics can be translated in the position domain in order to give statistical measures of the quality of the position solution Type Output Message Structure: Example: Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters GN Talker identifier. See Table 4: NMEA Talker ID GST String, 3 characters GST GNSS Psuedorange Error Statistics hhmmss.sss 123624.000 UTC time of the GGA or GNS fix associated with this sentence. < RMS\_D> Numeric Meter 6.3 RMS value of the standard deviation of the range inputs to the navigation process. Numeric Meter 2.5 Standard deviation of semi-major axis of error ellipse. Numeric Meter 2.4 Standard deviation of semi-minor axis of error ellipse. Numeric Degree s 88.4 Orientation of semi-major axis of error ellipse. < LatD> Numeric Meter 2.4 Standard deviation of latitude error. Numeric Meter 2.5 Standard deviation of longitude error. Numeric Meter 5.9 Standard deviation of altitude error. Hexadecimal \*43 Checksum. Character Carriage return and line feed. $GST,,,,,,,,\* $GNGST,123624.000,6.3,2.5,2.4,88.4,2.4,2.5,9.2\*43 23 ![Image 1 from page 23](pdf-image://page_23_img_1) ![Image 2 from page 23](pdf-image://page_23_img_2) ## Page 24 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. 2.2.10. GRS Message GRS Description GNSS range residuals. This sentence supports Receiver Autonomous Integrity Monitoring (RAIM). Range residuals can be computed in two ways for this process. The basic measurement integration cycle of most navigation filters generates a set of residuals and uses these to update the position state of the receiver. Type Output Message Structure: Example: Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters GN Talker identifier. See Table 4: NMEA Talker ID GRS String, 3 characters GRS GNSS Range Residuals hhmmss.sss 125524.000 Position fix UTC. hh: Hours (00–23) mm: Minutes (00–59) ss: Seconds (00–59) sss: Decimal fraction of seconds Numeric 1 Residual calculation mode. 0 = Residuals were used to calculate the position given in the matching GGA or GNS sentence 1 = Residuals were recomputed after the GGA or GNS position was computed Start of repeat block. Repeat times: 12. < Resi> Numeric Meter -0.4 Range residuals for SVs used in navigation. Range: -999 to 999. Note that this field is empty in case of an invalid value. End of repeat block. $GRS,,{,},,\* $GNGRS,125524.000,1,-0.4,-0.7,0.5,-4.6,0.2,1.1,-2.2,-0.6,-1.1,9.2,-2.1,3.1,1,1\*42 $GNGRS,125524.000,1,-11.4,,,,,,,,,,,,1,1\*52 $GNGRS,125524.000,1,19.4,-5.0,11.4,6.3,-118,3.3,-7.5,,,,,,2,1\*79 $GNGRS,125524.000,1,-5.6,4.6,21.1,,,,,,,,,,3,7\*51 24 ![Image 1 from page 24](pdf-image://page_24_img_1) ![Image 2 from page 24](pdf-image://page_24_img_2) ## Page 25 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description Numeric 1 GNSS system ID. See Table 8: GNSS Satellites (NEMA) Numbering. Note that this parameter is only available in messages in line with NMEA 0183 V4.10 or later versions. Numeric 1 GNSS system ID. See Table 8: GNSS Satellites (NEMA) Numbering. Note that this parameter is only available in messages in line with NMEA 0183 V4.10 or later versions. Hexadecimal \*42 Checksum. Character Carriage return and line feed. 2.2.11. RLM Message RLM Description Return Link Message. The receiver will detect the Galileo Search and Rescue (SAR) Return Link Message when the RLM function is enabled Type Output Message Structure: Example: Parameter: Field Format Unit Example Description $ Character - $ Each NMEA message starts with $. String, 2 characters GN Talker identifier. See Table 4: NMEA Talker ID RLM String, 3 characters RLM Return Link Message Hexadecimal 9A22BE296 30F010 Beacon of RLM. Beacon ID 15 hex characters (60 bits). hhmmss.sss 055054.000 Position fix UTC. hh: Hours (00–23) mm: Minutes (00–59) ss: Seconds (00–59) sss: Decimal fraction of seconds $RLM,,,,\* $GARLM,9A22BE29630F010,125713.000,F,5402\*3B 25 ![Image 1 from page 25](pdf-image://page_25_img_1) ![Image 2 from page 25](pdf-image://page_25_img_2) ## Page 26 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Field Format Unit Example Description < Meg\_Code> Hexadecimal F Message code, a hex character (4 bits). Identifies the Type of RLM Message Service. 0 = Reserved for future RLM services. 1 = Acknowledgement Service RLM 2 = Command Service RLM 3 = Message Service RLM 4 – E = Reserved for future RLM services F = Test Service RLM (currently used only by the Galieo Program) Numeric 5402 The data parameters provided by RLS. Short message contains 4 hex characters (16 bits) and long message contains 24 hex characters (96 bits). Hexadecimal \*3B Checksum. Character Carriage return and line feed. 26 ![Image 1 from page 26](pdf-image://page_26_img_1) ![Image 2 from page 26](pdf-image://page_26_img_2) ## Page 27 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. 2.3. PAIR Messages This chapter explains PAIR messages (proprietary NMEA messages defined by the chipset supplier) supported by the modules. 2.3.1. Packet Type: 001 PAIR_ACK Message $PAIR001 Description Acknowledges a PAIR command. An acknowledgement packet $PAIR001 is returned to inform the sender that the receiver has received the packet. Type Output Message Structure: Example: $PAIR001,004,0\*3F Parameter: Field Format Unit Description Numeric - Type of command/packet to be acknowledged. Numeric 0 = Command has been successfully sent 1 = Command is being processed. Please wait for the result. 2 = Command sending failed. 3 = is not supported. 4 = Command parameter error. Out of range/Some parameters were lost/Checksum error. 5 = MNL service is busy. You can try again soon. 2.3.2. Packet Type: 002 PAIR\_GNSS\_SUBSYS\_POWER\_ON Message $PAIR002 Description Acknowledges a PAIR command. An acknowledgement packet $PAIR001 is returned to inform the sender that the receiver has received the packet. Type Command Message Structure: Example: $PAIR001,,\* $PAIR002\* $PAIR002\*38 $PAIR001,002,1\*38 $PAIR001,002,0\*39 27 ![Image 1 from page 27](pdf-image://page_27_img_1) ![Image 2 from page 27](pdf-image://page_27_img_2) ## Page 28 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. Parameter: None Result: Returns $PAIR001 message. 2.3.3. Packet Type: 003 PAIR\_GNSS\_SUBSYS\_POWER\_OFF Message $PAIR003 Description Power off GNSS system. Include DSP/RF/Clock and other GNSS modules. CM4 also can receive commands (Include the AT command / the race Command / the part of PAIR command which is not dependent on DSP.) after sending this command. Type Command Message Structure: Example: Parameter: None Result: Returns $PAIR001 message. Note: 1. The location service is not available after this command is executed. 2. The system can still receive configuration PAIR commands. The application is running if necessary. 3. CM4 will go to sleep if the application is not working at this time. The system can be awoken by the GNSS\_DATA\_IN\_EINT pin after going to sleep. $PAIR003\* $PAIR003\*39 $PAIR001,003,1\*39 $PAIR001,003,0\*38 28 ![Image 1 from page 28](pdf-image://page_28_img_1) ![Image 2 from page 28](pdf-image://page_28_img_2) ## Page 29 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. 2.3.4. Packet Type: 004 PAIR\_GNSS\_SUBSYS\_HOT\_START Message $PAIR004 Description Performs a hot start (uses all available data in the NVRAM). Normally a hot start means that the GNSS module has been powered down for less than 2 hours (RTC must be alive) with its ephemeris still valid. Therefore, there is no need to download an ephemeris again upon a hot start, thus making this startup method the fastest Type Command Message Structure: Example: Parameter: None Result: Returns $PAIR001 message. 2.3.5. Packet Type: 005 PAIR\_GNSS\_SUBSYS\_WARM\_START Message $PAIR005 Description Performs a warm start. A warm start means that the GNSS module remembers only rough time, position,and almanacs data, and thus needs to download an ephemeris before it can fix a position. Type Command Message Structure: Example: Parameter: None Result: Returns $PAIR001 message. $PAIR004\* $PAIR004\*3E $PAIR001,004,1\*3E $PAIR001,004,0\*3F $PAIR005\* $PAIR005\*3F $PAIR001,005,1\*3F $PAIR001,005,0\*3E 29 ![Image 1 from page 29](pdf-image://page_29_img_1) ![Image 2 from page 29](pdf-image://page_29_img_2) ## Page 30 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. 2.3.6. Packet Type: 006 PAIR\_GNSS\_SUBSYS\_COLD\_START Message $PAIR006 Description Performs a cold start, which means that there is no location information stored in the receiver, including time, position, and almanacs and ephemeris data. Type Command Message Structure: Example: Parameter: None Result: Returns $PAIR001 message. 2.3.7. Packet Type: 007 PAIR\_GNSS\_SUBSYS\_FULL\_COLD\_START Message $PAIR007 Description Performs a cold start and clears system and user configurations at the start, i.e., resets the module to its factory settings. Upon a full cold start, the module loses all data on the previous position. Therefore, it needs to search over the full frequency spectrum for all visible satellites before fixing a position. Type Command Message Structure: Example: Parameter: None Result: Returns $PAIR001 message. $PAIR006\* $PAIR006\*3C $PAIR001,006,1\*3C $PAIR001,006,0\*3D $PAIR007\* $PAIR007\*3D $PAIR001,007,1\*3D $PAIR001,007,0\*3C 30 ![Image 1 from page 30](pdf-image://page_30_img_1) ![Image 2 from page 30](pdf-image://page_30_img_2) ## Page 31 RYS352x PAIR Command Guide Copyright © 2023, REYAX TECHNOLOGY CO., LTD. 2.3.8. Packet Type: 010 PAIR\_REQUEST\_AIDING Message $PAIR010 Description Notifies the expiration of GNSS aiding data stored in the module. This message is automatically output when the module powers on Type Output Message Structure: Example: Parameter: Field Format Unit Description Numeric Type of data to be updated. 0 = EPO data 1 = Time 2 = Location Numeric Type of required GNSS data. 0 = GPS data 1 = GLONASS data 2 = Galileo data 3 = BDS data 4 = QZSS data Numeric Week Week number (including roll-over) Numeric Second Time of week Note: 1. The GNSS system outputs this message automatically. Do not send $PAIR010 manually. 2.3.9. Packet Type: 050 PAIR\_COMMON\_SET\_FIX\_RATE Message $PAIR050 Description Set Position Fix Interval. If set less than 1000 ms, ASCII NMEA will automatically increase the update interval in order to decrease IO throughput. It will return false if the operating voltage setting is not correct. (Any fix interval change between 1Hz <-> multihz causes GNSS to power on/off) Type Set Message Structure: $PAIR010,,,,\* $PAIR010,0,0,2044,369413\*33 $PAIR050,