Mapping and GIS Solutions Community

I am using the following:

1. Google Pixel 6 Pro
2. Catalyst 30 subscription
3. Trimble Mobile manager version 3.1.2.1407
4. Propeller App 1.3.3

When I look at the accuracy in Trimble Mobile manager it shows ~1ft.  See attached picture.  However, when using the propeller app my location appears to only be within ~3ft.  In the attached picture the actual location is at the lamppost but shows the blue dot about 3 ft off the lampost.

Are there any additional settings that need to be considered or other suggestion on why the difference in accuracy?

Hi Trent

Two things to check here

1. Have you set TMM to be the mock location provider? Take a look at the Location Sharing with other apps section of the help
2. Is this a datum Issue? Make sure your GNSS Output datum matches the reference frame your Propeller app is using 
   • For example - If it's using WGS84 then you can select that output option from the list of TMM reference datums so they match.  
   • If they don't match then you will have a positional error based on the difference between these two systems.
   • For more Information on this topic and practical advice take a look at the BLOG: Common Problems With Coordinate System Configurations

It might be a good idea to reach out to your local Trimble reseller at this point. They will have specialist local knowledge to help you determine and resolve this issue

I am using the following:

1. Google Pixel 6 Pro
2. Catalyst 30 subscription
3. Trimble Mobile manager version 3.1.2.1407
4. Propeller App 1.3.3

When I look at the accuracy in Trimble Mobile manager it shows ~1ft.  See attached picture.  However, when using the propeller app my location appears to only be within ~3ft.  In the attached picture the actual location is at the lamppost but shows the blue dot about 3 ft off the lampost.

Are there any additional settings that need to be considered or other suggestion on why the difference in accuracy?

@Tom thank you very much for the suggestions.  

1. Yes, TMM  is set to be the mock location provider
2. The detection mode was set to auto and the Geoid was set to EGM96 (Global)

Attached is the processing report from propeller.  Based on this the Frame has been updated to NAD83(2011) (EPOCH:2010) and the Geoid to Geoid12B (Conus) as shown in the attached image.

Does it matter if NAD83(2011) (EPOCH:2010) is used versus NAD83(2011) (EPOCH:2017.5)

I will be testing this out later this morning on site.

Hi Trent

Two things to check here

1. Have you set TMM to be the mock location provider? Take a look at the Location Sharing with other apps section of the help
2. Is this a datum Issue? Make sure your GNSS Output datum matches the reference frame your Propeller app is using 
   • For example - If it's using WGS84 then you can select that output option from the list of TMM reference datums so they match.  
   • If they don't match then you will have a positional error based on the difference between these two systems.
   • For more Information on this topic and practical advice take a look at the BLOG: Common Problems With Coordinate System Configurations

It might be a good idea to reach out to your local Trimble reseller at this point. They will have specialist local knowledge to help you determine and resolve this issue

I am using the following:

1. Google Pixel 6 Pro
2. Catalyst 30 subscription
3. Trimble Mobile manager version 3.1.2.1407
4. Propeller App 1.3.3

When I look at the accuracy in Trimble Mobile manager it shows ~1ft.  See attached picture.  However, when using the propeller app my location appears to only be within ~3ft.  In the attached picture the actual location is at the lamppost but shows the blue dot about 3 ft off the lampost.

Are there any additional settings that need to be considered or other suggestion on why the difference in accuracy?

When I went back and tested with the new Frame and Geoid settings it was even further off. 

I decided to delete and reinstall both Mobile manager and the Propeller mobile.   Once this was done and settings were completed again it was working perfectly!

Thank you very much for the assistance!

@Tom thank you very much for the suggestions.  

1. Yes, TMM  is set to be the mock location provider
2. The detection mode was set to auto and the Geoid was set to EGM96 (Global)

Attached is the processing report from propeller.  Based on this the Frame has been updated to NAD83(2011) (EPOCH:2010) and the Geoid to Geoid12B (Conus) as shown in the attached image.

Does it matter if NAD83(2011) (EPOCH:2010) is used versus NAD83(2011) (EPOCH:2017.5)

I will be testing this out later this morning on site.

Hi Trent

Two things to check here

1. Have you set TMM to be the mock location provider? Take a look at the Location Sharing with other apps section of the help
2. Is this a datum Issue? Make sure your GNSS Output datum matches the reference frame your Propeller app is using 
   • For example - If it's using WGS84 then you can select that output option from the list of TMM reference datums so they match.  
   • If they don't match then you will have a positional error based on the difference between these two systems.
   • For more Information on this topic and practical advice take a look at the BLOG: Common Problems With Coordinate System Configurations

It might be a good idea to reach out to your local Trimble reseller at this point. They will have specialist local knowledge to help you determine and resolve this issue

I am using the following:

1. Google Pixel 6 Pro
2. Catalyst 30 subscription
3. Trimble Mobile manager version 3.1.2.1407
4. Propeller App 1.3.3

When I look at the accuracy in Trimble Mobile manager it shows ~1ft.  See attached picture.  However, when using the propeller app my location appears to only be within ~3ft.  In the attached picture the actual location is at the lamppost but shows the blue dot about 3 ft off the lampost.

Are there any additional settings that need to be considered or other suggestion on why the difference in accuracy?