Reconciling the numbers...

[Nate The Surveyor]

I am baffled by what I see. I JUST SHOT point number 8.
THEN
I turned around, and am staking POINT NUMBER 8.
The distance to last, (white box, 1 square up, on right) says we are 0.015 ft horizontally, from the last shot, and 0.008 Vertically.

BUT, DTT, on the left says we are 0.337 from the target. Also, it says south 0.051 and West 0.333.

I cannot help but say that something is wrong.
After a while, I stored this shot. It still showed a discrepancy. BIZARRE! After storing the shot, the dist to last was the correct number.
But, I feel either that something is wrong, or the martians have landed. I cannot figure this out.


Nate

 

[Matthew D. Sibole]

Do a hard reboot and try it again. I have seen this before but it has been a long time.

 

[Nate The Surveyor]

It did this on the last job too. And, that was with another version of the software.
Are you saying that the display of wrong data, (the stake data) is a product of some sort of memory problem, where old data is getting used, and current data is not?
Well, the problem has persisted through two versions.
I can start a fresh job (The screen shot you see above was from a fresh job). and see if I can get it to happen consistently....
N

 

[Matt Johnson]

Nate can you attach the project archive to this thread?

 

[Nate The Surveyor]

OK, it's about 26 MB.

 

[Nate The Surveyor]

I have not dpos-ed it yet. This is how it came from the field.
It has screen shots. That show the problem.
N

 

[Mikhail Drakin]

Stake whiteboxes (DTT, CTT, North/South, Ahead/Back, etc) between Start and Stop use distance vector from current accumulated averaged position (not taking into account clusters) to target point. The "Distance to last" whitebox shows distance from current cluster position to previous point, hence the difference.

 

[Matt Johnson]

Stake whiteboxes (DTT, CTT, North/South, Ahead/Back, etc) between Start and Stop use distance vector from current accumulated averaged position (not taking into account clusters) to target point. The "Distance to last" whitebox shows distance from current cluster position to previous point, hence the difference.

I figured it was something like this. The stake whiteboxes should use the vector from the best group too.

 

[Mikhail Drakin]

Will be fixed in the next pre-release and then in release.

 

[Nate The Surveyor]

I just updated to version 2.0.5.786
Thank you.
I was not sure what was going on.
N

 

[Nate The Surveyor]

Got another update... now I'm in 2.0.5.791
hmmm

N

 

[Nate The Surveyor]

Got another update... now I'm in 2.0.5.794
I read carefully through the update notes. This release definitely addresses the subject of this thread.

Thanks.
N

 

[Nate The Surveyor]

Another update... 2.0.5.797.
Tell me when I can move over to the RELEASE version. Would you recommend that I STAY at 797, until the release version is that?
It looks like Release is now at 2.0.5.674.
Thanks.
N

 

[Matt Johnson]

Another update... 2.0.5.797.
Tell me when I can move over to the RELEASE version. Would you recommend that I STAY at 797, until the release version is that?
It looks like Release is now at 2.0.5.674.
Thanks.
N

You shouldn't switch to the release version until it has a number greater than or equal to the current version you have.

 

[Nate The Surveyor]

OK, thanks.
N

 

[Nate The Surveyor]

Just moved up to 2.0.5.802
A note in the release, mentions local system name. I'd LIKE to be able to name it as I like... Suggestions are ok, but I have struggled a bit, to get it to behave as I like. I often make LDP's. The name contains the scale factor in PPM. It might read like this: "9-6s-25w LOCAL 50k50k@102PPM"

 

[Matt Johnson]

Just moved up to 2.0.5.802
A note in the release, mentions local system name. I'd LIKE to be able to name it as I like... Suggestions are ok, but I have struggled a bit, to get it to behave as I like. I often make LDP's. The name contains the scale factor in PPM. It might read like this: "9-6s-25w LOCAL 50k50k@102PPM"

Any local system's can be named edited after pressing Save in the localization screen. You can also edit the name with "Adjust Grid-to-Ground & Rename". Using this feature it can also rename it with a "project name scale factor" format similar to what you suggested.

 

[Nate The Surveyor]

What did happen...several versions ago I might add.. was I tried "Adjust Grid-to-Ground & Rename", and wound up with several file names. for the same "localize". And, none would work... ( Bug Maybe?) Maybe I just try again. Hey, keeping up is a challenge. I am GLAD that the development of this product is on going.
N

 

[Matt Johnson]

What did happen...several versions ago I might add.. was I tried "Adjust Grid-to-Ground & Rename", and wound up with several file names. for the same "localize". And, none would work... ( Bug Maybe?) Maybe I just try again. Hey, keeping up is a challenge. I am GLAD that the development of this product is on going.
N

This has been in J-Field a long time, at least a year I think. Tapping the scale difference button and the accepting some value will append the scale factor to the name.

 

[Nate The Surveyor]

I'm probably doing SOMETHING out of sequence.... no matter. I have struggled with it... and not sure why.
N