I thought about getting one, but opted for a slightly used South Galaxy G1. Very similar to the Trimble R10. It processes GPS L5 which was key for me. I'm not sure the Reach RS2 does?
gnss l5, but no sbas and a few other things that are supposed to be added with firmware updates in the future.
Finally received my dual reciever..
Haven't had time to evaluate yet.
?ÿ
?ÿ
I would like to know how this works out for you as well. I have been looking at this, not so much as a daily driver, but for those little quick things, and GCPs for drone work.
I would like to know how well it connects to WDS & Trimble network.
It will not connect to AllTerra Central's (Formerly WDS) RTKNET. The way that the network was set up originally was to be a "Trimble only" network. As of right now, if you are capable of consuming CMRp, there is a chance you would be able to log on, but you would only get GPS corrections. You would not receive GLONASS, Galileo, etc. corrections.
You may be able to connect to Trimble's VRSNow or RTX Fast, but you will need to keep in mind that the corrections are broadcast in a worldwide projection and not NAD83(2011). You will have to define in your data collector a transformation to get you from (I believe) IGS 08 (2014 Epoch) back to NAD83(2011) or your coordinates will not match by about a meter with anything you have done previously using RTKNET.
So I received my RS2 yesterday and did some testing. I got only 1 unit for testing but could not do a baseline static because my other units are on project sites.?ÿ
Did a fast static observation and got the following RINEX file:
3.03 OBSERVATION DATA M: Mixed RINEX VERSION / TYPE
RTKCONV 2.4.3 b33 20190828 111643 UTC PGM / RUN BY / DATE
log: D:Downloadsraw_201906271253_base.UBX COMMENT
format: u-blox COMMENT
10hz COMMENT
MARKER NAME
MARKER NUMBER
MARKER TYPE
OBSERVER / AGENCY
REC # / TYPE / VERS
ANT # / TYPE
-769312.3636 -5456452.8445 3201623.8126 APPROX POSITION XYZ
0.0000 0.0000 0.0000 ANTENNA: DELTA H/E/N
G 4 C1C L1C D1C S1C SYS / # / OBS TYPES
2019 6 27 12 53 22.9950000 GPS TIME OF FIRST OBS
2019 6 27 13 36 4.9960000 GPS TIME OF LAST OBS
G SYS / PHASE SHIFT
0 GLONASS SLOT / FRQ #
C1C 0.000 C1P 0.000 C2C 0.000 C2P 0.000 GLONASS COD/PHS/BIS
> 2019 6 27 12 53 22.9950000 0 11
G 9 19035146.976 100030370.599 -1458.835 48.000
G 8 19251154.758 101165490.626 -719.427 47.000
.....
> 2019 6 27 12 53 23.9950000 0 11
G 9 19035424.417 100031830.118 -1460.059 48.000
G 8 19251291.847 101166211.031 -720.935 48.000
?ÿ
I have only used Sokkia & Topcon and the occational South brands and as far as I can remember time stamps are rounded off to the
nearest second. I am not sure if after you processed the data (kinematic) if the software will automatically round it off to the nearest
second in its computation. I usually process my data in kinematic mode for bathymetry survey to match each rover position with the
time stamp from the echo sounder.?ÿ?ÿ
Question : has anyone encountered RINEX files with decimal seconds part (see highlighted text) for the time component?
Given the Emlid Reach RS2 uses LoRa spread spectrum, it fits the criteria for use in NZ also: https://gazette.govt.nz/notice/id/2019-go1588 & https://www.rsm.govt.nz/licensing/frequencies-for-anyone/short-range-devices-gurl/ - A word of advice though - it pays to make sure you've bought your gear from someone authorised to sell RCM compliance labelled equipment...
We bought a pair of RS2's and in a quick and dirty test, we occupied the same benchmark with both the RS2 and our trusty old Leica GS12. Each occupation was 60 seconds, using ntrip corrections from the nearest Smartnet CORS base, and we averaged the positions over that time. Occupations were about 5 minutes apart. Both were within 20mm XY and 30mm Z, when compared to the benchmark coords, and within 1mm of each other.
