Trimble Mobile Manager is a simple app for configuring and controlling the Trimble Catalyst software-defined positioning service, which can deliver meter- to centimeter-level positioning on your Android-powered device through a simple monthly subscription.
To run this app, you will need:
For more information on the Trimble Catalyst service, purchasing subscriptions, and where to buy a Trimble Catalyst DA1 antenna, visit https://catalyst.trimble.com.
If you are working in an area outside of Trimble's VRS Now coverage zone with a Catalyst Precision subscription level, you may want to configure and use your own GNSS correction source.
To configure and use a custom (local) GNSS correction source:
If you want to have a consistent coordinate output while using different correction sources or use coordinates in a different reference frame from your correction source frame, you can set an Output reference frame.
To configure an Output reference frame:
If the local correction source frame you are using is not listed, then you can select "Same as source (Transformation off)" as the output reference frame. This forwards any positions as received in terms of your local correction source reference frame.
Setting an output reference frame also sets the output EPSG code, which can be queried and used as position meta-data for other Catalyst enabled applications utilizing Trimble Mobile Manager. For more information on EPSG codes and their use, refer to the official website http://www.epsg.org/.
If you are unsure of which reference frame to use, use Auto selection. Trimble Mobile Manager will select a suitable frame for you based on your current location.
If the output reference frame and source reference frame are the same, then no transformation is applied.
The purpose of the Output reference frame setting is to achieve consistent coordinate output, i.e. to compensate for shifts introduced by frame or epoch shifts. The following Target reference frame options are available:
The purpose of the GNSS source reference frame setting is to identify the reference frame used by a third party NTRIP caster when Trimble Mobile Manager is configured to use custom local corrections instead of the Trimble Corrections Hub. In contrast to global correction streams like SBAS or Trimble RTX, the reference frame of a local correction stream can't always be auto-populated with 100% accuracy. The following setting provides the option for Auto selection, or for the user to select a reference frame from a list of known reference frames:
To view your subscription details tap, then tap Account & Subscriptions
Trimble Catalyst subscriptions can only be used on one device at a time. You can see which device currently holds the license in this screen.
If your subscription is checked-out on a device, and you attempt to use Trimble Catalyst on a different device, the second device will only operate in Autonomous mode and will be limited to 2-3 meter accuracy.
If your assigned subscriptions allow different operating modes, you can switch between subscription levels using the Subscription Selector:
To switch your subscription license from one device to another you need to check-in the license first (by signing out), before checking out the license file (by signing in) on another device.
To sign out of Trimble Mobile Manager, tap the Main menu, then tap .
If your Trimble Catalyst subscription is checked out on a device that is no longer accessible (e.g. because it is lost, damaged, or stolen), you can terminate the license on that device remotely by contacting Trimble Support. Send an email to firstname.lastname@example.org, or contact the Trimble Distributor from whom you purchased your Trimble Catalyst subscription.
To run Trimble Catalyst, your device needs to meet the following minimum specifications.
This app has already automatically checked your system hardware against these minimum requirements. If your device is not compatible, the Trimble Mobile Manager app, and Trimble Catalyst service will not run. Your device's compatibility can be verified in the Device section in the System menu, where you will see one of the following status messages:
If you need technical support or additional trouble-shooting, contact your local Trimble distributor. They may request that you generate a log-file to help trouble-shoot any problems you may be experiencing with Trimble Mobile Manager or the Trimble Catalyst service on your device.
Trimble Mobile Manager can capture a log file that records status messages and crash details. The log file can be used by the Trimble technical support team to help identify where any problems with Trimble Mobile Manager may be occurring. The log file is completely anonymous.
To generate and send a log file from Trimble Mobile Manager, tap the Main menu, then tap Help & Feedback, then tap Send Email.
Your Android device will invite you to tap an icon of the app you want to use to share the log data with others. For example, you may wish to send the log file to a Google Drive folder, to a DropBox account, or to email it directly. Tap the icon of your preferred email client to generate an automatic email that includes a ZIP attachment of the log file, as well as a system summary for your Android device. The email will be automatically addressed to the Catalyst Support team.
Go to the support pages on catalyst.trimble.com for further documentation and help materials. If you need further assistance, send an email to email@example.com, or contact the Trimble Distributor from whom you purchased your Trimble Catalyst subscription.
The following keys are added to location extras and are accessible by any application. For more details on use of location extras, refer to Google's Android Location API documentation.
|diffAge||float||Message age of any RTK message in seconds|
|diffStatus||int||Position solution status: 1=Autonomous, 2=DGPS, 4=Fixed, 5=Float|
|vrms||float||Vertical accuracy (RMS) in meters|
|hrms||float||Horizontal accuracy (RMS) in meters|
|receiverModel||string||Receiver model string|
|mockProvider||string||Mock location provider string|
|satellitesView||int||Number of satellites in view|
|satellitesId||int||Array containing IDs of satellites in view. The number of elements in the array is indicated by satellitesView.|
|satellitesElv||int||Array containing elevation angles of satellites in view expressed in degrees. The number of elements in the array is indicated by satellitesView. Satellite elevations are stored in the same order as their IDs in the satellitesId array.|
|satellitesAzm||int||Array containing azimuth angles of satellites in view expressed in degrees. The number of elements in the array is indicated by satellitesView. Satellite azimuth angles are stored in the same order as their IDs in the satellitesId array.|
|satellitesSnr||int||Array containing signal-to-noise ratio (SNR) values for the satellites in view. The number of elements in the array is indicated by satellitesView. SNR values are stored in the same order as the corresponding satellite IDs in the satellitesId array.|
|satellitesUse||boolean||Array of flags indicating if a particular satellite has been used in a position computation. The number of elements in the array is indicated by satellitesView. Values are stored in the same order as the corresponding satellite IDs in the satellitesId array.|