Changes in the data base have bit me twice

Nate The Surveyor

Well-Known Member
One of the wonderful things about the Javad LS is the concept that all points shot from a single base name, are made into a single entity, allowing that group to be shifted, as one. In math class, one is known as "Unity".

Well, this unity of points association broke on me twice now.

I have a job, that I started back about a year ago. Friday, I used the same job. Except, I set my base station about a mile SE of the old base station. I set the base up autonomous, and used "Reverse Shift" (press the SETUP hardware button 2x) to update the coordinate, for my new base station. Well, the connection between the points from that base, are, shall we say, not connected. It shifted my shot to the old point, but did not move my base. Thus, all my work was performed off the autonomous solution. I spoke with Shawn Billings about it. He said he'd seen it before, but that he did not often "Return to old jobs". I do it frequently. Also, he told me to watch for the "Shift Icon" to be sure it shifted.

On a previous Job, it DID shift it, but with an error.

So, I recommend, don't altogether trust this feature. (Reverse Shift). The best is to re occupy a point in the old data base, to check.... I had a check... I thought, because of dpos... however, dpos only shifts the BASE around, and moves none of the sideshots.

Also, I'd much appreciate being "Kept in the loop" Let me know when changes are made in the database. So, I can be extra watchful. (I'm assuming some changes were made in the data base, to allow PPK, and something bit me.)
I can salvage my day of work. But, figuring it out, has cost me 2 days of work now. And, I also have to re compute this job. (Shift is 1.78' horiz).


Thank you,

Nate
 

Shawn Billings

Shawn Billings
5PLS
On a previous Job, it DID shift it, but with an error.

Just to be clear. This issue was resolved as you will recall shortly after it was discovered months ago.

Regarding the current issue...
The problem seems to be that the old database was not accounted for when working with the newer versions of J-Field that supported base to rover processing and switching between various base solutions. The connection between the base and rover is not being recognized. Nate, I would recommend sending the project to support. It's an important issue for sure.
 

Nate The Surveyor

Well-Known Member
DPOS fundamentally failed this one... only the base gets moved.
And, I have NO PPK shots... So, I don't have any certainty at this point as to what is realllllll. I did take a shot on a previous base... and it missed by 1.81' (The amount + -0.02' of the shift) So, it's real fouwled up... Without help, (put database back together) I an sunk. I plan (unless programmers at Javad can help) to go, re occupy the base, and reshoot a dozen of my prev shot points. I am NOT even sure that the REVERSE SHIFT did it right....
Don'tcha just love it when your favorite machine is fowled up?
:)

File name is: Caddo Gap North

I just pressed the button, send to support... If all goes well, maybe it'll be there within the hour.


N
 

Nate The Surveyor

Well-Known Member
Shawn, on the prev job, it seems that we concluded the best solution was to abandon the Javad file, and start over, with all points being design points. I was able to finish the job, without this repair... but reverse shift was bad by o.20'. I have not had occasion to return to that job.
Thanks
N
 

Shawn Billings

Shawn Billings
5PLS
It does not appear that this issue is related to any database issue, but was caused by a corruption to the base connectivity to the rover points that was able to be reestablished using the tools in the points screen (Recover Base point, Recover DPOS session).
 

Nate The Surveyor

Well-Known Member
Because of this feature, of "UNITY" or "One" being the base, and all sideshots, taken from said base, It'd kinda be nice if we had a feature, so that we could select by base (& all sideshots, from said base) This way, when we come in from the field, we can download "By Base".
Not a critical thing, but maybe a handy thing.
Thanks,
Nate
 

Nate The Surveyor

Well-Known Member
I am "stuck" on the Pre release version. The other day, I moved to the "Release" version. Then, uploaded coords, went to the field, and it would not read the old coords.

Went to a Restaurant, with WIFI. I went BACK to Pre Release.

Now, it would read the old coords, but it would not read the new ones.

I had left the Thumb drive at home... so I went home, deleted all the new coords, and re uploaded the coords. It started working again.

Dpos worked right. Connectivity worked. All was happy in "Nate's World".

Then, Yesterday, I found that a new version of J-Field was out. (Pre Release). And, so I uploaded it. Now, connectivity is broken again.

The thing is, many of my jobs are "Ongoing". Work in a town, and simply add a few coords, and do another job. So, I add to the file. Leave the Job in the LS.

Such it is.

Should I try to go back to my previous version of Pre Release, or should I try to recover my base point?

Thank you,

N
 

Matt Johnson

Well-Known Member
5PLS
Downgrading to older versions of JField is usually never recommended. If there are changes to the database format, it can cause problems with projects that contain data from the newer version of JField.

We need to know your workflow which is causing the problems with base station sessions in order to try and replicate this problem.
 

Nate The Surveyor

Well-Known Member
Well, yesterday morning, it was an UPgrade, from ( hmmm I am not sure,) to J-field 2.0.5.775, that broke the connectivity to the sideshots.
Now, I am trying to go back... to what I was on,
 

Shawn Billings

Shawn Billings
5PLS
I've not lost any connectivity in Pre-Release. Going back and forth could be causing you some issues Nate.

I'll be free this afternoon. I need to get step by step details on how you are setting up your job. It could be that you are doing something different (not wrong, just different) that we are not doing that is causing you to see this and us not. I would not recommend going back though. Use the recovery tools to re-establish the connection for now.
 
Top