RTK SURVEYOR- NOTHING BUT ISSUES

I have spent countless hours trying to get our system to work… Intermittent data collection, or even connection between the rtk surveyor and ucenter. We have tried four different antennas, it has worked on two of the four for brief moments, then cannot get it back up and running. The device says it is connected, not receiving. We have gone through numerous sets of instructions from different forums. Firmware is correct & up to date. Can anyone help? Please.

Sorry for all the hassle!

Let’s start with the basics:

  • You’ll need an L1/L2 antenna. If you got a Surveyor kit, the antenna that came with the kit (TOP106) should be all you need. Can you let us know what the other four antennas that you’re using?

  • Once you’ve got the antenna hooked up, and you go outside, do you see the PPS LED illuminate once per second? This will tell us whether the connection between your antenna and the Surveyor is good.

  • Next, can you connect the Surveyor to [SW Maps](https://docs.sparkfun.com/SparkFun_RTK_ … e/#sw-maps) app? This will allow us to see the HPA or horizontal positional accuracy that you can get. With no corrections, you should be ~0.3m

  • Once you get all of the above covered, then we can talk about corrections, NTRIP, and all the rest. At no time should you need or use u-center. It’s fine, you can have a look, but you really shouldn’t use it for configuration.

Thank you very much for your reply and info. With this, we seem to be gettin somewhere!

*We have two L1/L2 antennas. we have also tried two different low quality GNSS receivers that came with verizon cell boosters- make & model unknown.

*Once connected and outside, PPS does in fact illuminate per second.

*Connecting to SW Maps

  • in ROVER mode it will connect. After a moment, LAT LONG info will appear on the bottom of the device connection window. We can then go into the GNSS STATUS screen where the info will be displayed.

  • in BASE mode we can connect. No LAT LONG info appears, no info appears in the STATUS screen, and it auto disconnects after a few seconds. PPS does still flash per second though.

That’s where we’re at, thank you again for your help. Eager to see next steps.

Thank you very much for your reply and info. With this, we seem to be gettin somewhere!

*We have two L1/L2 antennas. we have also tried two different low quality GNSS receivers that came with verizon cell boosters- make & model unknown.

*Once connected and outside, PPS does in fact illuminate per second.

*Connecting to SW Maps

  • in ROVER mode it will connect. After a moment, LAT LONG info will appear on the bottom of the device connection window. We can then go into the GNSS STATUS screen where the info will be displayed.

  • in BASE mode we can connect. No LAT LONG info appears, no info appears in the STATUS screen, and it auto disconnects after a few seconds. PPS does still flash per second though.

That’s where we’re at, thank you again for your help. Eager to see next steps.

sparky:
Sorry for all the hassle!

Let’s start with the basics:

  • You’ll need an L1/L2 antenna. If you got a Surveyor kit, the antenna that came with the kit (TOP106) should be all you need. Can you let us know what the other four antennas that you’re using?

  • Once you’ve got the antenna hooked up, and you go outside, do you see the PPS LED illuminate once per second? This will tell us whether the connection between your antenna and the Surveyor is good.

  • Next, can you connect the Surveyor to [SW Maps](https://docs.sparkfun.com/SparkFun_RTK_ … e/#sw-maps) app? This will allow us to see the HPA or horizontal positional accuracy that you can get. With no corrections, you should be ~0.3m

  • Once you get all of the above covered, then we can talk about corrections, NTRIP, and all the rest. At no time should you need or use u-center. It’s fine, you can have a look, but you really shouldn’t use it for configuration.

[attachment=0]Screenshot_20230626-120825_SW_Maps.JPG[/attachment][attachment=1]Screenshot_20230626-120922_SW_Maps.JPG[/attachment][attachment=2]Screenshot_20230626-114905_SW_Maps.JPG[/attachment]

sparky:
Sorry for all the hassle!

Let’s start with the basics:

  • You’ll need an L1/L2 antenna. If you got a Surveyor kit, the antenna that came with the kit (TOP106) should be all you need. Can you let us know what the other four antennas that you’re using?

  • Once you’ve got the antenna hooked up, and you go outside, do you see the PPS LED illuminate once per second? This will tell us whether the connection between your antenna and the Surveyor is good.

  • Next, can you connect the Surveyor to [SW Maps](https://docs.sparkfun.com/SparkFun_RTK_ … e/#sw-maps) app? This will allow us to see the HPA or horizontal positional accuracy that you can get. With no corrections, you should be ~0.3m

  • Once you get all of the above covered, then we can talk about corrections, NTRIP, and all the rest. At no time should you need or use u-center. It’s fine, you can have a look, but you really shouldn’t use it for configuration.

Doesn’t look like the screen shots came through. Please repost if possible.

We have two L1/L2 antennas. we have also tried two different low quality GNSS receivers that came with verizon cell boosters- make & model unknown.

Do you have the model or link of the L1/l2 antennas? Please avoid any low grade GNSS antennas as they are very likely just L1 and won’t work.

in ROVER mode it will connect. After a moment, LAT LONG info will appear on the bottom of the device connection window. We can then go into the GNSS STATUS screen where the info will be displayed.

Great! Now you can use SW Maps to take and record points as needed.

in BASE mode we can connect. No LAT LONG info appears, no info appears in the STATUS screen, and it auto disconnects after a few seconds. PPS does still flash per second though.

This is expected. By default, the Surveyor will do a Survey-In (https://docs.sparkfun.com/SparkFun_RTK_ … gure_base/). During the 60 seconds of survey-in, the device won’t transmit anything. Once complete, the device’s location will be locked to coordinates determined during the survey-in process.

Depending on your application, the Surveyor in Rover mode will provide positional fixes that are ~0.3m of accuracy. If you need higher precision then that they you’ll need to provide the Surveyor with a correction source (https://docs.sparkfun.com/SparkFun_RTK_ … n_sources/). Once RTCM is fed into the Surveyor, you’ll have precision of ~20mm.

Yes sorry I forgot that aspect, models are the TOP106.

Thanks! Those will work just fine.

Great. Next, how what are our next steps in working towards corrections, NTRIP, and all the rest?

Thank you!

Currently, we have attempted to collect static data via the SWapp “log to file” where we are producing .ubx files (100+ MB for approx. 24 hours). Then using the RTKLIB-RTKCONV to obtain RINEX OBS, which seem to momentarily produce files for a split second and then they disappear, which I assume because they are blank. From there I had planned to upload to OPUS to post process our Fixed location and proceed to plug the results into the RTK2GO, but can not seem to get to that stage.

Additional Questions that arise:

-Is the SW app the preferred instruct the SF-RKTsurveyor way to log static data to Sd card?

-Has the SF-RKTsurveyor already been preprogramed to log in Rawx format?

-Can it log directly to RTCM format to bypass the need for the RTKCONV conversion?

Screenshot 2023-07-04 122139.png

what are our next steps in working towards corrections, NTRIP, and all the rest?

Please see Correction Sources in the docs: https://docs.sparkfun.com/SparkFun_RTK_ … n_sources/

It sounds like you are attempting to setup a permanent base. Docs are here: https://docs.sparkfun.com/SparkFun_RTK_ … nent_base/

Is the SW app the preferred instruct the SF-RKTsurveyor way to log static data to Sd card?

We recommend users log to an SD card in the unit so that they do not have to be connected over bluetooth for longs periods of time (hours).

Has the SF-RKTsurveyor already been preprogramed to log in Rawx format?

No, five NMEA messages (GGA, GSA, GST, GSV, and RMC) are default on. RAWX and SFRBX can be enabled through the messages menu: https://docs.sparkfun.com/SparkFun_RTK_ … _messages/

Can it log directly to RTCM format to bypass the need for the RTKCONV conversion?

You can see a list of supported messages that can be logged here: https://docs.sparkfun.com/SparkFun_RTK_ … l-messages Many RTCM messages can be logged directly. I’m not entirely sure that’s what you really need, but it’s possible.

We can not convert our UBX file. Currently, we have attempted to collect static data via the SWapp “log to file” where we are producing .ubx files (100+ MB for approx. 24 hours). Then using the RTKLIB-RTKCONV to obtain RINEX OBS, which seem to momentarily produce files for a split second and then they disappear, which I assume because they are blank.

Ok, so we have been slowly making progress. For some reason our raw, messages were turned off which I believe we were unable to convert ubx to osb. So now I am collecting 24+ hour data file to post process through OPUS. While that is running, I have been trying to get the NTRIP side of it working with my Topcon FC5000 and Hyper V Rover Running Magnet Field Software. I was able to get my mount point listed on SNIP, and I was able to login with my FC5000 to start getting corrections.

My current issue is that I still only get an autonomous signal. My corrections are only being received every 7 seconds consistently. I have my RTKsurveyor on a WiFi on a 1GB fiber service, and 2 miles away I have my FC5000/HyperV using WiFi on a 1 GB fiber service. Using just GPS and GLONAS, I receive 13 satellites and my HRMS sits around 2.0. Which 13 satellites is typically enough to produce a fixed signal with my normal Base/Rover setup on the two constellations. Attempting to use all constellations, I get more satellites (around 18) but my HRMS raises to 2.7.

Any suggestions on how to resolve this issue?

7 seconds between RTCM updates is odd. Nearly every base I’ve ever used is 1Hz.

Check that your caster is indeed transmitting. For example, go to http://rtk2go.com:2101/ and checkout mountpoint ‘bldr_SparkFun1’, you’ll see it’s setup for 1Hz RTCM 3.2.

http://rtk2go.com:2101/SNIP::MOUNTPT?ba … _SparkFun1 will show you uptimes. Check that your base is similarly reporting at 1Hz.

On the rover side, I won’t be much help. I’m not familiar with the FC5000 but the obvious questions apply: is it connected to the right mount point? Is it getting RTCM at 1 Hz?

RTCM is ~530 bytes per second - you could basically use carrier pigeons at that speed. A fiber connection speed doesn’t matter but getting regular intervals (once per second) to your rover is paramount.

I have been able to get the corrections to populate consistently (0-2 seconds). I am viewing 12 satellites (GPS & GLOSNAS) but I am still not able to get anything other than an autonomous position. Looking over and comparing our mount point (MLS_NTRiP) data, it appears to be similar data as your example. I am logged into the correct mount point with the data collector.

I connected to your mountpoint MLS_NTRiP. I don’t see anything obviously wrong with it. Data is coming in once per second. I’ve got an RTK express pulling in your data just fine (see image below). However, I can’t get a RTK fix or float, likely because you are on the other side of the globe and the ZED just can’t do anything with RTCM that bad. Can you successfully mount to other stations in HI from your rover?

Hi again, I am continuing to have issues getting a fixed signal. I have tried and tried again. Currently I have been able to login and connect to my RTK network. Once connected I have 17 out of 17 satellites now (GPS & GLOSNAS), I am getting corrections now every 2-10 seconds but am still unable to get a fixed or even a float position. Currently I have all messages turned on at this time. With all the issues that I’ve been having, I have since purchased another separate system that I have been able to get up and working out of the box. Using the same location mount point and coax. I am at a loss currently as to why this system I have purchased has not been a strait forward solution. If there is not another avail remedy for this unit please let me know. If not, I would like to ask if I can exchange this unit for one of your other units such as the RTK Reference Station GPS-22429? please let me know what can be done.

Thank You

I appreciate your patience! It sounds like you have an alternate solution. The RTK Reference Station is built upon much of the same technology so I suspect you may run into the same problems. You are welcome to return the unit for a refund.

My understanding is that you are working to setup your SparkFun RTK Surveyor as your base, and use your TopCon HiPer V, with the FC5000 data collector, as your rover.

The SparkFun RTK units use RTCM as the communication format between the base and rover. The HiPer V units, based on reading the manual, can use either CMR/CMR+ or RTCM. Does the HiPer V rover need to be configured to expect RTCM and not CMR?

Is the base RTK Surveyor base configured with good base coordinates? A couple times I’ve missed the minus sign on the longitude (I work in the US) when setting the base coordinates so the base coordinates were in the wrong hemisphere. A couple other times I fat-fingered the base coordinates and they were a couple hundred miles off. Under both conditions my rover would not get an RTK Fixed solution.

Correct toeknee, that was my intentions. My base coordinates are currently in the “survey-in” mode. But I made sure to double and triple check as I could see how that could be an easy error to make. And my rover is set up for RTCM corrections which is how my typical corrections are also received. It is unfortunate that I did not have success as I had hoped to expand the network with another 5-10 units. But at this time I think I will have to return the unit.