Mapping and GIS Solutions Community

 View Only
Back to discussions
Expand all | Collapse all

Mobile Manager: Failed to connect to correction source

  • 1.  Mobile Manager: Failed to connect to correction source

    Posted 03-07-2022 13:21
    I am a GIS Analyst for the engineering department of my city and we've recently upgraded our old Trimble units to R2, as we wanted the functionality of adding data straight to our online maps rather than shooting the point data and extracting it in the office later.

    It is important for us to have extremely precise horizontal and vertical accuracy because the engineers depend on this information for accurate Utility modeling in AutoCAD.
    We purchased 3 R2 Units, 3 iPads to be used with each subsequent R2 unit, and 3 separate RTK subscriptions so that they can be used on each device with accuracy within 6 inches.

    We have been running into two separate issues with ESRI Field Maps and the Trimble Mobile Manager App, though I suspect that the issue lies with the Mobile Manager app.

    The issue that we have been running into is that we receive an error message after having the R2 units connected to the app after a couple of minutes. We turn the antenna units on, then connect to the position source on the mobile app and immediately start receiving position accuracy and available satellites. After a few minutes of being connected, we get an error message that says: "Failed to authorize connection to correction source. Please check username and password." We have our subscription services logged in under the GNSS configuration under a Custom local configuration under the "Server account" section. We have each R2 unit and its correlated iPad labeled with numbers so that they do not get mixed up when the inspectors take them into the field, and we have verified that each iPad is logged into its own subscription number so that no two iPads are accidentally logged in under the same subscription. Yet we keep getting this error message any time we try to shoot points in the field.

    We have also been receiving an error message inside of the ESRI Field Maps app. After turning on the R2 units and connecting them in the mobile manager, we switch over to the Field Maps app and make sure that the location provider is set to the Trimble units. When we select the R2 antennas as the Location Provider, we get an error message that says: "Incompatible Location Profile: Your current location profile may be incompatible with locations from your provider." and if we attempt to add a point in the map anyway, it gives an error that says: "Failed to load attribute" and will not allow us to submit the point. 

    I'm not sure what we are doing wrong here, but this has only started happening over the past couple of weeks when I created Point Z layers to record elevation for the points. We were previously recording points on normal point layers with no Z attributes before I realized that we were missing elevations. After I hosted the Point Z layers on AGOL, we started getting the incompatible location profile error, and the Failed to authorize connection to correction source error. I haven't been able to find any support on this or anyone that has had the same issues that I have been having. I've gone through this ESRI help page multiple times and made sure that we have NMEA reporting enabled. I am at a loss for what to do at this point and would appreciate any kind of help or suggestions that I can get.

    ------------------------------
    Brittany Betzer
    ------------------------------


  • 2.  RE: Mobile Manager: Failed to connect to correction source

    Posted 03-14-2022 11:21
    After lots of troubleshooting, I have a few answers, but not all.

    Before I had posted this, I had done minimal research and mostly only had referred to the "Prepare for High-Accuracy Data Collection" page which did not yield very many results. I've done a lot more research and found a little more help on the issue, so I thought I would leave some helpful links in case anyone else has been having similar issues.

    The biggest issue that we had in Trimble mobile manager was with the error "Failed to authorize connection to correction source. Please check username and password." I thought this was the source of the problem because if our units were not connecting to the correction source, then I assumed this would be the source of the problem in Field Maps.
    This is not the case - I came to learn that users are meant to disconnect the Trimble unit in Mobile Manager before connecting the unit in Field Maps. We were getting this error because Field Maps was now connected directly to the correction source, so if we tried to connect the unit again in Mobile Manager, we would run into this error because the correction source login was already being used by Field Maps at this point. Both applications could not use our correction at the same time, so one app would have to be disconnected from the unit in order to view RTK corrections in one of the apps. The solution was to disconnect the Trimble unit and revert back to the integrated antenna in Field Maps, then connect the unit to view the RTK reporting in Mobile Manager and we had no issues after implementing this.

    I have still been having issues with having an "Incompatible Location Profile" in Field Maps, but I suspect that I just need to find the correct transformation configuration from the R2 units in Mobile Manager to a custom location profile in Field Maps. Two of our Trimble units will allow us to close the error message and still submit points through the map interface, but the accuracy is still off. Our third unit will not allow us to submit points in the map at all, so I think something needs to be configured with the licensing for the third unit.

    Here are a few links that helped me with some of the issues, and I will continue to update as I figure out what kind of transformation settings we need to use in order to be compatible with Field Maps.

    On using the correct transformation with basemaps:
    https://community.esri.com/t5/arcgis-collector-questions/z-coordinates-don-t-match-benchmarks/m-p/11741
    https://community.esri.com/t5/arcgis-collector-questions/collector-location-profile-issue/m-p/90457

    On setting up Trimble Mobile Manager with Field Maps:
    https://support.frontierprecision.com/portal/en/kb/articles/setting-up-trimble-r1-r2-in-esri-field-maps



    ------------------------------
    Brittany Betzer
    ------------------------------



  • 3.  RE: Mobile Manager: Failed to connect to correction source

    Posted 03-27-2022 13:25
    Brittany,

    It looks like you are on the right path! The video that Frontier put together is the key to addressing the incompatible profile issue within Field Maps. Nearly every accurate correction source (VRS, RTX, etc.) are broadcasting corrections in NAD 83 2011 Epoch 2010. If you match the profile to what Karissa shows you in the video, you shouldn't be getting this error anymore. That is, of course, assuming that you are using AGOL versus Portal. If you are using portal and push out feature layers/web map in your own coordinate system, it's likely not Web Mercator Auxillary Sphere so you'll need to use your system (map coordinate system) in it's place. I hope this makes sense. Regarding your third R2 that seems to be behaving different that the rest, i would make sure it's on the latest firmware or at the very least that all three R2s match firmware versions. https://forms.trimble.com/globalTRLTAB.aspx?nav=Collection-115212. Alternatively, it could be an issue with our RTK subscription on that unit so have you tried a different login to confirm? Also, there is a chance that your third R2 was not configured to be sub-foot (decimeter) so you can confirm this via the web ui (WIFI) or Trimble Installation Manager (via cabled connection to window matching running TIM).

    ------------------------------
    Zach Edwards
    ------------------------------

    Original Message