Noisy site

Matt Johnson

Matt Johnson

Well-Known Member
5PLS
Bruce Dawson said:
I talked with the guy a bit and he asked what it was used for. As soon as I said GPS he nodded his head and told me that batteries get bad after about a year with them. I bought a new battery and will test it out today. Could it be that the battery was only good at full power for a couple of hours and then it began to sputter out?
Click to expand...

The chart for the number of cycles for this battery from its manual.

upload_2016-6-9_9-40-59.png


http://www.power-sonic.com/images/powersonic/sla_batteries/ps_psg_series/12volt/PS1290.pdf

If you could attach the project archive we could take a look at your coordinates.
 
Shawn Billings

Shawn Billings

Shawn Billings
5PLS
Sounds like a ITRF base reference frame vs. NAD83 reference frame issue, or perhaps a localization issue (if one was used), or somehow an autonomous base position was used. Like Matt said, too many possibilities without looking at the project. When parts of a project line up with other parts of a project but the whole doesn't agree with the whole, it sounds like a base setup issue.
 
B

Bruce Dawson

Active Member
Matt, do I "Archive Current Project" and upload to here?

Btw, I used my system on a different project today and it worked flawlessly. Points look good after download. Think the battery was my issue on the radio.
 
B

Bruce Dawson

Active Member
I think I am closing in on the problem with my shifted points. I had the same issue today on a different site a hundred miles or more away from the first one. Similar issues. This site had new points about 3 feet away from the previous data. Both sites are ones that I used DPOS to adjust. Originally, I setup on an autonomous position, then processed through DPOS to bring the bases to adjusted positions. I applied the adjustment to the data. Now when I return to the site, with the adjusted positions, and chose the adjusted coordinate for the base, I seem to be getting the original autonomous position. So my new stuff is out by whatever the adjustment was, horizontally and vertically.

What am I doing wrong?
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
Bruce Dawson said:
Positioning Issue
On a different note, and perhaps related, I got some strange results on that site using the truck battery hookup. This was a site I had been to previously, about a year ago. I had found some existing corners then, tied some topo features like fences, etc. and was back to set new property corners for a newly adjusted parcel. I setup on my base rebar from before, checked into a found corner (looked good) then began to set rebar. My first corner was like 6 feet west from where I had set a lath for it's location a year ago. Same with the next 3. The new corners were suppose to be about 3 feet west from one of those previously tied fences, but they were more like 9 feet today. When I got back to the office and downloaded, the points landed right where they were suppose to in the drawing, 3 feet west of the fence! I looked at the coordinates for my base and found that the numbers for the rebar did not match the base numbers by 6 feet. How did that happen? My process was this: I chose the rebar coordinate "20" from last years work in the Start Base screen. I stored is as a new point "Base20" and started the base. This is how I have done it since day one. How did the "Base 20" position change and why was my check shot fine?
Click to expand...

When I export 20 and Base20 they both have the same coordinate:

EXPORT-CSV-PREVIEW_20160614-11.06.52.png


This is not the case for you?
 
B

Bruce Dawson

Active Member
Hi Matt,

I am now more confused. I am looking at the points now in the LS and these are the values I am seeing (from Points on the main screen):

20,172453.826,1772959.497,922.278,FDRC
Base20,172453.906,1772966.204,924.375,FDRC

The value for 20 is the autonomous position, before DPOS. Base20 is DPOS adjusted. The other points in the project are still autonomous positions. I tried an export under Data Exchange and get the same coordinates for the two points like you do. I don't understand why the coordinates are showing the same values there, but not in Points.

I remember applying the DPOS adjustment and I thought all my survey points collected from that point would be adjusted. It does not seem to have happened.

Bruce
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
Bruce are you sure you aren't looking at the Survey Origin coordinate? I see the correct shifted coordinates in the Points list with your project:

EXPLORER-OBJECTS_20160615-11.26.42.png


POINT-INFO_20160615-11.26.53.png
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
I looked into this more. There seems to be some bug that is causing the Rel RTK coordinate to be displayed in the Processed Point Info screen and when the point template is set to "Processed":

EXPLORER-OBJECTS_20160615-16.25.55.png


PROCESSED-POINT-INFO-SCREEN_20160615-16.24.37.png
 
B

Bruce Dawson

Active Member
Matt, that second screen shot is what I am seeing. Not trying to sound dumb, but I did a PrtScn from the top button, heard the shutter noise, but can't figure out how to send that to you. I wanted to show you just what you have shown me.
 
Michael Stazhkov

Michael Stazhkov

Developer
JAVAD GNSS
"1538 Marion Holcomb-160609" is an interesting project.
First part of the project was done on september-october of 2015 by an old J-Field version (I suppose it was 1.10.3.22043).
Second part of the project was done recently by one of the latest release version.

Point "20" from the first part was the base point and it was DPOSed by the old J-Field version. The point "20" has no flags that it is the Base point (I can't say now how it happens in the old version). Current coordinates of the point was shifted relative to original coordinates by DPOS but no history was recorded (it is OK for the old version).
With the current J-Field approach the point "20" looks wrong. The old point has no concept about the currently selected coordinate. It has only the current shifted coordinate and the original coordinate. The point information panel trying to show the selected coordinate (not the current coordinate) and from the "20" it wrongly reads that the original coordinate is selected now. But in many other algorithms the current coordinate is used (for ex. when the point was selected from the list for the "Base 20" point coordinate).

So, for the "Base20" point the DPOSed coordinate of the point "20" was selected (I suppose it should be OK).
On the point info panel you see the original coordinate of the "20" point.
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
Michael Stazhkov said:
"1538 Marion Holcomb-160609" is an interesting project.
First part of the project was done on september-october of 2015 by an old J-Field version (I suppose it was 1.10.3.22043).
Second part of the project was done recently by one of the latest release version.

Point "20" from the first part was the base point and it was DPOSed by the old J-Field version. The point "20" has no flags that it is the Base point (I can't say now how it happens in the old version). Current coordinates of the point was shifted relative to original coordinates by DPOS but no history was recorded (it is OK for the old version).
With the current J-Field approach the point "20" looks wrong. The old point has no concept about the currently selected coordinate. It has only the current shifted coordinate and the original coordinate. The point information panel trying to show the selected coordinate (not the current coordinate) and from the "20" it wrongly reads that the original coordinate is selected now. But in many other algorithms the current coordinate is used (for ex. when the point was selected from the list for the "Base 20" point coordinate).

So, for the "Base20" point the DPOSed coordinate of the point "20" was selected (I suppose it should be OK).
On the point info panel you see the original coordinate of the "20" point.
Click to expand...

I suspected this problem was caused by using an old project with the new versions of J-Field and DPOS. Is there an easy fix for this? It seems that if an old point does not know which coordinate should be selected, it should default to the shifted coordinate.
 
B

Bruce Dawson

Active Member
This was a strange thing and I was fooled by it. I don't understand why my first check shot was good, then subsequent staking of corners out by the 6 foot shift. Similar issues on the second job, although that one had a 3 foot miss even on the check shot. Both were indeed year old DPOS adjusted jobs. My solution that has worked so far has been to start a new project and just upload all the adjusted points as design points. All seems to work that way, but I lose the survey data for the points.

Thanks again guys!

Bruce
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
Bruce Dawson said:
This was a strange thing and I was fooled by it. I don't understand why my first check shot was good, then subsequent staking of corners out by the 6 foot shift. Similar issues on the second job, although that one had a 3 foot miss even on the check shot. Both were indeed year old DPOS adjusted jobs. My solution that has worked so far has been to start a new project and just upload all the adjusted points as design points. All seems to work that way, but I lose the survey data for the points.

Thanks again guys!

Bruce
Click to expand...

I would recommend you continue to use this work around with old DPOS projects for now.
 
Jim Frame

Jim Frame

Well-Known Member
Those of us who haven't yet delved deeply into some of these features find the prospect of doing so more than a little daunting. I expect it'll all make sense to me when I need to focus and learn how to use things like DPOS, but at the moment the idea of keeping track of all the things that might go wrong is just a little terrifying.
 
You must log in or register to reply here.
Top