GSM Location info on LTE E-Series


#1

According to some ublox documentation on the SARA R410M it would seem that the celllocate function is not available in current firmware but will be in future firmware updates? Can anyone verify this?

Has anyone had any luck with any sort of GSM location functionality with the R410M? It would seem the google-maps-device-locator library is unable to pull cell tower info with this module.

Also, has anyone checked out the GNSS functionality? Looking to grab a module from ublox to see if it is doable.


[issue] (E0 LTE) GoogleMapsDeviceLocator not firing
#2

CellLocate is not supported on the SARA-R410M-02B according to the datasheet. Even if it is supported in a later revision, the u-blox modules are generally not field upgraded because in most cases it requires access to the u-blox USB interface and in any case it requires recertification of the device.

The GSM tower location should work. The google maps integration does not because the R410M requires the AT+UCGED command instead of AT+CGED and the response is different. I haven’t updated the library yet.


#3

Well, I think I was wrong. I’m pretty sure it’s not possible to do cell tower location on LTE (SARA-R410M-02B), the E Series LTE and Boron LTE.

The problem is that the necessary info: MCC, MNC, BSIC, and cell ID can only be retrieved using mode 2 or mode 3 for AT+UCGED. The command reference says the SARA-R4 only supports modes 0 and 5 and indeed querying the device says that it’s true.

     8.125 AT send      12 "AT+UCGED=?\r\n"
     8.136 AT read  +   19 "\r\n+UCGED:  (0,5) \r\n"

Unfortunately, mode 5 only returns the P-CID (E-UTRAN cell Physical Cell ID), not the Lcellid (E-UTRAN CI cell identifier), so it can’t be used for geolocation. And mode 0 doesn’t return anything other than OK.

I could be missing something, but I can’t find a way to get the necessary cell IDs.

And you can’t do CellLocate on the SARA-R410M-02B either, so it’s kind of hard to figure out where it is without GPS, apparently. That’s unfortunate.


Google Maps Device Locator integration and Mesh devices?
#4

Ouch. OK. Thanks Rick.


#5

From the datasheet, it shows the R410 can be updated OTA?

image


#6

In theory, FOAT could be used to upgrade the modem firmware. However, there are three problems:

  • It’s megabytes in size, far too large to buffer on the E Series/Boron
  • It takes something like a half hour to complete
  • The hardware would need to undergo certification again

#7

Can you suggest an alternative to calculating approximate position. For my specific application, I do not need GPS level tracking. An approximation is adequate. I remember seeing online there is algorithm which can be used on the device to calculate this approximation, which is basically what Google Maps service was doing. I’m afraid this will require the same information which is not available from LTE/ublox hardware. I’m trying to locate the article. I will post here once I find.


#8

I believe this is the article I was reviewing before. Do you know off the top of your head if the new LTE/u-blox hardware supports CellLocate capability?


#9

CellLocate is not supported on the u-blox SARA-R410M-02-B (E Series LTE or Boron LTE).


#11

Thanks. Sorry, I read further your responses above and you stated this is the current situation and as now, I am out of luck using these devices unless I add a GPS module.


#12

With some important caveats, you can now get approximate (1 tower) cell tower location on the E Series LTE!

The google-maps-device-locator library 0.0.5 is required. No code changes are required.

The problem is that the u-blox SARA-R410M-02B does not support the AT+CGED command that the SARA-U and SARA-G do, and AT+UCGED does not provide any useful information for geolocation.

I can get the cell identifier (CI) and LAC using the AT+CREG command. Unfortunately I can’t get the operator, MCC, and MNC efficiently.

However, the caveat is that the E Series LTE only works on AT&T in the United States, so it will always be “AT&T”, 310, 410. So you can get your location anywhere in the United States now.


The Boron does not currently work with the cell locator because as of 0.8.0-rc.25 it does not yet support Cellular.command. But when it does, there’s a new google-maps-device-locator method to pass in the operator, MCC, and MNC if you are using a 3rd-party SIM card with the Boron LTE. It’s not ideal, but better than nothing if you know approximately where you are.


#13

@rickkas7 Quick question from you last post on this topic, the Boron can or can’t obtain approximate cell tower location with library version 0.0.5 and 0.8.0-rc.25? I’m able to successfully receive and pass location data when utilizing the project code and an Argon, but receive no location data when attempting with the Boron.


#14

It is not possible to get location data on either Boron (2G/3G or LTE) using 0.8.0-rc.26 or older. The reason is that Cellular.command, necessary to get the tower information, is not supported in those versions on the Boron.

I don’t know what version it will be added in, but it’s a known issue that will be addressed.


#15

Awesome. That’s a pretty good start for me. My application is US based and even if I can only get approximate 1 tower for now, that is good for my situation. I simply need to demonstrate the concept and test the ability to track approximate locations with long battery life.