Tower Location/Trianglation with Boron?

Firmware
1

Does the locator library work with Boron? I integrated it into my code and it never calls out to the Webhook.

I get this in the logs:
publishLocation
0001099649 [ncp.at] TRACE: > AT+CGED=5
0001099978 [ncp.at] TRACE: < ERROR
0001099979 [ncp.at] TRACE: > AT+CGED=3
0001099984 [ncp.at] TRACE: < ERROR
0001099984 [ncp.at] TRACE: > AT+UDOPN=9
0001100014 [ncp.at] TRACE: < +UDOPN: 6,"AT&T"
0001100015 [ncp.at] TRACE: < OK
scanData=

which looks suspiciously like the modem is erroring when the library asks for the tower info. But the modem obviously exports this data since it is available in the particle web console.

code is:

#include "locator.h"

SYSTEM_MODE(AUTOMATIC);
SYSTEM_THREAD(ENABLED);

Locator locator;

void setup() {
locator.withLocatePeriodic(120);
}

void loop()
{
locator.loop();
}

Thoughts or ideas? Do I need to delve into the library deeper to add support for Boron?

2

Hey @mfarver,

Unfortunately the modems on our LTE Boron SKUs do not have support for the AT command set required for the locator library.

If this is a requirement for your use case, you may take a look at our Tracker series. In addition to an onboard GPS, they also support geolocation via nearby WiFi access points as well as from local cell towers. We have a cloud-based service called Location Fusion that will combine data from all of these sources and provide an improved accuracy fix.

1 Like
3

Does B SOM work with the library? Or solely tracker (which is a significantly more expensive option)?

4

Unfortunately, the BSOM uses the same modem as the Borons, so the same applies. The Tracker line uses a different modem, and therefore is the only option for supporting this functionality. It does so out of the box, however, and does not require this library.

1 Like