No FIX with the manually set coordinates for the base

[mark1st.john]

Hi Ben, One cause might be that there is an error on entering your coordinates and height values for your known point on your Base receiver and that they are too far from your current known location. I have had that happen to me with an error in the height entry. You need to enter ellipsoid height when using a manual base coordinate and you can obtain that from your average single coordinate if you don’t have it for your know position.
Your average single coordinates that you were successful in obtaining for your Base, should match your know point within a few meters. That is one way to check the location entered.

Edit: This also depends on what datum is used in collecting the average single coordinate and what datum you use for the known point. OPUS outputs in: REF FRAME: NAD_83(2011)(EPOCH:2010.0000) and ITRF2014 (EPOCH:2023.5174) and ORTHO HGT in NAVD88 (GEOID 18) so your Base would have to be set up using those parameters if using the OPUS known point or transformed to whatever datum you are using at your location.

Here is another discussion on this topic on the Forum.

RS2 rover won’t fix with manual base coordinate

This is my first time entering a manual base coordinate. I usually do average single for the base location but want absolute accuracy now. My rover unit keeps switching back and forth from single to float, the corrections input coming from LoRa switches back and forth from receiving corrections and waiting for corrections. The baseline is reading as in the 200s of meters even though my rover is roughly 5 meters away.

Regards, Mark