Hi Jim, I don't see the project on the support server. It could be over-sized project for our service. In this case please upload the project archive to our storage:
http://storage.javad.com/
Login: customer
Password: obpiWmoLM6feqDqaI7iG
Give a link to the uploaded archive in, for example, the...
We hide the parameter in the user mode. By default the parameter has "0" value (unlimited distance). It could be that in your profile it has a different value. You can set an engine parameters to the default values by pushing the "To Default" button on the bottom row of the screen.
Yes.
We will add the possibility.
The map screen has 5 customizable buttons on the right side. We will add the "Center on Current Position" to the list of custom commands.
We will think about it. Redesign of Collect / Stake and other map screens is in our plans for future releases.
FTP of the Washington (US) network doesn't work (we will change data downloading to other protocol).
The customer can manually choose the CORS (US) network.
Hi Nate. It seems you are right, original RTK coordinates were changed somehow. DPOS / RTPK coordinates are correct. I have compared original RTK coordinates, recorded into the JPS file and, as Justin team said, it is almost the same compare to post-processed.
At the moment we don't reproduce...
Nate, yes I see the issue. I mean I want to teach J-Field to read RTK position from the recorded JPS file like Justin does (Justin team said the RTK position from files should be equal to the RTPK position) and then it may help me understand the issue better. Anyway this functionality will be...
Justin team said that Justin doesn't see any discrepancy between RTK position recorded in the JPS file and the post-processed RTPK position. I am trying to reproduce that result in the J-Field and then compare the result and what is recorded in database. It can help to understand the issue.