Ive been thinking of improvements to the LS

[Nate The Surveyor]

Add a chime or noise at the end of every iteration of RTPK.

Add a white button that shows total time of fixed solutions, that are in agreement, with each other (I'm told 6 minutes fixed, in agreement, is gold) maybe a graphic, showing total time per point, (temporary points in RTPK, that is)
RTPK * (star on screen) should be color coded, so that we can differentiate fixed and floats. And a distance to the closest epoch, from rtk. This is not always the lead rtk point. This can indicate that we are on the correct init point.
I'm sometimes on a point for 30-40 minutes, or more. I'll store multiple shots, until I achieve a level of comfort, with the point.
Ability to change from rtk to RTPK should be allowed any time, not just when both are present and available.
I'm sometimes on a point 2 or 3 minutes before I get any rtk clicks. I need to be able to tell if it moves, in the iterations of RTPK, independent of RTK. In fact, I need to be able to see what is happening, ie qc the RTPK. (See above)
I need to be able to SELECT all shots, or points where rtk, and RTPK are in disagreement by more than a specified value. (0.08' or such like)

I hope I'm not making a mosquito (nuisance) of myself. I'm posting alot lately. I'm experiencing dead afternoons, and only working mornings, because of some sort of bad satellite issues beginning at around 12:30, to 4:00 PM. I've ordered a T-3, and I'm hoping that will help with dead afternoon syndrome.
I hope adding a T3 will help. Then, I'll be needing the LS upgrade.
Building software seems like a never-ending task.
If I could write software, I'd....
Have calluses on my fingertips.
Nate

 

[Nate The Surveyor]

I've been working a very RTPK dependant job. Most all shots are RTPK, with a few rtk clicks. I am on many points for more time than RTPK can process. I'm waiting on a T-3, but it's not here yet.
I'm sure it's just a matter of time. A little like waiting for a baby to be born. A watched pot never boils!
Then LS+ time!
N

 

[Matt Johnson]

I am on many points for more time than RTPK can process.

How long are you collecting data? RTPK should be able to handle hours worth of data but the processing time increases as the amount of data increases.

 

[Phillip Lancaster]

The T3 is going to be a huge increase in productivity coming from a T2 but the LS+ working with a T3 is the goal.

 

[Nate The Surveyor]

the processing time increases as the amount of data increases

Yeah. I know. And, I don't at present have a way to "watch" RTPK. I want a mechanism, similar to rtk, that allows me to determine that 6 minutes has passed, and RTPK is in agreement with itself. Since processing time seems to go up exponentially, each minute that passes. So, I propose a TIME LIMIT on RTPK, where it restarts, internally. This means it could be on a single point, for 30 minutes. And during the FIRST session, only one iteration is good (one minute). And then during the second session only 3 minutes are good. Then during the 3rd session, only 6 minutes are good. When storing the point, it averages all the sessions that agree within a specified tolerance.
At present, I'm doing all the above MANUALLY. I'm proposing an automated process to accomplish this, all to one coord. Using RTPK only.
Also, I'm proposing that DPOS be allowed to divide 30 minutes of data into 30 parts, and do all the same as rtpk. RTPK has interrupts, where signal gets poor, and full data is NOT available, for RTPK. On this point, DPOS should be stronger than RTPK, due to having full data, (downloaded from the base) and RTPK only having part data, due to radio or other communication glitches.
As you know, I like good data. We are discussing mechanisms to get there from here. If you have better way, do it.
I'm doing all this already.
Thanks.
Nate

 

[Nate The Surveyor]

What if.....
RTPK could run in a continuous data string? And, just give a sampling at every 1 minute? , or at every major shift point? (Where the location jumps) Without stopping? Then, there would be no delays, when starting over, with the whole data pile, up to that moment? Would that even be possible?
Nate

 

[Matt Johnson]

I want a mechanism, similar to rtk, that allows me to determine that 6 minutes has passed, and RTPK is in agreement with itself.

One already exists. You need to use "Stop Survey When RTKP Solution is Verified".

To get 6 minutes in between sessions that agree divide 6 minutes the session interval and add 2 to get the required Min RTPK Verification Level. For example if you have the session interval set to 90 seconds this means that you need 6 sessions that agree.

 

[Nate The Surveyor]

Is this in release, or pre-release?
Thank you,
Nate

 

[Matt Johnson]

Is this in release, or pre-release?
Thank you,
Nate

PreRelease right now.

 

[Nate The Surveyor]

A one-button press, that takes you to a colorful graphic, that shows RTPK data: green is good, yellow is poor or benein, red is bad. And some basic numbers, telling some basic information. In ashtech tools, it gave us error ellipses, with direction and size. I've missed those error estimate ellipses. It's be good if we could see and compare both rtk, and RTPK ellipses, together, on the same graphic.
Nate the dreamer.....

 

[Darren Clemons]

PreRelease right now.

Are we still a couple weeks away from this moving to release? I have been patiently waiting (yeah, that’s REALLY difficult for me ) for this to get to release as I have been so busy I didn’t want to deal with some of the pre release bugs that sometimes are there.

My impatience got the best of me yesterday and I put one of my LS’s on pre release to check out some of what I’ve read and, wow, there are some great improvements such as some of the screenshots Matt attached above.

I have one very, very large job that I am working on that will continue throughout most of this year. If I decide to “pull the trigger” and go to prerelease and then work any in that job, I would not be able to “go back” to the current release version I’m sure. My question is, if I do go to pre release, once that version is moved to release, I can move back to release version as well, correct?

If the move is coming soon, I may just wait it out, especially on the LS I’m using on that particular job. I don’t want to have any compatibility problems with it for sure.

 

[Adam]

I don't think there is any problem moving between release and prerelease regarding project compatibility. Sometimes data base changes and the like will cause incompatibility. But I don't think thats the case now

 

[Nate The Surveyor]

On the check box rtk/RTPK must agree.
What does this mean?
Fully verified?
Or that the lead rtk point is in agreement?
Or that it has a few clicks that agree, but not necessarily the LEAD rtk group?
I realize we are "only in the beginning" of the possibilities, and capabilities of this gear.
Thank you,
Nate

 

[Darren Clemons]

I don't think there is any problem moving between release and prerelease regarding project compatibility. Sometimes data base changes and the like will cause incompatibility. But I don't think thats the case now

I wouldn’t have expected any issues if it was just Jfield or gnss updates, but the current pre release has a Linux update along with it. In the past when an OS change update was made work in that job couldn’t go backwards to the previous version..

 

[Matt Johnson]

On the check box rtk/RTPK must agree.
What does this mean?

Accept/Reject will be displayed after all RTK parameters have been with the exception of confidence. When Variety > 0 is met it will advance to Phase 2 without confidence being met. RTPK Verification is not required.

 

[Matt Johnson]

In the past when an OS change update was made work in that job couldn’t go backwards to the previous version..

When you install an update both the OS and J-Field updates must be installed together otherwise there could be compatibility issues. The action of not installing them together should be blocked now I believe.

 

[Nate The Surveyor]

Many times, in the field, I'm working on other things, while the LS is collecting.
After it achieves whatever settings, and the accept/reject screen is displayed, I would like it if it made a noise. At this time, any kind of noise will do, but an assignable noise would be nice. Especially as we will soon be able to controll the LS remotely, via Bluetooth and cell phone. This is something I will be using. A nice list of noises, from chime, to custom sounds, would really be cool.
Thank you,
Nate

 

[Michael Stazhkov]

After it achieves whatever settings, and the accept/reject screen is displayed, I would like it if it made a noise.

For manual and auto-stop we already have customizable sound ("On Stop Collect" event - it happens when accept/reject buttons are displayed):
Setup Action profile -> Options -> Survey Tones.

 

[Nate The Surveyor]

Ok, I'll be turning that on, along with trajectory coord!
Thank you!
Nate

 

[Nate The Surveyor]

One already exists

Well, isn't that a bit strong?
To say one already exists, to a guy using RELEASE, is to say I should be on pre release.
It'd be better to say: "one is in development, and is in pre release now... If and when it's moved to release, you will be able to see it. I've been on pre release before, and I've found that I generally don't want to be on pre release, unless I am made privy to things to watch for.

Fish or cut bait. I've decided that I should stick to fishing, as cutting bait, without an inside track, like you have is too risky to fishing!

My dad used to sing "I'm goin down to Rio, before I get old" he was 92 when he started singing it!
There's alot of work going into this LS program, that a general user is not aware of. Keep it up!
Thank you,
Nate