Mobile phone: Android Galaxy S26+ (SM-S947W)
External GNSS: Trimble DA2, with Trimble Catalyst GNSS positioning service (60cm subscription)
Hi everyone,
I have been trying to use the Trimble DA2 catalyst paired with QField, but QField does not seem to use the mock location provided by the catalyst. It shows a X/Y precision from 12 to 20 meters, far from the 60cm precision of the Trimble DA2. I am using a QGIS project packaged for QField using the QFieldSync extension.
Now, what makes me think it’s a QField issue, is that when using Trimble’s “Mobile Manager” app and when connected to the catalyst, it shows the correct precision (ranging from 0,6 to ~1,4m depending on areas). However, when in QField and using the “Internal storage” positioning device (which is supposed to be the Trimble DA2’s location and not the Android phone itself because I enabled the mock location in the “Developer Options”), it suddenly jumps to a very low precision such as 12-20m. When using the real phone’s position in QField (by disconnecting the catalyst), the precision reaches 3-5m again (average precision for a phone).
I tried reinstalling QField (and Mobile Manager), without any success. I don’t know what could be the problem, because all of this worked the first time I tried it on a test project in QField.
Have any of you had this issue before? Is there a solution? I’d be happy to provide more details if need be.
Best regards,
Benjamin
What have you set as output CRS in the Trimble Mobile Manager? If I am correct QField is assuming the coordinates are in WGS84, which is the standard for android location services.
Maybe QField is misinterpreting the received coordinates?
I am using WGS84 as output in Mobile Manager. Thinking about it, my QGIS project is in NAD83 though, should it have such a big difference as to the displayed precision?
I don’t know about that. You could try using different layer CRS and project CRS settings, to see if you find anything different.
Is the output in Mobile Manager set to QGS84 manually, or is it set to Same as source or auto? Maybe changing this might help?
Also I have seen topics on incorrect precisions shown on iPhones, where the actual recorded coordinates were correct, but QField was showing incorrect accuracies. Can you check if the actual recorded coordinates are correct?
Hi, sorry for the late answer. The output was indeed manually set to WGS84, but when choosing “Auto” I think it uses WGS84 so shouldn’t change anything.
My colleague uses an iPhone and we noticed the same problem, the coordinates seem correct but not the accuracy.
I wanted to try again today (on Android). I’ve tried to reset the bluetooth pairing, and even though I’m still connected and the catalyst shows an accuracy of 80cm (in Trimble’s Mobile Manager app), QField now doesn’t display any position. It looks like the app can’t access my position when using the catalyst. I’ve tried with SW Maps and I have the same problem, so it probably comes from Trimble’s Mobile Manager app. I will call our local reseller to see if there could be a solution to all this.
Thank you for taking the time to answer!