I’m a SurvPC user. When I started I thought it was important to know where the base is. But now I’ve decided it’s more important to use my ROVER to check that the base and the rover are properly configured, and/or so I know how to adjust the rover coordinates later because I let the base survey itself in to an approximate location.
I haven’t been able to connect to the rover with SurvPC and get the base coordinates. But I haven’t tried very hard. I bet it works perfectly with US$15,000 GNSS receivers that I can’t afford!
I generally either
(1) set the base coordinates (fixed base mode) using the SparkFun WiFi configuration so I know where the base “thinks” it is. I then check in to a known location with my rover to verify.
or
(2) let the base survey-in to an approximate location, and then check in with my rover to a number of known points. You can then (a) localize with SurvPC in the field so the rest of the points are spot-on or (b) just go survey with your Rover, and later back in the office you can adjust all your coordinates so your check in shots match your known locations.
As sparky said, you can connect with BT to the base after it surveys-in to see what coordinates it chose or confirm you set the fixed base coordinates properly. I’ve done it, and it works for sure. I just don’t find this terribly useful, as I work in NAD83 and the base is probably spitting out WGS84 coordinates on the NMEA when it surveys itself in. And for me it’s yet another device to charge and carry (Android for SWMaps) in addition to my iPhone (that I carry anyway and use for WiFi configuring the Facets) and my SurvPC tablet. But if you work in WGS84 and you have an android device anyway, it’s probably a good answer for you.
If you really want to know where the base is, I find it easiest to just set it, even if your coordinates are approximate (+/- a few meters). Faster and more deterministic than letting it survey in, especially if you reuse the same base location over multiple sessions or days. Sometimes consistent precision over multiple days is more important than absolute-in-the-world accuracy. Sparky made some great UI improvements here in recent beta releases to facilitate this.
Note that if you set fixed based coordinates that are too far out of whack, the rover just won’t go into float or fix. There’s no other warning I’ve noticed. I’ve learned this the hard way by accidentally entering coordinates for a point 2 miles away or forgetting the negative sign on a West longitude.
By far my preference is to do (1). Remember to fix the base using the coordinates in the same datum you’re using in SurvCE for your rover. I work in US State Plane Coordinate systems based on NAD83. So when I use the WiFi config to set the base, I need to enter NAD83 lat and lon. Not WGS84.
I use (2)(b) when I can’t do (1) for some reason.
I’ve done (2)(a) a couple times and it does work. I’m going to practice with this more.