Easting Error in Stakeout with JMT

K

Ken S

New Member
Yuri, Modot lets create a VRS by picking a lat and lon and time frame. They can deliver it in many Rinex formats. Attached is a Rinex2.11 file for VRS in my area. I thought it might give you some insight into what they are doing.
 

Attachments

  • Order_4.zip
    84.8 KB · Views: 341
Yuri Noyanov

Yuri Noyanov

Active Member
JAVAD GNSS
Ken,
To get a decision I need a data. Could you collect some data for this issue - start JMobile RTK rover and activate recording raw data logging and into a jps file, and set Store Base Correction check mark in file logging settings.
Then go to RTK Survey and in settings set check mark "Debug mode".
Then survey a point with known coordinate.
Send me the job with raw data and debug info inside.
 
K

Ken S

New Member
Please let me know what settings I should use. I use Nad83 2011, Missouri West Geoidal for coordinate system. Ntrip Correction type is set to rtcm3, Mount point is VRS_RTCM31.
 
Yuri Noyanov

Yuri Noyanov

Active Member
JAVAD GNSS
Ken
Today I fixed bug with conversion WGS84-NAD83 in iOS version. I hope this helps. The update is waiting Apple approval.
 
M

Mitchell D Lane

Active Member
Easting error seems to still be problem in the android JMT with T2 on ARdot vrs. Easting is .4 different with JMT+T2 than dpos and ngs. I can use same ARdot vrs setup in LS and matches dpos and ngs.
 
K

Ken S

New Member
I've been using SurvPC lately, I haven't checked JMT since the last update, but it did work before. I'll check it tomorrow.
 
D

Dennis M

Member
Mitchell D Lane said:
Easting error seems to still be problem in the android JMT with T2 on ARdot vrs. Easting is .4 different with JMT+T2 than dpos and ngs. I can use same ARdot vrs setup in LS and matches dpos and ngs.
Click to expand...
I never did get it resolved in JMT. I ended up purchasing the Victor data collector
 
K

Ken S

New Member
I tried JMT today with the most recent firmware on a first order NGS point and didn't get the right results. I think part of the problem is that the geoid file is not being applied correctly. Elevation is off by about the ortho height. I hope they fix this. i check settings and try again.
 
Yuri Noyanov

Yuri Noyanov

Active Member
JAVAD GNSS
Mitchell D Lane said:
Easting error seems to still be problem in the android JMT with T2 on ARdot vrs. Easting is .4 different with JMT+T2 than dpos and ngs. I can use same ARdot vrs setup in LS and matches dpos and ngs.
Click to expand...
Is the easting difference in feet or meters? 0.4 feet is very small to obtain. If in meters it is huge. Is the issue permanent it changes from position to position?
 
Yuri Noyanov

Yuri Noyanov

Active Member
JAVAD GNSS
Ken S said:
I tried JMT today with the most recent firmware on a first order NGS point and didn't get the right results. I think part of the problem is that the geoid file is not being applied correctly. Elevation is off by about the ortho height. I hope they fix this. i check settings and try again.
Click to expand...
As far as I understand the easting is wrong, not height. Geoid doesn't affect plain coordinates.
 
K

Ken S

New Member
Two versions of JMT are available on google play. v.3 works with Modot VRN but not v.4. After reinstalling I’m getting proper elevations with both versions. I’m using Geoid 12b . I have to set the conversion to WGS(ITRF2008) to NAD83(2011) by default JMT tries to set HTDP - Horizontal Time-Dependent Positioning. I'll try some more.
 
K

Ken S

New Member
I see what you mean. I just entered control coordinates in a design file. When I stored coordinates with survey point they are about right and when I stake the surveyed point it is correct, but when I stake the same point from the design points it telling me to go about a half of a foot east. I made a screencast. I'll post a link when it uploads.
 
You must log in or register to reply here.
Top