Trimble Mobile Manager

It is difficult to set up a new device and requires coordinate system codes and knowledge of your local satellites by coded name. Switching R2 and DA2 devices between users and reconnecting to a different mobile device is accomplished successfully by only the most skilled users and never on the first try. Constantly dropping connection and opening and closing Mobile Manager and Field maps should be expected. The amount of glitchy button pushing between the two apps is certainly not what developers had in mind and is an indication of its weakness in providing communication between Field Maps and your GNSS. It is a requirement for the two devices mentioned above so if you have to use these devices, it works best on a set up where the same iPad and user are constantly connected to the same receiver. When firmware and other subscriptions expire, plan out a few weeks of reconnecting to Mobile Manager and your GNSS as if you had repurchased your units anew, or purchase a unit that does not run with Mobile Manager. Our vendor works with us regularly to trouubleshoot and has the same set of challenges each time, so this is really not an issue of user error.

Constantly losing connection from R2s. Randomly signs out users. No secondary correction source. You would think the replacement for the GNSS Status app would function at least as well as the old one but no. In the old app if the iPad lost signal, no problem, it would automatically kick over to SBAS. In this one if it loses signal, the user has to go into GNSS Config and switch correction source from custom local (since we have a TPP server connecting to our Alloy base stations and performing RTK) to auto. I see no point in having a log in either. The log in plus all these other quirks and issues makes it very difficult on our field users.

You have to make an account just to use it. I already paid you thousands of dollars. My field staff don’t even want to open a second app just to use field maps let alone create another account.