# Unable to get Positioning fix with LAF 17.10

**URL:** <https://mangoh.discourse.group/t/unable-to-get-positioning-fix-with-laf-17-10/1036>\
**Category:** mangOH Red\
**Created:** [December 28, 2017, 1:34pm UTC](https://mangoh.discourse.group/t/unable-to-get-positioning-fix-with-laf-17-10/1036 "2017-12-28T13:34:07Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohamid](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@mohamid](https://mangoh.discourse.group/u/mohamid)\
**Post date:** [December 28, 2017, 1:34pm UTC](https://mangoh.discourse.group/t/unable-to-get-positioning-fix-with-laf-17-10/1036/1 "2017-12-28T13:34:07Z")

</div>

I used the example position on demand application that is available in the documentations. This was working on the MangOH red with LAF 17.07 using an active antenna (passive antenna was pants). But since migrating to 17.10 I can no longer get a fix. What has changed in the positioning components? I can’t go back to 17.07 since my application doesn’t work with the le\_data api of 17.07.

---

<div class="post-metadata">

**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\
**Post date:** [December 28, 2017, 9:15pm UTC](https://mangoh.discourse.group/t/unable-to-get-positioning-fix-with-laf-17-10/1036/2 "2017-12-28T21:15:54Z")

</div>

> [@mohamid](#):
>
> I used the example position on demand application that is available in the documentations. This was working on the MangOH red with LAF 17.07 using an active antenna (passive antenna was pants). But since migrating to 17.10 I can no longer get a fix. What has changed in the positioning components? I can’t go back to 17.07 since my application doesn’t work with the le\_data api of 17.07.

Have you tried with AT commands as mentioned in this post

> [@GPS antenna subjective tests](http://mangoh.discourse.group/t/gps-antenna-subjective-tests/1011):
>
> Guys, We did some subjective tests for GPS antennas with following antennas : 1- Mfg: Taoglas, Digi-key p/n: 931-1406-ND AGGBP.25B.07.0060A Description ANT MOD GPS 60MM 2STAGE MHFI SAW 2- Mfg: Abracon LLC, Digi-key p/n: 535-12616-ND APAM1866YA18 Description ACTIVE INTRNL ANT 1575.42MHZ GPS 3- Mfg: Yageo, Digi-key p/n: 311-1541-ND ANT2525JB08B1575A Description ACTIVE ANT GPS USE 25X25X4 4- Mfg: Inventek, Digi-key p/n: 1475-1008-ND ACTPAT254-01-IP Description ANT GPS CERAMIC U.FL AT …

There should really be no change between 17.07 and 17.10 that might cause this issue.

---

<div class="post-metadata">

**Author:** ![mohamid](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@mohamid](https://mangoh.discourse.group/u/mohamid)\
**Post date:** [December 28, 2017, 10:34pm UTC](https://mangoh.discourse.group/t/unable-to-get-positioning-fix-with-laf-17-10/1036/3 "2017-12-28T22:34:17Z")

</div>

Didn’t go though the lot but this is what looks out of place so far

AT!GPSSTATUS?  
Current time: 2017 12 28 3 22:32:30

2017 12 28 3 22:30:35 Last Fix Status = FAIL, FAILCODE = 9  
2017 12 28 3 22:31:35 Fix Session Status = ACTIVE

No TTFF available

OK

---

<div class="post-metadata">

**Author:** ![mohamid](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@mohamid](https://mangoh.discourse.group/u/mohamid)\
**Post date:** [December 28, 2017, 10:38pm UTC](https://mangoh.discourse.group/t/unable-to-get-positioning-fix-with-laf-17-10/1036/4 "2017-12-28T22:38:26Z")

</div>

I had done no other software modifications other than update the LAF so it was my primary suspect. it could be the hardware, but the same response is being shown on two mangOH Red boards

---

<div class="post-metadata">

**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\
**Post date:** [December 29, 2017, 6:59am UTC](https://mangoh.discourse.group/t/unable-to-get-positioning-fix-with-laf-17-10/1036/5 "2017-12-29T06:59:44Z")

</div>

So you never get a fix or dont get a fix as quickly as before? Do you have clear visibility to sky?

---

<div class="post-metadata">

**Author:** ![mohamid](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@mohamid](https://mangoh.discourse.group/u/mohamid)\
**Post date:** [December 29, 2017, 11:38am UTC](https://mangoh.discourse.group/t/unable-to-get-positioning-fix-with-laf-17-10/1036/6 "2017-12-29T11:38:41Z")

</div>

no I don’t get fix at all. Yes I have clear sky. I have tried it on two different boards

---

<div class="post-metadata">

**Author:** ![mlw](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/mlw/32/434_2.png) [@mlw](https://mangoh.discourse.group/u/mlw)\
**Post date:** [January 4, 2018, 1:43pm UTC](https://mangoh.discourse.group/t/unable-to-get-positioning-fix-with-laf-17-10/1036/7 "2018-01-04T13:43:36Z")

</div>

Mohamid,

I have just plugged my unit in and it started working happily with 17.11 (again very little difference between 17.10 and 17.11). Things to double check.

- Bias voltage on the antenna connector to make sure the LNA is actually running.

- How are you starting the GPS session? Mine is set to autostart as per below.

- Fail code 9 is ‘user ended the session’ so either there was a Legato or AT command sent to stop it or the session timed out because it could not find a fix within its time limit.

OK

Regards

Matt
