Problem in J-Field Software

[Nate The Surveyor]

I loaded an old job, maybe 5 yrs old. It was a project 1700 feet long, and about 200' Wide. River front property. The first one (5yrs ago) was a Retracement of a reputable surveyor.
Well, I set steel T posts around the whole perimeter. It has a localize.

I went to my old base, (In a clear cut, nice wide open place), and the Pine trees had all grown up. NO GOOD BASE.

I drove away, and found a field. Set a Cotton Spindle. Made a new base. Made autonomous base coord. Went to old base, and shot it. I used the Collect>Point>Shift (Button) This gave me This:

So, Point 360 was my PREVIOUS Point Number. 400 is my new shot on the old base, which generates this shift.
But, it is NOT applying this shift
Or, it is MIS applying this shift.
The problem seems to be in DPOS, and or, when it is shut down, and re started.
It seems to really have things fouled up.
In the field, it all looked right. And, in the field, things fit reasonably well.
This morning, I DPOS it, and things really went off the charts.
Is there any person left who can look at things?
I've sent this to support.
Murfreesboro nw walls is the file name.
Thanks,
Nate

 

[Ron Cloninger]

Nate, check your Geoid on the imported old job, mine always seem to be wrong. This may not have anything to do with your problem, this something I seem to change all of the time.
Ron

 

[David M. Simolo]

Nate, I know this seems like a pretty basic response but your situation is something I do all of the time. I work in State Plane. After I DPOS a file upon return to the office I apply the combined factor to put the project on the ground. If I come back to the job at a later date and set another autonomous base, I do a shift in the field to get the work done. But when I DPOS the new work at night DPOS will put everything back on state plane and I have to manually apply the combined factor and hold the common point I have reshot from the original work in order to meld all of the field work properly.

 

[Nate The Surveyor]

I use localize all the time. 99% of the time.
Localize is in it. It should not affect things.
From NOW on, m-local will never get DPOS.
If I use m-local, it will generate a coord for the base, and base will get restarted.
I have jobs with 80 base stations. And a localize.
N

 

[David M. Simolo]

Nate, I should have mentioned that I leave my autonomous solution for the day in the field alone and temporarily use the shift function to move all of the rest of my file to my current autonomous solution.

 

[ken larson]

Make sure your base is on the new point number and not still on autonomous if you restarted the base.

I was also told at least an hour of data on your base for it to have the best chance of dpos returning a valid location.

 

[Adam Plumley]

I loaded an old job, maybe 5 yrs old. It was a project 1700 feet long, and about 200' Wide. River front property. The first one (5yrs ago) was a Retracement of a reputable surveyor.
Well, I set steel T posts around the whole perimeter. It has a localize.

I went to my old base, (In a clear cut, nice wide open place), and the Pine trees had all grown up. NO GOOD BASE.

I drove away, and found a field. Set a Cotton Spindle. Made a new base. Made autonomous base coord. Went to old base, and shot it. I used the Collect>Point>Shift (Button) This gave me This:

View attachment 13122


So, Point 360 was my PREVIOUS Point Number. 400 is my new shot on the old base, which generates this shift.
But, it is NOT applying this shift
Or, it is MIS applying this shift.
The problem seems to be in DPOS, and or, when it is shut down, and re started.
It seems to really have things fouled up.
In the field, it all looked right. And, in the field, things fit reasonably well.
This morning, I DPOS it, and things really went off the charts.
Is there any person left who can look at things?
I've sent this to support.
Murfreesboro nw walls is the file name.
Thanks,
Nate

Nate, please contact one of the Support Team Members listed on the LS under support, live technical support for assistance with your project. You will need to setup a rams session for them to look into this.

 

[Nate The Surveyor]

Yesterday, I decided to be BOLD and updated to the latest, 4.0.0.1219.
I went to the field. I had it lockup on me, and I had it STORE a shot in DESIGN, (Pt. No 1288) when it was supposed to be SURVEY, This was in STAKE to LINE by 2 pnts. ALSO, it lost a couple of shots, that were done this way. 2 to be exact.

And, the above store shot (1288) has screen shots in DESIGN. The ones it totally failed to store, I have not yet found the screen shots for.

OK, I backed up 29 jobs, and deleted all jobs, and restored factory image, and reloaded my immediate jobs.
I also went BACK to version 4.0.0.1216, I am going to test things, to see what goes on.
I hope Javad company gets a group of programmers, that can fix some of this.
Nate

 

[Greg Flowe]

Yesterday, I decided to be BOLD and updated to the latest, 4.0.0.1219.
I went to the field. I had it lockup on me, and I had it STORE a shot in DESIGN, (Pt. No 1288) when it was supposed to be SURVEY, This was in STAKE to LINE by 2 pnts. ALSO, it lost a couple of shots, that were done this way. 2 to be exact.

And, the above store shot (1288) has screen shots in DESIGN. The ones it totally failed to store, I have not yet found the screen shots for.

OK, I backed up 29 jobs, and deleted all jobs, and restored factory image, and reloaded my immediate jobs.
I also went BACK to version 4.0.0.1216, I am going to test things, to see what goes on.
I hope Javad company gets a group of programmers, that can fix some of this.
Nate

I have been running this 4.0.0.1219 for quite sometime now and have not seen that happen. My only issue I had is that it was storing on its own a staked out shot that I had paused from running and after a certain amount of time it would store on its own and at that point I could not stakeout anymore because it was locked up only on the stakeout screen. I could go to collect and it would work. I would have to reboot to fix it. I did resolve that through my General Profiles by turning off auto store in that profile for staking with the help of Randy G. I beleive that was a work around and not a fix though software team needs to resolve. Other than that it has not given me trouble. I hope you work get it worked out.

 

[jack newsome]

Yesterday, I decided to be BOLD and updated to the latest, 4.0.0.1219.
I went to the field. I had it lockup on me, and I had it STORE a shot in DESIGN, (Pt. No 1288) when it was supposed to be SURVEY, This was in STAKE to LINE by 2 pnts. ALSO, it lost a couple of shots, that were done this way. 2 to be exact.

And, the above store shot (1288) has screen shots in DESIGN. The ones it totally failed to store, I have not yet found the screen shots for.

OK, I backed up 29 jobs, and deleted all jobs, and restored factory image, and reloaded my immediate jobs.
I also went BACK to version 4.0.0.1216, I am going to test things, to see what goes on.
I hope Javad company gets a group of programmers, that can fix some of this.
Nate

Nate, how do you go back to previous version of software and install?
Thanks

 

[Nate The Surveyor]

Well, I had recently moved UP to 4.0.0.1219, FROM 4.0.0.1216. Now, 16 is the RELEASE version. and 19 is the Pre-Release version.
So, I hit the GEAR button. It goes like this:
SUPPORT>Software>Updates>Gear Button. At this point, you can select "Release" (Recommended) (Green Color) or PRE-Release. (Yellow Color).

All I did, was select RELEASE, and update, and it took me back to RELEASE version, which is 4.0.0.1216
I'm not sure how far back you can go.
Nate

 

[Nate The Surveyor]

OK, I used Reverse Shift recently, and I learned a "Work Around". Circumstance is that you do a job, with 1500 coords. And, then another job comes along, on the same system. You don't want to go to the original base, because you will have hill shadow, and your base will be non attended. I want the base to be CLOSE to me.
1.) Set up base, set autonomous location.
2.) Go to prev base, and take shot. (This first shot, is for reference purposes, not for shift) Then, tell the LS what the desired coord is, and use M-Local to shoot , and allow it to add in the shift.
3.) Go back to your base, and shut it down, Then, restart the base, on a new coord. (Holding the updated base coord) NOW, go do your survey. Now, things work normally. It seems that the problems occur, when you DPOS that shifted base, to attempt to see it all. Don't Dpos that shifted group.

Nate

 

[avoidthelloyd]

Hey Friend. If you localize 99% of the time, why are you using DPOS at all? For elevation? In my workflow, DPOS is my route to my SPC's. All of my projects are related in this way, but if I didn't care about the SPC factor, I would just do it how we used to with a 5000,5000 or whatever... I'm curious what you get from DPOS?

 

[Nate The Surveyor]

Mr LLoyd,
I am a surveyor. surveyors want all the information possible.
I sometimes store a shot, before RTPK finishes. DPOS Base to Rover processing shows the RTPK point by dpos. IF this does not agree well with RTK, then I can post process the RTPK point, and often check it. (Points screen, highlight the point of interest, > > right arrow, right arrow, then post process selected point)
No legitimate activity in the LS, should cancel any other legitimate action. IF somebody has moved my base nail, and I have NOT set on the right nail, then DPOS will reveal it.
Also, if somebody has a base nail, NEAR mine, and somehow, somebody has set another NEAR mine, then I will catch it via DPOS.

Nate

 

[nusouthsc]

Mr LLoyd,
I am a surveyor. surveyors want all the information possible.
I sometimes store a shot, before RTPK finishes. DPOS Base to Rover processing shows the RTPK point by dpos. IF this does not agree well with RTK, then I can post process the RTPK point, and often check it. (Points screen, highlight the point of interest, > > right arrow, right arrow, then post process selected point)
No legitimate activity in the LS, should cancel any other legitimate action. IF somebody has moved my base nail, and I have NOT set on the right nail, then DPOS will reveal it.
Also, if somebody has a base nail, NEAR mine, and somehow, somebody has set another NEAR mine, then I will catch it via DPOS.

Nate

Nate,
I may be wrong, but I believe the Base to Rover processing in the points menu can be accomplished without DPOS. As long as you download the base file you should be able to do that.

 

[Nate The Surveyor]

Yes, you can. But, I like to monitor the base... ie if a year ago, it says it is at "Base1", and now it says it is 0.13' away, then other factors may be involved. Redundancy, and "Keeping up" with blunders are a hobby of mine.
Nate

 

[avoidthelloyd]

Nate,
If you are returning to a Base, are you not satisfied just checking in to a couple of points from that old project? It will confirm your base coordinates and you'll know you are good to go?

 

[Nate The Surveyor]

Nate,
If you are returning to a Base, are you not satisfied just checking in to a couple of points from that old project? It will confirm your base coordinates and you'll know you are good to go?

That part checks fine.
The rule is DON'T DPOS a shifted base.
But, you can dpos a non shifted base.
Somehow, the fall apart is happening in the DPOS sequence.
Nate