# Not "always" getting \_track.qo notes

**URL:** https://discuss.blues.com/t/not-always-getting-track-qo-notes/3111
**Category:** Notecard API
**Created:** [June 18, 2025, 2:46pm UTC](https://discuss.blues.com/t/not-always-getting-track-qo-notes/3111 "2025-06-18T14:46:11Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![richf](https://avatars.discourse-cdn.com/v4/letter/r/74df32/32.png) [@richf](https://discuss.blues.com/u/richf)
#### Post date: [June 18, 2025, 2:46pm UTC](https://discuss.blues.com/t/not-always-getting-track-qo-notes/3111/1 "2025-06-18T14:46:11Z")

</div>

Hi, my topic is similar to one posted on Dec 2022 [Not getting \_track.qo notes after initial Satellite Fix] - one big difference is that I’m not using the Notecard’s GPS engine – rather importing external GPS (NMEA) strings (via microController) and feeding the Lat/Lon via “NoteSetLocation()”.

Referring to page 4/19 on the above noted post – My sequence

NoteNewRequest(“hub.set”) [with “my” ProductID etc]  
NoteSetLocationMode(“fixed”, 280 /\* seconds \*/);  
NoteNewRequest(“card.location.track”);

I don’t presently use motion mode.  
After the setup commands are sent, I issue a ‘hub’ sync.

Do I need to programmically disable 'the on board GPS engine?

I find that “sometimes” a \_track.qo event happens – but not continuously and I can’t match the reason it was posted

I then periodically (every 10 seconds), post the current Lat/Lon values via NoteSetLocation(). I’m using a Lat/Lon simulator which allows for location ‘movement’.

Thanks for the help,  
Rich ..

---

<div class="post-metadata">

### Author: ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)
#### Post date: [June 20, 2025, 5:38pm UTC](https://discuss.blues.com/t/not-always-getting-track-qo-notes/3111/2 "2025-06-20T17:38:49Z")

</div>

Hi @richf,

When using a separate GPS/GNSS module, the best practice is to allow the Notecard to utilize it directly per our [guide on using an external GPS](https://dev.blues.io/example-apps/sample-apps/continuous-asset-tracking-with-external-gps-and-immediate-location-sync/).

Setting the `seconds` argument while using `fixed` in your `card.location.mode` request doesn’t do anything (that argument is only supported in `periodic` mode). Also, using `card.location.track` is only supported when the GPS module is in `periodic` mode anyway - [see the API docs here](https://dev.blues.io/api-reference/notecard-api/card-requests/latest/#card-location-track). The Notecard will only generate the `_track.qo` Notes if motion is detected as well.

I see what you’re trying to do, but in order to use a “fixed” location that is updated repeatedly, you’d have to effectively generate your own “track” Notes yourself in firmware instead of relying on the Notecard. You would also have to use `card.location.mode/"off":true` to disable the onboard GPS (otherwise you could run into conflicts between GPS and cell which could explain the “missing” Notes that you reported above).

A lot going on here, but I hope that helps!  
Rob
