Lantronix G520 G520 User Guide - Page 102

GPGSV Format

Page 102 highlights

10: Services Parameters Description End of message termination (1) A valid status is derived from all the parameters set in the software. This includes the minimum number of satellites required, any DOP mask setting, presence of DGPS corrections, etc. If the default or current software setting requires that a factor is met, and then if that factor is not met the solution will be marked as invalid. (2) CSR Technology Inc. does not support magnetic declination. All courses over ground data are geodetic WGS84 directions relative to true North. (3) Position was calculated based on one or more of the SVs having their states derived from almanac parameters, as opposed to ephemerides. (4) This feature is supported in the GSD4e product only. (5) This feature is supported in the GSD4e product, version 1.1.0 and later. GPGSV Format The $GPGSV includes the number of satellites in view, satellite ID numbers and their evaluation, azimuth and signal-to-noise ratio. Example: $GPGSV,4,1,16,21,50,358,38,22,28,272,37,29,53,164,36,18,51,319,31,*71E IMEI number is added at the start of every frame. Parameters MID GSV Parameters MID Number of Messages(1) Message Number(1) Satellites in View(1) Satellite ID Elevation Azimuth SNR (C/N0) .... Satellite ID Table 10-12 GPGSV Data Format Description GSV Protocol Header Example - $GPGSV Total number of GSV messages to be sent in this group Example - 4 Message number in this group of GSV messages Example - 1 16 Channel (Range 1 - 32) Example - 21 Channel 1 (Maximum 90) Example - 50 degrees Channel (True, Range 0 - 359) Example - 358 degrees Range 0 - 99, null when not tracking Example - 38dBHz (Satellite ID, elevation, azimuth, and SNR repeated for each satellite in view) Channel 4 (Range 1 - 32) Example - 18 G520 Series IoT Cellular Gateway User Guide 102

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225

10: Services
G520 Series IoT Cellular Gateway User Guide
102
(1)
A valid status is derived from all the parameters set in the software. This includes the minimum num
-
ber of satellites required, any DOP mask setting, presence of DGPS corrections, etc. If the default or cur
-
rent software setting requires that a factor is met, and then if that factor is not met the solution will be
marked as invalid.
(2)
CSR Technology Inc. does not support magnetic declination. All courses over ground data are geo
-
detic WGS84 directions relative to true North.
(3)
Position was calculated based on one or more of the SVs having their states derived from almanac
parameters, as opposed to ephemerides.
(4)
This feature is supported in the GSD4e product only.
(5)
This feature is supported in the GSD4e product, version 1.1.0 and later.
GPGSV Format
The $
GPGSV
includes the number of satellites in view, satellite ID numbers and their evaluation,
azimuth and signal-to-noise ratio.
Example: $GPGSV,4,1,16,21,50,358,38,22,28,272,37,29,53,164,36,18,51,319,31,*71E
IMEI number is added at the start of every frame.
Table 10-12
GPGSV Data Format
<CR><LF>
End of message termination
Parameters
Description
MID GSV Parameters
MID
GSV Protocol Header
Example – $GPGSV
Number of Messages
(1)
Total number of GSV messages to be sent in this group
Example – 4
Message Number
(1)
Message number in this group of GSV messages
Example – 1
Satellites in View
(1)
16
Satellite ID
Channel (Range 1 – 32)
Example – 21
Elevation
Channel 1 (Maximum 90)
Example – 50 degrees
Azimuth
Channel (True, Range 0 – 359)
Example – 358 degrees
SNR (C/N0)
Range 0 – 99, null when not tracking
Example – 38dBHz
….
(Satellite ID, elevation, azimuth, and SNR repeated for each satellite in
view)
Satellite ID
Channel 4 (Range 1 – 32)
Example – 18
Parameters
Description