Why is rtpk o.35' east, of rtk. Consistently, all day? Tilt is off.

Nate The Surveyor

Well-Known Member
IMG_20201215_140734.jpg
 

Adam

Well-Known Member
5PLS
Good catch Nate. I noticed it being off a little today too but it wasn't consistent and wasn't just in the Easting. I had some that were normal too. I noticed about .35 to .4' of difference between repeat shots too. I will send my project to support. Probably wouldn't hurt to send yours too. @Alexey Razumovsky
 
Last edited:

Nate The Surveyor

Well-Known Member
I don't have a good way to send to support team a large file. My internet connection is not that great. Download is FASTER than UPLOAD.
Can anybody suggest a web hosting service, or mechanism to send large files for review?
Thank you,
Nate
 

Michael Stazhkov

Developer
JAVAD GNSS
I don't have a good way to send to support team a large file. My internet connection is not that great. Download is FASTER than UPLOAD.
Can anybody suggest a web hosting service, or mechanism to send large files for review?
Thank you,
Nate
Nate, the best way for us is to send the project with the file to support from LS (Projects screen -> "Send Project to Support" button). And we need the project as there is difference after DPOS.
 

Nate The Surveyor

Well-Known Member
OK, Kirbytown is sent. It has a base file BASE6, and it's associated points, that gave a consistent Easting error of 0.35'.

And, I'm sending now REED222. It's a big file. It has a real problem, (I think is a gump up in the database) I tried to use BASE29, to SHIFT the base. It failed. (It would lock up the system, and a hard start was needed to keep working. I eventually restarted the base on BASE31, after backing it the base coord, from BASE1. I have tried ALL I can think of, to make it work.
Thank you,
My LS is 00435
 

Nate The Surveyor

Well-Known Member
Another problem with KirbyTown, is No. 1452, and 1483 are the SAME POINT. Inverse between them, and they are 0.26 apart. 1452 was shot with another profile, (It's called Endless) and I think it should be deleted, and re-made. When you look at 1452, it has some oddities. I think it's the wrong one.
Thank you,
Nate
 

Michael Stazhkov

Developer
JAVAD GNSS
And, I'm sending now REED222. It's a big file. It has a real problem, (I think is a gump up in the database) I tried to use BASE29, to SHIFT the base. It failed. (It would lock up the system, and a hard start was needed to keep working.
Nate, I am trying to reproduce the issue with "lock up the system". Could you tell exactly how you were trying to shift the BASE29 point? It could be 1-Local and to which point or coordinate?
 

Nate The Surveyor

Well-Known Member
I'm in the field. This is from memory.
Base 29 base30 base31 are my 3 base points. Base29 was supposed to shift about 3 feet. I can't remember more than that. It refused to shift, instead locking up. I backed in a coord, using Cogo, then used that coord to start base31. I did my work off base31.
 

Michael Stazhkov

Developer
JAVAD GNSS
OK, Kirbytown is sent. It has a base file BASE6, and it's associated points, that gave a consistent Easting error of 0.35'.
As you said the consistent error of 0.35' disappears after DPOS and I don't see now the big difference between RTK and RTPK in you project. What I can see now the Base6 DPOS session doesn't include any rover points. We think that the problem can be related to using coordinate system transformation without HTDP for some of our internal calculations. For points "Base6" and "1459" it gives difference in 10 cm (close to 0.35') between recorded base station coordinates. While using another CS transformation with HTDP gives 0.1 mm. We are trying to understand the problem deeper.
 
Top