Reach never get fixed

And so, what about gallileo ? Is this the same with glonass ?

hi, i do as you told me , but things dont get better . seems to be the gps single problem , is there any better RTK antenna that you recommand ?

Could you show us a picture of your Reach and antenna?

Also, when you are using Reach, are you outside in a clear area, or are you beside trees or buildings? (you could also show us a picture of the area where you are using Reach.)

i have come back to office , i will show them to you next time , and at same time , i will try it again . thanks ~~~

hi bide , this is the environment of where we test the rech with free ntrip service.

1 Like

It is a very nice place you have there! :helicopter:

With my GNSS eyes, I see vegetation in one direction and a building in another. If the other two sides are similar, then your test area looks quite good. There are only a small amount of obstructions and they are very low on the horizon.

If you can share your log files from a test, please do. Include the raw log, the base corrections, and the solution file please.

If you do not wish to share your log files, then maybe you could analyze or present them in a similar way to this: reach-bouncing-rtk-float-to-fix-on-tractor

1 Like

hi bide, thanks for you help!! here is the log file including everything i have for your reference ~~~ (686.3 KB)

oh by the way , bide , your hyperlink can t open . wonder it is correct

Thanks. Hyperlink fixed now.

Do you have a picture of the rover?

HI , TB, here you are .

1 Like

OK, my critique of these log files is:

  • log duration is too short. only 4 minutes of usable data. 10 or 20 minutes or even longer would be better. although, in ideal conditions, 4 minutes should be enough time to acquire a fix.
  • base is only using GPS and SBAS constellations. this is fine for acquiring fix and for troubleshooting, but if you add additional constellations (GLONASS) then it will hold the fix better.

In this pic, the rover is at top, and the base is at bottom.

  • connection was lost to VRS after ~2 minutes, base coordinate changed location. ambiguity resolution must start over. this makes it take longer to achieve fix

  • the only way to get a good amount of fixed points with these super short segments of log file was to use Fix-and-hold. The following plot is the result of post-processing 3 log segments. One for each of the VRS base coordinates:

    You can see three distinct groups of fixes and those are each from a portion of the log where the VRS base coordinate had not moved.

I think we had better wait for @zhangkaibest to record some longer log files.

Hmmm! What do you think about that rover pic @TB_RTK?

1 Like

ok got it . i will test it . thanks so much !!

oh… i think i would try a better groundplate, at least with flip of the bowl turning down and not up.

my sentiments exactly. the concave surface is a multipath nightmare. if there is no straight metal for a ground plane, then the convex side should perform much better.

so you guys suggest that i should flip the bowl , turn it down , not up right ? i will do that . thanks so much ~~


direct signal from satellite = Great
signal from satellite reflected in same direction = not great
signal from satellite reflected in reverse direction = Bad


I think @bide has drawing skills :grinning:


got it thanks !!!