In my opinion Justin looks good even on a cheap 7'' tablet (sorry for the quality of photos).
Among other capabilities it configures the rover for RTK++ and process static data using RTCM 3.0 messages with a powerful engine in real time. Works with static IP address.
Adding two Triumph-2 receivers with raw data only (one in the field and other to the office or two in the field) and I expect that the system can do the work.
Maximum rms in position SX, SY, SZ (ex: 0.010m) and the time in minutes (3min), during which the information is accumulated for solutions can be set.
Coordinate computation is carried out in a “reverse RTK” mode of operation. This involve some quality assurance aspects of server-based RTK processing.
I wonder if it can be an alternative (or competitor) to the classical base-rover/NTRIP RTK system.
RTK++ is a powerful function from inside Justin. Processing static data using RTCM 3 messages from the base, through "relay service" will work in the field, I think. Just need a RTK/RTK++ comparison screen at the rover. Also multi-base static data processing will be possible.
That is fantastic. As you say, multi-base processing opens up a lot of possibilities. It's like server based processing except that the server is with you.
I suppose it could be done in a way that the incoming raw data and rover raw data could be processed again and again until enough data is acquired to get a reliable fixed solution. In most cases we collect much more than we need when performing static observations to insure we will not need to return due not enough data. However, in this regard, perhaps a scheme could be in place that we keep collecting, Justin keeps processing until accuracy and quality is achieved.