Hepos/GGRS87/TM87 added in ReachView3 v. 6.3

Hi guys,

We’ve changed the transformation algorithm in one of the previous updates and made additional tests to check the freezing issue. Overall, everything looked well.

For now, we only faced short freezing during the project creation. If there’s a more serious lagging in your case, please check the background processes on your mobile device to ensure it’s not the root. If there are many opened apps, it can slow down the work with the CS.

Dear Kseniia,

thank you and your team for all your efforts!

I will test the app in the field tomorrow using my Samsung Tablet as a receiver (I had no problems with my Xiaomi Mi-8 Lite smartphone) and I will let you know about the results.

All the best

Vangelis Kroustalis

1 Like

Hi Vangelis,

I’m curious about how your test went! Have you collected points with GGRS87/HEPOS and the latest ReachView 3 version?

2 Likes

My apologies for my delayed answer, but I wanted to test the app thoroughly before writing anything more here.

Here is the thing: when I first tested the new firmware I was dissaponted. I worked with the following configuration:

  1. I used a Xiaomi Mi-8 Lite smartphone with a sim card in it as a hotspot. Through this device I connected to a CORS network via NTRIP protocol, RTK.
  2. I connected a Samsung Galaxy Tablet T295 as a receiver. This device communicated with the ReachRS 2 unit via bluetooth, and with the Miaomi device through Wi-fi.
  3. The ReachView 3 app was configured to survey in Hepos/GGRS87/TM87 with orthometric heights in Greek Geoid 2010.

After having recorded the coordinates of a couple of points in the field, the receiver started disconecting all the time. I switched the sim card and I used the Samsung T295 as a hotspot and the Xiaomi M-8 Lite as a receiver, but the situation did not improve. However, I didn’t want to draw any hasty conclusions. As it turned out later, this malfunction had nothing to do with the ReachView3 app. It was rather due to the very high temperatures of that day (I live in Athens).

Meanwhile, I have tested again three more times the app according to the above configuration, in NTRIP and Base-Rover, and it has worked flawlessly.

So, congratulations!! You have made it!

I am only missing one minor functionality: when surveying in RTK with a Base-Rover configuration the positions of the Base and the Rover do not appear on the screen. I don’t have this problem when surveying in NTRIP

Survying at the harbour of ancient Salamis, with a pair of ReachRS2 units, and with the ReachView3 app…

6 Likes

Hi Vangelis,

My apologies for my delayed answer, but I wanted to test the app thoroughly before writing anything more here.

No worries! I agree it’s always better to test everything accurately to be sure of the results. And I’m happy to know you can work with Hepos/GGRS87/TM87 fine now!

I am only missing one minor functionality: when surveying in RTK with a Base-Rover configuration the positions of the Base and the Rover do not appear on the screen.

I believe we’ll figure it out as well. If no rover and base positions are shown in the Status tab, I’d suggest checking the following:

  • The rover tracks several satellites and can calculate at least a Single solution
  • The base position in the Base mode tab is entered correctly and in the corresponding datum (HTRS07)
  • There’s a Receiving corrections status in the Corrections section on the rover

If this doesn’t help or you check the positions somewhere else, please share a screenshot with me.

Survying at the harbour of ancient Salamis, with a pair of ReachRS2 units, and with the ReachView3 app…

These photos deserve special thanks :smiley: The scenery is absolutely gorgeous!

4 Likes

Dear Kseniia,

thank you for your observations! Just a quick note about the Base-Rover issue:

I am only missing one minor functionality: when surveying in RTK with a Base-Rover configuration the positions of the Base and the Rover do not appear on the screen.

I believe we’ll figure it out as well. If no rover and base positions are shown in the Status tab, I’d suggest checking the following:

  • The rover tracks several satellites and can calculate at least a Single solution
  • The base position in the Base mode tab is entered correctly and in the corresponding datum (HTRS07)
  • There’s a Receiving corrections status in the Corrections section on the rover

When I noticed this issue the Rover was getting a fixed solution with more than 30 satellites in view. However, it proved to be a transient issue; Yesterday, I surveyed once again with a Base-Rover configuration (via Lora in RTK) and the positions of both the Base and the Rover appeared on the tablet screen.

Thank you for your interest, anyway.

Vangelis

Hi Vangelis,

That’s good! Thanks for sharing the news. It’s exciting to see how your project goes :slight_smile:

1 Like

A post was split to a new topic: App crashes when collecting points

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.