Hi, I finally managed to connect my RTK Facet Mosaic L-Band to the EMLID server.
I had set up a fixed base that broadcasts the UTM XYZ coordinates: 1000, 1000, 10.
I also managed to connect my rover, but it shows XYZ-type coordinates: 3600000, 660000, 4.5, which are the actual coordinates of my current location. However, it did not achieve a fixed solution, not even float — it stayed in differential mode.
With this, I have two questions:
Can I use my base to broadcast an arbitrary local coordinate system, for example, XYZ: 100, 100, 10? Or do the coordinates need to be closer to real-world values?
Is there any configuration related to the messages sent by the base and received by the rover that I should be aware of?
Thanks! Your previous comments on another post helped me a lot!
The Base coordinates should be in whatever support system and scale is expected. Want to be within a metres or so, or whatever accuracy you expect the system to operate down too. So probably cm when you have solid numbers.
Base is going to operate in a STATIC / TIMING / TIME-TRANSFER type mode, where all the signal differences ie received vs expected are going to be assumed to be “error” or range residuals.
The uBlox Rover receivers solve for the location of the Base too, and throws an error/warning if the position vs measurements look bogus.
Base typically needs to send a position message, say 1005, GLONASS Biases 1230, and MSM4 or MSM7 packets for each of the supported constellations.
Need probably at least 8 common satellites, probably at least 5 from a single constellation.
These parameters you’re talking about should they be adjusted in the settings, or how can I know what I’m doing wrong?
I have both the base and the rover in the same area, connected to the same Wi-Fi network, with a clear view of the sky and more than 30 satellites.