When will we have Cellular.command on the Boron (Date?) and will we be able to use AT+ULOC for CellLocate, GNSS or Both(Hybrid) I need Lat/Lng from ublox device. I need this If I cant get this on the boron what other device that is LTE(us) can I get this on? Is this supported on the E series?
Cellular.command will be available within a few weeks.
However, the LTE modem (u-blox SARA-R410M-02-B) does not support CellLocate. It would be difficult to use GNSS since the DDC interface isn’t exposed. This is a limitation of the modem so this is also the case with the E Series LTE.
It is possible to use the connected tower information in some cases to get a 1 tower approximate location using an external service (like Google GeoLocation) with LTE devices.
The Boron 2G/3G (SARA-U201) does support CellLocate.
What is the long term support for the SARA-U201 in North America is AT&T phasing out 3G by 2021?
In the United States, the Boron 2G/3G (u-blox SARA-U201) uses T-Mobile only, which has not set a sunset date for 3G.
The E Series E310 (u-blox SARA-U201) uses AT&T or T-Mobile, and will continue to use T-Mobile after AT&T ends 3G service.
However in general we recommend LTE in the United States, unless you need CellLocate.
Thanks for the fast response.
1 cell tower location would work.
My Question is: When Cellular.command starts working on the Boron LTE the Google Maps Geolocation will work?
Google Maps Geolocation should work on the Boron 2G/3G on the first release with Cellular.command.
There is a problem in the Cellular.command implementation that prevents the Boron LTE from being able to get the cell tower ID needed for geolocation. It will be fixed in Device OS, but it was non-trivial to fix so it won’t be available in the first Cellular.command release.
Hello, does Google Maps Geolocation work with Boron LTE? I have followed the turorial: Google Maps | Tutorials | Particle
and can’t get any response from either the Boron or googleapis.com
Thank you
Yes, geolocation works with the Boron LTE. Make sure you are using library version 0.0.7 (2020-08-12) and Device OS 1.2.1 or later (2.0.0 recommended).
Thanks for the quick reply!
Yes I am using Device OS 2.0.0 and library version 0.0.7
When I try the https request to see if ‘something’ is working I get a webpage with
This www.googleapis.com page can’t be found…
No webpage was found for the web address: https://www.googleapis.com/geolocation/v1/geolocate?key=AIza[my key]U_M18qHn0
HTTP ERROR 404
Is that an indication there’s something wrong with my Google Cloud service?
Thanks for your help.
The Google Geolocation API returns a 404 if the location is not found, so it could be that the tower ID is not known by Google. The tower ID database does not list every tower. It can also happen if the request isn’t correctly formatted.
Thank you.
Should my Boron at least be putting out an error?
After flashing with the sample program (from the tutorial), I get nothing in the Events console after it flashes successfully and goes through the normal messaging, ending with no updates pending…
Yes, you should be seeing the events show in the testing it out section of the tutorial. If you’re not, that would be the first thing to troubleshoot.
I’d check the USB serial debug log using particle serial monitor to see if there’s an error displayed there.
Ok; thank you! If I get it working, I’ll post again here.
Not having much luck today. After finding that I couldn’t see serial output using the Arduino IDE for some reason, I used the Particle CLI serial monitor.
The Boron gets as far as:
publishLocation
scanData=
and then seems to sit there; no further output. Does that mean something to you?
(let me know if I should be using another forum for soliciting help; I appreciate your time but don’t want to impose on you)
This is a more complete output (the testing Tracker was me checking that the serial output seemed to be working):
