# New RAK7246G update\_location\_from\_status

**URL:** <https://www.thethingsnetwork.org/forum/t/new-rak7246g-update-location-from-status/52530>\
**Category:** RAK Gateways\
**Created:** [October 19, 2021, 3:50pm UTC](https://www.thethingsnetwork.org/forum/t/new-rak7246g-update-location-from-status/52530 "2021-10-19T15:50:14Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![hphillip](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/hphillip/32/46261_2.png) [@hphillip](https://www.thethingsnetwork.org/forum/u/hphillip)\
**Post date:** [October 19, 2021, 3:50pm UTC](https://www.thethingsnetwork.org/forum/t/new-rak7246g-update-location-from-status/52530/1 "2021-10-19T15:50:15Z")

</div>

I have a RAK7246G gateway on TTN “v3” that I intend to move position from time to time.

It is running latest available firmware from RAK i.e, RAK7246\_on\_Raspbian\_OS\_V4.2.5\_20200909.img

In the console I have selected “Update from status messages”  
I see this confirmation of my intention in the Event details

```auto
"data": {
    "@type": "type.googleapis.com/google.protobuf.Value",
    "value": [
      "antennas",
      "location_public",
      "update_location_from_status"
    ]
  },

```

The GPS is functioning correctly, in the sense that I am seeing the correct longitude/latitude/altitude in every status message.

However in the console location overview, the map of the world is overlaid with “No location information available” rather than marking the current public position of the gateway.

The thread ‘[V3 Gateway Console not GW-GPS-Information are shown in the Console](https://www.thethingsnetwork.org/forum/t/v3-gateway-console-not-gw-gps-information-are-shown-in-the-console/45387)’  
did not provide any further clues/solution hence hoping all you experts what I should try next!

BTW, this gateway has not migrated from v2: it has only existed on v3

Any ideas?

---

<div class="post-metadata">

**Author:** ![kersing](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/kersing/32/44777_2.png) [@kersing](https://www.thethingsnetwork.org/forum/u/kersing)\
**Post date:** [October 19, 2021, 4:15pm UTC](https://www.thethingsnetwork.org/forum/t/new-rak7246g-update-location-from-status/52530/2 "2021-10-19T16:15:56Z")

</div>

> [@hphillip](#):
>
> move position from time to time

Ouch, that is going to hurt all nodes with ADR in the vicinity. Unless you have a second gateway at the same location…

---

<div class="post-metadata">

**Author:** ![hphillip](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/hphillip/32/46261_2.png) [@hphillip](https://www.thethingsnetwork.org/forum/u/hphillip)\
**Post date:** [October 19, 2021, 4:40pm UTC](https://www.thethingsnetwork.org/forum/t/new-rak7246g-update-location-from-status/52530/3 "2021-10-19T16:40:07Z")

</div>

There is a second gateway at fixed location. The “mobile” one is just for experimentation and range is very restricted (deliberately). It would be brought into play mainly for ad-hoc “fox hunting” 😉

---

<div class="post-metadata">

**Author:** ![hphillip](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/hphillip/32/46261_2.png) [@hphillip](https://www.thethingsnetwork.org/forum/u/hphillip)\
**Post date:** [October 24, 2021, 10:00am UTC](https://www.thethingsnetwork.org/forum/t/new-rak7246g-update-location-from-status/52530/4 "2021-10-24T10:00:36Z")

</div>

Time for a “Fox” hunt I think!  
Today I am getting frequent “Confirmed uplink” messages with good SNR, but sadly only a few seconds apart. Device Address suggests this is not aimed at TTN, but it is still having an impact ☹

![ConfirmedUplinks](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/0/3/035a3ddc2f458caed519bdcbb0f56e035a414135.jpeg)

This is probably one of the rare cases where a yagi could be justified (hooked up to my movable gateway) 😉

---

<div class="post-metadata">

**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\
**Post date:** [October 24, 2021, 11:02am UTC](https://www.thethingsnetwork.org/forum/t/new-rak7246g-update-location-from-status/52530/5 "2021-10-24T11:02:36Z")

</div>

> [@hphillip](#):
>
> This is probably one of the rare cases where a yagi could be justified

I don’t understand - under what conditions does a new bit of kit need justifying?

---

<div class="post-metadata">

**Author:** ![hphillip](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/hphillip/32/46261_2.png) [@hphillip](https://www.thethingsnetwork.org/forum/u/hphillip)\
**Post date:** [October 24, 2021, 11:23am UTC](https://www.thethingsnetwork.org/forum/t/new-rak7246g-update-location-from-status/52530/6 "2021-10-24T11:23:03Z")

</div>

I’m not saying I would _have_ to use a yagi(!), but to help get a bearing on a rogue signal, it would be invaluable. Otherwise, I left with just sampling RSSI/SNR in different locations while the rogue broadcaster is active.  
Who knows, it may be just an experimenter in my own street, or a user with excessive power further afield. If I can just peak up the reception signal strength I’ll have more chance finding the source.  
And in the end it may turn out to be perfectly legitimate use of the band and not a rogue experimenter!

---

<div class="post-metadata">

**Author:** ![hphillip](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/hphillip/32/46261_2.png) [@hphillip](https://www.thethingsnetwork.org/forum/u/hphillip)\
**Post date:** [October 27, 2021, 12:13pm UTC](https://www.thethingsnetwork.org/forum/t/new-rak7246g-update-location-from-status/52530/7 "2021-10-27T12:13:58Z")

</div>

This seemed the right thread to include this known issue, just FYI: ![KnownIssue](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/f/5/f59935a4067500b229f2c54e15c2bbbf05253b25.jpeg)