/members-area/personalblogs/b/blog/posts/adding-gps-functionality-to-the-bg96-on-the-telus-lte-m-iot-starter-kitPreviously, I developed an example program using the Telus LTE-M IoT Starter Kit (available from Avnet ) using the Mbed O/S. This effort is detailed in the Blog post https://www.element14.com/community/blogs/JimFlynn/2018/09/25/using-the-mbed-os...en-USTelligent Community 12https://community.element14.com/members-area/personalblogs/b/blog/posts/adding-gps-functionality-to-the-bg96-on-the-telus-lte-m-iot-starter-kitTue, 30 Jul 2019 19:24:33 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:84f006c6-edb4-4a21-8093-c1002895fac9ejeyaseelan0<p>is there a way for the application to first make a connection to the Azure iot hub even when the gps is not quite ready?</p><p>&nbsp;</p><p>when firing up the gps, cold indoors, it can take upto 45 mins or more, for the initial connection to the cloud, wondering if there is an easier work around to this somehow.</p><p>&nbsp;</p><p>Or, during development time, maybe a flag can be set during compile time to inform the application to report fake or manual (default lattitude, longitdue on bootup) and once more than x number of satellites are reported in line of sight, or a guaranteed fix is obtained, the application starts to reporting that.</p><p>&nbsp;</p><p>also perhpas, a user button press, to notify the application to bypass waiting for a gps fix.</p><p>&nbsp;</p><p>all of that to say, once the app boots up, it makes an initial connection to cloud and sends out an initial heartbeat that its alive and well etc</p><p>&nbsp;</p><p>just an idea.</p><img src="https://community.element14.com/aggbug?PostID=6114&AppID=293&AppType=Weblog&ContentType=0" width="1" height="1">