# HL7800 GPS is way off

**URL:** <https://forum.sierrawireless.com/t/hl7800-gps-is-way-off/17321>\
**Category:** HL78\
**Created:** [August 20, 2019, 7:56pm UTC](https://forum.sierrawireless.com/t/hl7800-gps-is-way-off/17321 "2019-08-20T19:56:19Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rique](https://avatars.discourse-cdn.com/v4/letter/r/d26b3c/32.png) [@Rique](https://forum.sierrawireless.com/u/Rique)\
**Post date:** [August 20, 2019, 7:56pm UTC](https://forum.sierrawireless.com/t/hl7800-gps-is-way-off/17321/1 "2019-08-20T19:56:19Z")

</div>

Have our prototype running with the HL7800. All seems to work fine except the GPS.  
First, it takes the GPS almost a minute to get a GPS lock.

Secondly, and most strangely, when we do an at+gnssloc? we get a location that is about 30km away from our present location.

We are using an active ceramic antenna from Taoglas (pn: aggbp.25b), delivring about 3.5 volts to it. It’s capable of using up to 5 volts.

We are using firmware v3.4.4.3

Any ideas?

---

<div class="post-metadata">

**Author:** ![Sierra\_klin2](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/sierra_klin2/32/4769_2.png) [@Sierra\_klin2](https://forum.sierrawireless.com/u/Sierra_klin2)\
**Post date:** [August 21, 2019, 9:13am UTC](https://forum.sierrawireless.com/t/hl7800-gps-is-way-off/17321/2 "2019-08-21T09:13:53Z")

</div>

Hi Rique,

For GPS cold start, it may take a long time to fix.  
For 30km issue, could you provide your result of at+gnssloc? and your exact position?

---

<div class="post-metadata">

**Author:** ![Rique](https://avatars.discourse-cdn.com/v4/letter/r/d26b3c/32.png) [@Rique](https://forum.sierrawireless.com/u/Rique)\
**Post date:** [August 21, 2019, 9:09pm UTC](https://forum.sierrawireless.com/t/hl7800-gps-is-way-off/17321/3 "2019-08-21T21:09:48Z")

</div>

AT+gnssloc? position reported: 43 Deg 14 Min 21.97 Sec N 80 Deg 17 Min 1.22 Sec W

Our exact position is: 43°23’56.7"N 80°28’22.2"W

---

<div class="post-metadata">

**Author:** ![Sierra\_klin2](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/sierra_klin2/32/4769_2.png) [@Sierra\_klin2](https://forum.sierrawireless.com/u/Sierra_klin2)\
**Post date:** [August 22, 2019, 6:59am UTC](https://forum.sierrawireless.com/t/hl7800-gps-is-way-off/17321/4 "2019-08-22T06:59:49Z")

</div>

Hi Rique，

It seems the degrees minutes seconds (DMS) is wrong in AT+gnssloc?.  
Please convert the correct DMS from GPRMC(dd.mmmmmmm).

---

<div class="post-metadata">

**Author:** ![Rique](https://avatars.discourse-cdn.com/v4/letter/r/d26b3c/32.png) [@Rique](https://forum.sierrawireless.com/u/Rique)\
**Post date:** [August 22, 2019, 8:07am UTC](https://forum.sierrawireless.com/t/hl7800-gps-is-way-off/17321/5 "2019-08-22T08:07:18Z")

</div>

the DMS is what I got right from AT+gnssloc?

GPRMC gives me this string  
$GPRMC,080441.00,A,4323.9371,N,08028.3706,W,0.3,29.6,220819,A,-1.41e-08\*2A

so when I plug 43.239371 -80.283706 into Google, I get the same wrong location.

---

<div class="post-metadata">

**Author:** ![mapart](https://avatars.discourse-cdn.com/v4/letter/m/e9c0ed/32.png) [@mapart](https://forum.sierrawireless.com/u/mapart)\
**Post date:** [August 22, 2019, 8:38am UTC](https://forum.sierrawireless.com/t/hl7800-gps-is-way-off/17321/6 "2019-08-22T08:38:59Z")

</div>

The format of the GPRMC position is in Degrees Decimal Minutes (DDM) whereas the format you use in google is Decimal Degrees (DD).  
What you get from GPRMC in DDM:

**Latitude:**  
Degrees = 43  
Minutes = 23.9371  
N  
**Longitude:**  
Degree = 80  
Minutes = 28.3706  
W

In DD this would be:  
Latitude: 43.398952  
Longitude: -80.472843

Martin

---

<div class="post-metadata">

**Author:** ![Rique](https://avatars.discourse-cdn.com/v4/letter/r/d26b3c/32.png) [@Rique](https://forum.sierrawireless.com/u/Rique)\
**Post date:** [August 22, 2019, 9:07am UTC](https://forum.sierrawireless.com/t/hl7800-gps-is-way-off/17321/7 "2019-08-22T09:07:27Z")

</div>

Ah thank you for the clarity.  
And I found a nice tool to convert the entire string to something useful, and I found that the location is indeed accurate in the string…So it looks like at+GNSSLOC? is converting it incorrectly.

[https://rl.se/gprmc](https://rl.se/gprmc)

Thanks again.
