Latest Contributions by DanColbert

Hi Kean, Yes, you'll need to use Trimble Mobile Manager (TMM) to configure and manage the RTK source.  You'll need to leave TMM running in the background in order to maintain connection to the RTK source. Once that's configured, Survey123 will receive RTK corrections. Regards, Dan ... View more

Hello Kean, It's likely that you need to reset the receiver before the FW update takes effect for the iOS changes (I'm assuming that's the platform you're using). Here is a detailed note outlining the procedure: https://trl.trimble.com/docushare/dsweb/Get/Document-978090/Support%20Note%20-%20Trimble%20R2%20with%20Survey123%20and%20other%20NMEA%20apps%20(June%202021).pdf Regards, Dan ... View more

Hello all who are following this thread.  I'm happy to report that Trimble R2 FW 5.51 is live and now supports iOS connection to Survey123  (and QuickCapture)! Please use Trimble Installation Manager  to update your R2 with this latest FW update.  Please also read through the accompanying Support Note, and if you're interested to read further details, the Release Notes are also available. Thank you for all of your support and patience. ... View more

Hi Eric, The FW for the R2 is expected very soon. It's currently in the final stages of release testing. I'll be sure to post an update here when it becomes available. ... View more

Hi Kean, We're currently working on an updated firmware release for the R2 that will enable it to work with Survey123.  As soon as the firmware is available, I'll update this thread (and a few others). Regards, Dan ... View more

Byron - You only need to run GNSS Status if you're using an internet-based correction source such as VRS or Direct IP. If you're just using SBAS or Satellite RTX, configure it once using GNSS Status, and that's it. Subsequent connections will then not require GNSS Status to be running. We're making progress on the R2 FW. That platform is a bit more complex and requires different engineering and QA procedures. No definitive timeline at this point for the release, but we're targeting "ASAP". ... View more

You're correct, access to metadata on iOS will not be possible outside of whatever the iOS Location Services API provides.  Furthermore, HTML5 Geolocation API has different implementation on different browsers and OSes.  You'll unfortunately see different behavior across mobile platforms (Android & iOS), and desktop (Windows & MacOS), and browsers (Safari, Chrome, IE, Edge, Firefox), and all the permutations. Some browsers will return the most current position from LocationServices, but only update that location if it changes by some threshold distance or time interval.  Some will return the location from a reverse IP lookup.  Unfortunately those implementations are a bit of a black-box, and GNSS manufacturers have no control over it, unfortunately. So much for write-it-once-run-it-many, huh?  ... View more

You're mostly correct, Malcolm. Yes, Collector uses the Trimble SDK and as such, has full access to all metadata on all platforms.  The Trimble SDK has additional benefits such as the ability to configure the receiver (real-time sources, etc.) from within an application - as opposed to a user having to go to an external application to do that.   Survey123 and QuickCapture are not WebApplications in the strictest sense.  They are native applications. On Android: GNSS Manufacturers have the ability to overwrite the devices internal GNSS positions using what's called a Mock Location Provider - it basically takes the external GNSS position and makes it look, to Android Apps, like the device internal provider.  In some cases, as with Trimble, we use an additional Android facility called "Location Extras" which is where we can put all the extended metadata not typically available through the standard location services.  Survey123 and QuickCapture make use of this procedure with Trimble GNSS devices. On iOS: GNSS Manufacturers have two options as well, though significantly different in implementation Override the internal device GNSS:  Through the GNSS Device manufacturer's Bluetooth implementation, the External GNSS receiver will automatically override the internal device GNSS when connected.  While this is convenient and simple, iOS doesn't support any extra metadata over this method.  This is the method which is used by the Trimble R2 currently. If using an R2, configure Survey123 and QuickCapture to use the "Internal Location Provider" when connected to the R2 - until the R2 supports the following (coming soon): NMEA Data over dedicated iAP Channel:  A manufacturer also has the option to support what amounts to a dedicated channel for streaming NMEA data.  Once white-listed as an application (such as Survey123 & QuickCapture) for clearance to use said channel, that application has access to all data (including metadata via NMEA) from the External Device.  In this case, the application uses this external channel as the source for all position information and bypasses the internal GNSS.  The Trimble R1 supports this currently (FW v5.44+), and the Trimble R2 will support this soon, as indicated elsewhere in this thread. ... View more

Hi Ryan, there is a FW update required in order to support the type of connection to Survey123 which supports metadata output.  That update is in process and will be released as soon as possible.  I'll update this thread (and others) with that information when available. ... View more

The R1 is fully supported out of the box, and includes full GNSS Metadata.  Simply pair the R1 to the iOS device, and then choose the R1 as the location provider in Survey123. Standard receiver configuration such as real-time sources still need to be configured using GNSS Status.  Other than that, no other receiver configurations are required. The R2 is supported on iOS, but without GNSS Metadata.  To achieve this, pair and connect the R2 to the iOS device and choose "Integrated Provider".  In this case, positions will be provided from the R2, but without GNSS Metadata. The R2 is supported on Android through Android Mock Location provider and includes GNSS Metadata.  On Windows, the R2 is supported through standard Bluetooth COM and NMEA. ... View more

Yes.  All correction services are supported. ... View more

Support for the R2 in QuickCapture (and Survey123) on Android is through Mock Locations and Location Extras. GNSS Status is still used for configuration, and to connect to real-time sources.  QuickCapture and Survey123 should be configured to use "Internal Location Service" after GNSS Status has been set as the Mock Location Provider in Android Developer Settings. ... View more

A similar update to the R2 is in progress and will be announced as soon as it becomes available. With respect to the R1: iOS is now supported through direct BT Pairing and NMEA Android is (and has been) supported through Mock Locations and Android Location Extras for metadata Windows is supported through standard BT COM port and NMEA ... View more

An updated firmware is now available for the R1.  The current beta release of Survey123 now supports the R1.  Of course, as soon as the beta release moves into production, it will be supported there as well. You can download the latest FW release HERE. ... View more

Hi Dave, there's no definitive timeline for the R2 firmware release at this time.  As soon as we're able to narrow in, I'll update accordingly. ... View more