A GNSS system need some time to create a Almanac ( a list of all satellites in the your sky region). For example, the RAK12500 (u-blox), can require until 12 minutes to complete the Almanac information. Other important point is the sky portion without obstacles. For example, if your gateway is installed in a building wall, all space behind the build is blocked and this kind of situation reduce the location precision. But it can be fixed moving the gatewa instalation to the roof
visually, the gps is installed correctly. the gateway logs show it doing pps sync w/ gps. also the main status page shows ‘close’ enough coordinates (in my first post) i’m wondering why the beacon info at the device doesn’t reflect the coordinates on the gateway status page.
Because this is a demo build we don’t have one b/w the antenna and gateway but we do have one on the POE. Other lightning arrestors in the vicinity are mounted higher than the gateway.
I am checking now this issue with our RUI3 team. I will get to you ASAP once I got any update.
PS We can also continue our communication via email if you prefer that support comms. Also, I moved the category to RAK3172 since it seems to be a device issue and not gateway.
we’re currently attaching to whatever aws uses going through the basicstation on the gateway. afaict (via the aws packet capture thing on their lora setup) there aren’t any proprietary frames on the LNS, just the join/data.